1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T M.3341TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2003) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Telecommunications management network Requirements for
2、 QoS/SLA management over the TMN X-interface for IP-based services ITU-T Recommendation M.3341 ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction and general principles of maintena
3、nce and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links
4、 M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 International public telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport networ
5、k M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600M.3999 Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.3341 (12/2003) i ITU-T Recommendation M.3341 Require
6、ments for QoS/SLA management over the TMN X-interface for IP-based services Summary This Recommendation addresses end-to-end Quality of Service (QoS) information collection, aggregation and exchange between Service Customers, Service Providers and Network Operators. In the context of this Recommenda
7、tion, Service Providers (SPs) include Telecom SPs, Internet SPs, Application SPs and Content SPs. Service Customers include end-Customers and other SPs. Functions and interfaces required to ensure end-to-end QoS classes are specified for the complete service life cycle. Source ITU-T Recommendation M
8、.3341 was approved on 14 December 2003 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. Keywords End-to-end, IP, Management, Measurement Point, Network Operator, Observation, Quality of Service (QoS), Service Customer, Service Provider, X-interface. ii ITU-T Rec. M.33
9、41 (12/2003) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff q
10、uestions 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 groups which, in turn, produce Recommendat
11、ions 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 ISO and IEC. NOTE In this Recommendatio
12、n, 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 provisions (to ensure e.g. interoperability or
13、 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 words does not suggest that compliance
14、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 concerning the evidence, validity or ap
15、plicability 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 by patents, which may be required to im
16、plement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2004 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the p
17、rior written permission of ITU. ITU-T Rec. M.3341 (12/2003) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions . 2 4 Abbreviations and Acronyms . 3 5 Service life cycle and QoS 4 5.1 Service product planning and development . 4 5.2 Negotiation and sales 4 5.3 Implementation. 5 5.4 E
18、xecution 5 5.5 Assessment . 5 6 QoS classes and traffic types 5 7 QMS functional requirements 5 7.1 QMS framework. 5 7.2 Basic requirements . 6 7.3 Business level requirements (use cases). 8 7.4 Specification level requirements 10 8 Interface requirements 18 Annex A QMS management scenarios . 19 A.1
19、 Implementation phase (service orders and provision) 20 A.2 Execution phase (monitor, surveillance) 20 ITU-T Rec. M.3341 (12/2003) 1 ITU-T Recommendation M.3341 Requirements for QoS/SLA management over the TMN X-interface for IP-based services 1 Scope This Recommendation addresses end-to-end quality
20、 of service (QoS) information collection, aggregation and exchange between service customers, service providers and network operators for IP-based services. In the context of this Recommendation, service providers (SPs) include telecom SPs, Internet SPs, application SPs and content SPs. Service cust
21、omers include end-customers and other SPs. Functions and interfaces required to manage end-to-end QoS are specified for the complete service life cycle. This Recommendation provides requirements in the form of use cases and preliminary information related to the analysis phase. This Recommendation a
22、lso recognizes the business need to manage QoS across multiple SPs. 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 indicated were va
23、lid. 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 Recommendation
24、s 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 1 ITU-T Recommendation G.1010 (2001), End-user multimedia QoS categories. 2 ITU-T Recommendation M.1530 (1999), Network maintenance information
25、. 3 ITU-T Recommendation M.1532 (2000), Network maintenance service performance agreement (MSPA). 4 ITU-T Recommendation M.1535 (1996), Principles for maintenance information to be exchanged at customer contact point (MICC). 5 ITU-T Recommendation M.1537 (1997), Definition of maintenance information
26、 to be exchanged at customer contact point (MICC). 6 ITU-T Recommendation M.1539 (1999), Management of the grade of network maintenance services at the maintenance service customer contact point (MSCC). 7 ITU-T Recommendation M.2301 (2002), Performance objectives and procedures for provisioning and
27、maintenance of IP-based networks. 8 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. 9 ITU-T Recommendation M.3020 (2000), TMN Interface Specification Methodology. 10 ITU-T Recommendation M.3200 (1997), TMN management services and telecommunications managed
28、 areas: overview. 11 ITU-T Recommendation M.3208.1 (1997), TMN management services for dedicated and reconfigurable circuits network: Leased circuit services. 12 ITU-T Recommendation M.3350 (Draft) (2004), TMN service management requirements for information interchange across the TMN X-interface to
29、support provisioning of telecommunication capabilities for disaster relief operations and mitigation. 2 ITU-T Rec. M.3341 (12/2003) 13 ITU-T Recommendation M.3400 (2000), TMN management functions. 14 ITU-T Recommendation Q.822 (1994), Stage 1, stage 2 and stage 3 description for the Q3 interface Per
30、formance management. 15 ITU-T Recommendation X.730 (1992), Information technology Open Systems Interconnection Systems Management: Object management function. 16 ITU-T Recommendation Y.1001 (2000), IP framework A framework for convergence of telecommunications network and IP network technologies. 17
31、 ITU-T Recommendation Y.1221 (2002), Traffic control and congestion control in IP-based networks. 18 ITU-T Recommendation Y.1540 (2002), Internet protocol data communication service IP packet transfer and availability performance parameters. 19 ITU-T Recommendation Y.1541 (2002), Network performance
32、 objectives for IP-based services. 20 TeleManagement Forum GB 917 (2001), SLA Management Handbook GB 917, Ver. 1.5. 21 OMG Document formal/2003-03-01, Unified Modeling Language (UML), Version 1.5. 3 Terms and definitions This Recommendation defines the following terms: 3.1 measurement point: The phy
33、sical or logical point at which measurements can be made and to which the data obtained is related, e.g., a measurement point in a network or a step in the business process dependant upon the service life cycle. In the implementation phase of the service life cycle, it could be the time that an orde
34、r is received by the service provider. 3.2 observation: An observation is used by the service customer to monitor the QoS of the telecommunication service provided to the SC by the SP. An observation is associated with exactly two measurement points. 3.3 end-to-end QoS: The QoS service level metrics
35、 relevant to the service being delivered as perceived by the SC. M.3341_F3-1MP Measurement PointISPTSP TSPSC SCNONONONOMP-a MP-b MP-c MP-d MP-e MP-f MP-g MP-hObservationFigure 3-1/M.3341 Measurement points and observation Figure 3-1 shows an example of Measurement Points (MP) and an Observation (Ob)
36、 in a typical network. The Internet Service Provider (ISP) receives telecommunication services from two Telecommunication Service Providers (TSPs). Network Operators (NOs) define the Measurement Points (MPs) at each end of their responsible part of the network. They have responsibilities to observe
37、their part of the network. MP-a and MP-b ITU-T Rec. M.3341 (12/2003) 3 are defined at the ingress and egress of one NOs network. Likewise, MP-g and MP-h are defined at the ingress and egress of another NOs network. Each TSP receives services from two Network Operators (NOs). TSPs have responsibiliti
38、es to observe their part of the networks, in Figure 3-1, spanning across two NOs networks. The ISP, which has a primary contract with the Service Customer (SC), has the responsibility to observe end-to-end QoS of the entire network, not merely a part of one TSP, and also has the responsibility to pr
39、ovide the observation data to SC. The SC is able to define an observation between the measurement points MP-a and MP-h. The observation provides QoS measurements from the ingress to the egress of the ISPs network regardless of the service providers or network operators involved. 4 Abbreviations and
40、acronyms This Recommendation uses the following abbreviations: 3GPP Third Generation Partnership Project C Customer ID Identificator IP Internet Protocol ISP Internet Service Provider ITU-T International Telecommunication Union Telecommunication Standardization Sector MP Measurement Point NO Network
41、 Operator NP Network Performance Ob Observation OMG Object Management Group P Provider PM Performance Management QMS QoS/SLA Management Service QoS Quality of Service QoSMS QoS management in a multi-service provider environment SC Service Customer SLA Service Level Agreement SP Service Provider TMF
42、TeleManagement Forum TMN Telecommunications management network TSP Telecommunication Service Provider VoIP Voice over IP XML eXtensible Markup Language 4 ITU-T Rec. M.3341 (12/2003) 5 Service life cycle and QoS Management of QoS and associated SLAs require interaction between many telecom operations
43、 business processes and TMN management services as defined in ITU-T Rec. M.3200 and TMN management function sets as defined in ITU-T Rec. M.3400. In order to understand and analyse these interactions, there are at least five phases of the service life cycle that should be considered. These five phas
44、es are shown in Figure 5-1: Service product planning and development; Negotiation and sales of a service product; Implementation (configuration, provisioning and commissioning) of a service product; Operation and maintenance of a service product; Periodic assessment of the QoS of a service and wheth
45、er it meets the SLA. M.3341_F5-1Develop templatesand parametricboundariesNegotiateindividualcontractsTake line/serviceorders andprovisionMonitor,surveillance,maintain, billReassessProduct/servicedevelopmentNegotiationand sales Implementation Execution AssessmentFigure 5-1/M.3341 Service life cycle (
46、Figure 5-1/GB917) The following subclauses describe those aspects of each phase related to QoS and SLA management across the X-interface between two TMN domains, but not all of the aspects involved in each phase within a single TMN domain. Furthermore, in some cases e.g., leased circuit services, th
47、e negotiation and sales phase is sometimes split into two phases: pre-ordering and ordering. Descriptions of these five phases are described in detail in GB 917. 5.1 Service product planning and development When planning and developing a service product, consideration must be given to a number of Qo
48、S and SLA aspects. In addition to the generic parameters there are technology-specific parameters. For example, in the case of IP-based services, these parameters and limits should be based on ITU-T Recs Y.1540, Y.1541 and M.2301. These Recommendations define QoS classes and the Network Performance
49、(NP) parameters and limits designed to support certain applications e.g., VoIP, streaming video, etc. However, if the service is a pure packet delivery service, the QoS parameters and limits will be the same as the NP. Further information is given in 6. 5.2 Negotiation and sales During this phase, the service provider must negotiate and agree with the customer technical details of specific instances of the service product offered. The QoS parameters and limits may be the same as those offered in the
