| Overview of Networking InfoChannel |
All InfoChannel digital signage components communicate via standard IP networking standards. InfoChannel can be easily integrated into your existing corporate network or a separate/dedicated InfoChannel network can be deployed.
There are three key components in an average InfoChannel network: |
| |
 |
| Role |
Allows design and maintenance of InfoChannel display content. |
| Operating System |
Windows XP |
| Communicates with |
Content Manager |
| Communicates via |
HTTP (TCP port 80 or 8080) |
|
| |
 |
| Role |
Provides a central repository for all display content, manages scheduling of content, monitors Player health and provides web-based content management system to allow collaborative design of content. |
| Operating System |
Windows Server 2003 (recommended) or Windows XP |
| Communicates with |
Users contributing display content
Administrators
Back-end data sources |
| Communicates Primarily via |
HTTP (TCP port 80 or 8080) |
| Communicates with Backend Data Sources (optionally) via |
XML, RSS, HTML, FTP, CIFS, others |
|
| |
 |
| Role |
Directly attached to one or displays. Responsible for playback of display content. |
| Operating System |
Windows XP |
| Communicates with |
Content Manager |
| Communicates via |
HTTP (TCP port 80 or 8080) |
|
| |
| Optimized Network Bandwidth Requirements |
InfoChannel minimizes network load by locally caching content at each player. New content is sent once from the Designer to Content Manager. In turn, Content Manager sends this new content once to each player scheduled to play the content. If subsequent changes are made to this content, only the modified elements are resent to the players—not the entire content.
e.g. If a template’s message of the day is only changed, only the changed text will be retransmitted.
|
| |
| How InfoChannel Can Be Deployed in Your Environment |
| There are several options when deploying InfoChannel in your environment. InfoChannel can be integrated into your existing network, deployed as a stand-alone network or a hybrid of both: |
| |
| Configuration |
Pros |
Cons |
Integrated Network
All digital signage components are directly connected to the corporate network. No VLANs or firewalling is configured. |
Supports large-scale deployment of digital signage network.
Allows a high-degree of staff collaboration and workflow of content changes.
Allows a high-degree of integration with backend corporate or external data feeds.
Allows complete monitoring and management of the solution.
|
Requires IT coordination for planning and implementation.
Requires IT assistance IP addressing and security compliance. |
DMZ Network
A dedicated VLAN is provisioned off of the corporate network to connect all digital signage components. User access to the digital signage network is optionally firewalled. |
Supports large-scale deployment of digital signage network.
High-degree of segregation between digital signage and corporate traffic.
Allows a high-degree of staff collaboration and workflow of content changes.
Allows a high-degree of integration with backend corporate or external data feeds.
Allows complete monitoring and management of the solution.
|
Requires IT coordination for planning and implementation.
Requires IT assistance for provisioning the VLAN, IP addressing and security compliance. |
Private Network
A dedicated/parallel network is deployed to connect all digital signage components. |
Supports large-scale deployment of digital signage network.
Completely segregates digital signage and corporate network traffic.
No integration concerns for IT.
|
All content changes and management must be made from the digital signage network—cannot be accessed from corporate network.
Limited backend data integration. |
Stand-Alone
Designer workstation is directly attached to one or more displays presenting identical content. |
Low cost
Simple configuration
No integration concerns for IT.
Completely segregates digital signage and corporate network traffic. |
Supports only a small number of displays.
All content changes must be made at the same workstation.
Playback is disrupted during Designer content updates.
Limited backend data integration.
|
|
