ITU-T J 166-2007 IPCablecom Management Information Base (MIB) framework (Study Group 9)《IPCablecom管理信息基础(MIB)框架》.pdf

1、 International Telecommunication Union ITU-T J.166TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2007) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom Management Information Base (MIB) framework ITU-T Recommendation J.1

2、66 ITU-T Rec. J.166 (12/2007) i ITU-T Recommendation J.166 IPCablecom Management Information Base (MIB) framework Summary ITU-T Recommendation J.166 describes the framework in which IPCablecom MIBs (management information base) are defined. It provides information on the management requirements of I

3、PCablecom-specified devices and functions and how these requirements are supported in the MIB. It is intended to support and complement the actual MIB Recommendations, which are included as annexes. Source ITU-T Recommendation J.166 was approved on 14 December 2007 by ITU-T Study Group 9 (2005-2008)

4、 under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. J.166 (12/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardizat

5、ion 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 basis. The World Telecommunication Standardization Assembly (WTSA), which mee

6、ts 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 Resolution 1. In some areas of information technology which fall within ITU-Ts

7、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 and a recognized operating agency. Compliance with this Recommendation is

8、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 met. The words “shall“ or some other obligatory language such as “must“ and

9、 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 possibility that the practice or implementation of this Recommendation may invo

10、lve 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 Recommendation development process. As of the date of approval of this Reco

11、mmendation, 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 information and are therefore strongly urged to consult the TSB patent database a

12、t 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.166 (12/2007) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative references 1 2.2 Informative referen

13、ces 2 3 Terms and definitions . 2 4 Abbreviations and conventions. 3 4.1 Abbreviations . 3 4.2 Conventions 3 5 Overview 4 5.1 IPCablecom reference architecture. 4 5.2 General requirements 4 5.3 Functional requirements . 8 6 MIBs available in an IPCablecom network 9 6.1 DOCSIS MIB modules. 10 6.2 IF

14、MIB 10 6.3 MIB II. 10 6.4 Ethernet MIB 13 6.5 Annex C 13 6.6 Annex B 13 6.7 Event Management MIB 13 6.8 SNMP MIB. 14 6.9 IPCablecom Extension MIB. 14 6.10 eDOCSIS eSAFE MIB. 14 6.11 Battery backup UPS MIB. 14 7 IPCablecom MIB module implementation. 14 7.1 MTA components. 14 7.2 MIB layering 15 8 Org

15、anization of the MIBs . 16 8.1 Definition MIB . 16 8.2 MTA MIB. 16 8.3 Signalling MIB . 17 8.4 MEM MIB 17 8.5 MTA Extension MIB 17 8.6 Signalling Extension MIB 17 8.7 Battery backup MIB . 17 Annex A MIB import data 18 Annex B MTA MIB 24 iv ITU-T Rec. J.166 (12/2007) Page Annex C Network call signall

16、ing MIB . 53 Annex D Management Event MIB . 76 Annex E Extension MTA MIB . 88 Annex F Signalling Extension MIB 90 ITU-T Rec. J.166 (12/2007) 1 ITU-T Recommendation J.166 IPCablecom Management Information Base (MIB) framework 1 Scope This Recommendation describes the framework in which IPCablecom MIB

17、s (management information base) are defined. It provides information on the management requirements of IPCablecom-specified devices and functions and how these requirements are supported in the MIB. It is intended to support and complement the actual MIB Recommendations, which are included as annexe

18、s. 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 following ITU-T Recommendations and othe

19、r 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 Recommendation are therefore encouraged

20、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 not give it, as a stand-alone document,

21、 the status of a Recommendation. ITU-T J.112-A ITU-T Recommendation J.112 Annex A (2001), Digital Video Broadcasting: DVB interaction channel for cable TV (CATV) distribution systems. ITU-T J.112-B ITU-T Recommendation J.112 Annex B (2004), Data-over-cable service interface specifications: Radio-fre

22、quency 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.167 ITU-T Recommendation J.167 (2007), Media terminal adapter (MTA) device provisionin

23、g requirements for the delivery of real-time services over cable television networks using cable modems. ITU-T J.170 ITU-T Recommendation J.170 (2005), IPCablecom security specification. ITU-T J.176 ITU-T Recommendation J.176 (2002), IPCablecom management event mechanism MIB. ITU-T J.199 ITU-T Recom

24、mendation J.199 (2006), Battery backup for cable based devices. IETF RFC 1907 IETF RFC 1907 (1996), Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2). IETF RFC 2011 IETF RFC 2011 (1996), SNMPv2 Management Information Base for the Internet Protocol using SMI

25、v2. IETF RFC 2013 IETF RFC 2013 (1996), SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2. 2 ITU-T Rec. J.166 (12/2007) IETF RFC 2578 IETF RFC 2578 (1999), Structure of Management Information Version 2 (SMIv2). IETF RFC 2579 IETF RFC 2579 (1999), Textual Conventions for S

26、MIv2. IETF RFC 2863 IETF RFC 2863 (2000), The Interfaces Group MIB. ANSI/SCTE 23-3 ANSI/SCTE 23-3 (2005), DOCSIS 1.1 Part 3: Operations Support System Interface. ANSI/SCTE 79-2 ANSI/SCTE 79-2 (2002), DOCS 2.0 Operations Support System Interface. 2.2 Informative references ITU-T J.160 ITU-T Recommend

27、ation J.160 (2005), Architectural framework for the delivery of time-critical services over cable television networks using cable modems. IETF RFC 1493 IETF RFC 1493 (1993), Definitions of Managed Objects for Bridges. IETF RFC 1643 IETF RFC 1643 (1994), Definitions of Managed Objects for the Etherne

28、t-like Interface Types. IETF RFC 2571 IETF RFC 2571 (1999), An Architecture for Describing SNMP Management Frameworks. IETF RFC 2572 IETF RFC 2572 (1999), Message Processing and Dispatching for the Simple Network Management Protocol (SNMP). IETF RFC 2573 IETF RFC 2573 (1999), SNMP Applications. IETF

29、 RFC 2574 IETF RFC 2574 (1999), User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3). IETF RFC 2575 IETF RFC 2575 (1999), View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP). IETF RFC 4293 IETF RFC 4293 (2006), Manageme

30、nt Information Base for the Internet Protocol (IP). 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 Termina

31、l Adapters (MTAs). CM-SP-OSSIv3.0 Data-Over-Cable Service Interface Specifications, DOCSIS 3.0, Operations Support System Interface Specification, CM-SP-OSSIv3.0-I01-061207, December 7, 2006, Cable Television Laboratories, Inc. draft-ietf-ipcdn-pktc- IETF Internet Draft, Management Event Management

32、Information Base eventmess-09 (MIB) for PacketCable- and IPCablecom-Compliant Devices, (draft-ietf-ipcdn-pktc-eventmess-09), October 2006. 3 Terms and definitions This Recommendation defines the following terms: 3.1 cable modem: A cable modem is a layer-two termination device that terminates the cus

33、tomer end of the ITU-T J.112/J.122 connection. ITU-T Rec. J.166 (12/2007) 3 3.2 IPCablecom: An ITU-T project that includes an architecture and a series of Recommendations that enable the delivery of real-time services over the cable television networks using cable modems. 3.3 management information

34、base (MIB): The specification of information in a manner that allows standard access through a network management protocol. 3.4 media terminal adapter (MTA): Contains the interface to a physical voice device, a network interface, CODECs, and all signalling and encapsulation functions required for Vo

35、IP transport, class features signalling and QoS signalling. 3.5 quality of service (QoS): Guarantees network bandwidth and availability for applications. 4 Abbreviations and conventions 4.1 Abbreviations This Recommendation uses the following abbreviations: CM Cable Modem MIB Management Information

36、Base MTA Media Terminal Adapter NCS Network Call Signalling QoS Quality of Service 4.2 Conventions Throughout this Recommendation, the words that are used to define the significance of particular requirements are capitalized. These words are: “MUST“ This word or the adjective “REQUIRED“ means that t

37、he item is an absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item is an absolute prohibition of this Recommendation. “SHOULD“ This word or the adjective “RECOMMENDED“ means that there may exist valid reasons in particular circumstances to ignore this item, but the

38、 full implications should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT“ 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 underst

39、ood and the case carefully weighed before implementing any behaviour described with this label. “MAY“ This word or the 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 produc

40、t, for example; another vendor may omit the same. 4 ITU-T Rec. J.166 (12/2007) 5 Overview IPCablecom MIB modules are designed to provide necessary functionality defined in IPCablecom Recommendations. MIBs that are developed for IPCablecom support embedded media terminal adapters (MTAs) and in most c

41、ases stand-alone MTAs and provide definitions for call signalling and MTA device provisioning functions. Future IPCablecom development phases will include other functional areas as well as requirements for other IPCablecom components, which will be considered for MIB module development. IPCablecom f

42、unctional areas that are being studied for future IPCablecom MIB definition include ITU-T Rec. J.161, ITU-T J.162, ITU-T J.167, ITU-T J.170 and ITU-T J.176. Additionally, in this specification, the term “DOCSIS“ is used to refer to DOCSIS version 1.1 ITU-T J.112, DOCSIS version 2 (ITU-T Rec. J.122)

43、or DOCSIS version 3 (ITU-T Recs J.21x and J.22x series), unless explicitly specified otherwise. 5.1 IPCablecom reference architecture The conceptual diagram for the IPCablecom architecture is shown in Figure 1. Please refer to ITU-T J.160 for more detailed information concerning the IPCablecom archi

44、tecture. Figure 1 IPCablecom network component reference model (partial) 5.2 General requirements The IPCablecom MIBs Framework Recommendation follows the Internet Standard Management Framework described in IETF RFC 3410. Additionally, the following requirements have been considered in the design of

45、 IPCablecom MIB modules: IPCablecom devices MUST be compliant with DOCSIS; Therefore, IPCablecom devices must support DOCSIS MIBs as defined in clause 6.1; take a minimalist approach for design of the IPCablecom MIB modules, i.e., if other MIB modules define the same functions, then rely on these MI

46、B modules rather than create new ones; organize MIB modules to support both embedded and stand-alone MTAs; organize MIB modules so as to allow functional partitioning of ITU-T Rec. J.112/J.122 (high-speed data) and IPCablecom (voice features); DOCSIS within IPCablecom applications requires support o

47、f SNMPv3; therefore IPCablecom MIB agents MUST comply with SNMPv3; ITU-T Rec. J.166 (12/2007) 5 IPCablecom MIBs MUST comply with SMIv2 as defined in IETF STD 58. 5.2.1 Provisioning and network management service provider A single physical device (e.g., embedded-MTA) will be completely provisioned an

48、d managed by a single business entity. In the case of multiple service providers offering different services on the same device (e.g., data by one provider, voice by another provider), a secondary service provider will act as the “contractor“ for the primary provider in the areas of device provision

49、ing and management. See Figure 2. Figure 2 Partitioning of management domains 5.2.2 Support for embedded and stand-alone MTAs The IPCablecom MIBs will provide features for both embedded and stand-alone MTAs. Since stand-alone MTAs are not required to include any CM related functions, the IPCablecom MIBs, therefore, should be independent of CM and able to provide management support for voice communications functionalities. Cable modems with embedded MTAs must adhere to the DOCSIS or eDOCSI