1、 International Telecommunication Union ITU-T Q.818TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2012) SERIES Q: SWITCHING AND SIGNALLING Q3 interface Web services-based management services Recommendation ITU-T Q.818 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTE
2、RNATIONAL 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, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGE
3、S Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NET
4、WORK 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.3000Q.3999 For further details, please refer t
5、o the list of ITU-T Recommendations. Rec. ITU-T Q.818 (05/2012) i Recommendation ITU-T Q.818 Web services-based management services Summary Recommendation ITU-T Q.818 defines a set of services required to support service-oriented web services-based interfaces and along with Recommendation ITU-T X.78
6、2 composes a framework for web services-based network management interfaces. It specifies protocol requirements, how some well-known web services should be used in network management interfaces and defines some network management-specific support services. The WSDL interface definitions for the netw
7、ork management-specific support services are also provided. History Edition Recommendation Approval Study Group 1.0 ITU-T Q.818 2012-05-14 2 Keywords Distributed processing, extensible markup language (XML), managed objects, network management interfaces, service-oriented, universal description disc
8、overy and integration (UDDI), web services (WS), web services description language (WSDL), XML schema. ii Rec. ITU-T Q.818 (05/2012) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication tec
9、hnologies (ICTs). The ITU Telecommunication Standardization 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 Tele
10、communication Standardization Assembly (WTSA), which 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 a
11、reas of information technology which fall within ITU-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 o
12、perating agency. Compliance with this Recommendation 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 “s
13、hall“ or some other obligatory language such as “must“ 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
14、practice or implementation of this Recommendation may involve 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 de
15、velopment process. As of the date of approval of this Recommendation, 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 the
16、refore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2012 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Q.818 (05/2012) iii Table of Contents Page 1 Scope 1
17、 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Web services-based network management services goal and requirements 3 6.1 Goals . 3 6.2 Information modelling dependencies . 4 6.3 Scoping . 5
18、 6.4 Notifications . 5 7 Framework overview and protocol requirements . 6 7.1 Framework overview 6 7.2 Protocol, languages and services requirements 7 8 Usage of well-known web services 7 8.1 Web services base notification . 7 8.2 UDDI service registration . 16 9 Framework support services . 21 9.1
19、Heartbeat service 21 9.2 Multiple object operation service . 23 9.3 Containment service . 29 10 Compliance and conformance 31 10.1 System conformance points 31 10.2 Basic conformance profile 31 Annex A WSDL definition of framework support services . 33 A.1 ITU notification service WSDL and XML schem
20、a definition . 33 A.2 ITU heartbeat service WSDL and XML schema definition . 44 A.3 ITU MOO service WSDL and XML schema definition 46 A.4 ITU containment service WSDL and XML schema definition 51 Bibliography. 55 Rec. ITU-T Q.818 (05/2012) 1 Recommendation ITU-T Q.818 Web services-based management s
21、ervices 1 Scope The network management architecture defined in ITU-T M.3010 introduces the use of multiple management protocols. So far, the GDMO/CMIP and CORBA GIOP/IIOP are possible choices at the application layer. Based on the management interface specification methodology defined in ITU-T M.302
22、0, more technology-based paradigms can be introduced into network management interfaces, and web services/XML is now an additional paradigm for network management. This Recommendation, together with ITU-T X.782, sets out to define a framework for defining how interfaces supported by management syste
23、ms and network elements should be modelled using web services/XML schema. It is the scope of this Recommendation to provide the following guidelines or instructions: protocol requirements for using web services in network management; how a web services-based notification service is used in network m
24、anagement interfaces; how a new service is registered and accessed using UDDI; how to monitor the availability of a web services notification forwarding mechanism; how to access multiple managed objects in one operation; compliance and conformance requirements. 2 References The following ITU-T Recom
25、mendations 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 th
26、erefore 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 published. The reference to a document within this Recommendation does not give it, as a st
27、and-alone document, the status of a Recommendation. ITU-T X.701 Recommendation ITU-T X.701 (1997), Information technology Open Systems Interconnection Systems management overview. ITU-T X.703 Recommendation ITU-T X.703 (1997), Information technology Open Distributed Management Architecture. ITU-T X.
28、782 Recommendation ITU-T X.782 (2012), Guidelines for defining web services for managed objects and management interfaces. ITU-T M.3010 Recommendation ITU-T M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3020 Recommendation ITU-T M.3020 (2010), Management interface sp
29、ecification methodology. ITU-T M.3702 Recommendation ITU-T M.3702 (2010), Common management services Notification management Protocol neutral requirements and analysis. OASIS UDDI OASIS Specification (2004), Universal Description, Discovery and Integration (UDDI) v3.0.2. OASIS WSN OASIS Specificatio
30、n (2006), Web Services Base Notification v1.3. 2 Rec. ITU-T Q.818 (05/2012) W3C SOAP W3C Recommendation (2007), SOAP Version 1.2 Part 1: Messaging Framework (Second Edition). W3C XML W3C Recommendation (2000), Extensible Markup Language (XML) 1.0 Second Edition. W3C XS-P1 W3C Recommendation (2004),
31、XML Schema Part 1: Structures Second Edition. W3C XS-P2 W3C Recommendation (2004), XML Schema Part 2: Datatypes Second Edition. W3C WSDL W3C Recommendation (2001), Web Services Description Language (WSDL) 1.1. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms def
32、ined elsewhere: 3.1.1 agent ITU-T M.3020 3.1.2 managed object class ITU-T X.701 3.1.3 manager ITU-T M.3020 3.1.4 notification ITU-T X.703 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CMIP Common Managem
33、ent Information Protocol CORBA Common Object Request Broker Architecture GDMO Guidelines for the Definition of Managed Objects GIOP General Inter-ORB Protocol IIOP Internet Inter-ORB Protocol MO Managed Object MOC Managed Object Class MOO Multiple Object Operation SOAP Simple Object Access Protocol
34、TMN Telecommunications Management Network UDDI Universal Description Discovery and Integration WS Web Services WSDL Web Services Description Language Rec. ITU-T Q.818 (05/2012) 3 WSN Web Services Notification XML extensible Markup Language XSD XML Schema Definition 5 Conventions A few conventions ar
35、e followed in this Recommendation to make the reader aware of the purpose of the text. While most of the Recommendation is normative, paragraphs succinctly stating mandatory requirements to be met by a management system (managing and/or managed) are preceded by a boldface “R“ enclosed in parentheses
36、, followed by a short name indicating the subject of the requirement, and a number. For example: (R) EXAMPLE-1: An example mandatory requirement. Requirements that may be optionally implemented by a management system are preceded by an “O“ instead of an “R“ For example: (O) OPTION-1: An example opti
37、onal requirement. The requirement statements are used to create compliance and conformance profiles. Many examples of WSDL and XML schema are included in this Recommendation, and WSDL specifying management specific services and supporting data types are included in a normative annex. The WSDL and XM
38、L schema are written in a 10 point courier typeface: 6 Web services-based network management services goal and requirements This clause describes the key goals of the services framework and the requirements that help the web services-based network management services support these goals. Clause 6.1
39、introduces the goals of the web services framework. Clause 6.2 then provides terminology and requirements. The requirements in this clause are requirements that the framework must satisfy and which are based on telecommunications management needs. Clauses 7, 8, 9 then describe a framework that meets
40、 these needs and defines how to achieve the requirements of this clause by using web services in a certain way. 6.1 Goals This Recommendation sets out to define a framework for defining how interfaces supported by management systems and network elements should be modelled. Some key goals of the fram
41、ework are identified here: application interoperability common usage of well-known web services. This clause elaborates on these two goals. 6.1.1 Application interoperability A key goal of the network management architecture and in particular the information architecture, is to promote a standard fr
42、amework for providing interoperability and information exchange between systems from a diverse set of network management system suppliers. Interoperability between systems involves many aspects of development. At its lowest layer, a common communication mechanism must be in place to support a common
43、 syntax, the establishment of 4 Rec. ITU-T Q.818 (05/2012) connectivity and the exchange of operation requests/replies between systems. This aspect of interoperability is inherently supported by the web services specifications. For network management, there is the need to provide application interop
44、erability. That is, management systems from diverse suppliers will be utilized within a single administrations TMN to support different functions necessary to support the management of its networks. To simplify integration of these various suppliers systems, they must agree on the semantics of the i
45、nformation being exchanged. This is accomplished with the specification of an information model. Guidelines for the definition of web services-based information models are specified in ITU-T X.782, but the services defined here should support those guidelines. 6.1.2 Common usage of well-known web se
46、rvices A second aspect of this framework is the definition of common usage and profiling of the distributed processing environment of choice. This aspect of the framework should indicate the reasonable expectations network management system suppliers may have for one another. Rather than redefining
47、the interface capabilities needed to support common network management functions such as notification filtering with each information model, the modelling guidelines in ITU-T X.782 rely upon a set of support services. These support services enable the information models to be simpler, and also enhan
48、ce interoperability. In defining these services, special effort will be taken to make use of some of the well-known web services. Specifically, this Recommendation will address the use of the web services notification as defined in OASIS WSN and web services UDDI service registration as defined in O
49、ASIS UDDI which will impact system interoperability (i.e., issues involving the use of web services within a single system are outside the scope of this Recommendation). Where network management needs cannot be met by the above mentioned well known web services, additional services will be defined. 6.2 Information modelling dependencies As described in the previous clause, the explicit modelling of resources that are manageable across an interface is central to application inter
