CN102340495B - Event center supporting cross-system service linkage and event processing method of event center - Google Patents

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 interlock of cross-system business

Technical field

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

Background technology

In business when interlock of realizing cross-system, the interface that at present many is between employing system carries out point-to-point to fetching realization.Interface to realize technology multifarious, mainly comprise: socket (SOCKET) mode, HTML (Hypertext Markup Language) (HTTP, Hyper Text Transfer Protocol) mode and message queue (MQ, Message Queue) mode etc.Wherein, MQ mode is widely used in the Interface realization of business support system, 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.But, the interface of each system is all according to own situation formulation, the codes and standards of the interface of each system and to realize technology all different, therefore, in the time of the business interlock of supporting cross-system, business interlock is limited to the interface capability of each system, and because the processing logic of each system is tightly coupled, the flexibility of business interlock is very poor, along with the increase of business interlock demand, form gradually netted interconnectedly, form spider web predicament, follow-up maintenance difficulty.Event center (EC, Event Center) scheme different with point-to-point interface docking mode, employing is similar to service-oriented architectural framework (SOA, Service-Oriented Architecture) in ESB (ESB, Enterprise Service Bus) to the way to manage of serving. event center is based on event-driven framework (EDA, Event-Driven Architecture) realize, all systems are remained neutral, the same with ESB, adopt bus structures.

Cross-system business interlock support scheme of the prior art adopts interface to carry out point-to-point docking mode realization, has formed network structure, and there are the following problems for this scheme:

1, exchanges data and application call are point-to-point direct connections, and this close-coupled mode has caused netted interconnected between system, form spider web structure, are unfavorable for expansion and safeguard, are difficult to fast responding market demand, support the quick action in market.

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

3, there is no unified codes and standards, service logic is disperseed, and causes quality management and business monitoring to be realized very difficult, the management and control of service operation difficult quality.

Summary of the invention

Technical problem to be solved by this invention is to provide a kind of event center and event-handling method thereof that supports the interlock of cross-system business, adopt bus structures mode acquisition process event by event center, make service logic become concentrated, and service is easy to expansion and safeguard.

For solving the problems of the technologies described above, the invention provides scheme as follows:

An event center that supports the interlock of cross-system business, comprising:

Acquisition module, for obtaining the primitive event that the event acquisition device of each system of network reports and converting the standardization event with consolidation form to;

Topicalization module, for according to predefined topicalization pattern, carries out topicalization processing to the standardization event of acquisition module acquisition, obtains subject events;

Process decision-making module, for according to predefined event response setting, determine the response policy of subject events;

Distribution control module, for according to the response policy of subject events, distributes control to subject events.

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

Registering unit, for the event acquisition ability of registered events collector and event acquisition device;

Subscriber units, for the subscription application to subject events according to event response processor, determines the relevant primitive event that subject events is corresponding, and subscribes to described relevant primitive event to each event acquisition device corresponding to described relevant primitive event;

Acquisition gateway, be used for the primitive event that passive reception and described event center exist the event acquisition device active reporting of subscribing relationship, and according to the demand of topicalization processing, by active inquiry dependent event collector, obtain the primitive event that described dependent event collector reports; And the primitive event reporting based on each event acquisition device, generate the standardization event with consolidation form.

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

Wherein, described processing unit, specifically comprises:

Excitation mode unit, for exciting the new event that obtains from a source event;

Merging patterns unit, at least two source events are merged to processing, forms a new event;

Split mode unit, for a source event is carried out to deconsolidation process, forms at least two new events;

Filtered model unit, for source event is carried out to filtration treatment, filters out the event that does not need to carry out topicalization processing;

Heartbeat mode unit, when periodically do not inspire a new event at source event, produces one for the abnormal anomalous event of identification service situation, as, system status monitoring is the type event;

Assembled unit, for utilizing at least two unit of described excitation mode unit, merging patterns unit, split mode unit, filtered model unit and heartbeat mode unit, processes source event, obtains new event;

Described regulation engine unit, for according to the topicalization pattern for standardization event setting in advance, calls described processing unit standardization event is carried out to topicalization processing, obtains subject events.

Preferably, in above-mentioned event center,

Described processing decision-making module, be further used for according to foregone conclusion part response setting, event flow set and the setting of event response processor, determine the response policy of subject events, described response policy comprises the flow of event rotary-die type whether making an immediate response with described subject events, wherein, described flow of event rotary-die type comprises publish-subscribe model and directed routing pattern;

Described distribution control module, is further used for the flow of event rotary-die type according to described subject events, described subject events is distributed to corresponding event response processor and processes.

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

Event memory module, for according to service priority information, determines the rank of the standardization event of described acquisition module acquisition, and stores in the event storage queue with corresponding priority; And according to the event number in the priority of event storage queue and event storage queue, determine the quantity of distribution scheduling thread corresponding to event storage queue, described distribution scheduling thread carries out topicalization processing for standardization event to the described topicalization module of dispatching described event storage queue.

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

Event filing module, carries out filing management for subject events or response policy result after treatment after described response policy is rejected;

Quality management module, assesses management for the health degree of each system to associated with described event center;

Tracing and monitoring module, follows the tracks of for other module to described event center, the operating state of described other module of record.

The present invention also provides a kind of event-handling method of event center, comprises the following steps:

Obtain the primitive event that the event acquisition device of each system in network reports and convert the standardization event with consolidation form to;

According to predefined topicalization pattern, the standardization event that acquisition module is obtained is carried out topicalization processing, obtains subject events;

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

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

Preferably, in above-mentioned event-handling method,

Described obtain the primitive event that event acquisition device reports and convert the standardization event with consolidation form to before, also comprise: the event acquisition ability of registered events collector and event acquisition device; Subscription application according to event response processor to subject events, determines the relevant primitive event that subject events is corresponding, and subscribes to described relevant primitive event to each event acquisition device corresponding to described relevant primitive event;

Describedly obtain the primitive event that event acquisition device reports and convert the standardization event with consolidation form to, comprise: passive reception and described event center exist the primitive event of the event acquisition device active reporting of subscribing relationship, and according to the demand of topicalization processing, by active inquiry dependent event collector, obtain the primitive event that described dependent event collector reports; And the primitive event reporting based on each event acquisition device, generate the standardization event with consolidation form.

Preferably, in above-mentioned event-handling method,

Described topicalization processing comprises:

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

Merge and process, at least two source events are merged to processing, form a new event;

Deconsolidation process, carries out deconsolidation process by a source event, forms at least two new events;

Filtration treatment, carries out filtration treatment to source event, filters out the event that does not need to carry out topicalization processing;

Heartbeat processing, in the time that source event does not periodically inspire a new event, produces one for the abnormal anomalous event of identification service situation; And,

Combined treatment, for exciting processing described in utilizing, merging at least two kinds of processing modes that processing, deconsolidation process, filtration treatment and heartbeat are processed, processes source event, obtains new event.

Preferably, in above-mentioned event-handling method,

Described according to predefined event response setting, determine the response policy of subject events, comprise: arrange according to foregone conclusion part response setting, event flow set and event response processor, determine the response policy of subject events, described response policy comprises the flow of event rotary-die type whether making an immediate response with described subject events, wherein, described flow of event rotary-die type comprises publish-subscribe model and directed routing pattern;

Described according to the response policy of subject events, subject events is distributed to control, comprising: according to the flow of event rotary-die type of described subject events, described subject events is distributed to corresponding event response processor and processes.

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

Obtain the primitive event that event acquisition device reports and convert to after the standardization event with consolidation form described, further according to service priority information, determine the rank of the standardization event of described acquisition module acquisition, and store in the event storage queue with corresponding priority; And according to the event number in the priority of event storage queue and event storage queue, determine the quantity of distribution scheduling thread corresponding to event storage queue, described distribution scheduling thread carries out topicalization processing for the standardization event of dispatching described event storage queue.

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

Subject events or response policy result after treatment after described response policy is rejected are carried out filing management;

The health degree of each system associated with described event center is assessed to management; And

Other module in described event center is followed the tracks of to the operating state of described other module of record.

Can find out from the above, a kind of event center and event-handling method thereof that supports the interlock of cross-system business provided by the invention, by the pattern of middleware, integrate relevant heterogeneous system, and collection event data, and the primitive event gathering is carried out to topicalization processing, then carry out distribution subscription, or event circulation, finally serve third party's system by processing protocol.The event center of the present embodiment and event-handling method thereof, adopt bus structures mode acquisition process event by event center, the final decoupling zero that forms service interface, the degree of depth of event is excavated, and uniform service standard interface, makes service logic become concentrated, be easy to expansion and the maintenance of service, accelerated the response speed of service, standardization service interface, improved quality and efficiency.And what event center adopted is bus structures, is independent of each system, it is loose coupling structure, exploitation and setting that the business interlock of cross-system only need to be correlated with in event center in the time that business demand changes, also only need to be revised and arrange and exploitation within the scope of event center.

Brief description of the drawings

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

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

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

Fig. 4 is the general function framework schematic diagram of the event center described in the embodiment of the present invention;

Fig. 5 is the parameter schematic diagram of embodiment of the present invention Plays event;

Fig. 6 is the schematic diagram of publish-subscribe model in the embodiment of the present invention;

Fig. 7 is the schematic diagram of directed routing pattern in the embodiment of the present invention;

Fig. 8 is the collecting flowchart schematic diagram of the acquisition module of event center described in the embodiment of the present invention;

Fig. 9 is the Stored Procedure schematic diagram of the event memory module of event center described in the embodiment of the present invention;

Figure 10 is the schematic diagram of embodiment of the present invention thread distribution scheduling;

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

Figure 12 is the schematic diagram of processing the processing decision-making of decision-making module described in the embodiment of the present invention;

Figure 13 is the schematic diagram that in the embodiment of the present invention, subject events distribution is controlled.

Embodiment

The invention provides a kind of event center and event-handling method thereof that supports the interlock of cross-system business, by the event acquisition device of each system in network to event center reported event, event center is concentrated event is carried out to acquisition and processing, make service logic become concentrated, service is easy to expansion and safeguards, and accelerated the response speed of service, standardization service interface, improved quality and efficiency.Below with reference to accompanying drawing, by specific embodiment, the present invention is described further.

First, please refer to Fig. 1, the event center 10 described in the embodiment of the present invention comprises:

Acquisition module, for obtaining the primitive event that the event acquisition device of each system of network reports and converting the standardization event with consolidation form to;

Topicalization module, for according to predefined topicalization pattern, carries out topicalization processing to the standardization event of acquisition module acquisition, obtains subject events;

Process decision-making module, for according to predefined event response setting, determine the response policy of subject events;

Distribution control module, for according to the response policy of subject events, distributes control to subject events.

The present embodiment also correspondingly provides a kind of event-handling method, is applied to the event center shown in Fig. 1, and as shown in Figure 2, this event-handling method comprises the following steps:

Step 21, obtains the primitive event that the event acquisition device of each system in network reports and converts the standardization event with consolidation form to;

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

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

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

In above-mentioned steps 22, described topicalization mode-definition the topicalization processing procedure of standardization event, described topicalization is processed and is specifically comprised:

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

Merge and process, at least two source events are merged to processing, form a new event;

Deconsolidation process, carries out deconsolidation process by a source event, forms at least two new events;

Filtration treatment, carries out filtration treatment to source event, filters out the event that does not need to carry out topicalization processing;

Heartbeat processing, in the time that source event does not periodically inspire a new event, produces one for the abnormal anomalous event of identification service situation; And,

Combined treatment, for exciting processing described in utilizing, merging at least two kinds of processing modes that processing, deconsolidation process, filtration treatment and heartbeat are processed, processes source event, obtains new event.

Can find out from the above, because prior art is in the time having the demand of cross-system business interlock, just need between each system, carry out point-to-point development interface.And because this point-to-point interface is tightly coupled, that is to say if interlock demand changes, just need development interface again, so prior art can cause intersystem interface increasingly sophisticated, form spider net type structure.Bus structures (focus on event that the event acquisition device of each system reports also) and the event center that the present embodiment provides adopts, be independent of each system, between itself and other system, it is loose coupling structure, therefore the interlock of the business of cross-system only need to be correlated with in event center exploitation and setting, in the time that business demand changes, also only need within the scope of event center, revise and arrange and exploitation, thereby make service logic become concentrated, be easy to expansion and the maintenance of service, accelerate the response speed of service, standardization service interface, quality and efficiency are improved.

To further each step of above-mentioned event center and each functional module and event-handling method be done to more detailed explanation below.

(1) event center overall introduction

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

In Fig. 3, RE represents primitive event (Raw Event), and TE represents subject events (Topic Event), and RC represents that response calls (Response Callback).As can be seen from Figure 3, event center receives the primitive event that the event acquisition device of each system reports, the model analysis class event that for example event acquisition device of province/city mining model system reports, work order/order event that the event acquisition device of market/number industry/group system reports, the client that the event acquisition device of one line customer service system reports contacts event, net maintains the cell monitoring event that the event acquisition device of system reports, and the system monitoring event that the event acquisition device of ITC system reports is waited for.Event center carries out format conversion to these primitive events, generates the standardization event (certainly, if the primitive event that event acquisition device reports is exactly standardization event, without carrying out format conversion) of consolidation form; Then standardization event is carried out to topicalization processing, obtain subject events; Again according to the alert response strategy of subject events, subject events is distributed to control, by ESB, subject events is distributed to corresponding event consumer (event response processor), the event response processor in core processing engine, core response service system, peripheral response service system and key business analytical system as shown in Figure 3.

In the present embodiment, event refers to the variation of client's (inside and outside) state, and the variation of customer status is the external manifestation that client's business demand changes, that is, event is to be used to indicate the data that client's business demand changes.The present embodiment, on the basis of event center, can be realized the marketing of taking the initiative in offering a hand based on event, customer insight and the channel interaction based on event, realizes and runs integrated and service marketing automation.

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

The primitive event that in the present embodiment, event center reports the event acquisition device of each system in network carries out format conversion, generate the standardization event of consolidation form, the definition of a kind of standardization event in the present embodiment is below described, it should be noted that, the concrete form of below introducing is not construed as limiting 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 event that the present embodiment provides

In the present embodiment, the description of standardization event, mainly follows " 5W+1R " principle, specifically as shown in Figure 5.Can find out, the standardization event of consolidation form comprises at least one of following six kinds of parameters:

The information of the object that 1, event reflects, in Fig. 5 wclient's phone number, system or the module number etc. of definition in mono-of ho;

2, the source-information of event, in Fig. 5 wevent origin system numbering, the terminal iidentification etc. of definition in mono-of here;

3, the temporal information of event, in Fig. 5 wthe Time To Event of definition, effective time, processing time etc. in mono-of hen;

4, the type information of event, in Fig. 5 wthe event type coding of definition, scene coding, spreading parameter etc. in mono-of hat;

5, the personalization attributes information of event, as ho in Fig. 5 wthe make of the event of definition, urgency level, level of security, significance level, shock grades, external command, circulation pattern identification etc. in one;

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

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

1, this event is had and be there is no special requirement (as priority, significance level, risk etc.), whether need to provide attachment data for reference or process;

2, whom this event should give and go to process (what place, who, must complete in how long);

Which task does 3, carrying out this time mainly complete?

4, the result of event how, when processes, and is to process overtime needs, or processes unsuccessfully.

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

<FML>

< event >

<WHO>

< client's phone number ></ client phone number >

< system numbering ></ system numbering >

< module numbering ></ module numbering >

</WHO>

<WHERE>

< carrys out origin system numbering ></ source system coding >

< terminal iidentification ></ terminal iidentification >

</WHERE>

<WHEN>

< Time To Event ></ Time To Event >

< event ></ effective time event > effective time

< event handling time ></ event handling time >

</WHEN>

<WHAT>

< type of service numbering ></ type of service coding >

< spreading parameter ></ spreading parameter >

</WHAT>

<HOW>

< make ></ make >

< urgency level ></ urgency level >

< level of security ></ level of security >

< significance level ></ significance level >

< shock grades ></ shock grades >

< external command ></ external command >

< flow of event rotary-die type ></ flow of event rotary-die type >

</HOW>

<RESULT>

< state-event ></ state-event >

< result is described ></ result and is described >

</RESULT>

</ event >

</FML>

(3) flow of event rotary-die type

In the present embodiment, flow of event rotary-die type comprises publish-subscribe model and directed routing pattern.Described processing decision-making module in Fig. 1, be further used for according to foregone conclusion part response setting, event flow set and the processing response setting of event response processor to event, determine the response policy of subject events, described response policy comprises the flow of event rotary-die type of described subject events; Described distribution control module, is further used for the flow of event rotary-die type according to described subject events, described subject events is distributed to corresponding event response processor and processes.Below introduce this two kinds of flow of event rotary-die types.

1, publish-subscribe model

Publish-subscribe model is the subscriber that event center is sent to subject events this subject events.

As shown in Figure 6, the event acquisition device in system A is registered primitive event to event center to the schematic diagram of publish-subscribe model, and event center carries out this primitive event to be published to after topicalization the consumer of each event, in the event response processor in system B; In the time that system B need to obtain certain subject events, just subscribe to event center; The event acquisition device of the primitive event that then, event center relates to this subject events is subscribed to; Then, the event acquisition device in system A reports primitive event to event center, and event center carries out obtaining after subject events after format conversion and topicalization processing, to the subscriber of this subject events, as system B, sends this subject events; System B carries out event response processing according to the handling process of oneself after taking subject events, and result is fed back to event center.The flow process of event subscription pattern that Here it is.

2, directed routing pattern

The schematic diagram of directed routing pattern as shown in Figure 7.

Directed routing pattern, is in carrying out event acquisition, the event response processor that just orientation has specified primitive event will give after event center is processed.Such system A just can, according to the needs of oneself, by system B, its intrasystem primitive event is processed, and event center just play the effect of a directed routing therein.

(4) event center functional module describes in detail

1. event acquisition function

The described acquisition module of event acquisition function event center is as shown in Figure 1 realized, be the function of setting at event center in order to collect various primitive events, its function comprises event registration management, event subscription management, event routing management, event acquisition service etc.

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

Figure 8 shows that the collecting flowchart schematic diagram of the acquisition module in the event center shown in Fig. 1.As shown in Figure 8, described acquisition module specifically comprises:

Registering unit, for the event acquisition ability of registered events collector and event acquisition device.

Registration comprises collector registration and event registration.Collector registration is that the collector of each system will provide before event acquisition service to event center, must register to the collector registration center of event center, the content of registration mainly comprises: the 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 event acquisition device is, need to carry out to the event registration center of event center the registration of certain primitive event acquisition capacity, the content of registration mainly comprises: event identifier, collector label, event type, state-event, time, event description, founder, creation-time, approval status, approver, examination & approval time, remarks, only have the registration of initiation, and event acquisition ability by examination & approval could should primitive event to event center confession.

Subscriber units, for the subscription application to subject events according to event response processor, determines the relevant primitive event that subject events is corresponding, and subscribes to described relevant primitive event to each event acquisition device corresponding to described relevant primitive event.

Event subscription mainly refer to event center receive subject events consumer initiate subscription application after, the primitive event that this subject events relates to needs event center to subscribe to each corresponding event acquisition device, and the content of subscription comprises: subscriber, event identifier, ageing, subscription status, state time, founder, collector numbering.Event acquisition device just can be supplied subscribed primitive event to event center after only receiving the subscription instruction of event center, and other the subscribed primitive event that do not have does not need to gathering.

Acquisition gateway, be used for the primitive event that passive reception and described event center exist the event acquisition device active reporting of subscribing relationship, and according to the demand of topicalization processing, by active inquiry dependent event collector, obtain the primitive event that described dependent event collector reports; And the primitive event reporting based on each event acquisition device, generate the standardization event with consolidation form.

Described acquisition module also comprises various interface, agent unit, service interface and event route (up, downstream routing) unit.

The pattern of event acquisition is divided into following a few class:

Initiatively report: when after event center and the built-in event acquisition device generation subscribing relationship of event source, the acquisition gateway of event center initiatively reported data by the built-in event acquisition device of event source, acquisition gateway carries out passive event collection work, and collecting result feedback to event source.

Acknowledgment of your inquiry: no matter whether event center and the built-in event acquisition device of event source subscribing relationship occurs, event center is processed and is needed because of topicalization, initiatively initiate inquiry to the built-in event acquisition device of event source by acquisition gateway, whether inquiry there is the event satisfying condition, and the built-in event acquisition device of event source according to circumstances feedback event data arrives acquisition gateway.

Agency reports: when after the event acquisition device generation subscribing relationship of event center and event source external (by plug-in monitoring), the acquisition gateway of event center initiatively reported data by the external event acquisition device of event source, acquisition gateway carries out passive event collection work, and collecting result feedback to event source.

Agents query: no matter whether event center and the external event acquisition device of event source subscribing relationship occurs, event center is processed and is needed because of topicalization, initiatively initiate inquiry to the external event acquisition device of event source by acquisition gateway, whether inquiry there is the event satisfying condition, and the external event acquisition device 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 the present embodiment standardization event adopts).If the primitive event that event acquisition device reports be utilize below the 1.～3. acquisition protocols is described, acquisition gateway need to be resolved the row format conversion of going forward side by side of this primitive event, obtains the standardization event of consolidation form.Below these several agreements are described.

1. CBossIntPkg acquisition protocols

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

Medical record:

Resolve CBossIntPkg packet, according to following correspondence setting in standardization event object.

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

Char strIntCmd[ID_LEN+1]; + char strIntSubCmd-> primitive event mark (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 class event is 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, event title, client's phone number, Event origin system banner, terminal iidentification, trigger event, Time To Event, event out-of-service time (optional), additional parameter etc.

What event acquisition device was inputted 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.

Medical record: analyzing XML packet, is set to related data the respective attributes of standardization event object.

3. Character segmentation combination protocol

Between each attribute, use special character to cut apart, and form a new character string, process as input parameter.

What event acquisition device was inputted 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.

Medical record: resolve combining characters string, decomposite all must event attribute (identical with above-mentioned agreement), and be set in the respective attributes of standardization event object.

4. Standard File Format collection

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

Be mainly used in carrying out when event queue is overflowed or database is abnormal file backup, and then carry out data reduction.

2. event memory function

Run in integrated event center, event data, after the processing of initial registration subscription, route, finally can obtain a large amount of client's event datas.For these a large amount of event datas are reasonably managed, in event center shown in Fig. 1, also comprise an event memory module, be used for according to service priority information, determine the rank of the standardization event of described acquisition module acquisition, and store in the event storage queue with corresponding priority; And according to the event number in the priority of event storage queue and event storage queue, determine the quantity of distribution scheduling thread corresponding to event storage queue, described distribution scheduling thread carries out topicalization processing for standardization event to the described topicalization module of dispatching described event storage queue.

This event memory module has facilitated the management of event data on the one hand, on the other hand for event center provides initial primitive event storehouse.Figure 9 shows that the Stored Procedure schematic diagram of this event memory module, this event memory module is pressed the information such as service priority, and event storage queue is carried out to classification processing, and concrete priority is described below:

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

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

3) high power capacity queue: the third level priority level of weighing event handling from the number of overall event source data.

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

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

The standardization event of different priorities is stored in corresponding event storage queue, then carry out classification according to the event number of storing in event storage queue, decide the thread distribution scheduling processing event storage of enabling different stage, and by different threads distribution scheduling, event is carried out to topicalization processing.Figure 10 has provided the schematic diagram of a thread distribution scheduling 100, can find out, event number is more, also more for the Thread Count of distribution scheduling.In following table, also show a kind ofly according to the priority of event capacity levels in event storage queue and event storage queue, decide the concrete example of thread distribution number.

Event capacity levels

Capacity number

Priority

Thread distribution number (can arrange)

Remarks

Senior	80％～99％	Excellent	More than 3000
					Middle rank	50％-80％	Good	2000-3000
Rudimentary	1％-50％	Poor	1000-2000

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

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

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

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

Storage queue structure can be taked sequential storage structure, and storage of linked list structure, the form storage for the event queue of often inserting, deleting with chained list, and for just order insertion, and the event queue that delete at end is taked storage organization sequentially.

The queue structure of sequential storage:

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

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

Chained list queue structure specifically comprises single-track link table, doubly linked list and circular linked list, does not repeat them here.

3. event topic function

Event topic is the core of event center, the described topicalization module of event center as shown in Figure 1 realizes, its function is simply interpreted as carries out the topicalization processing of closed loop to the standardization event data collecting at collection center, forms new subject events storehouse.

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

Excitation mode unit, for exciting the new event that obtains from a source event;

Merging patterns unit, at least two source events are merged to processing, forms a new event;

Split mode unit, for a source event is carried out to deconsolidation process, forms at least two new events;

Filtered model unit, for source event is carried out to filtration treatment, filters out the event that does not need to carry out topicalization processing;

Heartbeat mode unit, when periodically do not inspire a new event at source event, produces one for the abnormal anomalous event of identification service situation, as, system status monitoring is the type event;

Assembled unit, for utilizing at least two unit of described excitation mode unit, merging patterns unit, split mode unit, filtered model unit and heartbeat mode unit, processes source event, obtains new event.

Here above-mentioned source event can be standardization event, can be also the intermediate event obtaining after above-mentioned topicalization resume module, can also be subject events.Above-mentioned new event, can be subject events, can be also the intermediate event obtaining after above-mentioned topicalization resume module.

Described regulation engine unit, for according to the topicalization pattern for standardization event setting in advance, calls described processing unit standardization event is carried out to topicalization processing, obtains subject events.In topicalization pattern, define the topicalization processing procedure of standardization event, defined the concrete unit of described processing unit for processing standardization event, and the sequencing of processing.

4. process decision making function

Processing the described processing decision-making module of decision making function event center as shown in Figure 1 realizes, that basis is taking the subject events in subject events storehouse as basis, according to predefined event response setting, determine the response policy of subject events, form event response task library.

Figure 12 shows the flow process of the processing decision-making of processing decision-making module, wherein processes first region of decision-making module for subject events is carried out to Analysis of Policy Making, and judgement is wanted to process; Second region is how subject events is processed and carried out policy selection.

First the process of the Analysis of Policy Making of decision-making module is processed in explanation:

Process in decision-making module and set in advance multiple decision condition, as

One, event response setting

Event response arrange, for the response policy of subject events is set, and can carry out switch setting, comprise following some:

1) arrange without coupling, for arranging whether subject events is carried out to matching treatment, for the subject events without matching treatment, will be distributed to corresponding event respective processor and process; For the subject events of wanting matching treatment, can carry out inter-process by processing decision-making module.

2) whether whether all events close setting, for arranging to the processing of all subject events shut down decisions;

3) whether event category closes response setting, whether needs decision-making treatment for the subject events that some classification is set;

4) whether event closes response setting, whether needs decision-making treatment for some subject events is set;

Two, event flow set

Event flow set is system to be processed to the monitoring setting of event flow, comprises the setting of the following aspects:

1) whether control flow, for the overall flow that whether needs to control event center is set;

2) event type flow, for arranging the flow of subject events of some type;

3) event flow, for arranging the flow of subject events;

4) whether exceed flow, for flow restriction is set, as day, hour flow;

5) all service traffics, for arranging the flow of all business;

Three, event response processor arranges

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

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

2, this own health status of event center platform;

Then the process of the policy selection of decision-making module is processed in explanation.

One, response policy is the strategy setting of the processing mode to event, comprises following aspect:

1) event response strategy, for arranging the event response strategy of subject events;

2) ignore, for arranging, subject events is ignored to response;

3) wait-for-response, for arrange subject events is waited for a period of time after response;

4) response at once, responds subject events immediately for arranging

Two, priority evaluation

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

1) execution priority is not set, and determines to carry out the priority level of response.

Described processing decision-making module in Fig. 1, can be further used for according to foregone conclusion part response setting, event flow set and the setting of event response processor, determine the response policy of subject events, described response policy comprises the flow of event rotary-die type whether making an immediate response with described subject events, wherein, described flow of event rotary-die type comprises publish-subscribe model and directed routing pattern.Whether described response policy comprises the theme time is responded, and carry out the time of response.

5, function is controlled in distribution

The described distribution control module that function event center is as shown in Figure 1 controlled in distribution realizes, according to the flow of event rotary-die type (comprising distribution subscription and directed routing pattern) of the subject events of processing decision-making module generation, subject events is distributed to control, be distributed to corresponding event response processor and process.Wherein, publish-subscribe model be event response processor according to the demand of self, subscribe to processing the subject events of issuing in decision-making, be distributed to the subscriber of this subject events by event center.And directed routing pattern is that subject events is carried out to route distribution, give the event response processor of appointment.

It is the handling process of carrying out decision-making that distribution is controlled, and Figure 13 shows this flow process.

It is the core of event center that distribution is controlled, and mainly adopts four kinds of processing protocol, as follows:

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

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

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

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

6. event filing function

Event center shown in Fig. 1 can also comprise event filing module, carries out filing management for subject events or response policy result after treatment after described response policy is rejected.The content of filing comprises archival configuration, and event handling list, filing are processed, filing audit.

7. quality management module

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

In quality management, first to assess the working order of each system, the system health degree assessment management namely here proposing, here will not pay 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 is wherein that the weight of occupying in system according to different parts and the marking rule of self are carried out, specific as follows:

(2) evaluation rank

The health degree score that is drawn system by the score value of above-mentioned three weight parameter and self, can be divided into following seven ranks, as following table:

(3) rank control

To the system classification processing of giving a mark, be next to how dispatch deal of each rank according to above, see the following form in detail:

In upper table, flow adjustment is to be described according to adjusting the amount of falling, as to adjust 0 meaning be exactly not adjust, and 20% is exactly that total flow reduction by 20%, 100% is reduced to 100% by total flow exactly, namely stops.

8, tracing and monitoring module

Event center shown in Fig. 1 can also comprise tracing and monitoring module, follows the tracks of the operating state of described other module of record for other module to described event center.

In the running of the integrated event center system of operation, comprising various event acquisitions, event handling, arranging service, the processing procedure of service call etc., the present embodiment carrys out acquisition system working order in carrying out each step processing by tracing and monitoring module.

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

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.

Finally, understand the present embodiment in order further to help, by a concrete application example, event center and event-handling method thereof to the present embodiment are illustrated.

Business description:

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

First all primitive event registrations that, customer churn Early-warning Model in middle and high end need to be carried out event supplier registration and can provide to event center.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 to be to event center registered customers identity.Then, need to use event center topicalization module, above-mentioned primitive event is carried out to topicalization, topicalization rule need to be at regulation engine, for example ILOG, middle some row topicalization rules that arrange.According to business demand, following topicalization pattern need to be set:

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

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

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

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

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 event or B of operator event) and (middle and high end client bundle loosening event or middle and high end customer mobile phone terminal change planes early warning event))

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 event or B of operator event) or (middle and high end client bundle loosening event or middle and high end customer mobile phone terminal change planes early warning event))

Excite group's examination moderate loss early warning subject events

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

else

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

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

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

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 individual client's subject eventses to event center, and group's crm system is subscribed to above-mentioned 2 group customer subject eventses to event center; Then the primitive event that, event center relates to according to rule is subscribed to primitive event 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, carry out carrying out topicalization according to above-mentioned topicalization pattern, then, event center carries out after decision-making 7 subject eventses, distributes subject events by distribution control module to CMP and group's crm system, does concrete marketing again carry out by CMP and the CRM of group.

In sum, the event center that the present embodiment provides, by the pattern of middleware, integrate relevant heterogeneous system, and collection event data, and the primitive event gathering is carried out to topicalization processing, then carry out distribution subscription, or event circulation, finally serve third party's system by processing protocol.The event center of the present embodiment and event-handling method thereof, adopt bus structures mode acquisition process event by event center, the final decoupling zero that forms service interface, the degree of depth of event is excavated, and uniform service standard interface, makes service logic become concentrated, be easy to expansion and the maintenance of service, accelerated the response speed of service, standardization service interface, improved quality and efficiency.

The above is only embodiments of the present invention; it should be pointed out that for those skilled in the art, under the premise without departing from the principles of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.

Claims (10)

1. an event center that supports the interlock of cross-system business, is characterized in that, comprising:

Acquisition module, for obtaining the primitive event that the event acquisition device of each system of network reports and converting the standardization event with consolidation form to;

Topicalization module, for according to predefined topicalization pattern, carries out topicalization processing to the standardization event of acquisition module acquisition, obtains subject events;

Process decision-making module, be used for according to predefined event response setting, determine the response policy of subject events, comprise: arrange according to foregone conclusion part response setting, event flow set and event response processor, determine the response policy of subject events, described response policy comprises the flow of event rotary-die type whether making an immediate response with described subject events, and wherein, described flow of event rotary-die type comprises publish-subscribe model and directed routing pattern;

Distribution control module, for according to the response policy of subject events, distributes control to subject events, comprising: according to the flow of event rotary-die type of described subject events, described subject events is distributed to corresponding event response processor and processes.

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

Registering unit, for the event acquisition ability of registered events collector and event acquisition device;

Subscriber units, for the subscription application to subject events according to event response processor, determines the relevant primitive event that subject events is corresponding, and subscribes to described relevant primitive event to each event acquisition device corresponding to described relevant primitive event;

Acquisition gateway, be used for the primitive event that passive reception and described event center exist the event acquisition device active reporting of subscribing relationship, and according to the demand of topicalization processing, by active inquiry dependent event collector, obtain the primitive event that described dependent event collector reports; And the primitive event reporting based on each event acquisition device, generate the standardization event with consolidation form.

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

Wherein, described processing unit, specifically comprises:

Excitation mode unit, for exciting the new event that obtains from a source event;

Merging patterns unit, at least two source events are merged to processing, forms a new event;

Split mode unit, for a source event is carried out to deconsolidation process, forms at least two new events;

Filtered model unit, for source event is carried out to filtration treatment, filters out the event that does not need to carry out topicalization processing;

Heartbeat mode unit, when periodically do not inspire a new event at source event, produces one for the abnormal anomalous event of identification service situation;

Assembled unit, for utilizing at least two unit of described excitation mode unit, merging patterns unit, split mode unit, filtered model unit and heartbeat mode unit, processes source event, obtains new event;

Described regulation engine unit, for according to the topicalization pattern for standardization event setting in advance, calls described processing unit standardization event is carried out to topicalization processing, obtains subject events.

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

Event memory module, for according to service priority information, determines the rank of the standardization event of described acquisition module acquisition, and stores in the event storage queue with corresponding priority; And according to the event number in the priority of event storage queue and event storage queue, determine the quantity of distribution scheduling thread corresponding to event storage queue, described distribution scheduling thread carries out topicalization processing for standardization event to the described topicalization module of dispatching described event storage queue.

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

Event filing module, carries out filing management for subject events or response policy result after treatment after described response policy is rejected;

Quality management module, assesses management for the health degree of each system to associated with described event center;

Tracing and monitoring module, follows the tracks of for other module to described event center, the operating state of described other module of record.

6. an event-handling method for event center, is characterized in that, comprises the following steps:

Obtain the primitive event that the event acquisition device of each system in network reports and convert the standardization event with consolidation form to;

According to predefined topicalization pattern, the standardization event that acquisition module is obtained is carried out topicalization processing, obtains subject events;

According to predefined event response setting, determine the response policy of subject events, comprise: arrange according to foregone conclusion part response setting, event flow set and event response processor, determine the response policy of subject events, described response policy comprises the flow of event rotary-die type whether making an immediate response with described subject events, wherein, described flow of event rotary-die type comprises publish-subscribe model and directed routing pattern;

According to the response policy of subject events, subject events is distributed to control, comprising: according to the flow of event rotary-die type of described subject events, described subject events is distributed to corresponding event response processor and processes.

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

Described obtain the primitive event that event acquisition device reports and convert the standardization event with consolidation form to before, also comprise: the event acquisition ability of registered events collector and event acquisition device; Subscription application according to event response processor to subject events, determines the relevant primitive event that subject events is corresponding, and subscribes to described relevant primitive event to each event acquisition device corresponding to described relevant primitive event;

Describedly obtain the primitive event that event acquisition device reports and convert the standardization event with consolidation form to, comprise: passive reception and described event center exist the primitive event of the event acquisition device active reporting of subscribing relationship, and according to the demand of topicalization processing, by active inquiry dependent event collector, obtain the primitive event that described dependent event collector reports; And the primitive event reporting based on each event acquisition device, generate the standardization event with consolidation form.

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

Described topicalization processing comprises:

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

Merge and process, at least two source events are merged to processing, form a new event;

Deconsolidation process, carries out deconsolidation process by a source event, forms at least two new events;

Filtration treatment, carries out filtration treatment to source event, filters out the event that does not need to carry out topicalization processing;

Heartbeat processing, in the time that source event does not periodically inspire a new event, produces one for the abnormal anomalous event of identification service situation; And,

Combined treatment, for exciting processing described in utilizing, merging at least two kinds of processing modes that processing, deconsolidation process, filtration treatment and heartbeat are processed, processes source event, obtains new event.

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

Obtain the primitive event that event acquisition device reports and convert to after the standardization event with consolidation form described, further according to service priority information, determine the rank of the standardization event of described acquisition module acquisition, and store in the event storage queue with corresponding priority; And according to the event number in the priority of event storage queue and event storage queue, determine the quantity of distribution scheduling thread corresponding to event storage queue, described distribution scheduling thread carries out topicalization processing for the standardization event of dispatching described event storage queue.

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

Subject events or response policy result after treatment after described response policy is rejected are carried out filing management;

The health degree of each system associated with described event center is assessed to management; And

Other module in described event center is followed the tracks of to the operating state of described other module of record.