ITU-T Q 816 2-2007 CORBA-based TMN services Extensions to support service-oriented interfaces《基于公共对象请求代理架构(CORBA)的电信管理网(TMN)设备 支持设备导向接口的扩展件 研究组4》.pdf

《ITU-T Q 816 2-2007 CORBA-based TMN services Extensions to support service-oriented interfaces《基于公共对象请求代理架构(CORBA)的电信管理网(TMN)设备 支持设备导向接口的扩展件 研究组4》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 816 2-2007 CORBA-based TMN services Extensions to support service-oriented interfaces《基于公共对象请求代理架构(CORBA)的电信管理网(TMN)设备 支持设备导向接口的扩展件 研究组4》.pdf（70页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Q.816.2TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2007) SERIES Q: SWITCHING AND SIGNALLING Q3 interface CORBA-based TMN services: Extensions to support service-oriented interfaces ITU-T Recommendation Q.816.2 ITU-T Q-SERIES RECOMMENDATIONS SWITCH

2、ING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5,

3、 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE M

4、OBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000

5、Q.3999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.816.2 (03/2007) i ITU-T Recommendation Q.816.2 CORBA-based TMN services: Extensions to support service-oriented interfaces Summary ITU-T Recommendation Q.816.2 defines a set of TMN CORBA services required to

6、support service-oriented interfaces. It specifies how the ORB and common object services should be used in a lightweight fashion for supporting service-oriented interfaces, and defines extensions to the TMN-specific support services defined in ITU-T Recommendations Q.816 and Q.816.1. A CORBA IDL mod

7、ule defining the interfaces to the new TMN-specific support services is provided. The new services and the lightweight use of other CORBA services, along with ITU-T Recommendation X.780.2, compose a framework for CORBA-based service-oriented TMN interfaces with a wide range of applications. Source I

8、TU-T Recommendation Q.816.2 was approved on 16 March 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. Keywords Common object request broker architecture (CORBA), CORBA services, distributed processing, faade, interface definition language (IDL), managed object, m

9、anaged system, managing system, service orientation, service-oriented faade object, TMN interface. ii ITU-T Rec. Q.816.2 (03/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardi

10、zation Sector (ITU-T) is a permanent organ of ITU. 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 Assembly (WTSA), which

11、meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-

12、Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation

13、is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“

14、and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may i

15、nvolve the use of a claimed Intellectual Property Right. 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 R

16、ecommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent databas

17、e at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Q.816.2 (03/2007) iii CONTENTS Page 1 Scope 1 1.1 Purpose . 2 1.2 Application . 2 2 References. 3 3 Definit

18、ions 5 4 Abbreviations 7 5 Conventions 10 6 Service-oriented interface design considerations . 10 6.1 Flexible use of faade design pattern . 11 6.2 Lightweight use of ORB. 12 6.3 Use of session service by managed and managing systems . 15 6.4 Lightweight use of naming service. 15 6.5 Lightweight use

19、 of notification service 18 6.6 Lightweight use of telecom log service 20 6.7 Relationship to coarse-grained interface design considerations. 22 7 Service-oriented framework and requirements overview. 22 7.1 Framework overview 22 7.2 Framework constituents overview 24 7.3 Relationships between servi

20、ce-oriented, coarse-grained and fine-grained frameworks. 30 8 Framework ORB and common object services usage requirements for supporting service-oriented interfaces 32 8.1 ORB usage requirements 33 8.2 Naming service. 33 8.3 Notification service 34 8.4 Telecom log service 40 8.5 Concurrency control

21、and object transaction services . 41 8.6 CORBAsecurity 42 9 Framework support services requirements for supporting service-oriented interfaces. 44 9.1 Session service 44 9.2 Other ITU-T support services. 49 10 Service-oriented compliance and conformance 49 10.1 Standards document compliance 49 10.2

22、System conformance 50 10.3 Conformance statement guidelines. 53 iv ITU-T Rec. Q.816.2 (03/2007) Page Annex A Service-oriented framework support services IDL 54 A.1 Module idlVersion . 55 A.2 Module session 55 A.3 Module nmsSession . 56 A.4 Module emsSession . 58 A.5 Module emsSessionFactory . 59 Bib

23、liography. 61 ITU-T Rec. Q.816.2 (03/2007) 1 ITU-T Recommendation Q.816.2 CORBA-based TMN services: Extensions to support service-oriented interfaces 1 Scope The TMN architecture defined in ITU-T Rec. M.3010 (2000) introduces concepts from distributed processing and includes the use of multiple mana

24、gement protocols. ITU-T Recs Q.816 and X.780 subsequently define within this architecture a framework for applying the common object request broker architecture (CORBA) as one of the TMN management protocols. In this approach, manageable network resources are modelled as software objects accessible

25、using CORBA. Information models written in the CORBA interface definition language (IDL) describe the object interfaces. In the original CORBA TMN framework, each managed object class (MOC) is a CORBA IDL interface and so each manageable resource is an independent CORBA object identified and accesse

26、d by an interoperable object reference (IOR) that allows for location-transparency. CORBA-based TMN interfaces using the approach where each manageable resource is addressable with a unique IOR have become known as “fine-grained“ interfaces. This approach flexibly allows each managed object to resid

27、e anywhere but at the expense that managing systems have on hand an IOR for each managed object they wish to access. CORBA-based TMN interfaces where not an IOR need be assigned to each manageable resource have become known as “coarse-grained“ interfaces. A coarse-grained TMN interface exposes a coa

28、rser level of abstraction between a managing system and a managed system for accessing manageable resources but without loss of any detail. At a coarse-grained TMN interface a CORBA object (with an IOR), which is used to access manageable resources having no IOR and invoke operations on them, is ref

29、erred to as a faade, while an object that is accessed through a faade is referred to as a lightweight object. ITU-T Recs Q.816.1 and X.780.1 extend the framework to support coarse-grained interfaces where one or more faades are defined for each MOC. This Recommendation, along with ITU-T Rec. X.780.2

30、, add specifications to the framework to enable it to support a service-oriented style of interaction between managing systems and managed systems in addition to the fine-grained and coarse-grained styles specified in the other framework documents. This style of interaction has certain benefits. For

31、 example, it can relieve a managing system from having to separately retrieve an identifier or a location information for each type or even each instance of manageable resource it wishes to access, and it can provide a more efficient and very flexible separation of behaviour and state of managed obj

32、ects. By introducing the so-called “service-oriented faades“ it also changes somewhat the way software may be structured on the managed systems, a flexibility which some managed system suppliers may prefer. The service-oriented framework adopts a lightweight specific use of CORBA to maximize interop

33、erability and interface performance. As a consequence, the use of the naming service can be minimalistic and the use of the ORB and all common object services is lightweight by nature. A service-oriented architecture (SOA) is an architectural style that aims at maximizing service sharing, reuse and

34、interoperability in distributed environments through loose coupling among interacting components that expose their behaviour through interfaces. In anticipation of the frequent discovery of new business opportunities or threats, an SOA aims at providing open and agile business solutions that can rap

35、idly extend or change on demand, and so SOA-based solutions are composed of reusable services with published and standards-compliant interfaces. The service-oriented approach to CORBA interface design is intended to support efficient SOA interfaces and allow for growth and change as technologies and

36、 services are evolving. 2 ITU-T Rec. Q.816.2 (03/2007) The scope of this Recommendation is the same as the fine-grained and coarse-grained TMN CORBA frameworks. These frameworks and the service-oriented extensions cover all interfaces in the TMN where CORBA may be used. These interfaces are OS-OS in

37、terfaces according to ITU-T Rec. M.3010, where one OS takes a client/manager role (e.g., an NMS) and the other OS takes a server/agent role (e.g., an EMS). To be concrete, the service-oriented framework support services IDL of Annex A refers to an NML-EML interface but it can be applied to any manag

38、ing system and managed system. It is expected, however, that not all capabilities and services defined here are required in all TMN interfaces. This implies that the framework can be used for interfaces between management systems at all levels of abstractions (inter- and intra-administration at vari

39、ous logical layers) as well as between management systems and network elements. 1.1 Purpose The purpose of this Recommendation and the companion ITU-T Rec. X.780.2 is to extend the TMN CORBA framework to enable it to be used in a wider range of applications. The extensions enable a lightweight mode

40、of interaction between the managing and managed systems which may be preferred in many situations. They also enable the endorsement of de facto CORBA services and information models usage which are recognized in the telecommunications industry. Thus, this Recommendation is intended for use by variou

41、s groups specifying network management interfaces. 1.2 Application ITU-T Rec. X.780.2 accompanies this Recommendation and extends the object modelling guidelines, the superclasses, and the standard sets of data types, exceptions, notifications and constants defined in ITU-T Recs X.780 and X.780.1. C

42、ollectively, ITU-T Rec. X.780.2 and this Recommendation define a framework for CORBA-based service-oriented TMN interfaces. ITU-T Rec. M.3010 provides, in its Amendment 1 (2003), conformance definitions for TMN interfaces between physical blocks. When CORBA is used as the TMN management protocol, th

43、e conformance criteria refer to the CORBA framework which provides more than one paradigm choice for ORB and CORBA services usage (Q.816-series ITU-T Recommendations) and information modelling in IDL (X.780-series ITU-T Recommendations). Currently these choices are the fine-grained and coarse-graine

44、d approaches. According to ITU-T Rec. M.3010 an operations system (OS) interface may make a claim, by level, of TMN interface information conformance for each management capability that the interface supports. The supported management capability sets shall be specified by an information model docume

45、nt. Level A, Level B and Level C are defined and distinguished only by the source of the information models that are applied to specify the managed object classes the OS interface supports. The applicable information models need to be specified and well-documented in: ITU-T Recommendations, in case

46、of Level A conformance; standards of other de jure or de facto standards bodies, in case of Level B conformance; a non-standard way, in case of Level C conformance. In all cases, implementation conformance statements proformas following the X.781-series of ITU-T Recommendations, as appropriate, shal

47、l be provided. Because ITU-T Recs X.780, X.780.1 and X.780.2 define slightly different approaches to modelling manageable resources on fine-grained, coarse-grained and service-oriented interfaces, interface model specifications will be slightly different for the fine-grained, coarse-grained and serv

48、ice-oriented framework paradigms. While information modelling according to ITU-T Recs X.780 and X.780.1 will always lead to Level A TMN interface information conformance, the lightweight information modelling according to ITU-T Rec. X.780.2 may lead to any conformance level. ITU-T Rec. Q.816.2 (03/2

49、007) 3 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 references are subject to revision; 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 publishe