ANSI SCTE 140:2019 pdf free download – Cable Modem IPv4 and IPv6 eRouter Specification
The cable modem is not referred to as a CPE in [MULPIv3.0] and [eDOCSIS]. Only devices attached to the Customer-Facing Interfaces of a cable modem are termed CPEs in [MULPIv3.0] and [eDOCSIS]. In TR-069, all devices located in the customer premises are considered CPEs. For the eRouter case, the term CPE has the same meaning within DOCSIS and TR-069; that is, the eRouter eSAFE is considered to be a ‘CPE’ under both the DOCSIS and TR-069 definitions, whereas the eCM is not. However, in this specification the eSAFE term is used when referring to the eRouter.
The main differences between both architectures are:
• A TR-069 Device 2.x [TR-181] is a TR-069 enabled CPE such as Residential Gateways (RGs) and other type of network devices (e.g., Access Modem). Different services can be implemented on a TR-069 Device. The Access Modem could be part of the device itself, by modeling it as an upstream interface of the entire TR-069 CPE, or the device contains only CPE services. In eDOCSIS the eCM is the Access Modem and eRouter is an application or functional entity (eSAFE). DOCSIS specifications define CMs and eSAFEs such as eRouters (embedded eRouters within an eCM).
• The management of eSAFEs in eDOCSIS is separated from the eCM. In TR-069 the management of services is integrated with the CPE device management.
TR-069 allows the transparent integration of access network technologies within the RG and CPE Services by combining the multiple components and their respective management data. The TR-069 device can either configure and monitor the Access Modem managed elements, simply report the Access Modem status and configuration, or do nothing with the Access Modem. The latter is the case of TR-069 in the context of eDOCSIS where the eCM is managed and provisioned independently of any eSAFE supporting TR-069 management. Figure 5-4 shows the alignment of eDOCSIS, eRouter, and TR-069 device architectures where the reuse of the TR- 069 protocol stack and data models for eDOCSIS devices such as eRouter can be seen. A general purpose eSAFE is shown for illustration purposes. The main difference between both models is the separation of the CM bridge of the internal WAN/LAN bridging function at the eRouter compared to the integrated TR-069 Device 2.x. Figure 5-4 is based on the “Simple Router Example (Interfaces Visualized)” figure of [TR-181]. In Figure 5-4, the stack layers are seen as interfaces per [TR-181], physical interfaces (e.g., Ethernet, SSID, WiFi Radio), bridges, ports, Bridges, Ethernet Link interfaces (LLC), and IP Interfaces. The Operator-Facing TR-069 Etherlink Interfaces correspond to the eDOCSIS Logical CPE Interfaces (LCI). IP additional interfaces can represent IP Tunnels and other IP forwarding models.