ITU-T Y 1701-2007 Common equipment management function requirements (Study Group 15)《一般设备管理功能要求 研究组15》.pdf

《ITU-T Y 1701-2007 Common equipment management function requirements (Study Group 15)《一般设备管理功能要求 研究组15》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Y 1701-2007 Common equipment management function requirements (Study Group 15)《一般设备管理功能要求 研究组15》.pdf（96页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T G.7710/Y.1701TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2007) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Data over Transport Generic aspects Transport network control aspects SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE

2、, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Operation, administration and maintenance Common equipment management function requirements ITU-T Recommendation G.7710/Y.1701 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORK

3、S INTERNATIONAL TELEPHONE 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 TEL

4、EPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G.499 TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPMENTS G.700G.799 DIGITAL NETWORKS G.800G.899 DIGITA

5、L SECTIONS AND DIGITAL LINE SYSTEM G.900G.999 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 General G.7000G.7099 Transport network control aspects G.7700G.7799 PACKET O

6、VER TRANSPORT ASPECTS G.8000G.8999ACCESS NETWORKS G.9000G.9999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. G.7710/Y.1701 (07/2007) i ITU-T Recommendation G.7710/Y.1701 Common equipment management function requirements Summary ITU-T Recommendation G.7710/Y.1701

7、addresses the equipment management functions (EMFs) inside a transport network element that are common to multiple technologies. For example, common applications are described for date users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent ed

8、ition 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 of a Recommendation. ITU-T G.805 ITU-T Recommenda

9、tion G.805 (2000), Generic functional architecture of transport networks. ITU-T G.806 ITU-T Recommendation G.806 (2006), Characteristics of transport equipment Description methodology and generic functionality. ITU-T G.808.1 ITU-T Recommendation G.808.1 (2006), Generic protection switching Linear tr

10、ail and subnetwork protection. ITU-T G.809 ITU-T Recommendation G.809 (2003), Functional architecture of connectionless layer networks. ITU-T G.826 ITU-T Recommendation G.826 (2002), End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connect

11、ions. ITU-T G.827 ITU-T Recommendation G.827 (2003), Availability performance parameters and objectives for end-to-end international constant bit-rate digital paths. ITU-T G.828 ITU-T Recommendation G.828 (2000), Error performance parameters and objectives for international, constant bit-rate synchr

12、onous digital paths. ITU-T G.829 ITU-T Recommendation G.829 (2002), Error performance events for SDH multiplex and regenerator sections. ITU-T G.7712 ITU-T Recommendation G.7712/Y.1703 (2003), Architecture and specification of data communication network. 2 ITU-T Rec. G.7710/Y.1701 (07/2007) ITU-T M.

13、20 ITU-T Recommendation M.20 (1992), Maintenance philosophy for telecommunication networks. ITU-T M.2101 ITU-T Recommendation M.2101 (2003), Performance limits for bringing-into-service and maintenance of international multi-operator SDH paths and multiplex sections. ITU-T M.2110 ITU-T Recommendatio

14、n M.2110 (2002), Bringing into service international multi-operator paths, sections and transmission systems. ITU-T M.2120 ITU-T Recommendation M.2120 (2002), International multi-operator paths, sections and transmission systems fault detection and localization procedures. ITU-T M.2140 ITU-T Recomme

15、ndation M.2140 (2000), Transport network event correlation. ITU-T M.3010 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3013 ITU-T Recommendation M.3013 (2000), Considerations for a telecommunications management network. ITU-T M.3016 ITU-T Recomme

16、ndation M.3016 series (2005), Security for the management plane: ITU-T Rec. M.3016.0 Overview. ITU-T Rec. M.3016.1 Security requirements. ITU-T Rec. M.3016.2 Security services. ITU-T Rec. M.3016.3 Security mechanism. ITU-T Rec. M.3016.4 Profile proforma. ITU-T M.3060 ITU-T Recommendation M.3060/Y.24

17、01 (2006), Principles for the Management of Next Generation Networks. ITU-T M.3100 ITU-T Recommendation M.3100 (2005), Generic network information model. ITU-T M.3400 ITU-T Recommendation M.3400 (2000), TMN management functions. ITU-T Q.821 ITU-T Recommendation Q.821 (2000), Stage 2 and stage 3 desc

18、ription for the Q3 interface Alarm surveillance. ITU-T Q.822 ITU-T Recommendation Q.822 (1994), Stage 1, stage 2 and stage 3 description for the Q3 interface Performance management. ITU-T X.700 ITU-T Recommendation X.700 (1992), Management framework for Open Systems Interconnection (OSI) for CCITT a

19、pplications. ITU-T X.701 ITU-T Recommendation X.701 (1997), Information technology Open Systems Interconnection Systems management overview. ITU-T X.720 ITU-T Recommendation X.720 (1992), Information technology Open Systems Interconnection Structure of management information: Management information

20、model. ITU-T X.731 ITU-T Recommendation X.731 (1992), Information technology Open Systems Interconnection Systems Management: State management function. ITU-T X.733 ITU-T Recommendation X.733 (1992), Information technology Open Systems Interconnection Systems Management: Alarm reporting function. IT

21、U-T Rec. G.7710/Y.1701 (07/2007) 3 ITU-T X.734 ITU-T Recommendation X.734 (1992), Information technology Open Systems Interconnection Systems Management: Event report management function. ITU-T X.735 ITU-T Recommendation X.735 (1992), Information technology Open Systems Interconnection Systems Manag

22、ement: Log control function. ITU-T X.744 ITU-T Recommendation X.744 (1996), Information technology Open Systems Interconnection Systems Management: Software management function. ITU-T X.754 ITU-T Recommendation X.754 (2000), Enhanced event control function. 3 Definitions 3.1 Terms defined elsewhere

23、This Recommendation uses the following terms defined elsewhere: 3.1.1 Terms defined in ITU-T G.806: atomic function (AF) management point (MP) 3.1.2 Terms defined in ITU-T M.3010: network element (NE) network element function (NEF) workstation function (WF) Q-Interface operations system (OS) 3.1.3 T

24、erm defined in ITU-T M.3013: message communication function (MCF) 3.1.4 Term defined in ITU-T M.3100: management interface 3.1.5 Term defined in ITU-T X.700: managed object 3.1.6 Terms defined in ITU-T X.701: agent manager 3.2 Terms defined in this Recommendation This Recommendation defines the foll

25、owing terms: 3.2.1 C The adjustment in time to compensate for delivery delay. 3.2.2 S The difference in time between the arrival of the time signal at the edge of the NE and the time indicated on the local real time clock, immediately after a reset local clock request has been completed. 3.2.3 X The

26、 delivery delay of the time signal from the External Time Reference to the edge of the NE. 4 ITU-T Rec. G.7710/Y.1701 (07/2007) 3.2.4 Y The drift of the local Real Time Clock within a 24-hour interval of the External Time Reference. 3.2.5 Z The difference between the time that a prescribed event is

27、detected by the NE and the time that the NE assigns to this event. 3.2.6 local craft terminal (LCT): Used for maintenance purposes at the NE. 3.2.7 embedded communication channel (ECC): An ECC provides a logical operations channel between NEs, utilizing, e.g., a data communication channel (DCC) with

28、in SDH or a general communication channel (GCC 0-2) within OTN as its physical layer. 3.2.8 management application function (MAF): An application process that participates in system management. Each NE and operations system (OS) must support a MAF. A MAF is the origin and termination for all TMN mes

29、sages. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations: AF Atomic Function AIS Alarm Indication Signal ALM ALarM Reporting AP Access Point API Access Point Identifier AR Availability Ratio ARC Alarm Reporting Control AST Alarm Status function ASY Alarm Synchronizati

30、on function AvFb Bidirectional Availability Filter function AvFu Unidirectional Availability Filter function BBE Background Block Error BBER Background Block Error Ratio BDI Backward Defect Indication BEI Backward Error Indication BIS Bringing-Into-Service BUT Begin Unavailable Time CMISE Common Man

31、agement Information Service Element CMSN Client Management Subnetwork CP Connection Point CPL Current Problem List function CPU Central Processing Unit CSES Consecutive Severely Errored Second CTP Connection Termination Point Cur15m-x Current 15-minute Register Function (x = c, s, t for Counter, Sna

32、pshot and Tidemark) ITU-T Rec. G.7710/Y.1701 (07/2007) 5 Cur24h-x Current 24-hour Register Function (x = c, s, t for Counter, Snapshot and Tidemark) DCN Data Communication Network DEG DEGraded DEGM Degraded Monitor period DEGTHR Degraded Threshold DS Defect Second D Mediation device (Q-interface); O

33、perations system interfaces (Q-interface). The functionality required to be supported by the NE will determine the type of Q-interface to be provided. For instance, the two main varieties of NEs expected are the NEs with mediation functions (MF) and “regular“ NEs. 12 ITU-T Rec. G.7710/Y.1701 (07/200

34、7) 6.1.3 x.MSN requirements In Figure 3, a number of requirements should be noted concerning the architecture of the x.MSN: a) Multiple NEs at a single site Multiple, addressable NEs may be present at a single physical location. For example, in Figure 3, NEEand NEGmay be collocated at a single equip

35、ment site. b) NEs and their communications functions The message communication function of an NE initiates/terminates (in the sense of the lower protocol layers), routes, or otherwise processes management messages over ECCs, or other data communication network interfaces connected via an external Q-

36、interface. c) Inter-site communications The inter-site or inter-office communications link between the NEs will normally be provided by the ECCs. d) Intra-site communications Within a particular site, the NEs may communicate via an intra-site ECC or via a LAN. Figure 3 illustrates both instances of

37、this interface. NOTE A standardized LAN for communicating between collocated network elements has been proposed as an alternative to the use of an ECC. The LAN would potentially be used as a general site communications network serving all NEs. The specification of the LAN is beyond the scope of this

38、 Recommendation and is defined in ITU-T G.7712. 6.1.4 x.MSN data communication network It is intended that this Recommendation should place no restriction on the physical transport topology to support management communications. Thus it is expected that the supporting data communication network (DCN)

39、 may contain string (bus), star, ring or mesh topologies. The DCN also supports seamless connectivity with remote transport domains and NEs as specified in ITU-T Rec. G.8601/Y.1391 as well as with termination points located in NEs under control by a third party network operator as specified in ITU-T

40、 Rec. G.8601/Y.1391. See ITU-T G.7712 for the management of DCNs architectures and specifications, including the network layer protocol. Each Management Subnetwork (x.MSN) must have at least one NE which is connected to an OS (possibly via a mediation device). This NE is called a gateway network ele

41、ment (GNE) and is illustrated in Figure 3. The GNE should be able to perform an intermediate system network layer routing function for ECC messages destined for any end system in the x.MSN. Messages passing between the OS and any of the end systems in the subnetwork are routed through the GNE and, i

42、n general, other intermediate systems. NOTE This is a specific instance of the general requirement that messages passing between communicating subnetworks shall use the network layer relay. 6.1.5 Management of the DCN NEs communicate via the DCN. In order to have the DCN operate properly, a number o

43、f management functions are required. Examples are: 1) retrieval of network parameters to ensure compatible functioning, e.g., packet size, timeouts, quality of service, window size, etc.; 2) establishment of message routing between DCN nodes; 3) management of network addresses; 4) retrieval of opera

44、tional status of the DCN at a given node; 5) capability to enable/disable access to the DCN. ITU-T Rec. G.7710/Y.1701 (07/2007) 13 6.1.6 Remote log-in For remote log-in security, see requirements in ITU-T M.3016 series “Security for the management plane“ 6.1.7 Relationship between technology domains

45、 The transport network has to deal with many technology domains (i.e., connection-oriented and connectionless). When they are connected together, these domains create a client-server relationship between them. This situation leads to hybrid NEs that handle a specific technology internally and in the

46、 transport ports, but also have access ports, which are able to convert from another technology to this specific one. Figure 4 shows such a client-server relationship between two different management subnetworks. G.7710-Y.1701(07)_F04Technology A portClientmanagement Sub-networkTechnology A(CMSN A)T

47、echnology A portNE B(techn. A)NE E(techn. B)NE C(hybrid techn. A/B)NE A(techn. A)LayernetworkR(techn. B)Network element (NE) Technology B layers Technology A layersServermanagement Sub-networktechnology B(SMSN B)NE D(hybrid techn. A/B)LayernetworkR(techn. B)LayernetworkS(techn. B)LayernetworkT(techn

48、. B)LayernetworkS(techn. B)LayernetworkT(techn. B)LayernetworkY(techn. A)LayernetworkX(techn. A)Figure 4 Example of management network relationships 14 ITU-T Rec. G.7710/Y.1701 (07/2007) NEs C and D contain technology B (server) layer network entities and technology A (client) layer network entities

49、. These NEs are therefore part of more than one type of management subnetwork. The Technology A Ports in NEs C and D can be managed in one of the following ways: as an entity that is managed by the CMSN OSF; as an entity that is managed by the SMSN OSF; as a stand-alone fragment which is not managed except as an equipment fragment. This may be achieved by one or more agents within such a NE, using one or