When talking about throughput, all sorts of numbers get tossed around. However, it is crucial to clarify what data you are talking about when demonstrating and comparing values. What’s included, and what’s not?
DOCSIS 3.1 uses OFDM(A); this blog explains the basics of multiplexing, modulation and multiple access used with this new technology.
The CM-STATUS feature is of significant value in DOCSIS 3.x networks. However, originally it was designed in a way it was not 100% reliable. A specification addition in March 2014 changed this messaging facility and it was further fine-tuned in August 2014. This blog post provides an overview on why and how.
If you ask cable people for the differences between DOCSIS and EuroDOCSIS, the only thing they can typically think of is the difference in downstream channel width: 6 MHz for DOCSIS, 8 MHz for EuroDOCSIS. In reality there’s a lot more to it, as we will discuss in this blog post!
With climate changes and possible blackouts in Belgium, saving energy is becoming ever more important. So how can the Cable world contribute? The future standard, DOCSIS 3.1, promises advanced energy saving features using DOCSIS Light Sleep (DLS) mode. No need to wait though, the current specification (DOCSIS 3.0) already provides a mechanism to reduce cable modem power usage: Energy Management 1×1. Let’s take a closer look.
Rigorously testing a network device or distributed service requires complex, realistic network test environments. Linux Traffic Control (tc) with Network Emulation (netem) provides the building blocks to create an impairment node that simulates such networks. This first post of a three-part series, introduces both.
When cable operators offer telephony services over their networks, they do so based upon the PacketCable standards. At least, in the United States. In Europe there is EuroPacketCable. But what is the difference and what were the drivers for it? Find out in this blog post.
Will it turn out to be a marathon, or will 10 miles do this time? If understanding DOCSIS 3.0 was running 10 miles, how far will I need to run before I understand 3.1? Is the terrain rough and hilly or will it be a walk in the park?
Rigorously testing a network device or distributed service requires complex, realistic network test environments. Linux Traffic Control (tc) with Network Emulation (netem) provides the building blocks to create an impairment node that simulates such networks. This second post of a three-part series shows which impairments are available and how they can be configured.
While working with DOCSIS systems it is important to understand the upstream periodic ranging process. Ranging can be seen as the DOCSIS heartbeat between Cable Modem (CM) and Cable Modem Termination System (CMTS). As many people tend to struggle with the details of this process, the goal of this article is to visualize the periodic ranging process. Lets take a closer look at that ranging process – and let’s try to understand where things can go wrong during this DOCSIS heartbeat.