ANSI SCTE 165-14-2019 pdf free download – IPCablecom 1.5 Part 14: Embedded MTA Analog Interface and Powering.
1.1Purpose
This standard defines the embedded MTA(E-MTA) requirements for the analog interface and for powering of theE-MTA.An embedded MTA is a DOCSIS cable modem(CM) integrated with an IPCablecom multimedia terminaladapter (MTA).
The purpose of this specification is to define a set of requirements that will enable a service that is sufficientlyreliable to meet an assumed consumer expectation of essentially constant availability, including, specifically,availability during power failure at the customer ‘s premises, and (assuming the service is used to connect to thePSTN), access to emergency services (91 1, etc.).
1.2Scope
This document covers requirements for the E-MTA analog interface and for powering of the E-MTA. It is the intention of this document to address requirements only for the E-MTA.See Section 5.3.1 for a complete descriptionof the E-MTA.
To enable a service that meets the assumed customer expectations described in Section 1.1, three E-MTA interfaceshave been identified: (1) powering the E-MTA, (2) telemetry support, and (3) the analog POTS interface.
Powering the E-MTA is critical for the service to function during periods when utility power fails.Consequently, thepower consumption characteristics of the E-MTA will enable service providers to offer alternate powering techniques.
Telemetry support enables the service provider to remotely monitor the status of the E-MTA. The first application oftelemetry enables remote monitoring of the E-MTA power source.
The analog POTS interface requirements ensure that CPE that meets telephone industry interoperability
requirements (normal telephones, answering machines, etc.) will also operate in the IPCablecom environment. Notethat the voice-grade analog transmission requirements are dependent on the compression algorithm utilized to
transport the packetized voice signal in the IPCablecom architecture.These requirements are derived from existingPSTN requirements that are based on a full 64 kbps voice channel. Therefore, the requirements specified are
relevant only for theG.7ll audio codec. Other audio codec compression algorithms specified by IPCablecom [2] arenot addressed in this specification.
Note also that the telemetry interface specified in this document is between the E-MTA and an external local un-interruptible power supply (UPS).The UPS itself is not within the scope of this document, so specific requirementsfor the UPS are not included here.Nonetheless, requirements for the E-MTA telemetry interface may have certaindesign implications on the UPS.
1.3Motivation
IPCablecom interface specifications define a system architecture to allow vendors to develop interoperableequipment capable of providing packet-based voice, video and other high-speed multimedia services over hybridfiber coax (HFC) cable systems utilizing the DOCSIS protocol. IP-based voice telephony services are one possibleservice application.
From time to time this document refers to the voice communications capabilities of an IPCablecom network in termsof “IPTelephony.”The legalVregulatory classification of IlP-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 standardterms such as “call,””call signaling,” “telephony,” etc., it should be recalled that, while an lPCablecom networkperforms activities analogous to these PSTN functions, the manner by which it does so differs considerably from themanner in which they are performed in the PSTN by telecommunications carriers, and that these differences may besignificant for legal/regulatory purposes. Moreover, while reference is made here to “IP Telephony,” it should be recognized that this term embraces a number of different technologies and network architecture, each with different potential associated legal/regulatory obligations. No particular legal/regulatory consequences are assumed or implied by the use of this term.ANSI SCTE 165-14 pdf download