1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.827.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (10/2004) SERIES Q: SWITCHING AND SIGNALLING Q3 interface Requirements and analysis for the common management functions of NMS-EMS interfaces ITU-T Recommendation Q.827.1 ITU-T Q-SERIES RECOMMENDATION
2、S 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 SPECIFICATIONS OF SIGNALLING SYSTEMS N
3、o. 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 NETWORK Q.1000Q.1099 INTERWORKING WITH SAT
4、ELLITE 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 For further details, please refer to the list of
5、 ITU-T Recommendations. ITU-T Rec. Q.827.1 (10/2004) i ITU-T Recommendation Q.827.1 Requirements and analysis for the common management functions of NMS-EMS interfaces Summary This Recommendation provides the requirements and analysis for the common management functions for NMS-EMS interface which c
6、an be used for network technology-specific management interfaces. The requirements and analysis for the management interface between EMS and NMS are provided using the TMN interface specification methodology described in ITU-T Rec. M.3020. Source ITU-T Recommendation Q.827.1 was approved on 7 Octobe
7、r 2004 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. Keywords Common management, Unified Modelling Language (UML). ii ITU-T Rec. Q.827.1 (10/2004) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of tele
8、communications. 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 basis. The World Teleco
9、mmunication 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 Resolution 1. In some are
10、as 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 and a recognized ope
11、rating 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 met. The words “shall
12、“ 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 possibility that the prac
13、tice 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 Recommendation develo
14、pment 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, implementors are cautioned that this may not represent the latest information and are therefo
15、re strongly urged to consult the TSB patent database. ITU 2005 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.827.1 (10/2004) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions .
16、2 4 Abbreviations 2 5 General overview 3 6 Requirements 3 6.1 Business level requirements . 3 6.2 Specification level requirements 8 7 Analysis 26 7.1 Conventions 26 7.2 Common management function set 26 7.3 Performance management function set 57 7.4 Fault management function set. 72 7.5 Security ma
17、nagement function set 80 Appendix I Table of managed entities 80 ITU-T Rec. Q.827.1 (10/2004) 1 ITU-T Recommendation Q.827.1 Requirements and analysis for the common management functions of NMS-EMS interfaces 1 Scope This Recommendation provides the requirements and analysis of common management fun
18、ctions applicable at NMS-EMS interface. The term “common“ is used in two different contexts. In the first context, it includes analysis of the requirements that are applicable for fault, performance, configuration and security management functions. The second usage is to analyse the requirements tha
19、t are independent of the specific technology. An example of the first context is logging events for alarms, performance threshold crossing, and inventory changes to the data of the entities. An example of the second context is the method for collecting and reporting performance measurements independ
20、ent of the network technologies, such as EPON or SDH-DLC. This Recommendation follows the interface specification methodology described in ITU-T Rec. M.3020 2. In this Recommendation, the Element Management System (EMS) is an Operation System (OS) 1 used to manage the individual network elements sup
21、porting specific network technologies as well as the networks between them. One or more systems may be required depending on the different supplier products and geographic distribution of the elements in the network. The Network Management System (NMS) represents an integrated management OS across d
22、ifferent technology and supplier systems. The management functions covered in this Recommendation include common management, performance management, fault management and security management. Configuration management and performance parameters are network technology-dependent, and they will be addres
23、sed in other technology-specific Recommendations. Security management is for future study. These management functions are described and divided by UML use cases in the requirements. The analysis provides the managed entities that support a protocol-neutral information model for common management fun
24、ctions, and also explains the static and dynamic relationships between these managed entities using UML class diagrams and sequence diagrams. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this
25、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 edition of the Recommendations and other r
26、eferences 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. 1 ITU-T Recommendation M.3010 (2000), Principles for a telecommunica
27、tion management network. 2 ITU-T Recommendation M.3020 (2000), TMN interface specification methodology. 3 ITU-T Recommendation M.3100 (1995), Generic network information model. 4 ITU-T Recommendation M.3200 (1997), TMN management services and telecommunications managed areas: overview. 5 ITU-T Recom
28、mendation M.3400 (2000), TMN management functions. 2 ITU-T Rec. Q.827.1 (10/2004) 6 ITU-T Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, Information technology Open Systems Interconnection Structure of management information: Management information model. 7 ITU-T Recommendation X.721 (1992) | I
29、SO/IEC 10165-2:1992, Information technology Open Systems Interconnection Structure of management information: Definition of management information. 8 ITU-T Recommendation X.731 (1992) | ISO/IEC 10164-2:1993, Information technology Open Systems Interconnection Systems Management: State management fun
30、ction. 9 ITU-T Recommendation X.733 (1992) | ISO/IEC 10164-4:1992, Information technology Open Systems Interconnection Systems Management: Alarm reporting function. 10 ITU-T Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, Information technology Open Systems Interconnection Systems Management: Ev
31、ent report management function. 11 ITU-T Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, Information technology Open Systems Interconnection Systems Management: Log control function. 12 ITU-T Recommendation X.739 (1993) | ISO/IEC 10164-11:1994, Information technology Open Systems Interconnection
32、 Systems Management: Metric objects and attributes. 13 ITU-T Recommendation X.792 (1999), Configuration audit support function for ITU-T applications. 3 Terms and definitions No new definitions are needed in this Recommendation. 4 Abbreviations This Recommendation uses the following abbreviations: A
33、SAP Alarm Severity Assignment Profile CM Configuration Management CMIP Common Management Information Protocol CORBA Common Object Request Broker Architecture EFD Event Forwarding Discriminator EMS Element Management System EPON Ethernet Passive Optical Network FM Fault Management FS Function Set FTP
34、 File Transfer Protocol ID Identifier ITU-T International Telecommunication Union Telecommunication Standardization Sector MO Managed Object NMS Network Management System OS Operations System PM Performance Management ITU-T Rec. Q.827.1 (10/2004) 3 QoS Quality of Service SDH-DLC Synchronous Digital
35、Hierarchy Digital Loop Carrier TMN Telecommunications Management Network UML Unified Modelling Language 5 General overview The EMS shown in Figure 5-1 is used to manage the individual network elements supporting some specific network technologies. One or more systems may be required depending on the
36、 different supplier products and geographic distribution of the elements in the network. NMS, the network layer management system shown in Figure 5-1, represents an integrated management OS across the different technology and supplier systems. The logical representation shown by NMS may be realized
37、by one or more physical interfaces. Figure 5-1 shows the Q interface addressed in this Recommendation. Q.827.1_F5-1Network Management SystemsElement Management SystemNetwork ElementsQFigure 5-1/Q.827.1 Reference interface 6 Requirements 6.1 Business level requirements This Recommendation only focuse
38、s on the management interface between NMS and EMS and the interface management functions associated with them. Through the interface, NMS can query and modify configuration information, and EMS should report changes in configuration, performance data, and fault information to NMS. 6.1.1 Actor roles
39、The actor in this Recommendation is NMS. NMS is the network management system that manages the whole network system by interacting with suppliers EMSs. 6.1.2 Telecommunications resources Both the suppliers EMSs and the managed network equipments are viewed as relevant telecommunications resources in
40、 this Recommendation. 6.1.3 High-level use-case diagrams This clause contains the high-level UML use-case diagrams that summarize the functionalities and interfaces of EMS. 4 ITU-T Rec. Q.827.1 (10/2004) The first overview use-case diagram (Figure 6-1) shows the main management function sets (FS) in
41、volved in the NMS-EMS management interface. Q.827.1_F6-1Configuration management FSPerformance management FSSecurity management FSFault management FSCommon management FSManagement interface FS NMSFigure 6-1/Q.827.1 NMS-EMS management interface function set The following four use-case diagrams (Figur
42、es 6-2 to 6-5) show the common management function sets, which are: Common management function set overview (Figure 6-2), Notification management function set (Figure 6-3), Log management function set (Figure 6-4), and Bulk data transfer control function set (Figure 6-5). Q.827.1_F6-2Notification ma
43、nagement FS Bulk data transfer control FSLog management FSCommon management FS NMSFigure 6-2/Q.827.1 Common management function set overview ITU-T Rec. Q.827.1 (10/2004) 5 Figure 6-3/Q.827.1 Notification management function set Q.827.1_F6-4Create logDelete logSuspend log Resume logQuery logModify lo
44、gDelete log recordsLog management FSNMSQuery log recordsLog object management FSLog record management FSFigure 6-4/Q.827.1 Log management function set 6 ITU-T Rec. Q.827.1 (10/2004) Q.827.1_F6-5Request file preparationTransfer files Confirm file receivedBulk data transfer control FSNMSNotification r
45、eportReport file infoFigure 6-5/Q.827.1 Bulk data transfer control function set Configuration management function set is network technology dependent, so it will not be addressed in this Recommendation. The following three diagrams show the functions involved in the performance management function s
46、et. Figure 6-6 illustrates performance management function set, Figure 6-7 is the performance measurement management function set use-case diagram, and Figure 6-8 is the threshold management function set use-case diagram. Figure 6-6/Q.827.1 Performance management function set ITU-T Rec. Q.827.1 (10/
47、2004) 7 Q.827.1_F6-7Create measurement jobDelete measurement jobSuspend measurement jobResume measurement jobQuery measurement jobPerformance data reportBulk data transfer control FSPerformance measurement management FSNMSStop measurement jobFigure 6-7/Q.827.1 Performance measurement management func
48、tion set Figure 6-8/Q.827.1 Performance threshold management function set The following two use-case diagrams (Figures 6-9 and 6-10) show the functions involved in fault management function set. 8 ITU-T Rec. Q.827.1 (10/2004) Figure 6-9/Q.827.1 Fault management function set Figure 6-10/Q.827.1 ASAP
49、management function set 6.2 Specification level requirements This clause contains textual details for each of the use cases shown in the high-level use-case diagrams of the previous clause. The details are provided to clarify the roles of external actors and telecommunications resources, to establish the basis for interactive diagrams in the analysis part, and to refine the previous high-level use-case diagrams to a specification level. Use-case details include the following components:
