CN106921619A - A kind of correlating event processing method and processing device - Google Patents
A kind of correlating event processing method and processing device Download PDFInfo
- Publication number
- CN106921619A CN106921619A CN201510993292.8A CN201510993292A CN106921619A CN 106921619 A CN106921619 A CN 106921619A CN 201510993292 A CN201510993292 A CN 201510993292A CN 106921619 A CN106921619 A CN 106921619A
- Authority
- CN
- China
- Prior art keywords
- event
- mark
- elementary
- revocation
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012545 processing Methods 0.000 title claims abstract description 36
- 238000003672 processing method Methods 0.000 title claims abstract description 12
- 238000000034 method Methods 0.000 claims description 50
- 230000000875 corresponding effect Effects 0.000 description 32
- 230000008569 process Effects 0.000 description 30
- 230000000694 effects Effects 0.000 description 11
- 230000006378 damage Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000013589 supplement Substances 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000032683 aging Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000008713 feedback mechanism Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000035882 stress Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
Abstract
This application discloses a kind of correlating event processing method and processing device.A kind of correlating event processing method includes：Receive treatment request message of the event request side for object event；Judge whether to have received the corresponding event handling request message of group mark；If not receiving the corresponding event handling request message of group mark, in the case where object event is revocation event, the processing failure message of object event is not directed to event request side feedback；If having received the corresponding event handling request message of group mark, the corresponding elementary event of treated group mark is further determined whether, if untreated and object event is elementary event, the not treatment operation of performance objective event.Using such scheme, correct treatment can be made in the case where message is out of order and event request side is fed back in time, it is to avoid the various problems caused by message retransmission.
Description
Technical field
The application is related to net application technology field, more particularly to a kind of correlating event processing method and processing device.
Background technology
The development of network technology, not only realizes the resource-sharing between equipment, also causes the association between equipment
Become easier to realize.In Internet era, as long as an equipment possesses linking Internet function, with regard to energy
It is enough easily to be communicated with the arbitrary equipment for accessing internet, further realize various collaboration features.
Any form of equipment cooperation, is required for being completed based on interacting message, under application scenes, disappears
Breath interaction has certain sequence requirement, if processed without requirement in sequence, it is possible to cause system
Run-time error.
For example, there is message A and message B, message B is used to ask to perform certain event, and message B is used for please
Ask and cancel the event, from the angle of sender, treatment logic is first to send message A to retransmit message B naturally.
Under normal circumstances, recipient should also be processed according to the order reception message of B after first A and successively, however,
The uncertainty of intermediate communication link but result in the objective reality of message disorder phenomenon.According to prior art
Processing mode, if recipient have received corresponding revocation request before elementary event request is received,
Revocation event can be caused because elementary event does not exist first cannot be performed, and then also result in elementary event
It is normal to perform without revocation, cause expectation function normally to realize.Although in some cases can be with profit
Pointed out with error feedback mechanism sender retransmit request, but retransmit operation not only result in device resource and
The waste of Internet resources, also increased extra operation and the stand-by period to user.In fact, at some
It is ageing to require application scenarios higher, even if retransmitting request also cannot may in time play corresponding effect.
The content of the invention
For above-mentioned technical problem, the application provides a kind of correlating event processing method and processing device, is disappeared with reducing
Various problems caused by breath retransmission mechanism, technical scheme is as follows：
According to the first aspect of the application, there is provided a kind of correlating event processing method, event handling side is applied to,
The elementary event that is mutually related and its revocation event share same event group mark, and the method includes：
Treatment request message of the event request side for object event is received, the object event includes basic thing
Part or revocation event；
Group mark according to the object event, judges whether to have received at the corresponding event of described group of mark
Reason request message；
If not receiving the corresponding event handling request message of described group of mark, it is in the object event
In the case of elementary event, the treatment operation of the object event is performed；It is revocation thing in the object event
In the case of part, the processing failure message of the object event is not directed to event request side feedback；
If having received the corresponding event handling request message of described group of mark, place is further determined whether
The corresponding elementary event of described group of mark was managed, if processed and described object event is revocation event,
Then perform the treatment operation of the object event；If untreated and described object event is elementary event,
The treatment operation of the object event is not performed then.
According to the second aspect of the application, there is provided a kind of correlating event processing unit, event handling side is applied to,
The elementary event that is mutually related and its revocation event share same event group mark, and the device includes：
Message reception module, it is described for receiving treatment request message of the event request side for object event
Object event includes elementary event or revocation event；
First judge module, for being identified according to the group of the object event, judges whether to have received described
The corresponding event handling request message of group mark；
Second judge module, for judging whether the corresponding elementary event of treated described group of mark；
3rd judge module, the type for judging the object event；
First performing module, for do not received the corresponding event handling request message of described group of mark and
In the case that the object event is elementary event, the treatment operation of the object event is performed；
Second performing module, for do not received the corresponding event handling request message of described group of mark and
In the case that the object event is revocation event, not to event request side feedback for the object event
Processing failure message；
3rd performing module, for receiving the corresponding event handling request message of described group of mark,
Treat the described group of corresponding elementary event of mark and the object event is in the case of revocation event, to hold
The treatment operation of the row object event；
4th performing module, for receiving the corresponding event handling request message of described group of mark, not
Treat in the case that the described group of corresponding elementary event of mark and the object event be elementary event, no
Perform the treatment operation of the object event.
The technical scheme that the embodiment of the present application is provided, for elementary event and its revocation event of being mutually related
Same event group mark is shared, after event handling side joint receives request message, is according to a group mark judgement first
No other event requests for once receiving the group, then in conjunction with the event type for having received and current thing
Part type judges whether disorder phenomenon occur, and it is simultaneously timely that correct treatment is made in the case where appearance is out of order
Feed back to event request side, it is to avoid the various problems caused by message retransmission.
It should be appreciated that the general description of the above and detailed description hereinafter are only exemplary and explanatory,
The application can not be limited.
Brief description of the drawings
In order to illustrate more clearly of the embodiment of the present application or technical scheme of the prior art, below will be to implementing
Example or the accompanying drawing to be used needed for description of the prior art are briefly described, it should be apparent that, describe below
In accompanying drawing be only some embodiments described in the application, for those of ordinary skill in the art,
Other accompanying drawings can also be obtained according to these accompanying drawings.
Fig. 1 is the structural representation of the correlating event processing system of the application；
Fig. 2 is the first schematic flow sheet of the correlating event processing method of the application；
Fig. 3 is second schematic flow sheet of the correlating event processing method of the application；
Fig. 4 is the first structural representation of the correlating event processing unit of the application；
Fig. 5 is second structural representation of the correlating event processing unit of the application.
Specific embodiment
In order that those skilled in the art more fully understand the technical scheme in the application, below in conjunction with this Shen
Accompanying drawing that please be in embodiment, is described in detail, it is clear that institute to the technical scheme in the embodiment of the present application
The embodiment of description is only some embodiments of the present application, rather than whole embodiments.Based on the application
In embodiment, the every other embodiment that those of ordinary skill in the art are obtained should all belong to this Shen
The scope that please be protect.
Application scheme is used to process the correlating event with dependence, it is assumed that there are event X and event Y,
The wherein effect of Y is the implementing result for cancelling X, and treatment is seen in logic, and the execution of Y is needed with the execution of X
Premised on, then event X and event Y constitutes one group of correlating event.For example, event X be certain information of issue,
Event Y to recall above- mentioned information, event X be certain account is withholdd, event Y for recall it is above-mentioned withhold,
Etc..For convenience of description, in this application, the X in same group of correlating event is referred to as elementary event, Y
Referred to as cancel event.
The operation framework of application scheme is illustrated as shown in figure 1, at including event request side apparatus 10 and event
Reason side apparatus 20.Wherein event request side apparatus 10 are the request initiator of elementary event and revocation event, thing
Part treatment side apparatus 20 are the actual execution sides of elementary event and revocation event, and two side apparatus can be by various shapes
The real-time performance communication connection of formula, request side apparatus 10 indicate treatment side by sending event handling request message
Equipment 20 processes corresponding event.According to the difference of concrete application scene, the concrete form of two side apparatus both can be with
It is that server apparatus can also be client device, the application need not simultaneously be defined to this.For description side
Just, hereinafter will respectively with " event request side " and the abbreviation other side of " event handling side " in the application
Case is illustrated.
The purpose of design of application scheme is：Event handling side can recognize that the out of order situation of correlating event,
Correct treatment is made in the case where appearance is out of order and event request side is fed back in time, it is to avoid event request
Side re-transmission request message.Also to ensure that the processing mode when correlating event order is normal is unaffected simultaneously.
To meet the demand, the application provides a kind of correlating event processing method, shown in Figure 2, the method
May comprise steps of：
S101, receives treatment request message of the event request side for object event；
S102, the group mark according to object event judges whether to have received the corresponding event handling of group mark
Request message, S106 is performed if otherwise performing S103, being；
S103, judges the type of object event, then performed if elementary event S105, if revocation thing
Part then performs S105；
S104, the treatment operation of performance objective event (specially elementary event)；
S105, is not directed to the processing failure of object event (specially cancelling event) to event request side feedback
Message；
S106, judges whether the corresponding elementary event of treated group mark, if it is performs S107, otherwise
Perform S110；
S107, judges the type of object event, and S109 is then performed if revocation event；
S109, the treatment operation of performance objective event (specially cancelling event)；
S110, judges the type of object event, and S111 is then performed if elementary event；
S111, not the treatment operation of performance objective event (specially elementary event)
Above-mentioned correlating event processing method, is applied to event handling side apparatus, in S101, event handling side
Equipment receives event handling request message from communication interface, and in this application, the request that will be currently received disappears
Breath asks the event for the treatment of to be referred to as object event, according to the practical application scene of the application, a target
Event had both been probably that elementary event is also likely to be revocation event, and event handling side can be according to event handling request
Entrained information directly distinguishes the event type of the treatment of request in message.
In method flow shown in Fig. 2, other steps in addition to S101 can be divided into two major classes by function：Sentence
Disconnected class step and execution class step, wherein judging class step for the order/out of order feelings of identification events request message
Condition, performing class step is then used to perform corresponding processing mode according to recognition result, to ensure expectation function
It is normal to realize.
The judgement class step in the application method is illustrated first, is related in the method flow shown in Fig. 2
Judgement class step include S102, S103, S106, S107 and S110, illustrate separately below：
The effect of S102 is to judge whether to receive the event handling request message of certain event group first.
In this application, will be a pass for the elementary event of same event body and its revocation event definition
Connection event group, for example for same Confirmation of Orders operation and cancellation operation, for the same receipts of fund
Money and reimbursement operation, etc..The different event group of different event body correspondences, for any one occurrence,
In addition to the event identifier with itself, also with a group mark, if two group mark phases of event
Together, then illustrate that the two events are directed to same event body.
Event handling side can extract the group mark of the request event after an event handling request is received,
And judge whether to have before this and receive the event handling request with same group mark, if otherwise said
Bright is to receive this group for the treatment of request of event first, is to illustrate it is not to receive first.Certainly, no matter sentence
How is disconnected result, and event handling side is required for recording the group mark of current event, for subsequently sentencing
It is disconnected.In this application, need not be defined for group physical record of mark and judgment mode.
The effect of S106 be have determined that be not receive certain event group first message after, determine whether
The type of message for receiving before.
In this application, treatment that can be by inquiring about elementary event is recorded, and this group received before judgement disappears
Breath type.Because the reception and event handling of event handling request message are completed in event handling side,
Here it is considered that not postponing between message sink and event handling.Therefore, for arbitrary event
Group, if the treatment record of elementary event cannot be inquired, the message received before explanation is at revocation event
Reason request message, if instead the treatment record of elementary event can be inquired, received base before explanation
Present event processes request message and processed.
S103, S107 and S110 are the judgements to current goal event type, can be asked according to event handling
Ask entrained information in message directly to determine the event type of request treatment, no longer describe in detail here.
The execution class step in the application method is illustrated below, is related in the method flow shown in Fig. 2
Execution class step include S104, S105, S108, S109, S111 and S112, said separately below
It is bright：
S104, from deterministic process, current goal event is elementary event, and is not received before same
The treatment request of group event, this branches into normal sequence, and it is (specific to process the object event according to normal mode
It is elementary event), it is however generally that, normal process mode mentioned here should also comprise determining whether energy
It is enough to process and operated to event request side feedback processing result etc. is necessary after local completion treatment, this Shen
Please not reinflated explanation.
S105, from deterministic process, current goal event is revocation event, but is not received but before
Cross with the treatment request of group event, illustrate to occur in that it is out of order, now cancel cannot successful execution, but not
Event request side is needed to feed back the message for showing " revocation failure ".
In actual applications, " revocation failure " is the main original for causing event request to stress hair revocation request message
Because of (either automatic triggering or user trigger manually), and the application is sent " revocation failure " by preventing
The mode of message, precisely in order to avoiding other side from retransmitting revocation request message.
In the specific implementation, event handling side still can perform once revocation behaviour according to current request message
Make, but it can be seen from decision logic, the destruction operation is cannot be successful, therefore here can directly by
Processing mode is set to not perform destruction operation, so as to reduce the wasting of resources of event handling side.
In a kind of specific embodiment of the application, can also be directly to event request side feedback for current
The treatment success message of revocation event, it is to be understood that this step does not actually accomplish " revocation " place
Reason, according to the complete execution logic of the application, to ensure the normal realization of expectation function, if this step point
Branch is triggered, then after subsequently received event handling request message, will necessarily trigger S111 branches, so should
" cancelling successfully " message sends in advance equivalent in the case where the normal realization of expectation function is ensured, so that
Reduce the actual wait-for-response time of other side.
S109, from deterministic process, current goal event is revocation event, is received before with group event
Treatment request and treated with group elementary event, this branches into normal sequence, according to normal side
Formula processes the object event (specially cancelling event), it is however generally that, normal process mentioned here
Mode should also comprise determining whether to process and after local completion treatment to event request side feedback at
The necessary operation such as reason result, the not reinflated explanation of the application.
S111, from deterministic process, current goal event is elementary event, but is once received before
With the revocation request of group, illustrate to occur in that out of order.It is the reverse event of elementary event in view of revocation event,
Here it is by the way for the treatment of：Current elementary event is not processed, this way is equivalent to " supporting
Disappear " before the revocation event that does not process, finally, the expected knot with " first substantially cancelling again "
Fruit is consistent.Certainly the demands such as subsequent query are met, when actually keeping a record, still can be according to " basic thing
Part is processed ", the mode of " revocation event processed " recorded.
It can be seen that, application scheme can occur ensureing when message is out of order using the cooperation of S105 and S111
The normal realization of expectation function, and by way of preventing to send revocation event failed message, it is possible to reduce
The situation of event request side re-transmission request message occurs, so as to reduce the wasting of resources, reduce to user's use feeling
It is affected.In addition, the processing mode of " counteracting " can't cause more long delay, if in fact,
Only have elementary event treatment request message to occur postponing in whole process, then the process time of out of order process is not
Can be higher than the process time of normal sequence process, this also reduce further causes event request side because of time-out
The possibility of re-transmission request message.
With reference to Fig. 2 it can be found that in such scheme, thering are two to judge that branch is not related to, this is
Because in some systems, the factor such as meeting connected applications demand, network condition, interacts to event request message
Mechanism is configured so that 1 elementary event request and 1 revocation event are only allowed in same event group
Request, that is to say, that for event handling side, the event request message reception of same event group is sequentially
Only exist two kinds of situations：Elementary event request message → revocation event request message (normal sequence), revocation thing
Part treatment request message → elementary event processes request message (out of order), and two such is left a blank corresponding to branch
Situation is really be not in, therefore only by tetra- execution steps of S104, S105, S109 and S111
Can all of situation of covering：
Situation a, first receives elementary event treatment request message, then receive revocation event handling request message：
First carry out S104 branches, normal process elementary event；
S109 branches, normal process revocation event are performed again.
Situation b, first receives revocation event handling request message, then receive elementary event treatment request message：
S105 branches are first carried out, revocation event is untreated；
S111 branches are performed again, untreated revocation event before counteracting.
If system is not limited the event number in same event group, event handling side joint is received
Treatment request message order then can be increasingly complex, for example may repeatedly receive elementary event treatment request disappear
Breath or revocation event handling request message.For such case, need to only be supplemented on the basis of such scheme
The processing mode of S108 and S112 can ensure the normal realization of expectation function, as shown in figure 3, after supplement
Processing mode is as follows：
S108, from deterministic process, current goal event is elementary event, is received before with group event
Treatment request and treated elementary event with group, the branch is equivalent to repeating to have received for same
The elementary event treatment request of one event ontology, belongs to abnormal condition.Processing mode can normally go to hold
The treatment operation of the capable elementary event, but due to being successfully processed once before, therefore this is performed
Will not succeed, that is, new elementary event result will not be produced.
S112, from deterministic process, current goal event is revocation event, is received before with group event
Treatment request but it is untreated with group elementary event, that is to say, that be once connected to before with group removing
Pin event handling request, the revocation event handling request for same event ontology is have received equivalent to repetition,
Belong to abnormal condition.Processing mode can be the normal treatment operation for going to perform the revocation event, but by
It is cancelled and is not carried out with the treatment request of group elementary event, or elementary event in did not received, therefore this
Performing to succeed, that is, will not produce new revocation event handling result.
As can be seen that the S108 and S112 of supplement are only logically to have done perfect to method flow, it is actual
On can't produce actual effect, so if from simplify treatment from the point of view of, here can also directly by
The processing mode of S108 is set to not perform the treatment operation of the elementary event, sets the processing mode of S112
For the treatment for not performing the revocation event is operated, so as to reduce the resource consumption of event handling side.
Explanation is needed exist for, due to receiving the possibility of revocation event handling request in the presence of repetition, therefore
When S109 is performed, according to normal processing mode, can first judge object event same group of elementary event whether
It has been be revoked that, if be not revoked, further performed the destruction operation of the elementary event.If removed
Pin, illustrate to be currently needed for the revocation event of a repetition for the treatment of, and destruction operation will not be successfully, if conformed to the principle of simplicity
From the point of view of change treatment, processing mode directly can also be set to not perform the place of the revocation event here
Reason operation, so as to reduce the resource consumption of event handling side.
With reference to several specific situations being likely to occur, the handling process after improving is illustrated：
Foregoing situation a and situation b is not repeated explanation
Situation c, continuously receives the request message of elementary event treatment twice：
First carry out S104 branches, normal process elementary event；
S108 branches are performed again, and the elementary event for repeating does not produce actual effect.
Situation d, continuously receives revocation event handling request message twice：
S105 branches are first carried out, revocation event is untreated；
S112 branches are performed again, and the revocation event for repeating does not produce actual effect.
Situation e, first receives elementary event treatment request message, then receives revocation event handling request message, then
Receive elementary event treatment request message：
First carry out S104 branches, normal process elementary event；
S109 branches, normal process revocation event are performed again；
S108 branches are performed again, and the elementary event for repeating does not produce actual effect.
Situation f, first receives revocation event handling request message, then receives elementary event treatment request message, then
Receive revocation event handling request message：
S105 branches are first carried out, revocation event is untreated；
S111 branches are performed again, untreated revocation event before counteracting；
S112 branches are performed again, and the revocation event for repeating does not produce actual effect.
Increasingly complex message sequence situation, does not do exhaustive one by one herein.It can be seen that, even without to same
Event number in event group is limited, still can be to the various feelings that are likely to occur using application scheme
Shape is made and meets expected correct treatment.In addition, according to the introduction of preceding embodiment, in S111 with " counteracting "
Mode perform elementary event and its revocation event after, regardless of whether the treatment record of generation elementary event,
All without final result is influenceed, illustrate：After " counteracting " operation was performed once, subsequently
Have received again with the elementary event treatment request message of group, S108 performed if treatment record is generated before,
S111 is performed if treatment record is not generated before, the request of this elementary event will not produce actual effect.
Similarly, if whether the follow-up revocation event handling request message that have received with group, gave birth to according to before again
Recorded into treatment, S109 or S112 may be triggered, regardless of whether triggering which branch, revocation event will not
Produce actual effect.
Corresponding to above method embodiment, the application also provides a kind of correlating event for being applied to event handling side
Processing unit, shown in Figure 4, the device can include：
Message reception module 210, for receiving treatment request message of the event request side for object event；
First judge module 221, for being identified according to the group of object event, judges whether to have received group mark
Corresponding event handling request message；
Second judge module 222, for judging whether the corresponding elementary event of treated group mark；
3rd judge module 223, the type for judging object event；
First performing module 231, for not receiving the corresponding event handling request message of group mark and mesh
In the case that mark event is elementary event, the treatment operation of performance objective event；
Second performing module 232, for not receiving the corresponding event handling request message of group mark and mesh
In the case that mark event is revocation event, the processing failure to event request side feedback for object event does not disappear
Breath；
3rd performing module 233, for receiving the corresponding event handling request message of group mark, locating
Managed the group corresponding elementary event of mark and in the case that object event is revocation event, performance objective event
Treatment operation；
4th performing module 234, for receiving the corresponding event handling request message of group mark, not locating
Managed the group corresponding elementary event of mark and in the case that object event is elementary event, not performance objective thing
The treatment operation of part.
In a kind of specific embodiment of the application, the second performing module can be specifically for：Please to event
Side is asked to feed back the treatment success message for current revocation event.
In a kind of specific embodiment of the application, the second performing module can be specifically for：
The not treatment operation of performance objective event；
Or
After the treatment operation failure of performance objective event, the place of object event is not directed to event request side feedback
Reason failed message.
Shown in Figure 5, in a kind of specific embodiment of the application, said apparatus can also include the
Five performing modules 235, for received the corresponding event handling request message of group mark, processed group
Identify in the case that corresponding elementary event and object event be elementary event, not the place of performance objective event
Reason operation.
In a kind of specific embodiment of the application, said apparatus can also include the 6th performing module 236,
For to have received the corresponding event handling request message of group mark, untreated group of mark corresponding basic
In the case that event and object event are revocation event, the not treatment operation of performance objective event.
It is understood that the 5th performing module 235 and the 6th performing module 236 are used as two kinds of functional independences
Module, both can as shown in Figure 5 simultaneously configuration in a device, it is also possible to individually configure in a device,
Therefore the structure shown in Fig. 5 should not be construed as the restriction to application scheme.
The function of modules and the implementation process of effect specifically refer to correspondence step in the above method in said apparatus
Rapid implementation process, will not be repeated here.
As seen through the above description of the embodiments, those skilled in the art can be understood that this
Application can add the mode of required general hardware platform to realize by software.Based on such understanding, this Shen
The part that technical scheme please substantially contributes to prior art in other words can be in the form of software product
Embody, the computer software product can be stored in storage medium, such as ROM/RAM, magnetic disc,
CD etc., including some instructions are used to so that computer equipment (can be personal computer, server,
Or the network equipment etc.) perform method described in some parts of each embodiment of the application or embodiment.
Each embodiment in this specification is described by the way of progressive, identical phase between each embodiment
As part mutually referring to what each embodiment was stressed is the difference with other embodiment.
For especially for device embodiment, because it is substantially similar to embodiment of the method, so describing to compare
Simply, the relevent part can refer to the partial explaination of embodiments of method.Device embodiment described above is only
It is only illustrative, wherein the module illustrated as separating component can be or may not be physics
It is upper separate, when application scheme is implemented can the function of each module in same or multiple softwares and/or
Realized in hardware.Some or all of module therein can also be according to the actual needs selected to realize this reality
Apply the purpose of a scheme.Those of ordinary skill in the art are without creative efforts, you can with
Understand and implement.
The above is only the specific embodiment of the application, it is noted that common for the art
For technical staff, on the premise of the application principle is not departed from, some improvements and modifications can also be made,
These improvements and modifications also should be regarded as the protection domain of the application.
Claims (10)
1. a kind of correlating event processing method, is applied to event handling side, it is characterised in that be mutually related
Elementary event and its revocation event share same event group mark, and methods described includes：
Treatment request message of the event request side for object event is received, the object event includes basic thing
Part or revocation event；
Group mark according to the object event, judges whether to have received at the corresponding event of described group of mark
Reason request message；
If not receiving the corresponding event handling request message of described group of mark, it is in the object event
In the case of elementary event, the treatment operation of the object event is performed；It is revocation thing in the object event
In the case of part, the processing failure message of the object event is not directed to event request side feedback；
If having received the corresponding event handling request message of described group of mark, place is further determined whether
The corresponding elementary event of described group of mark was managed, if processed and described object event is revocation event,
Then perform the treatment operation of the object event；If untreated and described object event is elementary event,
The treatment operation of the object event is not performed then.
2. method according to claim 1, it is characterised in that described not feed back pin to event request side
To the processing failure message of the object event, including：Current revocation event is directed to event request side feedback
Treatment success message.
3. method according to claim 1, it is characterised in that described not feed back pin to event request side
To the processing failure message of the object event, including：
The treatment operation of the object event is not performed；
Or
After performing the treatment operation failure of the object event, the target is not directed to event request side feedback
The processing failure message of event.
4. method according to claim 1, it is characterised in that methods described also includes：
It is the feelings of elementary event in the processed corresponding elementary event of described group of mark and the object event
Under condition, the treatment operation of the object event is not performed.
5. method according to claim 1, it is characterised in that methods described also includes：
In the feelings that the untreated corresponding elementary event of described group of mark and the object event are revocation event
Under condition, the treatment operation of the object event is not performed.
6. a kind of correlating event processing unit, is applied to event handling side, it is characterised in that be mutually related
Elementary event and its revocation event share same event group mark, and described device includes：
Message reception module, it is described for receiving treatment request message of the event request side for object event
Object event includes elementary event or revocation event；
First judge module, for being identified according to the group of the object event, judges whether to have received described
The corresponding event handling request message of group mark；
Second judge module, for judging whether the corresponding elementary event of treated described group of mark；
3rd judge module, the type for judging the object event；
First performing module, for do not received the corresponding event handling request message of described group of mark and
In the case that the object event is elementary event, the treatment operation of the object event is performed；
Second performing module, for do not received the corresponding event handling request message of described group of mark and
In the case that the object event is revocation event, not to event request side feedback for the object event
Processing failure message；
3rd performing module, for receiving the corresponding event handling request message of described group of mark,
Treat the described group of corresponding elementary event of mark and the object event is in the case of revocation event, to hold
The treatment operation of the row object event；
4th performing module, for receiving the corresponding event handling request message of described group of mark, not
Treat in the case that the described group of corresponding elementary event of mark and the object event be elementary event, no
Perform the treatment operation of the object event.
7. device according to claim 6, it is characterised in that second performing module specifically for：
The treatment success message of current revocation event is directed to event request side feedback.
8. device according to claim 6, it is characterised in that second performing module specifically for：
The treatment operation of the object event is not performed；
Or
After performing the treatment operation failure of the object event, the target is not directed to event request side feedback
The processing failure message of event.
9. device according to claim 6, it is characterised in that described device also includes that the 5th performs mould
Block, for receiving the corresponding event handling request message of described group of mark, processed described group of mark
Know corresponding elementary event and the object event is not in the case of elementary event, the target thing to be performed
The treatment operation of part.
10. device according to claim 6, it is characterised in that described device also includes that the 6th performs
Module, for received the corresponding event handling request message of described group of mark, untreated described group
Identify corresponding elementary event and the object event is not in the case of revocation event, the target to be performed
The treatment operation of event.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510993292.8A CN106921619B (en) | 2015-12-24 | 2015-12-24 | Associated event processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510993292.8A CN106921619B (en) | 2015-12-24 | 2015-12-24 | Associated event processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106921619A true CN106921619A (en) | 2017-07-04 |
| CN106921619B CN106921619B (en) | 2020-04-14 |
Family
ID=59459713
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510993292.8A Active CN106921619B (en) | 2015-12-24 | 2015-12-24 | Associated event processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106921619B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109951261A (en) * | 2019-03-20 | 2019-06-28 | 江苏满运软件科技有限公司 | Middleware message transmits compensation method, device, electronic equipment, storage medium |
| CN113923176A (en) * | 2021-09-30 | 2022-01-11 | 完美世界(北京)软件科技发展有限公司 | Instant messaging message withdrawal method, device, equipment and computer readable medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090013181A1 (en) * | 2007-07-03 | 2009-01-08 | Electronics & Telecommunications Research Institute | Method and attestation system for preventing attestation replay attack |
| CN102347851A (en) * | 2010-07-29 | 2012-02-08 | 阿里巴巴集团控股有限公司 | Event processing method and server thereof |
| CN102567099A (en) * | 2011-12-30 | 2012-07-11 | 百度在线网络技术（北京）有限公司 | Method, device and equipment used for controlling operation object |
| CN102598761A (en) * | 2009-08-31 | 2012-07-18 | 捷讯研究有限公司 | Methods and apparatus to avoid mobile station transmission of duplicate event-based and polled acknowledgments |
| CN103246548A (en) * | 2012-02-02 | 2013-08-14 | 迈普通信技术股份有限公司 | Method and device for scheduling fault-tolerant order-preserving events |
-
2015
- 2015-12-24 CN CN201510993292.8A patent/CN106921619B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090013181A1 (en) * | 2007-07-03 | 2009-01-08 | Electronics & Telecommunications Research Institute | Method and attestation system for preventing attestation replay attack |
| CN102598761A (en) * | 2009-08-31 | 2012-07-18 | 捷讯研究有限公司 | Methods and apparatus to avoid mobile station transmission of duplicate event-based and polled acknowledgments |
| CN102347851A (en) * | 2010-07-29 | 2012-02-08 | 阿里巴巴集团控股有限公司 | Event processing method and server thereof |
| CN102567099A (en) * | 2011-12-30 | 2012-07-11 | 百度在线网络技术（北京）有限公司 | Method, device and equipment used for controlling operation object |
| CN103246548A (en) * | 2012-02-02 | 2013-08-14 | 迈普通信技术股份有限公司 | Method and device for scheduling fault-tolerant order-preserving events |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109951261A (en) * | 2019-03-20 | 2019-06-28 | 江苏满运软件科技有限公司 | Middleware message transmits compensation method, device, electronic equipment, storage medium |
| CN109951261B (en) * | 2019-03-20 | 2021-09-28 | 江苏满运软件科技有限公司 | Middleware message transmission compensation method and device, electronic equipment and storage medium |
| CN113923176A (en) * | 2021-09-30 | 2022-01-11 | 完美世界(北京)软件科技发展有限公司 | Instant messaging message withdrawal method, device, equipment and computer readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106921619B (en) | 2020-04-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111080449B (en) | Cross-chain transaction method of blockchain, management node and blockchain network | |
| WO2021057084A1 (en) | Blockchain-based data processing method and apparatus, system, and electronic device | |
| CN105740258B (en) | Method for processing business and device based on idempotent number verification | |
| CN103677988B (en) | The multi-process means of communication and system for software systems | |
| CN113347164A (en) | Block chain-based distributed consensus system, method, device and storage medium | |
| CN110784331B (en) | Consensus process recovery method and related nodes | |
| CN106470184A (en) | Safety certifying method, apparatus and system | |
| CN106250254B (en) | A kind of task processing method and system | |
| CN112529577A (en) | Block chain cross-chain system and method based on excitation treatment | |
| CN105978938A (en) | Service processing equipment service status determining method and scheduling equipment | |
| CN106921619A (en) | A kind of correlating event processing method and processing device | |
| CN109962837A (en) | Message treatment method, device, storage medium and electronic device | |
| US9132550B2 (en) | Apparatus and method for managing robot components | |
| CN106453340A (en) | Data processing method and system for intelligent robot | |
| CN110162959A (en) | Data processing method and device based on device-fingerprint | |
| CN101925882A (en) | Method of improving replica server performance and replica server system | |
| CN108965786A (en) | A kind of electronic whiteboard content sharing method and device | |
| CN106487858B (en) | Information method for uploading and device | |
| CN109104472A (en) | Block chain network network-building method, device, equipment and computer readable storage medium | |
| Kobayashi et al. | The effectiveness of D-Case application knowledge on a safety process | |
| CN111754348A (en) | Scene combined transaction method and device | |
| Utsunomiya et al. | A safety knowledge representation of the automatic driving system | |
| Maamar et al. | A new approach to model web services' behaviors based on synchronization | |
| CN115150031B (en) | Distributed system message response method and device based on distributed message | |
| CN112367299B (en) | Application program interface API management method and related device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240223 Address after: Guohao Times City # 20-01, 128 Meizhi Road, Singapore Patentee after: Advanced Nova Technology (Singapore) Holdings Ltd. Country or region after: Singapore Address before: Ky1-9008 Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands, ky1-9008 Patentee before: Innovative advanced technology Co.,Ltd. Country or region before: Cayman Islands |
|
| TR01 | Transfer of patent right |