ITU-R S 1251-1997 NETWORK MANAGEMENT C PERFORMANCE MANAGEMENT OBJECT CLASS DEFINITIONS FOR SATELLITE SYSTEMS NETWORK ELEMENTS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SA.pdf

1、STD-ITU-R RECMN S.325L-ENGL 3797 4855232 0530578 Ob3 Rec. ITU-R S.1251 1 RECOMMENDATION ITU-R S.125 1 NETWORK MANAGEMENT - PERFORMANCE MANAGEMENT OBJECT CLASS DEFINITIONS FOR SATELLITE SYSTEMS NETWORK ELEMENTS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SATELLITE SERVICE (Question ITU-R 201/

2、4) ( 1997) The ITU Radiocommunication Assembly, considering a) that digital satellite systems will remain as constituents elements of publidprivate networks in a technologically independent way; b) c) should be reflected in to the management functionality definitions; d) multiplexing equipment which

3、 have to be measured and controlled via the management system; e) transport networks with which this Recommendation has to be compatible; 0 form the precedents for the object definitions in this Recommendation; g) mendation M.3000 is desirable; h) radio systems in SDH transport networks including th

4、eir management capabilities; j) that IT-T Recommendation G.707 (1996) specifies the Synchronous Digital Hierarchy (SDH); that ITU-T Recommendations G.803 and G.805 define the architecture of SDH transport networks which that ITU-T Recommendation G.783 specifies the general characteristics and functi

5、ons of synchronous that ITU-T Recommendations G.831 and G.784 define the management principles and capabilities of SDH that IT-T Recommendation G.774 defines the managed objects for terrestrial SDH transport networks which that compatibility with the Telecommunications Management Network (TMN) as de

6、fined in ITU-T Recom- that IT-T Recommendation G.861 defines the principles and guidelines for the integration of satellite and that Recommendation ITU-R S. 1 149 specifies aspects of satellite-based SDH transport networks, recommends that digital satellite systems in the fixed-satellite service (FS

7、S) comply with the management functionality defined in this Recommendation to facilitate their integration with SDH transport networks. 1 Scope The scope of this Recommendation is the definition of the performance management features of satellite specific SDH functions as defined in ITU-R Recommenda

8、tion S. 1 149 - 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 Recommendation is concer

9、ned with the lowest level details of the network management concept. This level is referred to as the “Network Element” level. STD-ITU-R RECMN S.125L-ENGL 3797 m 4855232 0530579 TTA m 2 1 2 3 4 5 6 7 8 Rec . ITU-R S.1251 CONTENTS Scope 1 . 1 1.1.1 Background . 1.1.2 Introduction to Performance Manag

10、ement (PM) Examples of performance parameters which may be captured by PM . The performance management model Description of object classes in the model Inheritance hierarchy for PM object classes . Performance management object class definitions in GDMO format ITU-T Recommendation 4.822 definitions

11、PM requirements list . 3.1 5.1 5.2 SDH technology specific object classes 5.2.1 IT-T Recommendations G.774-01 and 06 definitions 5.2.2 Satellite specific PM object classes . 5.3 Package defmitions . Supporting ASN . 1 Productions . Naming hierarchy for PM object classes 5.4 Atributes 5.5 6.1 Near en

12、d name bindings . 6.1.1 Naming policy . Far end name bindings 6.2.1 Naming policy . 6.2 6.3 Subordmation rules . Pointer constraints Name bindings for additional satellite multiplex hierarchy performance monitoring points . Page 1 2 2 2 3 5 7 7 9 9 10 10 12 22 23 27 27 27 28 30 30 35 35 35 1.1 Intro

13、duction to Performance Management (PM) 1.1.1 Background The definition of performance management for SDH transport systems is contained in IT-T Recommendation G.774 Part O1 and Part 06 . The satellite system object class definitions contained in this Recommendation are closely aligned with the lates

14、t unidirectional based version of G.774-06. ITU-T Recommendations G.774-01 and 06 are based upon IT-T Recommendation 4.822 “Stage 1. 2 and 3 Description for the 43 Interface. Performance Management” . 1.1.2 The following list contains examples of parameters which may be captured via the PM functions

15、 defined in this Recommendation . The list is not exhaustive and is not intended to limit the choice of parameters which a network operator may implement . - Errored seconds - Severely errored seconds . Unavailable seconds . Controlled slips . Threshold transgressions Examples of performance paramet

16、ers which may be captured by PM Separate parameters are recorded for the near end and the far end Separate parameters are recorded for the near end and the far end Separate parameters are recorded for the near end and the far end Separate parameters are recorded for the near end and the far end Sepa

17、rate parameters are recorded for the near end and the far end STD-ITU-R RECMN S-125L-ENGL L777 Li855212 0530580 71T 3 Rec. ITU-R S.1251 sdhCurrentData The conditions, under which any parameters are recorded, are important and the control of these conditions is included in the defmition of the PM fun

18、ctions. sdhCurrentDataUnidirectiona1 Use for new work 2 PM requirements list msCurrentDataTR The PM requirements list from ITU-T Recommendation G.774-01 is summarized below: - - - Supports PM event generation by Network Elements (NEs). Supports PM event collection from NEs by management systems. Sup

19、ports manager control of siartsuspend/resume/reset/stop of PM functions. msCurrentDataNearEndTR Use for new work - - - - Supports notification reports of PM collection from NEs to managers. Supports NE storage of results for delayed collection by managers. Supports historical data collection and sto

20、rage by NEs. Supports editing of this historical data. pathTerminationCurrentData - - Supports the changing of thresholds in NEs by managers. Supports the sending of Quality of Service (QoS) notifications from NEs when thresholds are crossed. pathTerminationCurrentDataNearEnd Use for new work pathTe

21、rminationCurrentDataFarEnd Continue to use These requirements are satisfied in the terrestrial environment defined by IT-T Recommendations G.774-01 and 06 by creating the SDH managed object classes listed in Table 1 which also shows the developments required to update the Recommendation from a bidir

22、ectional to a unidirectional basis. TABLE 1 ITU-T Recommendation G.774 terrestrial environment managed object classes r I I Revised ITU-T Recommendation G.774-06 (1 996) Comments I Existing ITU-T Recommendation G.774-01 Use for new work I msCurrentDataNearEnd I msCurrentData I Continue to use I msCu

23、rrentDataFarEnd I I Continue to use I msCurrentDataFarEndTR I I I I I I 4 Existing ITU-T Recommendation G.774-01 pathTerminationCurrentDataTR STD-ITU-R RECMN S.1251-ENGL 1797 i855212 U530583 b5b Revised ITU-T Recommendation G.774-06 (1996) Comments pathTenninationCurrentDataNearEndTR Use for new wor

24、k Rec. ITU-R S.1251 TABLE 1 (continued msHistoryDataFarEnd Continue to use I pathTerminationCurrentDataFarEndTR 1 pathTerminationHistoryData Continue to use pathTenninationHistory DataNearEnd pathTerminationHistory DataFarEnd Continue to use Use for new work msHistoryData rsSectionCurrentData Use fo

25、r near end PM only I Use for new work I msHistory DataNearEnd I rsSectionCurrentDataTR Use for near end PM only rsHistory Data Use for near end PM only msAdaptationCurrentData No change msAdaptationHistory Data No change The requirements list was considered to be sufficiently general to encompass th

26、e satellite environment apart from an additional requirement for different durations of recording intervals. It was considered to be necessary to create specific managed object classes to support the specialized satellite SDH equipment, and these object classes are listed in Table 2. satMSCurrentDat

27、aNearEnd TABLE 2 Satellite specific managed object classes msCurrentDataNearEnd Equivalent terrestrial object class I Satellite object class satMSCurrentDataNearEndTR I I msCurrentDataNearEndTR I sdhCurrentDataUnidirectiona1 I satSDHCurrentDataUnidirectiona1 I STDmITU-R RECMN S-1251-ENGL Satellite o

28、bject class satPathTermCurrentDataNearEnd 1997 Li855212 0530582 Equivalent terrestrial object class pathTerminationCurrentDataNearEnd 572 m satPathTermCurrentDataNearEndTR satMScurrentDataFarEnd Rec. ITU-R S.1251 pathTenninationCurrentDataNearEndTR rnsCurrentDataFarEnd TABLE 2 (continued) satMSCurre

29、ntDataFarEndTR msCurrentDataFarEndTR satP athTermCumntDataFarEndTR pathTerminationCurrentDataTR satPathTermCurrentDataFarEnd I pathTerminationCurrentDataFarEnd I I satPathTermHistory DataNearEnd satMSHistoryDataFarEnd satFathTermHistory DataFarEnd satMS AdaptCurrentData satMSAdaptHistory Data pathTe

30、rminationHistory DataNearEnd rnsHistory DataFarEnd pathTerrninationHistory DataFarEnd msAdaptationCurrentData msAdaptationHistory Data msHistory DataNearEnd I satMSHistory DataNearEnd I The full text of these satellite object class definitions, in GDMO format as defined in ITU-T Recommendation X.722

31、, follows the tables. All satellite specific object classes start with the letters “sat” to distinguish them from terrestrial object classes. Terrestrial SDH PM managed objects may be employed in SDH equipment located in satellite earth stations, particularly for the SDH functions near to the terres

32、trial interface. If the physical hardware is highly integrated, then managed objects from both environments might be deployed in the same piece of equipment. 3 The performance management model The performance management services are modelled as illustrated in Fig. 1. This shows current PM data being

33、 collected from a monitored Network Element (NE) via a currentData object for a defined period called the granularity period. At the end of each measurement period a summary report (scanReport) may be issued and the result is also forwarded to the historyData object. 6 t - STD-ITU-R RECMN S*L251-ENG

34、L 1997 W Li855212 0530583 429 Rec. ITU-R S.1251 Other granularity - History data - FIGURE 1 The performance management information model Network element 0 QoS alarm record Scan report record i I -, Communication port STD*ITU-R RECMN S-125l-ENGL 1997 q855232 053058Li 3b5 7 Rec. ITU-R S.1251 Threshold

35、s are controlled via thresholdData objects and when a threshold is transgressed a PM alarm may be generated by the currentData object issuing a notification message. All events may be logged for future reference in an eventRecord stored in the log function and any performance measurement may be stat

36、istically processed by the use of scanner objects. The scanner reports may include several types of content: e.g. a time series of measurements from one NE, or a number of measurements across a number of objects, or general statistics for single or multiple objects across single or multiple time ins

37、tances. CSES events are only managed in the sdhCurrentData subclass instances that employ 15 min granularity periods. This is to avoid information duplication. Bidirectional monitoring information which might be required for backward compatibility may be derived from the unidirectional measurements

38、so it is considered that there is no need for extra objects to provide bidirectional monitoring. 3.1 Description of object classes in the model The currentData object will be an instantiation of the object class of currentDataR1 and will perform the accumulation or other measurement of the parameter

39、 being monitored for the specified interval, called the granularity period. At the end of each interval the object will inform the corresponding historyData object of the result for storage. It may also emit a scanReport notification which may result in a corresponding event report being sent to a m

40、anaging system (it is not mandatory that the discriminator construct in the log be configured such that this notification is logged). The currentData object may contain a pointer to a thresholdData object if any of the thresholds are variable. When a threshold is transgressed a QoS alarm notificatio

41、n is sent to the managing system. This event may be logged. The historyData object contains a copy of the results for each granularity period. The thresholdData object contains a set of threshold values and is referenced from the currentData object by a pointer. There are several types of scanners d

42、efined in IT-T Recommendation X.738 and any of these may be used. The scanner function may be employed to aggregate sets of measurements from a number of currentData or historyData objects. The scanner may prepare a scanReport for bulk transfer of information to a managing system, or it may undertak

43、e some local processing to minimize the amount of data that needs to be transferred. e.g. derive mean values or calculate variances. The scanReport may also be stored in the log for future reference. The type of scanners which may be employed, for example, are; the simplescanner or the dynamicSimple

44、Scamer. Scanners which can perform calculations are; the meanscanner, the meanvariancescanner and the minMaxScamer. For detailed analysis of a difficult problem it may be better to access the historyData object directly rather than the derived statistics in the scanReport. Also the scanReport in the

45、 generic log may have been overwritten if a significant amount of time has passed or the log has had to accept a large number of entries. 4 Inheritance hierarchy for PM object classes The PM inheritance hierarchy for SDH transport systems is specialized for SDH technology as distinct from the genera

46、l PM hierarchy as defined in ITU-T Recommendation 4.822. 8 STD-ITU-R RECMN S-1251-ENGL 1997 H 9855232 0530585 2TL H Rec. ITU-R S.1251 FIGURE 2 The inheritance hierarchy for SDH PM I Scanner I I CurrentData I msCurrentDaaNearEnd L I msCurrentDataNearEndTR msCurrentDataFarEnd -1 msCurrentDataFarEndTR

47、I L I 1 pathTerminationCurrentData NearEnd I l I I I pathTerminationCurrentData NearEndTR I I 7 pathTenninationCurrentDaa I FarEnd pathTerminat ionCurrentData I FarEndTR tl history Data I I msHistoryDataNearEnd msHistory DataFarEnd L pathTerminationHistory Data NearEnd pathTerminationHistory Data Fa

48、rEnd I251-Q2 STD-ITU-R RECMN S.1251-ENGL 1797 Rec. ITU-R S.1251 9 5 IT-T Recommendation 4.822 (1994) contains the definitions of the basic object classes involved in PM i.e. currentData, thresholdData and historyData. These object definitions are reproduced here to assist with the comprehension of P

49、M but the reference source remains ITU-T Recommendation Q.822. Performance management object class definitions in GDMO format 5.1 IT-T Recommendation Q.822 definitions currentData MANAGED OBJECT CLASS DERIVED FROM CHARACTERIZED BY currentDataPkg PACKAGE BEHAVIOUR currentDataBehaviour BEHAVIOUR DEFINED AS “The currentData object class is a class of managed support objects that contain the current performance data. This object class is a particular type of scanner that scans its own attributes (see IT-T Recommendation X.739).