1、 International Telecommunication Union ITU-T Y.2234TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2008) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Service aspects: Service capabilities and service architecture Ope
2、n service environment capabilities for NGN Recommendation ITU-T Y.2234 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.200Y.299 Networ
3、k 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 Architecture, ac
4、cess, 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 GENERATION NETWORKS Frame
5、works 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 addressing Y.2300Y.23
6、99 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.2234 (09/2008) i Recommendation ITU-T Y.2234 Open service environme
7、nt capabilities for NGN Summary Recommendation ITU-T Y.2234 describes open service environment (OSE) capabilities for NGN. OSE capabilities are built on NGN release 1 capabilities with the aim to enable enhanced, flexible service creation and provisioning. This framework requires use of standard int
8、erfaces to ensure NGN OSE-based service reusability, portability across networks, as well as accessibility by NGN application providers and/or developers. OSE capabilities enable applications development using NGN OSE-based services for exposing the NGN capabilities. This Recommendation provides ser
9、vice requirements, functional requirements and architecture of open service environment capabilities. Source Recommendation ITU-T Y.2234 was approved on 12 September 2008 by ITU-T Study Group 13 (2005-2008) under Recommendation ITU-T A.8 procedure. Keywords Next generation networks (NGN), NGN OSE-ba
10、sed service, open service environment, open service environment capabilities, OSE, service-oriented architecture. ii Rec. ITU-T Y.2234 (09/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and commu
11、nication technologies (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. Th
12、e 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 Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution
13、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 Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a
14、recognized operating 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. T
15、he 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 compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibilit
16、y 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, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recomm
17、endation 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 required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information
18、and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 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 Y.2234 (09/2008) iii CONTENTS Page 1 Scop
19、e 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation. 2 4 Abbreviations and acronyms 2 5 Conventions 4 6 Service requirements for open service environment capabilities . 4 7 Functional requirements for open service environment capabilities 5 7.1
20、Service coordination functional requirements 5 7.2 Service discovery functional requirements 6 7.3 Service registration functional requirements 6 7.4 Service management functional requirements 6 7.5 Service composition functional requirements 7 7.6 Service development support functional requirements
21、 7 7.7 Interworking with service creation environment functional requirements. 7 7.8 Policy enforcement functional requirements 8 8 Service architecture for open service environment capabilities . 8 8.1 OSE positioning within the NGN reference architecture . 8 8.2 Service architecture 10 9 Security
22、considerations. 12 Appendix I Use cases for NGN open service environment 13 I.1 Introduction 13 I.2 Service registration and service discovery . 13 I.3 BookItWell . 14 I.4 IPTV new customer application . 16 Appendix II Relationship of SOA concepts with open service environment capabilities 20 Append
23、ix III Relationship of standards in other SDOs with open service environment capabilities 21 III.1 Open Service Access (OSA)/Parlay . 21 III.2 Open Mobile Alliance (OMA) . 21 III.3 Organization for the Advancement of Structured Information Standards (OASIS) 21 III.4 World Wide Web Consortium (W3C) 2
24、2 III.5 Object Management Group (OMG) . 22 III.6 TeleManagement Forum (TMF). 23 III.7 Information sources for OSE capabilities. 24 Bibliography. 28 iv Rec. ITU-T Y.2234 (09/2008) Introduction The ability to implement new functionalities in current networks may be limited or impossible due to the cap
25、abilities of the installed equipment. Software provisioning to implement new functionalities is essentially restricted to equipment vendors, since the existing or current application programming interfaces (APIs) are typically proprietary (i.e., not open) (Recommendation ITU-T Y.2201). NGN enables n
26、ew capabilities and supports a wide range of emerging services, including services with advanced and complex functionalities. In response to a drive from application providers and/or developers to develop new applications and capabilities accessible via standard interfaces, there is an increasing ne
27、ed for NGN providers to cooperate in the development of standard application network interfaces (ANIs). Furthermore, software reusability and portability is encouraged to facilitate cost-effective development. The support of an open service environment within NGN aims to provide efficient and flexib
28、le capabilities based on the use of standard interfaces to NGN applications, thereby enabling applications to take full advantage of the NGN capabilities. Some general benefits of an open service environment are as follows (Recommendation ITU-T Y.2201). Applications and capabilities can be easily de
29、veloped by NGN providers as well as by application providers. Capabilities can be made portable and/or reusable across networks. Standard ANIs can accommodate interactions between NGN entities and applications. Within an open service environment, each capability is required to function either indepe
30、ndently or in conjunction with other capabilities for the realization of applications. Each capability performs all corresponding service functions for the requesting entity. Applications may be provisioned over different networks, so the capabilities must be able to function independently from the
31、underlying network technologies (Recommendation ITU-T Y.2201). Rec. ITU-T Y.2234 (09/2008) 1 Recommendation ITU-T Y.2234 Open service environment capabilities for NGN 1 Scope The objective of this Recommendation is to define an open service environment (OSE) framework for NGN. This framework is buil
32、t on NGN release 1 capabilities ITU-T Y.2201 with the aim to enable enhanced, flexible service creation and provisioning. The use of standard interfaces will ensure NGN OSE-based service reusability, portability across networks, as well as accessibility by NGN application providers and/or developers
33、. This Recommendation provides service requirements, functional requirements and architecture of open service environment capabilities. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recomm
34、endation. 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 referen
35、ces 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 stand-alone document, the status of a Recommendation. ITU-T M.3060 Recommendation ITU-T M.3060/Y.2401 (2006), Principles for the
36、 Management of Next Generation Networks. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2201 Recommendation ITU-T Y.2201 (2007), NGN release 1 requirements. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements
37、 for NGN release 1. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 application network interface (ANI) ITU-T Y.2012: Interface which provides a channel for interactions and exchanges between applications and NGN elements. The ANI offer
38、s capabilities and resources needed for the realization of applications. 3.1.2 application programming interface (API) b-ITU-T I.312: An API provides a set of interfaces from an application environment to an execution environment. The execution environment provides services to the application enviro
39、nment. 2 Rec. ITU-T Y.2234 (09/2008) 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 open service environment capabilities: Capabilities provided by an open service environment to enable enhanced and flexible service creation and provisioning based on
40、the use of standards interfaces. NOTE Open service environment capabilities enable services reusability, portability across networks and accessibility by application providers and user applications in NGN. 3.2.2 service chain: A set of coordinated services that occur in a specific sequence. 3.2.3 se
41、rvice composition: Service composition is the capability of creating new services from other existing services. NOTE NGN OSE-based services will be used as key building blocks to quickly create a composite service. Service composition can occur in a static or in a dynamic way. While in static compos
42、ition, composite services are defined in advance, dynamic composition sends the request for service discovery using the service description to find the needed services and composes the services during run time. 3.2.4 service coordination: The ability to manage the relationships and interactions amon
43、g services to provide a “service chain“, as well as among services and applications. 3.2.5 service development support: Service development support provides an environment for service creation, development and maintenance. 3.2.6 service discovery: Service discovery performs a search against all regi
44、stered services and provides the related service information. 3.2.7 service management: Service management provides the overall service managing functions such as service monitoring, service tracking and unexpected failure control. 3.2.8 service registration: Service registration manages the informa
45、tion about services and maintains the most up-to-date information. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ANI Application Network Interface API Application Programming Interface APL-GW-FE Application Gateway Functional Entity APL-SCM-FE Applic
46、ation Service Coordination Manager Functional Entity ASF Application Support Functions ASF update management; auditing; version control; logging, e.g., provide a record of the history of services; access control management; statistical analysis of service registration and utilization. Support NGN se
47、rvice reuse by providing service composition capability. Support of a service composition language. Offer a development support environment which supports construction, trialling, deployment and removal of applications ITU-T Y.2201. Allow interworking with service creation environments and network e
48、ntities for creation and provisioning of applications and services ITU-T Y.2201. Provide a secure access to the NGN capabilities in alignment with the general NGN security requirements as specified in ITU-T Y.2201. Support policy enforcement capability for resource protection and management, and ser
49、vice personalization. 7 Functional requirements for open service environment capabilities This clause describes functional requirements specific to the support of NGN open service environment capabilities. OSE capabilities consist of service coordination, service discovery, service registration, service management, service composition, service development support, interworking with service creation environments and policy enforcement. 7.1 Service coordination functional requirements The NGN service c
