hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.2 Encoding | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.2.0 Encoding schemes | ETSI TS 103 280 [7] messages shall be encoded in either XML (see clause 9.2.1) or JSON (see clause 9.2.4). Clauses 9.2.2 and 9.2.3 apply to both encodings. A Receiver that receives a WI message in a given encoding shall either respond in the same encoding or return an error message indicating that it does not support t... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.2.1 XML Schema | Messages encoded in XML format [4] shall conform to the WI XSD Schema, which is provided as an XML XSD Schema Set in the Forge repository (https://forge.etsi.org/rep/li/schemas-definitions/-/tree/main/103120). Each National Profile may, subject to national agreement, specify additional schema files that give definition... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.2.2 Error conditions | If a Receiver receives a WI Message which does not conform to the relevant schema (either XSD or JSON), or fails due to some other transport-related issue (e.g. it is too large for the receiver to process or the version is not supported), it shall not attempt to process any of the contents. It shall respond with a top-... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.2.4 JSON Schema | Messages encoded in JSON format [27] shall conform to the WI JSON Schema, which is provided as a set of JSON Schema files [28] in the Forge repository (https://forge.etsi.org/rep/li/schemas-definitions/-/tree/main/103120). This schema set is derived from the XSD schema set (see clause 9.2.1) following the translation s... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.3 HTTP Transport | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.3.1 Use of HTTP | HTTP Transport is the defined transport mechanism for WI messages in the present document, unless a nationally-defined transport mechanism is to be used (see clause 9.4). For security details relating to the HTTP exchange, see clause 9.3.4. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.3.2 Client/Server architecture | When using HTTP for WI message exchange, the Sender acts as an HTTP client while the Receiver acts as an HTTP server. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.3.3 HTTP Configuration | The POST method shall be used for all HTTP requests. The body of the POST message shall contain a single HI1 Request Message, as defined in clause 5 and clause 6.3.1, and encoded as per clause 9.2. The Content-Type shall be set to text/xml or application/json as appropriate (see clause 9.2.0). Caching shall not be used... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.3.4 Transport security | Implementations shall support HTTPS as defined in IETF RFC 9110 [5], including the support for mutual authentication through bidirectional certificate usage. Implementations shall use HTTPS unless specifically directed otherwise in the relevant national profile. The use of pre-shared keys may be considered for authenti... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 9.4 Nationally-defined Transport | If HTTP transport as defined in clause 9.3 is not to be used in a particular country, a nationally-defined alternative may be agreed on a national basis. Such a transport mechanism shall not break any of the requirements of clause 9.2. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10 Delivery Object | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.1 Overview | A delivery Object represents the delivery of information to a request for that information as part of a task. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.2 DeliveryObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.2.1 Overview | The DeliveryObject consists of the following fields. Where the DeliveryObject is created in response to a Task Object, that Task Object shall be referenced in the AssociatedObjects field of the DeliveryObject. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 75 Table 10.1: DeliveryObject Field Format Description Reference Refere... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.2.3 Delivery | Status DeliveryStatus DictionaryEntry The current status of the Delivery according to the Sender. Clause 10.2.4 DeliveryDesiredStatus DeliveryDesiredStatus DictionaryEntry The desired status of the Delivery, as specified by a Receiver. Clause 10.2.5 EncryptionDetails DeliveryEncryptionDetails Information that described... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.2.2 Manifest | A Manifest structure is used to describe the format of a Delivery structure. The Manifest either points to existing formats (such as the format specified in ETSI TS 102 657 [22]) for the delivery of information but also supports a mechanism to attach a manifest to that delivery. An example of this is where a manifest i... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.2.4 DeliveryStatus | The DeliveryStatus field indicates the current status of the Delivery as determined by the Sender. A Receiver may attempt to set the DeliveryStatus as part of an UPDATE Request. The Status field provides a mechanism for mapping the content of the DeliveryObject to the relevant nationally-defined processes. The rules fo... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.2.5 DeliveryDesiredStatus | The DeliveryDesiredStatus field indicates the current status of the Delivery as determined by the Receiver. Given as a DeliveryDesiredStatus Dictionary Entry. The DeliveryDesiredStatus Dictionary is defined in table 10.9 (see annex F for more details on Dictionaries). ETSI ETSI TS 103 120 V1.22.1 (2026-03) 79 Table 10.... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 10.2.6 DeliveryEncryptionDetails | The DeliveryEncryptionDetails structure provides information on what encryption has been applied to the content of the Delivery structure. Table 10.10: DeliveryEncryptionDetails Field Format Description Reference EncryptionReference Encryption Object identifier (see clause 7.9) Identifier of the Encryption Object used ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 1 Scope | The present document defines the embedded MTA (E-MTA) requirements for the analog interface and for powering of the E-MTA. An embedded MTA is a DOCSIS cable modem (CM) integrated with an IPCablecom multimedia terminal adapter (MTA). The purpose of the present document is to define a set of requirements that will enable... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] PKT-SP-NCS1.5-I03-070412: "PacketCable 1.5 Specifications; Network-Based Call Signaling Protocol", April 12, 2007, Cable Television Laboratories, Inc. [2] ETSI TS 103 161-3: "Access, Terminals, Transmission and Multiplexin... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] PKT-TR-ARCH1.5-V02-070412: "PacketCable 1.5 Architecture Framework", April 12, 2007, Cable Television Laboratories, Inc. [i.2] CM-SP-CMCI-C01-081104: ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 3 Definitions and abbreviations | |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Bellcore (Telcordia): PSTN research/standards organization Telcordia (Bellcore): PSTN research/standards organization |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: A/D Analog to Digital converter AC Alternating Current ANS Announcement Server CM Cable Modem CMCI Cable Modem Customer premise Interface CMS Call Management Server CMTS Cable Modem Termination System CPE Customer Premise Equipment NOTE: Usage... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 4 Void | |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 5 Introduction | |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 5.1 IPCablecom Overview | The IPCablecom project is aimed at defining interface documents that can be used to develop interoperable equipment capable of providing packet-based voice, video and other high-speed multimedia services over hybrid fibre coax (HFC) cable systems utilizing the Data Over Cable Interface Document [3]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 5.2 Service Goals | One potential application of the IPCablecom architecture is packet-based voice communications for cable system subscribers. The IPCablecom architecture as a whole enables voice communications, video, and data services based on bi-directional transfer of Internet protocol (IP) traffic between the cable system headend an... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 5.3 IPCablecom Reference Architecture | The IPCablecom architecture is composed of three distinct component networks: the "DOCSIS HFC Access Network", the "Managed IP Network" and the PSTN. The Cable Modem Termination System (CMTS) provides connectivity between the "DOCSIS HFC Access Network" and the "Managed IP Network". Both the Signalling Gateway (SG) and... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 5.3.1 Multimedia Terminal Adapter (MTA) | An MTA is an IPCablecom client device that contains a subscriber-side interface to the subscriber's CPE (e.g. telephone) and a network-side signalling interface to call control elements in the network (e.g. Call Management Server (CMS)). An MTA provides codecs and all signalling and encapsulation functions required for... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6 E-MTA Monitoring Requirements | The E-MTA is a critical element in the IPCablecom architecture. It provides the customer's interface to the service provider's network and is located outside the service provider's "headend". As such, it is critical that the operational status of the E-MTA be monitored in order to provide the quickest information to th... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.1 E-MTA Alarms | The E-MTA functions as the customer premise network interface to the IPCablecom network and thus enables service to the customer. If the E-MTA fails and is not capable of providing the intended service, the service provider will need to know about this condition quickly (and preferably before the customer). The minimum... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.1.1 CM Failures | The CM provides the critical connection between the MTA and the IPCablecom/DOCSIS network. A CM failure will affect the availability of the service. IPCablecom service will rely on the CM failure detection mechanisms defined by DOCSIS in [4]. DOCSIS specifies events that the CM must detect as well as events the CMTS mu... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.1.2 MTA Failures | The minimum MTA monitoring shall utilize the CM failure detection mechanisms defined by DOCSIS [4] since the CM and MTA are integrated together. Additional MTA monitoring mechanisms may be developed but are not defined in the present document. For example, the E-MTA may include internal on-line diagnostics utilized to ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.2 E-MTA Telemetry | The telemetry feature provides the ability for the E-MTA to transmit alarm information to the headend. The alarm information could reflect status of the E-MTA itself or of a supporting device connected to the E-MTA. Refer to [10] for information on the set of defined alarms. One powering option of the E-MTA is local po... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.2.1 Telemetry Signals (External Interface) | The E-MTA alarm telemetry input signals shall determine the input state by sensing the presence of a short circuit to ground (low) or an open circuit condition (float high) on the input connection (open drain compatible). The alarm active state is defined as the open circuit condition (float high). The alarm inactive s... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.2.1.1 Telemetry Signal 1 - AC Fail | The active alarm state of this signal indicates an "AC Fail" condition, which means the UPS, has detected a failure of the utility AC power and is operating off its battery. The inactive alarm state of this signal indicates an "AC Restored" condition which means the UPS has detected the presence of utility AC power and... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.2.1.2 Telemetry Signal 2 - Replace Battery | The active alarm state of this signal indicates a "Replace Battery" condition which means the UPS, via internal test mechanisms outside the scope of the present document, has determined that the battery can no longer maintain a charge sufficient enough to provide the designed amount of battery backup (e.g. eight hours ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.2.1.3 Telemetry Signal 3 - Battery Missing | The active alarm state of this signal indicates a "Battery Missing" condition, which means the UPS, has detected that a battery is not present and a battery should be installed in the UPS. The inactive alarm state of this signal indicates a "Battery Present" condition. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.2.1.4 Telemetry Signal - Battery Low | The active alarm state of this signal indicates a "Battery Low" condition which means the battery has sufficiently discharged (e.g. 75 % discharged) to the point where a power source can only be maintained for a short while longer. The inactive alarm state of this signal indicates a "Battery Not Low" condition which me... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 6.2.2 OSS Event Reporting | The MTA shall support the event and alarm reporting mechanism as defined in [10]. Furthermore, the MTA shall support the Powering events as defined in [10]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7 E-MTA Power Requirements | This clause defines the power requirements of the E-MTA. This includes power consumption and presents associated traffic models recommended for power consumption calculations. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.1 Power Considerations | E-MTA powering is an important element in providing reliable telephone service through HFC cable networks. There are two basic methods to power the E-MTA: 1) local with battery backup; and 2) network powering. Local power refers to utilizing the subscriber's home AC utility power as the supply for the E-MTA. A battery ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.2 Typical E-MTA Traffic Model | A projected "typical" E-MTA traffic model has been developed based on [9] and [i.3] and input from member operators. As the IPCablecom architecture is actually deployed in the field, and as consumer demand for services using that architecture continues to evolve, individual operators with actual IPCablecom implementati... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.3 Power Passing Tap Limitations | Power passing taps typically have a maximum continuous current rating that specifies limits on the amount of current that can be supplied to a particular "drop" off of the network (the drop is the clause of coax connecting the operator network to the subscriber's home). Power passing taps typically contain a self-reset... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.4 Average Power Calculations | For network-powered systems, E-MTA power is also limited by the total power available from the power node and the required number of E-MTAs to be supported from each node. Because a common power source is being utilized to power a large number of E-MTAs, long term average E-MTA power can be utilized for power node calc... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.5 Power Factor Considerations | Since network power utilizes alternating current (AC), the power factor of a device also affects a node's power calculation. Power factor specifies the ratio of watts to volt-amps. The IPCablecom power factor of an E-MTA device should be 0,85 or greater to ensure efficient utilization of the available network power. To... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.6 E-MTA Average Power Requirements | Since many different HFC power node domain architectures exist, it is not possible to calculate an E-MTA average power requirement that relates to all architectures. Nonetheless, several common power consumption objectives have been specified to enable efficient powering capabilities. The average E-MTA power consumptio... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.7 Service Requirements Under AC Fail Conditions | For local power with battery backup, the E-MTA device is aware of AC power failure via the UPS telemetry inputs or via internal means with an embedded UPS. Since data traffic is not required for IPCablecom service, data service may be de-activated immediately under local AC power fail conditions. However, all lines pro... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.8 Power Source Compatibility | To provide flexibility to make powering decisions on a node-by-node basis and to allow local power to network power migration, outdoor E-MTAs shall support both network power and local power with battery backup (as defined below). Since network powering is removed from the coax drop before entering the home, indoor E-M... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.9 Network Powering | Network power is supplied from a power node controlled by the service provider and is distributed through the HFC plant via the network cable. It is common practice for Network power to be delivered from the "tap" to the E-MTA either through centre conductor powering (centre coax conductor) or through composite pair (s... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.9.1 Centre Conductor Delivery | Centre conductor network power delivers power on the centre conductor of the coaxial cable drop. Outdoor E-MTAs shall be capable of extracting power from the centre conductor of the coaxial cable. If an E-MTA provides a subscriber side coaxial drop, network power shall be removed from the subscriber drop such that netw... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.9.2 Composite Pair Delivery | Composite pair network power delivers power on a separate pair of wires that are bundled with the coaxial cable drop (siamese) from the tap. E-MTAs shall be capable of accepting power though a separate pair of input terminals. The power-input terminals shall be compatible with 22, 24, and 26-gauge wire. The power-input... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.9.3 Network Power Characteristics | E-MTAs supporting network power shall be compatible with and properly operate from quasi-square wave voltages over the range 40-90 VAC at the input of the device. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.10 Local Powering with Battery Backup | Local powering is accomplished utilizing a UPS that converts household 120 V AC power to DC power for the E-MTA. The UPS also provides battery backup to bridge E-MTA operation through typical local power outages. In addition, telemetry signals provide remote monitoring capability for local AC power and battery conditio... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.10.1 E-MTA to UPS Interface | A standardized interface is defined between the E-MTA and an external UPS to allow vendor interoperability between the two devices. This interface is comprised of seven (7) conductors including two (2) for DC power, four (4) for telemetry signals, and one (1) for telemetry ground reference. The external E-MTA-UPS inter... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.10.1.1 Physical Connection | Since the interface cable between the E-MTA and UPS will typically be cut to length, the E-MTA should provide individual connections for each conductor but may utilize a standard multi-pin connector. The specific type of connection device will not be specified, however the connection device shall support 22, 24, and 26... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 7.10.1.2 Power Signals (External UPS) | The power interface is designed to provide 20 watts of peak power to the E-MTA which provides ample power for E-MTA implementations supporting a high speed data link and up to 4 telephony lines with a total ringing load of 10 REN. To enable the use of 22-26-gauge wire for the interface, 48 VDC nominal power is being re... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8 MTA Analog Port Requirements | The MTA analog port represents an interface between the IPCablecom/DOCSIS/IP (internet protocol) network and devices designed to function when connected to the PSTN using standard PSTN interfaces. The subscriber side of this interface is an analog interface consistent with the PSTN and the network side of this interfac... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1 Loop Start Signalling | |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.1 DC Supervisory Range | The DC supervisory range shall meet: RDC ≥ 450 Ω. RDC is the DC supervisory range. The actual value of RDC depends on the resistance of the loop wire from the E-MTA (the subscriber's inside wiring). That is, RDC = 430 + Rloop. NOTE: This accommodates a drop of 500 feet of AWG 22-gauge wire at 65 oC. Reference: clause 4... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.2 Idle State Voltage | The idle state is when the loop is open or on-hook. In this state the idle voltage satisfies: • Shall be 21 Vdc ≤ VIDLE ≤ 80 V dc. • Should be 42,75 Vdc ≤ VIDLE ≤ 80 V dc. • Ring is negative with respect to tip. • Rring-to-ground and tip-to-ground voltages are < 0. • Meet class A2 continuous source electrical safety fr... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.3 Loop Closure Detection | Loop closure is off-hook. Detection of loop closure shall meet: • Resistance ≤ RDC between tip and ring is loop closure. • Resistance ≥ 10 kΩ between tip and ring is not loop closure. • When loop closure is detected, appropriate actions as defined by the CMS will be taken. Reference: clause 4.1.4 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.4 Loop Open Detection | Loop open is on-hook. Detection of loop open shall meet: • Resistance ≥ 10 kΩ is loop open. • Resistance ≤ RDC + 380 Ω is not loop open. The MTA shall be able to distinguish between a hit, dial pulse, flash, or disconnect and signal appropriately to the CMS as defined in [1]. Reference: clause 4.1.5 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.5 Off-Hook Delay | The MTA shall be able to detect a subscriber origination request (off-hook) and attempt to transmit the notification to the CMS within 50 msec. 2-way voice signal transmission capability on the loop established within 50 msec of detecting the origination request (off-hook). Reference: clause 4.1.7 of [8]. Modified for ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.6 On-Hook Delay | The MTA shall be able to detect a subscriber termination request (on-hook) and attempt to transmit the notification to the CMS within 50 msec. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.7 Ringsplash | When the CMS indicates one 500 msec ringsplash, the MTA shall apply one 500 msec ± 50 msec ring burst to the line. Reference: clause 4.1.9 of [8]. NOTE: The ringsplash requirement stated here is within the bounds of the ringsplash requirement stated in [1]. Thus, by meeting this requirement, the NCS requirement is met ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.8 Distinctive Ringing | Defined ring cadences shall be applied to the drop within ±50 msec resolution. The MTA shall be able to apply any of the distinctive alerting patterns described in [1] to the line when signalled by the CMS. ETSI ETSI TS 103 161-14 V1.1.1 (2011-04) 20 Reference: clause 4.1.10 of [8]. NOTE: The ringing requirement stated... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.1.9 Transmission Path | The MTA shall support part-time on-hook transmission capabilities: part-time = within 400 msec after a ringsplash. On- hook transmission provides the capability of transmitting a voiceband signal in both directions on the loop when the loop is open (on-hook). Reference: clause 4.1.15 of [8]. Modified for IPCablecom. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2 General Supervision | |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2.1 Off-Hook Loop Current | The MTA shall provide at least 20 mA of loop current in the off-hook state. Loop voltage is such that the ring conductor is negative with respect to the tip conductor. Reference: clause 4.4.1 of [8]. Modified for IPCablecom. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2.2 Immunity to Line Crosses | Shorts between tip-to-tip, tip-to-ring, or ring-to-ring involving 2 or more lines shall not damage the MTA. Shorts between tip-to-ground or ring-to-ground involving 1 or more lines shall not damage the MTA. Reference: clause 4.4.3 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2.3 System Generated Open Intervals | When in the loop closure state (off-hook), interruptions to loop current feed shall not exceed 100 msec unless instructed by the CMS. Reference: clause 4.4.5 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2.4 Open Switching Interval Distortion | When in the loop closure state and providing loop current feed, loop current feed open commands of duration T shall have resolution to ±25 msec for 50 ≤ T ≤ 1 000 msec. When in the above state, the MTA shall continue to maintain loop closure (towards the CMS) with no interruptions > 1 msec. Loop current feed open shall... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2.5 Dial Pulsing | Dial pulses may be collected at the MTA. Depending on CMS instructions, the digits can either be individually sent or gathered according to the digit map and all digits sent in a single message. If the MTA supports dial pulsing, the MTA shall support 8 pps to 12 pps with 58 % to 64 % break. ETSI ETSI TS 103 161-14 V1.1... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2.6 DTMF Signalling | DTMF signalling will be collected at the MTA. Depending on CMS instructions, the digits can either be individually sent or gathered according to the digit map and all digits sent in a single message. The MTA shall not amplitude overload at the maximum expected DTMF signal level. (ANSI T1.401-1988 [11] describes the max... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.2.7 Dialtone Removal | The MTA shall remove dialtone within 250 msec of detecting the first dialled digit unless otherwise instructed by the CMS. NOTE: The NCS protocol defined in [1] provides the ability to request the MTA to play signals (in this case dialtone) in response to events (in this case off-hook). The protocol also provides the a... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3 General Ringing | |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.1 Alerting Signals | The MTA shall support unbalanced or balanced ringing. The applied cadence shall be within ±50 msec of the defined cadence. Nominal cadence has a 6-sec period with 1,7 sec to 2,1 sec ringing and 3,1 sec to 5,5 sec of silence. For Unbalanced Ringing: • Alerting cadence is applied to ring with tip grounded. • The dc compo... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.2 Ringing Delay | Ringing shall be applied within 200 msec of being signalled by the CMS. The cadence may be entered at any point (i.e. the cadence may start with the silent period). Reference: clause 4.5.3 of [8]. Modified for IPCablecom. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.3 Ringing Source | Shall meet the duration-limited source safety requirements of Telcordia GR-1089-CORE [7]. ETSI ETSI TS 103 161-14 V1.1.1 (2011-04) 22 Ringing frequency shall be 20 Hz ± 1 Hz. The dc component (offset) shall be ≤ 75 Vdc. Shall meet 1,2 ≤ peak-to-rms voltage ratio ≤ 1,6. The bridged C-weighted noise ≤ 90 dBrnC when refer... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.4 Ringing Capability | The minimum ringing voltage shall meet 40 Vrms across a 5 REN load on a drop with resistance ≤ RDC - 400 Ω. Reference: clause 4.5.5 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.5 Ringing Capacity | The MTA shall support 5 REN per line. The MTA shall support at least 10 REN per device for MTAs that support 2 or more lines. NOTE: It is anticipated that many MTAs will support more than 2 lines (i.e. 4 POTS lines) but it is also unreasonable to require the MTA with more than 2 lines to support 5 REN for each line for... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.6 Ring Trip | Ringing shall be removed within 200 msec of detecting loop closure. Reference: clause 4.5.7 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.7 Ring Trip Reporting Delay | The MTA shall be able to detect a ring trip and attempt to transmit the notification to the CMS within 300 msec. Reference: clause 4.5.8 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.3.8 Ring Trip Immunity | Ringing shall not be tripped when a termination of 10 kΩ in parallel with 6 uF is applied to tip and ring. Ringing shall not be tripped when a termination of 200 Ω is applied to tip and ring for ≤ 12 msec. Reference: clause 4.5.9 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4 Voice Grade Analog Transmission | The IPCablecom system utilizes digital transmission of voice signals to and from the MTA. The MTA converts between the digital voice signal on the IP network and the analog voice signal on the tip and ring loop. System impairments in the digital network, such as packet loss, can affect the voice signal but are outside ... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.1 Input Impedance | 600 Ω nominal. ERL (echo return loss) > 26 dB (29 dB objective). SRL (singing return loss) > 21 dB (24 dB objective). Reference: clause 5.3.1 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.2 Hybrid Balance | ERL > 21 dB (26 dB objective). SRL > 16 dB (21 dB objective). ERL = 15 + LT1 + LR1. SRL = 10 + LT1 + LR1. Where LT1 is transmit loss and LR1 is receive loss at 1 004 Hz. Reference: clause 5.4 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.3 Longitudinal Balance | 200 Hz: min > 45 dB, ave > 50 dB (ave > 61 dB objective). 500 Hz: min > 45 dB, ave > 50 dB (ave > 58 dB objective). 1 000 Hz: min > 45 dB, ave > 50 dB (ave > 52 dB objective). 3 000 Hz: min > 40 dB, ave > 45 dB. Reference: clause 5.5 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.4 MTA Loss | 4 dB in the D/A direction (towards the subscriber). 2 dB in the A/D direction (from the subscriber). This is the loss within the MTA. Reference: clause 5.8 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.5 MTA Loss Tolerance | Within ±1 dB of the MTA loss. Reference: clause 5.9 of [8]. ETSI ETSI TS 103 161-14 V1.1.1 (2011-04) 24 |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.6 Frequency Response | Off-hook transmission loss between 400 Hz to 2 800 Hz shall be within -0,5 to +1 dB of the loss at 1 004 Hz using a 0 dBm0 signal. On-hook transmission loss between 400 Hz to 2 800 Hz shall be within -1 to +2 dB of the loss at 1 004 Hz using a 0 dBm0 signal. (+ means more loss, - means less loss). Reference: clause 5.1... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.7 60 Hz Loss | The transmission path loss at 60 Hz shall be at least 20 dB greater than the off-hook transmission path loss at 1 004 Hz. The intention is to limit the encoding of 60 Hz induction in the A/D direction. Reference: clause 5.12 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.8 Amplitude Tracking | The deviation of a 1 004 Hz off-hook transmission path loss relative to the loss of a 0 dBm0 input signal. -37 to -3-dBm0 input: ±0,5 dB max (±0,25 dB ave). -50 to -37-dBm0 input: ±1,0 dB max (±0,5 dB ave). -55 to -50-dBm0 input: ±3,0 dB max (±1,5 dB ave). The deviation of a 1 004 Hz on-hook transmission path loss rela... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.9 Overload Compression | The increase in the off-hook transmission path loss at 1 004 Hz relative to the loss of a 0 dBm0 input signal. +3 dBm0 input: ≤ 0,5 dB increased loss. +6 dBm0 input: ≤ 1,8 dB increased loss. +9 dBm0 input: ≤ 4,5 dB increased loss. This is to ensure the receiver off-hook signal can be transmitted. Reference: clause 5.18... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.10 Idle Channel Noise | Not to exceed 20 dBrnC at the output of the MTA (18 dBrnC objective). Reference: clause 5.14 of [8]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.