CN107341047A - Route processing method, device, storage medium and the computer equipment of callback events - Google Patents
Route processing method, device, storage medium and the computer equipment of callback events Download PDFInfo
- Publication number
- CN107341047A CN107341047A CN201710349795.0A CN201710349795A CN107341047A CN 107341047 A CN107341047 A CN 107341047A CN 201710349795 A CN201710349795 A CN 201710349795A CN 107341047 A CN107341047 A CN 107341047A
- Authority
- CN
- China
- Prior art keywords
- service
- channel
- callback
- event
- callback event
- 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
- 238000003860 storage Methods 0.000 title claims abstract description 9
- 238000003672 processing method Methods 0.000 title claims abstract description 8
- 238000012545 processing Methods 0.000 claims abstract description 38
- 238000000034 method Methods 0.000 claims abstract description 25
- 238000013486 operation strategy Methods 0.000 claims description 35
- 238000012795 verification Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 8
- 238000009826 distribution Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/461—Saving or restoring of program or task context
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Economics (AREA)
- General Engineering & Computer Science (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Exchange Systems With Centralized Control (AREA)
- Telephonic Communication Services (AREA)
Abstract
The present invention relates to a kind of route processing method of callback events, device, storage medium and computer equipment, wherein method includes：Callback events request is obtained, callback events request includes the business event type of request；The set of channel callback events configuration information according to corresponding to obtaining business event type；If effective channel callback events configuration information in the set of channel callback events configuration information be present, then by callback events request be distributed to corresponding operational processor in effective channel callback events configuration information so that operational processor carries out corresponding readjustment processing.Without traveling through each business channel, but the business channel for being directly distributed to correlation is handled, and then shortens processing time, improves treatment effeciency.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for routing and processing a callback event, a storage medium, and a computer device.
Background
The channel event refers to business events of registration, real name, card binding, recharging, product, investment, refund and the like of users in different channels, and the callback refers to callback processing of the events. Currently, the processing of each callback event generally needs to traverse all channels and then be processed individually by logic code in the subscribed channels, resulting in long processing time and low efficiency.
Disclosure of Invention
Therefore, it is necessary to provide a routing processing method, device, storage medium, and computer device for callback events, aiming at the problems of long processing time and low efficiency of current callback events.
A routing processing method of a callback event comprises the following steps:
obtaining a callback event request, wherein the callback event request comprises a requested service event type;
acquiring a set of corresponding channel callback event configuration information according to the type of the service event;
if the effective channel callback event configuration information exists in the set of the channel callback event configuration information, distributing the callback event request to a service processor corresponding to the effective channel callback event configuration information so as to enable the service processor to perform corresponding callback processing.
In one embodiment, the callback event request further includes a user ID;
acquiring a set of corresponding channel callback event configuration information according to the service event type, wherein the set of corresponding channel callback event configuration information comprises:
searching a service channel corresponding to the user ID in a preset user channel relation table according to the user ID;
and acquiring a set of corresponding channel callback event configuration information according to the service event type and the service channel corresponding to the user ID.
In one embodiment, the callback event request further includes service information corresponding to a service event type;
acquiring a set of corresponding channel callback event configuration information according to the service event type, wherein the set of corresponding channel callback event configuration information comprises: and judging whether the callback event request is valid according to the service information, and if the callback event request is determined to be valid, acquiring a set of corresponding channel callback event configuration information according to the type of the service event.
In one embodiment, determining whether the callback event request is valid according to the service information includes:
and verifying the service information according to a preset verification rule, and if the verification is passed, determining that the callback event request is valid.
In one embodiment, the method further comprises the following steps:
and acquiring a channel service operation strategy, and generating channel callback event configuration information according to the channel service operation strategy.
In one embodiment, generating channel callback event configuration information according to a channel service operation policy includes:
acquiring a channel service operation strategy, wherein the channel service operation strategy comprises a service channel and a corresponding service event type;
generating a corresponding service processor and a check rule according to the type of the service event;
and establishing a corresponding relation among the service channels, the corresponding service event types, the service processors and the verification rules, and storing the corresponding relation as channel callback event configuration information.
In one embodiment, the method further comprises the following steps:
and determining the state of the service processor according to the channel service operation strategy, and storing the state in corresponding channel callback event configuration information.
In one embodiment, determining the state of the service processor according to the channel service operation policy, and storing the state in the channel callback event configuration information includes:
if the channel service operation strategy comprises the service effective time, generating the state of the service processor corresponding to the service event type according to the service effective time, and storing the state in channel callback event configuration information; or,
and if the channel service operation strategy comprises the termination service, modifying the state of the service processor corresponding to the service event type into invalid, and storing the modified state in the channel callback event configuration information.
A route processing apparatus of a callback event, comprising:
the callback event request receiving module is used for acquiring a callback event request, wherein the callback event request comprises a requested event type;
the channel callback event configuration association module is used for acquiring a corresponding channel callback event configuration set according to the event type;
and the callback event request distribution module is used for distributing the callback event request to a processor corresponding to the effective channel callback event configuration if the effective channel callback event configuration exists in the channel callback event configuration set, so that the processor carries out corresponding callback processing.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method as described above.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps as described in the above method when executing said program.
According to the routing processing method, device, storage medium and computer equipment for the callback event, the callback event request is obtained through monitoring, the corresponding channel callback event configuration information set is searched according to the callback event request, the callback event request is distributed to the corresponding service processor in the channel callback event configuration information effective in the set, so that the service processor carries out corresponding callback processing, each service channel does not need to be traversed, the callback event request is directly distributed to the relevant service channel for processing, the processing time is shortened, and the processing efficiency is improved.
Drawings
FIG. 1 is a flow diagram illustrating a method for routing callback events according to an embodiment;
FIG. 2 is a flowchart illustrating a method for routing callback events according to an embodiment;
FIG. 3 is a flowchart illustrating a method for routing callback events according to an embodiment;
FIG. 4 is a flow diagram illustrating generation of channel callback event configuration information in one embodiment;
FIG. 5 is a flow diagram illustrating generation of channel callback event configuration information in one embodiment;
FIG. 6 is a flowchart illustrating a method for routing callback events according to an embodiment;
fig. 7 is a schematic structural diagram of a route processing device for callback events in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention.
The embodiment of the invention provides a routing processing method of a callback event, which is applied to a routing server and comprises the following steps as shown in figure 1:
step S101, obtaining a callback event request;
in this embodiment, the routing server monitors the service events of the types of registration, real name, card binding, charging, product, investment, refund, etc. of each service channel user through the message bus ActiveMQ, so as to obtain a callback event request, where the callback event request includes the requested service event types, such as the service types of registration, real name, card binding, charging, product, investment, refund, etc.
Step S102, acquiring a set of corresponding channel callback event configuration information according to the type of the service event;
the routing server may search a set of channel callback event configuration information corresponding to the requested service event type in preset channel callback event configuration information according to the callback event request, that is, search all service channels subscribed to the service event type, and acquire channel callback event configuration information corresponding to each service channel. In this embodiment, the channel callback event configuration information may include information such as a name of a service channel, a service event type subscribed by the service channel, a name of a service processor corresponding to the service event type, and whether a state of the service processor is valid.
And step S103, if the effective channel callback event configuration information exists in the set of the channel callback event configuration information, distributing the callback event request to a corresponding service processor in the effective channel callback event configuration information so as to enable the service processor to perform corresponding callback processing.
And the routing server searches whether the state of the corresponding service processor in each channel callback event configuration information is valid or not in the set according to the set of the channel callback event configuration information acquired in the step, and if so, determines that the corresponding channel callback event configuration information is valid, so that the callback event request is distributed to the corresponding service processor in the valid channel callback event configuration information, and the service processor performs corresponding callback processing.
In the embodiment, the route server monitors and acquires the callback event request, searches the corresponding set of channel callback event configuration information according to the callback event request, and distributes the callback event request to the corresponding service processor in the effective channel callback event configuration information in the set so that the service processor performs corresponding callback processing, so that each service channel does not need to be traversed, and the callback event request is directly distributed to the relevant service channel for processing, thereby shortening the processing time and improving the processing efficiency.
In one embodiment, the service processor may be a specific code for processing a callback event corresponding to a service event type in a certain service channel, and the subscription relationship may be maintained in association with a name field of the service processor in the channel callback event configuration information. For example, a certain service channel "a" subscribes to a service processor corresponding to a service event of which the type is "product", and when a specific callback event is processed, the service processor can associate a corresponding code with the "a channel product processor" to process the callback event.
In the prior art, because the logic codes are processed separately in the subscribed channels, each channel callback event needs to be maintained separately, which is not beneficial to management, and along with the needs of business development, the number of channels is increased rapidly, changed frequently, terminated frequently and the like, so that the problem that the callback event logic codes in the channels and the common flow codes need to be modified continuously is faced, thereby causing a large workload. In the embodiment, the corresponding code is associated in the channel callback event configuration information as the service processor, so that when the service in the channel is changed, only the corresponding channel callback event configuration information needs to be modified, and the modification and maintenance are more convenient.
In an embodiment, the callback event request may further include a user ID, and the routing server stores a correspondence between the user ID and the belonging user channel, that is, a user channel relationship table. Therefore, the routing server can search the service channel corresponding to the user ID in the preset user channel relation table according to the user ID, so that the set of the corresponding channel callback event configuration information is obtained according to the service event type and the service channel corresponding to the user ID, namely, the set of the channel callback event configuration information corresponding to the service event type is searched in the service channel corresponding to the user ID, so that the searching is more convenient, and the searched information is more accurate.
In an embodiment, the callback event request may further include service information corresponding to a service event type, and as shown in fig. 2, the method for routing and processing the callback event may further include:
step S201, determining whether the callback event request is valid according to the service information.
In this embodiment, the service information is specific information corresponding to the service event type, for example, a callback event request with the service event type "investment", and the corresponding service information may include an ID of an investment user, an investment amount, an investment status, that is, information on whether the investment is successful or not, and the like. The routing server presets a corresponding service information check rule according to the service event type, so that the service information in the callback event request can be checked according to the preset check rule, if the check is passed, the callback event request can be determined to be valid, otherwise, the callback event request can be determined to be invalid.
In an embodiment, the callback event request with the service event type of "investment" is also taken as an example for explanation, for example, the routing server presets a check rule of the corresponding service information to check the investment state, so that if the investment state in the corresponding service information is "investment success", the check is passed, otherwise, the check is not passed.
Therefore, step S102 in the above embodiment may specifically be: and if the callback event request is determined to be valid, acquiring a set of corresponding channel callback event configuration information according to the service event type.
In an embodiment, as shown in fig. 3, the method for routing and processing a callback event may further include:
step S301, a channel service operation strategy is obtained, and channel callback event configuration information is generated according to the channel service operation strategy.
In this embodiment, the routing server may generate corresponding channel callback event configuration information according to the channel service operation policy, that is, generate corresponding channel callback event configuration information according to the operation policies of different service channels, so as to distribute the callback event request to the corresponding service channels for processing, thereby achieving the purpose of uniform routing. When a new docking service channel needs to be added, only corresponding channel callback event configuration information needs to be generated according to the operation strategy of the new service channel, and the public circulation code does not need to be modified, so that the maintenance is simple and convenient.
In one embodiment, as shown in fig. 4, generating channel callback event configuration information according to a channel service operation policy includes:
step S401, acquiring a channel service operation strategy;
step S402, generating a corresponding service processor and a check rule according to the type of the service event;
step S403, establishing a corresponding relationship between the service channels, the corresponding service event types, the service processors, and the verification rules, and storing the relationship as channel callback event configuration information.
In this embodiment, the routing server obtains the operation policy of each channel service, where each channel service operation policy may include information of each service channel and a corresponding service event type, so that channel callback event configuration information may be generated according to the channel service operation policy. Specifically, the corresponding service processor and the check rule can be generated according to the service event type in the channel service operation strategy, and the corresponding relationship among the service channel, the corresponding service event type, the service processor and the check rule is established, so that the configuration information of the channel callback event is stored.
In an embodiment, as shown in fig. 5, generating channel callback event configuration information according to a channel service operation policy may further include the following steps:
step S501, determining the state of the service processor according to the channel service operation strategy, and storing the state in the corresponding channel callback event configuration information. In this embodiment, if the channel service operation policy includes a service validity time, the routing server may generate a state of a service processor corresponding to a service event type according to the service validity time, specifically, if the current time is within the service validity time, determine that the state of the service processor corresponding to the service event type is valid, thereby generating a valid state, and if the validity time expires, modify the state to be invalid, and store the state in the channel callback event configuration information; in addition, if the channel service operation strategy comprises the termination service, the state of the service processor corresponding to the service event type is modified to be invalid, and the set state is stored in the channel callback event configuration information. Therefore, when the service termination in the channel occurs, only the corresponding channel callback event configuration information needs to be modified, so that the maintenance is more convenient.
In one embodiment, as shown in fig. 6, the method for routing and processing the callback event may include the following steps: step S601, receiving a callback event request;
the callback event request may include a requested service event type and corresponding service information.
Step S602, judging whether the callback event request is valid; if yes, executing step S602, otherwise executing step S606;
in one embodiment, whether the callback event request is valid may be determined based on the service information. The service information is specific information corresponding to the service event type, such as a callback event request with the service event type "investment", and the corresponding service information may include an ID of an investment user, an investment amount, an investment status, i.e., information on whether the investment is successful or not, and the like. The routing server presets a check rule of the corresponding service information according to the service event type, for example, the check rule of the service information corresponding to the service event type of "investment" preset by the routing server checks the investment state of the service information, so that if the investment state in the corresponding service information is "investment success", the check is passed, otherwise, the check is not passed, therefore, if the check is passed, the callback event request can be determined to be valid, otherwise, the callback event request is determined to be invalid.
Step S603, acquiring a set of channel callback event configuration information corresponding to the callback event request;
in an embodiment, the routing server may generate, in advance, corresponding channel callback event configuration information according to an operation policy of an operator, where each service event type in each channel corresponds to one record respectively. The channel callback event configuration information may specifically include information such as a name of a service channel, a service event type subscribed by the service channel, a name of a service processor corresponding to the service event type, and whether a state of the service processor is valid.
Therefore, the routing server can search a set of channel callback event configuration information corresponding to the requested service event type in preset channel callback event configuration information according to the callback event request, that is, search all service channels subscribed with the service event type, and acquire a set of channel callback event configuration information corresponding to each service channel.
Step S604, judging whether effective channel callback event configuration information exists in the set; if yes, executing step S605, otherwise executing step S606;
in this embodiment, whether the state of the corresponding service processor in each channel callback event configuration information is valid is searched in the set, and if the valid state exists, it is determined that the corresponding channel callback event configuration information is valid.
And step S605, distributing the callback event request to the service processor corresponding to the effective channel callback event configuration information so as to enable the service processor to perform corresponding processing.
Step S606 ends the flow.
In an embodiment, if the routing server obtains a callback event request of a certain service event type "product" and determines that the callback event request is valid through the step S602, all service channels subscribed with the service event type "product" are searched according to the step S603. If the set of the service channels subscribed with the service event type of "product" includes the a service channel, the B service channel, and the C service channel, the determination is made through step S604, and if only the states of the corresponding service processors in the channel callback event configuration information of the a service channel and the B service channel are valid, and the states of the corresponding service processors in the channel callback event configuration information of the C service channel are invalid, it is determined that valid the a service channel and the B service channel exist. And the callback event request is distributed to the corresponding A-channel product service processor and the B-channel product service processor in the channel callback event configuration information of the A-service channel and the B-service channel respectively, so that the A-channel product service processor and the B-channel product service processor perform corresponding processing.
The embodiment of the present invention further provides a route processing device for a callback event, as shown in fig. 7, including a callback event request receiving module 701, a channel callback event configuration association module 702, and a callback event request distribution module 703, where:
a callback event request receiving module 701, configured to obtain a callback event request, where the callback event request includes a requested event type;
a channel callback event configuration association module 702, configured to obtain a corresponding channel callback event configuration set according to an event type;
the callback event request distributing module 703 is configured to, if an effective channel callback event configuration exists in the channel callback event configuration set, distribute the callback event request to a processor corresponding to the effective channel callback event configuration, so that the processor performs corresponding callback processing.
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the following steps: acquiring a call-back event request, wherein the call-back event request comprises a requested service event type; acquiring a set of corresponding channel callback event configuration information according to the type of the service event; and if the effective channel callback event configuration information exists in the set of the channel callback event configuration information, distributing the callback event request to a service processor corresponding to the effective channel callback event configuration information so as to enable the service processor to perform corresponding callback processing.
In one embodiment, if the callback event request further includes service information corresponding to a service event type, the method further includes: judging whether the callback event request is valid or not according to the service information; acquiring a set of corresponding channel callback event configuration information according to the service event type, wherein the set of corresponding channel callback event configuration information comprises: and if the callback event request is determined to be valid, acquiring a set of corresponding channel callback event configuration information according to the service event type.
In one embodiment, determining whether the callback event request is valid according to the service information includes: and verifying the service information according to a preset verification rule, and if the verification is passed, determining that the callback event request is valid.
In one embodiment, further comprising: and acquiring a channel service operation strategy, and generating channel callback event configuration information according to the channel service operation strategy.
In one embodiment, generating channel callback event configuration information according to a channel service operation policy includes: acquiring a channel service operation strategy, wherein the channel service operation strategy comprises a service channel and a corresponding service event type; generating a corresponding service processor and a check rule according to the type of the service event; and establishing a corresponding relation among the service channels, the corresponding service event types, the service processors and the verification rules, and storing the corresponding relation as channel callback event configuration information.
In one embodiment, further comprising: and determining the state of the service processor according to the channel service operation strategy, and storing the state in corresponding channel callback event configuration information.
In one embodiment, determining the state of the service processor according to the channel service operation policy and saving the state in the channel callback event configuration information includes: if the channel service operation strategy comprises the service effective time, generating the state of the service processor corresponding to the service event type according to the service effective time, and storing the state in channel callback event configuration information; or, if the channel service operation strategy includes the termination service, modifying the state of the service processor corresponding to the service event type to be invalid, and storing the modified state in the channel callback event configuration information.
An embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the following steps: acquiring a call-back event request, wherein the call-back event request comprises a requested service event type; acquiring a set of corresponding channel callback event configuration information according to the type of the service event; and if the effective channel callback event configuration information exists in the set of the channel callback event configuration information, distributing the callback event request to a service processor corresponding to the effective channel callback event configuration information so as to enable the service processor to perform corresponding callback processing.
In one embodiment, if the callback event request further includes service information corresponding to a service event type, the method further includes: judging whether the callback event request is valid or not according to the service information; acquiring a set of corresponding channel callback event configuration information according to the service event type, wherein the set of corresponding channel callback event configuration information comprises: and if the callback event request is determined to be valid, acquiring a set of corresponding channel callback event configuration information according to the service event type.
In one embodiment, determining whether the callback event request is valid according to the service information includes: and verifying the service information according to a preset verification rule, and if the verification is passed, determining that the callback event request is valid.
In one embodiment, further comprising: and acquiring a channel service operation strategy, and generating channel callback event configuration information according to the channel service operation strategy.
In one embodiment, generating channel callback event configuration information according to a channel service operation policy includes: acquiring a channel service operation strategy, wherein the channel service operation strategy comprises a service channel and a corresponding service event type; generating a corresponding service processor and a check rule according to the type of the service event; and establishing a corresponding relation among the service channels, the corresponding service event types, the service processors and the verification rules, and storing the corresponding relation as channel callback event configuration information.
In one embodiment, further comprising: and determining the state of the service processor according to the channel service operation strategy, and storing the state in corresponding channel callback event configuration information.
In one embodiment, determining the state of the service processor according to the channel service operation policy and saving the state in the channel callback event configuration information includes: if the channel service operation strategy comprises the service effective time, generating the state of the service processor corresponding to the service event type according to the service effective time, and storing the state in channel callback event configuration information; or, if the channel service operation strategy includes the termination service, modifying the state of the service processor corresponding to the service event type to be invalid, and storing the modified state in the channel callback event configuration information.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (11)
1. A route processing method of callback events is characterized by comprising the following steps:
obtaining a call-back event request, wherein the call-back event request comprises a requested service event type;
acquiring a set of corresponding channel callback event configuration information according to the service event type;
if the effective channel callback event configuration information exists in the set of the channel callback event configuration information, the callback event request is distributed to a service processor corresponding to the effective channel callback event configuration information, so that the service processor performs corresponding callback processing.
2. The method for routing a callback event according to claim 1, wherein the callback event request further includes a user ID;
the acquiring of the set of the corresponding channel callback event configuration information according to the service event type includes:
searching a service channel corresponding to the user ID in a preset user channel relation table according to the user ID;
and acquiring a set of corresponding channel callback event configuration information according to the service event type and the service channel corresponding to the user ID.
3. The method for routing and processing the callback event according to claim 1, wherein the callback event request further includes service information corresponding to the service event type;
the acquiring of the set of the corresponding channel callback event configuration information according to the service event type includes: and judging whether the callback event request is valid according to the service information, and if the callback event request is determined to be valid, acquiring a set of corresponding channel callback event configuration information according to the service event type.
4. The method for routing and processing the callback event according to claim 3, wherein the determining whether the callback event request is valid according to the service information includes:
and verifying the service information according to a preset verification rule, and if the verification is passed, determining that the callback event request is valid.
5. The method for routing a callback event according to claim 1, further comprising:
and acquiring a channel service operation strategy, and generating the channel callback event configuration information according to the channel service operation strategy.
6. The method for route processing of a callback event according to claim 5, wherein the generating of the channel callback event configuration information according to a channel service operation policy comprises:
acquiring the channel service operation strategy, wherein the channel service operation strategy comprises a service channel and a corresponding service event type;
generating a corresponding service processor and a check rule according to the service event type;
and establishing a corresponding relation among the service channels, the corresponding service event types, the service processors and the verification rules, and storing the corresponding relation as channel callback event configuration information.
7. The method for routing a callback event according to claim 6, further comprising:
and determining the state of the service processor according to the channel service operation strategy, and storing the state in corresponding channel callback event configuration information.
8. The method for routing and processing the callback event according to claim 7, wherein the determining the state of the service processor according to the channel service operation policy and storing the state in the channel callback event configuration information comprises:
if the channel service operation strategy comprises service effective time, generating a state of a service processor corresponding to the service event type according to the service effective time, and storing the state in the channel callback event configuration information; or,
and if the channel service operation strategy comprises a termination service, modifying the state of the service processor corresponding to the service event type into invalid, and storing the modified state in the channel callback event configuration information.
9. A device for routing callback events, comprising:
the callback event request receiving module is used for acquiring a callback event request, wherein the callback event request comprises a request event type;
the channel callback event configuration association module is used for acquiring a corresponding channel callback event configuration set according to the event type;
and the callback event request distribution module is used for distributing the callback event request to a processor corresponding to the effective channel callback event configuration if the effective channel callback event configuration exists in the channel callback event configuration set, so that the processor performs corresponding callback processing.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 8.
11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 8 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710349795.0A CN107341047B (en) | 2017-05-17 | 2017-05-17 | Route processing method and device of callback event, storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710349795.0A CN107341047B (en) | 2017-05-17 | 2017-05-17 | Route processing method and device of callback event, storage medium and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107341047A true CN107341047A (en) | 2017-11-10 |
| CN107341047B CN107341047B (en) | 2020-07-14 |
Family
ID=60220165
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710349795.0A Expired - Fee Related CN107341047B (en) | 2017-05-17 | 2017-05-17 | Route processing method and device of callback event, storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107341047B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109711999A (en) * | 2018-11-14 | 2019-05-03 | 平安科技（深圳）有限公司 | Go out single method and device, computer equipment, storage medium based on halfpace |
| CN112347096A (en) * | 2019-08-09 | 2021-02-09 | 上海晶赞融宣科技有限公司 | Event distribution method and device, storage medium and terminal |
| CN114064330A (en) * | 2022-01-12 | 2022-02-18 | 广东睿江云计算股份有限公司 | Hook callback broadcast forwarding method and system based on OpenVidu |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794419A (en) * | 2010-04-13 | 2010-08-04 | 中兴通讯股份有限公司 | Method and device for automatically implementing business flow |
| US20130067489A1 (en) * | 2011-09-09 | 2013-03-14 | Microsoft Corporation | Power Efficient Callback Patterns |
-
2017
- 2017-05-17 CN CN201710349795.0A patent/CN107341047B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794419A (en) * | 2010-04-13 | 2010-08-04 | 中兴通讯股份有限公司 | Method and device for automatically implementing business flow |
| US20130067489A1 (en) * | 2011-09-09 | 2013-03-14 | Microsoft Corporation | Power Efficient Callback Patterns |
Non-Patent Citations (1)
| Title |
|---|
| 刘骁: ""移动互联网统一计费平台的设计与实现"", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109711999A (en) * | 2018-11-14 | 2019-05-03 | 平安科技（深圳）有限公司 | Go out single method and device, computer equipment, storage medium based on halfpace |
| CN112347096A (en) * | 2019-08-09 | 2021-02-09 | 上海晶赞融宣科技有限公司 | Event distribution method and device, storage medium and terminal |
| CN114064330A (en) * | 2022-01-12 | 2022-02-18 | 广东睿江云计算股份有限公司 | Hook callback broadcast forwarding method and system based on OpenVidu |
| CN114064330B (en) * | 2022-01-12 | 2022-05-13 | 广东睿江云计算股份有限公司 | Hook callback broadcast forwarding method and system based on OpenVidu |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107341047B (en) | 2020-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105447604B (en) | Account processing method and device | |
| US20190158626A1 (en) | Method, apparatus and computer readable storage medium for processing service | |
| CN106921754B (en) | Load balancing method, device, medium and electronic equipment of cluster system | |
| SA522432090B1 (en) | Network system and method for access management authentication and authorization | |
| CN107341047B (en) | Route processing method and device of callback event, storage medium and computer equipment | |
| US20140289286A1 (en) | System and method for performance tuning of garbage collection algorithms | |
| WO2019237594A1 (en) | Session persistence method and apparatus, and computer device and storage medium | |
| US20230319734A1 (en) | Method for computing power sharing and related devices | |
| CN110347515B (en) | Resource optimization allocation method suitable for edge computing environment | |
| CN105072139A (en) | Recommendation method and recommendation device | |
| CN113641762A (en) | Information pushing method, device and system and computer readable storage device | |
| CN114124490A (en) | Method and device for releasing new media content, storage medium and electronic equipment | |
| CN111831503B (en) | Monitoring method based on monitoring agent and monitoring agent device | |
| CN109327499B (en) | Service interface management method and device, storage medium and terminal | |
| CN112948255A (en) | Distributed kernel fuzzing test system and method | |
| CN106657140B (en) | Application authorization method and device | |
| CN104731660A (en) | Data distribution method, device and system | |
| JP3446697B2 (en) | Content usage control system | |
| CN108156201B (en) | Method and device for uniformly managing configuration data of application system | |
| CN110827079B (en) | Order following processing method, device and storage medium | |
| CN111131397B (en) | Application management method and system, gateway platform, server and storage medium | |
| CN107220129A (en) | Communication means and system between a kind of software module | |
| CN111767524B (en) | Authority management method, device, system, server and medium | |
| KR20190049059A (en) | Apparatus and method for cloud service brokerage | |
| CN113573299B (en) | Subscription data providing/acquiring method, providing/acquiring device and interactive system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20200714 Termination date: 20210517 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |