Blazeband in Fazzt 9.0

State-of-the-Art for Accelerated UDP Delivery since 2007

  • Deliver very large files, point to point, over wire/wireless networks with blazing speeds anywhere worldwide
  • Now available as a no-cost add-on with purchase of Fazzt content delivery products
  • Available as no-cost add-on for customers with a legacy Fazzt installation and a Maintenance contract

KenCast has been constantly enhancing its Blazeband technology since 2007. Blazeband provides a powerful mechanism for accelerating content delivery over IP networks. Blazeband works on point-to-point links to maximize the bandwidth utilization while maintaining the reliability which is the cornerstone of KenCast’s solutions. Blazeband allows file transfers to be performed several times faster than traditional methods such as FTP or HTTP. Blazeband can accelerate content delivery on the Internet, wireless networks, and corporate WANs.

Traditional TCP protocols, such as FTP and HTTP, require that every byte sent be acknowledged. Any data which is lost or not acknowledged must be resent. TCP uses data loss for bandwidth and congestion control. On networks with high latency or excessive packet loss, TCP protocols can suffer from poor efficiency. Even on networks with good performance characteristics, TCP protocols rarely achieve optimum bandwidth utilization.

Blazeband provides an alternative which overcomes these limitations of TCP. Blazeband utilizes UDP for bulk packet delivery. UDP (User Datagram Protocol) is the standard mechanism for delivering packet-based data over IP networks. UDP does not provide mechanisms for bandwidth control or reliability, but UDP packets can be sent very quickly.

Blazeband protocols provide bandwidth and congestion control through UDP messages, using intelligent algorithms which distinguish congestion losses from other types of packet losses. These algorithms prevent Blazeband bandwidth utilization from dropping off in the presence of occasional packet loss.

Blazeband achieves speed and reliability through the use of KenCast's (patented, additional patents pending) Fazzt Forward Error Correction (Fazzt FEC) technology, validation algorithm, accelerated UDP algorithms, and Missed Packet Collector algorithms. This includes the following tools:

KenCast Accelerated UDP toolbox:

  • Stream multiplexing
  • Packet-reordering
  • Forward-Error Correction (FEC)
  • Congestion control
  • Multi-Threading
  • Compression
  • Audit trail
  • Encryption
  • Plus automated optimization of window sizes, framing, ACKs, and all the fun bits of a protocol.

NEW -- Fazzt 9 also includes two transmission mechanisms which utilize Blazeband technology: one primarily for content distribution and one primarily for content contribution.

  • The Blazeband Pull Channel is primarily used for sending content from a Fazzt Enterprise Server to one or more Fazzt Clients.
  • The Blazeband Push Channel is primarily used for content contribution.

It is also possible to use the Blazeband Pull Channel for content contribution or the Blazeband Push channel for content distribution. The configurations discussed below are typically desirable because they simplify the firewall and router configuration at the largest number of locations.

The Blazeband Pull Channel is used with Fazzt's Unicast Delivery Framework, which handles automatic channel creation, scheduling, and bandwidth management at the Server. The Blazeband Pull Channel can be used as the primary (or only) content delivery mechanism, or it can be used as a backup mechanism for a multicast network (such as a satellite network).

The Blazeband Pull Channel uses both TCP and UDP protocols. The TCP connection is used for authentication and negotiation, while UDP is used to send data packets, using Blazeband technology for acceleration.

The Fazzt Client initiates the connection when using the Blazeband Pull Channel. This allows the Client machine to be behind a firewall or NAT router. In most cases, no special firewall or router configuration is necessary on the Client side of the connection.

The Blazeband Push Channel is primarily used for content contribution, for example, from the Fazzt Contribution Server to a Fazzt Enterprise Server. The Blazeband Push Channel also utilizes a TCP connection for negotiation and authentication, and UDP for bulk data delivery using Blazeband technology. In this case, the transmitting side initiates the connection, so the transmitting side can be behind a firewall or NAT router. Port configuration for the receiving side (typically the Enterprise Server) is the same as for the Blazeband Pull Channel discussed above.