1、 International Telecommunication Union ITU-T Y.2232TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2008) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Service aspects: Service capabilities and service architecture NGN
2、 convergence service model and scenario using web services Recommendation ITU-T Y.2232 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y
3、.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199
4、Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 NEXT GENERATIO
5、N NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Numbering, naming and addre
6、ssing Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2232 (01/2008) i Recommendation ITU-T Y.2232 NGN co
7、nvergence service model and scenario using web services Summary The convergence service in NGN implies the integration of services in NGN in a unified manner to access each service in order to interwork with each service. Recommendation ITU-T Y.2232 defines the convergence model for NGN based on web
8、 services and provides a detailed scenario of each convergence model in the form of web services. Source Recommendation ITU-T Y.2232 was approved on 25 January 2008 by ITU-T Study Group 13 (2005-2008) under Recommendation ITU-T A.8 procedure. ii Rec. ITU-T Y.2232 (01/2008) FOREWORD The International
9、 Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating
10、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 meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce
11、 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-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this R
12、ecommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interop
13、erability 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“ and the negative equivalents are used to express requirements. The use of such words does not suggest that
14、 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 involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, va
15、lidity 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 Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be re
16、quired 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 database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reprod
17、uced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.2232 (01/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere:. 2 3.2 Terms defined in this Recommendation. 2 4 Abbreviations and acronyms 3 5 Conventions 4 6 Requirement
18、s to support convergence services model and scenario 4 7 Web services deployment model in NGN 4 7.1 Characteristics of web services 4 7.2 Web services deployment model 5 7.3 Web services gateway (WSG) 7 7.4 Web services gateway interaction patterns. 9 8 Web services-based convergence model and conve
19、rgence service scenarios 14 8.1 Basic convergence model. 14 8.2 Extended convergence model. 15 8.3 Convergence service scenarios. 17 9 Security considerations. 21 9.1 Threats to web services 21 9.2 Security requirements for web services 21 Appendix I Security considerations for web services. 23 I.1
20、Security technologies for web services-based NGN convergence services . 23 Appendix II Interoperability considerations for web services 25 II.1 Interoperability at the SOAP layer . 25 II.2 Interoperability at the SOAP message security layer. 26 Appendix III Information flows for WSG 29 III.1 Case 1:
21、 Information flows for security pattern. 29 III.2 Case 2: Information flows for substitution pattern. 30 III.3 Case 3: Information flows for composition pattern 31 Bibliography. 33 iv Rec. ITU-T Y.2232 (01/2008) Introduction The NGN service architecture has the three main functional characteristics
22、of (i) agnosticism, (ii) support for legacy capabilities and features, and (iii) support for an open service interface (Recommendation ITU-T Y.2012). Among these, the third characteristic implies that the NGN service platform is required to provide an open service interface, which provides an abstra
23、ction of the network capabilities. NGN users can create and provide enhanced services, which enables application of NGN capabilities using the “applications“ functional group known as the application-to-network interface (ANI) (Recommendation ITU-T Y.2012). ANI provides a channel for interactions an
24、d exchanges between applications and NGN elements. ANI offers the capabilities and resources needed for the realization of applications. Also, NGN provides open service environment (Recommendation ITU-T Y.2201) for application developers. This Recommendation proposes the NGN convergence models and s
25、cenario of (i) interactions among web services-enabled NGN services, and (ii) interaction with web services-enabled NGN services, along with NGN services, which does not have a web services feature. The overall value proposition of this Recommendation lies in extending the space of application devel
26、opers for the NGN services interface to include members of IT communities and others who are in skills areas other than programming language developers, such as web developers. The various perspectives on the value proposition are as follows: The end user is the consumer of the services. The end use
27、r is provided with more services in a timelier manner, and services may be delivered that are more personalized to their unique market segments. The application developer is the person programming the application who makes use of web services to deliver application functionality to the end user. The
28、 developer benefits from (i) access to NGN capabilities using an intuitive function, (ii) the ability to use a common application framework that supports web services to build and deploy their applications. A service provider is an entity that operates the NGN services. The value proposition of web
29、services for the service provider is (i) to offer a wide range of services rapidly and inexpensively, (ii) to differentiate itself by means of offering specialized services and serving strategic niche markets, (iii) to reach customers who are only interested in niche applications, and possibly cross
30、-sell them, and (iv) to build customer loyalty by providing a means to customize services and assistance with this. The network operator is the entity that supports the network resources that support the web services. The value proposition for the network operator is the increased use of network res
31、ources and hence, increased revenue. Rec. ITU-T Y.2232 (01/2008) 1 Recommendation ITU-T Y.2232 NGN convergence service model and scenario using web services 1 Scope The objective of this Recommendation is to describe the NGN convergence service model and scenario using web services. This Recommendat
32、ion defines the convergence model for NGN based on web services and provides a detailed scenario of each convergence model in the form of web services. The term convergence in NGN has focused mainly on the convergence of media, such as voice, data and video. However, to realize the ultimate converge
33、nce of services in NGN, it is necessary to develop detailed requirements to allow for the convergence of services. It is also important to clearly identify the value being added by a convergence service. The convergence services in NGN imply the integration of services in NGN in a unified manner to
34、access each service in order to interwork with each service. Implementing the convergence service in current networks may be restricted or impossible due to the capabilities of the installed equipment. Moreover, service provisioning of the convergence service to implement new functionalities is esse
35、ntially restricted to equipment vendors, as the APIs are typically proprietary ITU-T Y.2012. Thus, for the open service interface of NGN, NGN is required to support standard ANI API and a unified manner for accessing the NGN services from the IT side. Currently, the capabilities and requirements b-I
36、TU-T Y.2000-Sup.1 ITU-T Y.2201 for open services environments have been described. Web services is one of the technologies of open services environments. The use of web services is expanding rapidly as the need for application-to-application communication and interoperability grows. In NGN, web serv
37、ices provide a standard means of communication among different software applications of NGN services to the users. To address these capabilities among these applications in NGN environments, and to allow them to be combined for more complex services, a standard reference convergence model is needed
38、in an NGN environment. The scope of this Recommendation is to address a convergence service scenario in NGN using web services. This Recommendation covers: Requirements to support convergence services model and scenario. A web services deployment model for NGN. NGN convergence services model and its
39、 scenarios using web services. 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 re
40、ferences 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 published. The referen
41、ce to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2013 Recommendation ITU-T Y.2013 (2006), Converged services
42、 framework functional requirements and architecture. 2 Rec. ITU-T Y.2232 (01/2008) ITU-T Y.2091 Recommendation ITU-T Y.2091 (2008), Terms and definitions for Next Generation Networks. ITU-T Y.2201 Recommendation ITU-T Y.2201 (2007), NGN release 1 requirements. ITU-T Y.2701 Recommendation ITU-T Y.270
43、1 (2007), Security requirements for NGN release 1. W3C SOAP 0 W3C Recommendation (2007), SOAP Version 1.2 Part 0: Primer (Second Edition). W3C SOAP 1 W3C Recommendation (2007), SOAP Version 1.2 Part 1: Messaging Framework (Second Edition). W3C WSDL 0 W3C Recommendation (2007), Web Services Descripti
44、on Language (WSDL) Version 2.0 Part 0: Primer. W3C WSDL 1 W3C Recommendation (2007), Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 access b-ITU-T X.1142: Perf
45、orming an action. 3.1.2 access control b-ITU-T X.1142: Controlling access in accordance with a policy. 3.1.3 access control information b-ITU-T X.812: Any information used for access control purposes, including contextual information. 3.1.4 gateway b-ITU-T H.310: A function that converts transmissio
46、n formats and/or protocols between different network environments. 3.1.5 principal b-ITU-T X.811: An entity whose identity can be authenticated. 3.1.6 service ITU-T Y.2091: A set of functions and facilities offered to a user by a provider. 3.1.7 service convergence ITU-T Y.2013: The coordination of
47、a set of services such that the end users view is that of a single service. The component services may have different providers. 3.1.8 SOAP W3C SOAP 1: The formal set of conventions governing the format and processing rules of a SOAP message. These conventions include the interactions among SOAP nod
48、es generating and accepting SOAP messages for the purpose of exchanging information along a SOAP message path. 3.1.9 SOAP intermediary W3C SOAP 1: A SOAP intermediary is both a SOAP receiver and a SOAP sender and is targetable from within a SOAP message. It processes the SOAP header blocks targeted
49、at it and acts to forward a SOAP message towards an ultimate SOAP receiver. 3.1.10 WSDL W3C WSDL 1: Web services description language Version 2.0 (WSDL 2.0) provides a model and an XML format for describing Web services. WSDL 2.0 enables one to separate the description of the abstract functionality offered by a service from concrete details of a service description such as “how“ and “where“ that functionality is offered. 3.2 Terms defined in this Recommendation This Recommendation defines the
