ITU-T J 167-2007 Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable modems (Study Group.pdf

1、 International Telecommunication Union ITU-T J.167TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2007) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom Media terminal adapter (MTA) device provisioning requirements for the delivery

2、of real-time services over cable television networks using cable modems ITU-T Recommendation J.167 ITU-T Rec. J.167 (12/2007) i ITU-T Recommendation J.167 Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable m

3、odems Summary ITU-T Recommendation J.167 describes the IPCablecom media terminal adapter (MTA) device initialization and provisioning process. It is limited to the provisioning of an IPCablecom embedded-MTA device by a single provisioning and network management provider. Source ITU-T Recommendation

4、J.167 was approved on 14 December 2007 by ITU-T Study Group 9 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. J.167 (12/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and

5、communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basi

6、s. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolu

7、tion 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration a

8、nd a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are me

9、t. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possib

10、ility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Re

11、commendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest informat

12、ion and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. J.167 (12/2007) iii CONTENTS Page 1 S

13、cope 1 2 References. 1 2.1 Normative references 1 2.2 Informative references 2 3 Terms and definitions . 3 4 Abbreviations and conventions. 3 4.1 Abbreviations . 3 4.2 Conventions 3 5 Introduction 4 5.1 Service goals. 4 5.2 Specification goals 4 5.3 IPCablecom reference architecture. 5 5.4 Component

14、s and interfaces. 6 6 Provisioning overview 10 6.1 Device provisioning 10 6.2 Endpoint provisioning 10 6.3 Provisioning state transitions 10 6.4 Basic and hybrid flow provisioning state transitions . 11 7 Provisioning flows 11 7.1 Backoff, retries and time-outs 12 7.2 Embedded-MTA power-on initializ

15、ation flows . 13 7.3 Embedded-MTA power-on initialization flow (Basic flow) 24 7.4 Embedded-MTA power-on initialization flow (Hybrid flow) 25 7.5 Endpoint provisioning completion notifications 28 7.6 Post initialization incremental provisioning. 29 7.7 Reflecting the State of the endpoint interface

16、in the ifTable 32 7.8 Provisioning of the signalling communication path between the MTA and CMS 33 7.9 MTA replacement. 33 7.10 Temporary signal loss. 33 7.11 MTA hard reboot/soft reset scenarios 33 8 DHCP options. 33 8.1 DHCP option 122: Client configuration option 33 8.2 DHCP option 60: Vendor-cli

17、ent identifier . 38 8.3 DHCP options 12 and 15 38 8.4 DHCP option 6 . 38 8.5 DHCP option 43 . 38 8.6 DHCP option 1 . 41 iv ITU-T Rec. J.167 (12/2007) Page 8.7 DHCP option 3 . 41 8.8 DHCP OPTION CL_V4_PACKETCABLE_MIB_ENV_OPTION 41 9 MTA provisionable attributes. 42 9.1 MTA configuration file 42 10 MT

18、A device capabilities. 56 10.1 IPCablecom version 57 10.2 Number of telephony endpoints . 57 10.3 TGT support . 57 10.4 HTTP download file access method support 57 10.5 MTA24 event SYSLOG notification support. 57 10.6 NCS service flow support. 58 10.7 Primary line support . 58 10.8 Vendor specific T

19、LV Type(s) 58 10.9 NVRAM ticket/Ticket information storage support. 58 10.10 Provisioning event reporting support . 58 10.11 Supported CODEC(s). 58 10.12 Silence suppression support . 59 10.13 Echo cancellation support. 59 10.14 RSVP support . 59 10.15 UGS-AD support 59 10.16 MTAs “ifIndex“ starting

20、 number in “ifTable“. 60 10.17 Provisioning flow logging support . 60 10.18 Supported provisioning flows. 60 10.19 T38 version support 61 10.20 T38 error correction support. 61 10.21 RFC 2833 DTMF support 61 10.22 Voice metrics support. 61 10.23 Device MIB support . 61 10.24 Multiple grants per inte

21、rval support . 63 10.25 V.152 Support. 63 11 TLV-38 SNMP notification receiver specification. 64 11.1 Sub-TLVs of TLV-38. 64 11.2 Mapping of TLV fields into SNMP tables . 66 11.3 TLV-38 and TLV-11 configuration example . 72 12 SNMPv2c management requirements 76 12.1 SNMPV2c coexistence mode tables c

22、ontent created by MTA after MTA4 for hybrid and basic flows 77 12.2 SNMP default entries for SNMPv2 access. 78 ITU-T Rec. J.167 (12/2007) v Page 13 Service interruption impact reporting and other enhanced features support 80 13.1 eDocsis requirements support. 80 13.2 IPCablecom extension MIB . 81 13

23、.3 Battery backup MIBs 81 13.4 Syslog MIBs . 81 13.5 Foreign potential detection. 81 Appendix I SNMPv2c coexistence configuration example Template for service providers . 82 ITU-T Rec. J.167 (12/2007) 1 ITU-T Recommendation J.167 Media terminal adapter (MTA) device provisioning requirements for the

24、delivery of real-time services over cable television networks using cable modems 1 Scope This Recommendation describes the IPCablecom media terminal adapter (MTA) device initialization and provisioning process. It is limited to the provisioning of an IPCablecom embedded-MTA device by a single provis

25、ioning and network management provider. NOTE The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T recommendations has not been applied. 2 References 2.1 Normative references The fol

26、lowing ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Rec

27、ommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does no

28、t give it, as a stand-alone document, the status of a Recommendation. ITU-T J.83 ITU-T Recommendation J.83 (2007), Digital multi-programme systems for television, sound and data services for cable distribution. ITU-T J.112.B ITU-T Recommendation J.112 Annex B (2004), Data-over-cable service interfac

29、e specifications: Radio-frequency interface specification. ITU-T J.162 ITU-T Recommendation J.162 (2007), Network call signalling protocol for the delivery of time-critical services over cable television networks using cable modems. ITU-T J.166 ITU-T Recommendation J.166 (2007), IPCablecom Managemen

30、t Information Base (MIB) framework. ITU-T J.170 ITU-T Recommendation J.170 (2005), IPCablecom security specification. IETF RFC 2131 IETF RFC 2131 (1997), Dynamic Host Configuration Protocol. IETF RFC 2132 IETF RFC 2132 (1997), DHCP Options and BOOTP Vendor Extensions. IETF RFC 2475 IETF RFC 2475 (19

31、98), An Architecture for Differentiated Services. IETF RFC 2616 IETF RFC 2616 (1999), Hypertext Transfer Protocol HTTP/1.1. IETF RFC 2833 IETF RFC 2833 (2000), RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals. IETF RFC 2863 IETF RFC 2863 (2000), The Interfaces Group MIB. IETF RFC 3

32、396 IETF RFC 3396 (2002), Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4). 2 ITU-T Rec. J.167 (12/2007) IETF RFC 3410 IETF RFC 3410 (2002), Introduction and Applicability Statements for Internet Standard Management Framework. IETF RFC 3411 IETF RFC 3411 (2002), An Architect

33、ure for Describing Simple Network Management Protocol (SNMP) Management Frameworks. IETF RFC 3412 IETF RFC 3412 (2002), Message Processing and Dispatching for the Simple Network Management Protocol (SNMP). IETF RFC 3413 IETF RFC 3413 (2002), Simple Network Management Protocol (SNMP) Applications. IE

34、TF RFC 3414 IETF RFC 3414 (2002), User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3). IETF RFC 3415 IETF RFC 3415 (2002), View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP). IETF RFC 3495 IETF RFC 3495 (2003), Dynami

35、c Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration. IETF RFC 3584 IETF RFC 3584 (2003), Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework. IETF RFC 3594 IETF RFC 3594 (2003), PacketCable Security Ticket Control S

36、ub-Option for the DHCP CableLabs Client Configuration (CCC) Option. IETF RFC 3617 IETF RFC 3617 (2003), Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP). 2.2 Informative references IETF RFC 3315 IETF RFC 3315 (2003), Dynamic Host Conf

37、iguration Protocol for IPv6 (DHCPv6). IETF RFC 4682 IETF RFC 4682 (2006), Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices. IETF RFC 5098 IETF RFC 5098 (2008), Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MT

38、As). IETF-draft-eventmess IETF Internet Draft, Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-compliant Devices, October 2006, http:/www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-eventmess-09.txt, work in progress. DOCSIS 3.0 Data-Over-Cable Service Interface

39、 Specifications, DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification, CM-SP-MULPIv3.0-I02-061222, June 12, 2006, Cable Television Laboratories, Inc. ITU-T J.222.2 ITU-T Recommendation J.222.2 (2007), Third-generation transmission systems for interactive cable television services IP cabl

40、e modems: MAC and upper layer protocols. CableLabs DHCP CableLabs DHCP Options Registry Specification, CL-SP-CANN-DHCP-Reg-I01-070119, January 19, 2007, Cable Television Laboratories, Inc. ITU-T Rec. J.167 (12/2007) 3 3 Terms and definitions This Recommendation defines the following terms: 3.1 cable

41、 modem: A cable modem is a layer-two termination device that terminates the customer end of the J.112 connection. 3.2 IPCablecom: An ITU-T project that includes an architecture and a series of Recommendations that enable the delivery of real-time services (such as telephony) over the cable televisio

42、n networks using cable modems. 4 Abbreviations and conventions 4.1 Abbreviations This Recommendation uses the following abbreviations: CM Cable Modem CMS Call Management Server CPE Customer Premises Equipment DHCP Dynamic Host Configuration Protocol DNS Domain Name System FQDN Fully Qualified Domain

43、 Name HTTP HyperText Transfer Protocol IP Internet Protocol IPSec Internet Protocol Security MAC Media Access Control MTA Media Terminal Adapter PSTN Public Switched Telephone Network SNMP Simple Network Management Protocol TFTP Trivial File Transfer Protocol TGS Ticket Granting Server 4.2 Conventio

44、ns It is understood that implementing this Recommendation is optional. If this Recommendation is implemented, the key words “MUST“ and “SHALL“ as well as “REQUIRED“ are to be interpreted as indicating a mandatory aspect of this Recommendation. The key words indicating a certain level of significance

45、 of particular requirements that are used throughout this Recommendation are summarized below: “MUST“ This word or the adjective “REQUIRED“ means that the item is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item is an absolute prohibition of this Recommendat

46、ion. “SHOULD“ This word or the adjective “RECOMMENDED“ means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course. 4 ITU-T Rec. J.167 (12/2007) “SHOULD NOT“

47、 This phrase means that there may exist valid reasons in particular circumstances when the listed behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label. “MAY“ This word or the

48、adjective “OPTIONAL“ means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product; for example, another vendor may omit the same item. 5 Introduction 5.1 Service goals Cable operators are interested

49、in deploying high-speed data communications systems on cable television networks. The intended service enables voice communications, video and data services based on bidirectional transfer of Internet Protocol (IP) traffic, between the cable system headend and customer locations, over an all-coaxial or hybrid-fibre/coax (HFC) cable network, defined by DOCSIS Recommendations. This is shown in simplified form in Figure 1. NOTE The term “DOCSIS“ in this Recommendation is understood to refer to DOCSIS version 1.1 (ITU-T