CN108476149A - Operation management maintainance system - Google Patents
Operation management maintainance system Download PDFInfo
- Publication number
- CN108476149A CN108476149A CN201680076734.5A CN201680076734A CN108476149A CN 108476149 A CN108476149 A CN 108476149A CN 201680076734 A CN201680076734 A CN 201680076734A CN 108476149 A CN108476149 A CN 108476149A
- Authority
- CN
- China
- Prior art keywords
- network
- operation management
- maintainance
- client
- management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Abstract
A kind of operation management maintainance system, including：Element management system manages certain types of one or more network elements；One or more network elements, wherein each network element includes an operation management maintainance client and one or more Network Element Function execution units, the operation management maintainance client is interacted by one or more interfaces with Element management system, and the one or more Network Element Function execution units of operation management maintainance client control are interacted with other network elements.It is possible thereby to which EMS functions are detached, NE can fully be integrated with management system, it is easy to accomplish the standardization of function module and interface improves the reliability and scalability of OAM, the actual requirement of OAM is met in the case where network system is more and more huger.
Description
The present invention relates to the communications field, in particular to a kind of operation management maintainance (OAM, Operation Administration Maintenance) system.
In the past few years, Ethernet (Ethernet) is developed from local area network to Metropolitan Area Network (MAN) or wide area network.Enterprise, school, government department etc. connect respective local area network using Ethernet, establish virtual working environment, campus or community etc. with this.With the continuous expansion of network size, the network equipment is more and more diversified, and the growth of geometry grade occurs in network node number, and network OA M system has become the key of operator or the growth of ISP's business.
Network OA M system includes the function of two planes: management plane (management plane) executes the functions such as network management and configuration and provides interface to network administrator；Network plane (network plane) executes the functions such as transmitting-receiving and the routing of data, is monitored by management plane and is managed.
At present, having had some tissues is that Ethernet OAM defines standard or agreement, such as IEEE 802.3 (such as being known as 802.3ah) and IEEE 802.1 (such as being known as 802.1ag) that International Telecommunication Union (ITU, International Telecommunication Union) defines；Correspond respectively to Open System Interconnection (OSI, Open System Interconnection) 7 layer protocols media access control (MAC, Media Access Control) layer and logic link control (LLC, Logic Link Control) layer.Wherein the control information of 802.1ag can also be carried by WLAN (802.11) by Ethernet bearing.Above two agreement can also be used in combination, for finding, verifying, test, be isolated, restoring various failures present in large scale network.
Fig. 1 is a schematic diagram of typical multitiered network OAM deployment, as shown in Figure 1, the different layers in network use different OAM agreements.Every layer all uses respective OAM agreement, such as client, ISP and operator to dispose OAM tool on corresponding layer to monitor network.
As shown in Figure 1, multiprotocol label switching (MPLS, Multi-Protocol Label Switch) OAM be used to monitor the MPLS network of operator (such as operator 1 shown in FIG. 1), and IEEE 802.1ag OAM be used to monitor the Ethernet of operator (such as operator 2 shown in FIG. 1).Furthermore, IEEE 802.1ag OAM is also deployed in ISP's layer and client layer, and IEEE 802.3ah be used to monitor customer equipment (CE, Customer Equipment) and between supplier edge (UPE, User-facing Provider Edge) equipment of user side
Link.
At present in the ethernet link layer OAM that such as IEEE 802.3ah is defined, monitoring and malfunction elimination (troubleshoot) can be carried out to single ethernet link, and test and Fault Isolation furthermore can be also carried out to single ethernet link.The main contents that IEEE 802.3ah is defined include: discovery (Discovery), link monitors (Link Monitoring), remote failure indicates (Remote Failure Indication) and remote loop-back (Remote loopback) etc..The main contents that IEEE 802.1ag is defined include: detection of connectivity (Continuity Check), link tracing (Link Trace) and loopback (loopback) test etc..
In addition, its hetero-organization also defines corresponding standard or agreement.Such as Metro Ethernet Forum (MEF, Metro Ethernet Forum) proposes the OAM framework of carrier ethernet.
Fig. 2 is a schematic diagram of the OAM framework of carrier ethernet, as shown in Figure 2, the Ethernet of carrier class can be divided into multiple subnets in the function of management plane, for example including Network Management System (NMS, Network Management System), Element management system (EMS, Element Management System) and network element (NE, Network Element).
It is carried out for a subclass such as fault management (FM, Fault management) function of OAM, WiMAX Forum provides a kind of Definition of Division.Fault management on EMS includes: alert notification, association and filtering；Fault recognition, elimination and recovery；Forward alarm/event to NMS.It include: to repair failure when equipment automatically detects failure or provisional solution is provided and notifies user in the fault management on NMS；Backup management, Preservation tactics, daily maintenance, failure notification and failure tracking are provided.
It should be noted that the above description of the technical background is intended merely to conveniently carry out clear, complete explanation to technical solution of the present invention, and facilitates the understanding of those skilled in the art and illustrate.It cannot be merely because these schemes be expounded in background technology part of the invention and think that above-mentioned technical proposal is known to those skilled in the art.
Summary of the invention
But inventor has found: IEEE 802.3ah etc. only relates to single network element at present, does not define to high-level interface, can not be fully integrated with management system；And EMS function can not separate, also very limited to the support of NMS function.
And the OAM framework of carrier class or carrier-class only gives the scheme for being divided into multiple subnets, but for the network equipment, it is difficult to realize the standardization of functional module and interface.
Therefore, under the increasingly huger trend of the network systems such as Ethernet, the framework to OAM system is needed to redefine.
The embodiment of the present invention provides a kind of operation management maintainance system, comprising:
Element management system manages certain types of one or more network elements, including one or more management function execution units；
One or more network elements, wherein each network element includes an operation management maintainance client and one or more Network Element Function execution units, the operation management maintainance client is interacted by one or more interfaces with the Element management system；The operation management maintainance client controls one or more of Network Element Function execution units and interacts with other network elements.
The embodiment of the present invention also provides a kind of operation management maintainance system, comprising:
One or more network elements, wherein each network element includes an Element management system, an operation management maintainance client and one or more Network Element Function execution units；
The Element management system includes one or more management function execution units；The operation management maintainance client is interacted by one or more interfaces with the Element management system, and the operation management maintainance client controls one or more of Network Element Function execution units and interacts with other network elements.
The beneficial effect of the embodiment of the present invention is: OAM system being at least divided into EMS and NE two parts from framework and redefines each interface, wherein each NE includes at least an OAM client and one or more Network Element Function execution units.It is possible thereby to which EMS function is separated, NE can sufficiently be integrated with management system, it is easy to accomplish the standardization of functional module and interface improves the reliability and scalability of OAM system, the actual requirement of OAM is met in the case where network system is more and more huger.
Referring to following description and accompanying drawings, only certain exemplary embodiments of this invention is disclosed in detail, specifying the principle of the present invention can be in a manner of adopted.It should be understood that embodiments of the present invention are not so limited in range.In the range of the spirit and terms of appended claims, embodiments of the present invention include many changes, modifications and are equal.
The feature for describing and/or showing for a kind of embodiment can be used in one or more other embodiments in a manner of same or similar, be combined with the feature in other embodiment, or the feature in substitution other embodiment.
It should be emphasized that term "comprises/comprising" refers to the presence of feature, one integral piece, step or component when using herein, but the presence or additional of one or more other features, one integral piece, step or component is not precluded.
The embodiment of the present invention elements and features described in one drawing or one embodiment can with one or
Elements and features shown in more other attached drawings or embodiment combine.In addition, in the accompanying drawings, similar label indicates corresponding component in several attached drawings, and may be used to indicate corresponding component used in more than one embodiment.
Fig. 1 is a schematic diagram of typical multitiered network OAM deployment；
Fig. 2 is a schematic diagram of the OAM framework of carrier ethernet；
Fig. 3 is a schematic diagram of the OAM system of the embodiment of the present invention；
Fig. 4 is another schematic diagram of the OAM system of the embodiment of the present invention；
Fig. 5 is another schematic diagram of the OAM system of the embodiment of the present invention；
Fig. 6 is another schematic diagram of the OAM system of the embodiment of the present invention；
Fig. 7 is another schematic diagram of the OAM system of the embodiment of the present invention.
Referring to attached drawing, by following specification, aforementioned and other feature of the invention be will be apparent.In the specification and illustrated in the drawings, specifically disclose only certain exemplary embodiments of this invention, which show some embodiments that can wherein use principle of the invention, it will be appreciated that, the present invention is not limited to described embodiments, on the contrary, the present invention includes whole modifications, modification and the equivalent fallen within the scope of the appended claims.
In this application, network element can be understood as the minimum unit that can be monitored and manage in OAM.Such as can be client connected to the network (such as mobile terminal, personal computer, printer etc.), it is also possible to router, interchanger, server etc..In addition, network element can be understood as one or more hardware devices, it is understood that for the one or more logic units being mounted on hardware device.
In this application, it is illustrated by taking Ethernet as an example, i.e., the application redefines the framework in 802.3ah about OAM.But the present invention is not limited to Ethernets, can be applicable to other networks.
The embodiment of the present invention provides a kind of OAM system.Fig. 3 is a schematic diagram of the OAM system of the embodiment of the present invention, as shown in figure 3, OAM system 300 may include:
EMS 301 manages certain types of one or more network elements 302, 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 passes through one or more interfaces and interacts with EMS 301, and OAM client 3021 controls one or more Network Element Function execution units 3022 and interacts with other network elements (being not shown in Fig. 3).
In the present embodiment, each functional module of EMS 301 does not interact directly with each functional module of network element 302, and each network element 302 is interacted by the OAM client 3021 and EMS 301.Furthermore OAM client 3021 can be interacted by one or more Network Element Function execution units 3022 (alternatively referred to as other sublayers, such as OAM sublayer) of primitive and network element 302；OAM sublayer can be located at Open System Interconnection (OSI, Open System Interconnection) reference model data link layer, in media access control (MAC, Media Access Control) between layer and logic link control (LLC, Logic Link Control) sublayer.
Thus, it is possible to which EMS function is separated, NE can sufficiently be integrated with management system, it is easy to accomplish the reliability and scalability of OAM can be improved in the standardization of functional module and interface.
Fig. 4 is another schematic diagram of the OAM system of the embodiment of the present invention, as shown in figure 4, OAM system 400 may include: EMS 301 and network element 302, as described above.
As shown in figure 4, OAM system 400 can also include:
NMS 401 manages one or more EMS 301；It is interacted by one or more interfaces with EMS301.
In the present embodiment, in the case where such as network size is not king-sized situation, framework shown in Fig. 3 can be used, it can not configure NMS；In the king-sized situation of such as network size, framework shown in Fig. 4 can be used, it can configuration NMS.Thus it is not only easy to realize the standardization of functional module and interface, and the flexibility and scalability of framework can be kept.In addition, Fig. 3 and Fig. 4 show the case where EMS function centralized control, however, the present invention is not limited thereto, such as EMS function can also be distributed in each NE.
Fig. 5 is another schematic diagram of the OAM system of the embodiment of the present invention, as shown in figure 5, OAM system 500 may include: NMS 501, EMS 502 and NE 503.Wherein EMS 502 is distributed on each NE 503, and EMS 502 may include one or more management function execution units (being not shown in Fig. 5)；That is, each NE 503 may include EMS 502, furthermore each NE 503 further includes an OAM client 5031 and one or more Network Element Function execution units 5032.
In addition, OAM system can not also include NMS in the case where such as network size is not king-sized situation.
Fig. 6 is another schematic diagram of the OAM system of the embodiment of the present invention, as shown in fig. 6, OAM system 600 may include: one or more NE 503；Wherein EMS 502 is distributed on each NE 503.That is, each NE 503 may include 502, OAM clients 5031 of an EMS and one or more Network Element Function execution units 5032；
EMS 502 may include one or more management function execution units (being not shown in Fig. 6)；OAM visitor
Family end 5031 passes through one or more interfaces and interacts with EMS 502, and OAM client 5031 controls one or more Network Element Function execution units 5032 and interacts with other network elements (being not shown in Fig. 6).
In the present embodiment, can be as shown in Fig. 3 or 6, OAM system includes EMS and two layers of network element；Can also as shown in fig. 4 or 5, OAM system includes NMS, EMS and three layers of network element.Only the present invention is described in detail by taking three-tier architecture shown in Fig. 4 as an example below, however, the present invention is not limited thereto.
Fig. 7 is another schematic diagram of the OAM system of the embodiment of the present invention, as shown in fig. 7, OAM system 700 may include NMS 601, EMS 602 and NE 603；Wherein, EMS 602 can be one or more, and each EMS 602 can manage one or more NE 603.For the sake of simplicity, Fig. 7 only diagrammatically illustrates an EMS 602 and a NE 603, however, the present invention is not limited thereto.
As shown in fig. 7, EMS 602 may include:
Configuration unit 6021 (alternatively referred to as configurator) manages the configuration information of one or more network elements 603；
Polymerized unit 6022 (alternatively referred to as aggregation) manages the warning information of one or more network elements 603 based on preset rules；
Fault Isolation unit 6023 (alternatively referred to as failure isolation) carries out every the analysis of variance failure of one or more network elements 603；
Fault recovery unit 6024 (alternatively referred to as failure recovery) carries out recovery operation to one or more network elements 603 to eliminate network failure；
Remote testing administrative unit 6025 (alternatively referred to as remote test manager) manages the test that one or more network elements 603 are carried out.
It is worth noting that, several management function execution units (such as configuration unit, polymerized unit, Fault Isolation unit etc.) that EMS 602 includes only schematically are listed above, however, the present invention is not limited thereto, management function execution unit in EMS 602 may include wherein one or more of said units, it can also include other functional units, such as can be with customized one or more management function execution units.
As shown in fig. 7, network element 603 may include:
OAM client 6031 (OAM client)；Each network element 603 is interacted by the OAM client 6031 and EMS 602.
Remote failure indicating unit 6032 (alternatively referred to as RFI, remote failure indication), indicates the network element 603 or the failure of other network elements；
Link monitoring unit 6033 (alternatively referred to as LM, link monitor), to the link between network element 603 into
Row snoop-operations；
Remote testing unit 6034 (alternatively referred to as remote test agent) carries out test operation to the network element 603 or other network elements；
Ability discovery unit 6035 (alternatively referred to as capability discovery), the ability discovery for carrying out OAM to the network element 603 or other network elements operate.
As shown in fig. 7, in the present embodiment, each network element is interacted by OAM client with EMS, and furthermore the modules in EMS and network element are redefined；What thus the logical relation in framework between modules was defined is clearer, and the reliability and scalability of OAM can be improved.
It is worth noting that, several Network Element Function execution units that NE 603 includes (such as remote failure indicating unit, link monitoring unit, remote testing unit are only schematically listed above, etc.), however, the present invention is not limited thereto, Network Element Function execution unit in NE 603 may include wherein one or more of said units, it can also include other functional units, such as can be with customized one or more Network Element Function execution units.
As shown in fig. 7, having multiple interfaces, such as interface a as shown in Figure 7, interface b, interface c, interface d and interface e between NMS 601 and EMS 602；There is multiple interfaces, such as interface f as shown in Figure 7, interface g, interface i, interface k and interface l between EMS 602 and NE 603.
In addition, there is interface j between the Fault Isolation unit 6023 and fault recovery unit 6024 of EMS 602 as shown in fig. 7, can have interface h between the polymerized unit 6022 and Fault Isolation unit 6023 of EMS 602.
Furthermore, as shown in Figure 7, there is interface m between the OAM client 6031 and remote failure indicating unit 6032 of NE 603, there is interface n between the OAM client 6031 and link monitoring unit 6033 of NE 603, there is interface o between the OAM client 6031 and remote testing unit 6034 of NE 603, there is interface p between the OAM client 6031 and ability discovery unit 6035 of NE 603.
As shown in fig. 7, also can have multiple interfaces, such as interface q as shown in Figure 7, interface r, interface s, interface t between NE 603 and other NE 603.
It is worth noting that, schematically showing only the interface between each entity, however, the present invention is not limited thereto above；Above-mentioned whole interfaces can be used for example, the part of interface in above-mentioned interface can also be used only, above-mentioned interface can also suitably be changed (such as merge, delete, modify etc.).Other interfaces can additionally be increased.
It is schematically illustrated below for the interactive process on each interface.
In interface a, configuration unit 6021 can receive NMS 601 transmission for request a certain network element currently match
The message of confidence breath or configuration adjustment information, and send the current configuration information of the network element to NMS 601 or configure adjustment information；
For example, NMS 601 makes configuration parameter adjustment to NE 603 by EMS 602 or NMS 601 requests to EMS 602 current configuration information of NE 603；EMS 602 can send confirmation message to NMS 601 to indicate that a successful configuration parameter adjustment or EMS 602 can send the current configuration information of NE 603 to NMS 601.
In interface b, polymerized unit 6022 can receive the message of the warning information for requesting a certain network element of the transmission of NMS 601, and the warning information for meeting preset rules is sent to NMS 601；In addition, polymerized unit 6022 can also receive the request of NMS 601, alert list related with single failure has been solved is removed.
For example, NMS 601 requests EMS 602 to send Active Alerts list for a certain specific NE or one group of NE set, which may include the information such as filtering rule, such as type, severity, time and NE ID；EMS 602 can return to legal Active Alerts list to NMS 601 according to the request.
In interface c, the analysis result of failure cause can be sent to NMS 601 by Fault Isolation unit 6023；
For example, the reason of EMS 602 returns to current failure to NMS 601 (can be described as root cause) analysis is as a result, the analysis result may include certain information for allowing NMS 601 further to study, it is also possible to the analysis result that can not be confirmed.
In interface d, fault recovery unit 6024 receives the message that the request that NMS 601 is sent in the case where failure does not mitigate carries out fault recovery, and sends restoration result to NMS 601.
For example, NMS 601 can request to initiate or start recovery operation, and EMS 602 can return to the result of recovery operation to NMS 601 in the case where failure cannot be restored automatically.
In interface e, remote testing administrative unit 6025 can receive the message that the request of the transmission of NMS 601 is tested, and send test result to NMS 601；
For example, NMS 601 can request to initiate test operation, and EMS 602 can execute the test, and return to the result of test operation to NMS 601 when needing the additional information about failure.
In interface f, configuration unit 6021 can be interacted based on the request from NMS 601 with OAM client 6031 the network element 503 to be managed for configuration, such as interactive information may include parameter, threshold value etc..
For example, EMS 602 can be based on the parameter and condition of the request configuration NE 603 of NMS 601.
In interface g, polymerized unit 6022 can receive the warning information and characteristic information relevant to single failure of the transmission of OAM client 6031；
For example, OAM client 6031 can send one group of Active Alerts set of current NE and the characteristic information about single network event of failure；Alarm can be related to certain rule, such as alarm propagation path, specific geographical area, particular device or the repeat alarms from same source.Alarm can be divided into multiple set, it is as caused by identical network failure that wherein the alarm in the same set, which has very high probability, relevant set also may include communication feature information, and it is as caused by identical network failure that these communication feature information, which are considered having very high probability,.
In interface h, polymerized unit 6022 can forward the warning information and characteristic information relevant to single failure to Fault Isolation unit 6023.
For example, these warning informations and characteristic information can be transmitted to Fault Isolation unit 6023 to search the root cause of failure；Wherein the set of these information may be from multiple network elements 603, it is possible thereby to pay close attention to network failure from broader angle.
In interface i, Fault Isolation unit 6023 receives the warning information and characteristic information relevant to single failure that OAM client 6031 is sent, and carries out the analysis of failure cause；
For example, OAM client 6031 can send Active Alerts set and the characteristic information about single network event of failure；Alarm can be related to certain rule, such as alarm propagation path, specific geographical area, particular device or the repeat alarms from same source.Alarm can be divided into multiple set, it is as caused by identical network failure that wherein the alarm in the same set, which has very high probability, relevant set also may include communication feature information, and it is as caused by identical network failure that these communication feature information, which are considered having very high probability,.
In interface j, Fault Isolation unit 6023 can send the message for initiating recovery operation in the case where obtaining failure cause to fault recovery unit 6024.
For example, Fault Isolation is to can determine and identify the process for the reason of leading to network failure, once the root cause of network failure is found, Fault Isolation will initiate recovery operation.
In interface k, fault recovery unit 6024 can be interacted according to the result and preset rules of Fault Isolation with OAM client 6031 to carry out recovery operation；
For example, result and predetermined rule of the EMS 602 according to Fault Isolation, send request to NE 603 to repair failure, once failure is successfully recovered, EMS 602 can send to NMS 601 and request, it is desirable that empty the Active Alerts in relation to the NE 603.
In interface l, remote testing administrative unit 6025 can also be interacted with OAM client 6031 to carry out test operation；
For example, EMS 602 is requested by remote testing unit 6034 of the OAM client 6031 into NE 603
Test operation is carried out, the remote testing unit 6034 in NE 603 will return to test result to EMS 602 by OAM client 6031.
In interface m, remote failure indicating unit 6032 can be interacted to carry out remote failure instruction operation in the case where this earth fault is detected with OAM client 6031；
For example, remote failure indicating unit 6032 will initiate RFI operation by OAM client 6031 if this earth fault is detected；In addition, the fault message about other NE can also be notified by remote failure indicating unit 6032 to the OAM client 6031 of the NE 603.
In interface n, link monitoring unit 6033 can be interacted with OAM client 6031 to carry out link snoop-operations；
For example, link monitoring unit 6033 can initiate link snoop-operations by OAM client 6031, OAM client 6031 can collect that communication feature information and receives link are monitored as a result, being used to obtain the statistical data in relation to communication conditions.
In interface o, remote testing unit 6034 can be interacted with OAM client 6031 to carry out test operation；
For example, OAM client 6031 can initiate test operation (such as loopback is tested) according to the request of EMS 602, or test operation can also automatically be initiated according to configuration information.
In interface p, ability discovery unit 6035 can be interacted with OAM client 6031 to carry out ability discovery operation；
For example, ability discovery is the first stage for identifying long-range NE OAM ability, this information is provided to OAM client 6031 to ensure that OAM operation is supported.
In interface q, remote failure indicating unit 6032 is also used to carry out exchanging for remote failure instruction information between OAM client 6031 of other network elements with the network element 603.
For example, the information about this earth fault can be exchanged between the OAM client 6032 of multiple network elements.
In interface r, link monitoring unit 6033 is also used to carry out exchanging for link monitoring information between OAM client 6031 of other network elements with the network element 603.
For example, the information about communication link can be exchanged between the OAM client 6031 of multiple network elements.In addition, the variable from local management information library (MIB, Management Information Base) can also be exchanged between OAM client 6031.
In interface s, remote testing unit 6034 is also used to carry out exchanging for test information between OAM client 6031 of other network elements with the network element 603.
For example, the information about test can be exchanged between the OAM client 6032 of multiple network elements.
In interface t, ability discovery unit 6035 is also used to carry out exchanging for ability information between OAM client 6031 of other network elements with the network element 603.
For example, the information about ability can be exchanged between the OAM client 6032 of multiple network elements.
It is worth noting that, Fig. 7 only diagrammatically illustrates a kind of specific implementation form of the embodiment of the present invention by way of example, however, the present invention is not limited thereto, partial function execution unit therein, which can be used for example, perhaps part of interface or can also define other function execution units or interface.
As can be seen from the above embodiments, OAM system is at least divided into EMS and NE two parts from framework and redefines each interface, wherein NE includes an OAM client and one or more Network Element Function execution units.It is possible thereby to which EMS function is separated, NE can sufficiently be integrated with management system, it is easy to accomplish the standardization of functional module and interface improves the reliability and scalability of OAM system, the actual requirement of OAM is met in the case where network system is more and more huger.
The device and method more than present invention can be by hardware realization, can also be by combination of hardware software realization.The present invention relates to such computer-readable programs, when the program is performed by logical block, the logical block can be made to realize devices described above or component parts, or the logical block is made to realize various method or steps described above.The invention further relates to the storage mediums for storing procedure above, such as hard disk, disk, CD, DVD, flash memory.
For one or more combinations of one or more of function box described in attached drawing and/or function box, it can be implemented as general processor for executing function described herein, digital signal processor (DSP), specific integrated circuit (ASIC), field programmable gate array (FPGA) either other programmable logic device, discrete gate or transistor logic, discrete hardware components or it is any appropriately combined.One or more combinations of one or more of function box for attached drawing description and/or function box, it is also implemented as calculating the combination of equipment, for example, the combination of DSP and microprocessor, multi-microprocessor, the one or more microprocessors or any other this configuration combined with DSP communication.
Combining specific embodiment above, invention has been described, it will be appreciated by those skilled in the art that these descriptions are all exemplary, it is not limiting the scope of the invention.Those skilled in the art can make various variants and modifications to the present invention with spirit according to the present invention and principle, these variants and modifications are also within the scope of the invention.
Claims (15)
- A kind of operation management maintainance system, comprising:Element management system manages certain types of one or more network elements, including one or more management function execution units；One or more network elements, wherein each network element includes an operation management maintainance client and one or more Network Element Function execution units；The operation management maintainance client is interacted by one or more interfaces with the Element management system, and the operation management maintainance client controls one or more of Network Element Function execution units and interacts with other network elements.
- Operation management maintainance system according to claim 1, wherein the operation management maintainance system further include:Network Management System, the one or more Element management systems of management；It is interacted by one or more interfaces and the Element management system.
- Operation management maintainance system according to claim 2, wherein the management function execution unit includes:Configuration unit manages the configuration information of one or more of network elements；Polymerized unit manages the warning information of one or more of network elements based on preset rules；Fault Isolation unit carries out every the analysis of variance failure of one or more of network elements；Fault recovery unit carries out recovery operation to one or more of network elements to eliminate network failure；Remote testing administrative unit manages the test that one or more of network elements are carried out.
- Operation management maintainance system according to claim 3, wherein the configuration unit executes following one or more operations:Receive the message of the Network Management System current configuration information for requesting the network element sent or configuration adjustment information；The current configuration information or configuration adjustment information of the network element are sent to the Network Management System；It is interacted based on the request from the Network Management System with the operation management maintainance client the network element to be managed for configuration.
- Operation management maintainance system according to claim 3, wherein the polymerized unit executes following one or more operations:Receive the message for the warning information for requesting the network element that the Network Management System is sent；The warning information for meeting the preset rules is sent to the Network Management System；Receive warning information and characteristic information relevant to single failure that the operation management maintainance client is sent；To warning information described in the Fault Isolation unit forwards and characteristic information relevant to single failure；The request of the Network Management System is received, alert list related with single failure has been solved is removed.
- Operation management maintainance system according to claim 3, wherein the Fault Isolation unit executes following one or more operations:The warning information and characteristic information relevant to single failure of the polymerized unit and/or operation management maintainance client transmission are received, and carries out the analysis of failure cause；The analysis result of failure cause is sent to the Network Management System；The message for initiating recovery operation is sent to the fault recovery unit in the case where obtaining failure cause.
- Operation management maintainance system according to claim 3, wherein the fault recovery unit executes following one or more operations:According to the result and preset rules of Fault Isolation, interact with the operation management maintainance client to carry out recovery operation；Receive the message that the request that the Network Management System is sent in the case where failure does not mitigate carries out fault recovery；Restoration result is sent to the Network Management System.
- Operation management maintainance system according to claim 3, wherein the remote testing administrative unit executes following one or more operations:Receive the message that the request that the Network Management System is sent is tested；Test result is sent to the Network Management System；It interacts with the operation management maintainance client to carry out test operation.
- Operation management maintainance system according to claim 1, wherein the Network Element Function execution unit includes:Remote failure indicating unit indicates the network element or the failure of other network elements；Link monitoring unit carries out snoop-operations to the link between network element；Remote testing unit carries out test operation to the network element or other network elements；Ability discovery unit, the ability discovery for carrying out operation management maintainance to the network element or other network elements operate.
- Operation management maintainance system according to claim 9, wherein the remote failure indicating unit executes following one or more operations:In the case where this earth fault is detected, interacted with the operation management maintainance client to carry out remote failure instruction operation；Exchanging for remote failure instruction information is carried out between other described network elements and the operation management maintainance client of the network element.
- Operation management maintainance system according to claim 9, wherein the link monitoring unit executes following one or more operations:It interacts with the operation management maintainance client to carry out link snoop-operations；Exchanging for link monitoring information is carried out between other described network elements and the operation management maintainance client of the network element.
- Operation management maintainance system according to claim 9, wherein the remote testing unit executes following one or more operations:It interacts with the operation management maintainance client to carry out test operation；Exchanging for test information is carried out between other described network elements and the operation management maintainance client of the network element.
- Operation management maintainance system according to claim 9, wherein the ability discovery unit executes following one or more operations:It interacts with the operation management maintainance client to carry out ability discovery operation；Exchanging for ability information is carried out between other described network elements and the operation management maintainance client of the network element.
- A kind of operation management maintainance system, comprising:One or more network elements, wherein each network element includes an Element management system, an operation management maintainance client and one or more Network Element Function execution units；The Element management system includes one or more management function execution units；The operation management maintainance client is interacted by one or more interfaces with the Element management system, and the operation management maintainance client controls one or more of Network Element Function execution units and interacts with other network elements.
- Operation management maintainance system according to claim 14, wherein the operation management maintainance system further include:Network Management System, the one or more Element management systems of management；It is interacted by one or more interfaces and the Element management system.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2016/076248 WO2017156675A1 (en) | 2016-03-14 | 2016-03-14 | Operation administration maintenance system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108476149A true CN108476149A (en) | 2018-08-31 |
| CN108476149B CN108476149B (en) | 2020-12-15 |
Family
ID=59851451
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201680076734.5A Active CN108476149B (en) | 2016-03-14 | 2016-03-14 | Operation management maintenance system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108476149B (en) |
| WO (1) | WO2017156675A1 (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101013973A (en) * | 2007-02-09 | 2007-08-08 | 华为技术有限公司 | Network element state detecting method and network management equipment |
| CN101350735A (en) * | 2007-07-20 | 2009-01-21 | 中兴通讯股份有限公司 | Method for synchronization of alarm |
| CN101729282A (en) * | 2008-10-30 | 2010-06-09 | 中兴通讯股份有限公司 | Processing method and device for single-board alarming |
| CN103248400A (en) * | 2012-02-13 | 2013-08-14 | 索尼公司 | Appliance management apparatus and appliance management method |
| US20140342721A1 (en) * | 2008-04-16 | 2014-11-20 | Nokia Solutions And Networks Oy | Managing a network element |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7546361B2 (en) * | 2003-10-10 | 2009-06-09 | Nortel Networks Limited | Method and network for delivering management software for a network element |
| CN101924649B (en) * | 2010-08-03 | 2015-04-01 | 中兴通讯股份有限公司 | Remote management method and system for optical network unit (ONU) in passive optical network (PON) system |
| CN105049245B (en) * | 2015-07-02 | 2018-12-25 | 深圳市西迪特科技有限公司 | The Element management system of EPON |
-
2016
- 2016-03-14 WO PCT/CN2016/076248 patent/WO2017156675A1/en active Application Filing
- 2016-03-14 CN CN201680076734.5A patent/CN108476149B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101013973A (en) * | 2007-02-09 | 2007-08-08 | 华为技术有限公司 | Network element state detecting method and network management equipment |
| CN101350735A (en) * | 2007-07-20 | 2009-01-21 | 中兴通讯股份有限公司 | Method for synchronization of alarm |
| US20140342721A1 (en) * | 2008-04-16 | 2014-11-20 | Nokia Solutions And Networks Oy | Managing a network element |
| CN101729282A (en) * | 2008-10-30 | 2010-06-09 | 中兴通讯股份有限公司 | Processing method and device for single-board alarming |
| CN103248400A (en) * | 2012-02-13 | 2013-08-14 | 索尼公司 | Appliance management apparatus and appliance management method |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017156675A1 (en) | 2017-09-21 |
| CN108476149B (en) | 2020-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10733037B2 (en) | STAB: smart triaging assistant bot for intelligent troubleshooting | |
| US7587633B2 (en) | Fault tolerant routing in a network routing system based on a passive replication approach | |
| EP0909056B1 (en) | Network management event correlation in environments containing inoperative network elements | |
| US8775589B2 (en) | Distributed network management system and method | |
| US8370466B2 (en) | Method and system for providing operator guidance in network and systems management | |
| AU720079B2 (en) | Method and apparatus for integrated network management and systems management in communications networks | |
| WO2016119436A1 (en) | Alarm processing method and device, and controller | |
| US20020059417A1 (en) | Status polling failover of devices in a distributed network management hierarchy | |
| US20060230309A1 (en) | System for remote fault management in a wireless network | |
| CN112291075B (en) | Network fault positioning method and device, computer equipment and storage medium | |
| US20110141914A1 (en) | Systems and Methods for Providing Ethernet Service Circuit Management | |
| EP3203684B1 (en) | Method, apparatus and system for network operations, administration and maintenance | |
| WO2015026809A1 (en) | Network management layer - configuration management | |
| EP3069474B1 (en) | Correlation of event reports | |
| US10547524B2 (en) | Diagnostic transparency for on-premise SaaS platforms | |
| Varga et al. | Integration of service-level monitoring with fault management for end-to-end multi-provider ethernet services | |
| CN108476149A (en) | Operation management maintainance system | |
| Ellsworth et al. | A non-proprietary network operations platform for openroadm environment | |
| Yu et al. | A practical scheme for MPLS fault monitoring and alarm correlation in backbone networks | |
| Vieira et al. | THANOS: Teleprotection holistic application for ONOS controller | |
| CN112583623B (en) | Filtering information configuration method and system | |
| Hao et al. | Fault management for networks with link state routing protocols | |
| KR100608917B1 (en) | Method for managing fault information of distributed forwarding architecture router | |
| KR100275530B1 (en) | Method for managing the state of atm switch by telecommunicatons management network | |
| Zhu | Reliability Management Framework for Softwarized Networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |