The cable industry took another step toward its "10G" future this week with the release of a new set of specifications giving operators and their suppliers a common framework for disaggregated networks that will deliver multi-gigabit speeds and, eventually, lead them to fully virtualized access networks.

That new set of CableLabs specifications – called the Flexible MAC Architecture (FMA) – provides suppliers with the technical means to develop interoperable products. The specs will likewise provide cable operators with the ability to build and develop these next-gen access networks without worrying about getting locked into vendor-specific, proprietary technologies.

FMA should also put to rest a years-long technical and engineering debate over what path operators should take as they pivot from traditional, integrated Converged Cable Access Platforms (CCAPs) to more disaggregated and distributed forms of the access network. Until recently, that debate has centered on whether to go with remote PHY (whereby the PHY of the CCAP is deployed in a fiber node) or remote MACPHY (where both the PHY and the MAC processing are pushed out toward the edge).

"The biggest takeaway for FMA is flexibility," said Jon Schnoor, lead architect, wired technologies at CableLabs. "It allows the operator to choose when and how they implement and deploy CCAP functionality. It gives them choices of where to do it in the access network where it makes the most sense for them."

FMA also represents a complete disaggregation of the industry's broadly deployed integrated CCAP device. "We literally blew it up," said Schnoor, who also authored a blog post about the new specs.

Multi-phase approach

Although FMA will ultimately enable cable operators to deploy the MAC anywhere, phase I of the FMA project – as defined by this initial batch of specs – is focused on remote MACPHY, where the MAC and PHY are miniaturized and packed into a fiber node.

Further out, phase II will focus on specs for a remote MAC core, and phase III will set upon a full virtualization of the access network. The time frames for phase II and III are still to be decided, Schnoor said.

FMA building blocks

Back to FMA phase I. For that, CableLabs, Schnoor explains, has developed three key pieces that will work together: the MAC Manager, the Remote MACPHY Device (RMD) and an optional element called the PacketCable Aggregator.

The MAC Manager relates to how operators will control the remote MAC, which used to reside in the central CCAP core but will instead be moved to Remote MACPHY Devices that are deployed further out on the network. To facilitate that, CableLabs has crafted a spec called the MAC Manager Interface, which takes data from the operator's OSS and BSS and translates it into Yang data models that, in turn, are shot down to the Remote MACPHY device.

The MAC Manager can be virtualized. "It's just software," Schnoor said.

The optional PacketCable Aggregator (supported by its own specified and interoperable interface) will help operators manage IP voice services that still rely on the industry's PacketCable backend specs. Managing PacketCable services properly will become an issue as operators disaggregate their networks and deploy about 10x the number of nodes they have out there today.

Boiled down, the PacketCable Aggregator will enable those PacketCable telephony systems to perform the necessary translations and make the overall system take on the appearance of a traditional CCAP deployment underpinned by much fewer nodes, as well as to ensure that the right node connects to the backend of the network.

How the Distributed CCAP Architecture (DCA) fits in

FMA, Schnoor explains, is also a "foundational piece" for the work being done around the Distributed CCAP Architecture (DCA) program.

And what, pray tell, is that? DCA, which initially focused on remote PHY, is all about the complete disaggregation of the DOCSIS network and the individual DOCSIS functi...

The cable industry took another step toward its "10G" future this week with the release of a new set of specifications giving operators and their suppliers a common framework for disaggregated networks that will deliver multi-gigabit speeds and, eventually, lead them to fully virtualized access networks.

That new set of CableLabs specifications – called the Flexible MAC Architecture (FMA) – provides suppliers with the technical means to develop interoperable products. The specs will likewise provide cable operators with the ability to build and develop these next-gen access networks without worrying about getting locked into vendor-specific, proprietary technologies.

FMA should also put to rest a years-long technical and engineering debate over what path operators should take as they pivot from traditional, integrated Converged Cable Access Platforms (CCAPs) to more disaggregated and distributed forms of the access network. Until recently, that debate has centered on whether to go with remote PHY (whereby the PHY of the CCAP is deployed in a fiber node) or remote MACPHY (where both the PHY and the MAC processing are pushed out toward the edge).

"The biggest takeaway for FMA is flexibility," said Jon Schnoor, lead architect, wired technologies at CableLabs. "It allows the operator to choose when and how they implement and deploy CCAP functionality. It gives them choices of where to do it in the access network where it makes the most sense for them."

FMA also represents a complete disaggregation of the industry's broadly deployed integrated CCAP device. "We literally blew it up," said Schnoor, who also authored a blog post about the new specs.

Multi-phase approach

Although FMA will ultimately enable cable operators to deploy the MAC anywhere, phase I of the FMA project – as defined by this initial batch of specs – is focused on remote MACPHY, where the MAC and PHY are miniaturized and packed into a fiber node.

Further out, phase II will focus on specs for a remote MAC core, and phase III will set upon a full virtualization of the access network. The time frames for phase II and III are still to be decided, Schnoor said.

FMA building blocks

Back to FMA phase I. For that, CableLabs, Schnoor explains, has developed three key pieces that will work together: the MAC Manager, the Remote MACPHY Device (RMD) and an optional element called the PacketCable Aggregator.

The MAC Manager relates to how operators will control the remote MAC, which used to reside in the central CCAP core but will instead be moved to Remote MACPHY Devices that are deployed further out on the network. To facilitate that, CableLabs has crafted a spec called the MAC Manager Interface, which takes data from the operator's OSS and BSS and translates it into Yang data models that, in turn, are shot down to the Remote MACPHY device.

The MAC Manager can be virtualized. "It's just software," Schnoor said.

The optional PacketCable Aggregator (supported by its own specified and interoperable interface) will help operators manage IP voice services that still rely on the industry's PacketCable backend specs. Managing PacketCable services properly will become an issue as operators disaggregate their networks and deploy about 10x the number of nodes they have out there today.

Boiled down, the PacketCable Aggregator will enable those PacketCable telephony systems to perform the necessary translations and make the overall system take on the appearance of a traditional CCAP deployment underpinned by much fewer nodes, as well as to ensure that the right node connects to the backend of the network.

How the Distributed CCAP Architecture (DCA) fits in

FMA, Schnoor explains, is also a "foundational piece" for the work being done around the Distributed CCAP Architecture (DCA) program.

And what, pray tell, is that? DCA, which initially focused on remote PHY, is all about the complete disaggregation of the DOCSIS network and the individual DOCSIS functi...