WO2017156675A1

WO2017156675A1 - Operation administration maintenance system

Info

Publication number: WO2017156675A1
Application number: PCT/CN2016/076248
Authority: WO
Inventors: 王昊; 易粟; 范小菁; 王乐菲; 薛文倩; 松仓隆一
Original assignee: 富士通株式会社; 王昊; 易粟; 范小菁; 王乐菲; 薛文倩
Priority date: 2016-03-14
Filing date: 2016-03-14
Publication date: 2017-09-21
Also published as: CN108476149A; CN108476149B

Abstract

An operation administration maintenance system, comprising: a network element management system for managing one or more network elements of a specific type; and one or more network elements, wherein each of the network elements comprises an operation administration maintenance client and one or more network element function execution units, the operation administration maintenance client interacts with the network element management system by means of one or more interfaces, and the operation administration maintenance client controls the interaction of one or more network element function execution units with the other network elements. Thus, an EMS function can be separated, and an NE can be fully integrated with a management system, thereby making it easy to realize the standardization of a functional module and an interface, improving the reliability and the extendibility of the OAM, and satisfying the actual requirements of the OAM as the network system becomes larger.

Description

Operation management and maintenance system

Technical field

The present invention relates to the field of communications, and in particular, to an Operation Administration Maintenance (OAM) system.

Background technique

In the past few years, Ethernet has evolved from a local area network to a metropolitan area network or a wide area network. Enterprises, schools, government departments, etc. use Ethernet to connect their respective local area networks to establish a virtual office environment, campus or community. As the network scale continues to expand, network devices become more diverse, and the number of network nodes grows geometrically. The network OAM system has become the key to the growth of operators or service providers.

The network OAM system includes two plane functions: a management plane performs network management and configuration functions and provides interfaces to network administrators; a network plane performs data transmission and reception and routing functions, and is monitored by the management plane. And management.

At present, some organizations have defined standards or protocols for Ethernet OAM, such as IEEE 802.3 (for example, called 802.3ah) and IEEE 802.1 (for example, 802.1ag) defined by the International Telecommunication Union (ITU); Corresponding to the Media Access Control (MAC) layer of the Open System Interconnection (OSI) Layer 7 protocol and the Logical Link Control (LLC) layer. The 802.1ag control information may be carried by an Ethernet bearer or by a wireless local area network (802.11). The above two protocols can also be used in combination to discover, verify, test, isolate, and recover various faults in large-scale networks.

Figure 1 is a schematic diagram of a typical multi-layer network OAM deployment. As shown in Figure 1, different OAM protocols are used at different layers of the network. Each layer uses its own OAM protocol, such as customers, service providers, and operators deploy OAM tools on their respective layers to listen to the network.

As shown in Figure 1, the Multi-Protocol Label Switch (MPLS) is used to listen to the MPLS network of the carrier (such as the carrier 1 shown in Figure 1). The IEEE 802.1ag OAM is used for monitoring operations. Ethernet (for example, operator 2 shown in Figure 1). In addition, IEEE 802.1ag OAM is also deployed at the service provider layer and the client layer, while IEEE 802.3ah is used to listen to the customer equipment (CE, Customer Equipment) and the provider side (UPE, User-facing Provider Edge). Between devices Link.

Currently, in an Ethernet link layer OAM, such as defined by IEEE 802.3ah, it is possible to listen and troubleshoot a single Ethernet link, and also to test and fault isolate a single Ethernet link. The main contents defined by IEEE 802.3ah include: Discovery, Link Monitoring, Remote Failure Indication, and Remote Loopback. The main contents defined by IEEE 802.1ag include: Continuity Check, Link Trace and loopback testing.

In addition, other organizations have defined corresponding standards or protocols. For example, the Metro Ethernet Forum (MEF) proposes the OAM architecture of Carrier Ethernet.

2 is a schematic diagram of an OAM architecture of a carrier-grade Ethernet. As shown in FIG. 2, a function of a carrier-grade Ethernet network in a management plane may be divided into multiple sub-networks, for example, a network management system (NMS). An element management system (EMS) and a network element (NE, Network Element).

For a subclass of OAM, such as fault management (FM), the WiMAX Forum gives a definition of partitioning. Fault management on the EMS includes: alert notification, association and filtering; fault acknowledgment, elimination and recovery; forwarding of alerts/events to the NMS. Fault management on the NMS includes: when the device automatically detects a fault, repairs the fault or provides a temporary solution and notifies the user; provides backup management, protection policies, routine maintenance, fault notification, and fault tracking.

It should be noted that the above description of the technical background is only for the purpose of facilitating a clear and complete description of the technical solutions of the present invention, and is convenient for understanding by those skilled in the art. The above technical solutions are not considered to be well known to those skilled in the art simply because these aspects are set forth in the background section of the present invention.

Summary of the invention

However, the inventor found that IEEE 802.3ah and the like currently only involve a single network element, and there is no definition of the upper layer interface, and cannot be fully integrated with the management system; and the EMS function cannot be separated, and the support for the NMS function is also limited.

The carrier-class or carrier-class OAM architecture only gives a scheme of dividing into multiple subnets, but for network equipment, it is difficult to standardize functional modules and interfaces.

Therefore, in the trend of increasingly large network systems such as Ethernet, the architecture of the OAM system needs to be redefined.

An embodiment of the present invention provides an operation management and maintenance system, including:

a network element management system that manages one or more network elements of a particular type, including one or more management function execution units;

One or more network elements, wherein each of the network elements includes an operation management maintenance client and one or more network element function execution units, and the operation management maintenance client communicates with the network element through one or more interfaces The management system performs interaction; the operation management maintenance client controls the one or more network element function execution units to interact with other network elements.

The embodiment of the invention further provides an operation management and maintenance system, comprising:

One or more network elements, wherein each of the network elements includes a network element management system, an operation management maintenance client, and one or more network element function execution units;

The network element management system includes one or more management function execution units; the operation management maintenance client interacts with the network element management system through one or more interfaces, and the operation management maintenance client controls the One or more network element function execution units interact with other network elements.

The beneficial effects of the embodiments of the present invention are: dividing the OAM system into at least two parts of the EMS and the NE and redefining each interface, where each NE includes at least one OAM client and one or more network element function execution units. Therefore, the EMS function can be separated, the NE can be fully integrated with the management system, the standardization of the function modules and interfaces can be easily realized, the reliability and scalability of the OAM system can be improved, and the OAM can be satisfied in the case where the network system becomes larger and larger. Actual requirements.

Specific embodiments of the present invention are disclosed in detail with reference to the following description and the drawings, in which <RTIgt; It should be understood that the embodiments of the invention are not limited in scope. The embodiments of the present invention include many variations, modifications, and equivalents within the scope of the appended claims.

Features described and/or illustrated with respect to one embodiment may be used in one or more other embodiments in the same or similar manner, in combination with, or in place of, features in other embodiments. .

It should be emphasized that the term "comprising" or "comprises" or "comprising" or "comprising" or "comprising" or "comprising" or "comprises"

DRAWINGS

The elements and features described in one of the figures or an embodiment of the embodiments of the invention may be associated with one or The elements and features shown in more other figures or embodiments are combined. In the accompanying drawings, like reference numerals refer to the

1 is a schematic diagram of a typical multi-layer network OAM deployment;

2 is a schematic diagram of an OAM architecture of a carrier Ethernet;

3 is a schematic diagram of an OAM system according to an embodiment of the present invention;

4 is another schematic diagram of an OAM system according to an embodiment of the present invention;

FIG. 5 is another schematic diagram of an OAM system according to an embodiment of the present invention; FIG.

6 is another schematic diagram of an OAM system according to an embodiment of the present invention;

FIG. 7 is another schematic diagram of an OAM system according to an embodiment of the present invention.

detailed description

The foregoing and other features of the present invention will be apparent from the The specific embodiments of the present invention are disclosed in the specification and the drawings, which are illustrated in the embodiment of the invention The invention includes all modifications, variations and equivalents falling within the scope of the appended claims.

In this application, a network element can be understood as the smallest unit that can be monitored and managed in OAM. For example, it may be a client connected to a network (such as a mobile terminal, a personal computer, a printer, etc.), or may be a router, a switch, a server, or the like. In addition, a network element can be understood as one or more hardware devices, and can also be understood as one or more logical units installed on a hardware device.

In the present application, an Ethernet is taken as an example for description, that is, the present application redefines the architecture of OAM in 802.3ah. However, the present invention is not limited to Ethernet, and can be applied to other networks.

An embodiment of the present invention provides an OAM system. FIG. 3 is a schematic diagram of an OAM system according to an embodiment of the present invention. As shown in FIG. 3, the OAM system 300 may include:

EMS 301, which manages one or more network elements 302 of a particular type, including one or more management function execution units 3011;

One or more network elements 302, wherein each network element 302 includes an OAM client 3021 and one or more network element function execution units 3022; the OAM client 3021 interacts with the EMS 301 through one or more interfaces, OAM Client 3021 controls one or more network element function execution units 3022 to interact with other network elements (not shown in FIG. 3).

In this embodiment, each functional module of the EMS 301 does not directly interact with each functional module of the network element 302. Each network element 302 interacts with the EMS 301 through the OAM client 3021. In addition, the OAM client 3021 can interact with one or more network element function execution units 3022 (also referred to as other sub-layers, such as OAM sub-layers) of the network element 302 through primitives; the OAM sub-layer can be located in an open system interconnection ( OSI, Open System Interconnection) The data link layer of the reference model, between the Media Access Control (MAC) layer and the Logical Link Control (LLC) sublayer.

Thereby, the EMS function can be separated, the NE can be fully integrated with the management system, and the standardization of the function modules and interfaces can be easily realized, and the reliability and scalability of the OAM can be improved.

4 is another schematic diagram of an OAM system according to an embodiment of the present invention. As shown in FIG. 4, the OAM system 400 may include an EMS 301 and a network element 302, as described above.

As shown in FIG. 4, the OAM system 400 may further include:

An NMS 401 that manages one or more EMSs 301; interacts with the EMS 301 through one or more interfaces.

In this embodiment, for example, if the network scale is not particularly large, the architecture shown in FIG. 3 may be used, that is, the NMS may not be configured; for example, if the network scale is particularly large, the architecture shown in FIG. 4 may be used. , you can configure NMS. This not only makes it easy to standardize functional modules and interfaces, but also maintains the flexibility and scalability of the architecture. In addition, FIG. 3 and FIG. 4 show the case of centralized control of the EMS function, but the present invention is not limited thereto, and for example, the EMS function may be distributed to each NE.

FIG. 5 is another schematic diagram of an OAM system according to an embodiment of the present invention. As shown in FIG. 5, the OAM system 500 may include: an NMS 501, an EMS 502, and an NE 503. Wherein the EMS 502 is distributed on each NE 503, and the EMS 502 may include one or more management function execution units (not shown in FIG. 5); that is, each NE 503 may include an EMS 502, and each NE 503 further includes a The OAM client 5031 and one or more network element function execution units 5032.

In addition, the OAM system may not include the NMS, for example, if the network size is not particularly large.

FIG. 6 is another schematic diagram of an OAM system according to an embodiment of the present invention. As shown in FIG. 6, the OAM system 600 may include: one or more NEs 503; wherein the EMS 502 is distributed on each NE 503. That is, each NE 503 can include an EMS 502, an OAM client 5031, and one or more network element function execution units 5032;

The EMS 502 can include one or more management function execution units (not shown in Figure 6); the OAM guest The client 5031 interacts with the EMS 502 through one or more interfaces, and the OAM client 5031 controls one or more network element function execution units 5032 to interact with other network elements (not shown in FIG. 6).

In this embodiment, as shown in FIG. 3 or 6, the OAM system includes two layers: an EMS and a network element. As shown in FIG. 4 or 5, the OAM system includes three layers: an NMS, an EMS, and a network element. The present invention will be described in detail below by taking only the three-layer architecture shown in FIG. 4 as an example, but the present invention is not limited thereto.

FIG. 7 is another schematic diagram of an OAM system according to an embodiment of the present invention. As shown in FIG. 7, the OAM system 700 may include an NMS 601, an EMS 602, and an NE 603. The EMS 602 may be one or more, and each EMS 602. One or more NE 603s can be managed. For the sake of simplicity, FIG. 7 shows only one EMS 602 and one NE 603, but the invention is not limited thereto.

As shown in FIG. 7, EMS 602 can include:

A configuration unit 6021 (also referred to as a configurator) that manages configuration information of one or more network elements 603;

Aggregation unit 6022 (also referred to as aggregation), which manages alarm information of one or more network elements 603 based on preset rules;

Fault isolation unit 6023 (also referred to as failure isolation), which isolates and analyzes faults of one or more network elements 603;

A failure recovery unit 6024 (also referred to as failure recovery) that performs recovery operations on one or more network elements 603 to eliminate network failures;

A remote test management unit 6025 (also referred to as a remote test manager) that manages tests performed by one or more network elements 603.

It should be noted that the above only schematically enumerates several management function execution units (such as a configuration unit, an aggregation unit, a fault isolation unit, and the like) included in the EMS 602, but the present invention is not limited thereto, and the management function in the EMS 602 is executed. The unit may include one or more of the above units, and may also include other functional units, for example, one or more management function execution units may also be customized.

As shown in FIG. 7, the network element 603 can include:

OAM client 6031 (OAM client); each network element 603 interacts with the EMS 602 through the OAM client 6031.

The remote fault indication unit 6032 (also referred to as RFI, remote failure indication), which indicates that the network element 603 or other network element is faulty;

Link monitoring unit 6033 (also referred to as LM, link monitor), which links to the link between network elements 603 Line listening operation;

a remote test unit 6034 (also referred to as a remote test agent), which performs a test operation on the network element 603 or other network elements;

A capability discovery unit 6035 (also referred to as capability discovery) performs OAM capability discovery operations on the network element 603 or other network elements.

As shown in FIG. 7, in this embodiment, each network element interacts with the EMS through the OAM client, and in addition, each module in the EMS and the network element is redefined; thus, the logical relationship between each module in the architecture is The definition is clearer and can improve the reliability and scalability of OAM.

It should be noted that the above only schematically enumerates several network element function execution units (such as a remote fault indication unit, a link monitoring unit, a remote test unit, and the like) included in the NE 603, but the present invention is not limited thereto, and the NE is not limited thereto. The network element function execution unit in 603 may include one or more of the above units, and may also include other functional units, for example, one or more network element function execution units may also be customized.

As shown in FIG. 7, there are multiple interfaces between the NMS 601 and the EMS 602, such as interface a, interface b, interface c, interface d and interface e as shown in FIG. 7; between EMS 602 and NE 603 Multiple interfaces, such as interface f, interface g, interface i, interface k, and interface l as shown in FIG.

Further, as shown in FIG. 7, there may be an interface h between the aggregation unit 6022 of the EMS 602 and the fault isolation unit 6023, and an interface j between the fault isolation unit 6023 and the fault recovery unit 6024 of the EMS 602.

In addition, as shown in FIG. 7, an interface m is provided between the OAM client 6031 of the NE 603 and the remote fault indication unit 6032, and an interface n is provided between the OAM client 6031 of the NE 603 and the link listening unit 6033. An O interface between the OAM client 6031 and the remote test unit 6034 of the 603 has an interface p between the OAM client 6031 of the NE 603 and the capability discovery unit 6035.

As shown in FIG. 7, there may be multiple interfaces between the NE 603 and other NEs 603, such as interface q, interface r, interface s, and interface t as shown in FIG.

It should be noted that the above only schematically shows the interface between the entities, but the present invention is not limited thereto; for example, all the above interfaces may be used, or only some of the above interfaces may be used, and the above interfaces may also be used. Make appropriate changes (such as merging, deleting, modifying, etc.). In addition, other interfaces can be added.

The following describes the interaction process on each interface.

In the interface a, the configuration unit 6021 can receive the current configuration sent by the NMS 601 for requesting a certain network element. Set the information or configure the information of the adjustment information, and send the current configuration information or configuration adjustment information of the network element to the NMS 601;

For example, NMS 601 makes configuration parameter adjustments to NE 603 via EMS 602, or NMS 601 requests EMS 602 for current configuration information for NE 603; EMS 602 can send an acknowledgment message to NMS 601 to indicate a successful configuration parameter adjustment, or EMS 602 The current configuration information of the NE 603 can be sent to the NMS 601.

At the interface b, the aggregating unit 6022 can receive the message sent by the NMS 601 for requesting the alarm information of a certain network element, and send the alarm information that meets the preset rule to the NMS 601; in addition, the aggregating unit 6022 can also receive the NMS 601. Request to clear the list of alerts related to a single fault that has been resolved.

For example, NMS 601 requests EMS 602 to send an active alert list for a particular NE or a set of NEs, the request may include filtering rules such as type, severity, time, and NE ID; EMS 602 may request NMS based on the request 601 returns a list of active alarms that match the rules.

At interface c, the fault isolation unit 6023 can send the analysis result of the fault cause to the NMS 601;

For example, the EMS 602 returns to the NMS 601 the result of the current failure (which may be referred to as a root cause) analysis, which may include some information for further study by the NMS 601, or an unconfirmable analysis result.

At interface d, failure recovery unit 6024 receives a message sent by NMS 601 requesting failure recovery without a mitigation of the failure, and transmits a recovery result to NMS 601.

For example, in the event that the failure cannot be automatically recovered, the NMS 601 can request to initiate or initiate a recovery operation, and the EMS 602 can return the result of the recovery operation to the NMS 601.

At the interface e, the remote test management unit 6025 can receive the message sent by the NMS 601 for testing, and send the test result to the NMS 601;

For example, when additional information about a fault is needed, the NMS 601 can request to initiate a test operation, the EMS 602 can perform the test, and return the results of the test operation to the NMS 601.

At interface f, the configuration unit 6021 can interact with the OAM client 6031 based on a request from the NMS 601 to perform configuration management on the network element 503, for example, the interaction information can include parameters, thresholds, and the like.

For example, the EMS 602 can configure the parameters and conditions of the NE 603 based on the request of the NMS 601.

At interface g, the aggregating unit 6022 can receive the alarm information sent by the OAM client 6031 and the feature information related to the single fault;

For example, the OAM client 6031 can send a set of active alarms for the current NE and feature information about a single network failure event; the alert can be related to a certain rule, such as an alert propagation path, a particular geographic region, a particular device, or from the same source. Repeat the alert. Alarms can be divided into multiple sets, where the alarms in the same set have a high probability of being caused by the same network failure, and the related set can also contain communication characteristic information, which is considered to have a high probability Caused by the same network failure.

At interface h, aggregation unit 6022 can forward the alert information and feature information associated with a single fault to fault isolation unit 6023.

For example, the alert information and feature information can be forwarded to the fault isolation unit 6023 to look up the faulty root cause; wherein the set of such information may come from multiple network elements 603, thereby allowing network faults to be viewed from a broader perspective.

At interface i, the fault isolation unit 6023 receives the alarm information sent by the OAM client 6031 and characteristic information related to a single fault, and analyzes the cause of the fault;

For example, the OAM client 6031 can send an active alert set and feature information about a single network failure event; the alert can be related to a certain rule, such as an alert propagation path, a particular geographic region, a particular device, or a duplicate alert from the same source. Alarms can be divided into multiple sets, where the alarms in the same set have a high probability of being caused by the same network failure, and the related set can also contain communication characteristic information, which is considered to have a high probability Caused by the same network failure.

At interface j, the fault isolation unit 6023 may send a message to the fault recovery unit 6024 to initiate a recovery operation if the cause of the failure is obtained.

For example, fault isolation is the process of being able to identify and identify the cause of a network failure. Once a root cause of a network failure is found, fault isolation initiates a recovery operation.

At the interface k, the fault recovery unit 6024 can interact with the OAM client 6031 to perform a recovery operation according to the result of the fault isolation and the preset rule.

For example, the EMS 602 sends a request to the NE 603 to repair the fault based on the results of the fault isolation and the predefined rules. Once the fault is successfully recovered, the EMS 602 can send a request to the NMS 601 requesting that the active alert for the NE 603 be emptied.

At interface 1, the remote test management unit 6025 can also interact with the OAM client 6031 to perform a test operation;

For example, EMS 602 requests from remote test unit 6034 in NE 603 via OAM client 6031 To perform the test operation, the remote test unit 6034 in the NE 603 will return the test results to the EMS 602 via the OAM client 6031.

At the interface m, the remote fault indication unit 6032 can interact with the OAM client 6031 to perform a remote fault indication operation if the local fault is detected;

For example, if a local fault is detected, the remote fault indication unit 6032 will initiate an RFI operation through the OAM client 6031; in addition, fault information about other NEs may also be notified to the OAM client 6031 of the NE 603 via the remote fault indication unit 6032. .

At interface n, the link listening unit 6033 can interact with the OAM client 6031 to perform a link listening operation;

For example, the link monitoring unit 6033 can initiate a link listening operation through the OAM client 6031, and the OAM client 6031 can collect the communication characteristic information and the result of receiving the link monitoring for acquiring statistical data about the communication status.

At interface o, remote test unit 6034 can interact with OAM client 6031 to perform a test operation;

For example, the OAM client 6031 can initiate a test operation (eg, a loopback test) based on a request from the EMS 602, or can automatically initiate a test operation based on the configuration information.

At interface p, the capability discovery unit 6035 can interact with the OAM client 6031 to perform a capability discovery operation;

For example, capability discovery is the first phase of identifying remote NE OAM capabilities, and this information is provided to the OAM client 6031 to ensure that OAM operations are supported.

At the interface q, the remote fault indication unit 6032 is further configured to exchange remote fault indication information between other network elements and the OAM client 6031 of the network element 603.

For example, information about local failures can be exchanged between OAM clients 6032 of multiple network elements.

At the interface r, the link monitoring unit 6033 is further configured to exchange link monitoring information between the other network element and the OAM client 6031 of the network element 603.

For example, information about the communication link can be exchanged between OAM clients 6031 of a plurality of network elements. In addition, variables from the Management Information Base (MIB) can also be exchanged between the OAM clients 6031.

At the interface s, the remote testing unit 6034 is further configured to exchange test information between other network elements and the OAM client 6031 of the network element 603.

For example, information about the test can be exchanged between OAM clients 6032 of multiple network elements.

At the interface t, the capability discovery unit 6035 is further configured to exchange capability information between other network elements and the OAM client 6031 of the network element 603.

For example, information about capabilities can be exchanged between OAM clients 6032 of multiple network elements.

It is to be noted that FIG. 7 is a schematic diagram showing a specific embodiment of the embodiment of the present invention, but the invention is not limited thereto, for example, a part of the function execution unit or part of the interface may be used, or Define other functional execution units or interfaces.

It can be seen from the foregoing embodiment that the OAM system is at least divided into two parts, EMS and NE, and redefines each interface. The NE includes an OAM client and one or more network element function execution units. Therefore, the EMS function can be separated, the NE can be fully integrated with the management system, the standardization of the function modules and interfaces can be easily realized, the reliability and scalability of the OAM system can be improved, and the OAM can be satisfied in the case where the network system becomes larger and larger. Actual requirements.

The above apparatus and method of the present invention may be implemented by hardware or by hardware in combination with software. The present invention relates to a computer readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to cause the logic component to implement the various methods described above Or steps. The present invention also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, or the like.

One or more of the functional blocks described in the figures and/or one or more combinations of functional blocks may be implemented as a general purpose processor, digital signal processor (DSP) for performing the functions described herein. An application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof. One or more of the functional blocks described with respect to the figures and/or one or more combinations of functional blocks may also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors One or more microprocessors in conjunction with DSP communication or any other such configuration.

The present invention has been described in connection with the specific embodiments thereof, and it should be understood by those skilled in the art that A person skilled in the art can make various modifications and changes to the present invention within the scope of the present invention.

Claims

An operation management and maintenance system, comprising:

a network element management system that manages one or more network elements of a particular type, including one or more management function execution units;

One or more network elements, wherein each of the network elements includes an operation management maintenance client and one or more network element function execution units; the operation management maintenance client communicates with the network element through one or more interfaces The management system interacts, and the operation management maintenance client controls the one or more network element function execution units to interact with other network elements.
The operation management and maintenance system according to claim 1, wherein the operation management and maintenance system further comprises:

A network management system that manages one or more of the network element management systems; interacts with the network element management system via one or more interfaces.
The operation management and maintenance system according to claim 2, wherein the management function execution unit comprises:

a configuration unit that manages configuration information of the one or more network elements;

An aggregation unit that manages alarm information of the one or more network elements based on a preset rule;

a fault isolation unit that isolates and analyzes faults of the one or more network elements;

a fault recovery unit that performs a recovery operation on the one or more network elements to eliminate network faults;

A remote test management unit that manages tests performed by the one or more network elements.
The operation management and maintenance system according to claim 3, wherein said configuration unit performs one or more of the following operations:

Receiving a message sent by the network management system for requesting current configuration information or configuration adjustment information of the network element;

Sending current configuration information or configuration adjustment information of the network element to the network management system;

And interacting with the operation management and maintenance client to perform configuration management on the network element based on a request from the network management system.
The operation management and maintenance system according to claim 3, wherein said aggregation unit performs one or more of the following operations:

Receiving a message sent by the network management system for requesting alarm information of the network element;

Sending alarm information that meets the preset rule to the network management system;

Receiving alarm information sent by the operation management and maintenance client and characteristic information related to a single fault;

Transmitting the alarm information and feature information related to a single fault to the fault isolation unit;

Receiving a request from the network management system to clear a list of alarms associated with a single failure that has been resolved.
The operation management and maintenance system according to claim 3, wherein the fault isolation unit performs one or more of the following operations:

Receiving, by the aggregation unit and/or the operation management and maintenance client, the alarm information and feature information related to a single fault, and performing analysis of the fault cause;

Sending an analysis result of the cause of the failure to the network management system;

A message initiating a recovery operation is sent to the failure recovery unit if the cause of the failure is obtained.
The operation management and maintenance system according to claim 3, wherein said failure recovery unit performs one or more of the following operations:

Performing a recovery operation with the operation management and maintenance client according to the result of the fault isolation and the preset rule;

Receiving a message that the network management system sends a request for failure recovery without a failure to be mitigated;

Sending a recovery result to the network management system.
The operation management and maintenance system according to claim 3, wherein said remote test management unit performs one or more of the following operations:

Receiving a message sent by the network management system for testing;

Sending test results to the network management system;

Interact with the operation management maintenance client to perform a test operation.
The operation management and maintenance system according to claim 1, wherein the network element function execution unit comprises:

a remote fault indication unit, indicating that the network element or other network element is faulty;

a link monitoring unit that performs a listening operation on a link between network elements;

a remote testing unit that performs a test operation on the network element or other network element;

A capability discovery unit that performs operation discovery and maintenance operations on the network element or other network elements.
The operation management and maintenance system according to claim 9, wherein the remote fault indication unit performs one or more of the following operations:

In the case that a local fault is detected, interacting with the operation management and maintenance client to perform a remote fault indication operation;

The remote fault indication information is exchanged between the other network element and the operation management and maintenance client of the network element.
The operation management and maintenance system according to claim 9, wherein said link monitoring unit performs one or more of the following operations:

Interacting with the operation management and maintenance client to perform a link monitoring operation;

The exchange of link monitoring information is performed between the other network element and the operation management and maintenance client of the network element.
The operations management and maintenance system of claim 9, wherein the remote test unit performs one or more of the following operations:

Interacting with the operation management maintenance client to perform a test operation;

Exchanging test information between the other network element and the operation management and maintenance client of the network element.
The operation management and maintenance system according to claim 9, wherein the capability discovery unit performs one or more of the following operations:

Interacting with the operation management maintenance client to perform a capability discovery operation;

The exchange of capability information is performed between the other network element and the operation management and maintenance client of the network element.
An operation management and maintenance system, comprising:

One or more network elements, wherein each of the network elements includes a network element management system, an operation management maintenance client, and one or more network element function execution units;

The network element management system includes one or more management function execution units; the operation management maintenance client interacts with the network element management system through one or more interfaces, and the operation management maintenance client controls the One or more network element function execution units interact with other network elements.
The operation management and maintenance system of claim 14, wherein the operation management system further comprises:

A network management system that manages one or more of the network element management systems; interacts with the network element management system via one or more interfaces.