ITU-T M 3108 3-2001 TMN management services for dedicated and reconfigurable circuits network Information model for management of virtual private network service (Study Group 4)《专用.pdf

《ITU-T M 3108 3-2001 TMN management services for dedicated and reconfigurable circuits network Information model for management of virtual private network service (Study Group 4)《专用.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3108 3-2001 TMN management services for dedicated and reconfigurable circuits network Information model for management of virtual private network service (Study Group 4)《专用.pdf（18页珍藏版）》请在麦多课文档分享上搜索。

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T M.3108.3 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2001) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Telecommunications management network TMN managemen

2、t services for dedicated and reconfigurable circuits network: Information model for management of virtual private network service ITU-T Recommendation M.3108.3 (Formerly CCITT Recommendation) ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CI

3、RCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph s

4、ystems 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.1100M.1199 International public telephone network M.1200M.1299 International data transmission syste

5、ms M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600M.3999 Common channel signalling systems M.4000M.4999 For further details, please refer to the

6、 list of ITU-T Recommendations. ITU-T M.3108.3 (01/2001) i ITU-T Recommendation M.3108.3 TMN management services for dedicated and reconfigurable circuits network: Information model for management of virtual private network service Summary This Recommendation provides a GDMO-based information model

7、to support the management of the Virtual Private Network Service as outlined in ITU-T M.3208.3. Source ITU-T Recommendation M.3108.3 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. ii ITU-T M.3108.3 (01/2001) FOREWORD The Interna

8、tional Telecommunication Union (ITU) is the United Nations specialized 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 Recommendati

9、ons 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 ITU-T study groups which, in turn, produce Recommendations on these topics. The approva

10、l 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 collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration

11、“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. 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

12、. 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 Recommendation, ITU had not received notice of intellect

13、ual 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 therefore strongly urged to consult the TSB patent database. ITU 2001 All rights reserved. No part of this public

14、ation may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. ITU-T M.3108.3 (01/2001) iii CONTENTS Page 1 Scope, purpose and application 1 1.1 Scope. 1 1.2 Purpose 1 1.3 Application 1 2 Refere

15、nces. 1 3 Definitions 2 4 Abbreviations 2 5 Overview. 2 6 Information model 4 6.1 Managed objects . 4 6.1.1 VPN service. 4 6.1.2 vpnLCS 4 6.2 Attributes 5 6.3 Name bindings 5 6.3.1 vpnService-account . 5 6.3.2 vpnLCS-account 5 6.4 Parameter Definitions . 5 6.4.1 createVpnServiceError 5 6.4.2 createV

16、pnLCSError . 5 6.4.3 deleteVpnLCSError . 6 6.5 ASN.1 syntax 6 6.5.1 Rules of extensibility. 6 6.5.2 ASN.1 module . 6 7 Functional units. 7 7.1 VPN Service Order functional unit. 8 7.2 VPN Leased Circuit Management functional unit 8 7.3 Negotiation of functional units . 8 8 Conformance. 9 8.1 Static

17、conformance . 9 8.2 Dynamic conformance 9 8.3 Conformance to managed object definitions 9 Appendix I UML class diagrams for VPN service object model . 9 I.1 Introduction. 9 iv ITU-T M.3108.3 (01/2001) Page I.2 UML class diagrams for inheritance of object classes . 10 I.3 UML class diagrams for conta

18、inment relationships . 11 ITU-T M.3108.3 (01/2001) 1 ITU-T Recommendation M.3108.3 TMN management services for dedicated and reconfigurable circuits network: Information model for management of virtual private network service 1 Scope, purpose and application 1.1 Scope This Recommendation provides a

19、GDMO-based information model to support the management of the Virtual Private Network Service as outlined in ITU-T M.3208.3. 1.2 Purpose The purpose of this Recommendation is to support the standard interfaces, across the X-interface, between service customers and service providers for the purposes

20、of managing the virtual private network services in the service management layer of the TMN. It specifically intended to support the requirements provided in ITU-T M.3208.3. 1.3 Application This Recommendation is applicable to the interfaces between systems that participate in the ordering and the m

21、anagement of the virtual private network services. 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 Recomme

22、ndations 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 references listed below. A list of the currently valid ITU-T Recommendations is regularly p

23、ublished. ITU-T G.805 (2000), Generic functional architecture of transport networks. ITU-T M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3100 (1995), Generic network information model. ITU-T M.3108.1 (1999), Information model for leased circuit and reconfigurable ser

24、vices. ITU-T M.3200 (1997), TMN management services and telecommunications managed areas: overview. ITU-T M.3208.1 (1997), TMN management services for dedicated and reconfigurable circuits network: Leased circuit services. ITU-T M.3208.3 (2000), TMN management services for dedicated and reconfigurab

25、le circuits network: virtual private network service. ITU-T M.3400 (2000), TMN management functions. ITU-T Q.821 (2000), Stage 2 and stage 3 description for the Q3 interface Alarm surveillance. 2 ITU-T M.3108.3 (01/2001) ITU-T X.721 (1992), Information technology Open Systems Interconnection Structu

26、re of management information: Definition of management information. ITU-T X.734 (1992), Information technology Open Systems Interconnection Systems Management: Event report management function. ITU-T X.735 (1992), Information technology Open Systems Interconnection Systems Management: Log control fu

27、nction. ITU-T X.746 (2000), Information technology Open Systems Interconnection Systems management: Scheduling function. ITU-T X.790 (1995), Trouble management for ITU-T Applications. 3 Definitions This Recommendation uses the definitions provided in ITU-T M.3208.3. 4 Abbreviations This Recommendati

28、on uses the following abbreviations: GDMS Guidelines for the Definition of TMN Management Services LCS Leased Circuit Service MOC Managed Object Class MOI Managed Object Instance NE Network Element NML Network Management Layer SAG Service Access Group SAP Service Access Point SC Service Customer SLA

29、 Service Level Agreement SML Service Management Layer SP Service Provider TMN Telecommunication Management Network UML Unified Modelling Language VPN Virtual Private Network 5 Overview This clause provides an overview of the information model and its use in the management of VPN services. Clause 6 p

30、rovides the formal definition of the GDMO-based information model. The management of a VPN service starts when a Service Customer (SC) requests the service. This can be achieved by the SC requesting SP to create an instance of vpnService. The SP then informs the SC of the availability of the request

31、ed service through a notification of the creation of an instance of vpnService. ITU-T M.3108.3 (01/2001) 3 After the SC has been notified about the creation of the vpnService instance, the SC can modify the service through management operations for some attributes. An instance of the networkR1 is us

32、ed for naming. All entries in that MOI can be changed only by the SP, though the SC can read (GET) such information. A vpnService MOI contains zero or more serviceAccessGroups, though a vpnService MOI containing less than two serviceAccessGroups is not very useful. The SC can create instances of ser

33、viceAccessGroup MOC. A serviceAccessGroup MOI contains zero or more SAPs. A serviceAccessGroup MOI is created without any SAPs. After creation a instance of serviceAccessGroup, the SC can add or remove SAPs from the serviceAccessGroup. The SC can identify some or all of the SAPs desired in a service

34、AccessGroup. If the SC adds to a serviceAccessGroup more SAPs than are explicitly identified, then the SP assigns additional SAPs, from the same service location to the serviceAccessGroup, and informs the SC about the identity of those SAPs. The SC can add or remove SAPs from a serviceAccessGroup th

35、rough management operations. After the requested VPN service has been implemented by the SP, the SC can request the creation of one or more VPN Leased Circuit in the VPN service. The VPN Leased Circuit connects the VPN service access points that are included in the specified service access groups. T

36、he SC can create instances of vpnLeasedCircuit MOC. Figures 5-1 and 5-2 represent the inheritance of the MOCs and the containment relationships of the MOIs respectively. Inheritance and containment are not shown for all of the MOs that are imported from other Recommendations. Figure 5-2 does not sho

37、w the containment of the M.3100 network MO in directory objects as specified in ITU-T M.3100. T0414330-00top (X.721)vpnLCS vpnServiceServiceAccessGroup(M.3108.1)TransportService(M.3108.1)serviceAccessDomainR1(M.3108.1)network (M.3100)networkR1 (M.3100)ServiceAccessEquipmentView(M.3108.1)Figure 5-1/M

38、.3108.3 Inheritance relationship 4 ITU-T M.3108.3 (01/2001) T0414340-00networkR1 (M.3100)account (X.790)vpnLCSvpnServiceServiceAccessGroup(M.3108.1)ServiceAccessEquipmentView(M.3108.1)Figure 5-2/M.3108.3 Containment relationship This Recommendation defines two Functional Units (FUs): VPN service; VP

39、N Leased circuit management. These FUs cover the management functions defined in ITU-T M.3208.3. 6 Information model This clause provides the information model for the management of VPN services using GDMO. 6.1 Managed objects 6.1.1 VPN service vpnService MANAGED OBJECT CLASS DERIVED FROM “ITU-T Rec

40、. M.3108.1:1999“: serviceAccessDomainR1; CHARACTERIZED BY vpnServicePackage PACKAGE BEHAVIOUR vpnServiceBehaviour BEHAVIOUR DEFINED AS “ This instantiable MO represents a VPN service. The sadId equals to vpnId, used to identify the VPN service. The serviceType in the serviceAccessDomainR1 is not pre

41、sent in this MOC.“;, “ITU-T Rec. M.3108.1:1999“: serviceDescriptionListPackage; REGISTERED AS m3108PartVPNObjectClass 1; 6.1.2 vpnLCS vpnLCS MANAGED OBJECT CLASS DERIVED FROM “ITU-T M.3108.1:1999“: transportService; CHARACTERIZED BY vpnLeasedCircuitPackage PACKAGE BEHAVIOUR vpnLeasedCircuitBehaviour

42、 BEHAVIOUR DEFINED AS “This instantiable MO represents a VPN leased circuit. If the SLA allows the SC to specify the route and the SC did not specify the route in the service request, then the route attribute shall be present as an empty SEQUENCE. The route cannot be changed through a management ope

43、ration on this MO. “; ATTRIBUTES bandwidth GET-REPLACE, “ITU-T M.3108.1:1999“: originatingLocationSap GET SET-BY-CREATE, “ITU-T M.3108.1:1999“: terminatingLocationSap GET SET-BY-CREATE; ITU-T M.3108.3 (01/2001) 5 CONDITIONAL PACKAGES “ITU-T M.3108.1:1999“: routePackage PRESENT IF “route was present

44、in the service request “, “ITU-T M.3108.1:1999“: originatingLocationCPEModifyPackage PRESENT IF “originatingLocationCPE was present in the service request “, “ITU-T M.3108.1:1999“: terminatingLocationCPEModifyPackage PRESENT IF “terminatingLocationCPE was present in the service request “; REGISTERED

45、 AS m3108PartVPNObjectClass 2; 6.2 Attributes bandwidth ATTRIBUTE WITH ATTRIBUTE SYNTAX M3108PartVPNASN1Module.Bandwidth; MATCHES FOR EQUALITY; REGISTERED AS m3108PartVPNAttribute 1; 6.3 Name bindings 6.3.1 vpnService-account vpnService-account NAME BINDING SUBORDINATE OBJECT CLASS vpnService AND SU

46、BCLASSES; NAMED BY SUPERIOR OBJECT CLASS “Rec. X.790“:account AND SUBCLASSES; WITH ATTRIBUTE “ITU-T M.3108.1:1999“: sadId; CREATE createVpnServiceError; DELETE “ITU-T M.3108.1:1999“: deleteServiceAccessDomainError; REGISTERED AS m3108PartVPNNameBinding 1; 6.3.2 vpnLCS-account vpnLCS-account NAME BIN

47、DING SUBORDINATE OBJECT CLASS vpnLCS AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS “Rec. X.790“:account AND SUBCLASSES; WITH ATTRIBUTE “ITU-T M.3108.1:1999“: serviceID; CREATE createVpnLCSError; DELETE deleteVpnLCSError; REGISTERED AS m3108PartVPNNameBinding 2; 6.4 Parameter Definitions 6.4.1 creat

48、eVpnServiceError createVpnServiceError PARAMETER CONTEXT SPECIFIC-ERROR ; WITH SYNTAX M3108PartVPNASN1Module.CreateVpnServiceError ; BEHAVIOUR createVpnServiceErrorBehaviour BEHAVIOUR DEFINED AS “the parameter is used for VPN service creation.“ ; REGISTERED AS m3108PartVPNParameter 1 ; 6.4.2 createV

49、pnLCSError createVpnLCSError PARAMETER CONTEXT SPECIFIC-ERROR ; WITH SYNTAX M3108PartVPNASN1Module.CreateVpnLCSError ; 6 ITU-T M.3108.3 (01/2001) BEHAVIOUR createVpnLCSErrorBehaviour BEHAVIOUR DEFINED AS “the parameter is used for VPN LCS creation.“ ; REGISTERED AS m3108PartVPNParameter 2 ; 6.4.3 deleteVpnLCSError deteteVpnLCSError PARAMETER CONTEXT SPECIFIC-ERROR ; WITH SYNTAX M3108PartVPNASN1Module.DeleteVpnLCSError ; BEHAVIOUR deleteVpnLCSErrorBehaviour BEHAVIOUR DEFINED AS “the paramet