Home
Overview SCALA Overview  
Scala InfoChannel 5 (New)
Scala InfoChannel 3
 
IC3 Overview Scala InfoChannel 3 Overview  
IC3 Designer IC3 Designer
IC3 Network Manager IC3 Network Manager
IC3 Player IC3 Player
IC3 Broadcast Server IC3 Broadcast Server
IC3 Reporter IC3 Reporter
Device Control Extensions
Playback Hardware/Screens
Scala Service Plan
 
 
Scala Customer Profiles
 
 
The Scala Difference
Why Use Satellite?
 
 
Downloads - PDF Data Sheets
Software Product brochures
IC3 Designer - Product Brochure PDFIC3 Designer
IC3 Network Manager - Product Brochure PDFIC3 Network Manager
IC3 Player - Product Brochure PDFIC3 Player
IC3 Broadcast Server - Product Brochure PDFIC3 Broadcast Server
IC3 Reporter - Product Brochure PDFIC3 Reporter
Overview Documents
Scala InfoChannel "Connect" Brochure (PDF)IC3 Brochure (NEW)
IC3 Benefits - FactSheet PDFIC3 Benefits
IC3 Workflow - FactSheet PDFIC3 Workflow
Scala Solutions Brochures
Scala Solutions - PDF BrochureSolutions Overview
Scala Solutions : Cable - PDF BrochureCable
Scala Solutions : Corporate - PDF BrochureCorporate
Scala Solutions : Education - PDF BrochureEducation
Scala Solutions : Government - PDF BrochureGovernment
Scala Solutions : Signage - PDF BrochureSignage
White Papers
Whitepaper PDF: How InfoChannel Works—AbridgedHow InfoChannel Works
Miscellaneous
Scala PDF Guide: Product Generation OverviewProduct Generations
Scala PDF Guide: InfoChannel 3—New Features since IC200Features since IC200
 
 
External Links :
Scala web site
Cross Links :
diVA product page
Scala IC3 R7.4 announced
Scala IC3 R7.5 announced
 
Scala - Overview
PAGE TOP

Scala InfoChannel 3

Why Use Satellite?
IP Multicast Technology

Scala InfoChannel Overview

UPDATE HUNDREDS, OR THOUSANDS OF SITES IN ONE TRANSMISSION

In smaller networks, the way that Scala InfoChannel communicates between the Network Manager and Player is with standard Internet protocols such as FTP or with UNC paths. In larger networks, and especially with larger content such as MPEG2 files, standard FTP transmissions can be very inefficient - having each player pull its content individually from a central FTP server. Imagine 1,000 players each trying to pull 1 gigabyte of content from a single Network Manager server, more or less at the same time. That's a lot of data! In fact, your IT department might think that they were under a "denial of service attack" from this sort of job that amounts 1 terabyte of traffic.

Now imagine if you could communicate with those 1,000 Players by sending content JUST ONCE. That's the beauty of IP Multicast. And that's the beauty of Scala's software family; the same software architecture scales from 10 players to 10,000 players seamlessly. InfoChannel even supports a shared multicast delivery offering from Hughes Network Systems, which lets you "pay by the megabyte". This can be a very economical alternative to purchasing dedicated bandwidth for smaller multicast networks.

TECHNOLOGY OVERVIEW

Here's the bad news - the public Internet does not support IP Multicast. The good news is that most satellite providers DO support multicast, and in fact, prefer multicast transmissions. This paper will explain some of the terminology and hopefully de-mystify the technology for you.

As your digital signage network expands into hundreds or thousands of remote sites, it may become time to consider one of the four multicast technologies currently available. These are:

  • Dedicated Satellite Multicast Bandwidth
  • Shared Satellite Multicast Delivery
  • Datacast (over-the-air terrestrial)
  • Terrestrial IP Multicast

Scala supports each of these network technologies, along with the bevy of wired and wireless unicast technologies such as 802.11b, 802.11g, and standard hardwired CAT5 connections. Installing a 256Kbps Frame Relay connection or even a relatively cheap DSL circuit to each player location, assuming you can even get DSL service in all locations, can really add up when it comes to your monthly commutations bill. By using IP multicast technology on your 1,000-unit network, your price per site per month can be a fraction of a cheap DSL circuit and it has a ubiquitous footprint.

When it comes to large narrowcasting deployments, Scala's significant competitive advantage is that the InfoChannel 3 suite and its predecessor have both supported IP multicast for several years and new customers will not be the guinea pig by any stretch of the imagination. With over 15,000 units in the field and with multiple networks having over 1,000 players each, InfoChannel can administer any number of sites - whether it's 10 or 10,000 players.

There are four main ways to communicate via multicast. The most common is a dedicated satellite multicast subscription, which is supported by all major satellite bandwidth providers including Hughes Network Systems, Spacenet (Gilat), and GlobeComm.

Scala is a founding member of the Hughes Broadband Alliance, and as such, our software has specific support for Hughes' DIRECWAY® multicast delivery system. This program offers the smaller network to "pay by the megabyte". So if you have 200MB to send out once a week, dedicated bandwidth is probably a waste, but with Hughes, your costs can be significantly lower for the smaller network with infrequent, but larger updates. Most of our larger customers use this method today.

A third option is a relatively new offering provided by PBS National Datacast in the United States. This program uses spare bandwidth in digital television (HDTV) channels to transmit data via standard over the air broadcast antennas. For networks that need high bandwidth one way communications in major metropolitan areas, this can be a very interesting alternative. An HDTV channel has 19.4 Mbps throughput over the air. With today's variable bit rate encoders for video, there is often significant spare bandwidth (e.g. 6 Mbps) for other applications. This has been successfully tested with Scala InfoChannel at WHYY in Philadelphia.

InfoChannel Broadcast Server 3

A fourth alternative is terrestrial IP multicast. This is offered by many major ISPs and telecom companies such as AT&T, MCI/Worldcom, Sprint, and others. This is not very common, but if all of your locations are within the same "cloud", it is possible for the network operator to enable multicast data over your network.

 

DEDICATED SATELLITE MULTICAST

The standard InfoChannel 3 workflow diagram most easily explains satellite multicast, where Network Manager Enterprise Edition sends its jobs to Broadcast Server for direct transmission to a satellite uplink. This assumes that you have purchased dedicated bandwidth from a specific satellite service provider on a 24/7 basis. This is usually in the 1 to 3Mbps range. You will need to either co-locate your broadcast server at your satellite provider's location, or you must have a backhaul connection into their NOC for this to work. Dedicated bandwidth means customers will pay for the same bandwidth regardless of how much that they use and might cost upwards of US $20,000 per month. This is rather expensive if you have only 20 sites (US$1,000 per month per site), but very inexpensive if you have 2,000 sites (only US$10 per month per site).

Organizations that already have a satellite network in place may be able to share bandwidth with other applications during "slow times", or you can also add additional bandwidth fairly easily. It is important to "do the math". If you try and send out more data than you have paid for, "bits will fall on the floor" since this is STREAMING data to all sites in real time. InfoChannel is a store and forward application, so only after it has buffered the entire content will it start to act on those instructions. If you've only paid for 2Mbps and you're using it all for distance learning video, no other data (including InfoChannel) will ever make it through. It is easy to limit the speed of the multicast in the configuration menu of the Broadcast Server. Some existing InfoChannel installations have gotten by with as little as 128 Kbps.

Customers have three choices in where to host the Broadcast Server. First, and most popular, is by collocation. Similar to web hosting, companies often purchase or rent an entire FTP server on-site at the satellite provider that controls their transmissions. Secondly, the Broadcast Server could be located on YOUR premises, if you are able to provide a backhaul circuit to the NOC. This can become quite expensive depending on how close you live to your NOC. And for the really large customers, Hughes will be happy to sell you your own uplink facility. This is a significant capital investment, and requires a VERY LARGE DISH.

Remote sites require their own small dishes and satellite modems, of which consumer models currently start at less than US$500 each. These are one-time fees to purchase the units outright. To take advantage of Network Manager's network monitoring and verification abilities, customers will need to add a backchannel, which can now be provided on the same small satellite dish. An Internet backchannel could run in the US$50 to $100 per site per month range

TERRESTIAL IP MULTICAST

Standard Ethernet cards produced in the past decade have been capable of multicast transmissions. The reason for the slow adoption rate is because to have a private multicast network, all the segments through the entire data path (via both Intranet and Internet) must be multicast-compatible. And as most of us will attest, the public Internet is not exactly the best network for reliable, real-time, streaming.

For large organizations, it can be just as difficult to enable multicast internally with IT staff as well as externally through an Internet Service Provider. The CEO will still want to get email after all! Also, ISPs must configure all of their routers to allow multicast traffic, so expect a lot of setup time on both ends.

The advantage of terrestrial IP multicast is that it requires no additional hardware and given the aforementioned setup, requires little, if any, extra infrastructure