ITU-T Y 1391-2006 Architecture of service management in multi bearer multicarrier environment《多承载、多载波环境中的业务管理结构》.pdf

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 Ethernet over Transport aspects SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-G

2、ENERATION NETWORKS Internet protocol aspects Transport Architecture of service management in multi bearer, multicarrier environment CAUTION ! PREPUBLISHED RECOMMENDATION This prepublication is an unedited version of a recently approved Recommendation. It will be replaced by the published version aft

3、er editing. Therefore, there will be differences between this prepublication and the published version. 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

4、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 four years, est

5、ablishes 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, the necessary s

6、tandards 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. However, the

7、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 negative equivalent

8、s 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 use of a claimed

9、 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 Recommendation, ITU had/had

10、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 2006 All rights

11、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) Prepublished version 1ITU-T Recommendation G.8601/Y.1391 (ex. G.asm) Architecture of Service Management in multi bearer, multicarrier envi

12、ronment Summary This Recommendation defines a set of requirements that are applicable to Client Service Management in multi-carrier, multi-transport-technology networks. ITU-T Rec. G.8601/Y.1391 (06/2006) Prepublished version 2ITU-T Recommendation G.8601/Y.1391 Architecture of Service Management in

13、multi bearer, multicarrier environment 1 Scope 4 2 References.4 3 Terms and definitions .4 4 Acronyms and abbreviations 6 5 Conventions 7 5.1 Nomenclature .7 6 Introduction 7 7 Generic Description of Client Service Management8 7.1 Generic Management Areas .9 7.1.1 End-to-End Management10 7.1.2 Acces

14、s Link Management 10 7.1.3 Edge-to-edge Management.10 7.1.4 Transport Management.10 7.2 OAM flow categories. 11 7.2.1 Customer OAM 11 7.2.2 UNI OAM.11 7.2.3 Path OAM.11 7.2.4 Service OAM11 8 Business Relationship Models: Service Provider to End Customer.11 8.1 Single Carrier: Ownership Model 0 (OM-0

15、)12 8.1.1 Single Carrier Dark Fibre connection.13 8.2 Multiple Carriers 15 8.2.1 Ownership Model 1 (OM-1).15 8.2.2 Ownership Model 2 18 8.2.3 Incompatible Edge device 20 8.3 Composite Carrier Scenarios21 9 Network Transport Technology25 9.1 Drawing Conventions.26 9.2 Candidate Technologies .26 9.3 T

16、echnology Models26 9.3.1 Single Technology Model 26 ITU-T Rec. G.8601/Y.1391 (06/2006) Prepublished version 39.3.2 Multiple Technology Models .26 9.4 Applicability of Technology Models to Ownership Models29 10 Applicable Client Service Types 31 11 Management Communication Functions31 11.1 Performanc

17、e Information32 11.2 Commands and responses.34 11.3 Autonomous Notification .34 11.4 Remotely Located NE (CLE) Software Up-grades35 12 Testing Requirements .35 ITU-T Rec. G.8601/Y.1391 (06/2006) Prepublished version 41 Scope This Recommendation defines architectural requirements for the edge-to-edge

18、 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 requirements for the transference of the management and/or control data between the edge points is

19、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 considered in the context of business relationships that may be involved in the delivery of a ser

20、vice 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 the Service Provider and carrying said services. Although the client service management detail

21、 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. loopback, end node configuration etc). This Recommendation describes the architecture for service man

22、agement 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 ITU-T Recommendation G.707/Y.1322 (2000), Network node interface for the synchronous digital hierarchy

23、 (SDH). ITU-T Recommendation G.709/Y.1331 (2003), Interfaces for the Optical Transport Network (OTN). ITU-T Recommendation G.806 (2004), Characteristics of transport equipment Description methodology and generic functionality. 3 Terms and definitions This Recommendation defines the following terms:

24、3.1 Anomaly: (See G.806) “The smallest discrepancy which can be observed between the actual and desired characteristics 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 Performanc

25、e Monitoring (PM) process and for the detection of defects.” 3.2 Defect: (See 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 faul

26、t cause.” 3.3 Degrade: A degrade is the presence of a defect for a sufficient period of time that impairs the ability of a resource to perform the desired function. ITU-T Rec. G.8601/Y.1391 (06/2006) Prepublished version 53.4 Edge Service: The service from the perspective of a single SOF. 3.5 Edge-t

27、o-edge: The path serving the service that source at a local SOF (Service Origination Function) and sinks at a remote SOF. 3.6 End-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 G.806) “The

28、fault cause persisted long enough to consider the ability of an item to perform a required function to be terminated. The item may be considered as failed; a fault has now been detected.” 3.8 Fault: (See G.806) “A fault is the inability of a function to perform a required action. This does not inclu

29、de an inability due to preventive maintenance, lack of external resources, or planned actions.” 3.9 MAP: Management Access Point. 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

30、 may be at any point in the transport network including at the edge of the transport network. 3.10 Network resource: 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)

31、Operational: Service is operating within the bounds of the established SLA. 2) Degraded: Service is operational; 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 oper

32、ator for maintenance actions. Service failure may be attributed to path level defects, service failures at the 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

33、 remote edge-service PMs (conveyed between edges) to formulate edge-to-edge service PMs. These edge-to-edge service PMs are then compared to SLA thresholds to determine the operational disposition of the service. 3.12 SMF: (Service Management Function.) A logical entity found within a service-aware

34、NE that performs Management Access Point (MAP) and/or Test Access Point (TAP) functions. ITU-T Rec. G.8601/Y.1391 (06/2006) Prepublished version 63.13 SOF: (Service Origination Function.) Network Element (NE) function, managed by the Service Provider (SP) which represents the edge optical service po

35、int. It performs customer frame/signal mapping to the SP optical network. Typically incorporates a SMF. 3.14 UNI: (User Network Interface.) The UNI is the bearer between the CPE and the Network 4 Acronyms and abbreviations This Recommendation uses the following abbreviations: ETH Ethernet MAC layer

36、network ETY Ethernet Physical interface CE Customer Equipment CLE_NE Customer Located Equipment Network Element CPE Customer Premise Equipment C/R Command Response CSM Client Service Management EM Element Management FD Flow Domain MAP Management Access Point NE Network Element NM Network Manager NMS

37、 Network Management System NNI Network to network interface NO Network Operator OAM Operations, Administration and Maintenance OAMiF OAM in Frame OM-n Ownership Model n OSS Operator Supervisory System OTN Optical Transport Network PE Provider Edge PL Private Line PM Performance Monitoring PDH Plesio

38、chronous Digital Hierarchy PTE Path Terminating Equipment SDH Synchronous Digital Hierarchy SLA Service Level Agreement SM Service Management SMF Service Management Function ITU-T Rec. G.8601/Y.1391 (06/2006) Prepublished version 7SNC Sub Network Connection SOF Service Origination Function SP Servic

39、e Provider SS Service Status TAP Test Access Point UNI User Network Interface 5 Conventions 5.1 Nomenclature For purposes of signal identification the following nomenclature will be used in this recommendation Signal Names will have the format: Letter.number.number Where Letter represents the Servic

40、e 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 Number represents the Ownership Model (OM) Examples: R.3.1 is Owned by Red SP (SP_R), and is SP_Rs 3rdsignal and is configured as OM-1 B.1.0 is Owned by Blue

41、 SP (SP_B), and is SP_Bs 1stsignal and is configured as OM-0 P.2.2 is Owned by Purple SP (SP_P), and is SP_Ps 2ndsignal and is configured as OM-2 Note: The ownership model at each edge of a client signal connection may be different; this is dependant of the location of the MAP and whether the SP own

42、s the edge device. 6 Introduction Service providers are demanding a simple service model for transport of Client Data Services over networks that fits their existing operational model. That is, the Client Data private line service must be analogous to existing private line services, and more importa

43、ntly must interface into existing management systems. This Recommendation is structured with numbered requirements integrated into the descriptive 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

44、 requirement. All requirements will appear on a separate line in Bold. Note: The numbering is not always contiguous to allow for insertion of requirements if and when this document is updated. R1 Management of the Client Private Line Service should interface to existing management systems. R2 A defe

45、ct 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. ITU-T Rec. G

46、.8601/Y.1391 (06/2006) Prepublished version 8R3 If a network defect or failure occurs in an interface, mapping function, or path, it is necessary to detect it, diagnose it, localise it, notify the NMS/OSS and take corrective actions appropriate to the type of defect. The primary objective is to redu

47、ce operating costs by minimising service interruptions, operational repair times and operational resource. The business drivers for managed Client Services are: - Manageability of the network Management of the service offered to the customer Interconnection of billing/management data to carrier OSS

48、systems Accessibility of Performance data for confirmation of Service level agreement (SLA) conformance. Also of importance is the manageability of remotely located Customer Located Equipment (CLE). Several business models are used to define the requirements for Client Service Management (CSM). The

49、Network Technologies and combinations thereof are defined, as are the applicable Client Service types. R4 To confirm SLA compliance with the customer, the Service Provider (SP) must have visibility of the performance of the Client Interface at the edge of the transport network. a) The edge NE must support the ability of a remote device to query service configuration information. (i.e., Service or Circuit ID, service PM, thresholds, etc) R5 To confirm SLA compliance with the customer, the SP must have visibility of the mapping function performance at the edg