ITU-R S 1252-1997 NETWORK MANAGEMENT C PAYLOAD CONFIGURATION OBJECT CLASS DEFINITIONS FOR SATELLITE SYSTEM NETWORK ELEMENTS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SATE.pdf

1、 STD-ITU-R RECMN S.1252-ENGL L797 S 4855232 0530bL7 b31 = Rec. ITU-R S.1252 1 RECOMMENDATION ITU-R S.1252 NETWORK MANAGEMENT - PAYLOAD CONFIGURATION OBJECT CLASS DEFINITIONS FOR SATELLITE SYSTEM NETWORK ELEMENTS FORMING PART OF SDH TRANSPORT NETWORKS IN THE FIXED-SATELLITE SERVICE (Question ITU-R 20

2、114) (1 997) The IT Radiocommunication Assembly, considering that digital satellite systems will remain as constituent elements of public/private networks in a technology a) independent way; b) that IT-T Recommendation G.707 (1996) specifies the Synchronous Digital Hierarchy (SDH); c) should be refl

3、ected in the management functionality defmitions; that IT-T Recommendations G.803 and G.805 define the architecture of SDH transport networks which d) multiplexing equipment which have to be measured and controlled via the management system; that 1W-T Recommendation G.783 specifies the general chara

4、cteristics and functions of synchronous e) transport networks with which this Recommendation has to be compatible; that IT-T Recommendations G.831 and G.784 define the management principles and capabilities of SDH f, form the precedents for the object definitions in this Recommendation; that ITU-T R

5、ecommendation G.774 defines the managed objects for terrestrial SDH transport networks which g) mendation M.3000 is desirable; that compatibility with the Telecommunications Management Network (TMN) as defined in ITU-T Recom- h) radio systems in SDH transport networks including their management capa

6、bilities; that ITU-T Recommendation G.861 defines the principles and guidelines for the integration of satellite and .i) that Recommendation ITU-R S. 1 149 specifies aspects of satellite-based SDH transport networks, recommends that digital satellite systems in the FSS comply with the management fun

7、ctionality defined in this Recommendation to facilitate their integration with SDH transport networks. 2 I 2 3 4 8 Rec. ITU-R S.1252 CONTENTS Page 2 Scope of this Recommendation Introduction to payload configuration Consideration of satellite operational scenarios 2.1 Satellite specific payloads . 2

8、.2 2.2.1 Scenario 1 2.2.2 Scenario 2 modifiableSatVC3AsymTTPSource . modifiableSatVC3AsymTTPSink . 2.2.3 Scenario 3 - payload configuration . Attributes 14 Actions . 15 4.1 Definition of satellite VC-3 structure for scenario 2 applications . 15 4.2 Definition of satellite TUG structure 16 4.3 Defini

9、tion of client type 17 Notifications . 17 Parameters 17 Name bindings 17 7.1 Name binding definitions 18 Flexibility for growth . 19 Supporting ASN. 1 - Productions . 19 1 Scope of this Recommendation This Recommendation deals with satellite specific payload configuration. Payload configuration deal

10、s with the control of the adaptation functions which sit between the layers of the SDH architecture, see ITU-T Recommendation G.805. It does not cover the control of SDH cross-points which come under the “fabric” managed object class. 2 Introduction to payload configuration The existing terrestrial

11、Recommendation on this subject is ITU-T Recommendation G.774-02 (1 993). This was extensively revised in 1996 with many of the object classes being updated to Revision 1 status, indicated by adding R1 to the end of the object class name. This Recommendation follows the 1996 practice. Traditional ter

12、restrial SDH payload configuration operations may be applied to the terrestrial SDH adaptation functions which might be found in satellite earth stations. 2.1 Satellite specific payloads Specialized adaptation equipment functions have been defined in Recommendation IT-R S. 1 I49 to support asymmetri

13、c and point-to-multipoint working in satellite systems and this Recommendation defines the corresponding payload configuration management object classes to control these specialized adaptation functions. This Recommendation is concerned with the lowest level details of the network management concept

14、. This level is referred to as the “Network Element” level. STD-ITU-R RECMN S-1252-ENGL 1997 4855232 0530bL9 4OLi Rec. ITU-R S.1252 3 One objective is to ensure that these features are compatible with terrestrial SDH transport network management systems. STD-ITU-R RECMN S-1252-ENGL 1997 m q855212 05

15、30b20 L2b Transport signal STM-O (5 1M) 4 Rec. ITU-R S.1252 Possible signai components Several receive, STM-O format, signals may be supported. Total traffic must fit into an STM-O One AU-3 = VC-3 2.2 The satellite SDH operational scenarios are defined in Recommendation ITU-R S.1149. Consideration o

16、f satellite operational scenarios 2.2.1 Scenario 1 Scenario 1 employs a standard terrestrial payload, STM-1, in a standard terrestrial manner and therefore does not require payload configuration applied to its Higher Order Satellite Section Adaptation (HSSA) function. 2.2.2 Scenario 2 Scenario 2 emp

17、loys a standard STM-O (51M) signal format in both directions of transmission but with asymmetric loading of the multiple receive direction signals compared to the transmit direction signal. Multiplexing and demultiplexing of Lower Order Virtual Containers (LOVCs) (VC-2, VC-12) and possibly Higher Or

18、der Virtual Container (HOVC) (VC-3) and asymmetry reconciliation are performed in the Higher Order Satellite Path Adaptation (HSPA) function which is a satellite specific function. Therefore, a specialized payload configuration control method had to be defined. TABLE 1 Scenario 2 -Arrangements I One

19、 to seven - TUC- STD-ITU-R RECMN S.1252-ENGL 1997 4855232 0530b2L Ob2 5 Rec. ITU-R S.1252 DEFINED AS ?This object class models the process of controlling the Adaptation function HSPA located between the lower order path connection LPC-m, in scenario 2, and the corresponding Higher Order Satellite Pa

20、th Termination (HSPT). Scenarios are defmed in Recommendation ITU-R S. 1 149. The Adaptation functionality may be different between transmit and retum directions to support asymmetric and point to multipoint operation.?; ATTRIBUTES satVC3AsymTPSouceStcture GET, clientTypeStructure GET; ACTIONS defin

21、eClientTypeStructure; ; ; REGISTERED AS (rRecS.1252MObjectClass O1 1; moifiableSatVC3AsymTTPSink modifiableSatVC3AsymTTPSink MANAGED OBJECT CLASS DERIVED FROM CHARACTERIZED BY ?ITLJ-T Recommendation M.3 100?:supportableClientListPackage, modifiableSatVC3AsymTTPSinkPackage PACKAGE BEHAVIOUR modifiabl

22、eSatVC3AsymTPSinkBehaviour BEHAVIOUR DEFINED AS ?Recommendation IT-R S. 1250?: satVC3AsymTTPSink; ?This object class models the process of controlling the Adaptation function HSPA located between the lower order path connection LPC-rn, in scenario 2, and the corresponding Higher Order Satellite Path

23、 Termination (HSPT). Scenarios are defined in Recommendation IT-R S. 1 149. The Adaptation functionality may be different between transmit and return directions to support asymmetric and point to multipoint operation.?; ATTRIBUTES satVC3AsymTTPSinkStcture GET, clientTypeStructure GET; ACTIONS define

24、SatVC3AsymTTPSinkStructure, defmeClientTypeStructure; ; ; REGISTERED AS rRecS. 1252MObjectClass 02); 2.2.3 Scenario 3 - payload configuration The information model for the payload configuration process is based upon the signal structures. This part of the Recommendation defines those subclasses whic

25、h are special to scenario 3 satellite systems as defined in Recommendation IT-R S.1149. Extensions to the following definitions will be possible by simply incorporating new items in the ASN.1 Productions listing rather than requiring the development of new subclasses. 6 STD-ITU-R RECMN SaL252-ENGL 1

26、777 Rec. ITU-R S.1252 4855232 0530b22 TT Note that terrestrial object classes covering configuration actions, which may e used on the terrestrial ; MANAGED OBJECT CLASS “Recommendation ITU-R S. 1250“: satLSAdaptSource; STD-ITU-R RECMN S.1252-ENGL 3777 4855232 0530b25 708 M 9 Rec. ITU-R S.1252 ATTRIB

27、UTES ACTIONS REGISTERED AS rRecS. 1252MObjectClass 03); clientTypeStructure GET; defmeClientTypeStructure; ; ; modifiableSatTUG11AdaptSink modifiableSatTUG 1 1 AdaptSink DERIVED FROM CHARACTERIZED BY “ITU-T Recommendation M.3 1 OO“:supportableClientListPackage, modifiableSatTUG 1 1AdaptSinkPackage P

28、ACKAGE BEHAVIOUR modifiableSatTUG 1 1 AdaptSinkBehaviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower order path connection LPC-rn, in scenario 3, and the corresponding satellite section termination (SST). Scenarios are d

29、efmed in Recommendation ITU-R S.1149. The Adaptation functionality may be different between transmit and return directions to support asymmetric and point to multipoint operation.“; ATTRIBUTES ACTIONS REGISTERED AS rRecS. 1252MObjectClass 04); MANAGED OBJECT CLASS “Recommendation ITU-R S. 1250“: sat

30、LSAdaptSink; clientTypeStructure GET; defmeClientTypeStructure; ; ; modifiableSatTUG 12AdaptSource modifiableSatTUG 12AdaptSource MANAGED OBJECT CLASS DERIVED FROM CHARACTERIZED BY “ITU-T Recommendation M.3 1 OO“:supportableCIientListPackage, modifiableSatTUG12AdaptSourcePackage PACKAGE BEHAVIOUR mo

31、difiableSatTUG12AdaptSourceBehaviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower order path connection LPC-m, in scenario 3, and the corresponding satellite section termination (SST). Scenarios are defined in Recommendat

32、ion ITU-R S.1149. The Adaptation functionality may be different between transmit and return directions to support asymmetric and point to multipoint operation.“; ATTRIBUTES ACTIONS REGISTERED AS rRecS. 1252MObjectClass 05); “Recommendation ITU-R S. 1250“: satLSAdaptSource; clientTypeStructure GET; d

33、efineClientTypeStructure; ; modifiableSatTUG12AdaptSink modifiableSatTUG 12AdaptSink MANAGED OBJECT CLASS DERIVED FROM CHARACTERIZED BY “ITU-T Recommendation M.3 lOO“:supportableClientListPackage, modifiableSatTUG 12AdaptSinkPackage PACKAGE “Recommendation ITU-R S. 1250“: satLSAdaptSink; STD-ITU-R R

34、ECMN S-LZ52-ENGL 1777 Y855212 0530b2b b4Lt 9 10 Rec. ITU-R S.1252 BEHAVIOUR modifiableSatTUG12AdaptSinkBehaviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower order path connection LPC-m, in scenario 3, and the correspondi

35、ng satellite section termination (SST). Scenarios are defined in Recommendation IT-R S. 1 149. The Adaptation functionality may be different between transmit and return directions to support asymmetric and point to multipoint operation.“; ATTRIBUTES clientTypeStructure GET; defuieClientTypeStructure

36、; ; ; ACTIONS REGISTERED AS (rRecS. 1252MObjectClass 06); modifiableSatTUG21AdaptSource modifiableSatTUG2 1 Adaptsource DERIVED FROM CHARACTERIZED BY “ITU-T Recommendation M.3 1 OO“:supportableClientListPackage, modifiableSatTUG2 1 AdaptSourcePackage PACKAGE BEHAVIOUR modifiableSatTUG21AdaptSourceBe

37、haviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower order path connection LPC-m, in scenario 3, and the corresponding satellite section termination (SST). Scenarios are defined in Recommendation ITU-R S.1149. The Adaptat

38、ion functionality may be different between transmit and return directions to support asymmetric and point to multipoint operation.“; ATTRIBUTES MANAGED OBJECT CLASS “Recommendation ITU-R S. 1250“: satLSAdaptSource; satTUG2 1 AdaptSourceStructure GET, clientTypeStructure GET; defineSatTUG2 1 AdaptSou

39、rceStructure, defmeClientTypeStructure; ; ; ACTIONS REGISTERED AS (rRecS. 1252MObjectClass 07); modifiableSatTUG21AdaptSink modifiableSatTUG2 1 Adaptsink DERIVED FROM CHARACTERIZED BY “IT-T Recommendation M.3 1 OO“:supportableClientListPackage, modifiableSatTUG2 1 AdaptSinkPackage PACKAGE BEHAVIOUR

40、modifiableSatTG2 1 AdaptSinkBehaviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower order path connection LPC-m, in scenario 3, and the corresponding satellite section termination (SST). Scenarios are defined in Recommenda

41、tion ITU-R S. 1149. The Adaptation functionality may be different between transmit and return directions to support asymmetric and point to multipoint operation.“; MANAGED OBJECT CLASS “Recommendation ITU-R S. 1250“: satLSAdaptSink; STD-ITU-R RECMN S-1252-ENGL 1777 m 4855232 0530b27 580 m Rec. ITU-R

42、 S.1252 11 ATTRIBUTES satTG2 1 AdaptSinkSucture GET, ClientTypeStructure GET; defmeSatTG2 1 AdaptSinkStructure defineClientTypeStructure; ; ; ACTIONS REGISTERED AS rRecS. 1252MObjectClass 08); modifiableSatTUG22AdaptSource modifiableSatTG22AdaptSource MANAGED OBJECT CLASS DERIVED FROM CHARACTERIZED

43、BY “IT-T Recommendation M.3 1 OO“:supportableClientListPackage, modifiableSatTG22AdaptSourcePackage PACKAGE BEHAVIOUR modifiableSatTG22AdaptSourceBehaviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower order path connectio

44、n LPC-my in scenario 3, and the corresponding satellite section termination (SST). Scenarios are defined in Recommendation ITU-R S.1149. The Adaptation functionality may be different between transmit and retuni directions to support asymmetric and point to multipoint operation.“; ATTRIBUTES “Recornm

45、endation IT-R S. 1250“: saLSAdaptSource; satTG22AdaptSourceStructure GET, clientTypeStructure GET; defuieSatTUG22AdaptSourceStructure, defineClientTypeStructure; ; ; ACTIONS REGISTERED AS rRecS. 1252MObjectClass 09); modifiableSatTUG22AdaptSin k modifiableSatTG22AdaptSink MANAGED OBJECT CLASS DERIVE

46、D FROM CHARACTERIZED BY “IT-T Recommendation M.3 1 OO“:supportableClientListPackage, modifiableSatTUG22AdaptSinkPackage PACKAGE BEHAVIOUR modifiableSatTG22AdaptSinkBehaviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower or

47、der path connection LPC-m, in scenario 3, and the corresponding satellite section termination (SST). Scenarios are defined in Recommendation IT-R S.1149. The Adaptation functionality may be different between transmit and return directions to support asymmetric and point to multipoint operation.“; AT

48、TRIBUTES “Recommendation IT-R S. 1250“: satLSAdaptSink; satTG22AdaptSinkStructure GET, clientTypeStructure GET; defineSatTG22AdaptSinkStructure defineClientTypeStructure; ; ; ACTIONS REGISTERED AS rRecS. 1252MObjectClass 10); STD-ITU-R RECMN S-1252-ENGL 1777 = 4855232 0530b28 qL7 12 Rec. ITU-R S.125

49、2 modifiableSatTUG23AdaptSouree modifiableSatTG23AdaptSource MANAGED OBJECT CLASS DERIVED FROM CHARACTERIZED BY “ITU-T Recommendation M.3 1 OO“:supportableClientListPackage, modifiableSatTUG23AdaptSourcePackage PACKAGE BEHAVIOUR modifiableSatTG23AdaptSourceBehaviour BEHAVIOUR DEFINED AS “This object class models the process of controlling the Adaptation function located between the lower order path connection LPC-m, in scenario 3, and the corresponding satellite section termination (SST). Scenari