This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
Overlay or Converged Network for Telepresence?
First on the list is Quality of Service (QoS). Telepresence is interactive video conferencing, which is a real-time application. Because real-time traffic is very different than data traffic (see previous post), a well engineered QoS solution is vital. If the current network does not yet implement QoS, there is a lot of work to do to design a QoS strategy, get it implemented in all routers and switches and verify it is operating correctly. The impact of the telepresence application on the existing data applications must be assessed to ensure they will continue to work with adequate performance.
If deploying QoS on the enterprise network will be a big task, consider using the overlay model instead. Because only telepresence traffic is carried on the overlay connections, the implementation of QoS is much simpler. It is still needed, in order to separate signaling and management traffic from video and audio traffic, but it is more forgiving and much easier to get right.
Second on the list is bandwidth. Telepresence is a large consumer of bandwidth. And the bandwidth that it consumes is constant, so no statistical multiplexing is possible. I will spend more time on calculating the bandwidth needed for telepresence in my next post. But the tricky part about bandwidth is determining how much is needed for the existing data applications. Data applications require bursts of bandwidth when users require new data on their screens or when they access a database. If there is insufficient headroom in the network to support those bursts, application performance suffers.
An overlay network solves this problem by isolating the telepresence traffic on its own links. These links can then be utilized to very high levels because the telepresence bandwidth is both predictable and well behaved (not bursty.) It is easier to predict the performance result of an overlay and it eliminates the potential impact on data applications. In some cases, it may also be more cost effective to implement the overlay because of the high utilizations possible on these dedicated links.
The third decision point is the schedule. While both of the issues cited above can be resolved with careful engineering, this work takes time to design, implement and verify. If the telepresence decision came from the top, as it often does, the schedule may also have come from the top and may not provide sufficient time to get convergence done right. For these scenarios the overlay network can again provide relief because it is much simpler to deploy.
Don't despair, the overlay does not have to be the final solution. The overlay network can be merged back into the converged network once the right QoS is deployed and the bandwidth issues are well understood. Long term, the converged network will provide the best cost efficiency. But while the network evolves and the network team learns the details of supporting large volumes of real-time traffic, the overlay network can provide a simpler solution.