Fiber & Cable Systems

DAA (Distributed Access Architecture)

Q: What is the difference between Remote PHY and Remote MACPHY in a DAA deployment?

Remote PHY (R-PHY) places only the DOCSIS and video physical layer in the node; the upstream and downstream QAM and OFDM/OFDMA modulators move to a Remote PHY Device (RPD), while the MAC stays centralized in a CCAP core in the headend, connected over a pseudowire defined by the DEPI and UEPI protocols. Remote MACPHY (R-MACPHY) pushes both the MAC and PHY into the node, so the Remote MACPHY Device (RMD) terminates DOCSIS scheduling locally and connects upstream only via standard IP/Ethernet. R-PHY keeps scheduling centralized for easier capacity pooling and simpler node hardware, while R-MACPHY reduces the timing and synchronization burden on the network because each node is largely autonomous. Most large MSOs have standardized on R-PHY, while R-MACPHY appears in smaller or fiber-deep builds.

Q: How much does DAA improve the downstream SNR compared to analog optics?

Traditional analog AM optical links accumulate noise and distortion (CNR typically 48 to 51 dB, with composite second-order and composite triple-beat products) across the optical span before the signal is even modulated onto the coax. By digitizing the signal in the node, DAA removes the analog optical link from the impairment budget entirely, so the modulation error ratio (MER) seen at the cable modem is set almost entirely by the short coax segment. Operators commonly see 3 to 6 dB of MER improvement, often raising downstream MER above 40 to 43 dB, which is enough to support 4096-QAM DOCSIS 3.1 OFDM profiles that analog plant could not reliably carry at 256-QAM.

Q: What Ethernet transport bandwidth does a Remote PHY node require?

A Remote PHY node carries fully modulated DOCSIS and IP video as digital Ethernet rather than analog RF over fiber. A node serving a 1.2 GHz downstream spectrum plus a 204 MHz upstream typically needs a 10 Gigabit Ethernet (10GbE) link, and node-plus-segmentation builds frequently provision two 10GbE or a 25GbE uplink. The node also needs precise timing: IEEE 1588v2 (PTP) synchronization to roughly +/- 1.5 microseconds is required so the RPD and the CCAP core agree on DOCSIS upstream scheduling slots. This is why DAA deployments add a PTP grandmaster clock to the headend or hub.

/dee-ay-ay/ (Distributed Access Architecture)

A cable access network design that relocates DOCSIS signal processing from the headend out into fiber-fed nodes, converting the long optical span from an analog link into a digital Ethernet connection. In a Remote PHY build the node hosts the QAM and OFDM modulators while the MAC stays in a centralized core; in a Remote MACPHY build both layers move to the node. Because the analog optical link is removed from the impairment budget, DAA recovers 3 to 6 dB of modulation error ratio at the cable modem, enough to run 4096-QAM DOCSIS 3.1 profiles across the existing HFC plant. The architecture is the foundation of fiber-deep and 1.8 GHz DOCSIS 4.0 upgrades.

Category: Fiber & Cable Systems

Node uplink: 10 to 25 GbE

MER gain: 3 to 6 dB

How DAA Reshapes the Cable Access Network

For decades, hybrid fiber-coax networks carried fully modulated RF as an analog optical signal from the headend to the optical node, where it was converted back to RF and pushed onto the coaxial plant. That analog amplitude-modulated link was the dominant noise and distortion source in the chain, contributing composite second-order and composite triple-beat products and limiting carrier-to-noise ratio to roughly 48 to 51 dB before the signal ever reached a subscriber. Distributed Access Architecture breaks this model by moving the digital-to-analog conversion all the way to the node. Instead of carrying analog RF over glass, the fiber now carries Ethernet frames, and the node itself regenerates clean RF locally.

The two dominant variants differ in how much intelligence moves to the node. Remote PHY places only the physical layer in a Remote PHY Device, keeping the DOCSIS MAC and scheduler in a Converged Cable Access Platform (CCAP) core back in the headend; the two communicate over a pseudowire defined by the Downstream External PHY Interface (DEPI) and Upstream External PHY Interface (UEPI). Remote MACPHY moves both the MAC and PHY into the node, so each Remote MACPHY Device schedules its own DOCSIS traffic and connects upstream over ordinary IP. Remote PHY simplifies node hardware and pools capacity centrally; Remote MACPHY reduces the network-wide timing burden because each node is largely self-contained.

DAA also changes the timing and transport requirements. Because the upstream CMTS scheduling decisions must align precisely with the remote modulator, the node and core synchronize over IEEE 1588v2 Precision Time Protocol to roughly plus or minus 1.5 microseconds, which forces operators to add a PTP grandmaster clock to the hub. The payoff is large: digital transport tolerates far longer fiber spans, supports node segmentation without adding analog lasers, and recovers enough link budget to justify the move to wider 1.2 GHz and 1.8 GHz spectrum plans.

Link Budget and MER Recovery

End-to-end MER (analog optics):
1 / MER_total ≈ 1 / MER_coax + 1 / CNR_optical + 1 / MER_RF

DAA case (digital optics):
1 / MER_total ≈ 1 / MER_coax + 1 / MER_RF (optical term removed)

QAM order vs. required MER (approx.):
256-QAM → ≈ 34 dB | 1024-QAM → ≈ 37 dB | 4096-QAM → ≈ 43 dB

Removing the analog optical CNR term (≈ 48 to 51 dB) from the reciprocal sum typically lifts delivered MER from ≈ 37 dB to ≈ 41 to 43 dB, the margin needed to deploy 4096-QAM DOCSIS 3.1 OFDM profiles.

Centralized vs. Distributed Access Compared

Attribute	Centralized (Analog Optics)	Remote PHY (DAA)	Remote MACPHY (DAA)
Fiber carries	Analog AM RF	Digital Ethernet	Digital Ethernet
Node uplink	1310/1550 nm optics	10 to 25 GbE	10 to 25 GbE
MAC location	Headend CCAP	Headend CCAP core	In the node
PHY location	Headend + node	In the node (RPD)	In the node (RMD)
Timing need	Loose	PTP ± 1.5 μs	Relaxed (local sched.)
Delivered MER	≈ 37 dB	≈ 41 to 43 dB	≈ 41 to 43 dB
Max QAM order	256-QAM typical	4096-QAM	4096-QAM

Common Questions

Frequently Asked Questions

What is the difference between Remote PHY and Remote MACPHY in a DAA deployment?

Remote PHY (R-PHY) puts only the DOCSIS and video physical layer in the node via a Remote PHY Device, keeping the MAC in a centralized CCAP core connected over the DEPI and UEPI pseudowires. Remote MACPHY (R-MACPHY) moves both MAC and PHY into the node, so each Remote MACPHY Device schedules DOCSIS traffic locally and uplinks over standard IP. R-PHY pools capacity centrally with simpler node hardware; R-MACPHY reduces network-wide timing dependence. Most large MSOs have standardized on R-PHY.

How much does DAA improve the downstream SNR compared to analog optics?

Analog AM optical links accumulate CNR of about 48 to 51 dB plus CSO and CTB distortion before the coax even sees the signal. Digitizing in the node removes that optical term from the impairment budget, so delivered MER is set mostly by the short coax run. Operators typically gain 3 to 6 dB of MER, often pushing downstream MER above 40 to 43 dB, the threshold for reliable 4096-QAM DOCSIS 3.1 OFDM profiles.

What Ethernet transport bandwidth does a Remote PHY node require?

An R-PHY node sends modulated DOCSIS and IP video as digital Ethernet rather than analog RF. A 1.2 GHz downstream with a 204 MHz upstream usually needs a 10GbE link, and segmented builds often provision two 10GbE or a 25GbE uplink. The node also needs IEEE 1588v2 (PTP) timing to about ± 1.5 microseconds so the RPD and CCAP core agree on upstream scheduling, which is why DAA adds a PTP grandmaster clock at the hub.

Related Terms

← D0 DAB Antenna →