ITU-R S 1250-1997 NETWORK MANAGEMENT ARCHITECTURE FOR DIGITAL SATELLITE SYSTEMS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SATELLITE SERVICE《形成SDH传送网部分的固定卫星业务的数字卫星系统的网络结构》.pdf

《ITU-R S 1250-1997 NETWORK MANAGEMENT ARCHITECTURE FOR DIGITAL SATELLITE SYSTEMS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SATELLITE SERVICE《形成SDH传送网部分的固定卫星业务的数字卫星系统的网络结构》.pdf》由会员分享，可在线阅读，更多相关《ITU-R S 1250-1997 NETWORK MANAGEMENT ARCHITECTURE FOR DIGITAL SATELLITE SYSTEMS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SATELLITE SERVICE《形成SDH传送网部分的固定卫星业务的数字卫星系统的网络结构》.pdf（68页珍藏版）》请在麦多课文档分享上搜索。

1、 STD-ITU-R RECMN S.1250-ENGL 1777 m 4855232 0530510 3Tb m 1 Rec. ITU-R S.1250 RECOMMENDATION ITU-R S.1250 NETWORK MANAGEMENT ARCHITECTURE FOR DIGITAL SATELLITE SYSTEMS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SATELLITE SERVICE (Question IT-R 20114) (1 997) The ITU Radiocommunication Assem

2、bly, considering a) that digital satellite systems will remain as constituents elements of public/private networks in a technologically independent way; b) that ITU-T Recommendation G.707 (1996) specifies the Synchronous Digital Hierarchy (SDH); c) should be reflected in the management functionality

3、 definitions; d) multiplexing equipment which have to be measured and controlled via he management system; e) transport networks with which this Recommendation has to be compatible; that ITU-T Recommendations G.803 and G.805 define the architecture of SDH transport networks which that ITU-T Recommen

4、dation G.783 specifies the general characteristics and functions of synchronous that IT-T Recommendations G.831 and G.784 define the management principles and capabilities of SDH 9 form the precedents for the object definitions in this Recommendation; g) that compatibility with the Telecommunication

5、s Management Network (TMN) as defined in IT-T Recommendation M.3000 is desirable; that IT-T Recommendation G.774 defines the managed objects for terrestrial SDH transport networks which h) radio systems in SDH transport networks including their management capabilities; j) Recommendation is based, th

6、at ITU-T Recommendation G.861 defmes the principles and guidelines for the integration of satellite and that Recommendation IT-R S.1149 specifies the satellite specific SDH transport system upon which this recommends that digital satellite systems in the fixed-satellite service (FSS) comply with the

7、 management functionality defined in this and associated Recommendations to facilitate their integration with international SDH transport networks. 1 Scope The scope of this Recommendation is the definition of Network-Element-management features for satellite specific SDH functions as defined in Rec

8、ommendation ITU-R S.1149 “Network Architecture and Equipment functional aspects of Digital Satellite Systems in the FSS forming part of SDH Transport Networks”. One objective is to ensure that these features are compatible with terrestrial SDH Transport Network management systems. This Recommendatio

9、n is concerned with the lowest level details of the Telecommunications Management Network (TMN) concept. This level is referred to as the “Network Element” level. 2 1 2 3 4 5 6 7 STD-ITU-R RECMN S.L250-ENGL 1. 997 E 4855232 05305LL 232 Rec . ITU-R S.1250 CONTENTS Page Scope 1.1 Introduction . 1.2 Me

10、thodology . 1.3 Object background 1.4 Structure of the Recommendation 1.5 Abbreviations 1.6 Definitions Alternative management systems . 2.1 2.2 2.3 Discussion of network management concepts 2.1.1 TheMIB The IETF approach, the SNMP The ITU and KOs TMN management approach . 2.3.1 Principles of TMN .

11、2.3.2 TMN management services . TMN management communication services . Separation from underlying communications . Interactions with Operations, Administration and Maintenance (OA the required attributes visible at its boundary (one or more interfaces), - - There is no requirement for a one-to-one

12、mapping between real resources and the managed objects which represent them. A real resource may be represented by one or several managed objects. Managed objects can be embedded in other managed objects. If a resource is not represented by a managed object then it cannot be managed by the managemen

13、t system as it is effectively invisible. The details of the functional architecture of TMN can be found in Annex B. 2.3.2 TMN management services Telecommunications management is the integration of the management of several telecommunication managed areas of a service provider to maximize the overal

14、l quality of service provided to the customers by maximizing the productivity of the resources of the service provider. Thus the business objective of telecommunications management is to continually improve the quality of service delivered to the customer by improving the productivity of the operati

15、ons of the service provider. TMN management services are defined as a matrix of service components as illustrated in Table 3 which is taken from IT-T Recommendation M.3200 1992 - TMN Management Services Overview. it exhibits the required behaviour to defined stimuli; it emits the required notificati

16、ons when the defined events take place. e.g. a threshold is crossed. TABLE 3 TMN management services template Functional a area Fault Layer 1. Business 2. Service management management 3. Network 4. Network Element management If Others C e Performance I Security I Accounting ITU-T Recommendation G.7

17、74 only deals with the lowest network element management layer. The revised ITU-T Recommendation M.3200 “TMN Management Services” dated April 1995 expanded the five areas of management (performance, fault, configuration, accounting and security management) to include several other areas as detailed

18、below. The latest text will be adopted for this Recommendation. STDmITU-R RECMN S-1250-ENGL 1797 YA55212 0530517 523 10 Rec. IT-R S.1250 2.3.2.1 List of management services The following list of management services have been identified; - Customer administration - Network provisioning management - W

19、ork force management - - - Tariffs, charging and accounting administration Quality of service and network performance administration Traffic measurement and analysis administration - Traffic management - - Maintenance administration Routing and digit analysis administration - Security administration

20、 - Logistics management. NOTE 1 - The above list is not exhaustive and is meant only as a guide. NOTE 2 - Some management services may be too large to handle as a single service. NOTE 3 - Some definitions which are of interest to this Recommendation are reproduced below. 2.3.2.2 Management services

21、definitions 2.3.2.2.1 QoS degradation can be the result of many different causes such as design errors, under-dimensioning of resources and failures of components. When there is no testing coverage for some of these root causes then the only way to uncover them is by QoS monitoring or via the compla

22、ints of dissatisfied customers. Experience has shown that it can take several years to solve some deep rooted problems even with the best expertise available. Some common QoS degradations are hard-to-reach directions and poor transmission quality. ITU-T Recommenda- tions E.420-E.428 and E.800-E.880

23、explore this aspect of management. Techniques to improve the quality of the design process, called design reliability management, have recently been introduced (see similar techniques described in Recommendation M.20). Quality of service (QoS) and network performance management Traffic measurement a

24、nd analysis administration, see ITU-T Recommendations ES00 through E.720 and their supplements. Traffic management, see IT-T Recommendations E.410 through E.4 14. 2.3.2.3 Development from TMN management services TMN Management Services (MSs) are the starting point for the development of the TMN inte

25、rface specifications via the performance of Tasks 1 and 2 of the interface-definition methodology, using GDMS, as described in ITU-T Recommendation M.3020 “TMN Interface Specification Methodology”. 2.3.2.4 Management information processing Previous sections have defined the management environment in

26、 global terms, e.g. the employment of an object-oriented management information database. It is now necessw to define the interactions between these various management entities. Management of telecommunications systems is an information processing activity which is geographically distributed over a

27、very wide range of distances and a large number of terminals. STDaITU-R RECMN S-1250-ENGL 1797 m 4855212 0530520 245 Rec. ITU-R S.1250 11 2.3.3 Manager and agent roles The Management Application Function (MAF) can adopt one of two roles which are referred to as manager or agent. For any given activi

28、ty it is usually in one or other of these roles but there may be cases where it has to function in both roles simultaneously. 2.3.3.1 The manager role The part of the distributed application that issues directives, receives responses to its directives and also receives unsolicited notifications. 2.3

29、.3.2 The agent role The part of the application process that provides a front-end process to a collection of managed objects and generates the responses to directives from the manager and also issues unsolicited notifications about events detected by the resources under its control which are represe

30、nted as managed objects for the purpose of supporting the management function. In the general case managers and agents may be involved in “many-to-many” type relationships which is rather difficult to control as it raises difficulties about synchronization and concurrent and possibly conflicting dir

31、ectives. This issue is for further study. 2.4 TMN management communication services See Fig. 3 for a block diagram of TMN management communications. FIGURE 3 Management communications Managing system Manager MIB System under management hI Communications /I . i I Directives Responses Notifications i/

32、 I Agent os O Local environment O MIB objects O0 Y r I 2.5 Separation from underlying communications The separation of the management communication from any underlying communication protocol is considered to be beneficial for several reasons: - - - - - Therefore this Recommendation does not call for

33、 any underlying protocol requirements. it will make integration of these new management concepts into existing management systems much easier; it will facilitate the interoperation of the two types of management systems; it will allow greater flexibility in solving any communication access problem c

34、aused by any fault condition; it avoids translation between the two management systems at the private/public network boundary; it avoids some duplication of objects and object classes. 12 Rec. ITU-R S.1250 3 Interactions with Operations, Administration and Maintenance (OATPSource tu2CTPSource tdCTPS

35、ource “CdJdhonlCIPSouu msTTPSink rsTTPSink vcl IITpsink vcl2TPSink vc2TPSink vc3TPSink slcemcal.wITIpsiaL G.774 I I G.774 msTTPSource rsTTPSource vcllTTPSoue vcl2TFSource vcZTPSource vc3TFSource vc4“Source *llTmsaicc adaptor G.774 G.774 augBidirectional augSink augSource tug2Source tug2Sink hig3Bidi

36、recional tug3Source tug3Sink tug2BidirectionaJ S.1250 stugl 1 Source stugl 1 Sink stugl2Source stugl2Sink stug2 1 Source stug2 1 Sink r stug22Source stug22Sink NOTE 1 -The object classes in the lower G.774 and S.1250 boxes are all at the same levei of the hierarchy. f23Q-04 - STD-ITU-R RECMN S*Li!SO

37、-ENGL 1997 = 4855232 0530524 990 9 Object Class Rec. ITU-R S.1250 15 Functionality 4.1.2 Summary of functions by generic object class The following list is abstracted from the object class definitions of the latest version of IT-T Recommendation M.3 100. Conditional features are shown in brackets on

38、ly if they remain as conditional and have not been selected as mandatory for deployment in the satellite transport network management environment. Activating conditional features usually results in more notification messages which may cause overloading of management communication facilities in some

39、situations. TABLE 5 Functions of object classes networkId, userlabel. Network R1 systemTitle. I Managed Element Complex managedElementComplexId, systemTitle, createDeleteNotifications. I I I l Managed Element managedElernentId, sy stemTide, alarmstatus, I I administrativestate, operationalstate, usa

40、gestate, environmentalAlam, equipmentAlam, communicationsAlarm, processingErrorAlarm, I createDeleteNotification, -I (attributeValueChangeNotification), (stateChangeNotification), (audibleVisualLocalAlarm), (resetAudibleAlarm), userlabel, (vendorName), (version), (locationName), currentProblemList,

41、extemalTime, sy sternTiming Source. 16 Object Class STD-ITU-R RECMN S.1250-ENGL 1777 = 4855212 0530525 827 H Functionality Rec. ITU-R S.1250 L Termination Point supporedBy ObjectList, createDeleteNotifications. TABLE 5 (continued) Managed Element R1 environmentalAlam, IofiecordIdParameter. I correla

42、tedRecordNameParameter, I susDectobiectlistPaeter. equipmentAlm, IogRecordIdParameter, correlatedRecordNameParameter. I suspectObjectlistParameter, I communicationsAiarm. I logRecordIdFarameter, correlatedRecordNameParameter, susoectObiectListParameter. processingEmrAlarm, IogRecordIdParameter, corr

43、elatedRmrdNameParameter, suspectObjecListParameter, alarmSeverityAssignmentPointer. I (attributeValueChangeNotification), I fstateChaneeNotificationk operationalStae, crossComeciionPointer, tmnCommunicaionsAlarmInformation. I alarmSeverityAssignmentPointer. I Trail Temination Point Sink I I uostream

44、connectivitvpointer. I I administrativestate, I suDDortabieCiientList. downstreamConnectivity Pointer, administrativestate, supportableClientList. Connection Termination Point Source I I uostreamconnectivitvpointer. I CTPUUpstreamPointer, (ctphstance), (channelNumber). Connection Termination Point S

45、ink I I downstreamConnectivitvPointer. I I I CTPUDownstreamPointer, (ctphtance), (channelNumber). - STD-ITU-R RECMN S*L250-ENGL 1797 W Y855212 053052b 7b3 Rec. ITU-R S.1250 17 . userlable, vendorName, TABLE 5 (continued) Object Class Object Deletion Record, Management Operations Scheduler, Functiona

46、lity Equipment equipmentId, replaceable, (createDeleteNotifications), (attributeVaiueChangeNotification), I (stateChangeNotification), I (administrativeOperationaiStates), affectedobjectlist, environmentAlm. tmnCommunicationsAlarmInformation, processingErrorAiarm, I version, I locationName. currentP

47、roblemList. Equipment RI serialNumber, supportedBy ObjectsList, alarmSeverityAssignmentPointer, equiprnentsEquipmentAlarmR1, processing EiTorAlmR1, environmentaiAlmR1, processingErrorAlarmR1. General Management Support Alarm Severity Assignment Profile, I- I Attribute Value Change Record. I I I Alar

48、mRecord, l Discriminator, Event Forwarding Discriminator, Event Log Record, Log, Log Record, State Change Record, I I Obiect Creation Record, I I Current AI Summary Control. I 5 SDH object classes The inheritance structure and naming tree for SDH specific management object classes are defined in ITU

49、-T Recommendation G.774 and are shown in Fig. 5. 18 SPI TTP RS “P STD-1TU-R RECMN S-125D-ENGL 1797 4855232 0530527 bTT 9 Rec. ITU-R S.1250 FIGURE 5 Naming tree for G.774 SDH object classes MS TTP VC-4 TTP VC-3 TTP VC-2 TTP VC-11 TTP VC-12 TTP mms 5.1 Table 6 is abstracted from IT-T Recommendation G.774-01 and contains examples of SDH specific object classes for administration events and alarm conditions. Summary of facilities and alarms contained in SDH object classes TABLE 6 A