WO2001076226A2

WO2001076226A2 - Video network

Info

Publication number: WO2001076226A2
Application number: PCT/US2001/008638
Authority: WO
Inventors: Thomas D. Fay; Sergei Tselin
Original assignee: Rms Networks, Inc.
Priority date: 2000-04-04
Filing date: 2001-04-04
Publication date: 2001-10-11
Also published as: WO2001076226A3; AU2001250868A1

Abstract

A method and system are provided which controls playing of video at one or more remote sites (102) by transmitting videos to be stored at one or more remote sites (102) to selectively play the stored videos.

Description

VIDEO NETWORK FIELD OF THE INVENTION

The present invention is directed to a video network and, more particularly, to a satellite-based video network for managing the display of advertising at one or more locations.

BACKGROUND OF THE INVENTION

The advertising industry is large and growing. Billions of dollars are spent every year on U.S. advertising and U.S. advertising sales continue to climb. The advertising industry is diverse and includes such media as television, newspapers, magazines, radio, specialty media, the Internet, outdoor billboards, direct mail and telephone directories. Television has historically been one of the leading medium for advertising, accounting for a substantial percentage of total advertising expenditures in the United States.

SUMMARY OF THE INVENTION

In accordance with one embodiment, a system and method is provided to control a playing of video at one or more remote sites. The system and method involves transmitting data corresponding to at least one playlist and one or more videos to be played to a remote site via satellite transmission such that video from the one or more videos are played at the remote site according to the playlist. The one or more videos may include at least one advertisement.

In accordance with a further embodiment, a system and a method is provided to facilitate playing of video at a remote site which involves maintaining data corresponding to at least one playlist and one or more videos to be played, the playlist and the one or more videos being received via satellite transmission; and playing video from the one or more videos according to the playlist. The one or more videos may include at least one advertisement.

Other and further aspects of the present invention will become apparent during the course of the following description and by reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate certain embodiments of the invention.

Fig. 1 illustrates a general overview of the components of a satellite-based network control system (NCS) in one embodiment;

Fig. 2 illustrates an example of how sites may be grouped in a health network;

Fig. 3 illustrates a general overview of the components of satellite uplink facility or facilities of NCS of Fig. 1; Fig. 4 illustrates a general overview of the components of network or remote site of NCS of Fig. 1;

Fig. 5 illustrates a general overview of the components of network or remote site which changes the playing of video, such as advertising, according to an inventory at that site; Fig. 6 illustrates a general overview of the components of network operations center of NCS of Fig. 1;

Fig. 7 illustrates a general overview of the components of NCS to enable client access over the internet to information regarding client advertisements played at one or more remote sites; Fig. 8 is a flow chart of a process by which video is transmitted to one or more remote destinations in accordance with one embodiment;

Fig. 9 is a flow chart of a process by which playlist(s) are transmitted to one or more remote destinations in accordance with one embodiment;

Fig. 10 is a flow chart of a process by which files at one or more remotes sites may be remotely deleted in accordance with one embodiment;

Fig. 11 is a flow chart of a process by which commands are transmitted in accordance with one embodiment;

Fig. 12 is a flow chart of a process by which a broadcast server of satellite facility of Fig. 1 transmits information and requests to one or more remote destinations in accordance with one embodiment;

Fig. 13 is a flow chart of a process by which requested j obs are queued in accordance with one embodiment; Fig. 14 is a flow chart of a process by which video or sequence of videos displayed at a remote site is changed or modified according to inventory information associated with that site;

Fig. 15 is a flow chart of a process by which clients of NCS may obtain information related to their advertising through a web site;

Fig. 16 is a flow chart of a process by which a web clients of NCS may obtain information related to their advertisements through a web site over the internet;

Fig. 17 is a flow chart of a process by which NCS provides information related to a client's advertisements to the client through a web site; Fig. 18 is a flow chart of a process by which video is delivered to one or more network sites via satellite transmission;

Fig. 19 is a flow chart of a process by which a playlist is delivered to one or more network sites via satellite transmission;

Fig. 20 is a flow chart of a process by which segments may be auto deleted;

Fig. 21 is a flow chart of a process by which files may be deleted; Fig. 22 is a flow chart of a process by which content may be updated manually;

Fig. 23 is a flow chart of process by which a broadcast server performs satellite transmission;

Figs. 24, 25, 26 and 27 illustrate an example of an update file; and Figs. 28, 29 and 30 illustrate an example of a playlist file.

DETAILED DESCRIPTION Recent developments in satellite technology, such as higher bandwidth and lower costs, have reduced many of the inefficiencies involved in using CDs and videotapes. Satellite distribution reduces the need for employees to update the programming and rewind the video tapes every day. New CDs and videos do not have to be sent to every location on a periodic basis, but may be done as a backup. Another advantage of satellite transmission is the ability to transmit very large files of data. Large video files are often too large to transmit through the Internet without a high speed Internet connection at the remote sites. With reference to the Figures, several embodiments of the present invention will now be shown and described. In accordance with an embodiment, Fig. 1 illustrates a general overview of a satellite-based network control system (NCS) 100 configured to manage display of video, such as advertising, at one or more remote sites. Each remote site includes a video network having one or more displays, preferably arranged at point-of-sale (POS) locations, for displaying advertising and, if desired, other video programs, according to playlist(s) associated with the site.

Video may be distributed to one or more of these remote sites through "store and forward" satellite transmission. Through store and forward, video may be transmitted not as a video feed but instead in the form of data, which can be reassembled differently at each location into a continuous program, such as according to playlist(s), and displayed accordingly.

Such an arrangement enables control, manipulation and monitoring of data at each receiving site, and provides the ability to control what, when and how video plays at each remote site. The advantages of store and forward over video streaming is that store and forward enables the video content to be varied and controlled on a regional or site basis.

Accordingly, the selection and display of advertising, as well as other video programs, may be customized or tailored for one or more remote sites to promote sales of specific products and/or services, to increase retail branding, to enable more efficient targeting of advertising to consumers, and so forth.

In general, NCS 100 provides a network operator with a set of tools to manage a video network at one or more remote sites. In one embodiment, the video network at one or more remote sites are retail video networks, e.g., display networks at locations where products and/or services are sold., such as at specialty and non-specialty retail stores.

More specifically, through satellite communications, NCS 100 may provide manual and/or automatic control over various functions involving the distribution, update, monitoring and display of video (including advertising and if desired other video programs) at one or more remote sites having one or more displays. These functions may include: (1) Maintenance of an index of each location with the site hard drive content and playlist;

(2) Transmission of video files to and update of video files at one or more destinations, such as at a remote network, remote state and/or remote site, via satellite;

(3) Transmission of playlist(s) to and update of playlist(s) at one or more destinations, such as at a remote network, remote state and/or remote site, via satellite;

(4) Addition, deletion or modification of video files, including advertising or other video programs, maintained, stored or currently played at or by one or more destinations, such as at a remote network, remote state and/or remote site;

(5) Rebooting and refreshing of components (e.g., servers, etc.) of one or more remote sites as well as stopping or starting playback at one or more remote sites;

(6) Monitoring including reporting and auditing of files and events (including display of video) at one or more remote sites, including checking hard drive content of a site or retrieval and review of performance data;

(7) Modification of time tables;

(8) Modification of video (e.g., advertising) played at a remote site according to inventory levels at the site; (9) Internet accessibility by clients to information associated with clients' advertisements played at one or more remote sites through an advertising tracking system. This information may include a number of times clients' advertisements played at a specific remote site, each remote site and/or all sites; the specific times clients' advertisements were played at a specific remote site, each remote site and/or all sites, and so forth. In addition to Internet access to the above, clients may also view their advertisements over the Internet; and

(10) Virtual geographic representation (e.g., a U.S. map) of each video network, with the status of every network site represented on the map by different color codes or other distinguishing trait(s). While various available video formats may be employed, NCS 100 preferably utilizes video in MPEG format, more preferably MPEG 1 or MPEG 2, in performing the operations described herein. Turning again to Fig. 1, for purposes of explanation, NCS 100 may be divided into the following subsystems, such as a network operations center 102, satellite uplink facilities 132, and one or more remote sites 152. Satellite uplink facilities 132 and the components thereof provide for satellite communications between network operations center 102 and any one of remote sites 152. Satellite uplink facilities 132 may provide unidirectional satellite communications from network operations center 102 to any one of remote sites 152, but preferably provides for bi-directional satellite communications therebetween. A randomization algorithm is preferably employed by satellite uplink facilities to minimize communications traffic when transmitting and receiving from one or more remote locations.

Referring to Fig. 6, network operations center 102 includes a network controller (NC) 105, video library 110, playlist library 115, and network operator workplace console(s) 120 having associated therewith a graphical display interface (GUI) 125. The components of network operations center 102 are connected to each other across network interconnections, preferably through a local area network (LAN) via Ethernet.

NC 105 may be a computerized system, such as a server, including conventional computer components, such as one or more processors, communications system for communicating across network, RAM, ROM and storage device (e.g., hard drive). NC 105 may also include an operating system 205, SQL server 210, update engine(s) 220 for updating playlist, video, etc. at one or more remote sites; a content tracking engine 225 for tracking video content and associated information distributed or maintained at one or more remote sites; playlist tracking engine 230 for tracking playlist(s) distributed and maintained at one or more remote sites; a grouping database 240 for maintaining information associated with a grouping, categorization, subcategorization of remote sites in NCS 100; as well as other programs for implementing the processes to be performed by NC 105, as discussed herein. These programs may be stored locally in NC 105 or in a location readily accessible by NC 105. NC 105 is preferably a Dual PHI based PC running Windows NT Server, SQL Server 7.0 and Internet Information Server. NC 105 may be connected to a broadcast server (discussed below) at satellite uplink facility 132, via a dedicated Tl line. NC 105 is configured to perform Location Management, Content Update Playlist Update, Hard Drive Maintenance, Remote Network DVS Control, Remote Location Auditing, Monitoring of one or more remote locations, such as a remote network, state and/or site. For example, NC 105 is configured to coordinate input from network operators received from one or more OWCs 120; track network site content such as playlist(s), video, display logs and so forth; track play list distribution to network sites, and monitor and respond to network events by either representing the event graphically or collecting event related statistics.

NC 105 further enables a client, such as an advertiser, to track and monitor video (e.g., advertising video) associated with the client for display at any one of remote sites 152. The user may communicate with NC 105 through a dedicated or non-dedicated network connection, or generally through the Internet.

Video library 110 maintains or stores video content including video segments and advertisements intended for distribution and display at one or more remote sites. Video library 110 may include sub-libraries or directories to maintain video according to categories, advertisers, products/services, and so forth. New video content is maintained in video library 110 for later distribution to remote sites by NC 105. Video library 110 may be default directories ("Libraries") on its LAN segment where MPEG files intended for distribution are located. Video files, such as completed segment and advertisement MPEG files, are preferably deposited by customers into their respective "Segment" and "Ad" Library in video library 110.

Playlist library 115 stores and maintains playlist files intended for distribution to one or more destinations. Playlist library 115 may include sub-libraries or directories to playlists video according to categories, advertisers or advertising clients, products/services, and so forth. OWC 120 may be a dedicated or non-dedicated terminal or PC-based system, including conventional computer components, such as one or more processors, communications system or interface for communicating across a network or with a networked device, RAM, ROM, storage device (e.g., hard drive), input device(s), display, printing device and so forth. OWC 120 includes an operating system (e.g., Windows NT) and a browser.

A network operator may employ OWC 120 to manipulate a digital video server (described below) at each network site 152. NC 105 converts selections made at OWC 120 into tables and SQL commands and sends this information along with the associated video files (e.g., MPEG files) to a broadcast server of satellite uplink facility 132 via a TCP/IP connection.

OWC 120 may be a PC workstation connected to NC 105 via TCP/IP. All the interfaces between OWC 120 and NC 105 are handled through a web-based Graphical User interface (GUI) 125, e.g., Internet Explorer 5.0, installed on OWC 120. The default monitor resolution for OWC 120 is preferably 1024x768. Using this interface, the network operator will be able to perform various functions, such as those described below, as well as to remotely control video-display operations at one or more remote destinations. Because the interface is web-based, the number of simultaneously connected operators may be limited by the NC's hardware which may be modified accordingly to increase or decrease a number of operator connections.

Through OWC 120, a network operator may perform various network- related functions and operations, including but not limited to: • Routine Updates including scheduling a transmission of updated playlists and segments;

• Network Site Administration including adding sites/deleting sites/suspending sites;

• Network Site Hard Drive Maintenance including auditing, file resynchronization, deleting old files;

• Network DVS Control including stop/start/pause/refresh/reboot operations; and

• Monitoring Network DVS system performance, for example, to check for compliance.

Fig. 7 illustrates a remote site 152 in which an advertising tracking method and system are provided for clients to track their advertisement and information associated therewith, through a web site. As shown, a web server 250 includes an advertising tracking program 255 for facilitating the provision of information associated with a client's advertisements on NCS 100 to the client. Web server 250 is connected to network operation center 102. Web server 250 is generally configured to receive requests from a client for information submitted through a web site or page, obtain the requested information from NCS 100, and provide the information to the client.

Client device 270 with a browser enables a user to access one or more web sites or pages to communicate with web server 250 to enable clients to obtain information associated with their advertisements, via the web site(s) or page(s). Clients may send requests for information and receive such information through client device 270.

Client device 270 may be a processor-based system which includes conventional computer components, such as a processor, RAM, ROM, storage device, user inputs and a display. Through the use of a web browser 275 of client device 270, a client may surf the Internet and access desired web sites or pages. Client device 270 may be a PC-based computer with a browser, a personal digital assistant (PDA) with a web browser, WebTV or any device with web browsing capability.

The advertising tracking system provided herein enables, for example, advertisers to verify through a web site at any time, 24 hours a day, every day, for each of their commercials or advertisements, various information-related to their advertisements, such as:

• a number of times client's advertising was displayed on a specific day, on a day-to-day basis, week-to-week basis, and so forth; • a number of remote sites playing the client's advertisement and an identity of those site; and

• the advertiser's advertisements currently stored or maintained in video library 110 or played at one or more remote sites, which may be viewed by the advertiser over the Internet; and Other information associated with the client's advertisement in NCS 100.

Referring to Fig. 3, satellite uplink facilities 132 may include a broadcast server (BS) 135 including a data collector application or program 140 and a multicast protocol engine 142, a satellite interface 145 and a satellite transmitter and receiver ("transceiver") 150. BS 135 is connected to NC 105 across a communications medium, and BS 135 is also connected to satellite transmitter/receiver 150 (e.g., satellite dish) or hub, across a satellite interface 145. BS 135 may be a computerized system, such as a server, including conventional computer components, such as one or more processors, communications system for communicating across network, RAM, ROM and storage device (e.g., hard drive). BS 135 may include an operating system 305, datacollector 140, multicast protocal engine 142, SQL server 310, a transmission job queue 315, an inbox 320 and an outbox 325 as well as other programs for implementing the processes to be performed by BS 135, as discussed herein. These programs and associated directories may be stored or maintained locally in BS 135 or in a location readily accessible by BS 135.

BS 135 is preferably a Dual PHI based PC system running Windows NT Server, SQL Server 7.0, and Starburst Omnicast 1.06.02 with an amount of storage sufficient to hold at least two full Digital Video Server shows. While BS 135 may reside at a variety of locations, BS 135 preferably resides at satellite uplink facilities 132 and is connected to NC 105 via a TCP/IP network.

BS 135 includes two logical components: data collector 140 (such as SQL 7.0 with an interface for a multicast protocol engine such as Starburst) and Starburst Omnicast Version 1.06.02

In a general transmission operation, NC 105 prepares a transmission job. When a job comes up in the transmission queue, BS 135 copies the assets into an appropriate multicast protocol engine directory (e.g., a Starbust directory), and NC 105 provides the transmission parameters directly to the multicast protocol engine. Upon completion of the j,ob, the transmission results are translated into SQL and placed in a database for access and analysis by NC 105. Likewise, performance reports received from the field are also stored in the SQL database for access and analysis by NC 105.

Data Collector 420 is a service running on BS 135 and reporting information (e.g., the current list of MPEG files, remaining hard drive space, software version numbers, and relevant day to day activity) to be retrieved and maintained from one or more remote sites.

Referring to Fig. 4, each remote site 152 may include a satellite transmitter/receiver 155 and a digital video server (DVS) 160 for managing the display of video at a remote site.

DVS 160 may be a computerized system, such as a server, including conventional computer components, such as one or more processors, communications system for communicating across network, RAM, ROM and storage device (e.g., hard drive). DVS 160 may also include satellite send and receive circuitry for transmitting and receiving, respectively, information via satellite.

DVS 160 further include programs or applications or databases, such as an operating system 405, playback manager 410, content update manager 415, status manager 420, playlist database 430, video library 435 and a timetable manager 440, as well as other programs implemented by DVS 160 to perform the functions and processes as described herein.

DVS 160 is preferably a Windows NT based system with at least a 400 MHz processor, 64 MB RAM, a 6 gigabyte or greater hard drive, a Microsoft Direct

Show compliant MPEG decoder board with Driver, PCI receiver and transmitter boards with associated software, and a Phillips Smartcard port.

DVS 160 operates as a receiver/player in a digital video broadcast network. DVS 160 receives digital video content (MPEG) and generates an analog video signal for air and play on video components. DVS 160 generates the signal, using a decoder from the playback assets on the hard disk of DVS 160.

The order of playback is controlled by the playlist on DVS 160. The assets on DVS 160 are updated on a regular basis by the network operator via OWC 120.

DVS 160 features include site-specific start and stop times, site-specific playlists, and site specific reporting of various performance parameters. DVS 160 is preferably configured to be completely hands off and does not require a keyboard, mouse or monitor. All operational aspects of DVS 160, including playlist, MPEG content, start/stop times and reporting parameters, are configured and controlled remotely from OWC 120 via a satellite network. DVS 160 may include Smartcard control to implement Philips Smartcard

TVs which may be employed as display 290. The Smartcard implementation may include the following:

• TV turned on/off with the start and stop of playback;

• On volume equivalent to last volume; • Front panel locked out;

• Volume change requests from front panel are forwarded back to the TV; and • Report information from the TVs consists on On/Off verification and video signal present. This enables tracking of each video display in each location. The ability to control the video display increases in-store compliance by reducing risks associated with manual operation, since televisions activate automatically and may not be manually turned off.

As discussed above. DVS 160 may include a number of software programs for use in performing various features and functions described herein. These may include Digital Video Playback Manager (DVPM) 410, Time Table Manager (TTM) 440, Content Update Manager (CONUM) 415, and Status Manager (SM) 420. Digital Video Playback Manager (DVPM) 410 is a service that controls all aspects of MPEG playback. DVPM 410 uses one configuration file for the playlist, PLAYLIST.INI. PLAYLIST.INI is an ASCII text file that indicates which MPEG segments and ads are to play at that Network Site. The MPEG files will play in the order they appear in the PLAYLIST.INI file. After playing all files listed, DVPM 410 will cycle back to the top of the file and begin replaying the MPEG files again. This procedure is repeated until the stop time as defined in a timetable file, which may be modified by a network operator via GUI 125 of OWC 120.

Time Table Manager (TTM) 440 is a service that controls scheduling aspects of DVS 160 and uses one configuration file TT.INI. TT.INI is an ASCII file that provides the timetable for the Network DVS processes. The timetable specifies start and stop times for video playback as well as the time and day for submission of performance data to NCS 100. The timetable may be based on a 7-day week, and can be customized on a Sunday through Saturday basis or in a time frame as desired.

Content Update Manager (CONUM) 415 monitors for and executes commands from NCS 100 to copy, move and/or delete files. Commands are ASCII text files named UPDATE.INF. All instructions and commands from NC 105 are received in this format.

Status Manager (SM) 420 monitors system performance, collects performance data, and reports information about the network site DVS 160 to data collector 140.

Furthermore, DVS 160 may play videos in a variety of ways, including for example: Content Rotation - Advertisement in a particular slot may be rotated. For example, in a simple playlist without content rotation, if an advertiser purchases a 30- second spot that runs each half-hour in a 2-hour show, only four different advertisements can be rotated throughout the day. With content rotation, an unlimited number of client advertisements may be rotated in the client's time slot.

Real Time Content - Show content can also be rotated out on a real time basis. Weather and/or sports scores and schedules can be changed on a daily basis or more frequently, if desired.

Daily Scheduling - Multiple playlists can be utilized during the course of the day. For example, training can be scheduled for early and late hours. Similarly, the show can be appropriately targeted to the correct audience, so that family fare would show during core daylight hours while more adult oriented content could be shown in the evening hours.

Once Through - The playlist can be configured to state at a specific time and cycle through only once. This feature can be utilized for training material where it is intended for viewing at exact time.

Referring to Fig. 5, there is provided a system which may be incorporated into NCS 100 or other video display networks (e.g., non-satellite based systems or video networks) to enable modification of the display of video at a remote site according to inventory information associated with the site. As shown, at a remote site, an inventory management system 510 includes an inventory program for tracking the inventory of products and/or services available at the remote site and an inventory database 520 for storing information associated with the product and/or services at the site. One or more input/output devices 525, such as a cash register, communicate with inventory management system to update the inventory information.

Inventory database 520 may include inventory information which identifies the products and/or services available at the site, a quantity of the products or services available at the site, a current price of the products and/or services at the site, a price range of the products and/or services at the site and so forth. The products may be identified by SKU number or other product and service identifiers.

At a remote site, DVS 160 communicates with inventory management system 510 and receives or retrieves inventory information therefrom. DVS 160 may modify the playing of advertisement at a site according to inventory information, such as a product and/or service inventory level. These modifications may include:

• Preventing or Prohibiting play of a product or service advertisement if the availability of the product or service is below a predetermined amount; • Replacing play of a product or service advertisement with an alternative advertisement of a different product or service if the availability of the product or service is below a predetermined amount;

• Modifying a number of times a product or service advertisement on a playlist is played if the availability of the product or service is above or below a predetermined amount;

• Modifying the price in a product or service advertisement if the availability of the product or service is below or above a predetermined amount. For example, if the quantity of a product is high, the advertised price to be played may be reduced to promote sale. If the quantity of a product is low, the advertised price to be played may be increased to increase revenue. The modification of the advertised price may be subject to some predefined price range for the product or service; and

• Adding play of a product or service advertisement if the availability of the product or service is above a predetermined amount. For example, an advertisement previously prohibited from play may be played when the associated product or service is more readily available at the site (e.g., a new shipment of the product). Also, the playing of an advertisement for a new product or service may be initiated by DVS 160 upon detection of the new product or service through the inventory information. DVS 160 may search locally for a video file associated with that product or service or may request advertisement video from NC 105 for that product or service, if available. This may be accomplished through the SKU identifier or other product or service identifiers related to the product or service.

Figs. 24, 25, 26 and 27 illustrate an example of a command file generated or prepared by NC 105 to remotely control one or more remote sites according to control selections by a network operator or generally NC 105. Figs. 28, 29 and 30 illustrate an example of a playlist. As shown, the playlist identifies one or more video files arranged in an display order for one or more associated remote sites, hi this example, the playlist includes 101 video items to be displayed in one cycle.

Various network operations or features of NCS 100 are further described below.

Location Management

The location management module provides the capability to add and delete sites from the system, and edit or suspend individual sites that are already in the system.

The playlist start and stop times can be controlled individually for each site. The information maintained for each site may include, for example:

Unit # (7 Digit Integer) Playback Start Time

IP # Playback Stop Time

Office Name

Street Address City

State

Zip

Market (e.g., New York 1)

Subnetwork (e.g., Pediatrics)

The TCP/IP address is displayed. However, the network operator may be prohibited from modifying or deleting this information if satellite uplink facility 132 employs an algorithm to derive the TCP/IP address based on the Unit Number.

Grouping

In order to target specific markets and demographics, the sites within NCS 100 may be grouped according to various parameters, such as geographic location, business specialty, or demographic audience. Each group may then be treated as a single entity so that actions affecting the configuration of the hard drive are performed on a group basis. Show updates, playlist changes and content deletions are performed concurrently on all sites within a specific group. However, actions that do not affect the hard drive configuration, e.g., stop/start, report and reboot, may be performed on a site- specific basis.

For example, as shown in Fig. 2, four levels of grouping may be provided as an example in a health network. At the top level is the entire health network. The second tier may include the three subnetworks, General Practitioner, OB/GYN, and

Pediatrics. Within each of the three subnetworks are the individual groups, comprised of specific sites. The total number of groups across all three subnetworks preferably does not exceed 256. To maintain the integrity of the grouping, a site preferably belongs to one Subnetwork and one group within that Subnetwork. The parameters for each group include, for example, Group ID (i.e., Group

Number), Group Name, Description, and reporting schedule (day/time). A mechanism will be provided to create new groups, delete groups, reassign a site from one group to another, combine groups together to form larger groups, and suspend a site or group. In this module, the network operator will have the ability to filter sites for selection using various fields under location management; Zip Code, City, State, Market and

Subnetwork. When a site is moved from a group in one Subnetwork to a group in a different Subnetwork, the system will automatically change its Subnetwork assignment.

Add/Delete/Edit/Suspend Sites NCS 100 may be configured to provide a network operator the ability to add, delete, edit or suspend sites in the database will be as simple as choosing the desired action and entering the required information. The functions available include Add a Site, Delete a Site and Edit a Site (editing also includes the ability to suspend a site). If adding a site, the network operator will be required to enter the location management information discussed earlier. The network operator will have the option of assigning the new site to an existing group. When deleting a site, the network operator selects the site to delete from the list and click on Delete. To edit an existing site, the network operator selects the site from the selection window and clicks on Edit. Each field will be filled with the previously supplied information. Simply change the necessary fields and click on the Update button.

Suspend will be used when sites are entered in the system, but are not yet operational, or are temporarily out of service. The network operator should suspend a site to prevent it from appearing in the selection window and to minimize unnecessary satellite traffic.

Synchronization All sites within a defined group need to maintain the same hard drive configuration (MPEG assets and playlist). Therefore, when a new site is added to a group, a site is reassigned to a different group or a site has been in suspend mode. NCS 100 provides a mechanism to synchronize the HD content of the site with the benchmark for the group to which it is assigned. The synchronization process will determine the hard drive content of the site, compare that with the benchmark for the group, and transmit the files necessary to achieve the benchmark. The network operator will also be able to synchronize an entire Group if desired. In order to perform synchronization, the requisite MPEG assets and playlists should be available for the system (e.g., located on BS 135).

Content Update

NCS 100 may provide for the update of content at one or more remote sites. Through GUI 125 of OWC 120, a network operator may commence an update operation for one or more remote sites, e.g., one or more DVSs 160. For example, an update operation may involve the following: • Client loads completed video content or assets into a default directory of video library 110;

• Network operator selects files for transmission;

• Network operator builds recipient list of one or more predefined groups; • Network operator selects immediate or delayed (e.g., scheduled) transmission;

• NC 105 loads video files onto BS 135 via connection;

• BS 135 transmits files via multicast using multicast protocol engine (e.g., Starburst engine); and • Transmission results are compiled for and displayed to the network operator. The transmission may involve, for example, the following process, e.g., files are loaded onto BS 135 and then transmitted using a multicast protocol engine (e.g., Starburst). Through the use of GUI 125, the network operator can accelerate the process by preloading the files onto BS 135 as they become available (e.g., as encoding is finished). Once files are loaded on BS 105, they are maintained there until deleted by the network operator. This precludes having to load the same files onto the BS 135 repeatedly.

NC 105 maintains a Queue of pending transmissions. Jobs are started as soon as possible after their scheduled start time, depending on the duration of the previous job and with "immediate" jobs taking precedence. The network operator may access this job queue to modify job priority, reschedule or delete jobs, check job status, or place jobs on hold. When jobs are first submitted, NC 105 will provide an estimated completion time (ECT) depending upon the size and number of jobs in the queue. The accuracy of these times will improve as additional broadcasts are performed. ECT may not be available during initial operation while the system is accumulating performance- related statistics.

Using the transmission results from the multicast protocol engine, NC 105 will prepare a transmission report for the network operator to review along with a retransmission job that will send missing files to appropriate locations. The network operator will have the option of sending the job as is, modifying the job or deleting it.

Playlist Update

In one embodiment, NCS 100 provides for the update of playlist(s) for one or more remote sites. Digital Video Playback Manager 410 (Fig. 4) on DVS 160 may be employed to control the sequence of video file play back according to a playlist(s). The playlist may be an ASCII text file processed by Playback Manager 410.

A network operator may commence update playlist operation to update playlist(s) for one or more remote sites, e.g., for one or more DVS 160, via GUI 125 of OWC 120. For example, the playlist update process may involve the following: • Client loads completed playlists into the default directory of the playlist library; • Network operator selects playlist for transmission; • Network operator builds recipient list of one or more predefined groups;

• Network operator selects immediate or delayed (e.g., scheduled) transmission • NC 105 confirms that the files needed by the playlist exist in the Hard

Drives of the selected sites;

• NC 105 loads playlist onto BS 135 across a connection;

• BS transmits playlist via multicast using a multicast protocol engine, such as a Starburst engine; and • Transmission results are compiled and displayed to the network operator. The scheduling mechanism for playlist delivery is similar to that discussed above for content update.

Auditing

NC 105 maintains an up to date image of the hard drive (HD) on each DVS 160 in the network by recording every update in a database. This database tracks the desired content of the HD (the "benchmark") for each Group. NC 105 also records every transmission completion report and tracks files that are not delivered. This mechanism tracks the "actual" HD content of each remote site.

NCS 100 may provide several capabilities and functions with this system:

• NC 105 may provide Audit reports listing which files are missing from individual site HDs based on the benchmark Group content; • NC 105 may prepare synchronization updates which transmit missing assets to individual or groups of sites; and

• A network operator may request a Remote Audit of a site, group or entire network which will compare the HD content reported from the remote site or sites in the field to the information stored in NC 105 and update the NC information.

File Deletions

As time goes by and assets become outdated, it will be necessary to delete them from the memory or hard disks of DVS 160 or accessed by DVS 160. A network operator through GUI 125 of OWC 120 may implement a manual and automatic function to accomplish the deletions.

Auto Delete- In this process, NC 105 automatically deletes outdated show segments (excluding ads). This would normally be accomplished after a show is updated with new content and a new playlist. The network operator selects the autodelete function via GUI 125 of OWC 120, builds a list of site groups where he or she wishes to accomplish the deletion, and executes the command. The actual Autodeletion is performed by DVS 160 which compares the content of the directory that holds the show segments with the segments in the currently loaded playlist.

Manual Delete- In this process, the network operator selects the affected sites and which files to delete from each site. For example, network operator builds a list of locations where the network operator wishes to delete files by selecting a Group (e.g., a group including one or more remote sites). NC 105 builds and displays list of files located on the hard drive (HD) of those sites. Network operator selects which files are to be deleted. NC 105 compares files selected for deletion to current playlist content at each affected location and warns the network operator if any files targeted for deletion are on a current playlist. Thereafter, NC 105 executes the delete command for target sites.

Scheduling and delivery of the deletion command are handled in the same manner as other transmissions. Upon completion of the command, NC 105 will generate a completion report.

Remote Network DVS Control

NCS 100 may be configured to directly control playback for one or more remote sites. The following commands can be sent to one or more remote sites by a network operator using through the use of GUI 125 on OWC 120:

• PLAY - Starts playback using the latest playlist transmitted to the Network DVS;

• PAUSE - Stops playback at the current frame in the show (image freezes). Playback will resume from this point when PLAY is selected;

• STOP - Stops playback completely (screen goes blank). The PLAY command must be used to resume playback, and playback will start at the beginning of the current playlist;

• REFRESH - Immediately reinitializes playback at the beginning of the current playlist;

• REPORT - Initiates request for Network DVS to transmit performance data for the current period. (See also Manual Monitoring); • HD AUDIT - Initiates a query of the remote site requesting an inventory of hard drive (HD) content. NC 105 compares this inventory with the data maintained by NC 105, displays any discrepancies, and updates the NC data accordingly. (See also Manual Monitoring);

• UPDATE TIMETABLE - Creates a new timetable based on latest playback start/stop times and report day/time entered for selected site under Location

Management. Revised timetable is automatically forwarded to selected location. Monitoring

NCS 100 provides for monitoring of one or more destinations. Two monitoring examples, Automated Monitoring and Manual Monitoring, as discussed herein. In Automated Monitoring, each DVS 160 of a remote site collects data on performance of the system on a daily basis and stores that data locally on the HD. DVS 160 forwards that information to the data collector 140 of broadcast server 135 of satellite uplink facility 132. This information may be forwarded based on a predetermined schedule or specified in a DVS timetable, e.g., every day, once a week, a specified time and/or date, and so forth. The information which may be collected may include:

• Total run time for the system in minutes;

• Total playtime in minutes;

• Percentage (%) Compliance (total playtime/playtime specified in timetable) on daily basis; • Date/Time of last report;

• Date/Time of current report;

• Number of system restarts in reporting period;

• Total number of playlist cycles in reporting period; and

• Number of user logons in reporting period.

In Manual Monitoring, a network operator should select a remote site with a DVS 160 to query, type of data to be retrieved from the site, request processing options and execute the request. It is preferred that, in the case of Manual Monitoring, DVS 160 does not erase the collected data automatically. If the network operator wishes to reset a DVS's data collector, that should be specified in command parameters (See Remote Control).

Reporting

A series of predefined reports may be provided on a national, state, city, server level and so forth. These reports can be viewed through OWC 120 or printed out. Examples of report-types provided by NCS 100 may include: • Compliance Reports, which summarize the overall reliability of servers within a geographic area;

• Operations Reports, which provide performance data (total play time, individual compliance data) for each store within a given population; • Store Reports, which provide a complete picture of a Network DVS

(HD content, start/stop times, playlist date/time stamp, etc.);

• Compliance Maps - Visual compliance maps are provided at the national, state, and, in certain cases, metropolitan level. Color codes provide information on general compliance levels for the geographic areas displayed. At higher resolution levels, individual server locations are displayed with color-coding. Compliance and detailed information for a specific location can be obtained by clicking the desired location on the map.

While the reporting feature is discussed above as providing reports on a national, State (e.g., NY, CT, etc.) or server level, NCS 100 may provide for reporting on other groupings or categories, as desired.

A more detailed description of the various operations and functions described herein will be described below with reference to the flowcharts of Figs. 8-23. Fig. 8 illustrates a flow diagram of a video transmission process 800 by which video files are transmitted to one or more remote sites. At steps 802 and 804, a network operator selects a file transmit option and selects a file selection option, respectively, through GUI 125 of OWC 120. At step 806, the network operator then selects one or more video files, e.g., video segments or advertisements, to be transmitted. These files may be selected from video library 110, which is preferably designated as a default directory. At step 808, the network operator then selects a desired destination (e.g., a network, state or remote site) to transmit the selected files. For example, the network operator adds the selected destination onto a destination transmit. At step 810, NC 105, via OWC 120, checks whether the destination identification is complete, e.g., whether the network operator has completed selections of the destinations to receive the selected video files. If the destination identification is not complete, the network user may select additional destinations to add onto the destination list at step 812. Steps 808 and 812 are repeated until all the desired destinations have been selected. Otherwise, if the destination identification is complete, the network operator may then initiate a transmit operation or command at step 814.

Thereafter, at step 816, NC 105 creates a transmit table and SQL file ("XT/SQL') and initiates a process to resolve available memory space (e.g., hard drive (HD) space) with hard drive table (HDT) and video updates in the job queue. This preferably excludes proposed deletion operations.

At step 820, NC 105 checks whether the free memory of the remote sites receiving the selected files exceeds a first predetermined amount or percentage, such as 20%. If not, NC 105 checks whether any remote site's memory is less than a second predetermined amount or percentage, such as 10% at step 824. If memory is less than the second predetermined amount or percentage, NC 105 identifies those remote sites for display on OWC 120 to the network operator at step 826. The process 800 then returns to step 804 to enable to network operator to recommence the selection process or operation or to exit or terminate video transmission process 800. If the memory of the remote sites is greater than or equal to the second predetermined amount or percentage (e.g., 10%), NC 105 identifies those remote sites with free memory less than a third of the predetermined amount or percentage (e.g., 20%) which is provided to OWC 120 for display to the network operator at step 828. At step 830, the network operator may revise the transmission parameters via GUI 125 of OWC 120. If the transmission parameters are revised, NC 105 identifies those remote sites with free memory less than a fourth of the predetermined amount or percentage (e.g., 10%) which is provided to OWC 120 for display to the network operator at step 832. The process 800 then returns to step 804 to enable to network operator to recommence the selection process or operation or to exit or terminate video transmission process 800. Otherwise, at step 834, NC 105 identifies those files that will be overwritten at the receiving remote site(s) and, at step 836, request confirmation for the file overwrites. If the file overwrites are not confirmed, the process 800 then returns to step 804 to enable to network operator to recommence the selection process or operation or to exit or terminate video transmission process 800. If a confirmation is received at step 836, the network operator may select a transmission period, e.g., immediate transmission or scheduled transmission at step 838. At step 840, the transmission parameters are displayed by OWC 120 to the network user for confirmation. If the transmission parameters are not confirmed, the process 800 then returns to step 804 to enable to network operator to recommence the selection process or operation or to exit or terminate video transmission process 800.

If the transmission parameters are confirmed at step 842, the transmission event is logged, e.g., stored in a log or an equivalent thereof, at step 844. NC 105 converts selections made at OWC 120 into tables and SQL commands ("XT/SQL") and sends this information along with any associated video files to BS 135. The XT/SQL is placed on the job queue at BS 135.

Fig. 9 illustrates a playlist transmission process 900 by which one or more playlists are transmitted to one or more destinations.

At step 902, new or formatted playlist(s) are placed in inbox of playlist library 115.

At step 904, a network operator selects a playlist to transmit from playlist library 115 via GUI 125 of OWC 120. At step 906, the network operator then selects a desired destination (e.g., a network, state or remote site) to transmit the selected playlist. For example, the network operator adds the selected destination onto a destination list. At step 908, NC 105, via OWC 120, checks whether the destination identification is complete, e.g., whether the network operator has completed selections of the destinations to receive the selected video files. If the destination identification is not complete, the network user may select additional destinations to add onto the destination list at step 910.

Otherwise, at step 912, if the destination identification is complete, the content (e.g., video files) identified on the selected playlist is compared with a table 914 (e.g., hard drive table (HDT)) identifying content stored or maintained at the selected destinations. This table may be stored or maintained by NC 105 and updated accordingly as content is added or deleted at a destination. At step 916, the content identified on the selected playlist is compared with video updates in a job queue 918 to check whether content (e.g., files) missing at the selected destinations are being transmitted to the selected destinations. At step 920, NC 105 then determines whether the playlist content exists at the selected destinations, e.g., is stored at or being transmitted to the selected destinations. If not, NC 105 identifies the missing playlist content files and a number of destinations (e.g., number of remote sites) where the files are missing and this information may be provided to the network operator, via OWC 120, at step 922. If the network operator requires more detail, then NC 105 may identify destinations (e.g., remote sites) where specific files are missing and this information may be provided to the network operator, via OWC 120, at step 926. Otherwise, at step 928, the network operator is prompted whether to proceed with the transmission of the selected playlist. If not, the process 900 then returns to step 904 to enable the network operator to recommence the selection process or to exit or terminate the playlist transmission process 900.

In either case where the network operator confirms continuance of transmission at step 928 or the playlist content exists at the selected destinations at step 920, NC 105 generates transmit tables and SQL commands (XT/SQL) according to the selections, at step 930. That is, the network operator selections are converted to XT/SQL. The network operator may then select a transmission period, e.g., immediate transmission or scheduled transmission at step 932. Thereafter, the network operator is requested to confirm transmission, via

OWC 120 at step 934. If the transmission is not confirmed, the process 900 then returns to step 904 to enable the network operator to recommence the selection process or to exit or terminate playlist transmission process 900. Otherwise, at step 936, the transmission event is logged or recorded, e.g., stored in a log or an equivalent thereof. NC 105 then sends this the XT/SQL information along with any associated video files to BS 135. The XT/SQL is placed on the transmission queue at BS 135.

Fig. 10 illustrates a deletion process 1000 by which video content, e.g., video files or segments, stored or maintained at one or more destinations are deleted.

At step 1002, the network operator selects the HD maintenance operation or command, via GUI 125 of OWC 120.

At step 1004, the network operator selects delete segments (or ads) operation to implement a manual deletion process. At step 1006, the network operator initiates a selection destination operation or command to implement deletion at one or more destinations (e.g., a network, State, City, site or so forth. At step 1008, the network operator then selects a desired destination for performing a deletion operation. For example, the network operator adds the selected destination onto a destination list. At step 1010, NC 105, via OWC 120, checks whether the destination identification is complete, e.g., whether the network operator has completed selections of the destinations to perform the deletion operation. If the destination identification is not complete, the network user may select additional destinations to add onto the destination list at steps 1006 and 1008. Otherwise, if identification is complete, NC 105 generates a list of video files (e.g., video segments or ads) with number of sites at step 1012. At step 1014, the network operator may request additional detail. If requested, NC 105 generates a list of sites for the selected video files at step 1016.

At step 1018, the network operator may select video files from the list to delete. At step 1020, the deletion selections are compared to the playlist(s) of the selected sites from a playlist table 1022. At step 1024, NC 105 determines whether a conflict exists, e.g., whether the deletion selections would delete video files on the playlist of the selected sites. If so, a list of video files with conflicts are displayed to the network operator, via GUI 125 of OWC 120. At step 1028, the network operator may request additional detail. If requested, NC 105 generates a list of sites for the selected video files at step 1030. In any event, a step 1032, the network operator is provided with the option of revising the destination list at step 1006 or the deletion list at step 1018.

If the network operator does not choose to revise the destination or deletion list, NC 105 generates an update file (e.g., update.inf) associated with the deletion selections at step 1034. At step 1036, the network operator may then select a transmission period, e.g., immediate transmission or scheduled transmission. Thereafter, at step 1038, NC 105 generates transmit tables and SQL commands (XT/SQL) according to the selections. That is, the network operator selections are converted to XT/SQL.

At step 1040, the network operator is requested to confirm deletion, via OWC 120. If the transmission is not confirmed, the process 1000 then returns to step 1006 to enable the network operator to recommence the selection process or to exit or terminate file deletion process 1000. Otherwise, if the network operator confirms the deletion operation, the transmission event is logged or recorded, e.g., stored in a log or an equivalent thereof at 1042. NC 105 then sends this the XT/SQL information along with any associated video files to BS 135. The XT/SQL is placed on the transmission or job queue at step 1044. The above describes a manual deletion operation. An automatic deletion operation will also be described below with reference to Fig. 10.

At step 1050, the network operator may select an automatic deletion operation. At step 1052, the network operator initiates a selection destination operation or command to implement deletion at one or more destinations (e.g., a network, State, City, site or so forth. At step 1054, the network operator then selects a desired destination for performing a deletion operation. For example, the network operator adds the selected destination onto a destination list. At step 1056, NC 105, via OWC 120, checks whether the destination identification is complete, e.g., whether the network operator has completed selections of the destinations to perform the deletion operation. If the destination identification is not complete, the network user may select additional destinations to add onto the destination list at steps 1052 and 1054.

Otherwise, if the identification is complete, NC 105 prepares an update file (e.g., update.inf) associated with the deletion selections at step 1058. At step 1060, NC 105 generates transmit tables and SQL commands (XT/SQL) according to the selections. That is, the network operator selections are converted to XT/SQL. At step 1062, the network operator may then select a transmission period, e.g., immediate transmission or scheduled transmission. At step 1064, the network operator is requested to confirm automatic deletion, via OWC 120. If the automatic deletion is not confirmed, the process 1000 then returns to step 1050 to enable the network operator to recommence the automatic deletion process or to exit or terminate file deletion process 1000. Otherwise, if the network operator confirms the deletion operation, the transmission event is logged or recorded, e.g., stored in a log or an equivalent thereof at step 1066. NC 105 then sends this the XT/SQL information along with any associated video files to BS 135. The XT/SQL is placed on the transmission or job queue at step 1068.

Fig. 11 illustrates a command process 1100 by which predefined commands are transmitted to one or more remote sites.

At step 1102, the network operator selects the Command Option operation or function. At step 1104, the network operator then selects a desired destination (e.g., a network, state or remote site) to transmit command(s). For example, the network operator adds the selected destination onto a destination list. At step 1106, NC 105, via OWC 120, checks whether the destination identification is complete, e.g., whether the network operator has completed selections of the destinations to receive the selected video files. If the destination identification is not complete, the network user may select additional destinations to add onto the destination list at step 1108.

Otherwise, at step 1110, if the destination identification is complete, the network user is provided with options to select a specific command, such as:

• Report (single site); • Report - Delayed (multiple sites);

• Reboot (single site);

• Refresh (multiple sites);

• Stop Playback (single site);

• Start Playback (single site); • HD Audit (single site); and

• HD Audit - Delayed (multiple sites).

At step 1112, the network operator initiates a transmit operation of the selected command to the selected sites.

At step 1114, NC 105 generates an update file (e.g., update.inf) associated with the command selections. At step 1116, NC 105 generates transmit tables and SQL commands (XT/SQL) according to the command selections. That is, the network operator selections are converted to XT/SQL files. At step 1118, the network operator may then select a transmission period, e.g., immediate transmission or scheduled transmission. At step 1120, the network operator is requested to confirm the command execution, via OWC 120. If the transmission is not confirmed, the process 1100 then returns to step 1102 to enable the network operator to recommence the command selection process or to exit or terminate command transmission process 1100. Otherwise, if the network operator confirms execution, the transmission event is logged or recorded, e.g., stored in a log or an equivalent thereof at step 1122. NC 105 then sends this the XT/SQL information along with any associated video files to BS 135. The XT/SQL is placed on the transmission or job queue at step 1124.

Fig. 12 illustrates a flowchart of a process 1200 by which broadcast server 135 implements transmission tasks or jobs from NC 105.

At step 1202, BS 135 received XT/SQL files from NC 105. At step 1204, BS 135 determines whether the data files to be transmitted exist on BS 135. If not, BS 135 obtains those files to be transmitted and not at BS 135 from content directories 1208 of NC 105, via Tl/Internet. These files are then transmitted to BS assets 1210 of BS 135. BS assets 1210 may store or maintain files previously received from NC 105.

At 1212, if the data files exist at BS 135, BS 135 generates transmission files in a format suitable for transmission by multicast protocol engine based on the XT/SQL files from NC 105. For example, if a Starburst engine is employed, BS 135 may generate *.jtx files including the IP addresses of the sites to receive the transmission as well as the files to be transmitted.

At step 1214, the transmission files are then placed on a job queue for execution. At step 1216, the SQL timer is set to a time period greater than, for example, one minute. At step, 1218, BS 135 determines whether a transmission is in progress. If so, the SQL timer is reset to a time period greater than one minute at step 1216. Otherwise, if no transmissions are in progress, BS 135 determines whether the current transmission job on the queue is scheduled for transmission at step 1220. If not, the next immediate transmission job is obtained at step 1222.

If the transmission job is scheduled, BS 135 determines whether files associated with the transmission job exist in BS assetts 1210. If not, the transmission job is placed on hold and the network operator is flagged regarding the no transmission.

If the files exist at BS assets 1210, BS 135 updates the benchmark for the transmission job at step 1228. At step 1230, BS 135 moves files to be transmitted to an outdirectory of BS 135. At step 1232, the *jtx files are moved to an outbox of BS 135. At step 1234, a satellite transmission operation is implemented via the multicast protocol engine for the transmission job.

At step 1236, BS 135 logs or records the transmission results in a transmission event log (e.g., whether transmission was successful, unsuccessful and so forth). At step 1238, BS 105 creates error tables identifying any errors in the transmission.

At step 1240, BS 135 moves files back to BS assetts 1210. At step 1242, BS 135 updates the Network Controller's hard drive table (HDT) according to the executed transmission job. At step 1244, BS 135 sends an error report to NC 105. At step 1246, the operator is notified of the transmission. At 1248, the network operator may request retransmission with an error occurred with the transmission. If a retransmission is requested, new XT/XQL files are created at step 1250. At step 1252, the network operator may select a transmission period, e.g., immediate or scheduled transmission. The transmission event is logged or recorded, e.g., stored in a log or an equivalent thereof at step 1254. NC 105 then sends this the XT/SQL information along with any associated video files to BS 135. The XT/SQL is placed on the transmission or job queue at step 1256.

Fig. 13 is a flow chart of a process 1300 by which requested jobs are queued in accordance with one embodiment.

At steps 1305 and 1310, NC 105 maintains transmission job files, e.g., .jtx files, and a Queue of pending transmissions. Jobs are started as soon as possible after their scheduled start time, depending on the duration of the previous job and with "immediate" jobs taking precedence. At steps 1315 and 1320, transmissionjobs are displayed to a network operator, via GUI 125 of OWC 120, the jobs being displayed in order of sequence. The information displayed to the network operator may include each job, its operation, its date of origin, its transmission period (e.g., immediate or scheduled) and its time of origin. The network operator may access this job queue to modify job priority, reschedule or delete jobs, check job status, or place jobs on hold. Fig. 14 is a flow chart of a process 1400 by which video or sequence of videos displayed at a remote site is changed or modified according to inventory information associated with that site. Process 1400 may be employed with any video network system, and is not limited to the satellite-based network control system shown and described herein. As one example, the process 1400 will be described with reference to Fig. 5.

At step 1410, DVS 160 of a site obtains inventory information associated with the site from an inventory management system 510. The inventory information may identify the products and/or services available at the site, a quantity of the products or services available at the site, a current price of the products and/or services at the site, a price range of the products and/or services at the site and so forth. The products may be identified by SKU number or other product and service identifiers. This inventory information may be maintained in inventory database 520.

Inventory management system 510 may provide the inventory information to DVS 160 at scheduled times (e.g., each day, each week, etc.) or upon a request from DVS 160 or NC 105.

At step 1420, DVS 160 compares the inventory levels (e.g., quantity) of the products and/or services with the product and/or service advertisements played at the remote site according to playlist(s).

At step 1430, DVS 160 modifies the playing of the advertisements on the playlist according to an inventory level of those products and/or services at the site. For example, these modifications may include: • Prohibiting play of a product or service advertisement if the availability of the product or service is below a predetermined amount;

• Replacing play of a product or service advertisement with an alternative advertisement of a different product or service if the availability of the product or service is below a predetermined amount; • Modifying a number of times a product or service advertisement on a playlist is played if the availability of the product or service is above or below a predetermined amount.

• Modifying the price in a product or service advertisement if the availability of the product or service is below or above a predetermined amount. For example, if the quantity of a product is high, the advertised price to be played may be reduced to promote sale. If the quantity of a product is low, the advertised price to be played may be increased to increase revenue. The modification of the advertised price may be subject to some predefined price range for the product or service;

• Adding play of a product or service advertisement if the availability of the product or service is above a predetermined amount. For example, an advertisement previously prohibited from play may be played when the associated product or service is more readily available at the site (e.g., a new shipment of the product). Also, the playing MISSING AT THE TIME OF PUBLICATION

If not, the client may be prompted for the password again or sent to the previous page on the web site. Otherwise, if valid, web server 1630 provides a selection of options to the client, such as those described above for Fig. 15. These selections are displayed to the client. At step 1640, web server 250 receives a selection from the client, via client device 270 over the Internet 260. At step 1650, web server 250 requests the selected information from NCS 100. For example, web server 250 may access the databases of NCS 100 storing or maintaining information associated with the selection for the client.

At step 1660, the selected information is received or retrieved by web server 250. At step 1670, web server 250 provides the selected information to the client for display or print out, as desired.

Fig. 17 is a flow chart of a process 1700 by which NCS 100 provides information related to a client's advertising to the client through a web site.

At step 1710, NCS 100 through NC 105 and BS 135 maintains information for each client related to their advertising at one or more remote sites.

At step 1720, NCS 100 receives a request from web server 250 for selected information related to advertisement of a client on NCS 100.

At step 1730, NCS 100 transmits the selected information to network server 250. Alternatively, instead of requesting the information from NCS 100, web server 250 may be configured with the ability to access directly or indirectly the databases or memory maintaining the relevant information to be retrieved.

Fig. 18 is a flow chart of a general process 1800 by which video is delivered to one or more network sites via satellite transmission. At step 1810, a network operator may select one or more files for transmission from a default directory, via OWC 120.

At step 1820, the network operator may select a target, such as a particular network, group of sites, geographical region (e.g., a state), site and so forth, for the transmission. At step 1830, NC 105 determines whether adequate HD space exists on servers of those targeted sites, and if so, at step 1840, BS 135 transmits the selected file(s) to the targeted sites through the use of multicast protocol engine/server 142. Fig. 19 is a flow chart of a general process 1900 by which a playlist is delivered to one or more network sites via satellite transmission.

At step 1910, a network operator may select one or more playlists for transmission from a default directory, via OWC 120. At step 1920, the network operator may select a target, such as a particular network, group of sites, geographical region (e.g., a state), site and so forth, for the transmission.

At step 1930, NC 105 verifies whether playlist content exists on servers of those targeted sites, and if so, at step 1940, BS 135 transmits the selected playlist(s) to the targeted sites through the use of multicast protocol engine/server 142.

Fig. 20 is a flow chart of a general process 2000 by which segments may be auto deleted.

At step 2010, a network operator may initiate an auto delete function, via OWC 120. At step 2020, the network operator may select a target, such as a particular network, group of sites, geographical region (e.g., a state), site and so forth, for the transmission.

At step 2030, BS 135 transmits data corresponding to a command to perform the auto delete function to the targeted sites, through the use of multicast protocol engine/server 142.

At step 2040, DVS 160 of a selected site, responsive to the received command, deletes video and/or other content (e.g., segment content) which is not on a current playlist.

Fig. 21 is a flow chart of a general process by which files may be deleted. At step 2110, a network operater may initiate a segment/ad delete function, via OWC 120.

At step 2120, the network operator may select a target, such as a particular network, group of sites, geographical region (e.g., a state), site and so forth, for the transmission. At step 2130, NC 105 then compiles a list of files on each remote server associated with the selected sites and provides it to the network operator. At step 2140, the network operator may then select files to delete from the compiled list.

At step 2150, NC 105 verifies that the files marked for deletion are no in a current playlist for those sites. If the files are not in the current playlist, NC 105 generates a delete command at step 2160 which is then transmitted to the selected sites by BS 135 through the use of multicast protocol engine/server 142 at step 2170.

At step 2180, DVS 160 of a selected site, responsive to the received command, deletes the files marked for deletion.

Fig. 22 is a flow chart of a general process by which content may be updated manually by a network operator.

At step 2210, a network operator may select a target, such as a particular network, group of sites, geographical region (e.g., a state), site and so forth.

At step 2220, the network operator may then select a command/function (e.g., reboot, refresh, report, HD audit, etc.) to be initiate. At step 2230, NC 105 generates data corresponding to the selected command, e.g., generates a command file such as update.inf.

At step 2240, BS 135 transmits data corresponding to the selected command to the selected sites through the use of multicast protocol engine/server 142.

At step 2250, DVS 160 of a selected site, responsive to the selected command, executes the command. This may be performed by a content update manager of the selected site.

Fig. 23 is a flow chart of general process by which a broadcast server, e.g., BS 135, performs satellite transmission.

At step 2310, BS 135 receives transmission information from NC 105. At step 2320, BS 135 generates a package.

At step 2330, BS 135 transmits this package of data to one or more sites through the use of multicast protocol engine 142.

At step 2340, BS 135 sends a reception report to NC 105.

At step 2350, NC 105 may resolve reception report and initiates retransmission with a network operator concurrence.

Regarding the databases shown herein, it is to be understood that the data and fields, as well as the number of databases, can be readily modified from the described embodiment and adapted to provide variations for operating the system and method described herein. The databases may be maintained locally or at a location accessible by the components of NCS 100.

While the above has been described in the context of advertisement video and advertising, NCS 100 may be implemented for other video subject matter.

Furthermore, video may include audio components which are played in conjunction with the video files at one or more locations.

It will be apparent to those skilled in the art that various modifications and variations can be made in the system and processes of the present invention without departing from the spirit or scope of the invention.

Claims

1. A method of controlling playing of video at one or more remote sites, comprising: transmitting videos to be stored at one or more remote sites via satellite transmission; and controlling the one or more remote sites to selectively play the stored videos.

2. The method according to claim 1, wherein videos are selectively transmitted to remote sites such that at least two remote sites store different combinations ofvideos.

3. The method according to claim 1, wherein one or more of the videos are advertisements.

4. The method according to claim 1, wherein the videos are in a MPEG format.

5. The method according to claim 1, wherein the controlling comprises transmitting to the remote site play control information to be stored at the one or more remote sites, the play control information identifying a manner in which videos are to be selectively played at the one or more remote sites.

6. The method according to claim 5, wherein the play control information identifies selected videos to be played at one or more remote site.

7. The method according to claim 5, wherein the play control information identifies an order in which selected videos are to be played at one or more remote sites.

8. The method according to claim 5, wherein the play control information identifies a time schedule in which selected videos are to be played at one or more remote sites.

9. The method according to claim 5, wherein the controlling further comprises updating data to be stored at one or more remote sites.

10. The method according to claim 9, wherein the updating updates the data to be stored at one or more remote sites according to a triggering event.

1 i . The method according to claim 9, wherein the updating updates the data to be stored at the one or more remote sites based on a benchmark identifying predefined data each of the one or more remote sites should maintain.

12. The method according to claim 11 , wherein the predefined data comprises one of play control information and videos.

13. The method according to claim 9, wherein the updating updates play control information to be stored at one or more remote sites.

14. The method according to claim 13, wherein the updating adds, deletes or modifies play control information to be stored at one or more remote sites.

15. The method according to claim 13, wherein the updating updates play control information so that at least two remote sites store different play control information.

16. The method according to claim 9, wherein the updating updates videos to be stored at one or more remote sites.

17. The method according to claim 16, wherein the updating adds, deletes or modifies. videos to be stored at one or more remote sites.

18. The method according to claim 17, wherein the updating deletes videos stored at one or more remote sites according to current play control information identifying current videos to be played at the one or more remote sites.

19. The method according to claim 16, wherein the updating updates videos so that at least two remote sites store different combination ofvideos.

20. The method according to claim 1, further comprising adding a new remote site to be controlled.

21. The method according to claim 20, wherein the adding a new remote site includes synchronizing data to be stored at the new remote site based on a benchmark identifying predefined data each of the one or more remote sites should maintain.

22. The method according to claim 21, wherein the predefined data comprises one of play control information and videos.

23. The method according to claim 1, further comprising eliminating one or more remote sites.

24. The method according to claim 1, further comprising suspending operations at one or more remote sites.

25. The method according to claim 1, further comprising editing site specific information of a remote site.

26. The method according to claim 1, further comprising tracking data stored at one or more remote sites.

27. The method according to claim 26, wherein the tracking tracks data stored at one or more remote sites by tracking data successfully transmitted to the one or more remote sites.

28. The method according to claim 26, wherein the tracking tracks data stored at one or more remote sites by receiving information from the one or more remote sites identifying actual data stored at the one or more remote sites.

29. The method according to claim 26, wherein the data comprises one of play control information and videos.

30. The method according to claim 29, further comprising maintaining an up- to-date image of data stored at one or more remote sites.

31. The method according to claim 30, further comprising identifying missing data that should be maintained at one or more remote sites.

32. The method according to claim 31 , further comprising generating a report identifying the missing data.

33. The method according to claim 31, further comprising updating the one or more sites with the missing data.

34. The method according to claim 1, wherein the controlling directly initiates one or more remote sites to commence play ofvideos stored at the one or more remote sites according to play control information stored at the one or more remote sites.

35. The method according to claim 1, wherein the controlling directly initiates one or more remote sites to stop play ofvideos at a current frame of a video being played.

36. The method according to claim 35, wherein the controlling directly initiates one or more remote sites to resume play ofvideos from the current frame of the video being played.

37. The method according to claim 1, wherein the controlling directly initiates one or more remote sites to restart play ofvideos.

38. The method according to claim 1, further comprising monitoring performance of video play at one or more remote sites.

39. The method according to claim 38, wherein the monitoring includes receiving from one or more remote sites information corresponding to the performance of video play at the one or more remote sites.

40. The method according to claim 38, wherein information of performance of video play at a remote site from the one or more remote sites includes one of total system operation time of the remote site, total playtime in a predetermined time period at the remote site, percentage compliance in a predetermined time period at a remote site, time of a prior report on performance of the remote site, time of a current report on performance of the remote site, number of system restarts in a predetermined time period at the remote site, total number of playing cycles in a predetermined time period at the remote site, and a number of user logons to the remote site.

41. The method according to claim 1, further comprising generating a compliance report indicating system reliability of one or more remote sites.

42. The method according to claim 1, further comprising generating an operation report providing performance data of one or more remote sites.

43. The method according to claim 1, further comprising generating a site report providing specific information on system operation and components of one or more sites.

44. The method according to claim 1, further comprising checking storage capacity of one or more remote sites prior to transfer of data thereto.

45. The method according to claim 44, further comprising notifying an operator if a storage capacity of any one of the one or more remote sites is below a predetermined storage capacity level.

46. The method according to claim 44, further comprising preventing data transfer to a remote site if the storage capacity of the remote site is below a predetermined storage capacity level.

47. The method according to claim 1, wherein a playing of at least one video at a remote site is modified according to inventory levels of one or more products associated with the video.

48. The method according to claim 1, further comprising providing to a client at a remote location information relating to play of the client's video.

49. The method according to claim 48, wherein the information is transmitted across the Internet to the client.

50. The method according to claim 48, wherein the information is requested and obtained from the one or more remote sites pursuant to a request by the client.

51. The method according to claim 48, wherein the information includes a number of times the client's video was played.

52. The method according to claim 48, wherein the information includes at least one of a number of remote sites playing the client's video and an identity of the remote sites playing the client's video.

53. The method according to claim 48, wherein the providing transmits the client's video to the client for display.

54. The method according to claim 1, wherein the one or more remote sites are classified into one or more groups

55. The method according to claim 54, wherein the same videos are transmitted to each remote site in a specific group.

56. The method according to claim 54, wherein the controlling comprises transmitting to each remote site in a specific group the same play control information for local storage, the play control information identifying a manner in which videos are to be selectively played at each of the remote sites in the specific group.

57. The method according to claim 54, wherein the controlling further comprises updating data to be stored at one or more remote sites on a group basis.

58. The method according to claim 57, wherein the updating updates the data to be stored at each remote site in the same group based on a group benchmark identifying predefined data each remote site in the group should maintain.

59. The method according to claim 58, wherein the predefined data comprises one of play control information and videos.

60. The method according to claim 59, wherein the updating adds, deletes or modifies play control information to be stored at one or more remote sites on a group basis.

61. The method according to claim 59, wherein the updating adds, deletes or modifies videos to be stored at one or more remote sites on a group basis.

62. The method according to claim 54, further comprising adding a new remote site to a specific group.

63. The method according to claim 62, wherein the adding a new remote site includes synchronizing data to be stored at the new remote site based on a group benchmark identifying predefined data each remote site in the specific group should maintain.

64. The method according to claim 63, wherein the predefined data comprises one of play control information and videos.

65. The method according to claim 54, further comprising removing a remote site from a specific group.

66. The method according to claim 54, further comprising reassigning a remote site from one group to another group.

67. The method according to claim 54, further comprising creating, modifying or deleting a group.

68. The method according to claim 54, further comprising tracking data of one or more remote sites on a group basis.

69. The method according to claim 54, further comprising monitoring performance of video play at one or more remote sites on a group basis.

70. The method according to claim 1, further comprising providing an operator with a graphical user interface to control playing of video at one or more remote sites.

71. The method according to claim 70, wherein the graphical user interface includes a map identifying a geographical location of one or more remote sites.

72. The method according to claim 71, wherein the map further identifies a level of compliance of one or more remote sites.

73. The method according to claim 71, wherein the operator accesses specific site information by selection of a desired remote site on the map.

74. The method according to claim 71, wherein the map is adapted to distinguish remote sites of a selected group.

75. The method according to claim 70, wherein the graphical user interface enables the operator to manually update selectively data to be stored at any one of the one or more remote sites.

76. The method according to claim 75, wherein the data includes at least one ofvideos and play control information.

77. The method according to claim 75, further comprising notifying the operator of update operations in violation of predetermined rules.

78. The method according to claim 1, wherein the controlling controls a mode in which videos are played at one or more remote sites, the modes including one of a content rotation mode, real-time content mode, daily scheduling mode and once through mode.

79. The method according to claim 1, wherein videos are played at a point of sale location at one or more remote sites.

80. A method of controlling a playing ofvideos at a remote site, comprising: storing data corresponding to videos and play control information identifying a manner in which videos are to be selectively played at the remote site, the data being received via satellite transmission; and playing the stored videos according to the play control information.

81. The method according to claim 80, wherein one or more of the videos are advertisements.

82. The method according to claim 80, wherein the videos are in a MPEG format.

83. The method according to claim 80, wherein the play control information identifies selected videos to be played at one or more remote site.

84. The method according to claim 80, wherein the play control information identifies an order in which selected videos are to be played at one or more remote sites.

85. The method according to claim 80, wherein the play control information identified a time schedule in which selected videos are to be played at one or more remote sites.

86. The method according to claim 80, further comprising updating the data at the remote site.

87. The method according to claim 86, wherein the updating adds, deletes or modifies play control information to be stored at one or more remote sites.

88. The method according to claim 86, wherein the updating updates videos at the remote site.

89. The method according to claim 88, wherein the updating deletes videos stored at the remote site according to current play control information identifying current videos to be played at the remote site.

90. The method according to claim 80, wherein play functions at the remote site are controlled from another location via satellite transmission.

91. The method according to claim 90, wherein the play functions include one of suspending operations at the remote site, playing videos at the remote site, stopping play ofvideos at the remote site, resuming play ofvideos at the remote site, and restarting play ofvideos at the remote site.

92. The method according to claim 80, further comprising reporting to another location information identifying actual data stored at the one or more remote sites, via satellite transmission.

93. The method according to claim 92, wherein the actual data includes one of play control information and videos.

94. The method according to claim 80, further comprising monitoring performance of video play at the remote site.

95. The method according to claim 94, further comprising transmitting information corresponding to the performance to another location, via satellite transmission.

96. The method according to claim 95, wherein information corresponding to the performance includes one of total system operation time of the remote site, total playtime in a predetermined time period at the remote site, percentage compliance in a predetermined time period at a remote site, time of a prior report on performance of the remote site, time of current report on performance of the remote site, number of system restarts in a predetermined time period at the remote site, total number of playing cycles in a predetermined time period at the remote site, and a number of user logons of the remote site.

97. The method according to claim 80, further comprising providing specific information on system operation and components of the site to another location, via satellite transmission.

98. The method according to claim 80, further comprising reporting storage capacity of the remote site to another location, via satellite transmission.

99. The method according to claim 80, further comprising modifying a playing of at least one video at the remote site according to inventory levels of one or more products associated with the video.

100. The method according to claim 80, wherein the videos and play information stored at the remote site is synchronized with another remote site in a video network.

101. A host system for controlling playing of video at one or more remote sites, comprising: a storage medium for storing videos; satellite communications interface for establishing satellite communications with one or more remote sites; and one or more processors for controlling transmission ofvideos to be stored at the one or more remote sites via satellite transmission and for controlling the one or more remote sites to selectively play the stored videos.

102. The host system according to claim 101, wherein videos are selectively transmitted to remote sites such that at least two remote sites store different combinations ofvideos.

103. The host system according to claim 101, wherein one or more of the videos are advertisements.

104. The host system according to claim 101, wherein the videos are in a MPEG format.

105. The host system according to claim 101, wherein the processor controls the playing ofvideos at the one or more remote sites by controlling transmission and storage of play control information at the one or more remote sites, the play control information identifying a manner in which videos are to be selectively played at the one or more remote sites.

106. The host system according to claim 105, wherein the play control information identifies selected videos to be played at one or more remote site.

107. The host system according to claim 105, wherein the play control information identifies an order in which selected videos are to be played at one or more remote sites.

108. The host system according to claim 105, wherein the play control information identifies a time schedule in which selected videos are to be played at one or more remote sites.

109. The host system according to claim 105, wherein the processor further controls updating of data to be stored at one or more remote sites.

110. The host system according to claim 109, wherein the processor controls update of the data to be stored at one or more remote sites according to a triggering event.

111. The host system according to claim 109, wherein the processor controls the update of the data to be stored at the one or more remote sites based on a benchmark identifying predefined data each of the one or more remote sites should maintain.

112. The host system according to claim 111, wherein the predefined data comprises one of play control information and videos.

113. The host system according to claim 109, wherein the processor controls the update of play control information to be stored at one or more remote sites.

114. The host system according to claim 113, wherein the processor controls the addition, deletion or modification play control information to be stored at one or more remote sites.

115. The host system according to claim 113, wherein the processor controls the update of play control information so that at least two remote sites store different play control information.

116. The host system according to claim 109, wherein the processor controls the update ofvideos to be stored at one or more remote sites.

117. The host system according to claim 116, wherein the processor controls the addition, deletion or modification ofvideos to be stored at one or more remote sites.

118. The host system according to claim 117, wherein the processor controls the deletion ofvideos stored at one or more remote sites according to current play control information identifying current videos to be played at the one or more remote sites.

119. The host system according to claim 116, wherein the processor controls the update ofvideos so that at least two remote sites store different combination of videos.

120. The host system according to claim 101, wherein the processor further controls addition of a new remote site to be controlled.

121. The host system according to claim 120, wherein the processor controls synchronization of data to be stored at the new remote site based on a benchmark identifying predefined data each of the one or more remote sites should maintain.

122. The host system according to claim 121, wherein the predefined data comprises one of play control information and videos.

123. The host system according to claim 101, wherein the processor controls elimination of one or more remote sites.

124. The host system according to claim 101, wherein the processor controls suspension of operations at one or more remote sites.

125. The host system according to claim 101, wherein the processor further controls editing of site specific information of a remote site.

126. The host system according to claim 101, wherein the processor further controls tracking of data stored at one or more remote sites.

127. The host system according to claim 126, wherein the processor controls tracking of data stored at one or more remote sites by tracking data successfully transmitted to the one or more remote sites.

128. The host system according to claim 126, wherein the processor controls tracking of data stored at one or more remote sites by receiving information from the one or more remote sites identifying actual data stored at the one or more remote sites.

129. The host system according to claim 126, wherein the data comprises one of play control information and videos.

130. The host system according to claim 129, the processor controls maintenance of an up-to-date image of data stored at one or more remote sites.

131. The host system according to claim 130, the processor further controls identification of missing data that should be maintained at one or more remote sites.

132. The host system according to claim 131, wherein the processor further controls generation of a report identifying the missing data.

133. The host system according to claim 131, wherein the processor further controls update of the one or more sites with the missing data.

134. The host system according to claim 101, wherein the processor controls direct initiation of one or more remote sites to commence play ofvideos stored at the one or more remote sites according to play control information stored at the one or more remote sites.

135. The host system according to claim 101, wherein the processor controls direct initiation of one or more remote sites to stop play ofvideos at a current frame of a video being played.

136. The host system according to claim 135, wherein the processor controls direct initiation of one or more remote sites to resume play ofvideos from the current frame of the video being played.

137. The host system according to claim 101, wherein the processor controls direct initiation of one or more remote sites to restart play ofvideos.

138. The host system according to claim 101, wherein the processor further controls a monitoring of performance of video play at one or more remote sites.

139. The host system according to claim 138, wherein the processor controls monitoring by receiving from one or more remote sites information corresponding to the performance of video play at the one or more remote sites.

140. The host system according to claim 138, wherein information of performance of video play at a remote site from the one or more remote sites includes one of total host system operation time of the remote site, total playtime in a predetermined time period at the remote site, percentage compliance in a predetermined time period at a remote site, time of a prior report on performance of the remote site, time of a current report on performance of the remote site, number of host system restarts in a predetermined time period at the remote site, total number of playing cycles in a predetermined time period at the remote site, and a number of user logons to the remote site.

141. The host system according to claim 101, wherein the processor further controls generation of a compliance report indicating host system reliability of one or more remote sites.

142. The host system according to claim 101, wherein the processor further controls generation of an operation report providing performance data of one or more remote sites.

143. The host system according to claim 101, wherein the processor further controls generation of a site report providing specific information on host system operation and components of one or more sites.

144. The host system according to claim 101, wherein the processor further controls checking of storage capacity of one or more remote sites prior to transfer of data thereto.

145. The host system according to claim 144, wherein the processor further controls notification of an operator if a storage capacity of any one of the one or more remote sites is below a predetermined storage capacity level.

146. The host system according to claim 144, wherein the processor further controls prevention of data transfer to a remote site if the storage capacity of the remote site is below a predetermined storage capacity level.

147. The host system according to claim 101, wherein a playing of at least one video at a remote site is modified according to inventory levels of one or more products associated with the video.

148. The host system according to claim 101, wherein the processor controls provision information relating to play of the client's video to a client at a remote location.

149. The host system according to claim 148, wherein the information is transmitted across the Internet to the client.

150. The host system according to claim 148, wherein the information is requested and obtained from the one or more remote sites pursuant to a request by the client.

151. The host system according to claim 148, wherein the information includes a number of times the client's video was played.

152. The host system according to claim 148, wherein the information includes at least one of a number of remote sites playing the client's video and an identity of the remote sites playing the client's video.

153. The host system according to claim 148, wherein the processor controls the transmission of the client's video to the client for display.

154. The host system according to claim 101, wherein the one or more remote sites are classified into one or more groups

155. The host system according to claim 154, wherein the same videos are transmitted to each remote site in a specific group.

156. The host system according to claim 154, wherein the processor controls transmission of the same play control information to each remote site in a specific group for local storage, the play control information identifying a manner in which videos are to be selectively played at each of the remote sites in the specific group.

157. The host system according to claim 154, wherein the processor controls update of data to be stored at one or more remote sites on a group basis.

158. The host system according to claim 157, wherein the processor controls update of the data to be stored at each remote site in the same group based on a group benchmark identifying predefined data each remote site in the group should maintain.

159. The host system according to claim 158, wherein the predefined data comprises one of play control information and videos.

160. The host system according to claim 159, wherein the processor controls addition, deletion or modification of play control information to be stored at one or more remote sites on a group basis.

161. The host system according to claim 159, wherein the processor controls addition, deletion or modification ofvideos to be stored at one or more remote sites on a group basis.

162. The host system according to claim 154, wherein the processor further controls addition of a new remote site to a specific group.

163. The host system according to claim 162, wherein the processor controls synchronization of data to be stored at the new remote site based on a group benchmark identifying predefined data each remote site in the specific group should maintain.

164. The host system according to claim 163, wherein the predefined data comprises one of play control information and videos.

165. The host system according to claim 154, wherein the processor further controls removal of a remote site from a specific group.

166. The host system according to claim 154, wherein the processor further controls reassignment of a remote site from one group to another group.

167. The host system according to claim 154, wherein the processor further controls creation, modification or deletion of a group.

168. The host system according to claim 154, wherein the processor further tracks data of one or more remote sites on a group basis.

169. The host system according to claim 154, wherein the processor further controls monitoring of performance of video play at one or more remote sites on a group basis.

170. The host system according to claim 101, wherein the processor further controls provision to an operator of a graphical user interface to control playing of video at one or more remote sites.

171. The host system according to claim 170, wherein the graphical user interface includes a map identifying a geographical location of one or more remote sites.

172. The host system according to claim 171, wherein the map further identifies a level of compliance of one or more remote sites.

173. The host system according to claim 171, wherein the operator accesses specific site information by selection of a desired remote site on the map.

174. The host system according to claim 171, wherein the map is adapted to distinguish remote sites of a selected group.

175. The host system according to claim 170, wherein the graphical user interface enables the operator to manually update selectively data to be stored at any one of the one or more remote sites.

176. The host system according to claim 175, wherein the data includes at least one ofvideos and play control information.

177. The host system according to claim 175, wherein the processor further controls notification to the operator of update operations in violation of predetermined rules.

178. The host system according to claim 101, wherein the processor controls a mode in which videos are played at one or more remote sites, the modes including one of a content rotation mode, real-time content mode, daily scheduling mode and once through mode.

179. The host system according to claim 101, wherein videos are played at a point of sale location at one or more remote sites.

180. A host system for controlling a playing ofvideos at a remote site, comprising: satellite communications interface for establishing satellite communications; storage device for storing data corresponding to videos and play control information identifying a manner in which videos are to be selectively played at the remote site, the data being received via satellite transmission; and processor to control playing of the stored videos according to the play control information.

181. The host system according to claim 180, wherein one or more of the videos are advertisements.

182. The host system according to claim 180, wherein the videos are in a MPEG format.

183. The host system according to claim 180, wherein the play control information identifies selected videos to be played at one or more remote site.

184. The host system according to claim 180, wherein the play control information identifies an order in which selected videos are to be played at one or more remote sites.

185. The host system according to claim 180, wherein the play control information identified a time schedule in which selected videos are to be played at one or more remote sites.

186. The host system according to claim 180, wherein the processor further updates the data at the remote site.

187. The host system according to claim 186, wherein the processor further controls addition, deletion or modification of play control information to be stored at one or more remote sites.

188. The host system according to claim 186, wherein the processor controls update ofvideos at the remote site.

189. The host system according to claim 188, wherein the processor controls deletion ofvideos stored at the remote site according to current play control information identifying current videos to be played at the remote site.

190. The host system according to claim 180, wherein play functions at the remote site are controlled from another location via satellite transmission.

191. The host system according to claim 190, wherein the play functions include one of suspending operations at the remote site, playing videos at the remote site, stopping play ofvideos at the remote site, resuming play ofvideos at the remote site, and restarting play ofvideos at the remote site.

192. The host system according to claim 180, wherein the processor further controls reporting to another location of information identifying actual data stored at the one or more remote sites, via satellite transmission.

193. The host system according to claim 192, wherein the actual data includes one of play control information and videos.

194. The host system according to claim 180, wherein the processor further controls monitoring of performance of video play at the remote site.

195. The host system according to claim 194, wherein the processor further controls transmission of information corresponding to the performance to another location, via satellite transmission.

196. The host system according to claim 195, wherein the information corresponding to the performance includes one of total host system operation time of the remote site, total playtime in a predetermined time period at the remote site, percentage compliance in a predetermined time period at a remote site, time of a prior report on performance of the remote site, time of current report on performance of the remote site, number of host system restarts in a predetermined time period at the remote site, total number of playing cycles in a predetermined time period at the remote site, and a number of user logons of the remote site.

197. The host system according to claim 180, wherein the processor further controls provision of specific information on host system operation and components of the site to another location, via satellite transmission.

198. The host system according to claim 180, wherein the processor further controls reporting of storage capacity of the remote site to another location, via satellite transmission.

199. The host system according to claim 180, wherein the processor further controls modification of a playing of at least one video at the remote site according to inventory levels of one or more products associated with the video.

200. The host system according to claim 180, wherein the videos and play information stored at the remote site is synchronized with another remote site in a video network.