1、 International Telecommunication Union ITU-T Y.2023TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2012) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Frameworks and functional architecture models Functional requireme
2、nts and architecture for the next generation network multimedia communication centre service Recommendation ITU-T Y.2023 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Servi
3、ces, applications and middleware Y.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 Servi
4、ces and applications Y.1100Y.1199 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 Ch
5、arging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION 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
6、 and networks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Smart ubiquitous networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.290
7、0Y.2999 Future networks Y.3000Y.3099 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2023 (04/2012) i Recommendation ITU-T Y.2023 Functional requirements and architecture for the next generation network multimedia communication centre service Summary The multimed
8、ia communication centre (MCC) provides a set of advanced services beyond traditional communication services. The MCC enables a service provider to deliver communication services to individual and enterprise customers. The objective of Recommendation ITU-T Y.2023 is to identify and describe the funct
9、ional requirements, architecture and key procedures of the MCC. History Edition Recommendation Approval Study Group 1.0 ITU-T Y.2023 2012-04-22 13 Keywords Functional architecture, master agent, MCC service, mobile agent, multimedia communication centre (MCC), NGN, RTWG, subagent. ii Rec. ITU-T Y.20
10、23 (04/2012) FOREWORD The International 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 respons
11、ible 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 meets every four years, establishes the topics for study by the ITU
12、-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-Ts purview, the necessary standards are prepared on a collaborative
13、 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 is voluntary. However, the Recommendation may contain certain manda
14、tory 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“ and the negative equivalents are used to express requirements. Th
15、e 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 involve the use of a claimed Intellectual Property Right. ITU take
16、s 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 Recommendation, ITU had not received notice of intellectual proper
17、ty, 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 database at http:/www.itu.int/ITU-T/ipr/. ITU 2012 All rights reserved.
18、No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.2023 (04/2012) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviat
19、ions and acronyms 2 5 Conventions 4 6 Overview of the MCC in the NGN . 4 7 Functional requirements for support of the MCC service 6 7.1 Unified service capabilities broker for the MCC . 6 7.2 Agent and sub-agent management 6 7.3 Supporting mobile agents with a real-time web communication capability
20、6 8 Functional architecture of the next generation network (NGN) for the support of the MCC service . 7 8.1 MCC functions in the NGN 7 8.2 Logical diagram of the MCC functions 8 8.3 Description of the MCC functional entities 10 9 Description of reference points . 13 9.1 Reference point description f
21、or MCC functions in the NGN . 13 9.2 Reference points description 13 10 MCC procedures and functional description 14 10.1 Communication requests queuing and distribution 14 10.2 MCC service initialization 15 10.3 Procedure to use the USBF . 15 10.4 Overload control . 16 10.5 Communication control op
22、erations for MCC agents 18 10.6 Management operations for supervisors . 21 10.7 MCC agent management 23 10.8 Video sharing 25 10.9 Video conferencing 26 10.10 Web and application collaboration . 27 10.11 User context information adoption . 29 10.12 Supporting of mobile agents with real-time web comm
23、unication capability 30 11 Security considerations . 31 Appendix I Multimedia communication centre layered architecture and deployment principles 32 iv Rec. ITU-T Y.2023 (04/2012) Page I.1 Multimedia communication centre (MCC) hierarchical deployment principles 32 I.2 MCC layered architecture . 34 B
24、ibliography. 36 Rec. ITU-T Y.2023 (04/2012) 1 Recommendation ITU-T Y.2023 Functional requirements and architecture for the next generation network multimedia communication centre service 1 Scope This Recommendation, based on ITU-T Y.2012, covers extended features in order to support applications and
25、 services for the multimedia communication centre (MCC). This Recommendation describes functional requirements, architecture, and entities of the MCC in order to support next generation network (NGN) service requirements and capabilities. This Recommendation covers: support of requirements and capab
26、ilities defined in ITU-T Y.2216 from an architectural viewpoint; functional requirements of the NGN architecture to support applications and services of the MCC; functional architecture, entities extensions, and procedures for applications and services of the MCC. 2 References The following ITU-T Re
27、commendations 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
28、 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 reference to a document within this Recommendation does not give it, as a
29、 stand-alone document, the status of a Recommendation. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2010), Functional requirements and architecture of next generation networks. ITU-T Y.2216 Recommendation ITU-T Y.2216 (2010), NGN capability requirements to support the multimedia communication centre se
30、rvice. ITU-T Y.2701 Recommendation ITU-T Y.2701 (2007), Security requirements for NGN release 1. ITU-T Y.2702 Recommendation ITU-T Y.2702 (2008), Authentication and authorization requirements for NGN release 1. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms de
31、fined elsewhere: 3.1.1 customer b-ITU-T M.3050.1: The customer buys products and services from the enterprise or receives free offers or services. A customer may be a person or a business. NOTE In the MCC service, the customers can experience advanced customer services offered by enterprises by comm
32、unicating through the NGN. 3.1.2 enterprise ITU-T Y.2216: The enterprise is responsible for delivering products and services to the customer. 2 Rec. ITU-T Y.2023 (04/2012) NOTE In MCC service by using the multimedia communication centre capabilities provided by NGN, each enterprise can provide its o
33、wn advanced customer services, such as business consultation, sale promotion, etc. 3.1.3 MCC agent ITU-T Y.2216: An MCC agent is an NGN end-user who acts as an enterprises agent in the MCC service. The MCC agent uses an NGN terminal to communicate with customers and perform communication control ope
34、rations, such as holding or transferring communications, etc. 3.1.4 MCC applications ITU-T Y.2216: MCC applications are a set of applications provided and deployed by an enterprise in order to support its MCC service offer to its customers. NOTE The MCC applications organize and manage the mechanism
35、s set and controlled by each enterprise in the MCC service. For example, the mechanisms can allow policy control of communication requests queuing, and management of media resources, etc. MCC applications interact with NGN entities to provide MCC service to customers. 3.1.5 MCC service ITU-T Y.2216:
36、 A service that enables customers to have multimedia communications through the NGN with enterprises by multiple means and that provides advanced features for the customer-enterprise interaction. NOTE The multiple means can be multimedia conversational communications, web and application collaborati
37、on, content push and sharing, etc. Advanced features include enhanced communication control, communication queuing, etc. 3.1.6 service enabler b-ITU-T Y.2240: A function or closely related set of functions made available over one or more well-defined interfaces to other consuming software applicatio
38、ns. NOTE In the MCC, a service enabler refers to certain types of service capabilities that can be invoked by MCC functions and resides outside of the MCC (e.g., location server function, presence server function). 3.2 Terms defined in this Recommendation This Recommendation defines the following te
39、rms: 3.2.1 master agent: A type of multimedia communication centre (MCC) agent which creates agents and manages the created agents accordingly. 3.2.2 mobile agent: A type of multimedia communication centre (MCC) agent which provides the MCC service in a mobile way. The mobile agent usually installs
40、agent software on the mobile terminal (e.g., smartphone). 3.2.3 real-time web communication gateway: A Web gateway that enables message conversion and real-time media stream transcoding through Internet for a mobile multimedia communication centre (MCC) agent. 3.2.4 sub-agent: A type of multimedia c
41、ommunication centre (MCC) agent which is created by a master agent. The sub-agent and the master agent work together for providing the MCC service to customers. 3.2.5 supervisor: A type of multimedia communication centre (MCC) agent which provides the MCC service to MCC customers and monitors other
42、MCC agents. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ANI Application Network Interface API Application Programming Interface AS Application Server Rec. ITU-T Y.2023 (04/2012) 3 BGW Border Gateway BSS Business Support System COLLF Collaboration F
43、unction CONF Conference Function CPE Customer Premises Equipment CRM Customer Relationship Management CSCF Call Session Control Function CTIF Communication Telephony Integration Function DB Data Base DTMF Dual Tone Multi Frequency HTTP Hypertext Transfer Protocol ID Identifier IM Instant Message IMS
44、 IP Multimedia Subsystem IP Internet Protocol IVR Interactive Voice Response IVVR Interactive Voice and Video Response LAN Local Area Network LCSF Location Server Function LSF Location Service Function MCC Multimedia Communication Centre MCDF Multimedia Call Distribution Function MGCF Media Gateway
45、Control Function MGW Media Gateway MLP Mobile Location Protocol MMRF MCC Media Resource Function MSC Mobile Switching Centre NGN Next Generation Network NMS Network Management System NNI Network to Network Interface OA Office Automation OAM Operations, Administration and Maintenance OCF Overload Con
46、trol Function OSS Operation Support System PSF Presence Server Function RWCG Real-time Web Communication Gateway SCMF Software Control Management Function 4 Rec. ITU-T Y.2023 (04/2012) SDP Session Description Protocol SIMPLE SIP for Instant Messaging and Presence Leveraging Extensions SIP Session In
47、itiation Protocol SOAP Simple Object Access Protocol SSF Service Support Function TDM Time-division multiplexing TTS Text to Speech UNI User to Network Interface URI Uniform Resource Identifier USBF Unified Service Broker Function VLR Visitor Location Register WSF Web-enabled Service Function XDM XM
48、L Document Management 5 Conventions In this Recommendation: The keywords “is required to“ indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed. The keywords “is recommended“ indicate a requirement which is re
49、commended but which is not absolutely required. Thus this requirement needs not be present to claim conformance. The keywords “can optionally“ indicate an optional requirement which is permissible, without implying any sense of being recommended. These terms are not intended to imply that the vendors implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and s
