1、 International Telecommunication Union ITU-T M.3102TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2011) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Unified generic management information model for connection-oriented and co
2、nnectionless networks Recommendation ITU-T M.3102 ITU-T M-SERIES RECOMMENDATIONS TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International t
3、elephone circuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1
4、100M.1199 International public telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599Integrated services digital networks M.
5、3600M.3999 Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3102 (01/2011) i Recommendation ITU-T M.3102 Unified generic management information model for connection-oriented and connectionless networks Summary Recomme
6、ndation ITU-T M.3102 provides a management information model for unified connection-oriented and connectionless networks, based on the unified functional architecture of transport networks specified in Recommendation ITU-T G.800. This model describes information object classes (IOCs) and their prope
7、rties that are generic and useful to describe information exchanged across all interfaces defined in Recommendation ITU-T M.3010, TMN architecture. These generic information object classes are intended to be applicable across different technologies, architecture and services. The information object
8、classes in this Recommendation may be specialized to support the management of various telecommunications networks. This Recommendation follows Recommendation ITU-T M.3020, management interface specification methodology on the analysis phase. The information models provided in this Recommendation ar
9、e in a protocol-neutral manner, and can be mapped to multiple protocol-specific information models (design phase). History Edition Recommendation Approval Study Group 1.0 ITU-T M.3102 2011-01-13 2 Keywords Connectionless network, connection-oriented network, unified information model. ii Rec. ITU-T
10、M.3102 (01/2011) 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 Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is res
11、ponsible 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 meets every four years, establishes the topics for study by the
12、 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 purview, the necessary standards are prepared on a collabora
13、tive 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 voluntary. However, the Recommendation may contain certain m
14、andatory 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 the negative equivalents are used to express requirements
15、. 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 involve the use of a claimed Intellectual Property Right. ITU
16、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 Recommendation, ITU had not received notice of intellectual pr
17、operty, 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 at http:/www.itu.int/ITU-T/ipr/. ITU 2011 All rights reserv
18、ed. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T M.3102 (01/2011) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbre
19、viations 2 5 Conventions 3 6 Information object classes 3 6.1 Imported information entities and local labels . 3 6.2 Class diagrams 3 6.3 Information object class definitions . 19 6.4 Information relationship definitions . 40 7 Common information definitions . 58 7.1 Attributes 58 7.2 Notifications
20、. 67 Appendix I Relationship between IOCs and functional architecture entities . 68 Appendix II Relationship between IOCs from ITU-T M.3160 and this Recommendation 70 Bibliography. 72 Rec. ITU-T M.3102 (01/2011) 1 Recommendation ITU-T M.3102 Unified generic management information model for connectio
21、n-oriented and connectionless networks 1 Scope This Recommendation provides a unified management information model for both connection-oriented and connectionless networks. The information model is based on the unified functional architecture of transport network specified in ITU-T G.800. It is the
22、scope of this Recommendation to define the following: the entities representing the abstraction of resources in unified connection-oriented and connectionless transport networks; the attributes of these entities; and the relationship among these entities, including the entities at the same layer and
23、 at different layers. The above entities are defined in a protocol- and technology-neutral way, which is based on the methodology specified in ITU-T M.3020. But the management interactions are not the purpose of this Recommendation. It is outside the scope of this Recommendation to define the intera
24、ctions across the management interface. 2 References The following 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
25、 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 references listed below. A list of the currently valid ITU-T Recommendations is regularly published. Th
26、e reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T G.800 Recommendation ITU-T G.800 (2007), Unified functional architecture of transport networks. ITU-T G.805 Recommendation ITU-T G.805 (2000), Generic functional ar
27、chitecture of transport networks. ITU-T G.809 Recommendation ITU-T G.809 (2003), Functional architecture of connectionless layer networks. ITU-T M.3020 Recommendation ITU-T M.3020 (2010), Management interface specification methodology. ITU-T M.3100 Recommendation ITU-T M.3100 (2005), Generic network
28、 information model. ITU-T M.3160 Recommendation ITU-T M.3160 (2008), Generic, protocol-neutral management information model. ITU-T M.3701 Recommendation ITU-T M.3701 (2010), Common management services State management Protocol neutral requirements and analysis. 2 Rec. ITU-T M.3102 (01/2011) 3 Defini
29、tions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 information object class ITU-T M.3020 3.1.2 information type ITU-T M.3020 3.1.3 managed entity ITU-T M.3100 3.1.4 management interface ITU-T M.3100 3.2 Terms defined in this Recommendation This Re
30、commendation has no new definitions. 4 Abbreviations This Recommendation uses the following abbreviations: Ac Access Abs Abstract AP Access Point CL Connectionless CO Connection-Oriented Con Connection Dm Domain Ed End ER Entity Relationship Fw Forwarding FwEP Forwarding End Point FwIP Forwarding In
31、termediate Point FwP Forwarding Point FwPP Forwarding Point Pool Gr Group Im Intermediate IOC Information Object Class Lk Link Log Logical Ly Layer MP2MP Multipoint-to-Multipoint NE Network Element Nw Network P2P Point-to-Point Rec. ITU-T M.3102 (01/2011) 3 Pl Pool Pt Point Ptr Pointer Rel Relations
32、hip SNw SubNetwork Top Topological 5 Conventions This Recommendation uses the conventions defined in ITU-T M.3020 for requirements capture and analysis. 6 Information object classes 6.1 Imported information entities and local labels None. 6.2 Class diagrams 6.2.1 Attributes and relationships 6.2.1.1
33、 Network fragment The network fragment is a grouping of information object classes (IOCs) that represents collections of interconnected telecommunications and management objects (logical or physical) capable of exchanging information. These objects have one or more common characteristics, for exampl
34、e, they may be owned by a single customer or provider, or associated with a specific service network. A network may be nested within another (larger) network, thereby forming a containment relationship. Layer_Network_Domain in this Recommendation can be either connection-oriented or connectionless.
35、IOCs in the network fragment are presented in Figure 1. Figure 1 Containment diagram of network fragment The entity relationship (ER) diagram of the network fragment is presented in Figure 2. 4 Rec. ITU-T M.3102 (01/2011) Abs_Lk_Pt_UAbs_Fw_Pt_USNw_UAc_Gr_U* Includes its subclasses:Fw_Ed_Pt_U and Fw_
36、Im_Pt_UManaged Entity* Represent the IOCs that can be able to support the SNw_U IOC.*Abs_Lk_UIOCs shown in dotted outlines are found in other fragment.#containedInSNwListrelation-SNw_U-Ac_Gr_U#containedAcGrList0*0*#supportByObjectList0*0*#containedInSNwList#containedSNwListrelation-SNw_U-SNw_U#conta
37、inedFwPtList01relation-SNw_U-Abs_Fw_Pt_U0*relation-SNw_U-Abs_Lk_Pt_U#containedInSNwList#containedLkPtList010*#containedLkList#linkPtrList02010*0*relation-SNw_U-Abs_Lk_U-1relation-SNw_U-Abs_Lk_U-2relation-SNw_U-Managed_Entity0*0*IOCs shown in dotted outlines are found in other fragment.* Include its
38、subclasses:Top_Lk_U and Log_Lk_U*Figure 2 ER diagram of network fragment 6.2.1.2 Forwarding point fragment IOCs in forwarding point fragment for the network element view are presented in Figure 3. * Includes its subclassesFw_Ed_Pt_UFw_Im_Pt_UManaged Element (M.3160)0*0*IOCs shown in dotted outlines
39、are found in other fragment.Figure 3 Forwarding point fragment Network element view IOCs in forwarding point fragment for the network view are presented in Figure 4. Rec. ITU-T M.3102 (01/2011) 5 Figure 4 Forwarding point fragment Network view The entity relationship (ER) diagram of the termination
40、point fragment for the network element view is presented in Figure 5. Figure 5 ER diagram of forwarding point fragment 6.2.1.3 Topology and connectivity fragment IOCs in the topology and connectivity fragment for the network view are presented in Figure 6. 6 Rec. ITU-T M.3102 (01/2011) Figure 6 Topo
41、logy and connectivity fragment The entity relationship (ER) diagrams of the topology and connectivity fragment are presented in Figures 7 and 8. 110* 0*#aEnd #zEnd#containedInSNwList01SNw_U010*#lkPtr02Ac_Gr_U#lkPtrList020*0*0*#containedLkPtList#containedLkList010*Object classes shown in dotted outli
42、nes are foundin other fragment#lkPtrList0*02#containedAcGrList#containedInSNwList0*0*#acPtList 010*Abs_Lk_UAbs_Lk_UAbs_Lk_Pt_U* Can be an instance of Top_Lk_Pt_U,Log_Lk_CO, Ac_Gr_U, or SNw_U.End_of_LinkEnd_of_Link *relation-Abs_Lk_U-a_EndofLinkrelation-Abs_Lk_U-z_EndofLinkrelation-Ac_Gr_U-Abs_Lk_Ure
43、lation-Abs_Lk_Pt_U-Abs_Lk_Urelation-SNw_U-Abs_Lk_Pt_Urelation-SNw_U-Ac_Gr_Urelation-Ac_Gr_U-Fw_Ed_Pt_U* Include its subclasses* Include its subclassesrelation-SNw_U-Abs_Lk_U-2relation-SNw_U-Abs_Lk_U-1*Top_Lk_Pt_Urelation-Top_Lk_Pt_U-Fw_Ed_Pt_U#serverFwEdPtPtrFw_Ed_Pt_UFigure 7 ER diagram of topology
44、 and connectivity fragment (part 1) Rec. ITU-T M.3102 (01/2011) 7 Lk_Con_CO0*110*010*0*0*SNw_Con_CO0*SNw_Fw_Rel_CL010*01010*Fw_Im_Pt_U0*0*Trail_COSNw_Ac_Rel_CL0*01Log_Lk_Pt_COrelation-Log_Lk_Pt_U-Fwg_Pt_U#fwPtInLkPtListTop_Lk_ULog_Lk_COrelation-Log_Lk_CO-Lk_Con_CO#lkConPtrListrelation-Lk_Con_CO-Abs_
45、Ac_Rel_U#serverAcRelList#clientFwRelPtrListrelation-Lk_Con_CO-client_Trail_CO#clientTrail#conListrelation-Trail_CO-SNw_Con_CO#componentPtrList#compositePtrrelation-SNw_Con_CO-Lk_Con_COrelation-SNw_Con_CO-SNw_Con_COrelation-Top_Lk_U-Abs_Ac_Rel_U#serverAcRelAbs_Ac_Rel_U0*#componentPtrList#clientLkPtrL
46、ist#componentPtrListrelation-SNw_Ac_Rel_CL-Top_Lk_U0*relation-SNw_Ac_Rel_CL-SNw_Fw_Rel_CLrelation-SNw_Fw_Rel_CL-Top_Lk_U0*relation-SNw_Fw_Rel_CL-SNw_Fw_Rel_CLObject classes shown in dotted outlines are foundin other fragmentObject classes shown in dotted outlines are foundin other fragment* Includes
47、 its subclasses:Trail_CO in that case, the SNw_Ac_Rel_CL can be composed of an ordered sequence of Top_Lk_U(s) and Subnetwork_Forwarding_Relationship_CL(s), which can be shown in Figure 19: Figure 19 Intra-layer relationship for CL networks SNw_Ac_Rel_CL composition which supports ordered sequence R
48、ec. ITU-T M.3102 (01/2011) 13 In a connectionless network, a SNw_Ac_Rel_CL can sometimes be represented by a corresponding SNw_Fw_Rel_CL in the largest subnetwork, thus providing a multiple access relationship, as shown in Figure 20. Figure 20 Intra-layer relationship for CL networks SubNetwork_Acce
49、ss_Relationship_CL supported by one SNw_Fw_Rel_CL 6.2.3.2.3 Subnetwork partitioning and subnetwork forwarding relationship If a SNw_U is dividable (e.g., matrix subnetwork), it can be vertically partitioned into smaller SNw_U(s) connected by the Abs_Lk_U(s). This is applicable for both connection-oriented layer networks and connectionless networks, which is shown in Figure 21. Figure 21 Inter-layer relationship: Subnetwork partitioning A SNw_U can also be fragmented by several Abs_S
