ITU-T Q 840 1-2007 Requirements and analysis for NMS-EMS management interface of Ethernet over Transport and Metro Ethernet Network (EoT MEN) (Study Group 4)《(预发布)以太无源光网络(EPON)管理接口.pdf

1、 International Telecommunication Union ITU-T Q.840.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2007) SERIES Q: SWITCHING AND SIGNALLING Q3 interface Requirements and analysis for NMS-EMS management interface of Ethernet over Transport and Metro Ethernet Network (EoT/MEN) ITU-T Recommendatio

2、n Q.840.1 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119

3、 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NET

4、WORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLIN

5、G REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.840.1 (03/2007) i ITU-T Recommendation Q.840.1 Requirements and analysis for NMS-EMS management interface of Ethernet over Transport and Metro Ethernet Network (

6、EoT/MEN) Summary ITU-T Recommendation Q.840.1 covers the management of Ethernet over Transport (EoT) and Metro Ethernet Network (MEN). In this Recommendation, the Element Management System (EMS) is an Operations System (OS) used to manage the individual NEs in a network. One or more systems may be r

7、equired depending on the different supplier products and geographic distribution of the elements in the network. The goal of these systems is to manage elemental layer (NE view) information specific to the network element. The Network Management System (NMS) represents an integrated management OS ac

8、ross the different network technology and EMSs. An NMS communicates with an EMS through the Q Interface to realize its management functions. The functional requirements for the management interface between EoT/MEN EMS and NMS for the integrated management at the network layer and at the element laye

9、r are provided in this Recommendation. Source ITU-T Recommendation Q.840.1 was approved on 16 March 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Q.840.1 (03/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations spe

10、cialized agency in the field of telecommunications. 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

11、 a worldwide basis. 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 do

12、wn in WTSA Resolution 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

13、 administration and 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

14、provisions are met. 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 attent

15、ion to the possibility 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

16、outside of the Recommendation 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 th

17、e latest information 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. Q.840.1 (03/2007) ii

18、i CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions . 3 3.1 Definitions imported from ITU-T G.805. 3 3.2 Definitions imported from ITU-T G.809. 3 3.3 Definitions imported from ITU-T G.8010. 3 3.4 Definitions imported from ITU-T G.8011. 3 3.5 Definitions imported from MEF 10.1 4 4 Abbre

19、viations and acronyms 4 5 General overview 6 5.1 Network Element view concepts 9 5.2 Network View concepts . 10 5.3 Service View concepts MEF 10.1 13 6 Interface requirements 14 6.1 Business level requirements . 14 6.2 Specification level requirements 17 7 Analysis 52 7.1 Conventions 52 7.2 Common M

20、anagement Function Set 53 7.3 Configuration Management Function Set 53 7.4 Performance Management Function Set 86 7.5 Fault Management Function Set. 90 Appendix I Table of managed entities 91 Appendix II Examples for the combined use of ETHServiceClassProfile, ETHBandwidthProfile and ETHPerformanceP

21、rofile . 92 Appendix III Informational: State Management Mapping . 93 Bibliography 94 ITU-T Rec. Q.840.1 (03/2007) 1 ITU-T Recommendation Q.840.1 Requirements and analysis for NMS-EMS management interface of Ethernet over Transport and Metro Ethernet Network (EoT/MEN) 1 Scope This Recommendation spe

22、cifies the requirements and analysis for the management interface between the Element Management System (EMS) and the Network Management System (NMS) of Metro Ethernet as defined in MEF-10 and Ethernet over Transport (EoT), specifically the Ethernet ETH layer as defined in ITU-T G.8010. This Recomme

23、ndation follows the interface specification methodology described in ITU-T M.3020. In this Recommendation, the EMS is an Operations System (OS) used to manage the individual network elements supporting Metro Ethernet and EoT services as well as the networks between them. One or more EMSs may be depl

24、oyed depending on the different supplier products and geographic distribution of the network elements in the network. The NMS represents an integrated management OS across different technologies and EMSs. The NMS communicates with EMS through the Q Interface to realize its management functions. The

25、management functions covered in this Recommendation include configuration management, performance measurement parameters management, and alarm reporting and testing in fault management. These management functions are described and divided by UML use cases in the requirements. The analysis provides t

26、he managed entities which support a protocol-neutral information model for Metro Ethernet and EoT management, and also explains the static and dynamic relationships between these managed entities using UML class diagrams and sequence diagrams. This Recommendation does not cover all aspects about Eth

27、ernet management; only those related to Metro Ethernet and EoT services management are addressed. This Recommendation is built on and extends the information model provided in MEF 7. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in

28、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 to investigate the possibility of applying the most recent e

29、dition 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, the status of a Recommendation. MEF 4 Metro Ethernet Forum,

30、 Technical Specification MEF 4 (2004), MEF Architecture Framework Part 1: Generic Framework. MEF 6 Metro Ethernet Forum, Technical Specification MEF 6 (2004), Ethernet Services Definitions Phase I. MEF 7 Metro Ethernet Forum, Technical Specification MEF 7 (2004), EMS-NMS Information Model. MEF 10.1

31、Metro Ethernet Forum, Technical Specification MEF 10.1 (2006), Ethernet Service Attributes Phase 2. MEF 11 Metro Ethernet Forum, Technical Specification MEF 11 (2004), User Network Interface (UNI) Requirements and Framework. 2 ITU-T Rec. Q.840.1 (03/2007) MEF 12 Metro Ethernet Forum, Technical Speci

32、fication MEF 12 (2005), Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer. MEF 13 Metro Ethernet Forum, Technical Specification MEF 13 (2005), User Network Interface (UNI) Type 1 Implementation Agreement. MEF 15 Metro Ethernet Forum Technical Specification MEF 15 (2005),

33、Requirements for Management of Metro Ethernet Phase 1 Network Elements. MEF 16 Metro Ethernet Forum, Technical Specification MEF 16 (2006), Ethernet Local Management Interface (E-LMI). ITU-T G.805 ITU-T Recommendation G.805 (2000), Generic functional architecture of transport networks. ITU-T G.809 I

34、TU-T Recommendation G.809 (2003), Functional architecture of connectionless layer networks. ITU-T G.8010 ITU-T Recommendation G.8010/Y.1306 (2004), Architecture of Ethernet layer networks. ITU-T G.8011 ITU-T Recommendation G.8011/Y.1307 (2004), Ethernet over Transport Ethernet services framework. IT

35、U-T G.8011.1 ITU-T Recommendation G.8011.1/Y.1307.1 (2004), Ethernet private line service. ITU-T G.8011.2 ITU-T Recommendation G.8011.2/Y.1307.2 (2005), Ethernet virtual private line service. ITU-T G.8012 ITU-T Recommendation G.8012/Y.1308 (2004), Ethernet UNI and Ethernet NNI. ITU-T M.3020 ITU-T Re

36、commendation M.3020 (2007), Management interface specification methodology. ITU-T M.3100 ITU-T Recommendation M.3100 (2005), Generic network information model. ITU-T Q.827.1 ITU-T Recommendation Q.827.1 (2004), Requirements and analysis for the common management functions of NMS-EMS interfaces plus

37、Amendment 1 (2007), Addition of a common managed entity EMS. ITU-T X.731 ITU-T Recommendation X.731 (1992), Information technology Open Systems Interconnection Systems Management: State management function. IEEE 802-3 IEEE 802.3 (2002), IEEE Standard for Information technology Telecommunications and

38、 information exchange between systems Local and metropolitan area networks Specific requirements Part 3: Carrier sense multiple access with collision detection (CSMA/CD) Access Method and Physical Layer Specifications. IEEE 802.1Q IEEE 802.1Q (2005), IEEE Standard for Local and Metropolitan Area Net

39、works: Virtual Bridged Local Area Networks. IEEE 802.1X IEEE 802.1X (2004), IEEE Standard for Local and Metropolitan Area Networks: Port-Based Network Access Control. IETF RFC 2863 IETF RFC 2863 (2000), The Interfaces Group MIB. IETF RFC 3635 IETF RFC 3635 (2003), Definitions of Managed Objects for

40、the Ethernet-like Interface Types. IETF RFC 3636 IETF RFC 3636 (2003), Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs). ITU-T Rec. Q.840.1 (03/2007) 3 3 Terms and definitions This Recommendation uses the following terms. 3.1 Definitions imported from ITU-T G.805 The foll

41、owing terms from ITU-T G.805 are used in this Recommendation: Connection; Connection point; Link; Termination connection point; Trail; Trail termination. 3.2 Definitions imported from ITU-T G.809 The following terms from ITU-T G.809 are used in this Recommendation: Adaptation; Characteristic informa

42、tion; Client/server relationship; Connectionless trail; Flow; Flow domain; Flow domain flow; Flow point; Flow point pool; Flow point pool link; Flow termination; Layer network; Link flow; Port; Transport. 3.3 Definitions imported from ITU-T G.8010 The following terms from ITU-T G.8010 are used in th

43、is Recommendation: ETH Link; Traffic Conditioning Function; Flow Domain Fragment. 3.4 Definitions imported from ITU-T G.8011 The following terms from ITU-T G.8011 are used in this Recommendation: Committed Information Rate (CIR); Ethernet Private Line (EPL); Ethernet Virtual Private Line (EVPL); 4 I

44、TU-T Rec. Q.840.1 (03/2007) Ethernet Private LAN (EPLAN); Ethernet Virtual Private LAN (EVPLAN). 3.5 Definitions imported from MEF 10.1 The following terms from MEF 10.1 are used in this Recommendation: Bandwidth Profile: Also defined in ITU-T G.8011; Broadcast Service Frame; CE-VLAN ID Preservation

45、; CE-VLAN ID/EVC Map; Class of Service (CoS): Also defined in ITU-T G.8011; Color-aware; Color-blind; Committed Burst Size (CBS): Also defined in ITU-T G.8011; Committed Information Rate (CIR): Also defined in ITU-T G.8011; Customer Edge (CE); Ethernet Virtual Connection (EVC); Excess Burst Size (EB

46、S): Also defined in ITU-T G.8011; Excess Information Rate (EIR): Also defined in ITU-T G.8011; Frame; Ingress Frame; Metro Ethernet Network (MEN); Multicast Service Frame; Point-to-Point EVC; Service Frame; Service Multiplexing; Service Provider; Unicast Service Frame; User Network Interface: Also d

47、efined in ITU-T G.8012. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations: ASAP Alarm Severity Assignment Profile AVC Attribute Value Change BER Bit Error Rate CBS Committed Burst Size CE Customer Edge CES Circuit Emulation Service CI Characteristic Information CIR Co

48、mmitted Information Rate CM Configuration Management ITU-T Rec. Q.840.1 (03/2007) 5 CoS Class of Service CRC Cyclic Redundancy Check CTP Connection Termination Point EBS Excess Burst Size EIR Excess Information Rate ELMI Ethernet Local Management Interface EMS Element Management System EoT Ethernet

49、over Transport ETH Ethernet MAC layer network ETYn Ethernet physical layer network of order n FCS Frame Check Sequence FD Flow Domain FDFr Flow Domain Fragment FDX Full Duplex FE Fast Ethernet FM Fault Management FP Flow Point FPP Flow Point Pool FS Function Set FTP Flow Termination Point GE Gigabit Ethernet GFP Generic Framing Procedure HDLC