1、 International Telecommunication Union ITU-T Y.2013TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2006) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Frameworks and functional architecture models Converged services f
2、ramework functional requirements and architecture ITU-T Recommendation Y.2013 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
3、 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 Architect
4、ure, 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 GENERATION NETWORK
5、S 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 addressing Y.2
6、300Y.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. ITU-T Rec. Y.2013 (12/2006) i ITU-T Recommendation Y.2013 Converged servi
7、ces framework functional requirements and architecture Summary This Recommendation provides the high-level requirements and functional architecture for the converged services framework (CSF). The CSF defines an architectural framework to provide a seamless user experience across multiple networks. S
8、ource ITU-T Recommendation Y.2013 was approved on 14 December 2006 by ITU-T Study Group 13 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Y.2013 (12/2006) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of teleco
9、mmunications. 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 Telecomm
10、unication 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 areas
11、 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 opera
12、ting 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 “shall“
13、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 practi
14、ce 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 developm
15、ent process. As of the date of approval of this Recommendation, ITU had 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 str
16、ongly 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 reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Y.2013 (12/2006) iii CONTENTS Page 1 Scope 1 2 References. 1 3
17、 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation. 1 4 Abbreviations and acronyms 2 5 Overview and high-level requirements. 3 5.1 Introduction 3 5.2 High-level requirements . 3 6 CSF functional architecture and functional entities 4 6.1 Convergence coordination fu
18、nctional entity (CC-FE) . 5 6.2 Network support functional entity (NS-FE). 7 6.3 Edge support functional entity (ES-FE) . 8 6.4 Client support functional entity (CLS-FE). 9 6.5 Convergence policy functional entity (CP-FE) 11 7 Context of CSF within NGN 12 7.1 Relationship to NGN functional architect
19、ure. 12 7.2 Service convergence types . 16 Appendix I CSF use cases. 18 I.1 Voice and presence service converged service 18 I.2 Call forwarding Video conferencing converged service . 19 I.3 Movement of conference call from a fixed client to mobile client 20 I.4 Hybrid solution for a cross-network vi
20、deo + phone converged service (video on demand point of sale service using the CSF support and coordination functional entities). 21 I.5 Integrating information to improve customer service 25 Appendix II Standards related to CSF 28 II.1 CSF relationship to OSA/Parlay. 28 II.2 CSF relationship to OMA
21、 and OSE . 28 II.3 CSF relationship to underlying networks. 28 Appendix III Examples of three converged service types 30 III.1 Type 1 example: Converged service in a single service component 30 III.2 Type 2 example: Converged service in multiple service components (PIEA + IMS) . 31 III.3 Type 3 exam
22、ple: Converged service with other network IMS + Internet IM server 32 iv ITU-T Rec. Y.2013 (12/2006) Page Appendix IV CC-FE to CC-FE interworking description models 35 IV.1 Hierarchical convergence model 35 IV.2 Master-slave convergence model . 35 IV.3 Peer-to-peer convergence model 36 Appendix V CS
23、F configuration models 37 Bibliography. 39 ITU-T Rec. Y.2013 (12/2006) 1 ITU-T Recommendation Y.2013 Converged services framework functional requirements and architecture 1 Scope One objective of NGN is to enable seamless delivery of services across users multiple devices served across different env
24、ironments (home, cellular, enterprise, etc.) that are connected across multiple access networks in one operator domain or different operator domains. As users move across different environments, their services are managed and delivered to them seamlessly and with ease. The converged services framewo
25、rk (CSF) is designed to provide a common point of coordination for services, mobility, preferences, resources and the state of users on a per-user basis. This Recommendation defines the high-level requirements and functional architecture for the CSF. In addition, this Recommendation provides example
26、 use case scenarios (see Appendix I) to highlight the functionality of the CSF. 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 indic
27、ated 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 Re
28、commendations 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.60 ITU-T Recommendation M.60 (1993), Maintenance terminology and definitions. ITU-T Y.2012 ITU-T Recommendation Y.2012 (20
29、06), Functional requirements and architecture of the NGN release 1. ITU-T Y.2021 ITU-T Recommendation Y.2021 (2006), IMS for Next Generation Networks. ITU-T Y.2091 ITU-T Recommendation Y.2091 (2007), Terms and definitions for Next Generation Networks. 3 Definitions 3.1 Terms defined elsewhere This R
30、ecommendation uses the following terms defined elsewhere: 3.1.1 service: ITU-T Y.2091 A set of functions and facilities offered to a user by a provider. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 application: A software entity residing on an appli
31、cation server that contributes to the delivery of an end user service. 3.2.2 application server: A physical network element that provides computing resources that are applied to the delivery of services to end users through the execution of applications. 2 ITU-T Rec. Y.2013 (12/2006) 3.2.3 policy: A
32、n ordered combination of policy rules that defines how to administer, manage and control access to resources. This function is responsible for policy access, policy condition matching and corresponding policy decisions according to matched conditions. 3.2.4 policy management: This provides the funct
33、ions for describing, creating, updating, deleting, provisioning and viewing of policies. 3.2.5 service convergence: The coordination of a set of services such that the end users view is that of a single service. The component services may have different providers. 4 Abbreviations and acronyms This R
34、ecommendation uses the following abbreviations and acronyms: a.k.a. also known as AAA Authentication, Authorization and Accounting AM (PCMM) Application Manager AS (IMS) Application Server AS-FE Application Support Functional Entity CSF Converged Services Framework CC-FE Convergence Coordination Fun
35、ctional Entity CLS-FE Client Support Functional Entity CP-FE Convergence Policy Functional Entity DRM Digital Rights Management ES-FE Edge Support Functional Entity FE Functional Entity GPS Global Positioning System HSS (IMS) Home Subscriber Server iFC initial Filter Criteria IMS IP Multimedia Subsy
36、stem ISC IMS Service Control ISDN Integrated Services Digital Network NGN Next Generation Network NS-FE Network Support Functional Entity OSA Open Service Access OSE OMA Service Environment OSI Open Systems Interconnection PCMM PacketCable Multimedia PIEA PSTN/ISDN Emulation Architecture POD Point O
37、f Display PS (PCMM) Policy Server PSTN Public Switched Telephone Network ITU-T Rec. Y.2013 (12/2006) 3 RKS (PacketCable) Record Keeping Server SCP Service Control Point SIP Session Initiation Protocol SLF (IMS) Subscription Locator Function SPT (IMS) Service Point Trigger SSP Service Switching Point
38、 STB Set Top Box STP Signalling Transfer Point SUP-FE Subscriber User Profile Functional Entity UE User Equipment UPnP Universal Plug and Play VoD Video on Demand WMAN Wireless Metropolitan Area Network 5 Overview and high-level requirements 5.1 Introduction The main goal of the converged services f
39、ramework (CSF) is to provide the experience of a service that operates smoothly and consistently when crossing the boundaries of multiple access and core networks, or when service interaction events occur. To enable this, the framework should support features common to many applications. These inclu
40、de tracking the user state and profile, device identity, state and profile, session state and location across multiple NGN and non-NGN networks. Another key element of the CSF is that it will allow advanced services to be made available to legacy terminals. 5.2 High-level requirements The CSF is req
41、uired to support the following high-level requirements: 1) Function across various transport and control networks. 2) Integrate user preferences and current state for each active user identifier such that the user is not required to explicitly initiate session mobility. 3) Collect user-related infor
42、mation from services, core networks, access networks, devices and applications, subject to privacy and security considerations. 4) Process user- and service-related information about a particular user across multiple networks, devices and applications. 5) Distribute processed user-related informatio
43、n to services, core networks, access networks, devices and applications, subject to privacy and security considerations. 6) Respond to service requests by end users or applications with responses that consider the processed information about a user and his/her state (for example, multiple networks,
44、devices, applications). 7) Provide network-specific, application-specific or device-specific translated service requests on behalf of a received service request to allow an end user or network-agnostic application to achieve consistent behaviour across service provider domains. 4 ITU-T Rec. Y.2013 (
45、12/2006) 8) Integrate end user identifiers and preferences to create appropriate services behaviour for the currently “in use“ identifier. 9) Enable services that allow an end user to cause their current session to be transferred from one device to another, by user profile preference or user action.
46、 10) Enable services to be converged across various transport and control networks. 11) Support both network-operator-specific and third-party services. 12) Support management of user profile, location, presence, availability, preference and service subscription information that spans different netw
47、orks and devices, subject to privacy and security considerations. 13) Provide controlled access to information from services enablers (such as presence, availability, location, registration status, QoS options, media resources, billing) irrespective of the access network, application server and devi
48、ce to create enhanced integrated services on a per-user basis. 14) Be compliant with policy-based service management. 15) Support policy management of service convergence that is independent of the implementation method of the service. 16) Support digital rights management (DRM) and allow service pr
49、oviders to enable DRM when sharing content across multiple devices owned by the same user, across multiple access networks and across multiple identities of the same user. 17) Support the use of network adapters which allow information to be successfully delivered across an interface between systems using different data formats and protocols. 18) Support a flexible trace mechanism in order to locate service faults effectively. 19) Coordinate between services provided to a user, possibly by different service providers, such that their
