ITU-T G 8601-2006 Architecture of service management in multi-bearer multi-carrier environment (Study Group 15)《多承载、多载波环境中的业务管理结构》.pdf

《ITU-T G 8601-2006 Architecture of service management in multi-bearer multi-carrier environment (Study Group 15)《多承载、多载波环境中的业务管理结构》.pdf》由会员分享，可在线阅读，更多相关《ITU-T G 8601-2006 Architecture of service management in multi-bearer multi-carrier environment (Study Group 15)《多承载、多载波环境中的业务管理结构》.pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T G.8601/Y.1391TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2006) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Packet over Transport aspects Service management SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL A

2、SPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Transport Architecture of service management in multi-bearer, multi-carrier environment ITU-T Recommendation G.8601/Y.1391 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE

3、 CONNECTIONS AND CIRCUITS G.100G.199 GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS G.200G.299 INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES G.300G.399 GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-R

4、ELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G.499 TRANSMISSION MEDIA CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPMENTS G.700G.799 DIGITAL NETWORKS G.800G.899 DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900G.999

5、 QUALITY OF SERVICE AND PERFORMANCE GENERIC AND USER-RELATED ASPECTS G.1000G.1999 TRANSMISSION MEDIA CHARACTERISTICS G.6000G.6999 DATA OVER TRANSPORT GENERIC ASPECTS G.7000G.7999 PACKET OVER TRANSPORT ASPECTS G.8000G.8999Ethernet over Transport aspects G.8000G.8099 MPLS over Transport aspects G.8100

6、G.8199 Quality and availability targets (continuation of G.82x series) G.8200G.8299 Service Management G.8600G.8699 ACCESS NETWORKS G.9000G.9999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. G.8601/Y.1391 (06/2006) i ITU-T Recommendation G.8601/Y.1391 Architectur

7、e of service management in multi-bearer, multi-carrier environment Summary This Recommendation defines a set of requirements that are applicable to Client Service Management in multi-carrier, multi-transport-technology networks. Source ITU-T Recommendation G.8601/Y.1391 was approved on 6 June 2006 b

8、y ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. G.8601/Y.1391 (06/2006) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Secto

9、r (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), which meets every

10、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 within ITU-Ts purview,

11、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 Recommendation is voluntary

12、. 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 as “must“ and the neg

13、ative 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 Recommendation may involve the

14、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 of this Recommendati

15、on, ITU had not received notice of intellectual property, protected by patents, which may be required to implement 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 2007

16、 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. G.8601/Y.1391 (06/2006) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions . 1 4 Acronyms and abbreviations 3 5 Conventions 4 5.1 Nom

17、enclature . 4 6 Introduction 4 7 General description of client service management. 5 7.1 General management areas. 5 7.2 OAM flow categories . 7 8 Business relationship models: Service provider to end customer 7 8.1 Single carrier: Ownership Model 0 (OM-0). 8 8.2 Multiple carriers . 10 8.3 Composite

18、 carrier scenarios . 16 9 Network transport technology 18 9.1 Drawing conventions 18 9.2 Candidate technologies. 19 9.3 Technology models 19 9.4 Applicability of technology models to ownership models. 22 10 Applicable client service types . 24 11 Management communication functions 24 11.1 Performanc

19、e information 25 11.2 Commands and responses. 26 11.3 Autonomous notification 26 11.4 Remotely located NE (CLE) software upgrades 27 12 Testing requirements 27 ITU-T Rec. G.8601/Y.1391 (06/2006) 1 ITU-T Recommendation G.8601/Y.1391 Architecture of service management in multi-bearer, multi-carrier en

20、vironment 1 Scope This Recommendation defines architectural requirements for the edge-to-edge management and/or control of client services transported over various transport network topologies and technologies. The services for which such management capabilities are required are included. The requir

21、ements for the transference of the management and/or control data between the edge points is described along with the requirements for accessibility to management and/or control information at some point in the network, other than the end point. The provision of such management services is also cons

22、idered in the context of business relationships that may be involved in the delivery of a service to, for example, the Service Provider, Network Operator(s) and the Enterprise End customer. Consideration is also given to the management and/or control of Customer Located Equipment which is owned by t

23、he Service Provider and carrying said services. Although the client service management detail is not within the scope of this Recommendation, consideration is given to three generic management and/or control functions: performance reporting, status reporting and client service control (e.g., loopbac

24、k, end node configuration, etc). This Recommendation describes the architecture for service management and/or control, and includes the reference points of the architecture. It does not define the implementation methodology or any of the interfaces that may need to be specified. 2 References The fol

25、lowing 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 valid. All Recommendations and other references are subject to revision; users of this Rec

26、ommendation 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 Recommendations is regularly published. The reference to a document within this Recommendation does no

27、t give it, as a stand-alone document, the status of a Recommendation. ITU-T Recommendation G.707/Y.1322 (2007), Network node interface for the synchronous digital hierarchy (SDH). ITU-T Recommendation G.709/Y.1331 (2003), Interfaces for the Optical Transport Network (OTN). ITU-T Recommendation G.806

28、 (2006), Characteristics of transport equipment Description methodology and generic functionality. 3 Terms and definitions This Recommendation defines the following terms: 3.1 anomaly: (See ITU-T Rec. G.806) The smallest discrepancy which can be observed between the actual and desired characteristic

29、s of an item. The occurrence of a single anomaly does not constitute an interruption in the ability to perform a required function. Anomalies are used as the input for the Performance Monitoring (PM) process and for the detection of defects. 2 ITU-T Rec. G.8601/Y.1391 (06/2006) 3.2 defect: (See ITU-

30、T Rec. G.806) The density of anomalies has reached a level where the ability to perform a required function has been interrupted. Defects are used as input for PM, the control of consequent actions, and the determination of fault cause. 3.3 degrade: A degrade is the presence of a defect for a suffic

31、ient period of time that impairs the ability of a resource to perform the desired function. 3.4 edge service: The service from the perspective of a single SOF. 3.5 edge-to-edge: The path serving the service that sources at a local SOF (Service Origination Function) and sinks at a remote SOF. 3.6 end

32、-to-end: The complete path that the customer/client signal takes that sources at a local Customer Equipment (CE) and sinks at the remote CE. 3.7 failure: (See ITU-T Rec. G.806) The fault cause persisted long enough to consider the ability of an item to perform a required function to be terminated. T

33、he item may be considered as failed; a fault has now been detected. 3.8 fault: (See ITU-T Rec. G.806) A fault is the inability of a function to perform a required action. This does not include an inability due to preventive maintenance, lack of external resources, or planned actions. 3.9 management

34、access point (MAP): The Management Access Point is the point in the transport network where the Management System has its point of contact for purposes of management and/or control. This MAP may be at any point in the transport network including at the edge of the transport network. 3.10 network res

35、ource: Resources that are owned and managed by the SP in support of the offered customer service. 3.11 service status: Service status indicates that the service is in one of four states. 1) Operational: Service is operating within the bounds of the established SLA. 2) Degraded: Service is operationa

36、l; however, its performance is degraded in reference to the SLA. 3) Failure: Service failure has occurred and is not operational. 4) In-test: Service is under control of service/network operator for maintenance actions. Service failure may be attributed to path level defects, service failures at the

37、 client link, or significant disparity in achieving adherence to the SLA. The Service Status is generated by each SOF. The Service Status is generated by comparing local edge-service PMs and remote edge-service PMs (conveyed between edges) to formulate edge-to-edge service PMs. These edge-to-edge se

38、rvice PMs are then compared to SLA thresholds to determine the operational disposition of the service. 3.12 service management function (SMF): A logical entity found within a service-aware NE that performs Management Access Point (MAP) and/or Test Access Point (TAP) functions. 3.13 service originati

39、on function (SOF): The Network Element (NE) function, managed by the Service Provider (SP) which represents the edge optical service point. It performs customer frame/signal mapping to the SP optical network. Typically incorporates a SMF. 3.14 user network interface (UNI): The UNI is the bearer betw

40、een the CPE and the Network. ITU-T Rec. G.8601/Y.1391 (06/2006) 3 4 Acronyms and abbreviations This Recommendation uses the following abbreviations: C/R Command Response CE Customer Equipment CLE_NE Customer Located Equipment Network Element CPE Customer Premises Equipment CSM Client Service Managem

41、ent EM Element Management ETH Ethernet MAC layer network ETY Ethernet Physical interface FD Flow Domain MAP Management Access Point NE Network Element NM Network Manager NMS Network Management System NNI Network to Network Interface NO Network Operator OAM Operations, Administration and Maintenance

42、OAMiF OAM in Frame OM-n Ownership Model n OSS Operations Support System OTN Optical Transport Network PDH Plesiochronous Digital Hierarchy PE Provider Edge PL Private Line PM Performance Monitoring PTE Path Terminating Equipment SDH Synchronous Digital Hierarchy SLA Service Level Agreement SM Servic

43、e Management SMF Service Management Function SNC SubNetwork Connection SOF Service Origination Function SP Service Provider SS Service Status TAP Test Access Point UNI User Network Interface 4 ITU-T Rec. G.8601/Y.1391 (06/2006) 5 Conventions 5.1 Nomenclature For purposes of signal identification, th

44、e following nomenclature will be used in this Recommendation. Signal Names will have the format: Letter.number.number Where: Letter represents the Service Provider (SP): (e.g., R = Red SP; B = Blue SP; G = Green SP; P = Purple SP). Number represents the individual signal number belonging to the SP.

45、Number represents the Ownership Model (OM). Examples: R.3.1 is Owned by Red SP (SP_R), and is SP_Rs 3rd signal and is configured as OM-1. B.1.0 is Owned by Blue SP (SP_B), and is SP_Bs 1st signal and is configured as OM-0. P.2.2 is Owned by Purple SP (SP_P), and is SP_Ps 2nd signal and is configured

46、 as OM-2. NOTE The ownership model at each edge of a client signal connection may be different; this is dependant on the location of the MAP and whether the SP owns the edge device. 6 Introduction Service providers are demanding a simple service model for transport of Client Data Services over netwo

47、rks that fits their existing operational model. That is, the Client Data private line service must be analogous to existing private line services, and more importantly must interface into existing management systems. This Recommendation is structured with numbered requirements integrated into the de

48、scriptive normative clauses. In some instances where a requirement is applicable to more than one clause, there will be a reference to the original instance of that requirement. All requirements will appear on a separate line in Bold. NOTE The numbering is not always contiguous to allow for insertio

49、n of requirements if and when this Recommendation is updated. R1 Management of the Client Private Line Service should interface to existing management systems. R2 A defect or failure in a given layer network should not cause multiple alarm events to be raised, nor cause unnecessary corrective actions to be taken, in any higher level client layer networks. This applies to all client layer network types that the Private Line service is required to carry. R3 If a network defect or failure occurs in an interface, mapping function, or path, it is necessar