CN111131471B - Operation method and device of service system and electronic equipment - Google Patents
Operation method and device of service system and electronic equipment Download PDFInfo
- Publication number
- CN111131471B CN111131471B CN201911378506.5A CN201911378506A CN111131471B CN 111131471 B CN111131471 B CN 111131471B CN 201911378506 A CN201911378506 A CN 201911378506A CN 111131471 B CN111131471 B CN 111131471B
- Authority
- CN
- China
- Prior art keywords
- service
- data
- rule
- business
- service system
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method and a device for operating a business system and electronic equipment; wherein the method comprises the following steps: in response to an event that a first service system calls data to a second service system and/or an external data source in service operation, intercepting to obtain service data, namely in the process of service operation, for one service system, when the service system interacts with other service systems or data sources to generate service data, intercepting the service data; calling a rule engine to judge whether the service data meets a preset service rule; if the service data does not meet the service rule, the operation of the current service system is not in accordance with the service rule, and the service in operation is correspondingly fused.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to an operation method and an apparatus for a service system, and an electronic device.
Background
With the rapid development of the internet, a large number of business systems are widely applied. The business system is a processing system for providing various business services to users, such as a member registration system, an electronic commerce system, an electronic payment system, and the like. With the complexity of services, the implementation of one service may be split and commonly performed by a plurality of service systems. Specifically, after a user sends a certain service request, processing the service request involves calling a plurality of service systems to form a corresponding "call chain", and in service operation, the plurality of service systems are sequentially called to complete a service. Among them, ensuring that the operation of each service system conforms to the predetermined service rule becomes an important proposition of service completion quality.
Disclosure of Invention
In view of this, the present invention provides a method and an apparatus for operating a service system, and an electronic device.
Based on the above purpose, the present invention provides an operation method of a service system, which includes:
responding to an event that a first service system calls data to a second service system and/or an external data source in service operation, and intercepting to obtain service data;
calling a rule engine to judge whether the service data meets a preset service rule;
and if the service data does not meet the service rule, fusing the service.
On the other hand, the invention also provides an operation device of a service system, which comprises the following components:
the intercepting module is configured to respond to an event that the first service system calls data to the second service system and/or an external data source in service operation, and intercept and obtain service data;
the calling module is configured to call a rule engine and judge whether the business data meet a preset business rule or not;
and the fusing module is configured to fuse the service if the service data does not meet the service rule.
In yet another aspect, the present invention also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described above.
As can be seen from the above description, according to the operation method, the operation device and the electronic device of the service system provided by the present invention, in the process of service operation, when one service system interacts with other service systems or data sources to generate service data, the service data is intercepted, and whether the service data meets the predetermined service rule is judged through the rule engine, when the service data does not meet the service rule, it is indicated that the operation of the current service system does not meet the service rule, and the service in operation is correspondingly fused, so that the continuous operation of the service which does not meet the service rule can be effectively prevented, thereby eliminating the quality hidden trouble in service operation, further improving the service completion quality, and avoiding the loss of users.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic view of a business process flow;
FIG. 2 is a flow diagram of a method for operating a business system in accordance with one or more embodiments of the present disclosure;
FIG. 3 is a schematic diagram illustrating a call flow between business systems in one or more embodiments of the present disclosure;
FIG. 4 is a flow diagram of the steps of invoking a rules engine in one or more embodiments of the present description;
fig. 5 is a flowchart of an admission judgment step of a traffic rule in one or more embodiments of the present specification;
FIG. 6 is a flow diagram of the steps of invoking a rules engine in one or more embodiments of the present description;
FIG. 7 is a schematic structural diagram of an operating device of a business system according to one or more embodiments of the present disclosure;
fig. 8 is a schematic structural diagram of an electronic device according to one or more embodiments of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail with reference to the following embodiments and the accompanying drawings.
It is to be noted that technical terms or scientific terms used in the embodiments of the present invention should have the ordinary meanings as understood by those having ordinary skill in the art to which the present disclosure belongs, unless otherwise defined. The use of "first," "second," and similar terms in this disclosure is not intended to indicate any order, quantity, or importance, but rather is used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect.
As described in the background section, for some complex services, it is done jointly by multiple service systems. Referring to fig. 1, when a user issues a service request, processing the service request involves multiple service systems, which are sequentially called according to the service operation requirement and the calling order to complete the service. For example, a user issues a payment service, and to complete the payment service, a receipt of a payment request needs to be made during the operation process, payment settlement starts after the receipt, and verification of the user identity needs to be further performed during the payment settlement. Correspondingly, in the implementation of the service system, the three service systems shown in fig. 1 are an acquiring system, a payment settlement system and an identity verification system in sequence.
In the process of the service operation, each service system needs to satisfy its own service rule when processing internal processing, and also needs to satisfy the corresponding service rule when calling between service systems. When any one of the calling among the service systems does not meet the service rule, the subsequent service operation is considered to be out of compliance, namely the finally completed service is wrong. In the prior art, whether the call between the service systems meets the service rule is judged only by the log data generated in the service operation after the service is completed, however, the service which does not meet the service rule is completed at this time, which actually causes the loss of resources such as data, property, time and the like of a user, that is, the existing post-processing mode cannot really ensure the completion quality of the service.
In view of the above, one or more embodiments of the present disclosure provide an operation scheme of a service system, where in service operation involving multiple service systems, a rule engine determines whether a call between the service systems satisfies a service rule, and when the service rule is not satisfied, a currently running service is fused, so that the service does not continue to run, thereby preventing completion of the service operation that does not satisfy the service rule, avoiding a loss of a user, and ensuring the completion quality of the service.
Referring to fig. 2, a method for operating a service system is provided for an embodiment of the present specification, where the method includes the following steps:
step S201, responding to an event that the first service system calls data to the second service system and/or an external data source in service operation, and intercepting to obtain service data.
In this embodiment, the service is completed by a plurality of service systems together, and the plurality of service systems are sequentially invoked during the service operation. That is, for any service system in this embodiment, there may be an upstream service system, which is called by the upstream service system; it is also possible to have a downstream business system that will invoke the downstream business system. Fig. 3 is a schematic diagram of a call flow between service systems in this embodiment.
In the process of processing by the first service system 100, the service processing result of the second service system 200 needs to be used, that is, the first service system 100 calls the second service system 200, that is, step S11 in fig. 3. Specifically, the first service system 100 sends a request for service invocation to the second service system 200, and according to the request, after the second service system 200 performs its own service processing, the result of the service processing is returned to the first service system 100, and the service data described in this embodiment is also returned. In this embodiment, the service rule is determined when the service system is called, so that the service data between the first service system 100 and the second service system 200 is intercepted.
For example, the first business system 100 is a payment settlement system, and the second business system 200 is an identity verification system. In the process of processing payment settlement, the first business system 100 needs to invoke the second business system 200 to verify the identity of the user of the payment, so as to ensure the security of the payment settlement.
In addition, referring to fig. 3, the first service system 100 may use some other related data during the service processing, and the data is generally stored in a data source outside the service system, i.e. the external data source. The external data source may be the DataBase 300 (DataBase) or the Distributed Storage System 400 (Distributed Storage System). Specifically, the first service system 100 sends a data call request to an external data source, and the external data source returns data to the first service system 100 according to the request, that is, as shown in step S12 and step S13 in fig. 3. The data returned by the external data source is the service data described in this embodiment. Similarly, the process of the first service system 100 calling data from the external data source also needs to satisfy the predetermined service rule, so in this embodiment, the service data between the first service system 100 and the external data source is intercepted.
For example, in the process of processing payment settlement, the first service system 100 needs to obtain the phone number of the user at this time for reminding the user that payment is being made by sending a prompt message to the user. Accordingly, if the information related to the user's telephone number is stored in a database outside the first service system 10, the first service system 100 requests the database for the data to obtain the user's telephone number.
It should be noted that, referring to fig. 3, according to different service operation processes corresponding to different services, the first service system 100 may only call a part of the second service system 200, the database 300, and the distributed storage system 400, that is, only execute at least one of step S11, step S12, and step S13.
Step S202, a rule engine is called to judge whether the business data meets a preset business rule.
In this embodiment, based on the service data obtained by the interception, the rule engine is called correspondingly, and the service data is input into the rule engine. The rules engine is a component embedded in the application that enables separation of business decisions from the application code, accepts data input, interprets business rules, and makes business decisions based on the business rules. In this embodiment, referring to step S14 in fig. 3, after the intercepted and obtained service data is input into the rule engine, the rule engine can determine whether the service data meets the service rule according to the predetermined service rule.
Step S203, if the service data does not meet the service rule, the service is fused.
In this embodiment, the rule engine outputs a decision result according to the service data and the service rule, and the decision result is not only whether the service data meets the service rule, but also whether the currently running service is fused. The fusing is also called a fusing mechanism, and is generally implemented by a fuse, which is a protection technology in a computer system. When a fuse is triggered, subsequent requests through this fuse will all return failures directly. In this embodiment, if the rule engine determines that the service data does not satisfy the service rule, the fusing processing is performed on the currently running service, and the fused service directly terminates running. Referring to fig. 3, if it is determined in step S14 that the service data does not satisfy the service rule, the first service system 100 triggers fusing, and the service in operation is terminated.
Correspondingly, if the rule engine judges that the service data meets the service rule, the current service is operated.
It can be seen that, in the operation method of the service system of this embodiment, in the process of service operation, when one service system and another service system or data source will generate service data interaction, the service data is intercepted, and whether the service data meets a predetermined service rule is correspondingly judged through the rule engine, when the service data does not meet the service rule, it is indicated that the operation of the current service system does not meet the service rule, and the service in operation is correspondingly fused, so that the service that does not meet the service rule can be effectively prevented from continuing to operate, so that quality hidden troubles in service operation are eliminated, thereby improving service completion quality and avoiding user loss.
As an alternative embodiment, referring to fig. 4, step 201 in the foregoing embodiment specifically includes:
step S2011, responding to an interface calling request of a first service system to a target interface, and triggering a buried point preset at the target interface; the target interface is used for realizing service data communication between the first service system and the second service system or an external data source;
step S2012, intercepting the service data communicated through the target interface.
In this embodiment, the data interaction process performed when the service call is implemented between the service systems is implemented through an interface. The first service system calls the second service system, and when the service data is transmitted, a preset interface between the first service system and the second service system needs to be called first. Obviously, when the first service system calls the external data source, the interface for data communication between the first service system and the external data source is also the target interface.
Therefore, in this embodiment, the first service system issues an interface call request to the target interface to correspond to an event that the first service system calls data to the second service system and/or the external data source. Specifically, the trigger response of the event is realized by setting a buried point at the target interface. The buried point is a data acquisition method, and refers to a related technology for capturing, processing and sending specific user behaviors or events and an implementation process thereof. The technical essence of the embedded point is that events in the running process of the software application are monitored, and judgment and capture are carried out when the events needing attention occur. In this embodiment, when the first service system sends an interface call request to the target interface, the preset embedded point is triggered, and service data communicated through the target interface is intercepted.
As an alternative embodiment, referring to fig. 5, in the operation method of the service system, after the service data is input into the rule engine, before the determination on whether the service rule is satisfied, an admission determination step of the service rule needs to be further performed, which specifically includes:
step S501, at least one business rule is matched for the business data according to the target interface.
In this step, the business rules to be used by the rule engine are matched in the dimension of the interface. For example, the first business system is a payment settlement system that performs payment settlement for a payment submitted by the user for the content of the second business system or the external data source calling the business to be implemented. For a payment settlement, it is necessary to determine whether the compliance of the transaction and the identity legitimacy of both parties of the transaction satisfy the business rules, and in this step, the business rules for determining the compliance of the transaction and the identity legitimacy of both parties of the transaction are correspondingly matched.
Step S502, for each business rule, at least one corresponding admission condition is determined.
In this step, for each service rule obtained by matching, at least one admission condition is correspondingly set. In this embodiment, not every business rule is executed for the business rules obtained by root matching. Whether a service rule is executed depends on whether the service data can satisfy the admission condition. The admission condition is used for further screening the service data, so that the work of the rule engine can be more specific to accord with the actual application scene.
For example, when the first business system processes payment settlement, it is necessary to determine whether or not the security of one payment settlement satisfies the business rule. Specifically, in some scenarios, the risk of payment settlement is high, such as cross-border transaction and large transaction amount; in contrast, the risk is low when the transaction amount is small in domestic transaction. In order to make the operation of the rule engine more specific, two admission conditions are correspondingly set for the service rule for judging the risk of payment settlement, namely: the transaction type is a cross border transaction and the transaction amount is greater than 5000 dollars.
Step S503, judging whether the service data meets each admission condition; and if the admission condition that the service data do not meet exists, not executing to judge whether the service data meet the service rule or not.
In this step, corresponding parameters are extracted from the service data according to the determined admission conditions, and then the extracted parameters are respectively and correspondingly compared with the admission conditions for judgment. If the service data can satisfy each admission condition, the subsequent steps of the service rule judgment in the method of the embodiment are normally performed. If the admission conditions are not satisfied, that is, as long as the service data does not satisfy each admission condition, the subsequent step of judging the service rule is not executed, that is, the service rule is not executed.
For example, for a business rule that judges the risk of payment settlement, and its two admission conditions: the transaction type is cross-border transaction, and the transaction amount is larger than 5000 yuan. Extracting a first parameter corresponding to the transaction type and a second parameter corresponding to the transaction amount from the business data; wherein the value of the first parameter is indicative of a cross-border transaction and the value of the second parameter is indicative of 2000 dollars. The first parameter meets the admission condition whether the transaction amount is more than 5000 yuan, and the second parameter does not meet the admission condition whether the transaction amount is more than 5000 yuan; therefore, the business rule for determining the risk of payment settlement is not executed.
Therefore, in the embodiment, whether the matched service rule is executed or not is determined by setting the admission condition, so that the processing of the rule engine can be more detailed and concrete, the processing of the rule engine can better conform to the actual application scene, and the operation and completion quality of the service can be effectively improved.
As an alternative embodiment, referring to fig. 6, the step of invoking the rule engine specifically includes:
s601, loading a rule engine jar packet preset in the first business system;
step S602, analyzing the rule engine jar packet, and determining and calling an interface of the rule engine;
and step S603, inputting the business data into the rule engine through an interface of the rule engine.
In this embodiment, the calling of the business system to the rule engine is implemented by a jar packet. The jar package, also known as Java Archive File, is a compressed set of files written in the Java language. An executable JAR package is a self-contained (independent of other components, can be used for external use in an independent manner) Java application program, which is stored in a specially configured JAR file and can be executed without extracting the file or setting a path in advance.
In this embodiment, the data communication between the service system and the rule engine also uses an interface, and accordingly, data such as a configuration file, path information, and the like required for invoking the interface are packaged to generate a jar packet, that is, the rule engine jar packet. The rule engine jar packet is preset in a first business system, when the first business system needs to call a rule engine, the preset rule engine jar packet is loaded, then the rule engine jar packet is analyzed, an interface of the rule engine is determined through data contained in the rule engine jar packet, data communication between the first business system and the rule engine is further achieved, business data are input into the rule engine, and then the rule engine judges whether the business data meet business rules or not.
Further, the business rules in the rule engine are generally managed in the background by a management system. Corresponding to the change of the business, the business rules are changed correspondingly, and the management system of the business rules correspondingly generates the business rule updating data for realizing the change of the business rules. In this embodiment, the rule engine jar packet is updated according to the received service rule update data and the corresponding update rule engine jar packet, so that the operation of the service system can be adapted to the update of the service rule, and the normal and correct operation of the service system is ensured.
In the embodiment, a method for presetting a JAR packet in a service system is adopted to realize a near-end strategy of the rule engine, namely, one-time system-level calling is reduced, partial functions of the rule engine are made into the near-end rule engine JAR packet, the service system loads the rule engine JAR packet to acquire data from a cache at first, and an interface and other necessary data are determined, so that the operation efficiency of the service can be remarkably improved.
As an optional embodiment, after the service data is intercepted and obtained in the method of the embodiment, the service data is further converted into a JSON format. The JSON (JavaScript Object notification) is a lightweight data exchange format, which stores and represents data in a text format completely independent of a programming language, has a simple and clear hierarchical structure, is easy to read and write, and is easy to parse and generate by a machine. In this embodiment, the service data is converted into the JSON format to perform subsequent transmission, so that the data transmission efficiency can be effectively improved, and the operation efficiency of the whole service is further improved.
Based on the same inventive concept, referring to fig. 7, the present specification further provides an operating apparatus of a service system, including:
the intercepting module 701 is configured to respond to an event that the first service system calls data to the second service system and/or an external data source in service operation, and intercept and obtain service data;
a calling module 702 configured to call a rule engine to determine whether the service data satisfies a predetermined service rule;
a fusing module 703 configured to fuse the service if the service data does not satisfy the service rule.
As an optional embodiment, the external data source includes: at least one of a database and a distributed storage system.
As an optional embodiment, the interception module 701 is further configured to convert the service data into a JSON format.
As an optional embodiment, the intercepting module 701 is specifically configured to trigger a buried point preset at a target interface in response to an interface call request of a first service system to the target interface; the target interface is used for realizing service data communication between the first service system and the second service system or an external data source; intercepting the traffic data communicated through the target interface.
As an optional embodiment, the invoking module 702 is further configured to match at least one business rule for the business data according to the target interface; for each business rule, determining at least one admission condition corresponding to the business rule; judging whether the service data meets each admission condition; and if the admission condition that the service data do not meet exists, not executing to judge whether the service data meet the service rule or not.
As an optional embodiment, the invoking module 702 is specifically configured to load a rule engine jar package preset in the first business system; analyzing the rule engine jar packet, and determining and calling an interface of the rule engine; and inputting the business data into the rule engine through an interface of the rule engine.
As an optional embodiment, the apparatus further comprises: an update module configured to receive business rule update data; and updating the rule engine jar packet according to the business rule updating data.
For convenience of description, the above devices are described as being divided into various modules by functions, which are described separately. Of course, the functionality of the modules may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.
The apparatus of the foregoing embodiment is used to implement the corresponding method in the foregoing embodiment, and has the beneficial effects of the corresponding method embodiment, which are not described herein again.
Based on the same inventive concept, the present specification further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and running on the processor, and when the processor executes the computer program, the processor implements the method according to any of the above embodiments.
Fig. 8 is a schematic diagram illustrating a more specific hardware structure of an electronic device according to this embodiment, where the electronic device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.
The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, bluetooth and the like).
It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
It should be noted that the method of the embodiment of the present invention may be executed by a single device, such as a computer or a server. The method of the embodiment can also be applied to a distributed scene and completed by the mutual cooperation of a plurality of devices. In the case of such a distributed scenario, one of the multiple devices may only perform one or more steps of the method according to the embodiment of the present invention, and the multiple devices interact with each other to complete the method.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the idea of the invention, also features in the above embodiments or in different embodiments may be combined, steps may be implemented in any order, and there are many other variations of the different aspects of the invention as described above, which are not provided in detail for the sake of brevity.
In addition, well known power/ground connections to Integrated Circuit (IC) chips and other components may or may not be shown within the provided figures for simplicity of illustration and discussion, and so as not to obscure the invention. Furthermore, devices may be shown in block diagram form in order to avoid obscuring the invention, and also in view of the fact that specifics with respect to implementation of such block diagram devices are highly dependent upon the platform within which the present invention is to be implemented (i.e., specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the invention, it should be apparent to one skilled in the art that the invention can be practiced without, or with variation of, these specific details. Accordingly, the description is to be regarded as illustrative instead of restrictive.
While the present invention has been described in conjunction with specific embodiments thereof, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art in light of the foregoing description. For example, other memory architectures, such as Dynamic RAM (DRAM), may use the discussed embodiments.
The embodiments of the invention are intended to embrace all such alternatives, modifications and variances which fall within the broad scope of the appended claims. Therefore, any omissions, modifications, substitutions, improvements and the like that may be made without departing from the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (15)
1. An operation method of a business system comprises the following steps:
responding to an event that a first service system calls data to a second service system and/or an external data source in service operation, and intercepting to obtain service data; the service data is data transmitted between the first service system and the second service system and/or an external data source; the service data is acquired through a buried point preset at a target interface; the target interface is used for realizing service data communication between the first service system and the second service system or an external data source;
calling a rule engine to judge whether the service data meets a preset service rule;
and if the service data does not meet the service rule, fusing the service.
2. The method of claim 1, wherein the external data source comprises: at least one of a database and a distributed storage system.
3. The operation method of the business system according to claim 1, after the intercepting obtains the business data, further comprising:
and converting the service data into a JSON format.
4. The operation method of the service system according to claim 1, wherein the intercepting of the service data in response to an event that the first service system calls data to the second service system and/or an external data source during service operation includes:
responding to an interface calling request of a first service system to a target interface, and triggering a buried point preset at the target interface;
intercepting the traffic data communicated through the target interface.
5. The operation method of the business system according to claim 4, before the determining whether the business data satisfies the predetermined business rule, further comprising:
matching at least one service rule for the service data according to the target interface;
for each service rule, determining at least one corresponding admission condition;
judging whether the service data meets each admission condition; if the admission condition that the service data does not satisfy exists, the judgment of whether the service data satisfies the service rule is not executed.
6. The method of claim 1, wherein the invoking rules engine comprises:
loading a rule engine jar packet preset in the first business system;
analyzing the rule engine jar packet, and determining and calling an interface of the rule engine;
and inputting the business data into the rule engine through an interface of the rule engine.
7. The method of operating a business system of claim 6, further comprising:
receiving service rule updating data;
and updating the rule engine jar packet according to the business rule updating data.
8. An operation device of a business system, comprising:
the intercepting module is configured to respond to an event that the first service system calls data to the second service system and/or an external data source in service operation, and intercept and obtain service data; the service data is data transmitted between the first service system and the second service system and/or an external data source; the service data is acquired through a buried point preset at a target interface; the target interface is used for realizing service data communication between the first service system and the second service system or an external data source;
the calling module is configured to call a rule engine and judge whether the business data meet a preset business rule or not;
and the fusing module is configured to fuse the service if the service data does not meet the service rule.
9. The apparatus of claim 8, the external data source, comprising: at least one of a database and a distributed storage system.
10. The apparatus of claim 8, the interception module further configured to convert the traffic data into JSON format.
11. The apparatus according to claim 8, wherein the interception module is specifically configured to trigger a buried point preset at a target interface in response to an interface call request of a first service system to the target interface; intercepting the traffic data communicated through the target interface.
12. The apparatus of claim 11, the invoking module further configured to match at least one business rule for the business data according to the target interface; for each service rule, determining at least one corresponding admission condition; judging whether the service data meets each admission condition; if the admission condition that the service data does not satisfy exists, the judgment of whether the service data satisfies the service rule is not executed.
13. The apparatus of claim 8, the invocation module being specifically configured to load a rules engine jar package pre-installed in the first business system; analyzing the rule engine jar packet, and determining and calling an interface of the rule engine; and inputting the business data into the rule engine through an interface of the rule engine.
14. The apparatus of claim 13, further comprising:
an update module configured to receive business rule update data; and updating the rule engine jar packet according to the business rule updating data.
15. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of claims 1 to 7 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911378506.5A CN111131471B (en) | 2019-12-27 | 2019-12-27 | Operation method and device of service system and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911378506.5A CN111131471B (en) | 2019-12-27 | 2019-12-27 | Operation method and device of service system and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111131471A CN111131471A (en) | 2020-05-08 |
| CN111131471B true CN111131471B (en) | 2023-03-24 |
Family
ID=70504042
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911378506.5A Active CN111131471B (en) | 2019-12-27 | 2019-12-27 | Operation method and device of service system and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111131471B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109614262A (en) * | 2018-09-25 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Business method of calibration, device and computer readable storage medium |
| CN110380929A (en) * | 2019-07-15 | 2019-10-25 | 阿里巴巴集团控股有限公司 | A kind of idempotent validation checking method, device and equipment |
| CN110427304A (en) * | 2019-07-30 | 2019-11-08 | 中国工商银行股份有限公司 | O&M method, apparatus, electronic equipment and medium for banking system |
| CN110580234A (en) * | 2019-08-22 | 2019-12-17 | 广州易起行信息技术有限公司 | Fusing method suitable for micro server and external system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8732108B2 (en) * | 2010-10-07 | 2014-05-20 | International Business Machines Corporation | Rule authoring for events in a grid environment |
-
2019
- 2019-12-27 CN CN201911378506.5A patent/CN111131471B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109614262A (en) * | 2018-09-25 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Business method of calibration, device and computer readable storage medium |
| CN110380929A (en) * | 2019-07-15 | 2019-10-25 | 阿里巴巴集团控股有限公司 | A kind of idempotent validation checking method, device and equipment |
| CN110427304A (en) * | 2019-07-30 | 2019-11-08 | 中国工商银行股份有限公司 | O&M method, apparatus, electronic equipment and medium for banking system |
| CN110580234A (en) * | 2019-08-22 | 2019-12-17 | 广州易起行信息技术有限公司 | Fusing method suitable for micro server and external system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111131471A (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110032511A (en) | A kind of interface test method and interface testing equipment | |
| CN110780870B (en) | Service execution method, device, equipment and storage medium | |
| CN111143087A (en) | Interface calling method and device, storage medium and server | |
| CN112948835B (en) | Applet risk detection method and device | |
| CN109117609B (en) | Request intercepting method and device | |
| CN111638983A (en) | Interface calling method, interface calling device and terminal equipment | |
| CN111179061A (en) | Resource transfer processing method, device and equipment | |
| CN111552568A (en) | Cloud service calling method and device | |
| CN110704131B (en) | Method and device for calling native application by HTML5 application | |
| CN104503768A (en) | Call method and device for application programming interface (API) | |
| CN111415146A (en) | Resource data processing method, device and equipment | |
| CN109933508B (en) | Method and apparatus for transmitting information | |
| CN114979295A (en) | Gateway management method and device | |
| CN113010892B (en) | Method and device for detecting malicious behavior of small program | |
| CN114500640A (en) | Message generation method, message transmission device, electronic equipment and medium | |
| CN111355800B (en) | Service processing method, device, equipment and storage medium | |
| CN111131471B (en) | Operation method and device of service system and electronic equipment | |
| CN110336872B (en) | Method, device and system for acquiring third-party data | |
| CN111538483A (en) | Data processing method, equipment, server and readable storage medium | |
| CN110544087A (en) | Mobile payment method, device, equipment and computer readable storage medium | |
| CN110838929A (en) | System error checking method and system error checking device | |
| CN114428723A (en) | Test system, system test method, related device and storage medium | |
| CN113590352A (en) | Data calling method, device, equipment and readable storage medium | |
| CN113691618A (en) | Message notification method, device, message center and storage medium | |
| CN111523872A (en) | Transaction processing method and device, mobile terminal and computer readable storage medium |
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 |