ITU-T G 851 1-1996 Management of the Transport Network - Application of the RM-ODP Framework - Series G Transmission Systems and Media Digital Systems and Networks Digital Transmiscat.pdf

《ITU-T G 851 1-1996 Management of the Transport Network - Application of the RM-ODP Framework - Series G Transmission Systems and Media Digital Systems and Networks Digital Transmiscat.pdf》由会员分享，可在线阅读，更多相关《ITU-T G 851 1-1996 Management of the Transport Network - Application of the RM-ODP Framework - Series G Transmission Systems and Media Digital Systems and Networks Digital Transmiscat.pdf（72页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STAN DARDI ZATI ON SECTOR OF ITU G.851 .I (1 1/96) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital transmission systems - Digital networks - Telecommunications management network Management of the transport

2、network - Application of the RM-ODP framework ITU-T Recommendation G.851 .I (Previously CCIlT Recommendation) STD-ITU-T RECMN G.85L.L-ENGL L99b m Li8b259L Ob33852 Li79 m ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AN

3、D CIRCUITS IN TERNA TIONAL ANALOGUE CARRIER SYSTEM TRANSMISSION SYSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER- GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE WITH METALLIC LINES SYSTE

4、MS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY TRANSMISSION MEDIA CHARACTERISTICS DIGITAL TRANSMISSION SYSTEMS TERM I NAL EQU I PM ENTS General Coding of analogue signals by pulse code modulation Coding of analogue signals by methods other

5、than PCM Principal characteristics of primary multiplex equipment Principal characteristics of second order multiplex equipment Principal characteristics of higher order multiplex equipment Principal characteristics of transcoder and digital multiplication equipment Operations, administration and ma

6、intenance features of transmission equipment Principal characteristics of multiplexing equipment for the synchronous digital hierarchy Other terminal equipment General aspects Design objectives for digital networks Quality and availability targets Network capabilities and functions SDH network chara

7、cteristics DIGITAL NETWORKS DIGITAL SECTIONS AND DIGITAL LINE SYSTEM General Parameters for optical fibre cable systems Digital sections at hierarchical bit rates based on a bit rate of 2048 kbis Digital line transmission systems on cable at non-hierarchical bit rates Digital line systems provided b

8、y FDM transmission bearers Digital line systems Digital section and digital transmission systems for customer access to ISDN Optical fibre submarine cable systems Optical line systems for local and access networks G.lOO-G. 199 G .200-G.299 G.300-G.399 G.400-G.449 G.450-G.499 G.600-G.699 G.700-G.799

9、G.700-G.709 G.710-G.719 G. 720-G.729 G.730-G.739 G. 740-G.749 G.750-G.759 G.760-G ,769 G.770-G.779 G.780-G.789 G.790-G.799 G.800-G.899 G.800-G.809 G.810-G.819 G.820-G.829 G.830-G.839 G. 840-G.849 G.900-G.999 G .900-G.909 G.910-G.919 G.920-G.929 G.930-G.939 G .940-G. 949 G.950-G.959 G.960-G.969 G.970

10、-G .979 G. 980-G. 999 For further details, please refer to ITU-T List of Recommendations. ITU-T RECOMMENDATION G.851.1 MANAGEMENT OF THE TRANSPORT NETWORK-APPLICATION OF THE RM-ODP FRAMEWORK Source ITU-T Recommendation G.851.1 was prepared by ITU-T Study Group 15 (1993-1996) and was approved under t

11、he WTSC Resolution No. 1 procedure on the 8th of November 1996. STD-ITU-T RECUR G.851.L-ENGL 1b M Lib2591 Ob3385Li 241 m FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector

12、(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 meet

13、s 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 techn

14、ology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. I NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELL

15、ECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rig

16、hts, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU hadhad not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, imp

17、lementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O IT 1997 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including ph

18、otocopying and microfilm, without permission in writing from the ITU. Il Recommendation 6.851.1 (11/96) - STD-ITU-T RECMN G-85L-L-ENGL L77b 4862591 0633855 LB D CONTENTS Page 1 Scope 1.1 Objectives . 1.2 Principles Structure of this Recommendation . 1.3 2 References 3 Definitions 4 Abbreviations use

19、d in this Recommendation . 5 Methodology overview . 5.1 Introduction 5.1.1 RM-ODP viewpoint descriptions 5.2 5.3 Using RM-ODP viewpoints in a specification design methodology Tracing between the viewpoints . 5.3.1 Labelling 6 Enterprise viewpoint . 6.1 Scope of the enterprise viewpoint 6.2 Concepts

20、. 6.2.1 Community 6.2.2 Contract . 6.2.3 Roles 6.2.4 Policies 6.2.5 Actions 6.2.6 Activities . 6.2.7 Services . 6.2.8 Service feature . 6.2.9 Composition of services 6.3 Extension of communities 6.4 Domains 7 Information viewpoint 7.1 Information viewpoint 8 Computational viewpoint . Communications

21、domain-independent computational viewpoint . viewpoint specification . 8.1 Computational concepts . 8.1 . 1 8.1.2 Mappings to the communications domain-dependent computational 2 3 6 7 8 8 8 9 9 9 9 10 10 10 10 10 10 11 12 12 13 13 Recommendation G.851.1 (11/96) iii STD-ITU-T RECMN G-85L-L-ENGL Lb 48

22、b25L Ob3385b 014 m 9 Engineering viewpoint 9.1 Introduction 9.2 Engineering concepts 9.3 OS1 management based engineering viewpoint . 9.3.1 Impact of protocols on information and computational viewpoints 9.3.2 Enterprise viewpoint engineering constraints . 9.3.3 The use of GDMO packages and managed

23、objects . 9.3.4 Support of multiple management services at an engineering interface . 9.3.5 Identification . 9.3.6 Relationship mapping 9.3.7 The use of actions versus attribute operations for relationships and state modifications . The distributed processing environment . 9.4.1 Overview . 9.4 1 O T

24、he use of ensembles in the definition of network management applications . 10.1 Scope Annex A . Template and guidelines for the enterprise viewpoint specification . A . 1 A.2 Informal definition of the enterprise template Formal definition of the enterprise template Annex B . Information viewpoint s

25、tructure B . 1 Introduction B.2 Model descriptions i B.3 Structure of the specification B.3.1 Information object classes . B.3.2 Information relationships B.3.3 Static schema definition B.3.4 Dynamic Schemas B.3.5 Attributes . Annex C . Computational viewpoint template description . C . 1 Introducti

26、on C.2 Guidelines . Guidelines specific to the operation template . Clienthewer interface definitions . Considerations for mapping to different communications domains . C.2.1 C . 2.2 C.2.3 Page 14 14 14 14 15 16 16 16 16 17 17 17 17 17 17 19 19 20 21 21 22 23 23 25 26 28 28 29 29 30 30 33 34 iv Reco

27、mmendation G.851.1 (11196) STD-ITU-T RECMN G*85L-Z-ENGL L97b m 4862573 Ob33857 T50 m C.3 Formal template definitions C.3.1 Object class template . C.3.2 Interface template C.4 Example C.3.3 Operation template I Annex D . OS1 management engineering viewpoint templates and guidelines D.1 Templates . A

28、nnex E . Label syntax . BNF definition of label syntax . D.2 Possible mappings to managed object definitions E.0 Introduction E . 1 E.2 Enterprise viewpoint label tree structure E.2.1 Examples of use E.3.1 Examples of use Computational viewpoint label tree structure . E.4.1 Examples of use E.3 Infor

29、mation viewpoint label tree structure . E.4 Annex F . Ensemble template . The ensemble technique . F . 1 F.2 Ensemble template F.2.1 Introduction . F.2.2 Management context . F.2.3 Management information model . F.2.4 Ensemble conformance requirements . Appendix I - Examples of templates and specifi

30、cations guidelines Enterprise services versus contracts . I . 1 Appendix II Representation of combined states Appendix III . Service realization description 111.1 Scope 111.2 Concepts . Appendix IV - Example of use of the ensemble concepts and format Appendix V . Example specification development pr

31、ocess Page 34 34 35 35 37 39 39 40 40 40 40 42 43 43 44 44 44 45 45 45 45 45 45 46 46 46 47 49 49 50 52 55 Recommendation G.851.1 (11/96) V STD-ITU-T RECMN G-85L.l-ENGL L99b 48b257L Ob33858 777 Page Appendix VI . Inter-viewpoint mapping . VI.1 Approach VI.2 Information viewpoint mappings . VI.2.1 In

32、formation objects and relationships . VI.2.2 Static schema . VI.2.3 Dynamic schema . VI.3 Computational viewpoint mappings . VI.3.1 Computational operation . VI.3.2 Computational interface VI.3.3 Computational object Appendix VI1 - Guidelines for the use of Z in the information viewpoint . VI1 . 1 V

33、II.2 VII.3 vi Introduction 2 notation review VII.2.1 Schemas . VII.2.2 Symbols . VII.2.3 Example . Specification conventions . VII.3.1 Attribute specification . VI1.3.2 Object specification . VII.3.3 Relationship specification . Recommendation G.851.1 (11/96) 55 55 56 57 57 57 57 57 57 57 58 58 58 5

34、8 59 59 60 60 60 61 Recommendation G.851.1 MANAGEMENT OF THE TRANSPORT NETWORK - APPLICATION OF THE RM-ODP FRAMEWORK (Geneva, 1996) 1 Scope This Recommendation provides a description of the modelling concepts upon which the ITU-T Study Group 15 network level model is based. The model uses the Refere

35、nce Model of Open Distributed Processing (RM-ODP) framework i, 2, 3 and 4 as a starting point to define a prescriptive methodology for defining the network level model. A process used to develop a complete set of specifications based on this methodology is described in Appendix V. 1.1 Objectives Thi

36、s Recommendation has the following objectives: - to define a methodology for speciGing a network management model to support interfaces to a network operations system within the TMN architecture, initially using OSImanagement with other infrastructures (e.g. COMA IDL and ODP functions) to be used, a

37、s the standards for them become available; to produce models that can be flexibly distributed amongst different management system architectures (e.g. using OS1 management, or distributed processing based systems); the work shall provide for maximum reusability of specifications and processing entiti

38、es; this work shall retain maximum compatibility with existing OS1 management based Recommendations and should be seen as an extension to that installed base. NOTE - Implementation independent enterprise, information and computational viewpoints are being defined by this methodology. In this way the

39、 definitions which are used for the definition of OS1 management, for example, are equally applicable to subsequent definitions using other infrastructures. Therefore, while the initial Recommendations which use this methodology will be targeted for the OS1 management infrastructure, the models defi

40、ned in these Recommendations for the enterprise, information and computational viewpoints will be independent of infrastructure. - - - 1.2 Principles The RM-ODP has been selected in order to provide a framework for a rigorous specification technique which is traceable to requirements. The selection

41、of techniques is guided by the objective of retaining maximum compatibility with OS1 management. Maintain compatibility with existing OS1 management based Recommendations (e.g. M.3 100, G.774-X, X.700-Series on OS1 Management, Q.821, Q.822, etc.). Maintain a balance between the requirements for huma

42、n readability, machine readability and precision (e.g. use of formal notations). This Recommendation should facilitate the interworking of applications based on implementations using different infrastructures. Recommendation G.851.1 (11/96) 1 STD-ITU-T RECMN G*85L-L-ENGL 199b D 48b257L Ub338b0 545 1

43、.3 Structure of this Recommendation Clause 2 lists the references used by this Recommendation; clause 3 contains definitions which have been introduced in this Recommendation; and clause 4 defines the abbreviations used. Clause 5 provides an overview of the methodology described in the remainder of

44、this Recommendation. Clauses 6, 7, 8 and 9 provide specific details of the RM-ODP viewpoints used in the methodology which includes the enterprise, information, computational and engineering viewpoints respectively. Clause 1 O describes the use of ensembles in the definition of network management ap

45、plications. Annexes A, B, C and D contain descriptions of the templates used to define the enterprise, information, computational and engineering viewpoints respectively. Annex E defines the labelling syntax used within the methodology, and Annex F describes the template used for defining a manageme

46、nt ensemble. Appendices I through V contain various examples of the application of the methodology to solving network management problems and ways of using the methodology to develop standard specifications. Appendix VI defines the mapping between the various RM-ODP viewpoints used in the methodolog

47、y. Appendix VI1 provides some guidelines for the use of Z in the information viewpoint. 2 References The following ITU-T Recommendations contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were val

48、id. All Recommendations 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. A list of the currently valid ITU-T Recommendations is regularly published. i ITU-T Recommendation X.9

49、011 I ISOlEC 10746-1 I, Information technology - Basic reference model of open distributedprocessing: Overview. 2 ITU-T Recommendation X.902 (1 995) I ISOIEC 10746-2: 1996, Information technology - Open Distributed Processing - Reference Model: Foundations. 3 ITU-T Recommendation X.903 (1 995) I ISOAEC 10746-3: 1996, Information technology - Open Distributed Processing - Reference Model: Architecture. 4 ITU-T Recommendation X.904l I ISO/IEC 10746-4, Information technology - Open Distributed Processing - Reference Model: Archtiectural semantics. 5