Cable modem termination system

<h2 id="connections">Connections</h2>
In order to provide high speed data services, a cable company will connect its headend to the Internet via very high capacity data links to a <a href="/facts/Network_service_provider/EUH6z0rc">network service provider</a>. On the subscriber side of the headend, the CMTS enables communication with subscribers' <a href="/facts/Cable_modem/YsXWhXhK">cable modems</a>. Different CMTSs are capable of serving different cable modem population sizes—ranging from 4,000 cable modems to 150,000 or more, depending in part on traffic and thus number of channels allocated to each service group and the size of the service groups, although it is recommended for an I-CMTS to service, for example, 30,000 subscribers (cable modems).<a class="footnote-ref" id="fnref:2" href="#fn:2">2</a> A given headend may have between 1–12 CMTSs to service the cable modem population served by that headend or <a href="/facts/Hybrid_fibre-coaxial/cfkuHATl">HFC hub</a>.
One way to think of a CMTS is to imagine a <a href="/facts/Router_(computing)/Nh5cIyVf">router</a> with <a href="/facts/Ethernet/nMfhU8tU">Ethernet</a> <a href="/facts/Network_interface_controller/wyf5FR29">interfaces</a> (connections) on one side and <a href="/facts/Coaxial_cable/aG9FfCpL">coaxial cable</a> <a href="/facts/Radio_frequency/aWku7h4R">RF</a> interfaces on the other side. The Ethernet side is known as the Network Side Interface or NSI.<a class="footnote-ref" id="fnref:3" href="#fn:3">3</a><a class="footnote-ref" id="fnref:4" href="#fn:4">4</a>
A service group is a group of customers that share communication RF channels and thus bandwidth. A CMTS has separate RF interfaces and connectors for downlink and uplink signals. The RF/coax interfaces carry RF signals to and from coaxial "trunks" connected to subscribers' cable modems, using one pair of connectors per trunk, one for downlink and the other for uplink. In other words, there can be a pair of RF connectors for every service group, although it is possible to configure a network with different numbers of connectors that service a set of service groups, based on the number of downstream and upstream channels the cable modems in every service group use. Every connector has a finite number of channels it can carry, such as 16 channels per downstream connector, and 4 channels per upstream connector, depending on the CMTS.<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a> For example, if the cable modems on every service group use 24 channels for downstream, and 2 channels for upstream, then 3 downstream connectors can service the cable modems on two service groups, and be serviced by 1 upstream connector.<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a> A service group may serve up to 500 households. A service group has channels, whose bandwidth is shared among all members of the service group.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a><a class="footnote-ref" id="fnref:8" href="#fn:8">8</a><a class="footnote-ref" id="fnref:9" href="#fn:9">9</a><a class="footnote-ref" id="fnref:10" href="#fn:10">10</a><a class="footnote-ref" id="fnref:11" href="#fn:11">11</a><a class="footnote-ref" id="fnref:12" href="#fn:12">12</a> The channels are later regrouped at the cable headend or distribution hub and serviced by CMTSs and other equipment such as Edge QAMs.
The RF signals from a CMTS, are connected via coaxial cable to headend RF management modules for RF splitting and combining, with other equipment such as other CMTSs so that several CMTS can service one service group,<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a><a class="footnote-ref" id="fnref:14" href="#fn:14">14</a> and then to an "optics platform" or headend platform, which has transmitter and receiver modules that turn the RF signals into light pulses for delivery over fiber optics through an HFC network.<a class="footnote-ref" id="fnref:15" href="#fn:15">15</a><a class="footnote-ref" id="fnref:16" href="#fn:16">16</a> Examples of optics platforms are the Arris CH3000 and Cisco Prisma II. At the other end of the network, an optical node converts the light pulses into RF signals again and sends them through a coaxial cable "trunk". The trunk has one or more amplifiers along its length, and on the trunk there are distribution "taps" to which customers' modems are connected via coaxial cable.
In fact, most CMTSs have both Ethernet interfaces (or other more traditional high-speed data interfaces like <a href="/facts/Synchronous_optical_networking/G3LgtGS6">SONET</a>) as well as RF interfaces. In this way, traffic that is coming from the <a href="/facts/Internet/Xw1rVvJU">Internet</a> can be routed (or bridged) through the Ethernet interface, through the CMTS and then onto the RF interfaces that are connected to the cable company's hybrid fiber coax (<a href="/facts/Hybrid_fibre-coaxial/cfkuHATl">HFC</a>). The traffic winds its way through the HFC to end up at the cable modem in the subscriber's home. Traffic from a subscriber's home system goes through the cable modem and out to the Internet in the opposite direction.
CMTSs typically carry only <a href="/facts/Internet_Protocol/Qq6VeEal">IP</a> traffic. Traffic destined for the cable modem from the Internet, known as downstream traffic, is carried in IP packets encapsulated according to <a href="/facts/DOCSIS/UTcmNEsr">DOCSIS</a> standard. These packets are carried on data streams that are typically modulated onto a TV channel using either 64-QAM or 256-QAM versions of <a href="/facts/Quadrature_amplitude_modulation/02j52SWG">quadrature amplitude modulation</a>.
Upstream data (data from cable modems to the headend or Internet) is carried in Ethernet frames encapsulated inside DOCSIS frames modulated with <a href="/facts/QPSK/TFnpYe64">QPSK</a>, 16-QAM, 32-QAM, 64-QAM or 128-QAM using <a href="/facts/Time-division_multiple_access/ue5UzN7B">TDMA</a>, ATDMA or S-<a href="/facts/CDMA/o2RLKE4M">CDMA</a> frequency sharing mechanisms. This is usually done at the "subband" or "return" portion of the <a href="/facts/North_American_cable_television_frequencies/5pck3YoP">cable TV spectrum</a> (also known as the "T" channels), a much lower part of the frequency spectrum than the downstream signal, usually 5–42 MHz in <a href="/facts/DOCSIS/UTcmNEsr">DOCSIS 2.0</a> or 5–65 MHz in EuroDOCSIS.
A typical CMTS allows a subscriber's computer to obtain an <a href="/facts/IP_address/z9V22Sw9">IP address</a> by forwarding <a href="/facts/Dynamic_Host_Configuration_Protocol/lpASHnhz">DHCP</a> requests to the relevant servers. This DHCP server returns, for the most part, what looks like a typical response including an assigned IP address for the computer, gateway/router addresses to use, DNS servers, etc.
The CMTS may also implement some basic filtering to protect against unauthorized users and various attacks. <a href="/facts/Traffic_shaping/VCF0Gb3b">Traffic shaping</a> is sometimes performed to prioritize application traffic, perhaps based upon subscribed plan or download usage and also to provide guaranteed <a href="/facts/Quality_of_service/joz9VkUm">Quality of service</a> (QoS) for the cable operator's own <a href="/facts/PacketCable/g4gzzuM9">PacketCable</a>-based <a href="/facts/VOIP/5QGBbXYg">VOIP</a> service. However, the function of traffic shaping is more likely done by a Cable Modem or policy traffic switch. A CMTS may also act as a <a href="/facts/Network_bridge/5nyTQtNW">bridge</a> or <a href="/facts/Router_(computing)/Nh5cIyVf">router</a>.
A customer's <a href="/facts/Cable_modem/YsXWhXhK">cable modem</a> cannot communicate directly with other modems on the line. In general, cable modem traffic is routed to other cable modems or to the Internet through a series of CMTSs and traditional routers. However, a route could conceivably pass through a single CMTS.
A CCAP (Converged Cable Access Platform) combines CMTS and Edge QAM functionality in a single device so that it can provide both data (internet) with CMTS functionality, and video (TV channels) with Edge QAM functionality.<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a><a class="footnote-ref" id="fnref:18" href="#fn:18">18</a> Edge QAM (Quadrature Amplitude Modulator/Modulation) converts video sent via IP (internet protocol) or otherwise, into a QAM signal for delivery over a cable network. Edge QAMs are normally standalone devices placed at the "edge" of a network. They can also be connected to a CMTS core, to make up an M-CMTS system which is more scalable. A CMTS core is normally a conventional or I-CMTS that supports operation as a CMTS core in an M-CMTS system.<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a><a class="footnote-ref" id="fnref:20" href="#fn:20">20</a><a class="footnote-ref" id="fnref:21" href="#fn:21">21</a>

<h2 id="architectures">Architectures</h2>
A CMTS can be broken down into several different architectures, Integrated CMTS (I-CMTS), Modular (M-CMTS), Virtual CMTS (vCMTS) and remote CMTS. An I-CMTS incorporates into a single unit all components necessary for its operation.<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a> There are both pros and cons to each type of architecture.

<h3>Modular CMTS (M-CMTS)</h3>
In a M-CMTS solution the architecture of an I-CMTS is broken up into two components. The first part is the Physical Downstream component (PHY) which is known as the Edge QAM (EQAM). The second part is the IP networking and <a href="/facts/DOCSIS/UTcmNEsr">DOCSIS</a> MAC Component which is referred to as the M-CMTS Core. There are also several new protocols and components introduced with this type of architecture. One is the DOCSIS Timing Interface, which provides a reference frequency between the EQAM and M-CMTS Core via a DTI Server. The second is the Downstream External PHY Interface (DEPI). The DEPI protocol controls the delivery of DOCSIS
frames from the M-CMTS Core to the EQAM devices <a class="footnote-ref" id="fnref:23" href="#fn:23">23</a> Some of the challenges that entail an M-CMTS platform are increased complexity in RF combining and an increase in the number of failure points. One of the benefits of an M-CMTS architecture is that it is extremely scalable to larger numbers of downstream channels.<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a>

<h3>Virtual CMTS</h3>
Virtual CCAPs (vCCAPs) or virtual CMTSs (vCMTSs) are implemented on commercial off the shelf x86-based servers with specialized software,<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a> and can be used to increase service capacity without purchasing new CMTS/CCAP chassis, or add features to the CMTS/CCAP more quickly.<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a>

<h3>Remote CMTS</h3>
Remote CMTS/Remote CCAP moves all CMTS/CCAP functionality to the outside plant, in stark contrast to conventional CMTSs or CCAPs which are installed at a service provider location.<a class="footnote-ref" id="fnref:27" href="#fn:27">27</a><a class="footnote-ref" id="fnref:28" href="#fn:28">28</a>

<h2 id="manufacturers">Manufacturers</h2>
<h3>Current</h3>
<ul><li><a href="/facts/Arris_Group/3EaW5kRt">ARRIS Group</a></li>
<li>C9 Networks</li>
<li>Catapult Technologies</li>
<li>Coaxial Networks Inc.</li>
<li>Casa Systems</li>
<li><a href="/facts/Cisco_Systems/ocDgQt6T">Cisco Systems</a></li>
<li>Chongqing Jinghong</li>
<li>Damery sa</li>
<li><a href="http://www.gainspeed.com">Gainspeed (Nokia company)</a></li>
<li>WISI Communications GmbH</li>
<li><a href="/facts/Kathrein/Jf7q7CzE">Kathrein</a></li>
<li>Suma Scientific</li>
<li><a href="/facts/Huawei_Technologies/Qwu0tbnL">Huawei Technologies</a></li>
<li><a href="/facts/Harmonic_Inc./jSphsoGb">Harmonic Inc.</a></li>
<li><a href="/facts/Teleste/6CItAAf6">Teleste</a></li></ul>
<h3>Historical</h3>
<ul><li>3COM (Acquired by <a href="/facts/Hewlett-Packard/abuNSYNu">HP</a>)</li>
<li>Broadband Access Systems (Acquired by <a href="/facts/ADC_Telecommunications/UModdroM">ADC Telecommunications</a>)</li>
<li><a href="/facts/ADC_Telecommunications/UModdroM">ADC Telecommunications</a> (CMTS business acquired by <a href="/facts/BigBand_Networks/UX17eL8f">BigBand Networks</a>)</li>
<li><a href="/facts/BigBand_Networks/UX17eL8f">BigBand Networks</a> (Exited CMTS business, remaining business later acquired by <a href="/facts/Arris_Group/3EaW5kRt">ARRIS</a>)</li>
<li>Cadant (Acquired by <a href="/facts/Arris_Group/3EaW5kRt">ARRIS</a>)</li>
<li>Com21 (<a href="https://web.archive.org/web/20110609133306/http://www.cedmagazine.com/end-of-line-for-com21.aspx">CMTS business acquired by ARRIS</a>)</li>
<li>RiverDelta (Acquired by Motorola)</li>
<li><a href="/facts/Terayon/TxuTD8U8">Terayon</a> (Acquired by Motorola)</li>
<li><a href="/facts/Pacific_Broadband_Communications/KytWMJCv">Pacific Broadband Communications</a> (Acquired by <a href="/facts/Juniper_Networks/Vw0DBzXP">Juniper Networks</a>)</li>
<li><a href="/facts/Juniper_Networks/Vw0DBzXP">Juniper Networks</a> (Exited CMTS business)</li>
<li>LanCity (Acquired by <a href="https://www.planetbroadband.com/happy-25th-anniversary-lancity/">BayNetworks</a>)</li>
<li>Motorola (Acquired by ARRIS)</li>
<li>Daphne sa (Acquired by Damery sa)</li>
<li><a href="/facts/Scientific_Atlanta/IBARBkP0">Scientific Atlanta</a> (Acquired by Cisco)</li></ul>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/DOCSIS/UTcmNEsr">DOCSIS</a></li></ul>

<h2 id="external-links">External links</h2>

Wikimedia Commons has media related to CMTS.

<h2 id="references">References</h2>

<ol>
<li id="fn:1">"exv99w1". sec.gov. <a href="https://www.sec.gov/Archives/edgar/data/1141107/000095012311058190/g27481exv99w1.htm" target="_blank">https://www.sec.gov/Archives/edgar/data/1141107/000095012311058190/g27481exv99w1.htm</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Arris E6000 
manual https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF <a href="https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF" target="_blank">https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Data-Over-Cable Service Interface Specifications
DOCSIS® 3.0
MAC and Upper Layer Protocols Interface 
Specification
CM-SP-MULPIv3.0-C01-171207 <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">"Specifications Search". <a href="https://www.cablelabs.com/specifications/CM-SP-CMTS-NSI" target="_blank">https://www.cablelabs.com/specifications/CM-SP-CMTS-NSI</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Arris E6000 
manual https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF <a href="https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF" target="_blank">https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">The Arris E6000 manual https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF mentions upstream modules with 96 channels divided by 24 ports, and downstream modules with 128 channels divided by 8 ports <a href="https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF" target="_blank">https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">"Exv99w1". <a href="https://www.sec.gov/Archives/edgar/data/1141107/000095012311058190/g27481exv99w1.htm" target="_blank">https://www.sec.gov/Archives/edgar/data/1141107/000095012311058190/g27481exv99w1.htm</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">A Side-By Side Comparison of Centralized 
vs. Distributed Access Architectures. Commscope https://www.commscope.com/globalassets/digizuite/1618-arris-centralized-vs-distributed-access-networks-wp.pdf CMTS/CCAP handles service groups directly
 <a href="https://www.commscope.com/globalassets/digizuite/1618-arris-centralized-vs-distributed-access-networks-wp.pdf" target="_blank">https://www.commscope.com/globalassets/digizuite/1618-arris-centralized-vs-distributed-access-networks-wp.pdf</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">HFC Cable Architecture
Wade Holmes one optical node per service group https://courses.cs.duke.edu/spring18/compsci356/slides/cable-hfc-intro.pdf <a href="https://courses.cs.duke.edu/spring18/compsci356/slides/cable-hfc-intro.pdf" target="_blank">https://courses.cs.duke.edu/spring18/compsci356/slides/cable-hfc-intro.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">E6000® Converged Edge Router
Release 6.0 https://www.commscope.com/globalassets/digizuite/61837-e6000-cer-rel-6-0-data-sheet.pdf is a CCAP (CMTS) that can handle 96 upstream and 96 downstream service groups for a total of 192 streams, divided by 12 available slots in the router's image and in https://fccid.io/ANATEL/02605-15-07236/Manual-E6000/166C8E9C-8C13-4F42-B929-31E3DDBB82CA/PDF is 16 streams per slot, every slot has 16 connectors. The router has 14 slots but 2 are reserved, a service group has separate downlink and uplink cables at the CMTS according to diagram in Data-Over-Cable Service Interface Specifications 
DOCSIS®
 3.1 and the Arris E6000 manual where upstream and downstream ports use different connectors 
Physical Layer Specification and also to make use of 192 connectors in 12 slots with 16 connectors per slot but only 96 downlink and 96 uplink service groups
 <a href="https://www.commscope.com/globalassets/digizuite/61837-e6000-cer-rel-6-0-data-sheet.pdf" target="_blank">https://www.commscope.com/globalassets/digizuite/61837-e6000-cer-rel-6-0-data-sheet.pdf</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">E6000® Converged Edge Router
Downstream Cable Access Module 2 (DCAM-2) https://www.normann-engineering.com/products/product_pdf/ccap_cmts/arris/e6000-cer-dcam2.pdf has 16 ports for downstream signals, occupies 1 slot in a 14-slot e6000 chassis where 2 slots are reserved for router system modules <a href="https://www.normann-engineering.com/products/product_pdf/ccap_cmts/arris/e6000-cer-dcam2.pdf" target="_blank">https://www.normann-engineering.com/products/product_pdf/ccap_cmts/arris/e6000-cer-dcam2.pdf</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">https://archive.nanog.org/sites/default/files/08-Noll.pdf mentions "coax feeder cable" instead of trunk but mentions trunk or distribution amplifiers on the feeder which originates from an optical node or just node according to Optical Node 
Series (NC)
NC4000H4 
1.2 GHz Fiber Deep Node https://www.commscope.com/globalassets/digizuite/61985-nc4000h4.pdf <a href="https://archive.nanog.org/sites/default/files/08-Noll.pdf" target="_blank">https://archive.nanog.org/sites/default/files/08-Noll.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">Arris E6000 
manual https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF <a href="https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF" target="_blank">https://fccid.io/ANATEL/01759-14-07236/Manual-E6000/50DAF2B5-F106-42DF-A563-6008357AC079/PDF</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">Data-Over-Cable Service Interface Specifications
DOCSIS® 3.0
MAC and Upper Layer Protocols Interface 
Specification
CM-SP-MULPIv3.0-C01-171207 <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">Data-Over-Cable Service Interface Specifications
DOCSIS® 4.0
Physical Layer Specification
CM-SP-PHYv4.0-I06-221019. Cablelabs. <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">Data-Over-Cable Service Interface Specifications 
DOCSIS®
 3.1 
Physical Layer Specification 
CM-SP-PHYv3.1-I19-211110 <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">"StackPath". www.lightwaveonline.com. 13 September 2013. <a href="https://www.lightwaveonline.com/network-design/article/16658207/the-evolution-of-ccap" target="_blank">https://www.lightwaveonline.com/network-design/article/16658207/the-evolution-of-ccap</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">"Wayback Machine". www.nctatechnicalpapers.com. <a href="https://www.nctatechnicalpapers.com/Paper/2015/2015-evolution-of-cmts-ccap-architectures/download" target="_blank">https://www.nctatechnicalpapers.com/Paper/2015/2015-evolution-of-cmts-ccap-architectures/download</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">Cisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide
Chapter 3: Solution Overview for I-CMTS www.cisco.com/c/en/us/td/docs/cable/cmts/wideband/solution/guide/release_2-0/ds_solu/overvw_icmts.html <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">Cisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide
Chapter 2: Solution Overview for M-CMTS www.cisco.com/c/en/us/td/docs/cable/cmts/wideband/solution/guide/release_2-0/ds_solu/1overvw.html <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">Data-Over-Cable Service Interface Specifications
DOCSIS® 3.0
Physical Layer Specification
CM-SP-PHYv3.0-C01-171207 <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">Next Generation IPTV Services and Technologies. John Wiley & Sons. 2 January 2008. ISBN 978-0-470-16372-6. <a href="978-0-470-16372-6" target="_blank">978-0-470-16372-6</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">"Data-Over-Cable Service Interface Specifications Modular Headend Architecture" (PDF). www.cablelabs.com. Archived from the original (PDF) on 2015-02-27. Retrieved 2015-02-27. <a href="https://web.archive.org/web/20150227192938/http://www.cablelabs.com/wp-content/uploads/specdocs/CM-SP-M-OSSI-I08-081209.pdf" target="_blank">https://web.archive.org/web/20150227192938/http://www.cablelabs.com/wp-content/uploads/specdocs/CM-SP-M-OSSI-I08-081209.pdf</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">"CMTS Architectures". volpefirm.com. <a href="http://volpefirm.com/docsis3_architecture/" target="_blank">http://volpefirm.com/docsis3_architecture/</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">"Harmonic's 'CableOS' now connected to 18.4M modems". www.lightreading.com. <a href="https://www.lightreading.com/cable-technology/harmonic-s-cableos-now-connected-to-18-4m-modems" target="_blank">https://www.lightreading.com/cable-technology/harmonic-s-cableos-now-connected-to-18-4m-modems</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">"Lessons from Operating Tens of Thousands of Remote PHY Devices". SCTE. Retrieved 2 March 2024. <a href="https://www.nctatechnicalpapers.com/Paper/2021/2021-lessons-from-operating-tens-of-thousands-of-remote-phy-devices/download" target="_blank">https://www.nctatechnicalpapers.com/Paper/2021/2021-lessons-from-operating-tens-of-thousands-of-remote-phy-devices/download</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">"Impact of CCAP to CM Distance in a Remote PHY Architecture" (PDF). Retrieved 2 March 2024. <a href="http://bowe.id.au/michael/isp/DOCSIS/collected-references/2015-impact-of-ccap-to-cm-distance-in-a-remote-phy-architecture%20(1).pdf" target="_blank">http://bowe.id.au/michael/isp/DOCSIS/collected-references/2015-impact-of-ccap-to-cm-distance-in-a-remote-phy-architecture%20(1).pdf</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">Chapman, John. "DOCSIS Remote PHY Modular Headend Architecture (MHA v2)" (PDF). SCTE. Retrieved 2 March 2024. <a href="https://www.cisco.com/c/dam/en/us/solutions/ns341/ns522/ns791/workshop_remote_phy_chapman_paper.pdf" target="_blank">https://www.cisco.com/c/dam/en/us/solutions/ns341/ns522/ns791/workshop_remote_phy_chapman_paper.pdf</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
</ol>

Cable modem termination system open-in-new

Cable modem termination system