Such dissatisfaction causes trouble tickets, truck rolls and high customer attrition. The problem is further compounded when technicians use similar off-the-shelf hardware and software to validate network performance.
Service turn up and testing are important first steps to avoid unnecessary operational expenses after the service is delivered. Also important is quality of service (QoS) testing, accomplished via traditional Layer 2 and Layer 3 test methodologies like RFC2544 and ITU-T Y.1564. But today, thanks to the growing importance of QoE, a growing number of service providers are combining traditional QoS testing and newer QoE test methodologies like RFC6349 and internet speed testing methods.
1G and 10G: Proving both is a challenge
The future of the 10G platform is now becoming reality as broadband providers who have already proven consistent gigabit performance are reaching to meet consumer demand for faster speeds. At 10 Gbps, service providers lay the foundation upon which consumers will interact with the digital world every day.
The deployment of 10G networks also brings new challenges. These networks overwhelm available off-the-shelf hardware even more than 1G does, which means the hardware is unable to achieve the full 10G line rate. This factor leaves the service provider unable to verify 10G network performance.
And the problem is even worse with the do-it-yourself approach. A problem is bound to occur when the consumer tests their service with an older laptop that has a slower CPU and is unable to achieve 1 Gbps over its copper RJ-45 10/100/1000Base-T interface. Aggravated consumers that are unable to validate their 1G networks can become a nightmare for service providers when the service goes beyond 1 Gbps, as there is really no consumer laptop available today with a 10-Gbps interface. For example, the consumer can pay for a 2-Gbps DOCSIS 3.1 service but is unable to test the network speed with their top-of-the-line video gaming laptop.
Once they realize that their laptop is only measuring 200-300 Mbps out of a 2-Gbps service, they can become frustrated and may file an unwarranted complaint with their service provider. This complaint in turn will generate a ticket that could turn into a truck roll, an unnecessary operational expense for the service provider.
To eliminate deployment failure and remove any doubt that the broadband service meets the SLA, service providers should invest in dedicated test equipment that exceeds any consumer device performance to carry out stateful TCP testing. Consistent and relevant testing methodologies, as well as dedicated and specialized hardware, are needed for testing QoE and meeting SLAs with consumers.
For this reason, leading service providers are complementing traditional RFC2544 and ITU-T Y.1564 testing with QoE testing. These service providers use the RFC6349 methodology and simple upload/download testing to ftp/http servers to validate network performance. This stateful TCP/IP (Layer 4) testing builds consumer confidence in the provider.
Both internet speed testing and the RFC6349 testing strategies will require the deployment of dedicated TCP servers within the service provider footprint or dedicated rackmount test equipment. This dedicated equipment should be able to operate as both a TCP server and TCP client when testing against field equipment, in addition to carrying out other traditional Ethernet test methodologies like ITU-T Y.1564 and RFC2544 (see Figure 1).
A controlled test between a client connected directly to a TCP and HTTP server proved that when a 1-msec delay was introduced (for example, due to a network impairment), throughput dropped by less than 10% when using dedicated hardware. However, throughput dropped by more than 50% when using off-the-shelf laptops. A 10-msec delay between a client and a server remain as expected (see Figure 2).
As Figure 3 shows, even if dedicated hardware is used on the client side but not on the server side (white line), it still does not match the performance of dedicated (blue line) hardware for both client and server or calculated ideal (green dotted line).
Ricardo Torres is director of product marketing and a founding member of VeEX Inc. He leads the product marketing, strategic positioning and product management of VeEX’s Ethernet portfolio. He is also responsible for the company’s global business initiatives encompassing Carrier Ethernet/IP networks, mobile backhaul, 40GbE/100GbE and Ethernet synchronization technologies. Prior to joining VeEX, Ricardo worked at Sunrise Telecom, where he was responsible for managing the Ethernet/IP portfolio. He has also worked at Agilent Technologies in the area of high-speed fiber-optic networking.