Full Story

Interview with Nir Daube - VP of Product Management

Q. Telco Systems recently added HQoS support on the T-Marc 300 product line. Why is HQoS needed on a demarcation platform? A. Carrier Ethernet networks today are migrating from being uni-service network (i.e., best effort) to being a multi-service network (prioritized). In order to run a multi-service network the carrier needs a mechanism that allows him to enforce QoS policies per user per service.

Q. How can HQoS help a cellular wireless operator support more services?

A. Cell towers are sometimes located in good strategic places like industrial parks or city centers, where the operator might want to start offering business services alongside with its cell tower traffic. One of the main challenges in such an installation is how to make sure that the sensitive cell traffic will not be affected by the new business services running on the same infrastructure. In this example, each type of traffic has its own subsets of internal priority flows and bandwidth constraints. It is exactly in these types of applications where HQoS can support such a mixture of services, allowing each of them to get the required resources and quality.

Q. What types of transport technologies can HQoS run on?

A. Telco Systems today supports HQoS on QinQ, 802.1ad & VPLS transport technologies.

Q. Sounds complex, can this be practically used?

A. We visualize our devices as service machines. This means that the device transports services across the network. Using the service approach the user only needs to engineer a few general HQoS service package policies which can then be re-used on all other devices. Whenever a new service is added the technician only needs to apply the HQoS policy name in the service and the policy is implemented. This saves time and eliminates mistakes that might occur for each new service that is being added.