1、 International Telecommunication Union ITU-T Y.1292TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (09/2008) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Architecture, access, network capabilities and resource managemen
2、t Customizable IP networks (CIP): Framework for the requirements and capabilities related to the customization of IP service networks by customers Recommendation ITU-T Y.1292 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOB
3、AL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, 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.89
4、9 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services 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 Ope
5、ration, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 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: I
6、nteroperability of services 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 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 For further details, please refer to the list of
7、 ITU-T Recommendations. Rec. ITU-T Y.1292 (09/2008) i Recommendation ITU-T Y.1292 Customizable IP networks (CIP): Framework for the requirements and capabilities related to the customization of IP service networks by customers Summary Recommendation ITU-T Y.1292 describes the framework for requireme
8、nts and capabilities to enable the customization of IP networks and related IP service and IP transfer capability to meet the customers needs. Such a framework includes the service requirements and functional requirements and capabilities as well as the architectural considerations. In addition, thi
9、s Recommendation identifies the application scenarios and service procedures applicable to the context of customization using the capabilities made available to and/or performed by the customer of IP services. Source Recommendation ITU-T Y.1292 was approved on 12 September 2008 by ITU-T Study Group
10、13 (2005-2008) under Recommendation ITU-T A.8 procedures. ii Rec. ITU-T Y.1292 (09/2008) 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
11、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 Telecommunication Standardization Assembly (WTSA
12、), 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 of information technology which fall wi
13、thin 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 operating agency. Compliance with this Recomm
14、endation 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“ or some other obligatory language such
15、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 practice or implementation of this Recommenda
16、tion 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 development process. As of the date of approval
17、 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 therefore strongly urged to consult the TSB pate
18、nt database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 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.1292 (09/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and Definitions 2 3.1 Terms
19、defined elsewhere 2 3.2 Terms defined in this Recommendation. 2 4 Abbreviations and acronyms 3 5 Conventions 4 6 Overview 4 6.1 Service aspects 4 6.2 General customization model. 4 6.3 Service level agreements (SLAs) . 5 6.4 Menu-based network customization capabilities 6 6.5 Customer expectations 7
20、 6.6 Network capability requirements . 7 7 Functional capabilities 8 7.1 Overview 8 7.2 Naming, addressing and identification capabilities 8 7.3 End-user grouping capability . 9 7.4 Application clustering capability 9 7.5 Information navigation and query capabilities. 9 7.6 Auto-discovery and auto-c
21、onfiguration capabilities 9 7.7 Information access control and security capabilities 10 7.8 End-to-end transparency capability 10 7.9 Connection configuration capability 11 7.10 Routing and forwarding control capabilities 11 7.11 Alternative path selection and multi-homing capabilities 12 7.12 Mobil
22、ity control and management capabilities 12 7.13 Traffic measurement and usage parameter control capabilities . 13 7.14 SLA negotiation capabilities 13 7.15 End-to-end QoS provision and priority assignment capabilities 13 7.16 Information storage and directory processing capabilities. 13 7.17 Segment
23、 OAM and end-to-end OAM capabilities . 14 7.18 Virtual private network configuration capability . 14 7.19 Billing and charging capabilities 14 7.20 Client/server management and agent management capabilities. 15 8 Security considerations. 15 iv Rec. ITU-T Y.1292 (09/2008) Page Appendix I Service proc
24、edures and applications scenarios 17 I.1 Customizable personal directory services 17 I.2 Customizable access control services. 20 I.3 Customizable end-to-end QoS services 23 I.4 End-user customizable location monitoring services. 26 I.5 Customizable home networking services . 29 I.6 Client networkin
25、g services with QoS and security. 31 Appendix II Example of functional architecture and service creation scenario for end-user customizable VPN services. 34 Bibliography. 36 Rec. ITU-T Y.1292 (09/2008) v Introduction Recommendation ITU-T Y.1292 describes the framework for requirements and capabiliti
26、es to enable the customization of IP networks and related IP service and IP transfer capability to meet the customers needs (see Recommendations ITU-T Y.1001 and ITU-T Y.1241). The framework provided in this Recommendation includes an architectural model, high-level service requirements and function
27、al capabilities. In addition, this Recommendation identifies the application scenarios and service procedures applicable to the context of customization using the capabilities made available to and/or performed by the customer of IP services. In general, customization refers to the degree of managea
28、bility or controllability as exercised by the customer via a suitable agent. Such agent-based architecture is based on principles similar to those described in Recommendations ITU-T X.160 and ITU-T Y.130. Rec. ITU-T Y.1292 (09/2008) 1 Recommendation ITU-T Y.1292 Customizable IP networks (CIP): Frame
29、work for the requirements and capabilities related to the customization of IP service networks by customers 1 Scope This Recommendation covers the following: General overview and description of concepts related to the customization of IP services and related IP network aspects. General model of a cu
30、stomizable IP network from the end users perspective. Definition of and requirements for the service capabilities offered to an end user for customization purposes. Functional capabilities that can be controlled by the end user of a customizable IP network. In addition, Appendix I provides a descrip
31、tion of application scenarios and service procedures used by the end user of a customizable IP network. Note that the scope is restricted to IP networks when IP layer networks as defined in ITU-T G.809 and operation within the NGN transport stratum as defined in ITU-T Y.2011 are considered. The deta
32、iled mechanisms for supporting the capabilities of a customizable IP network are not covered by the scope of this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendati
33、on. 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 references li
34、sted 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 G.809 Recommendation ITU-T G.809 (2003), Functional architecture of connec
35、tionless layer networks. ITU-T M.60 Recommendation ITU-T M.60 (1993), Maintenance terminology and definitions. ITU-T M.3050.x Recommendations ITU-T M.3050.x-series (2007), Enhanced Telecom Operations Map (eTOM). ITU-T M.3060 Recommendation ITU-T M.3060/Y.2401 (2006), Principles for the Management of
36、 Next Generation Networks. ITU-T Y.1001 Recommendation ITU-T Y.1001 (2000), IP framework A framework for convergence of telecommunications network and IP network technologies. 2 Rec. ITU-T Y.1292 (09/2008) ITU-T Y.1241 Recommendation ITU-T Y.1241 (2001), Support of IP-based services using IP transfe
37、r capabilities. ITU-T Y.1311 Recommendation ITU-T Y.1311 (2002), Network-based VPNs Generic architecture and service requirements. ITU-T Y.1711 Recommendation ITU-T Y.1711 (2004), Operation it can be applied to various gateway routers or intermediate network equipment between end users and the netwo
38、rk. The packet filtering and security functions can be combined with specific protocols such as SIP, ITU-T H.323, FTP, etc. 7.8 End-to-end transparency capability One of the critical requirements is the support for seamless handover. End-to-end transparency is recommended to be maintained during han
39、dover since applications should run independently of the supporting infrastructure. The CIP providers network is recommended to support the following three types of end-to-end transparency: Location transparency With distributed computing technology, end users can gain access from anywhere regardles
40、s of the actual physical location of such servers. Network transparency The application server executes the corresponding control process independently of specific network types and end-user terminals. Protocol transparency Protocol transparency is achieved by providing a standardized user-to-networ
41、k interface, realizing independent service control processes, shielding complex network technical details from the service provision platform, and developing open communication network interfaces. The three types of transparency may be chosen by the end user. If the end user requires end-to-end tran
42、sparency, the CIP provider is recommended to check whether such end-to-end transparency can be supported. The CIP provider may have to restrict other functions, such as NAT or disguised traffic, that can disrupt the transparencies. In this case, there is a need to verify which functions disrupt loca
43、tion, network and protocol transparencies. Rec. ITU-T Y.1292 (09/2008) 11 7.9 Connection configuration capability The connection configuration capability allows the specification as to who is allowed to communicate with whom (e.g., end user, information service broker, information broker). There are
44、 three basic connection configurations: point-to-point, multicast and broadcast. Point-to-point connections may provide unidirectional and bidirectional, as well as symmetric and asymmetric, paths. For point-to-point connections, the CIP network can support the following features: Establishment, mod
45、ification or release at the request of two participating end users Establishment with unicast addressing/naming capability. A broadcast connection may provide unidirectional communication between one end user and other end users. This connection is one-to-many (all) during a particular initiated ses
46、sion. A multicast connection is the one-to-many relationship continued for the duration of a given initiated session. In this connection, one end user is the root, and the other end users are leaves. The root can send one copy of each packet and address it to the group of leaves wishing to receive i
47、t. End users can establish their own network configuration depending on their private resources and service/applications. End users may try to optimize their private communication configuration considering the communication cost and performance. 7.10 Routing and forwarding control capabilities Prope
48、r routing paths between the source and the destination are decided according to the traffic contract and overall network traffic condition. The routing paths between the source and the destination are selected by end users, e.g., best effort, VPNs, managed IP facilities. Based on the end users ident
49、ified routing selection, future routings can occur based on a definite routing policy. For connectionless transfer, the router forwards the IP packets with their respective QoS information and end user requirements along a selected routing link. The routing algorithm can be classified according to routing decision processes that are generally applied to end-to-end or hop-by-hop connections. For network scalability and robustness, some combinations of routing decision processes may be used for specific connections
