ITU-T Y 2212-2008 Requirements of managed delivery services (Study Group 13)《传输业务管理要求 13号研究组》.pdf

1、 International Telecommunication Union ITU-T Y.2212TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (02/2008) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Service aspects: Service capabilities and service architecture Req

2、uirements of managed delivery services Recommendation ITU-T Y.2212 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 Network as

3、pects 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, access

4、, 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 Framework

5、s 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.2399 N

6、etwork 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.2212 (02/2008) i Recommendation ITU-T Y.2212 Requirements of managed de

7、livery services Summary Recommendation ITU-T Y.2212 provides the service and functional requirements of managed delivery services (MDS). Source Recommendation ITU-T Y.2212 was approved on 29 February 2008 by ITU-T Study Group 13 (2005-2008) under Recommendation ITU-T A.8 procedure. Keywords Always o

8、n service (AoS), managed delivery services (MDS), MDS control, MDS functional architecture model, MDS service classification, MDS service partnership, MDS service profile, MDS service scenario, non-subscription based MDS, on-demand service (ODS), subscription-based MDS. ii Rec. ITU-T Y.2212 (02/2008

9、) 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 responsible for st

10、udying 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-T study gr

11、oups 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 basis with

12、 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 mandatory provis

13、ions (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. The use of such

14、 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 takes no position

15、 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 property, protected

16、 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 2009 All rights reserved. No part of th

17、is publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.2212 (02/2008) iii 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 Abbreviations and acronyms 2 5 C

18、onventions 3 6 MDS overview 3 6.1 MDS business model 3 6.2 MDS service provisioning 4 7 Service requirements of MDS 5 7.1 Requirements for MDS service classification 6 7.2 Requirements for MDS service partnership . 6 7.3 Requirements for the use of profiles for MDS . 6 7.4 MDS control requirements .

19、 7 7.5 Authentication and authorization requirements 7 8 Profiles for MDS management . 7 8.1 General requirements of MDS related profiles 7 8.2 MDS service profile . 8 8.3 Third-party provider profile . 9 8.4 User profile. 9 8.5 MDS control profile . 10 9 Functional architecture . 12 9.1 Functional

20、architecture model 12 9.2 MDS functional elements. 16 10 MDS service scenarios . 17 10.1 Subscription-based MDS service scenario . 17 10.2 Non-subscription based MDS service scenario 24 11 Security considerations. 26 iv Rec. ITU-T Y.2212 (02/2008) Introduction One of the advantages of the ITU-T NGN

21、is the openness formed by the whole of the ITU-T NGN architecture (Recommendation ITU-T Y.2001). The NGNs concept, principles and functional architectural model provides a great opportunity to initiate a more detailed development of various interfaces such as UNI, NNI, ANI, etc. NGN should have effi

22、cient and flexible capabilities to enable third-party providers and users to use NGN capabilities through the interfaces. This Recommendation describes “managed delivery services“ as the services that use ANI to enable the provision of managed delivery services between third-party providers and user

23、s. Rec. ITU-T Y.2212 (02/2008) 1 Recommendation ITU-T Y.2212 Requirements of managed delivery services 1 Scope The objective of this Recommendation is to describe the service and functional requirements of the managed delivery services (MDS) provided by an NGN provider to third-party providers via A

24、NI (application network interface), with features supported by the next generation network (NGN) ITU-T Y.2001, ITU-T Y.2011, ITU-T Y.2012, and ITU-T Y.2201. The service and functional requirements described in this Recommendation are built on the NGN general reference model ITU-T Y.2011 and generali

25、zed functional architecture ITU-T Y.2012. This Recommendation describes the service concept of MDS, the business model among players relevant to MDS, the service requirements of MDS, profiles for MDS management, the functional architecture model, MDS service scenarios, and security considerations fo

26、r MDS. This Recommendation describes several service scenarios to show how MDSs are operated. These service scenarios are described from a service procedural point of view, as well as in terms of the functional entities involved. 2 References The following ITU-T Recommendations and other references

27、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 therefore encouraged to investigat

28、e 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 stand-alone document, the status o

29、f a Recommendation. ITU-T Y.2001 Recommendation ITU-T Y.2001 (2004), General overview of NGN. ITU-T Y.2011 Recommendation ITU-T Y.2011 (2004), General principles and general reference model for next generation networks. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and arc

30、hitecture of the NGN release 1. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2006), Resource and admission control functions in 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.2701 (2007), Security requirements f

31、or 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 offers

32、capabilities and resources needed for the realization of applications. 2 Rec. ITU-T Y.2212 (02/2008) 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 managed delivery services (MDS): The services provided by an NGN provider to third-party providers with

33、 features supported by the NGN, in which comprehensive control capabilities for service delivery are available between third-party providers and their users. 3.2.2 MDS control profile: The set of information regarding service control, session control, resource control and transport control to suppor

34、t MDS. 3.2.3 MDS service profile: The sets of MDS service information to provide comprehensive control capabilities for service delivery between third-party providers and their users. 3.2.4 user: The user of the services of a third-party provider whose services are provided with managed delivery fea

35、tures facilitated through MDS. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AC Admission Control AMG-FE Access Media Gateway Functional Entity ANI Application Network Interface AoS Always on Service ASF ii) Third-party provider profile (this informa

36、tion is transferred from the third-party provider); iii) User profile (this information is transferred from the third-party provider); iv) MDS control profile (this information is maintained internally in the NGN provider); v) Others: for further study; b) The third-party provider is required to mai

37、ntain at least the following profiles: i) Third-party provider profile: Third-party provider identification information, service servers address and status information, and other information as needed (this information is required to be transferred to the NGN provider); ii) User profile (this inform

38、ation is transferred to the NGN provider); iii) Others: for further study; c) The user is required to have access to at least the following profiles: i) Third-party provider profile (this information is transferred from the third-party provider); ii) Others: for further study. Figure 8-1 shows the r

39、elationship of MDS-related profiles between players. 8 Rec. ITU-T Y.2212 (02/2008) Figure 8-1 Relationship of MDS-related profiles between players 8.2 MDS service profile An MDS service profile is recommended to be classified as one of several combinations, with various NGN network capabilities. The

40、 set of MDS service information is recommended to be selected by the third-party provider according to their service requirements. The basic information comprising the MDS service profile is as follows: CoS (class of services) information: This information relates to the differentiation of traffic h

41、andling (e.g., switching and routing) services, according to the service requirements corresponding to different classes of services, such as best effort, premium, etc. AC (admission control) information: This information relates to the admission control of MDS. Examples of priority classification s

42、chemes for admission of MDS include always admitted, premium class admitted, and admitted only when available, etc. BiC (bandwidth instantiation control) information: This information relates to the bandwidth control according to the service requirements, such as on-demand, permanent, fixed, variabl

43、e bandwidth, etc. SeC (security control) information: This information relates to the control of the security level, such as the level of firewalls, AAA, level of traversal in NAPT, privacy, etc. Multicast control information: This information relates to the multicast control of the MDS. Others: for

44、 further study Rec. ITU-T Y.2212 (02/2008) 9 Usage examples of MDS service profile are shown in Table 1. Table 1 Usage of MDS service profiles CoS AC BiC SeC Service examples Not provided BW pre-assigned network access Always admitted via predetermined AC policy Provided BW pre-assigned network acce

45、ss w/ security Not provided BoD BE class Admitted only when available Always on or Pre-scheduled or On-demand based Provided BoD w/ security Not provided IP-Media, Video phone service Always admitted via predetermined AC policy Provided IP-media/video phone Service w/ security Not provided Video pho

46、ne service, BoD Premium class Admitted only when available Always on or Pre-scheduled or On-demand based Provided VoD/BoD w/ security 8.3 Third-party provider profile This profile contains the relevant information of the third-party provider who has an MDS partnership with the NGN provider. The NGN

47、provider maintains and may modify this profile as required over the course of the partnership, to accommodate establishment, modification or cancellation of MDS. This profile is required to include the following information: Addresses of the servers of the third-party provider Server status informat

48、ion of the third-party provider Others: for further study This profile can optionally include the following information: Identifier of the third-party provider 8.4 User profile This profile contains relevant information regarding the users of the third-party provider. The NGN provider maintains this

49、 profile for each third-party provider. This profile is required to include the following information: Users IP address User name MDS service type (e.g., subscription-based MDS, non-subscription based MDS) Subscriber log in ID for network access in case of subscription-based MDS Detailed information about MDS service profile selected by the third-party provider (e.g., premium class for CoS, always admitted for AC, fixed bandwidth control for BiC, etc.) Others: for further study This profile c