ITU-T M 3108 1-1999 Information Model for Management of Leased Circuit and Reconfigurable Services - Series M TMN and Network Maintenance International Transmission Systems Telepho.pdf

《ITU-T M 3108 1-1999 Information Model for Management of Leased Circuit and Reconfigurable Services - Series M TMN and Network Maintenance International Transmission Systems Telepho.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3108 1-1999 Information Model for Management of Leased Circuit and Reconfigurable Services - Series M TMN and Network Maintenance International Transmission Systems Telepho.pdf（88页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU M.3108.1 (03199) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Telecommunications management network Information mode

2、l for management of leased circuit and reconfigurable services ITU-T Recommendation M.3108.1 (Previously CCITT Recommendation) ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Il Introduction

3、 and general principles of maintenance and maintenance organization International transmission systems International telephone circuits Common channel signalling systems International telegraph systems and phototelegraph transmission International leased group and supergroup links International leas

4、ed circuits Mobile telecommunication systems and services International public telephone network International data transmission systems Designations and information exchange International transport network M.10-M.299 M.300-M.559 M.560-M ,759 M. 760-M. 799 M.800-M.899 M. 900-M. 999 M.1000-M.1099 M.1

5、100-M.1199 M.1200-M.1299 M. 1300-M. 1399 M.1400-M.1999 M.2000-M.2999 U Integrated services digital networks M. 3600-M.3999 Common channel signalling systems M.4000-M.4999 For further details, please refer to ITU-T List of Recommendations. INFORMATION MODEL FOR MANAGEMENT OF LEASED CIRCUIT AND RECONF

6、IGURABLE SERVICES Summary This Recommendation provides a GDMO-based information model to support the management of the leased circuit service as outlined in Recommendation M.3208.1. Appendix I provides a protocol- independent version of this information model in “structured“ English. Appendix II pro

7、vides a mapping from the management functions in Recommendation M.3208.1 to the Managed Objects defined in this Recommendation. Appendix III provides a Unified Modelling Language (UML) view of the same information model. Source ITU-T Recommendation M.3108.1 was prepared by ITU-T Study Group 4 (1997-

8、2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of March 1999. Recommendation M.3108.1 (03/99) 1 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Se

9、ctor (ITU-T) is a permanent organ of the ITU. The 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 Conference (WTSC), which

10、 meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas of information

11、technology which fali within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation the term recognized operating agency (ROA) includes any individual, company, corporation or governmental organization that operates a public corres

12、pondence service. The terms Administration, ROA and public correspondence are defined in the Constitution of the ITU (Geneva, 1992). INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Int

13、ellectual Property Right. The 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, the ITU had

14、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 therefore strongly urged to consult the TSB patent database. O ITU 1999 All right

15、s reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. I I ii Recommendation M.3108.1 (03199) 1 1.1 1.2 1.3 2 3 4 5 5.1 5.2 5.3 5.4 5.5 6 6.1 6.2 6.

16、3 6.4 6.5 STDmITU-T RECMN fl-3308-3-ENGL 3997 = 4862573 ObbOSLl 8bT CONTENTS Page Scope. purpose and application Scope Purpose . Application . References Definitions Abbreviations . Overview Generic service request fragment . LCS service request fragment . Link connection service request fragment Tr

17、ansport service fragment . Resource fragment Information model Managed objects for generic service request fragment 6.1.1 CurrentServiceRequest . 6.1.2 serviceRequestHistoryRecord . 6.1.3 serviceModifyRequest . Managed objects for LCS request fragment . 6.2.1 CurrentLcsRequest . 6.2.3 IcsModieReques

18、t Managed objects for link connection service request fragment . 6.3.1 currentLinkConnectionServiceRequest . 6.3.2 1inkConnectionServiceRequestHistoryRecord 6.3.3 1inkConnectionServiceModiSlRequest . Managed objects for service fragment 6.4.2 lcs 6.4.3 1inkConnectionService 6.4.4 Service Access Doma

19、in . 6.4.5 Service Access Group . 6.2.2 IcsRequestHistoryRecord 6.4.1 Transport service . Managed objects for resource fragment . 6.5.1 Service Access Equipment Recommendation M.3108.i (03/99) 1 2 2 3 5 5 5 6 6 8 8 8 10 10 11 11 1.1 12 12 12 13 13 13 13 14 15 15 16 16 16 . 111 6.6 Packages . 6.6.1 a

20、liasNameInfoPackage 6.6.2 aliasNamePackage . 6.6.3 bandwidthInfoPackage 6.6.4 bandwidthPackage . 6.6.6 dateoff nstallationPackage . 6.6.7 daily SchedulingInfoPackage . 6.6.8 daily SchedulingCurrentPackage . 6.6.9 diversityInfoPackage . 6.6.1 O diversitypackage 6.6.12 equipmentTypePackage 6.6.13 expe

21、ctedDateOfl nstallationInfoPackage . 6.6.14 expectedDateOfl nstallationPackage 6.6.16 externalSchedulerInfoPackage 6.6.1 7 initialServiceAdministrativeStateInfoPackage 6.6.18 initialServiceAdministrativeStatePackage 6.6.19 modelTypePackage . 6.6.20 originatingLocationCPEInfoPackage 6.6.2 1 originati

22、ngLocationCPEModiSrPackage 6.6.5 customerRequestNumberPackage . 6.6.11 equipmentManufacturerPackage . 6.6.15 externalSchedulerCuentPackage . 6.6.22 originatingLocationCPEPackage 6.6.23 originatingLocationCPInfoPackage 6.6.24 originatingLocationInfoPackage . 6.6.25 originatingLocationSapInfoPackage .

23、 6.6.26 originatingLocationSapPackage 6.6.27 procedurepackage 6.6.28 quantityInfoPackage 6.6.29 quantitypackage 6.6.30 reflectiveOperationalStatePackage 6.6.3 1 reflectiveAdministrativeStatePackage . 6.6.32 routeInfoPackage . 6.6.33 routepackage . 6.6.3 5 serviceAvailabilityDateInfoPackage . 6.6.37

24、serviceCustomerContactPackage 6.6.3 8 serviceDescriptionInfoPackage . 6.6.34 serviceAdministrativeStatePackage 6.6.36 serviceAvailabilityDatePackage Page 17 17 17 17 17 17 17 18 18 18 18 18 18 18 19 19 19 19 19 19 19 19 20 20 20 20 20 20 20 20 21 21 21 21 21 21 21 22 22 iv Recommendation M.3108.1 (0

25、3199) STD-ITU-T RECMN Mm3308.3-ENGL L999 4862593 Obb09L3 632 6.6.39 6.6.40 6.6.41 6.6.42 6.6.43 6.6.44 6.6.45 6.6.46 6.6.47 6.6.48 6.6.49 6.6.50 6.6.51 6.6.52 serviceDescnptionPackage serviceProviderContactPackage serviceTerminationDateInfoPackage serviceTenninationDatePackage . serviceTypeInfoPacka

26、ge . terminating LocationCPEInfoPackage . terminatingLocationCPEModiSlPackage tenninatingLocationCPEPackage terminatingLocationCPInfoPackage . terminatingLocationInfoPackage terminatingLocationSapInfoPackage terminatingLocationSapPackage . weekly SchedulingInfoPackage . weekly Scheduling CurrentPack

27、ag e 6.7 Attributes 6.7.1 aliasName 6.7.2 bandwidth 6.7.3 cp . 6.7.4 customerRequestNumber 6.7.5 dateOfI nstallation 6.7.6 diversity . 6.7.7 equipmentManufacturer 6.7.8 equipmentType 6.7.9 expectedDateOfl nstallation . 6.7.1 O 1istOfSags 6.7.1 1 listofsaps . 6.7.12 modelType . 6.7.13 numberonspecifi

28、edsaps 6.7.14 originatinglocation . 6.7.1 5 originatingLocationCP 6.7.16 originatingLocationCPE 6.7.17 originatingLocationSap . 6.7.1 8 procedure . 6.7.20 quantity 6.7.19 providerRequestNumber . 6.7.2 1 requestedInitialServiceAdministrativeS tate 6.7.22 requestReceptionTime . 6.7.23 requestSequenceN

29、umber . 6.7.24 route . Page 22 22 22 22 22 23 23 23 23 23 23 23 23 24 24 24 24 24 24 25 25 25 25 25 25 26 26 26 26 26 26 27 27 27 27 27 28 28 28 Recommendation M.3108.1 (03/99) V 6.8 6.9 6.10 6.1 1 . I vi 6.7.25 6.7.26 6.7.27 6.7.28 6.7.29 6.7.30 6.7.3 1 6.7.32 6.7.33 6.7.34 6.7.35 6.7.36 6.7.37 sad

30、Id sagId saglocation . ServiceAvailability Date . serviceCustomerContact serviceInstance serviceProviderContact . serviceRequest State . serviceTeminationDate tenninatinglocation terminatingLocationCP . tenninatingLocationCPE . terminatingLocationSap Error messages 6.8.1 addToSagError 6.8.2 bandwidt

31、hunavailable . 6.8.3 CreateLCSError . 6.8.4 createLinkConnectionError . 6.8.5 createSadError . 6.8.6 createSagError . 6.8.7 deleteLCSError 6.8.8 deleteLinkConnectionEnor . 6.8.9 deleteSadError . 6.8.10 deleteSagEnor . 6.8.1 1 modifiLCSError 6.8.12 removeFromSagEnor 6.8.13 resourcesunavailable . Noti

32、fications . 6.9.1 IcsModifiProgressProblemReport 6.9.3 1inkConnectionModifiProgressProblemReport 6.9.4 1inkConnectionRequestProgressProblemReport . 6.9.2 IcsRequestProgressProblemeport . Actions 6.10.2 AddSapsToSag 6.10.1 updateServiceRequest . Name bindings 6.1 1.1 currentLcsRequest-account . 6.11.

33、2 IcsRequestHistoryRecord-CurrentLCSRequest . Recommendation M.3108.1 (03/99) Page 28 28 29 29 29 29 29 29 30 30 30 30 30 31 31 31 31 31 31 31 32 32 32 32 32 32 33 33 33 33 33 33 34 34 34 34 34 34 6.12 7 7.1 i 7.2 7.3 7.4 7.5 7.6 l 8 8.1 8.2 8.3 6.1 1.3 6.1 1.4 6.11.5 6.1 1.6 6.1 1.7 6.1 1.8 6.1 1.9

34、 lcsModiRequest-lcs currentLinkConnectionServiceRequest-account . 1inkConnectionServiceRequestHistoryRecord- currentLinkConnectionServiceRequest . linkComectionServiceModiRequest-linkConnectionService . serviceAccessEquipmentView-account IinkConnectionService-account ICs-account . 6.1 1.1 O serviceA

35、ccessDomain.account 6.11.11 serviceAccessGroup-serviceAccessDomain . ASN.l syntax 6.12.1 Rules of extensibility . 6.12.2 ASN . 1 module . Functional units Basic transport service functional unit . Transport service order functional unit Transport service order history functional unit Transport servi

36、ce modi functional unit . Transport resource visibility functional unit Negotiation of functional units . Conformance Static conformance . Dynamic conformance Conformance to managed object definitions Appendix I . Protocol-independent object description . Generic service request fragment . 1.1.2 ser

37、viceRequestHistoryRecord . I . 1 1.1.1 CurrentServiceRequest . I . 1.3 serviceModiRequest . 1.2 LCS request fiagrnent . I 1.2.1 currentLcsRequest . 1.2.2 IcsRequestHistoryRecord 1.2.3 IcsModXyRequestRecord Page 35 35 35 35 35 36 36 36 36 37 37 37 44 45 45 45 45 45 45 46 46 46 46 47 48 48 50 52 53 53

38、 55 55 Recommendation M.3108.1 (03/99) vii 1.3 1.4 1.5 1.6 Link connection service request fiagment 1.3.1 currentLinkConnectionServiceRequest . I . 3.2 1inkConnectionServiceRequestHistoryRecord I . 3.3 1inkConnectionServiceModiQRequest . Service fragment . 1.4.1 transportService . 1.4.2 lcs 1.4.3 1i

39、nkConnectionService Reconfigurable service fragment 1.5.1 serviceAccessDomain . 1.5.2 serviceAccessGroup Resource fiagment 1.6.1 serviceAccessEquipment . Appendix II . Mapping of M.3208.1 functions into M.3 108.1 MOS Appendix III - UML diagrams for leased circuit service object model III . 1 Introdu

40、ction 111.2 UML class diagrams for inheritance of M.3208.1 object classes . 111.3 111.4 111.5 UML class diagrams for modelling relationships UML class diagrams for modelling agent functionality . UML sequence diagrams to illustrate scenarios of object usage . VI11 Recommendation M.3108.1 (03199) - P

41、age 56 56 58 58 59 59 60 61 62 62 63 64 64 65 68 68 68 70 72 73 Recommendation M.3108.1 INFORMATION MODEL FOR MANAGEMENT OF LEASED CIRCUIT AND RECONFIGURABLE SERVICES (Geneva, 1999) 1 Scope, purpose and application 1.1 Scope This Recommendation provides a GDMO-based information model to support the

42、management of the leased circuit service as outlined in Recommendation M.3208.1. Appendix I provides a protocol- independent version of this information model in “structured“ English. Appendix II provides a mapping from the management functions in Recommendation M.3208.1 to the managed objects defin

43、ed in this Recommendation. Appendix III provides a Unified Modelling Language (UML) view of the same information model. 1.2 Purpose The purpose of this Recommendation is to support standard interfaces, across the X interface, among service customers, service providers and network providers for the p

44、urposes of managing leased circuit services in the service management layer of the TMN. It specifically intended to support the requirements provided in Recommendation M.3208.1. 1.3 Application This Recommendation is applicable to interfaces between systems that participate in the ordering and manag

45、ement of leased circuit 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 Recommendations and other

46、 references are subject to revision; all 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. - IT

47、U-T Recommendation G.805 (1 995), Generic functional architecture of transport networks. ITU-T Recommendation M.30 1 O (1 996), Principles for a telecommunications management network. - - ITU-T Recommendation M.3 1 O0 (1 995), Generic network information model. - ITU-T Recommendation M.3200 (1997),

48、TMN management services and telecommunications managed areas: Overview. ITU-T Recommendation M.3208.1 (1 997), TMN management services for dedicated und reconjgurable circuits network: Leased circuit services. ITU-T Recommendation M.3400 (1997), TMN management functions. - - Recommendation M.3108.1

49、(03199) 1 - ITU-T Recommendation 4.821 (1993), Stage 2 and stage 3 description for the Q3 interface -Alarm surveillance. CCITT Recommendation X.72 1 (1 992) I ISOIEC 1 O1 65-2: 1992, Information technology - Open Systems Interconnection - Structure of management information: DeJnition of managernent information. CCITT Recommendation X.734 (1 992) I ISO/IEC 10 164-5: 1993, Information technology - Open Systems Interconnection - Systems management: Event report management function. CCITT Recommendation X.735 (1 992) I ISO/IEC 1 O1 64-6: 1993, Information tec