ANSI SCTE 165-05:2019 pdf free download – IPCablecom 1.5 Part 5: MTA Device Provisioning
5.1 Service Goals
Cable operators are interested in deploying high-speed data communications systems on cable television systems. Cable operators have prepared a series of interface specifications that will permit the early definition, design, development, and deployment of packet data-over-cable systems on an uniform, consistent, open, non-proprietary, multi-vendor interoperable basis. The intended service enables voice communications, video, and data services based on bi-directional transfer of Internet protocol (IP) traffic, between the cable system headend and customer locations, over an all-coaxial or hybrid-fiber/coax (HFC) cable network, defined by the data-over-cable service interface specification (DOCSIS) standard. This is shown in simplified form in Figure 1. It is to be noted that the term “DOCSIS” in this document is understood to refer to DOCSIS version 1.1 or later, unless explicitly specified otherwise. Implementations of eCMs will refer to the corresponding DOCSIS versions and associated requirements in this document and DOCSIS specifications for compliance.
The transmission path over the cable system is realized at the headend by a cable modem termination system (CMTS), and at each customer location by a cable modem (CM). The intent is for operators to transfer IP traffic transparently between these interfaces. The legal/regulatory classification of IP-based voice communications provided over cable networks and otherwise, and the legal/regulatory obligations, if any, borne by providers of such voice communications, are not yet fully defined by appropriate legal and regulatory authorities. Nothing in this specification is addressed to, or intended to affect, those issues. In particular, while this document uses standard terms such as “call,” “call signaling,” “telephony,” etc., it will be evident from this document that while an IPCablecom network performs activities analogous to these PSTN functions, the manner by which it does so differs considerably from the manner in which they are performed in the PSTN by telecommunications carriers. These differences may be significant for legal/regulatory purposes.
5.2 Specification Goals
The goal of this specification document is to meet and to satisfy cable member companies (a.k.a. MSO), IPCablecom, and business and technical requirements. Requirements relevant to device provisioning are:
• A single physical device (e.g., embedded-MTA) will be completely provisioned and managed by a single business entity. This provider may establish business relationships with additional providers for services such as data, voice communications, and other services.
• To provision an E-MTA, both the DOCSIS and IPCablecom 1.5 provisioning steps MUST be performed. The eMTA MUST have its own IP address, different from the IP Address(es) of the eCM. The eMTA MUST also have its own MAC address, different from the MAC address of the eCM. Furthermore, the E-MTA MUST in be able to operate in environments where the eMTA IP address may be in the same, or different subnet as the eCM.