CN102075368A - Method, device and system for diagnosing service failure - Google Patents
Method, device and system for diagnosing service failure Download PDFInfo
- Publication number
- CN102075368A CN102075368A CN 201110042572 CN201110042572A CN102075368A CN 102075368 A CN102075368 A CN 102075368A CN 201110042572 CN201110042572 CN 201110042572 CN 201110042572 A CN201110042572 A CN 201110042572A CN 102075368 A CN102075368 A CN 102075368A
- Authority
- CN
- China
- Prior art keywords
- diagnosis
- diagnostic
- knowledge base
- fault
- result information
- 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.)
- Pending
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method, a device and a system for diagnosing service failure. The method comprises the following steps of: acquiring service information to be diagnosed, and initializing a diagnostic task case according to the service information to be diagnosed and executing the diagnostic task case to obtain diagnostic result information. The diagnostic task case is established automatically according to service to be diagnosed, so compared with the scheme of searching similar cases in a case library in the prior art, the method has pertinence, the positioning of service failure is more accurate, and the correctness of diagnosing the service failure can be improved.
Description
Technical field
The present invention relates to communication technical field, be specifically related to a kind of traffic failure diagnostic method, device and system.
Background technology
Be accompanied by the growth of telecommunication service, traffic failure also highlights day by day, and the failure diagnosis and the very first time reconditioning work of fault business become the problem that operator pays close attention to, and also is the critical function that network management system is paid close attention to.The intellectuality of failure diagnosis is the target that the fault management is pursued, and also is the professional high reliability during complicated telecommunications is used, the inevitable requirement of high survivability.But, caused the traffic failure diagnosis to become the difficult point problem of present webmaster in building owing to the reason that causes traffic failure is varied and unpredictable etc.
Traffic failure navigation system and method based on example, referring to the traffic failure that the past was successfully solved and the mode of solution records in the case library as an example, when running into new problem, in case library, seek similar example, utilize the analogism method to obtain the approximate reparation answer of new problem; The pairing approximation repair mode is verified modification again, makes it to be fit to new problem; If necessary, this problem is recorded case library as an examples of many successful.Case library mainly is to safeguard by the forgetting curve theory, and promptly long-term no example will be deleted.
The flow process of existing traffic failure diagnostic method specifically can be as follows:
Step 1, the network person of inspecting or terminal use find traffic failure, to webmaster reporting service fault message.
Fault message receiver module in step 2, the webmaster receives this traffic failure information, and according to predefined Rule Extraction or organize the needed fault relevant information of whole system, and initialization fault answer authentication module.
Step 3, fault message receiver module call case library according to traffic failure information, to obtain the approximate fault answer of this fault.
Step 4, fault message receiver module will be given fault answer authentication module from the approximate answer information that case library obtains and verify repair process.
Step 5, fault answer authentication module obtain the fault answer of this fault by the method for analogism.
Step 6, fault answer authentication module are according to the answer reconditioning work, if repair successfully, then execution in step 7, if repairing failure, then execution in step 8.
Step 7, report successful result, and as required, this examples of many successful is injected case library, withdraw from the traffic failure navigation system.
Step 8, report failure result withdraw from the traffic failure navigation system.
In research and practice process to prior art, the present inventor finds, owing to the reason that causes traffic failure generally speaking all can more complicated, and exist a large amount of presentations the same, and root is because of different situations, so diagnose the situation that occurs judging by accident of tending to according to existing scheme, causes correctly reconditioning work fault, and, adopt this method also can't solve for the traffic failure that does not have similar example in the case library.
Summary of the invention
The embodiment of the invention provides a kind of traffic failure diagnostic method, device and system, can improve the accuracy of traffic failure diagnosis.
A kind of traffic failure diagnostic method comprises:
Obtain business information to be diagnosed;
Set up the diagnostic task example according to business information described to be diagnosed;
Carry out described diagnostic task example, obtain diagnostic result information;
Described diagnostic result information is transparent to client.
A kind of traffic failure diagnosis server comprises:
Acquiring unit is used to obtain business information to be diagnosed;
Set up the unit, be used for setting up the diagnostic task example according to business information described to be diagnosed;
Performance element is used to carry out described diagnostic task example, obtains diagnostic result information;
Transmitting element is used for described diagnostic result information is transparent to client.
A kind of traffic failure diagnostic system comprises any traffic failure diagnosis server that the client and the embodiment of the invention provide;
Client is used for sending and waits to diagnose business information to the traffic failure diagnosis server, and receives the diagnostic result information that the traffic failure diagnosis server returns.
The embodiment of the invention adopts obtains business information to be diagnosed, then according to waiting to diagnose business information to set up and carrying out the diagnostic task example, to obtain diagnostic result information; Because the diagnostic task example is set up automatically according to waiting to diagnose business, so with respect to prior art by for the scheme of seeking similar example in the case library, have more specific aim, more accurate for the location of traffic failure, can improve the traffic failure diagnostic accuracy.
Description of drawings
In order to be illustrated more clearly in the technical scheme in the embodiment of the invention, the accompanying drawing of required use is done to introduce simply in will describing embodiment below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those skilled in the art, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the flow chart of the traffic failure diagnostic method that provides of the embodiment of the invention;
Fig. 2 is a schematic diagram of the traffic failure diagnostic system that provides of the embodiment of the invention;
Fig. 3 is another flow chart of the traffic failure diagnostic method that provides of the embodiment of the invention;
Fig. 4 is a schematic diagram of the fault diagnosis knowledge base that provides of the embodiment of the invention;
Fig. 5 a is the structural representation of the traffic failure diagnosis server that provides of the embodiment of the invention;
Fig. 5 b is another structural representation of the traffic failure diagnosis server that provides of the embodiment of the invention;
Fig. 6 is the structural representation of the traffic failure diagnostic system that provides of the embodiment of the invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those skilled in the art belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
The embodiment of the invention provides a kind of traffic failure diagnostic method, device and system.Below be elaborated respectively.
Embodiment one,
Present embodiment will be described from the angle of professional fault diagnosis server, for example, this traffic failure diagnosis server can comprise failure diagnosis engine and diagnostic task example, and the diagnostic task example element can comprise modules such as failure diagnosis kernel, fault diagnosis knowledge base and data collection agent module.
A kind of traffic failure diagnostic method comprises: obtain business information to be diagnosed, set up the diagnostic task example according to this business information to be diagnosed, carry out this diagnostic task example, obtain diagnostic result information, diagnostic result information is transparent to client.Referring to Fig. 1, idiographic flow can be as follows:
101, obtain business information to be diagnosed; Wherein, this business information to be diagnosed refers to the related data of waiting to diagnose business object, and can be brought in by the client provides.
For example, when needs carried out the traffic failure diagnosis, client can be initiated traffic failure diagnosis request according to current topological malfunction, and then the failure diagnosis engine is after receiving this traffic failure diagnosis request, obtain business information to be diagnosed from client, execution in step 102 then.
102, set up the diagnostic task example according to business information to be diagnosed;
Wherein, the traffic failure diagnosis server allows the user to diagnose many business at one time, we all are called a diagnostic task example diagnosis of every business, this diagnostic task example can exist with the form of thread, also can exist with the form of process, that is, a diagnostic task example specifically can be a diagnosis example thread, also can be a diagnosis example process.On carrying out, have a diagnosis algorithm in the diagnostic task example at least, so-called diagnosis algorithm refers to the step of diagnostic process, and a diagnosis algorithm can be at one or several diagnosis items.
On structure, a diagnostic task example can comprise modules such as failure diagnosis kernel, fault diagnosis knowledge base, data collection agent module; Then this moment, step 102 specifically can be as follows:
Wait to diagnose business information initialization diagnostic task example by failure diagnosis engine basis, to obtain the identification information of diagnostic task example, then the failure diagnosis engine to diagnose professional carry out resource registering and resource mutual exclusion management after, the identification information of this diagnostic task example is sent to client, to set up the communication between client and the diagnostic task example.
103, carry out this diagnostic task example, obtain diagnostic result information;
For example, can pass through failure diagnosis kernel loads fault diagnosis knowledge base in buffer area or internal memory, and carry out fault diagnosis knowledge base, obtain diagnostic result information.
Wherein, this diagnostic result information is described by diagnosis algorithm, comprises total diagnostic result at least, and optionally, this diagnostic result information can also comprise: this step is carried out information such as details, this step diagnostic result and/or reparation suggestion.Certainly, this diagnostic result information can also comprise the data message in other diagnostic procedures of user's interest, in this no longer class act.Generally speaking, need general data structure of definition to describe diagnostic result information.
Wherein, fault diagnosis knowledge base can be realized by script, this fault diagnosis knowledge base comprises a script at least, wherein, this script is corresponding with diagnosis algorithm, such as, can be corresponding one by one, promptly the corresponding script of diagnosis algorithm then " is carried out fault diagnosis knowledge base by the failure diagnosis kernel " and specifically can be comprised the steps:
A1, determine the pairing script of current diagnosis algorithm by the failure diagnosis kernel;
A2, send to carry out the pairing script of current diagnosis algorithm by the failure diagnosis kernel instruction to fault diagnosis knowledge base, so that fault diagnosis knowledge base is carried out the pairing script of this current diagnosis algorithm;
Wherein, fault diagnosis knowledge base is carried out the pairing script of current diagnosis algorithm and specifically can be adopted following any one mode to realize:
1) not stratified: not to diagnosing business to carry out layering; Then step " fault diagnosis knowledge base is carried out the pairing script of current diagnosis algorithm " is specifically as follows:
Fault diagnosis knowledge base obtains related datas such as alarm data required in the diagnostic procedure, performance data and/or service management data to the data collection agent module, do logic by the pairing script of current diagnosis algorithm according to the related datas such as alarm data, performance data and/or service management data that get access to then and carry out, obtain diagnostic result information.For example, specifically can be as follows:
Carry out alert analysis according to the alarm data that gets access to,, perhaps determine the network element or the link of fault to determine the traffic failure reason; And/or,
According to the performance change situation of the performance data analysis monitored object that gets access to, when there is reduction in the performance of finding this monitored object, determine the reduction reason, perhaps determine the network element or the link of fault; And/or,
Professional connective according to the service management Data Detection that gets access to, to determine the network element or the link of fault; And/or,
According to the service management Data Detection service attribute that gets access to, to determine the traffic failure reason; And/or,
Carry out oam (OAM, OperationAdministration and Maintenance) according to the service management data that get access to and detect, to determine the traffic failure reason.
2) layering: the diagnosis business is divided into operation layer, virtual circuit (PW, Pseudo Wire) layer, passage (Tunnel) layer and link layer; Then step " fault diagnosis knowledge base is carried out the pairing script of current diagnosis algorithm " is specifically as follows:
Fault diagnosis knowledge base obtains related datas such as alarm data required in the diagnostic procedure, performance data and/or service management data to the data collection agent module;
Fault diagnosis knowledge base respectively to diagnosing professional operation layer, PW layer, channel layer and link layer to diagnose, obtains the diagnostic result information of each layer according to the related datas such as alarm data, performance data and/or service management data that get access to;
Fault diagnosis knowledge base gathers the diagnostic result information of each layer, to obtain the pairing diagnostic result information of current diagnosis algorithm.
A3, receive the pairing diagnostic result information of preceding diagnosis algorithm that fault diagnosis knowledge base returns by the failure diagnosis kernel.
Wherein, can also carry the identification information of the pairing script of next diagnosis algorithm in this diagnostic result information, so that the failure diagnosis kernel is determined the pairing script of next diagnosis algorithm according to the identification information of the pairing script of this next diagnosis algorithm.
104, diagnostic result information is transparent to client;
Such as, can the diagnostic result information that obtain be transparent to client by the failure diagnosis kernel, so that the client executing subsequent operation.
For example, after client receives this diagnostic result information, can the real-time exhibition diagnostic result, and refresh topological malfunction, i.e. one of the every diagnosis of traffic failure diagnosis server, client all can show the diagnostic result of this diagnosis algorithm.
Further, for Free up Memory, if client has been accepted diagnostic result, then the traffic failure diagnosis server can also be deleted corresponding diagnostic task example.Promptly after being transparent to client, diagnostic result can also comprise:
If diagnostic result is accepted, the diagnostic task example of then deletion correspondence.
As from the foregoing, present embodiment adopts and obtains business information to be diagnosed, then according to waiting to diagnose business information to set up and carrying out the diagnostic task example, to obtain diagnostic result information; Because the diagnostic task example is set up automatically according to waiting to diagnose business, so with respect to prior art by for the scheme of seeking similar example in the case library, have more specific aim, more accurate for the location of traffic failure, can improve the traffic failure diagnostic accuracy.
Embodiment two,
According to embodiment one described method, below will be described in further detail for example.
This traffic failure diagnostic system can comprise traffic failure diagnosis server and client.During concrete enforcement, the traffic failure diagnosis server can comprise failure diagnosis engine and diagnostic task example; Wherein, the diagnostic task example can comprise modules such as failure diagnosis kernel, fault diagnosis knowledge base and data collection agent module, optionally, can also comprise the fault restoration module.Referring to Fig. 2, specific as follows:
(1) client
Refer to traffic failure diagnostic system client, (PC PersonalComputer) or equipment such as portable terminal, for convenience, in embodiments of the present invention, all abbreviates client as to be specifically as follows personal computer.This client is mainly as the inlet of this traffic failure diagnostic system, it provides Diagnostics Interfaces, be used for according to the diagnosis of the business datum initiation that provides this business, receive the diagnostic result information that the traffic failure diagnosis server returns, according to diagnostic result information updating topology malfunction, and in diagnostic procedure the real-time exhibition diagnostic result.
(2) traffic failure diagnosis server
This traffic failure diagnosis server can comprise failure diagnosis engine, failure diagnosis kernel, fault diagnosis knowledge base and data collection agent module; Optionally, can also comprise the fault restoration module.Specific as follows:
(1) failure diagnosis engine;
The failure diagnosis engine, bridge as client and failure diagnosis kernel, be mainly used in the life cycle of managing failures diagnostic task example, promptly be used for managing failures diagnostic task example establishment (being initialization), destroy (i.e. deletion), withdraw from unusually, and in initialization procedure, the relevant information of the business that needs are diagnosed passes to the diagnostic task example on the one hand, on the other hand, the relevant information of diagnostic task example is passed to client, to set up the communication between client and the failure diagnosis task instances.
It should be noted that if the diagnostic task example is to exist with the process form, the failure diagnosis engine is notified the progress information of this diagnostic task example of client so; If the diagnostic task example exists with the thread form, then the failure diagnosis engine is notified the thread information of this diagnostic task example of client.
In addition, the failure diagnosis engine also is used to provide resource registering, and realizes resource mutual exclusion management.
So-called resource registering and resource mutual exclusion management refer to: need the diagnostic result crossfire problem that prevents that resource contention from causing in the diagnostic procedure, used by two different business such as professional A and professional B such as same passage (Tunnel), in the diagnosis passage, just need do mutual exclusion so and handle, be used as the passage diagnostic result of professional B with the passage diagnostic result that prevents professional A mistakenly the resource of this passage.
(2) failure diagnosis kernel;
The failure diagnosis kernel is born the function of diagnosing controller in the whole service fault diagnosis system, it is mainly used in the record fault diagnosis knowledge base, issue the instruction (i.e. execution command) of carrying out the fault diagnosis knowledge base script and give fault diagnosis knowledge base, so that fault diagnosis knowledge base is carried out script, receive the diagnostic result information that fault diagnosis knowledge base returns, can carry the identification information of the pairing script of next diagnosis algorithm in this diagnostic result information, like this, the failure diagnosis kernel just can be determined the pairing script of next diagnosis algorithm according to the identification information of this script, by that analogy, thus make the failure diagnosis kernel each script can be together in series according to diagnostic process.
In addition, the failure diagnosis kernel also is used for being responsible for diagnostic result information is passed through client.
(3) fault diagnosis knowledge base;
Fault diagnosis knowledge base is mainly used in the professional diagnostic process of definition, is the nucleus module of this system.Wherein, diagnostic process can be according to presetting strategy setting.
Have a plurality of steps in diagnostic process, generally, each step is finished a diagnosis item or several diagnosis item that is associated, such as, " ATM business configuration data consistent check " is exactly a diagnosis item.Fault diagnosis knowledge base is generally realized by script, mainly finish the task that current step need be carried out in each script, the return information of script comprises the identification information of this task executions result and the corresponding script of next step: wherein, task executions result is called diagnostic result information in embodiments of the present invention.
The expansion and the maintenance that are provided with for convenience and make things convenient for fault diagnosis knowledge base, step and script can be man-to-man relations, and like this, newly-increased if desired diagnosis algorithm only needs to add the pairing script of this diagnosis algorithm in knowledge base; Equally, delete certain diagnosis algorithm if desired, the script that then only needs to delete this step correspondence is just passable.
(4) data collection agent module;
The data collection agent module mainly is responsible for the collection of desired data information in the diagnostic procedure.Diagnostic knowledge base obtains data to the data collection agent module as required, as performance data, alarm data, service attribute data or the like.Data collection agent module and perimeter systems alternately with image data, and are done analyzing and processing to the data that collect according to the requirement of diagnostic knowledge base such as external module, offer diagnostic knowledge base then.
(5) fault restoration module;
The fault restoration module is mainly used in finishes fault restoration.For example, after client had been accepted diagnostic result, client can trigger fault restoration, and then this moment, the fault restoration module can and be repaired regular reconditioning work fault according to diagnostic result.
Below will be to for example this traffic failure diagnostic method being described, as shown in Figure 3, idiographic flow can be as follows:
201, client selected treat the diagnosis business after, send the failure diagnosis request to the failure diagnosis engine, and send business information to be diagnosed to the failure diagnosis engine.
For example, this diagnosis business information can be carried at and send to the failure diagnosis engine in the failure diagnosis request.
202, the failure diagnosis engine is behind the request message that receives client initiation diagnosis, according to waiting to diagnose business information initialization diagnostic task example; That is, wait to diagnose business information initialization failure diagnosis kernel, diagnostic knowledge base and data collection agent module according to what obtain, and a business information to be diagnosed is sent to the diagnostic task example from client.
203, after task instances to be diagnosed was finished initialization, the failure diagnosis engine obtained the identification information of diagnostic task example, such as the sign of diagnostic task example (ID, IDentity), process or thread information.
204, the failure diagnosis engine is registered the resource of the business of current diagnosis and the mutual exclusion management as passage (Tunnel) and link etc., reports by mistake to prevent diagnostic result, and is convenient to discharge resource after the diagnosis end.
205, resource is registered and mutual exclusion management after, the failure diagnosis engine is notified to client with the identification information of diagnostic task example, client just obtain behind the identification information of diagnostic task example can be directly and the diagnostic task example carried out communication.
After the communication of having set up between client and the diagnostic task example, the failure diagnosis kernel starts diagnosis automatically, and promptly execution in step 206～212.
206, the failure diagnosis kernel is loaded into diagnostic knowledge base in buffer area or the internal memory, diagnoses business information scanning fault diagnosis knowledge base inlet according to waiting, and begins to carry out diagnostic knowledge base.
Wherein, fault diagnosis knowledge base can be realized by script, for convenience, in the present embodiment, is that example describes with the corresponding script of a diagnosis algorithm all; That is, in this step (step 206), the failure diagnosis kernel sends the instruction of the pairing script of the current diagnosis algorithm of execution to fault diagnosis knowledge base, and fault diagnosis knowledge base is carried out the pairing script of this current diagnosis algorithm after receiving this instruction.
207, fault diagnosis knowledge base is in the process of carrying out the pairing script of current diagnosis algorithm, obtains to the data collection agent module and finishes the needed data of this diagnosis algorithm, such as alarm data, performance data and/or service management data or the like.
208, data collection agent module and external module carry out alternately, gather desired data.Wherein, external module can be modules such as network element, alarm management module, performance management module or service management module.
209, the data collection agent module is carried out analyzing and processing according to the demand of fault diagnosis knowledge base to the data that collect, and the data after will handling then offer fault diagnosis knowledge base.
210, fault diagnosis knowledge base is done logic by the pairing script of current diagnosis algorithm to these data that get access to and is carried out after obtaining needed data, obtains execution result, is called diagnostic result information in embodiments of the present invention.
This diagnostic result information comprises total diagnostic result at least, and optionally, this diagnostic result information can also comprise: this step is carried out information such as details, this step diagnostic result and/or reparation suggestion.Certainly, this diagnostic result information can also comprise the data message in other diagnostic procedures of user's interest.
211, diagnostic knowledge base sends to the failure diagnosis kernel with diagnostic result information, wherein, carry the identification information of the pairing script of next diagnosis algorithm in the diagnostic result information, like this, the failure diagnosis kernel just can be determined the pairing script of next diagnosis algorithm according to this identification information, thereby each diagnosis algorithm is together in series according to diagnostic process.
212, the failure diagnosis kernel is transparent to client with diagnostic result information.
Client can show this diagnostic result information, and refresh topological malfunction after receiving this diagnostic result information, promptly, in every one step of execution, client all can show the diagnostic result information of this diagnosis algorithm, to refresh current displaying contents.
After executing current diagnosis algorithm, the failure diagnosis kernel continues the next diagnosis algorithm of diagnosis, by that analogy; The execution in step 206～212 that promptly circulates is carried out up to all diagnosis algorithms and to be finished.
If 213 diagnostic results are accepted by client, then whether client can further be selected fault to be repaired, if do not need to repair, then flow process finishes; Repair if desired, then client can send the fault restoration request to the fault restoration module, the fault restoration module is after receiving this fault restoration request, obtain diagnostic result information, such as can from client or failure diagnosis kernel, obtaining diagnostic result information, according to diagnostic result information the fault business is repaired then.
In addition, after diagnostic result information was transparent to client, if diagnostic result is accepted by client, then this traffic failure diagnosis server can also be deleted this diagnostic task example, so that resource is discharged.
As from the foregoing, present embodiment adopts and obtains business information to be diagnosed, then according to waiting to diagnose business information to set up and carrying out the diagnostic task example, to obtain diagnostic result information; Because the diagnostic task example is set up automatically according to waiting to diagnose business, so with respect to prior art by for the scheme of seeking similar example in the case library, have more specific aim, more accurate for the location of traffic failure, can improve the traffic failure diagnostic accuracy.And, in the present embodiment and since the script of fault diagnosis knowledge base be with diagnosis algorithm one to one, so, help the expansion and the maintenance of fault diagnosis knowledge base, such as, newly-increased if desired diagnosis algorithm only needs to add the pairing script of this diagnosis algorithm in knowledge base; In like manner, delete certain diagnosis algorithm if desired, the script that then only needs to delete this step correspondence is just passable.
Embodiment three,
According to embodiment two described methods, wherein, script in the fault diagnosis knowledge base can adopt multiple mode to formulate, such as, can formulate different scripts according to the difference of the content of diagnostic task, also can carry out layering, formulate different scripts at different layers then diagnosing business, or the like.
In the present embodiment, will be that example describes to formulate different scripts according to the difference of the content of diagnostic task.
Fault diagnosis knowledge base can be divided into a plurality of diagnostic knowledges unit, such as, fault diagnosis knowledge base can comprise alert analysis blocks of knowledge, performance evaluation blocks of knowledge, detection of connectivity blocks of knowledge, professional blocks of knowledge and the OAM detection blocks of knowledge of detecting, and is as follows:
(1) alert analysis blocks of knowledge;
The alert analysis blocks of knowledge, be mainly used in and obtain warning information such as service alarm, chain circuit alarming, physical entity alarm from the data collection agent module, alarm correlation analysis and alarm root cause analysis are carried out in alarm, gather the traffic failure reason according to analysis result then, perhaps determine out of order network element or link.
(2) performance evaluation blocks of knowledge:
The performance evaluation blocks of knowledge, be mainly used in and collect current performance statistics and historical performance statistics, wrap data etc. such as the business transmitting-receiving, according to the operation conditions in the Performance Analysis monitored object a period of time of presetting, draw the performance change situation, there are reduction or other problems if find performance, then determine the reduction reason, perhaps determine out of order network element or link.
(3) detection of connectivity blocks of knowledge;
The detection of connectivity blocks of knowledge, be mainly used in by searching the number order in path, detect professional connectedness such as orders such as Ping or TraceRout, can also wait the scope of dwindling fault detect as Pathping (also being a kind of order of searching the path) or display command (show) by other orders that network element provides, and then determine specific fault network element and link.
(4) the professional blocks of knowledge that detects;
The professional blocks of knowledge that detects, be mainly used in service related data is checked, such as to the correctness of business configuration or consistency, configuration correctness, address resolution protocol (ARP, Address ResolutionProtocol) study situation, network element single-board chip whether unusual packet loss or the like check.
(5) OAM detects blocks of knowledge:
Search failure cause by the OAM means.For example, can determine failure cause by OAM detection meanss such as the section of setting end attribute, continuity check (CC, Continuity Check) states of activation.
Fault diagnosis knowledge base is when carrying out the script of current diagnosis algorithm, carry out above-mentioned each diagnostic knowledge unit respectively, obtain the diagnostic result information of each unit, diagnostic result information to these unit gathers then, obtain final diagnostic result information, such as traffic failure reason and reparation suggestion or the like.
Above-mentioned each unit is Data transmission mutually in the process of implementation, its detected fault network element and faulty link information can be passed to other unit such as the detection of connectivity blocks of knowledge, so that other unit weighs points detect these network elements or links.
Other steps of present embodiment are with embodiment two.Present embodiment can be realized the beneficial effect that embodiment two is same.
Embodiment four,
Different with embodiment three is, in the present embodiment, will be with to diagnosing business to carry out layering, formulating different scripts at different layers then be that example describes.
In the present embodiment, fault diagnosis knowledge base adopts layer mode, be about to treat that the diagnosis business is divided into operation layer, PW layer, channel layer, link layer (comprising logic link layer and physical link layer), successively diagnose then, the diagnostic result with each layer gathers to draw the traffic failure reason at last.Referring to Fig. 4, specifically can be as follows:
(1) operation layer diagnostic knowledge unit;
Operation layer diagnostic knowledge unit is mainly used in diagnosing professional operation layer to diagnose, and concrete diagnosis content comprises alert analysis, performance evaluation, detection of connectivity, the detection of professional association attributes and/or OAM detection etc.
(2) PW layer diagnosis blocks of knowledge;
PW layer diagnosis blocks of knowledge is mainly used in diagnosing professional PW layer to diagnose, and concrete diagnosis content comprises alert analysis, performance evaluation, detection of connectivity, the detection of PW association attributes and/or OAM detection etc.
(3) channel layer diagnostic knowledge unit;
Channel layer diagnostic knowledge unit is mainly used in diagnosing professional channel layer to diagnose, and concrete diagnosis content comprises alert analysis, performance evaluation, detection of connectivity and/or the detection of passage association attributes etc.
(4) link layer diagnostic knowledge unit;
Link layer diagnostic knowledge unit is mainly used in diagnosing professional link layer to diagnose, and concrete diagnosis content comprises alert analysis, performance evaluation, detection of connectivity and/or the detection of link association attributes etc.
Fault diagnosis knowledge base is when carrying out the script of current diagnosis algorithm, carry out above-mentioned each diagnostic knowledge unit respectively, obtain the diagnostic result information of each unit, diagnostic result information to these unit gathers then, obtain final diagnostic result information, such as traffic failure reason and reparation suggestion or the like.
In the present embodiment, except the definition of fault diagnosis knowledge base and embodiment three were different, other step was all identical with embodiment two and three, does not repeat them here.Present embodiment can be realized the beneficial effect that embodiment two is same.
As from the foregoing, present embodiment (being embodiment four) is though the dimension of two kinds of fault diagnosis knowledge bases definition that provided with embodiment three is different, and they respectively have advantage.First kind of fault diagnosis knowledge base (fault diagnosis knowledge base that is provided such as embodiment three) is that the data dimension according to business association defines, it can the data at same type be analyzed in same blocks of knowledge, and this mode can find the fault point fast; And second kind of fault diagnosis knowledge base is (such as present embodiment, be the fault diagnosis knowledge base that embodiment four is provided) define according to professional level, from the link layer to the operation layer, successively investigate fault, this mode fault location operation realizes simple relatively.
It should be noted that, present embodiment goes for different application scenarioss respectively with embodiment three, such as some business being arranged according to the easier division of layer mode, some business then is inconvenient to carry out the layering division, or the like, so, according to different application scenarioss, can select suitable execution mode for use, so that more quickly and effectively business is diagnosed, and obtain diagnostic result, make follow-up can more effectively the reparation to traffic failure.
In addition, it should be noted that also that the traffic failure diagnostic system that the embodiment of the invention provided specifically can be applied to network management system, and other OSS (OSS, Operating Support System).In addition, this traffic failure diagnostic system can also not depend on any system, and directly as independently system's existence, at this moment, the diagnosis desired data can give in providing by the mode of data importing, does not repeat them here.
Embodiment five,
In order to implement above method better, the embodiment of the invention also correspondingly provides a kind of traffic failure diagnosis server, and shown in Fig. 5 a, this traffic failure diagnosis server comprises acquiring unit 501, sets up unit 502, performance element 503 and transmitting element 504;
Acquiring unit 501 is used to obtain business information to be diagnosed;
Set up unit 502, be used for setting up the diagnostic task example according to the business information to be diagnosed that acquiring unit 501 gets access to;
Transmitting element 504, the diagnostic result information that is used for performance element 503 is obtained is transparent to client.
Wherein, referring to Fig. 5 b, performance element 503 can comprise loading subelement 5031 and carry out subelement 5032;
Set up unit 502, be used for setting up failure diagnosis kernel, fault diagnosis knowledge base and data collection agent module according to business information to be diagnosed;
Carry out subelement 5032, be used for carrying out fault diagnosis knowledge base, obtain diagnostic result information by the failure diagnosis kernel.
Wherein, fault diagnosis knowledge base can be realized by script, this fault diagnosis knowledge base comprises a script at least, wherein, this script is corresponding with diagnosis algorithm, such as, can be corresponding one by one, promptly the corresponding script of diagnosis algorithm is then carried out subelement 5032 and can be comprised definite sub level unit, issues the sub level unit and receive the sub level unit;
Determine the sub level unit, be used for determining the pairing script of current diagnosis algorithm by the failure diagnosis kernel;
Issue the sub level unit, be used for sending the instruction of the pairing script of the current diagnosis algorithm of execution to fault diagnosis knowledge base, so that fault diagnosis knowledge base is carried out the pairing script of current diagnosis algorithm by the failure diagnosis kernel;
Receive the sub level unit, be used for receiving the diagnostic result information that fault diagnosis knowledge base returns, wherein, can carry the identification information of the pairing script of next diagnosis algorithm in this diagnostic result information by the failure diagnosis kernel.
Wherein, fault diagnosis knowledge base can adopt multiple mode to carry out the pairing script of current diagnosis algorithm, for example, and specifically can be as follows:
Carry out subelement 5032 and can also comprise information gathering sub level unit and script executing sub level unit;
Information gathering sub level unit is used for obtaining the required alarm data of diagnostic procedure, performance data and/or service management data by fault diagnosis knowledge base to the data collection agent module;
Script executing sub level unit is used to utilize the pairing script of current diagnosis algorithm that the alarm data, performance data and/or the service management data that get access to are done logic and carries out, and obtains diagnostic result information.
Wherein, script executing sub level unit specifically is used for carrying out alert analysis according to described alarm data, to determine the traffic failure reason, perhaps determines the network element or the link of fault; And/or, according to the performance change situation of described performance data analysis monitored object, when there is reduction in the performance of finding described monitored object, determine the reduction reason, perhaps determine the network element or the link of fault; And/or, professional connective according to the service management Data Detection, to determine the network element or the link of fault; And/or, according to service management Data Detection service attribute, to determine the traffic failure reason; And/or, carry out OAM according to the service management data and detect, to determine the traffic failure reason.
Optionally, also can carry out layering, after respectively each layer being diagnosed by fault diagnosis knowledge base, the diagnostic result information of each layer be gathered to obtain total diagnostic result information diagnostic task.I.e. this moment, carry out subelement 5032 and can also comprise information gathering sub level unit, diagnosis sub level unit and gather the sub level unit;
Information gathering sub level unit is used for obtaining the required alarm data of diagnostic procedure, performance data and/or service management data by fault diagnosis knowledge base to the data collection agent module;
Diagnosis sub level unit is used for by fault diagnosis knowledge base, utilizes described alarm data, performance data and/or service management data respectively to diagnosing professional operation layer, PW layer, channel layer and link layer to diagnose, and obtains the diagnostic result information of each layer;
Gather the sub level unit, be used for gathering, to obtain diagnostic result information by the diagnostic result information of fault diagnosis knowledge base with each layer.
Referring to Fig. 5 b, set up unit 502 and can comprise that identification information obtains subelement 5021 and handles subelement 5022;
Identification information obtains subelement 5021, is used for by the failure diagnosis engine according to waiting to diagnose business information initialization diagnostic task example, to obtain the identification information of diagnostic task example;
Then this moment, performance element 503 also is used to carry out the diagnostic task example after identification information obtains subelement 5021 initialization, obtains diagnostic result information; Specifically can be as follows:
Carry out subelement 5032, be used for obtaining diagnostic result information by carrying out the failure diagnosis kernel execution fault diagnosis knowledge base after identification information obtains subelement 5021 initialization.
In addition, shown in Fig. 5 b, this traffic failure diagnosis server can also comprise fault restoration unit 505;
Shown in Fig. 5 b, this traffic failure diagnosis server can also comprise delete cells 506;
During concrete enforcement, more than each unit can be used as independent entity and realize, also can carry out combination in any, realize as same entity or plurality of entity then.For example, acquiring unit 501 and delete cells 506 can be used as the failure diagnosis engine implemented in two, set up unit 502, performance element 503 and transmitting element 504 can be used as the diagnostic task example of implementing in two, be failure diagnosis kernel, fault diagnosis knowledge base and data collection agent module, fault restoration unit 505 can be used as the fault restoration module of implementing in two, or the like.
More than the concrete enforcement of each unit can not repeat them here referring to front embodiment.
This traffic failure Diagnosis Service implement body can be applied to network management system, and other OSS.In addition, this traffic failure diagnosis server can also not depend on any system, and directly as independently system's existence, at this moment, the diagnosis desired data can give in providing by the mode of data importing, does not repeat them here.
As from the foregoing, the acquiring unit 501 of the traffic failure diagnosis server of present embodiment can obtain business information to be diagnosed, then by setting up unit 502 and performance element 503 according to waiting to diagnose business information to set up and carrying out the diagnostic task example, to obtain diagnostic result information; Because the diagnostic task example is set up automatically according to waiting to diagnose business, so with respect to prior art by for the scheme of seeking similar example in the case library, have more specific aim, more accurate for the location of traffic failure, can improve the traffic failure diagnostic accuracy.And, in the present embodiment and since the script of fault diagnosis knowledge base be with diagnosis algorithm one to one, so, help the expansion and the maintenance of fault diagnosis knowledge base, such as, newly-increased if desired diagnosis algorithm only needs to add the pairing script of this diagnosis algorithm in knowledge base; In like manner, delete certain diagnosis algorithm if desired, the script that then only needs to delete this step correspondence is just passable.In addition, the fault diagnosis knowledge base in this traffic failure diagnosis can also have the various definitions mode, realizes comparatively flexible.
Embodiment six,
A kind of traffic failure diagnostic system comprises any traffic failure diagnosis server that the client and the embodiment of the invention provide; For example, referring to Fig. 6, this traffic failure diagnostic system can comprise traffic failure diagnosis server 601 and client 602;
Traffic failure diagnosis server 601 is used to obtain business information to be diagnosed, and sets up the diagnostic task example according to business information to be diagnosed, and carries out the diagnostic task example, obtains diagnostic result information, and diagnostic result information is transparent to client 602;
Wherein, the diagnostic task example comprises: failure diagnosis kernel, fault diagnosis knowledge base and data collection agent module, then:
Traffic failure diagnosis server 601 specifically is used for by failure diagnosis kernel loads fault diagnosis knowledge base to buffer area or internal memory, carries out fault diagnosis knowledge base by the failure diagnosis kernel, obtains diagnostic result information.
Wherein, fault diagnosis knowledge base can be realized that this fault diagnosis knowledge base comprises a script at least by script, and wherein, script is corresponding with diagnosis algorithm, then:
Traffic failure diagnosis server 601, specifically be used for determining the pairing script of current diagnosis algorithm by the failure diagnosis kernel, send the instruction of the pairing script of the current diagnosis algorithm of execution to fault diagnosis knowledge base by the failure diagnosis kernel, so that fault diagnosis knowledge base is carried out the pairing script of this current diagnosis algorithm, receive the diagnostic result information that fault diagnosis knowledge base returns by the failure diagnosis kernel, wherein, can carry the identification information of the pairing script of next diagnosis algorithm in the diagnostic result information.
Traffic failure diagnosis server 601, specifically be used for obtaining the required alarm data of diagnostic procedure, performance data and/or service management data to the data collection agent module by fault diagnosis knowledge base, do logic by the pairing script of current diagnosis algorithm according to described alarm data, performance data and/or service management data and carry out, obtain diagnostic result information.Specifically can not repeat them here referring to front embodiment.
Perhaps, can also carry out layering to diagnostic task, promptly, diagnostic task is divided into operation layer, PW layer, channel layer and link layer, after respectively each layer of diagnostic task being diagnosed by fault diagnosis knowledge base then, the diagnostic result information of each layer is gathered, obtain total diagnostic result information, that is:
Traffic failure diagnosis server 601, specifically be used for obtaining the required alarm data of diagnostic procedure, performance data and/or service management data to the data collection agent module by fault diagnosis knowledge base, respectively operation layer, PW layer, channel layer and the link layer of diagnosing business are diagnosed according to alarm data, performance data and/or service management data by fault diagnosis knowledge base, obtain the diagnostic result information of each layer, gather by the diagnostic result information of fault diagnosis knowledge base, to obtain the pairing diagnostic result information of current diagnosis algorithm each layer.
This traffic failure diagnosis server 601, specifically be used for by the failure diagnosis engine according to waiting to diagnose business information initialization diagnostic task example, to obtain the identification information of diagnostic task example, then by the failure diagnosis engine to diagnose professional carry out resource registering and resource mutual exclusion management after, the identification information of diagnostic task example is sent to client 602, to set up the communication between client 602 and the diagnostic task example.
Optionally, this traffic failure diagnosis server 601 also is used for obtaining diagnostic result information when client 602 triggers the reparation fault, according to diagnostic result information the fault business is repaired then.
Optionally, this traffic failure diagnosis server 601 also is used for then deleting the diagnostic task example if diagnostic result is accepted.
Wherein, client 602 is specifically as follows equipment such as personal computer or portable terminal, and this traffic failure diagnostic system specifically can be applied to network management system, and other OSS (OSS, OperatingSupport System).In addition, traffic failure diagnosis server 602 in this traffic failure diagnostic system or this traffic failure diagnostic system can also not depend on any system, and directly as independently system's existence, at this moment, the diagnosis desired data can give in providing by the mode of data importing, does not repeat them here.
More than the concrete enforcement of each equipment can not repeat them here referring to front embodiment.
Below will carry out schematic illustration to the concrete execution flow process of this traffic failure diagnostic system, as follows:
Step 1, client 602 selected treat the diagnosis business after, the failure diagnosis engine in traffic failure diagnosis server 601 sends the failure diagnosis request, and sends business information to be diagnosed to this failure diagnosis engine.
For example, this diagnosis business information can be carried at and send to the failure diagnosis engine in the failure diagnosis request.
Failure diagnosis engine in step 2, the traffic failure diagnosis server 601 is behind the request message that receives client 602 initiation diagnosis, according to waiting to diagnose business information initialization diagnostic task example; Promptly, diagnose the diagnosis of business information initialization traffic failure kernel, diagnostic knowledge base and data collection agent module (failure diagnosis kernel, diagnostic knowledge base and data collection agent module all belong to fault diagnosis server 601) according to waiting of obtaining from client 602, and business information to be diagnosed is sent to diagnostic task example in the traffic failure diagnosis server 601.
After step 3, task instances to be diagnosed were finished initialization, the failure diagnosis engine in the fault diagnosis server 601 obtained the identification information of diagnostic task example, such as the sign of diagnostic task example (ID, IDentity), process or thread information.
Failure diagnosis engine in step 4, the fault diagnosis server 601 is registered the resource of the business of current diagnosis and the mutual exclusion management as passage (Tunnel) and link etc., reports by mistake to prevent diagnostic result, and is convenient to discharge resource after the diagnosis end.
Failure diagnosis engine in step 5, the fault diagnosis server 601 resource is registered and mutual exclusion management after, the identification information of diagnostic task example is notified to client 602, client 602 just obtain behind the identification information of diagnostic task example can be directly and the diagnostic task example carried out communication.
After the communication of having set up between client 602 and the diagnostic task example, the failure diagnosis kernel in the fault diagnosis server 601 starts diagnosis automatically, i.e. execution in step 6～step 12.
Failure diagnosis kernel in step 6, the fault diagnosis server 601 is loaded into diagnostic knowledge base in buffer area or the internal memory, diagnoses business information scanning fault diagnosis knowledge base inlet according to waiting, and begins to carry out diagnostic knowledge base.
Wherein, fault diagnosis knowledge base can be realized by script, for convenience, in the present embodiment, is that example describes with the corresponding script of a diagnosis algorithm all; That is, (in the step 6), the failure diagnosis kernel sends the instruction of the pairing script of the current diagnosis algorithm of execution to fault diagnosis knowledge base, and fault diagnosis knowledge base is carried out the pairing script of this current diagnosis algorithm after receiving this instruction in this step.
Fault diagnosis knowledge base in step 7, the fault diagnosis server 601 is in the process of carrying out the pairing script of current diagnosis algorithm, obtain to the data collection agent module and to finish the needed data of this diagnosis algorithm, such as alarm data, performance data and/or service management data or the like.
Step 8, data collection agent module and external module carry out alternately, gather desired data.Wherein, external module can be modules such as network element, alarm management module, performance management module or service management module.
Step 9, data collection agent module are carried out analyzing and processing according to the demand of fault diagnosis knowledge base to the data that collect, and the data after will handling then offer fault diagnosis knowledge base.
Fault diagnosis knowledge base in step 10, the fault diagnosis server 601 is after obtaining needed data, by the pairing script of current diagnosis algorithm these data that get access to being done logic carries out, obtain execution result, be called diagnostic result information in embodiments of the present invention.
This diagnostic result information comprises total diagnostic result at least, and optionally, this diagnostic result information can also comprise: this step is carried out information such as details, this step diagnostic result and/or reparation suggestion.Certainly, this diagnostic result information can also comprise the data message in other diagnostic procedures of user's interest.
Diagnostic knowledge base in step 11, the fault diagnosis server 601 sends to failure diagnosis kernel in the fault diagnosis server 601 with diagnostic result information, wherein, carry the identification information of the pairing script of next diagnosis algorithm in the diagnostic result information, like this, the failure diagnosis kernel just can be determined the pairing script of next diagnosis algorithm according to this identification information, thereby each diagnosis algorithm is together in series according to diagnostic process.
Failure diagnosis kernel in step 12, the fault diagnosis server 601 is transparent to client 602 with diagnostic result information.
After executing current diagnosis algorithm, the failure diagnosis kernel continues the next diagnosis algorithm of diagnosis, by that analogy; The execution in step that promptly circulates 6～step 12 is carried out end up to all diagnosis algorithms.
If step 13 diagnostic result is accepted by client 602, then whether client 602 can further be selected fault to be repaired, if do not need to repair, then flow process finishes; Repair if desired, then client 602 can send the fault restoration request to the fault restoration module in the fault diagnosis server 601, the fault restoration module is after receiving this fault restoration request, obtain diagnostic result information, such as can from client 602 or failure diagnosis kernel, obtaining diagnostic result information, according to diagnostic result information the fault business is repaired then.
Wherein, fault diagnosis knowledge base can have the various definitions mode, specifically can not repeat them here referring to front embodiment.
As from the foregoing, traffic failure diagnosis server 601 in the traffic failure diagnostic system that present embodiment provided adopts and obtains business information to be diagnosed from client 602, then according to waiting to diagnose business information to set up and carry out the diagnostic task example, realize diagnosis to business in the mode that obtains diagnostic result information; Because the diagnostic task example in this programme is set up automatically according to waiting to diagnose business, so with respect to prior art by for the scheme of seeking similar example in the case library, have more specific aim, location for traffic failure is more accurate, can improve the traffic failure diagnostic accuracy.And, in the present embodiment and since the script of fault diagnosis knowledge base be with diagnosis algorithm one to one, so, help the expansion and the maintenance of fault diagnosis knowledge base, such as, newly-increased if desired diagnosis algorithm only needs to add the pairing script of this diagnosis algorithm in knowledge base; In like manner, delete certain diagnosis algorithm if desired, the script that then only needs to delete this step correspondence is just passable.In addition, the fault diagnosis knowledge base in this traffic failure diagnosis can also have the various definitions mode, realizes comparatively flexible.
One of ordinary skill in the art will appreciate that all or part of step in the whole bag of tricks of the foregoing description is to instruct relevant hardware to finish by program, this program can be stored in the computer-readable recording medium, storage medium can comprise: read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), disk or CD etc.
More than a kind of traffic failure diagnostic method, device and system that the embodiment of the invention provided are described in detail, used specific case herein principle of the present invention and execution mode are set forth, the explanation of above embodiment just is used for helping to understand method of the present invention and core concept thereof; Simultaneously, for those skilled in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (18)
1. a traffic failure diagnostic method is characterized in that, comprising:
Obtain business information to be diagnosed;
Set up the diagnostic task example according to business information described to be diagnosed;
Carry out described diagnostic task example, obtain diagnostic result information;
Described diagnostic result information is transparent to client.
2. method according to claim 1 is characterized in that, described execution diagnostic task example obtains diagnostic result information and comprises:
By failure diagnosis kernel loads fault diagnosis knowledge base in buffer area or internal memory;
Carry out fault diagnosis knowledge base by the failure diagnosis kernel, obtain diagnostic result information.
3. method according to claim 2 is characterized in that, described fault diagnosis knowledge base comprises a script at least, and described script is corresponding with diagnosis algorithm;
Then described by failure diagnosis kernel execution fault diagnosis knowledge base, obtain diagnostic result information and comprise:
Determine the pairing script of current diagnosis algorithm by the failure diagnosis kernel;
Send the instruction of the pairing script of the current diagnosis algorithm of execution to fault diagnosis knowledge base, so that fault diagnosis knowledge base is carried out the pairing script of described current diagnosis algorithm by the failure diagnosis kernel;
Receive the diagnostic result information that fault diagnosis knowledge base returns by the failure diagnosis kernel.
4. method according to claim 3 is characterized in that, carries the identification information of the pairing script of next diagnosis algorithm in the described diagnostic result information.
5. method according to claim 3 is characterized in that, described fault diagnosis knowledge base is carried out the pairing script of current diagnosis algorithm and comprised:
Fault diagnosis knowledge base obtains alarm data required in the diagnostic procedure, performance data and/or service management data to the data collection agent module;
The pairing script of current diagnosis algorithm is done logic according to described alarm data, performance data and/or service management data and is carried out, and obtains diagnostic result information.
6. method according to claim 5 is characterized in that, describedly does logic according to alarm data, performance data and/or service management data and carries out, and obtains diagnostic result information and comprises:
Carry out alert analysis according to described alarm data,, perhaps determine the network element or the link of fault to determine the traffic failure reason; And/or,
According to the performance change situation of described performance data analysis monitored object, when there is reduction in the performance of finding described monitored object, determine the reduction reason, perhaps determine the network element or the link of fault; And/or,
Professional connective according to the service management Data Detection, to determine the network element or the link of fault; And/or,
According to service management Data Detection service attribute, to determine the traffic failure reason; And/or,
Carry out oam OAM according to the service management data and detect, to determine the traffic failure reason.
7. method according to claim 3 is characterized in that, described diagnosis business is divided into operation layer, virtual circuit PW layer, channel layer and link layer;
Then described fault diagnosis knowledge base is carried out the pairing script of current diagnosis algorithm and is comprised:
Fault diagnosis knowledge base obtains alarm data required in the diagnostic procedure, performance data and/or service management data to the data collection agent module;
Fault diagnosis knowledge base respectively to diagnosing professional operation layer, PW layer, channel layer and link layer to diagnose, obtains the diagnostic result information of each layer according to described alarm data, performance data and/or service management data;
Fault diagnosis knowledge base gathers the diagnostic result information of each layer, to obtain the pairing diagnostic result information of current diagnosis algorithm.
8. according to each described method in the claim 1 to 7, it is characterized in that described basis business information to be diagnosed is set up the diagnostic task example and comprised:
Wait to diagnose business information initialization diagnostic task example by failure diagnosis engine basis, to obtain the identification information of diagnostic task example;
By the failure diagnosis engine to diagnose professional carry out resource registering and resource mutual exclusion management after, the identification information of described diagnostic task example is sent to client, to set up the communication between client and the diagnostic task example.
9. according to each described method in the claim 1 to 7, it is characterized in that described diagnostic result information is transparent to also comprises after the client:
If described diagnostic result is accepted, then delete described diagnostic task example.
10. a traffic failure diagnosis server is characterized in that, comprising:
Acquiring unit is used to obtain business information to be diagnosed;
Set up the unit, be used for setting up the diagnostic task example according to business information described to be diagnosed;
Performance element is used to carry out described diagnostic task example, obtains diagnostic result information;
Transmitting element is used for described diagnostic result information is transparent to client.
11. traffic failure diagnosis server according to claim 10 is characterized in that, described performance element comprises the loading subelement and carries out subelement;
Set up the unit, be used for setting up failure diagnosis kernel, fault diagnosis knowledge base and data collection agent module according to business information described to be diagnosed;
Load subelement, be used for by failure diagnosis kernel loads fault diagnosis knowledge base to buffer area or internal memory;
Carry out subelement, be used for carrying out fault diagnosis knowledge base, obtain diagnostic result information by the failure diagnosis kernel.
12. traffic failure diagnosis server according to claim 11 is characterized in that, described fault diagnosis knowledge base comprises a script at least, and described script is corresponding with diagnosis algorithm, and then described execution subelement comprises:
Determine the sub level unit, be used for determining the pairing script of current diagnosis algorithm by the failure diagnosis kernel;
Issue the sub level unit, be used for sending the instruction of the pairing script of the current diagnosis algorithm of execution to fault diagnosis knowledge base, so that fault diagnosis knowledge base is carried out the pairing script of described current diagnosis algorithm by the failure diagnosis kernel;
Receive the sub level unit, be used for receiving the diagnostic result information that fault diagnosis knowledge base returns, carry the identification information of the pairing script of next diagnosis algorithm in the described diagnostic result information by the failure diagnosis kernel.
13. traffic failure diagnosis server according to claim 12 is characterized in that, described execution subelement also comprises:
Information gathering sub level unit is used for obtaining the required alarm data of diagnostic procedure, performance data and/or service management data by fault diagnosis knowledge base to the data collection agent module;
Script executing sub level unit is used to utilize the pairing script of current diagnosis algorithm that described alarm data, performance data and/or service management data are done logic and carries out, and obtains diagnostic result information.
14. traffic failure diagnosis server according to claim 13 is characterized in that,
Described script executing sub level unit specifically is used for carrying out alert analysis according to described alarm data, to determine the traffic failure reason, perhaps determines the network element or the link of fault; And/or, according to the performance change situation of described performance data analysis monitored object, when there is reduction in the performance of finding described monitored object, determine the reduction reason, perhaps determine the network element or the link of fault; And/or, professional connective according to the service management Data Detection, to determine the network element or the link of fault; And/or, according to service management Data Detection service attribute, to determine the traffic failure reason; And/or, carry out oam OAM according to the service management data and detect, to determine the traffic failure reason.
15. traffic failure diagnosis server according to claim 12 is characterized in that, described diagnosis business is divided into operation layer, virtual circuit PW layer, channel layer and link layer, and then described execution subelement also comprises:
Information gathering sub level unit is used for obtaining the required alarm data of diagnostic procedure, performance data and/or service management data by fault diagnosis knowledge base to the data collection agent module;
Diagnosis sub level unit is used for by fault diagnosis knowledge base, utilizes described alarm data, performance data and/or service management data respectively to diagnosing professional operation layer, PW layer, channel layer and link layer to diagnose, and obtains the diagnostic result information of each layer;
Gather the sub level unit, be used for gathering, to obtain diagnostic result information by the diagnostic result information of fault diagnosis knowledge base with each layer.
16., it is characterized in that the described unit of setting up comprises according to each described traffic failure diagnosis server in the claim 10 to 15:
Identification information obtains subelement, is used for by the failure diagnosis engine according to waiting to diagnose business information initialization diagnostic task example, to obtain the identification information of diagnostic task example;
Handle subelement, be used for by the failure diagnosis engine to diagnose professional carry out resource registering and resource mutual exclusion management after, the identification information of described diagnostic task example is sent to client, to set up the communication between client and the diagnostic task example.
17. according to each described traffic failure diagnosis server in the claim 10 to 15, it is characterized in that, also comprise:
Delete cells is used for after transmitting element is transparent to client with diagnostic result information, if described diagnostic result is accepted, then deletes described diagnostic task example.
18. a traffic failure diagnostic system is characterized in that, comprises described any traffic failure diagnosis server of client and claim 10 to 17;
Described client is used for sending and waits to diagnose business information to the traffic failure diagnosis server, and receives the diagnostic result information that the traffic failure diagnosis server returns.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110042572 CN102075368A (en) | 2011-02-22 | 2011-02-22 | Method, device and system for diagnosing service failure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110042572 CN102075368A (en) | 2011-02-22 | 2011-02-22 | Method, device and system for diagnosing service failure |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102075368A true CN102075368A (en) | 2011-05-25 |
Family
ID=44033723
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110042572 Pending CN102075368A (en) | 2011-02-22 | 2011-02-22 | Method, device and system for diagnosing service failure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102075368A (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102611917A (en) * | 2011-12-21 | 2012-07-25 | 华为技术有限公司 | Method and device for preprocessing network television fault |
| CN102821211A (en) * | 2011-06-10 | 2012-12-12 | 中兴通讯股份有限公司 | Automatic testing method and device for communication network elements |
| WO2013086996A1 (en) * | 2011-12-13 | 2013-06-20 | 华为技术有限公司 | Failure processing method, device and system |
| WO2014183728A1 (en) * | 2013-11-18 | 2014-11-20 | 中兴通讯股份有限公司 | Performance data management method and device |
| CN104869025A (en) * | 2014-02-24 | 2015-08-26 | 中国移动通信集团广东有限公司 | PTN (Packet Transport Network) service configuration parameter detecting method and system |
| CN105703934A (en) * | 2014-11-28 | 2016-06-22 | 亿阳信通股份有限公司 | PON network fault diagnosis method and apparatus for household broadband service |
| CN107800555A (en) * | 2016-09-05 | 2018-03-13 | 南京中兴软件有限责任公司 | Business diagnostic method and device |
| CN110187936A (en) * | 2019-05-31 | 2019-08-30 | 口碑(上海)信息技术有限公司 | Data backflow platform, system and method |
| CN110704230A (en) * | 2019-09-29 | 2020-01-17 | 携程旅游网络技术（上海）有限公司 | Diagnostic method, system, electronic device, and medium for distributed multi-module system |
| CN113132001A (en) * | 2019-12-30 | 2021-07-16 | 中兴通讯股份有限公司 | Optical module management method, optical module management device, network equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060117102A1 (en) * | 2004-11-26 | 2006-06-01 | Jae-Min Jeon | Apparatus and method for diagnosing network |
| CN101494573A (en) * | 2009-03-17 | 2009-07-29 | 杭州华三通信技术有限公司 | Method, system and equipment for diagnosing failure |
| CN101605346A (en) * | 2008-06-10 | 2009-12-16 | 中兴通讯股份有限公司 | The fault restoration method and apparatus |
-
2011
- 2011-02-22 CN CN 201110042572 patent/CN102075368A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060117102A1 (en) * | 2004-11-26 | 2006-06-01 | Jae-Min Jeon | Apparatus and method for diagnosing network |
| CN101605346A (en) * | 2008-06-10 | 2009-12-16 | 中兴通讯股份有限公司 | The fault restoration method and apparatus |
| CN101494573A (en) * | 2009-03-17 | 2009-07-29 | 杭州华三通信技术有限公司 | Method, system and equipment for diagnosing failure |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102821211A (en) * | 2011-06-10 | 2012-12-12 | 中兴通讯股份有限公司 | Automatic testing method and device for communication network elements |
| CN102821211B (en) * | 2011-06-10 | 2017-04-19 | 中兴通讯股份有限公司 | Automatic testing method and device for communication network elements |
| WO2013086996A1 (en) * | 2011-12-13 | 2013-06-20 | 华为技术有限公司 | Failure processing method, device and system |
| CN103167539B (en) * | 2011-12-13 | 2015-12-02 | 华为技术有限公司 | Fault handling method, equipment and system |
| CN102611917B (en) * | 2011-12-21 | 2014-12-10 | 华为技术有限公司 | Method and device for preprocessing network television fault |
| CN102611917A (en) * | 2011-12-21 | 2012-07-25 | 华为技术有限公司 | Method and device for preprocessing network television fault |
| CN104660428B (en) * | 2013-11-18 | 2019-08-02 | 中兴通讯股份有限公司 | A kind of management method and device of performance data |
| WO2014183728A1 (en) * | 2013-11-18 | 2014-11-20 | 中兴通讯股份有限公司 | Performance data management method and device |
| CN104660428A (en) * | 2013-11-18 | 2015-05-27 | 中兴通讯股份有限公司 | Management method and management device for performance data |
| CN104869025A (en) * | 2014-02-24 | 2015-08-26 | 中国移动通信集团广东有限公司 | PTN (Packet Transport Network) service configuration parameter detecting method and system |
| CN105703934A (en) * | 2014-11-28 | 2016-06-22 | 亿阳信通股份有限公司 | PON network fault diagnosis method and apparatus for household broadband service |
| CN105703934B (en) * | 2014-11-28 | 2019-11-26 | 亿阳信通股份有限公司 | A kind of PON network method for diagnosing faults and device towards home broadband business |
| CN107800555A (en) * | 2016-09-05 | 2018-03-13 | 南京中兴软件有限责任公司 | Business diagnostic method and device |
| CN107800555B (en) * | 2016-09-05 | 2023-01-24 | 中兴通讯股份有限公司 | Service diagnosis method and device |
| CN110187936A (en) * | 2019-05-31 | 2019-08-30 | 口碑(上海)信息技术有限公司 | Data backflow platform, system and method |
| CN110704230A (en) * | 2019-09-29 | 2020-01-17 | 携程旅游网络技术（上海）有限公司 | Diagnostic method, system, electronic device, and medium for distributed multi-module system |
| CN110704230B (en) * | 2019-09-29 | 2023-08-01 | 携程旅游网络技术（上海）有限公司 | Diagnostic method, system, electronic device and medium for distributed multi-module system |
| CN113132001A (en) * | 2019-12-30 | 2021-07-16 | 中兴通讯股份有限公司 | Optical module management method, optical module management device, network equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102075368A (en) | Method, device and system for diagnosing service failure | |
| US10649838B2 (en) | Automatic correlation of dynamic system events within computing devices | |
| CN111209131B (en) | Method and system for determining faults of heterogeneous system based on machine learning | |
| US9672085B2 (en) | Adaptive fault diagnosis | |
| US10177984B2 (en) | Isolation of problems in a virtual environment | |
| US8443078B2 (en) | Method of determining equivalent subsets of agents to gather information for a fabric | |
| US8874963B2 (en) | Operations management apparatus, operations management method and program thereof | |
| CN104903866A (en) | Management system and method for assisting event root cause analysis | |
| CN104796273A (en) | Method and device for diagnosing root of network faults | |
| US20130132778A1 (en) | Isolation of problems in a virtual environment | |
| CN111858254B (en) | Data processing method, device, computing equipment and medium | |
| CN112737800B (en) | Service node fault positioning method, call chain generating method and server | |
| CN114884838B (en) | Monitoring method and server of Kubernetes component | |
| CN111881014B (en) | System test method, device, storage medium and electronic equipment | |
| CN102363969A (en) | Excavator and method and system for determining equipment failure | |
| CN103345439B (en) | A kind of full link monitoring method of health state of information system and device | |
| CN106980572B (en) | Online debugging method and system for distributed system | |
| CN110311812A (en) | A kind of network analysis method, device and storage medium | |
| CN110674034A (en) | Health examination method and device, electronic equipment and storage medium | |
| CN107104838A (en) | A kind of information processing method, server and terminal | |
| CN111181800A (en) | Test data processing method and device, electronic equipment and storage medium | |
| US20090113243A1 (en) | Method, Apparatus and Computer Program Product for Rule-Based Directed Problem Resolution for Servers with Scalable Proactive Monitoring | |
| CN106021046A (en) | Hard disk performance comparison method, device and server | |
| CN104579745A (en) | Mobile terminal and network inspection system | |
| CN106776169A (en) | A kind of method and device of the PSU of testing service device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110525 |