CN102340495A

CN102340495A - Event center supporting cross-system service linkage and event processing method of event center

Info

Publication number: CN102340495A
Application number: CN2010102388511A
Authority: CN
Inventors: 应展伟; 陈建聪; 唐文波
Original assignee: China Mobile Group Guangdong Co Ltd
Current assignee: China Mobile Group Guangdong Co Ltd
Priority date: 2010-07-26
Filing date: 2010-07-26
Publication date: 2012-02-01
Anticipated expiration: 2030-07-26
Also published as: CN102340495B

Abstract

The invention provides an event center supporting a cross-system service linkage and an event processing method of the event center. The event center comprises: an acquisition module, which is used for obtaining original events reported by event collectors of all systems in a network and converting the original events into standardized events having a unified format; a thematic module, which is used for carrying out thematic processing on the standardized events obtained by the acquisition module on the basis of a preset thematic mode so as to obtain theme events; a processing decision module, which is used for determining response strategies of the theme events according to preset event response arrangement; and a distribution control module, which is used for carrying out distribution and control on the theme event according to the response strategies of the theme events. According to the invention, events are collected and processed by employing a bus structure mode through an event center, so that service logics are concentrated; moreover, services are easy to expand and maintain.

Description

A kind of event center and event-handling method thereof that supports the professional interlock of interdepartmental system

Technical field

The present invention relates to the business support technical field in the communication network, be specifically related to a kind of event center and event-handling method thereof that supports the professional interlock of interdepartmental system.

Background technology

When the business interlock that realizes interdepartmental system, the interface that at present many is between the employing system carries out point-to-point to fetching realization.The realization technology of interface is multifarious, mainly comprises: socket (SOCKET) mode, HTTP (HTTP, Hyper Text Transfer Protocol) mode and message queue (MQ, Message Queue) mode or the like.Wherein, the MQ mode is widely used in the interface of business support system is realized, such as, IBM MQ middleware.IBM MQ middleware is a general product, intermediate conveyor can be interface instruction, can be data file, be a kind of general message-oriented middleware.Yet the interface of each system all is to formulate according to the situation of oneself, and the codes and standards of the interface of each system and realization technology are all different; Therefore, when the business interlock of supporting interdepartmental system, professional interlock is subject to the interface capability of each system; And because the processing logic of each system is tightly coupled, the flexibility of professional interlock is very poor, along with the increase of business interlock demand; Form netted interconnectedly gradually, form the spider web predicament, the follow-up maintenance difficulty.The scheme of event center (EC, Event Center) is different with point-to-point interface docking mode, adopts to be similar to service-oriented architectural framework (SOA; Service-Oriented Architecture) ESB (ESB in; Enterprise Service Bus) to the way to manage of service. event center is based on that event-driven framework (EDA, Event-Driven Architecture) realizes, all systems are remained neutral; The same with ESB, adopt bus structures.

The professional interlock of interdepartmental system of the prior art support scheme adopts interface to carry out point-to-point docking mode and realizes that formed network structure, there is following problem in this scheme:

1, exchanges data and application call are point-to-pointly directly to be connected, and this close-coupled mode has caused netted interconnected between system, forms the spider web structure, are unfavorable for expansion and safeguard, are difficult to respond fast the market demand, support the quick action in market.

2, the direct-connected service logic that causes is disperseed between system, does not have unified service view and the automation of overall flow (part has automatic flow), is unfavorable for follow-up service management and supporting.

3, do not have unified codes and standards, service logic is disperseed, and causes quality management and business monitoring to realize very difficulty, the management and control of service operation difficult quality.

Summary of the invention

Technical problem to be solved by this invention provides a kind of event center and event-handling method thereof that supports the professional interlock of interdepartmental system; Adopt bus structures mode acquisition process incident through event center; Make service logic become concentrated, and service is easy to expansion and maintenance.

For solving the problems of the technologies described above, the present invention provides scheme following:

A kind of event center that supports the professional interlock of interdepartmental system comprises:

Acquisition module is used for obtaining the primitive event that the incident collector of each system of network reports and converts the standardization incident with consolidation form to;

The topicalization module is used for according to the predetermined subject pattern, and the standardization incident that acquisition module obtains is carried out the topicalization processing, obtains subject events;

Handle decision-making module, be used for confirming the response policy of subject events according to predefined event response setting;

The distribution control module is used for the response policy according to subject events, and subject events is distributed control.

Preferably, in the above-mentioned event center, said acquisition module comprises:

Registering unit is used for the incident acquisition capacity of registered events collector and incident collector;

Subscriber units is used for according to the subscription application of event response processor to subject events, confirms the relevant primitive event that subject events is corresponding, and subscribes to said relevant primitive event to each corresponding incident collector of said relevant primitive event;

Acquisition gateway; Be used for the primitive event that the incident collector that there is subscribing relationship in passive reception and said event center initiatively reports; And,, obtain the primitive event that said dependent event collector reports through active inquiry dependent event collector according to the demand that topicalization is handled; And the primitive event that reports based on each incident collector, generate and have the standardization incident of consolidation form.

Preferably, in the above-mentioned event center, said topicalization module comprises processing unit and regulation engine unit;

Wherein, said processing unit specifically comprises:

The excitation mode unit is used for exciting the new incident that obtains from a source event;

The merging patterns unit is used at least two source events are merged processing, forms a new incident;

The split mode unit is used for a source event is carried out deconsolidation process, forms at least two new incidents;

The filtered model unit is used for source event is carried out filtration treatment, filters out to carry out the incident that topicalization is handled;

The heartbeat mode unit is used for when source event does not periodically inspire a new incident, and produce one and be used for the unusual anomalous event of identification service situation, as, system status monitoring is the type incident;

Assembled unit is used for utilizing at least two unit of said excitation mode unit, merging patterns unit, split mode unit, filtered model unit and heartbeat mode unit, and source event is handled, and obtains new incident;

Said regulation engine unit is used for according to the topicalization pattern to the standardization incident that is provided with in advance, calls said processing unit the standardization incident is carried out the topicalization processing, obtains subject events.

Preferably, in the above-mentioned event center,

Said processing decision-making module; Be further used for according to foregone conclusion spare response setting, incident flow set and the setting of event response processor; Confirm the response policy of subject events; Said response policy comprises the flow of event revolving die formula that whether makes an immediate response with said subject events, and wherein, said flow of event revolving die formula comprises distribution subscription pattern and directed routing pattern;

Said distribution control module is further used for the flow of event revolving die formula according to said subject events, said subject events is distributed to corresponding event response processor handles.

Preferably, in the above-mentioned event center, also comprise:

The incident memory module is used for according to service priority information, confirms the rank of the standardization incident that said acquisition module obtains, and stores in the incident storage queue with corresponding priority; And according to the priority of incident storage queue and the incident quantity in the incident storage queue; Confirm the quantity of the distribution scheduling thread that the incident storage queue is corresponding, standardization incident to the said topicalization module that said distribution scheduling thread is used for dispatching said incident storage queue is carried out topicalization and is handled.

Preferably, in the above-mentioned event center, also comprise:

Incident filing module is used for subject events after the said response policy rejecting or the result after the response policy processing are carried out filing management;

Quality management module is used for the health degree of each system related with said event center is assessed management;

The tracing and monitoring module is used for other module of said event center is followed the tracks of, the operating state of said other module of record.

The present invention also provides a kind of event-handling method of event center, may further comprise the steps:

Obtain the primitive event that the incident collector of each system in the network reports and convert standardization incident to consolidation form;

According to the predetermined subject pattern, the standardization incident that acquisition module obtains is carried out the topicalization processing, obtain subject events;

According to predefined event response setting, confirm the response policy of subject events;

According to the response policy of subject events, subject events is distributed control.

Preferably, in the above-mentioned event-handling method,

Said obtain the primitive event that the incident collector reports and convert standardization incident to consolidation form before, also comprise: the incident acquisition capacity of registered events collector and incident collector; According to of the subscription application of event response processor, confirm the relevant primitive event that subject events is corresponding, and subscribe to said relevant primitive event to each corresponding incident collector of said relevant primitive event to subject events;

Saidly obtain the primitive event that the incident collector reports and convert standardization incident to consolidation form; Comprise: the primitive event that passive reception and said event center exist the incident collector of subscribing relationship initiatively to report; And the demand of handling according to topicalization; Through active inquiry dependent event collector, obtain the primitive event that said dependent event collector reports; And the primitive event that reports based on each incident collector, generate and have the standardization incident of consolidation form.

Preferably, in the above-mentioned event-handling method,

Said topicalization is handled and is comprised:

Excite processing, excite the new incident that obtains from a source event;

Merge and handle, at least two source events are merged processing, form a new incident;

Deconsolidation process is carried out deconsolidation process with a source event, forms at least two new incidents;

Filtration treatment is carried out filtration treatment to source event, filters out to carry out the incident that topicalization is handled;

Heartbeat is handled, and when source event does not periodically inspire a new incident, produces one and is used for the unusual anomalous event of identification service situation; And,

Combined treatment is used for utilizing said at least two kinds of processing modes that excite processing, merging processing, deconsolidation process, filtration treatment and heartbeat to handle, and source event is handled, and obtains new incident.

Preferably, in the above-mentioned event-handling method,

Said according to predefined event response setting; Confirm the response policy of subject events; Comprise: be provided with according to foregone conclusion spare response setting, incident flow set and event response processor, confirm the response policy of subject events, said response policy comprises the flow of event revolving die formula that whether makes an immediate response with said subject events; Wherein, said flow of event revolving die formula comprises distribution subscription pattern and directed routing pattern;

Said response policy according to subject events is distributed control to subject events, comprising: according to the flow of event revolving die formula of said subject events, said subject events is distributed to corresponding event response processor handles.

Preferably, in the above-mentioned event-handling method, also comprise:

Said obtain the primitive event that the incident collector reports and convert standardization incident to consolidation form after; Further according to service priority information; Confirm the rank of the standardization incident that said acquisition module obtains, and store in the incident storage queue with corresponding priority; And according to the priority of incident storage queue and the incident quantity in the incident storage queue; Confirm the quantity of the distribution scheduling thread that the incident storage queue is corresponding, the standardization incident that said distribution scheduling thread is used for dispatching said incident storage queue is carried out topicalization and is handled.

Preferably, in the above-mentioned event-handling method, also comprise:

Subject events after the said response policy rejecting or the result after the response policy processing are carried out filing management;

Health degree to each system related with said event center is assessed management; And

Other module in the said event center is followed the tracks of, the operating state of said other module of record.

Can find out that from the above a kind of event center and event-handling method thereof that supports the professional interlock of interdepartmental system provided by the invention is through the pattern of middleware; Integrate relevant heterogeneous system; And the collection event data, and the primitive event of gathering is carried out topicalization handle, carry out distribution subscription then; Or the incident circulation, finally serve the third party system through processing protocol.The event center of present embodiment and event-handling method thereof adopt bus structures mode acquisition process incident through event center, finally form the decoupling zero of service interface; The tap/dip deep into of incident, the uniform service standard interface makes service logic become concentrated; Expansion that is easy to serve and maintenance; Accelerated the response speed of service, standardization service interface, improved quality and efficient.And what event center adopted is bus structures, is independent of each system; It is the loose coupling structure; Exploitation and setting that the business interlock of interdepartmental system only need be correlated with in event center get final product, and when business demand changes, also only need in the event center scope, revise being provided with and exploitation.

Description of drawings

Fig. 1 is the structural representation of the described event center of the embodiment of the invention;

Fig. 2 is the schematic flow sheet of the event-handling method of the described event center of the embodiment of the invention;

Fig. 3 is the position view of the described event center of the embodiment of the invention in network;

Fig. 4 is the general function framework sketch map of the described event center of the embodiment of the invention;

Fig. 5 is the parameter sketch map of standardization incident in the embodiment of the invention;

Fig. 6 is the sketch map of distribution subscription pattern in the embodiment of the invention;

Fig. 7 is the sketch map of directed routing pattern in the embodiment of the invention;

Fig. 8 is the collecting flowchart sketch map of the acquisition module of the said event center of the embodiment of the invention;

Fig. 9 is the Stored Procedure sketch map of the incident memory module of the said event center of the embodiment of the invention;

Figure 10 is the sketch map of thread distribution scheduling in the embodiment of the invention;

Figure 11 is the structural representation of topicalization module described in the embodiment of the invention;

Figure 12 is a sketch map of handling the processing decision-making of decision-making module described in the embodiment of the invention;

Figure 13 is the sketch map of subject events distribution control in the embodiment of the invention.

Embodiment

The invention provides a kind of event center and event-handling method thereof that supports the professional interlock of interdepartmental system; To the event center reported event, event center is concentrated incident is gathered and handled, and makes service logic become concentrated by the incident collector of each system in the network; Service is easy to expansion and safeguards; And accelerated the response speed of service, standardization service interface, improved quality and efficient.Below will combine accompanying drawing, the present invention done further explanation through specific embodiment.

At first, please with reference to Fig. 1, the described event center 10 of the embodiment of the invention comprises:

Present embodiment also correspondingly provides a kind of event-handling method, is applied to event center shown in Figure 1, and is as shown in Figure 2, and this event-handling method may further comprise the steps:

Step 21 is obtained the primitive event that the incident collector of each system in the network reports and is converted the standardization incident with consolidation form to;

Step 22, according to the predetermined subject pattern, the primitive event that acquisition module is obtained carries out the topicalization processing, obtains subject events;

Step 23 according to predefined event response setting, is confirmed the response policy of subject events;

Step 24 according to the response policy of subject events, is distributed control to subject events.

In the above-mentioned steps 22, said topicalization mode-definition the topicalization processing procedure of standardization incident, said topicalization is handled and is specifically comprised:

Excite processing, excite the new incident that obtains from a source event;

Can find out from the above, because prior art just need be carried out point-to-point development interface between each system when the demand of the professional interlock of interdepartmental system is arranged.And because this point-to-point interface is tightly coupled, that is to say, just need development interface again,, form the spider net type structure so prior art can cause intersystem interface increasingly sophisticated if the interlock demand changes.And the event center that present embodiment provided adopts is bus structures (focus on incident that the incident collector of each system reports also), is independent of each system, is the loose coupling structure between itself and other system; Therefore the business of the interdepartmental system interlock exploitation that need in event center, be correlated with and setting get final product; When business demand changes, also only need in the event center scope, revise being provided with and exploitation, thereby make service logic become concentrated; Expansion that is easy to serve and maintenance; Accelerated the response speed of service, standardization service interface, improved quality and efficient.

Below will further do more detailed explanation to each step of above-mentioned event center and each functional module and event-handling method.

(1) event center overall introduction

In the present embodiment; Event center is a kind of novel middleware that supports the professional interlock of interdepartmental system, and the key foundation that is based on the integrated information technology of operation (IT) supporting framework-EDA/SOA framework of software realization supports one of facility (event center, dynamic data switching center, ESB).The position of event center in network is specifically as shown in Figure 3.

Among Fig. 3, RE representes primitive event (Raw Event), and TE representes subject events (Topic Event), and RC representes that response calls (Response Callback).As can beappreciated from fig. 3; The primitive event that the incident collector of each system of event center reception reports; The model analysis class incident that reports of the incident collector of province/city's mining model system for example, worker's list/order incident that the incident collector of market/system of number industry/group reports, the client that the incident collector of a line customer service system reports contacts incident; Net maintains the cell monitoring incident that the incident collector of system reports, and the system monitoring incident that the incident collector of ITC system reports is waited for.Event center carries out format conversion to these primitive events, generates the standardization incident (certainly, if the primitive event that the incident collector reports is exactly the standardization incident, then need not to carry out format conversion) of consolidation form; Then the standardization incident is carried out topicalization and handle, obtain subject events; Again according to the decision-making response policy of subject events; Subject events is distributed control; Through ESB subject events is distributed to events corresponding consumer (event response processor), the event response processor in core processing engine as shown in Figure 3, core response service system, peripheral response service system and the key business analytical system.

In the present embodiment, incident is meant the variation of client's (inside and outside) state, and the variation of customer status is the external manifestation of client traffic changes in demand, that is, incident is the data that are used to indicate the client traffic changes in demand.Present embodiment on the basis of event center, can realize based on incident the marketing of taking the initiative in offering a hand, based on the customer insight and the channel interaction of incident, realize operation integrated with the service marketing automation.

The general function framework of event center is as shown in Figure 4, comprises functions such as incident collection, incident storage, event topicization, subject events management, incident distribution control, processing engine management, quality management and event-monitoring.Hereinafter will introduce these functions respectively.

Event center carries out format conversion to the primitive event that the incident collector of each system in the network reports in the present embodiment; Generate the standardization incident of consolidation form; The below definition of a kind of standardization incident in the explanation present embodiment; Need to prove that the concrete form of below introducing does not constitute restriction to the present invention.The present invention can adopt self-defining consolidation form, as long as this consolidation form can carry out complete definition to event attribute.

(2) format description of a kind of standardization incident of providing of present embodiment

In the present embodiment, " 5W+1R " principle is mainly followed in the description of standardization incident, and is specifically as shown in Figure 5.Can find out that the standardization incident of consolidation form comprises at least a of following six kinds of parameters:

The information of the object that 1, incident reflected is in Fig. 5 wClient's phone number, system or the module number etc. of definition among one of the ho;

2, the source-information of incident is in Fig. 5 wThe Event origin system numbering of definition, terminal iidentification etc. among one of the here;

3, the temporal information of incident is in Fig. 5 wThe Time To Event of definition, effective time, processing time etc. among one of the hen;

4, the type information of incident is in Fig. 5 wThe event type coding of definition, scene coding, spreading parameter etc. among one of the hat;

5, the personalization attributes information of incident is like ho among Fig. 5 wThe make of the incident of definition, urgency level, level of security, significance level, impact rank, external command, circulation pattern identification etc. in one;

6, the state information of incident and processing result information.

Can find out to have the standardization incident that above-mentioned consolidation form is described, can define the attribute of incident, and describe complete processing procedure, comprise with the mode of " narration " from different dimensions:

1, this incident is had do not have special requirement (like priority, significance level, risk etc.), it is for reference or handle whether need to provide attachment data;

2, (what place, who, must completion in how long) whom this incident should give and go to handle;

3, carry out this time and mainly accomplish which task?

4, the result of incident how, when handles, and is to handle overtime the needs, still handles failure.

A kind of file operation language (FML, File Manipulation Language) that below provides present embodiment accepted standard incident is described:

<FML>

< incident >

<WHO>

<client's Shou Jihaoma></client Shou Jihaoma>

<the numbering > of system; <the numbering > of/>system;

</WHO>

<WHERE>

</WHERE>

<WHEN>

</WHEN>

<WHAT>

</WHAT>

<HOW>

<impact rank; </>impact rank;

</HOW>

<miao Shu > as a result; </>Miao Shu > as a result;

</RESULT>

</Shi Jian>

</FML>

(3) flow of event revolving die formula

Flow of event revolving die formula comprises distribution subscription pattern and directed routing pattern in the present embodiment.Said processing decision-making module among Fig. 1; Be further used for according to the processing response setting of foregone conclusion spare response setting, incident flow set and event response processor incident; Confirm the response policy of subject events, said response policy comprises the flow of event revolving die formula of said subject events; Said distribution control module is further used for the flow of event revolving die formula according to said subject events, said subject events is distributed to corresponding event response processor handles.Below introduce this two kinds of flow of event revolving die formulas.

1, distribution subscription pattern

The distribution subscription pattern is the subscriber that event center is sent to subject events this subject events.

The sketch map of distribution subscription pattern is as shown in Figure 6, and the incident collector among the system A is registered primitive event to event center, and event center carries out being published to after the topicalization consumer of each incident with this primitive event, in the event response processor among the B of system; When the B of system need obtain certain subject events, just subscribe to event center; Then, the incident collector of the primitive event that relates to this subject events of event center is subscribed to; Then, the incident collector among the system A reports primitive event to event center, and event center to the subscriber of this subject events, like the B of system, sends this subject events after carrying out obtaining subject events after format conversion and topicalization are handled; System B carries out the event response processing according to the handling process of oneself after taking subject events, and feeds back to event center to result.The flow process of event subscription pattern that Here it is.

2, directed routing pattern

The sketch map of directed routing pattern is as shown in Figure 7.

The directed routing pattern is when the incident of carrying out is gathered, the just directed event response processor that will give after the processing of primitive event process event center of having specified.Such A of system just can through the B of system its intrasystem primitive event is handled, and event center just play the effect of a directed routing therein according to the needs of oneself.

(4) the event center functional module details

1. incident acquisition function

The incident acquisition function is realized by the said acquisition module of event center shown in Figure 1; Be the function of setting at event center in order to collect various primitive events, its function comprises event registration management, event subscription management, incident routing management, incident collection service etc.

The acquisition module of present embodiment in the handling process of whole event, through the acquisition process to incident, forms unified Event Service interface, has realized the decoupling zero to the data Fabric Interface; Can form simultaneously the consistent service view and the automation of overall flow; The interface specification of final formation standard is accelerated corresponding speed, promotes service quality.

Shown in Figure 8 is the collecting flowchart sketch map of the acquisition module in the event center shown in Figure 1.As shown in Figure 8, said acquisition module specifically comprises:

Registering unit is used for the incident acquisition capacity of registered events collector and incident collector.

Registration comprises collector registration and event registration.The collector registration is that the collector of each system will be before event center provides incident collection service; Must register to the collector registration center of event center, the content of registration mainly comprises: contents such as collector numbering, collector title, protocol type, network parameter.Event registration is that the acquisition capacity of newly-increased certain primitive event of incident collector is; Need carry out the registration of certain primitive event acquisition capacity to the event registration center of event center; The content of registration mainly comprises: event identifier, collector label, event type, state-event, time, event description, founder, creation-time, approval status, approver, examine time, remarks; Have only the registration of initiation, and could supply this primitive event to event center through the incident acquisition capacity of examining.

Subscriber units is used for according to the subscription application of event response processor to subject events, confirms the relevant primitive event that subject events is corresponding, and subscribes to said relevant primitive event to each corresponding incident collector of said relevant primitive event.

After event subscription is meant that mainly event center is received the subscription application of subject events consumer initiation; The primitive event that this subject events relates to needs event center to subscribe to each events corresponding collector, and the content of subscription comprises: subscriber, event identifier, ageing, subscription status, state time, founder, collector numbering.The incident collector is only received after the subscription of event center is instructed just can supply subscribed primitive event to event center, and other the subscribed primitive event that do not have need be to gathering.

Said acquisition module also comprises various interface, agent unit, service interface and incident route (up, descending route) unit.

The pattern of incident collection is divided into following several types:

Initiatively report: after the built-in incident collector generation subscribing relationship of event center and event source; The acquisition gateway of event center initiatively reported data by the built-in incident collector of event source; Acquisition gateway carries out passive event collection work, and feeds back to event source collecting the result.

Acknowledgment of your inquiry: no matter whether event center and the built-in incident collector of event source subscribing relationship takes place; Event center needs because of the topicalization processing; Initiatively initiate inquiry through acquisition gateway to the built-in incident collector of event source; Whether inquiry exists the incident that satisfies condition, and the built-in incident collector of event source according to circumstances feedback event data arrives acquisition gateway.

The agency reports: after the incident collector generation subscribing relationship of event center and event source external (through plug-in monitoring); The acquisition gateway of event center initiatively reported data by the external incident collector of event source; Acquisition gateway carries out passive event collection work, and feeds back to event source collecting the result.

Agents query: no matter whether event center and the external incident collector of event source subscribing relationship takes place; Event center needs because of the topicalization processing; Initiatively initiate inquiry through acquisition gateway to the external incident collector of event source; Whether inquiry exists the incident that satisfies condition, and the external incident collector of event source according to circumstances feedback event data arrives acquisition gateway.

In the present embodiment, acquisition gateway is as the core of event center, and it relates to following three quasi-protocols and a kind of Standard File Format (being the consolidation form that present embodiment standardization incident is adopted).If the primitive event that the incident collector reports be the below utilizing 1.～3. acquisition protocols describe, then acquisition gateway need be resolved the row format conversion of going forward side by side of this primitive event, obtains the standardization incident of consolidation form.Describe in the face of these several kinds of agreements down.

1. CBossIntPkg acquisition protocols

What the incident collector was imported is the CBossIntPkg protocol package, and acquisition gateway carries out format conversion to this protocol package, and output has the standardization event object of consolidation form.

Handle main points:

Resolve the CBossIntPkg packet, in the standardization event object, get final product according to following correspondence setting.

Char strIntID [ID_LEN+1];-＞Event origin system banner

Char strIntCmd [ID_LEN+1]; + char strIntSubCmd-＞primitive event sign (centre is cut apart with ": ")

Char strTelnum [ID_LEN+1];-＞client phone number

Char strRegion [SHORTID_LEN+1];-＞area code

Char strOperator [ID_LEN+1]; The operator of-＞trigger event

Char strUniContact [ID_LEN+1]-＞terminal iidentification;

Time To Event adopts system time to get final product (because this type incident is the crm system active push, processing is very timely)

2. XML form acquisition protocols

Definition XML form comprises following content: the operator of area code, primitive event coding, incident title, client's phone number, Event origin system banner, terminal iidentification, trigger event, Time To Event, incident out-of-service time (optional), additional parameter etc.

What the incident collector was imported is XML format protocol bag, and acquisition gateway carries out format conversion to this protocol package, and output has the standardization event object of consolidation form.

Handle main points: the analyzing XML packet, the respective attributes that is set to related data the standardization event object gets final product.

3. Character segmentation combination protocol

Use special character to cut apart between each attribute, and form a new character string, handle as input parameter.

What the incident collector was imported is combining characters string and attribute decollator (can not specify, be defaulted as "～"), and acquisition gateway carries out format conversion, and output has the standardization event object of consolidation form.

Handle main points: resolve the combining characters string, decomposite all and must get event attribute (identical), and be set in the respective attributes of standardization event object and get final product with above-mentioned agreement.

4. Standard File Format collection

The data of this document are stored according to the structure of " event object of standard ", and capture program only need carry out reduction of data and get final product.

Be mainly used in that event queue is overflowed or database carries out the file backup when unusual, and then carry out reduction of data.

2. incident memory function

Run in the incorporate event center, after the processing of event data through initial registration subscription, route, finally can obtain a large amount of client's event datas.In order reasonably to manage these a large amount of event datas get up; Also comprise an incident memory module in the event center shown in Figure 1; Be used for according to service priority information; Confirm the rank of the standardization incident that said acquisition module obtains, and store in the incident storage queue with corresponding priority; And according to the priority of incident storage queue and the incident quantity in the incident storage queue; Confirm the quantity of the distribution scheduling thread that the incident storage queue is corresponding, standardization incident to the said topicalization module that said distribution scheduling thread is used for dispatching said incident storage queue is carried out topicalization and is handled.

This incident memory module has made things convenient for the management of event data on the one hand, for event center initial primitive event storehouse is provided on the other hand.Shown in Figure 9 is the Stored Procedure sketch map of this incident memory module, and this incident memory module is pressed information such as service priority, and hierarchical processing is carried out in the incident storage queue, and concrete priority is described below:

1) urgent formation: the first order priority level that refers to weigh event handling from degree of being pressed for time.

2) important formation: the second level priority level that refers to weigh event handling from the significance level of incident.

3) high power capacity formation: from the third level priority level of how much weighing event handling of whole event source data.

4) general formation: the fourth stage priority level of weighing event handling from the normal vital degree of incident.

5) Low Priority Queuing: the incident beyond the above-mentioned priority can be weighed event handling according to actual conditions.

The standardization incident of different priorities is stored in the corresponding incident storage queue; Carry out classification according to the event number of storing in the incident storage queue then; Decide the thread distribution scheduling processing events storage of launching different stage, and through the different threads distribution scheduling incident is carried out topicalization and handle.Figure 10 has provided the sketch map of a thread distribution scheduling 100, can find out, event number is many more, and the Thread Count that is used for distribution scheduling is also many more.Also show a kind of priority in the following table, decide the concrete example of thread distribution number according to incident capacity levels in the incident storage queue and incident storage queue.

The incident capacity levels	Capacity number	Priority	Thread distribution number (can be provided with)	Remarks
					Senior	80％～99％	Excellent	More than 3000
Middle rank	50％-80％	Very	2000-3000
					Rudimentary	1％-50％	Difference	1000-2000

In sum, distribution scheduling is according to incident capacity number and queue priority in the formation, Thread Count is set to reach the purpose of system self-adaption event topic processing.

The incident storage is the reasonable stores processor to event data.Comprise incident storage, incident inquiry, three parts of event queue management.

Wherein, incident storage comprises field to be had: incident title, source, ageing, state, classification, creation-time, founder, collector ID.The specifying information of incident storage queue comprises again: title, type, state, length, description, creation-time, founder.Simultaneously, incident storage can also include the information of event response processor, like the numbering of processor, title, network parameter, protocol type, ageing, state, founder etc.The mode of incident storage specifically comprises: file mode, database mode, file+database mode etc.

The incident memory module is also carried out the management of formation, specifically comprises management such as memory capacity, queue length, queue structure, queuing message, Event Priority.The way to manage of formation comprises file mode and internal memory mode.Wherein, file mode is to change operation with the additions and deletions that the mode of file is carried out formation; The internal memory mode is to change management with the additions and deletions that the mode of internal memory is carried out formation.

The storage queue structure can be taked sequential storage structure and storage of linked list structure, for the stored in form of the event queue of often inserting, deleting with chained list, takes the storage organization of order for the event queue that just order is inserted and delete at the end.

The queue structure of sequential storage:

1) the same with sequence list, sequential queue is deposited the element in the current queue with a vector space.

2) because the team's head of formation and the position of tail of the queue change, two pointer front and rear are set indicate team's element and the position of tail of the queue element in vector space respectively, their initial value all should be changed to 0 when the formation initialization.

Chained list queue structure specifically comprises single-track link table, doubly linked list and circular linked list, repeats no more at this.

3. event topic function

Event topicization is the core of event center; Said topicalization module by event center shown in Figure 1 realizes; Its function simply is interpreted as the topicalization processing of the standardization event data that collects of gathering the center being carried out closed loop, forms new subject events storehouse.

Please with reference to Figure 11, the said topicalization module of event center shown in Figure 1 comprises processing unit and regulation engine unit.Wherein, said processing unit specifically comprises:

Assembled unit is used for utilizing at least two unit of said excitation mode unit, merging patterns unit, split mode unit, filtered model unit and heartbeat mode unit, and source event is handled, and obtains new incident.

Here above-mentioned source event can be the standardization incident, also can be the intermediate event that after above-mentioned topicalization resume module, obtains, and can also be subject events.Above-mentioned new incident can be a subject events, also can be the intermediate event that after above-mentioned topicalization resume module, obtains.

Said regulation engine unit is used for according to the topicalization pattern to the standardization incident that is provided with in advance, calls said processing unit the standardization incident is carried out the topicalization processing, obtains subject events.Define the topicalization processing procedure of standardization incident in the topicalization pattern, promptly defined the concrete unit of said processing unit for processing standardization incident, and the sequencing of handling.

4. processing decision making function

Handling decision making function is realized by the said processing decision-making module of event center shown in Figure 1; Be according to being the basis with the subject events in the subject events storehouse; According to predefined event response setting, confirm the response policy of subject events, form the event response task library.

Figure 12 shows the flow process of the processing decision-making of handling decision-making module, and first zone of wherein handling decision-making module is judged and wanted to handle for subject events is carried out Analysis of Policy Making; Second zone is how subject events to be handled carry out policy selection.

At first the process of the Analysis of Policy Making of decision-making module is handled in explanation:

Handle in the decision-making module and be provided with a plurality of decision condition in advance, as

One, event response setting

Event response is provided with, and is used to be provided with the response policy of subject events, and can carries out the switch setting, comprise following some:

1) do not have coupling setting, be used for being provided with whether subject events is carried out matching treatment,, will be distributed to the events corresponding respective processor and handle for the subject events of no matching treatment; For the subject events of wanting matching treatment, then can carry out inter-process by handling decision-making module.

Whether 2) whether all incidents close setting, be used for being provided with all subject events shut down decisions being handled;

3) whether response closing setting of event category, whether the subject events that is used to be provided with some classification needs decision-making treatment;

4) whether response closing setting of incident is used to be provided with some subject events and whether needs decision-making treatment;

Two, incident flow set

The incident flow set is to the monitoring setting of system handles incident flow, comprises the setting of the following aspects:

1) whether controls flow, be used to be provided with the whole flow that whether needs the control event center;

2) event type flow is used to be provided with the flow of the subject events of some type;

3) incident flow is used to be provided with the flow of subject events;

4) whether surpass flow, be used to be provided with flow restriction, like day, hour flow;

5) all service traffics are used to be provided with all professional flows;

Three, the event response processor is provided with

The event response processor is provided with, and is according to the health degree of system under the event response processor and the health degree of event center platform itself, to the processing response setting of incident, what time mainly comprises:

1, the system health degree situation of association, the i.e. health degree of system under the event response processor;

2, this own health status of event center platform;

The process of the policy selection of decision-making module is handled in explanation then.

One, response policy is to the strategy setting of the processing mode of incident, comprises following each side:

1) event response strategy is used to be provided with the event response strategy of subject events;

2) ignore, be used to be provided with subject events is ignored response;

3) wait-for-response is used to be provided with to wait for a period of time back response of subject events;

4) response at once is used to be provided with subject events is responded immediately

Two, priority evaluation

Priority evaluation emphasis is the evaluation setting to the priority level of carrying out response:

1) execution priority is not set, and the priority level of response is carried out in decision.

Said processing decision-making module among Fig. 1; Can be further used for according to foregone conclusion spare response setting, incident flow set and the setting of event response processor; Confirm the response policy of subject events; Said response policy comprises the flow of event revolving die formula that whether makes an immediate response with said subject events, and wherein, said flow of event revolving die formula comprises distribution subscription pattern and directed routing pattern.Whether said response policy comprises the theme time is responded, and the time of carrying out response.

5, distribution controlled function

The distribution controlled function is realized by the said distribution control module of event center shown in Figure 1; It is flow of event revolving die formula (comprising distribution subscription and directed routing pattern) according to the subject events of handling the decision-making module generation; Subject events is distributed control, be distributed to corresponding event response processor and handle.Wherein, the distribution subscription pattern is the demand of event response processor according to self, and the subject events of handling issue in the decision-making is subscribed to, and is distributed to the subscriber of this subject events by event center.And the directed routing pattern then is that subject events is carried out route distribution, gives the event response processor of appointment.

Distribution control is the handling process of carrying out decision-making, and Figure 13 shows this flow process.

Distribution control is the core of event center, mainly adopts four kinds of processing protocol, as follows:

Radio Broadcasting Agreements: Radio Broadcasting Agreements is similar to udp protocol,, carries out through Radio Broadcasting Agreements the data of issue event center according to all channels.

The program request agreement: the program request agreement is each channel or system, according to self needs, satisfies the data that oneself require to the event center request, and event center is according to the demand feedback data result.

Multicast protocol: multicast protocol is to play by all kinds of means according to the channel of having subscribed to, and arrives multiple support channels to data sync.

Polling protocol: polling protocol is a kind of according to a kind of processing protocol of carrying out the channel requesting query at interval, and it is according to the data of handling the request channel at interval.

6. incident is filed function

Event center shown in Figure 1 can also comprise incident filing module, is used for subject events after the said response policy rejecting or the result after the response policy processing are carried out filing management.The content of filing comprises archival configuration, and event handling is single, filing is handled, the filing audit.

7. quality management module

Event center shown in Figure 1 can also comprise quality management module, is used for the health degree of each system related with said event center is assessed management.Can be self-defined in the present embodiment setting grading rule, and then carry out the rank evaluation, and carry out the rank control and management according to the rank of evaluation.Below simply describe.

In quality management, at first to assess the working order of each system, the system health degree assessment management that just here proposes here will not be paid close attention to for the key element of assessment, just pays close attention to final assessment result.

(1) grading rule

To the assessment classification of system health degree, mark wherein is that the weight of in system, occupying according to different parts and the marking rule of self are carried out, and is specific as follows:

(2) evaluation rank

Draw the health degree score of system by above-mentioned three weight parameter and self score value, can be divided into following seven ranks, like following table:

(3) rank control

According to above next be how each rank is dispatched processing to system's hierarchical processing of giving a mark, see the following form in detail:

The flow adjustment is to describe according to the amount that adjustment is fallen in the last table, as to adjust 0 meaning be exactly not adjust, and 20% is exactly exactly total flow to be reduced to 100% to total flow reduction by 20%, 100%, just stops.

8, tracing and monitoring module

Event center shown in Figure 1 can also comprise the tracing and monitoring module, is used for other module of said event center is followed the tracks of the operating state of said other module of record.

In the running of the integrated event center of operation system; Comprising various incident collections, event handling, arranging service; The processing procedure of service call or the like, present embodiment comes acquisition system working order when carrying out each step processing through the tracing and monitoring module.

Tracing and monitoring is followed the tracks of each processing the system from literal understanding exactly, writes down the operating state of each processing, offers the administrative staff of system, conveniently in time makes adjustment according to the running status of each module.

Tracing and monitoring is that the processing procedure of whole event is monitored, and comprises flow of event component analysis, anomalous event monitoring, alarm monitoring processing.

At last, understand present embodiment,, come the event center and the event-handling method thereof of present embodiment are illustrated through a concrete applying examples in order further to help.

Business description:

To the wherein impact of high-end consumer markets, the A of operator need formulate measure targetedly and break through the A of operator for the activity of distributing telephone numbers (supposing that the number of distributing telephone numbers section is No. 189 sections) of tackling the B of operator.It is main market measure that the middle and high end client possesses activity; In the BI system, make up middle and high end customer churn Early-warning Model; This model can be exported various middle and high end customer churn early warning incidents, and this time comprises to concrete incident of the activity of distributing telephone numbers: the B customer manager of operator phone contact incident, 189 conversation early warning incidents, middle and high end client bundle loosening incident, the high-rise group of the B of operator customer phone and show loving care for incident, the B of operator outgoing call contact incident, the middle and high end customer mobile phone terminal early warning incident etc. of changing planes.When these different event occur, take different specific aim measures to carry out the client to concrete client and possess.

At first, customer churn Early-warning Model in middle and high end need be carried out all primitive events registrations that the incident supplier registers and can provide to event center.The middle and high end client possesses that platform campaign management platform CMP is carried out in the management of marketing activity, group's crm system need be to event center registered customers identity.Then, need utilization event center topicalization module, above-mentioned primitive event is carried out topicalization, topicalization rule need be at regulation engine, ILOG for example, in some row topicalization rules are set.According to business demand, following topicalization pattern need be set:

If (client's number in (individual VIP number))

If ((the B customer manager of the operator phone contact incident or B of operator outgoing call contact incident) and (middle and high end client bundle loosening incident or middle and high end customer mobile phone terminal change planes early warning incident))

Excite the individual VIP early warning subject events that highly runs off

Else if ((the B customer manager of the operator phone contact incident or B of operator outgoing call contact incident) or (middle and high end client bundle loosening incident or middle and high end customer mobile phone terminal change planes early warning incident))

Excite individual VIP moderate loss early warning subject events

Else excites the low loss early warning of individual VIP subject events

Else if (client's number in (group customer))

If ((the high-rise group customer contact of the B customer manager of the operator phone contact incident or B of operator incident) and (middle and high end client bundle loosening incident or middle and high end customer mobile phone terminal change planes early warning incident))

Excite group customer height loss early warning subject events

Else if ((the high-rise group customer contact of the B customer manager of the operator phone contact incident or B of operator incident) or (middle and high end client bundle loosening incident or middle and high end customer mobile phone terminal change planes early warning incident))

Excite group's examination moderate loss early warning subject events

Else excites the low loss early warning of group customer subject events

else

Excite the individual VIP early warning subject events that highly runs off

Excite individual VIP moderate loss early warning subject events

Else excites the low loss early warning of individual VIP subject events

Campaign management platform CMP subscribes to above-mentioned 5 personal client subject eventses to event center, and group's crm system is subscribed to above-mentioned 2 group customer subject eventses to event center; Then, event center is subscribed to primitive event according to the primitive event that rule relates to middle and high end customer churn Early-warning Model; Middle and high end customer churn Early-warning Model provides primitive event to event center; Event center carries out storage administration to these primitive events, then, carries out carrying out topicalization according to above-mentioned topicalization pattern; Then; After event center is made a strategic decision to 7 subject eventses, distribute subject events to CMP and group's crm system, do concrete marketing again by CMP and the CRM of group and carry out through the distribution control module.

In sum, the event center that present embodiment provides is through the pattern of middleware; Integrate relevant heterogeneous system; And the collection event data, and the primitive event of gathering is carried out topicalization handle, carry out distribution subscription then; Or the incident circulation, finally serve the third party system through processing protocol.The event center of present embodiment and event-handling method thereof adopt bus structures mode acquisition process incident through event center, finally form the decoupling zero of service interface; The tap/dip deep into of incident, the uniform service standard interface makes service logic become concentrated; Expansion that is easy to serve and maintenance; Accelerated the response speed of service, standardization service interface, improved quality and efficient.

The above only is an execution mode of the present invention; Should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; Can also make some improvement and retouching, these improvement and retouching also should be regarded as protection scope of the present invention.

Claims

1. an event center that supports the professional interlock of interdepartmental system is characterized in that, comprising:

2. event center as claimed in claim 1 is characterized in that, said acquisition module comprises:

3. event center as claimed in claim 1 is characterized in that, said topicalization module comprises processing unit and regulation engine unit;

Wherein, said processing unit specifically comprises:

4. event center as claimed in claim 1 is characterized in that,

5. event center as claimed in claim 1 is characterized in that, also comprises:

6. event center as claimed in claim 1 is characterized in that, also comprises:

7. the event-handling method of an event center is characterized in that, may further comprise the steps:

8. event-handling method as claimed in claim 7 is characterized in that,

9. event-handling method as claimed in claim 7 is characterized in that,

Said topicalization is handled and is comprised:

Excite processing, excite the new incident that obtains from a source event;

10. event-handling method as claimed in claim 7 is characterized in that,

11. event-handling method as claimed in claim 7 is characterized in that, also comprises:

12. event-handling method as claimed in claim 7 is characterized in that, also comprises: