CN111260336A - Business checking method, device and equipment based on rule engine - Google Patents
Business checking method, device and equipment based on rule engine Download PDFInfo
- Publication number
- CN111260336A CN111260336A CN202010091156.0A CN202010091156A CN111260336A CN 111260336 A CN111260336 A CN 111260336A CN 202010091156 A CN202010091156 A CN 202010091156A CN 111260336 A CN111260336 A CN 111260336A
- Authority
- CN
- China
- Prior art keywords
- service
- rule
- business
- checked
- data
- 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
Images
Classifications
-
- 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
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Human Resources & Organizations (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present disclosure provides a method, an apparatus and a device for service checking based on a rule engine, wherein the method for service checking based on the rule engine comprises: determining a business rule set matched with a business to be checked; traversing each service rule in the service rule set, and inputting the service data of the service to be checked into at least one data node, so that the at least one data node determines the service rule to be checked based on the service rule set and determines the service parameter corresponding to each service rule to be checked based on the service data; and operating each business rule to be checked according to the business parameters corresponding to each business rule to be checked to obtain a business checking result corresponding to each business rule to be checked.
Description
Technical Field
The present disclosure relates to the field of business checking technologies, and in particular, to a method, an apparatus, and a device for business checking based on a rule engine.
Background
The service parameter inspection is a check of whether the software system is correct for the service processing logic, and can be performed according to the service rule through the input and output parameters, so the service parameter inspection is also called service check hereinafter.
At present, different checking scripts can be compiled aiming at different service scenes, and finally, the checking scripts are uniformly operated to check the service. However, when writing each check script, the log to be used needs to be analyzed, and the complexity of the check script is determined by the complexity of the service scenario.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide a method, an apparatus, and a device for business check based on a rule engine, so as to improve the efficiency of business check.
According to a first aspect of one or more embodiments of the present specification, there is provided a method for rule engine-based business collation, comprising:
determining a business rule set matched with a business to be checked;
traversing each service rule in the service rule set, and inputting the service data of the service to be checked into at least one data node, so that the at least one data node determines the service rule to be checked based on the service rule set and determines the service parameter corresponding to each service rule to be checked based on the service data;
and operating each business rule to be checked according to the business parameters corresponding to each business rule to be checked to obtain a business checking result corresponding to each business rule to be checked.
Optionally, determining a service rule set matched with a service to be checked includes:
and determining a business rule set matched with the application identifier of the application to which the business to be checked belongs and/or the business scene of the business to be checked.
Optionally, each data node screens the service rule set to be checked based on a respective preset screening condition to obtain a service rule to be checked, and screens the service data to obtain a service parameter corresponding to the service rule to be checked based on a respective preset value-taking expression.
Optionally, the running of each service rule to be checked according to the service parameter corresponding to each service rule to be checked to obtain the service checking result corresponding to each service rule to be checked includes:
inputting a rule expression of the service rule to be checked and a service parameter corresponding to the service rule to be checked into a rule analyzer for analysis to obtain an analysis result;
and determining a service checking result corresponding to the service rule to be checked according to the analysis result.
Optionally, the method further includes:
before inputting a rule expression of a business rule to be checked and a business parameter corresponding to the business rule to be checked into a rule analyzer for analysis, the rule analyzer reloads a support array as an operation symbol of an operation parameter.
Optionally, the method further includes:
after obtaining the business rule to be checked and the business parameters, putting the business rule to be checked into a queue, and putting the business parameters into a rule engine context;
the method comprises the following steps of operating each business rule to be checked according to business parameters corresponding to each business rule to be checked to obtain a business checking result corresponding to each business rule to be checked, and comprises the following steps:
consuming the business rules to be checked in the queue, acquiring the business parameters corresponding to the business rules to be checked from the context of a rule engine, and inputting the business rules to be checked and the business parameters corresponding to the business rules to be checked into a rule analyzer to obtain an analysis result;
determining a service checking result corresponding to the service rule to be checked according to the analysis result, wherein the service checking result comprises the following steps:
and determining that the service rule to be checked passes checking in response to the analysis result being analysis pass, and determining that the service rule to be checked fails checking in response to the analysis result being analysis failure.
Optionally, the method further includes:
before determining a service rule set matched with a service to be checked, acquiring the service data from a service system, wherein the service to be checked is a service which is processed and completed in the service system, and the service data is a service context generated in the process of processing the service to be checked.
Optionally, the method further includes:
and after the business data is acquired, converting the business data into key-value pairs, wherein in the key-value pairs, keys comprise corresponding attribute information of the business data, and values represent values of the business data.
According to a second aspect of one or more embodiments of the present specification, there is provided a rules engine based business collation apparatus comprising:
the first determining module is used for determining a business rule set matched with the business to be checked;
the second determining module is used for traversing each service rule in the service rule set and inputting the service data of the service to be checked into at least one data node so that the at least one data node determines the service rule to be checked based on the service rule set and determines the service parameter corresponding to each service rule to be checked based on the service data;
and the checking module is used for operating each business rule to be checked according to the business parameters corresponding to each business rule to be checked to obtain the business checking result corresponding to each business rule to be checked.
Optionally, the first determining module is configured to:
and determining a business rule set matched with the application identifier of the application to which the business to be checked belongs and/or the business scene of the business to be checked.
Optionally, each data node screens the service rule set to be checked based on a respective preset screening condition to obtain a service rule to be checked, and screens the service data to obtain a service parameter corresponding to the service rule to be checked based on a respective preset value-taking expression.
Optionally, the checking module includes:
the input unit is used for inputting the rule expression of the service rule to be checked and the service parameter corresponding to the service rule to be checked into the rule analyzer for analysis to obtain an analysis result;
and the determining unit is used for determining a service checking result corresponding to the service rule to be checked according to the analysis result.
Optionally, the apparatus further comprises:
and the reloading module is used for reloading the rule analyzer with the support array as the operation symbol of the operation parameter before inputting the rule expression of the service rule to be checked and the service parameter corresponding to the service rule to be checked into the rule analyzer for analysis.
Optionally, the apparatus further comprises:
the storage module is used for putting the business rules to be checked into a queue and putting the business parameters into a rule engine context after the business rules to be checked and the business parameters are obtained;
the checking module is used for:
consuming the business rules to be checked in the queue, acquiring the business parameters corresponding to the business rules to be checked from the context of a rule engine, and inputting the business rules to be checked and the business parameters corresponding to the business rules to be checked into a rule analyzer to obtain an analysis result;
the determining unit is used for determining that the service rule to be checked passes checking in response to the analysis result being analysis pass, and determining that the service rule to be checked fails checking in response to the analysis result being analysis failure.
Optionally, the apparatus further comprises:
the acquisition module is used for acquiring the service data from a service system before determining a service rule set matched with a service to be checked, wherein the service to be checked is a service which is processed and completed in the service system, and the service data is a service context generated in the process of processing the service to be checked.
Optionally, the apparatus further comprises:
and the conversion module is used for converting the service data into key-value pairs after the service data is acquired, wherein in the key-value pairs, keys comprise corresponding attribute information of the service data, and values represent values of the service data.
According to a third aspect of one or more embodiments of the present specification, there is provided an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements any one of the above-mentioned rules engine-based business checking methods when executing the program.
As can be seen from the above description, in the method for service checking based on a rule engine according to one or more embodiments of the present disclosure, when checking a service, by defining a data node in the rule engine, a service rule to be checked in the service to be checked and service parameter service data corresponding to the service rule to be checked are determined to be screened, and then a corresponding service rule is executed in the rule engine based on a service data parameter corresponding to the service rule to be checked to obtain a service checking result corresponding to each service rule to be checked, so that a service checking logic may form a checking rule in a rule configuration manner, so as to process a service checking process by using existing rule matching and rule executing functions of the rule engine, and further match and execute the rule according to the service to be checked by using the rule engine to obtain a service checking result, the efficiency of service checking is improved.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure 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 disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a schematic diagram of a business system framework provided in accordance with one or more embodiments of the present disclosure;
FIG. 2 is a flow diagram of a rules engine based business reconciliation method provided by one or more embodiments of the present specification;
FIG. 3 is a schematic diagram of a rule model provided in one or more embodiments of the present description;
FIG. 4 is a flow diagram of a rules engine based business reconciliation method provided by one or more embodiments of the present specification;
FIG. 5 is a block diagram of a rules engine based business reconciliation apparatus according to one or more embodiments of the present description;
fig. 6 is a more specific hardware architecture diagram of an electronic device according to one or more embodiments of the present disclosure.
Detailed Description
For the purpose of promoting a better understanding of the objects, aspects and advantages of the present disclosure, reference is made to the following detailed description taken in conjunction with the accompanying drawings.
It is to be noted that technical terms or scientific terms used in the embodiments of the present disclosure should have a general meaning 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. "upper", "lower", "left", "right", and the like are used merely to indicate relative positional relationships, and when the absolute position of the object being described is changed, the relative positional relationships may also be changed accordingly.
In one or more embodiments of the present description, as shown in fig. 1, a business system 11 and a rule engine 12 are involved, wherein the business system 11 is, for example, a business provider, and the rule engine 12 may include business rules customized by the business provider. When the business system 11 processes the business, it may invoke the corresponding business rule from the rule engine 12 according to the received business data to make business decision. The service provider may divide the customized service rules to form a service rule set 1 to a service rule set N as shown in fig. 1, where N is a positive integer. In order to check the correctness of the business processing logic (hereinafter referred to as business check), when a business process is completed, the rule engine 12 may obtain the business data of the business to be checked from the business system 11, perform data preparation for the business to be checked based on the business data, obtain the business rule corresponding to the business to be checked and the business data corresponding to each business rule, and run the business rule based on the business data corresponding to the business rule to be checked, so as to obtain a business check result.
FIG. 2 is a flow diagram of a rules engine based business reconciliation method that can be performed by a rules engine, as shown in FIG. 2, comprising:
step 202: determining a business rule set matched with a business to be checked;
the service to be checked may be, for example, a service provided by the service system, and the terminal device may request the service system to process the service by installing an application program and executing the application program. The service is, for example, various service processing logics (also referred to as service processing flows) executable by the service system, taking the payment service system as an example, the service processing logics are, for example, processing flows in which the service system responds to the payment request according to the received payment request. Business rules refer to the description of business definitions and constraints used to maintain business structure or to control and affect the behavior of a business. The business rules can extract the business logic processed by the business system from the program codes, convert the business logic into simple business rules, express business behaviors by structured business rule data, describe the business behaviors by adopting a natural language-like language, and store the business logic in a rule base in a centralized manner. Business rules can be created, updated and debugged in real time by business personnel, and complex logical relationships between business rules are handled by a rules engine.
For example, a service rule set matching with an identifier of an application to which the service to be checked belongs and/or a service scenario of the service to be checked may be determined, and a service rule set matching with the service to be checked is obtained. The identification of the application may be, for example, the name or code of the application provided by the business system, etc. The business scenario is, for example, a scenario in which a business process flow is executed. The different service scenarios correspond to different service providers, for example, in the case of a payment service system, the transaction data sent by different shopping platforms correspond to different service scenarios.
For example, one rule set may include service rules of the same class divided in advance according to the classification of the service rules, where the service rules may be classified according to service scenarios, or may also be classified according to functions implemented by the service rules.
Step 204: traversing each service rule in the service rule set, and inputting the service data of the service to be checked into at least one data node, so that the at least one data node determines the service rule to be checked based on the service rule set and determines the service parameter corresponding to each service rule to be checked based on the service data;
for example, each data node may screen out the business rules participating in the business check from the business rule set based on a respective preset screening rule. For a set of business rules, not all business rules in the set are used in each business scene, so that the screening conditions of the data nodes can be configured in advance according to the business rules; for another example, for some service scenarios, the value of the service parameter has a certain numerical limit, for example, checking the user level, checking the minimum consumption amount, and the like, so the service parameter can be screened by configuring a value expression for the data node.
The service parameter corresponding to the service rule may be a service parameter for operating the service rule in the process of processing the service to be checked, for example, the service rule is that a is greater than or equal to b, and the value of a and the value of b are service parameters.
Step 206: and operating each business rule to be checked according to the business parameters corresponding to each business rule to be checked to obtain a business checking result corresponding to each business rule to be checked.
In the method for checking a service based on a rule engine according to one or more embodiments of the present specification, when checking a service, a data node in the rule engine is used to determine a service rule to be checked in the service to be checked and a service parameter corresponding to the service rule to be checked, and then the rule engine executes a corresponding service rule based on the service parameter corresponding to the service rule to be checked to obtain a service checking result corresponding to the service rule to be checked, so that a service checking logic may form a checking rule by rule configuration, and thus, an existing rule matching and rule execution function of the rule engine may be used to process a service checking process, thereby improving service checking efficiency.
In one or more embodiments of the present description, determining a set of business rules that match the business to be checked may include: and determining a business rule set matched with the application identifier of the application to which the business to be checked belongs and/or the business scene of the business to be checked. As an example, if the service to be checked is a service corresponding to a certain shopping App, the identifier of the shopping App is an application identifier of an application to which the service to be checked belongs. For example, the rule engine may match a set of business rules to be checked from a cache of a business system according to the name of an application (which is an example of the identification of the application) and a business scenario of a business to be checked, where the business rules that the business system has invoked over a period of time are stored in the cache of a business department.
In one or more embodiments of the present specification, each data node obtains a service rule to be checked by screening from the service rule set based on a respective preset screening condition, and obtains a service parameter corresponding to the service rule to be checked by screening from the service data based on a respective preset value-taking expression. For example, when the rule engine runs, the service rule set is traversed, for each service rule, service data sequentially flows through each data node in a plurality of data nodes configured in advance, each data node runs a screening condition and a value-taking expression configured in advance, the service rule to be checked is screened out from the service rule set through the screening condition, and the value-taking expression is used for taking the value of the service data flowing through the data node, so that a service parameter corresponding to the service rule to be checked is obtained; if the screening condition fails to operate, the current business rule does not need to be subjected to subsequent verification, namely, the business rule is not the business rule to be verified, and the business rule with the successfully operated screening condition is determined as the business rule to be verified. The screening conditions are configured for each data node, so that when the service data passes through each data node, some unnecessary service rules can be screened out, thereby reducing the service rules needing to be checked and improving the service checking efficiency. For example, the service data is exemplified by an array, assuming that there are two objects in the array, each object has two attributes, the first object is a-1 and b-2, the second object is a-2 and b-2, and assuming that the value of the above-mentioned screening condition is greater than 1, then, of the two objects, a-1 does not satisfy the screening condition, the service rule of a-1 and b-2 is filtered out, the service rule of a-2 and b-2 satisfies the screening condition, and is left, and then, using the value-taking expression, the value of the object satisfying the screening condition in the array item, that is, the value of a-2 and b-2 in b-2 is taken.
As another example, assuming that a user pays by using a combination of account balance and a red envelope in an account in a piece of service data, wherein 10 dollars are paid by using the account balance, and 2 dollars are paid by using the red envelope, the asset type (wherein the asset type may be the object a in the above example) in the piece of service data includes: account balance and red envelope, the value of the asset amount (the value of the asset amount may be object b in the above example) includes 10 and 2, and it is assumed that the screening condition of the data node through which the service data passes is: if the asset is the account balance, when the piece of service data passes through the data node, the service rule paid by using the balance is reserved, the service rule paid by using the red packet is filtered, and for the service data paid by using the balance, the value is taken through the value-taking expression of the data node, for example, the value-taking expression dolar (b) is used for taking the value of the service data paid by using the balance, the obtained value is 10, the value 10 is the service parameter corresponding to the service rule paid by using the balance, and when the service rule is checked, the correctness of the service rule execution is checked by using the service parameter.
In one or more embodiments of the present specification, the running each to-be-checked business rule according to the business parameter corresponding to each to-be-checked business rule, and obtaining the business checking result corresponding to each to-be-checked business rule may include: inputting a rule expression of the service rule to be checked and a service parameter corresponding to the service rule to be checked into a rule analyzer for analysis to obtain an analysis result; and determining a service checking result corresponding to the service rule to be checked according to the analysis result. For example, the current service rule to be checked and the service parameter corresponding to the service rule may be used as input of a rule parser, the service rule to be checked is parsed in the rule parser, if the parsing of the service rule to be checked is successful, it may be determined that the service checking result of the current service rule to be checked is passed, and if the parsing of the service rule to be checked is failed, it may be determined that the service checking result of the current service rule to be checked is failed. As an example, assuming that a value expression of a service rule to be checked is a value of a ═ b, and in a service parameter corresponding to the service rule, a value of a is 1 and a value of b is 2, when the rule parser checks the service rule, a is 1, and b is 2, and the value expression a is substituted into b, the service rule parsing fails, so that the service checking result of the service rule is a failure.
In one or more embodiments of the present specification, before inputting a rule expression of a business rule to be checked and a business parameter corresponding to the business rule to be checked into a rule parser for parsing, the rule parser reloads an operand which takes a support array as an operation parameter. For example, the operators overridden by the rule parser may include: | A The value of ═, >, < ═ and | is defined as the value of! Etc. the rule parser, after reloading these operators, may support an array type parameter as an operand, for example, for parameter $ A >1, parameter A is an array, then all entries in array A satisfy a condition greater than 1 returning true, otherwise returning false, and so on. If the rule parser does not override these operators, then if parameters of the array type need to be processed, the following script needs to be written: map ($ a, (x) = > (if (x >1) true; else false)). Obviously, preloading the operator in the rule parser can improve the processing efficiency of the rule parser. In addition, for the purpose of business check, the rule engine can also support the built-in functions of key word and character string processing such as in and contacts. The rule parser may use, for example, an Aviator engine or an MVEL engine.
In one or more embodiments of the present specification, in order to improve the execution efficiency of the rule engine, when performing business check, a producer and consumer mode may be adopted, where the producer may be a rule engine matcher for obtaining the business rule to be checked in the business check process, the consumer may be a rule engine executor for consuming the business rule to be checked, in the producer and consumer mode, the producer and the consumer are two types of threads, and in order to decouple the relationship between the producer and the consumer, a shared data region may be adopted by the producer and the consumer, the producer produces data and then directly places the data in the shared data region without considering the behavior of the consumer, and the consumer only needs to obtain data from the shared data region without considering the behavior of the producer, and the shared data region has a function of inter-thread concurrent cooperation, so that both threads, producer and consumer, can collaborate concurrently. Based on the producer and consumer relationships between the rules engine matcher and the rules engine executor, when the data preparation is carried out on the business rules to be checked, the rule engine matcher puts the business rules to be checked which are obtained by screening based on the screening conditions into a queue, the parameters corresponding to the business rules to be checked and obtained based on the value-taking expression are put into a rule engine context, the value-taking rule engine context can be stored in a data bus, when the business check is carried out, the business rules to be checked in the queue are consumed through the rule engine executor, for each business rule to be checked, corresponding business parameters are obtained from the context of the rule engine, therefore, based on the multithreading concurrent cooperation between the rule engine matcher and the rule engine executor, the operation of the business rules is in the ms level, and therefore the business checking efficiency is improved. Based on this, the business checking method based on the rule engine may further include: after obtaining the business rule to be checked and the business parameters, putting the business rule to be checked into a queue, and putting the business parameters into a rule engine context; the method comprises the following steps of operating each business rule to be checked according to business parameters corresponding to each business rule to be checked to obtain a business checking result corresponding to each business rule to be checked, and comprises the following steps: consuming the business rules to be checked in the queue, acquiring the business parameters corresponding to the business rules to be checked from the context of a rule engine, and inputting the business rules to be checked and the business parameters corresponding to the business rules to be checked into a rule analyzer to obtain an analysis result; determining a service checking result corresponding to the service rule to be checked according to the analysis result, wherein the service checking result comprises the following steps: and determining that the service rule to be checked passes checking in response to the analysis result being analysis pass, and determining that the service rule to be checked fails checking in response to the analysis result being analysis failure.
It should be noted that, because the data nodes have data dependency, for example, the data node B needs to use data generated by the data node a, if the service rules to be checked obtained by screening the data nodes and the service parameters corresponding to the service rules are all put into the queue, the service rules in the service rule set are all executed and the corresponding service parameters can be obtained from the queue, which is obviously infeasible.
In one or more embodiments of the present specification, the method for checking a business based on a rule engine may further include: before determining a service rule set matched with a service to be checked, acquiring the service data from a service system, wherein the service to be checked is a service which is processed and completed in the service system, and the service data is a service context generated in the process of processing the service to be checked. For example, for a service a to be checked, when the service system finishes processing the service a, the service system may send the service context of the service a to the rule engine to trigger the rule engine to perform service check on the service a, so that after the service is executed, the service check process is triggered, and the correctness of the service processing logic can be known in time.
In one or more embodiments of the present specification, the method for checking a business based on a rule engine may further include: after the business data is obtained, the business data is converted into a Key-Value pair, wherein in the Key-Value pair, a Key comprises corresponding attribute information of the business data, and a Value of the business data is represented. For example, assuming that there is a class with a class name of a, an attribute of B in the class, and an attribute of C in the class of B, C is described as a.b.c, where a is assumed to be a transaction, B is that the transaction is initiated by a shopping App, and C is the amount of the transaction. The rule engine may treat a.b.c as a.b.c ═ 1, where C is the parameter name, a.b represents a kind of attribute information of the C parameter, i.e., the C parameter belongs to the class B, and B belongs to the class a, and 1 is the value of the parameter C.
Fig. 3 is a schematic diagram of a rule model provided in one or more embodiments of the present specification, where, as shown in fig. 3, the rule model includes: a data preparation module 31 and a set of expressions 32. The data preparation module 31 includes N data nodes, the number of the data nodes may be expanded according to the complexity of the service rule to be checked, the data nodes may be configured with a screening condition and a value-taking expression in advance, when the service data flows through the data nodes, the screening condition and the value-taking expression of the data nodes are run, and the obtained values of the data nodes (i.e., the service parameters) are placed in the context of the rule engine. For each business rule to be checked, if the execution of the screening condition fails, the data preparation of the business rule fails, the business rule does not participate in the business check, and if the execution of the screening condition succeeds, the data preparation of the business rule succeeds, and the business rule is put into a queue. And when the rule execution expression set checks the service, acquiring the service rule from the queue, and acquiring the service data corresponding to the service rule from the context of the rule engine.
Fig. 4 is a flowchart of a method for checking a business based on a rule engine according to one or more embodiments of the present disclosure, and as shown in fig. 4, the method may be executed by a business system, a rule engine matcher, and a rule engine executor, where the rule engine matcher and the rule engine executor may be disposed in the rule engine, and the method may include the following processes:
step 402: a buried point acquires a service operation context to be checked;
step 404: converting the access parameters of the business system interface into Key-Value pairs;
the above steps 402 and 404 may be performed by the business system;
step 406: matching a service rule set corresponding to the service to be checked from a cache of the service system according to the application name and the service scene;
step 408: and traversing the service rule set to prepare data, wherein the data preparation is described in detail above and is not described herein again.
Step 410: putting the service data obtained by screening into a data bus, and putting the service rules into a queue;
the above steps 406 to 410 may be performed by a rules engine executor;
step 412: traversing the service rule queue;
step 414: acquiring a service rule obtained by the circulation;
step 416: acquiring service parameters corresponding to the service rules obtained by the current cycle from a data bus;
step 418: inputting the service rule obtained by the current cycle and the service data corresponding to the service rule into a rule resolver for execution;
step 420: determining whether the execution result of step 418 passes, if so, executing step 422, and if so, executing step 424;
step 422: returning to the step 414 to continue checking other business rules after the business check is passed;
step 424: and returning the business rules with failed execution and the corresponding business parameters.
It should be noted that the method of the embodiments of the present disclosure 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 such a distributed scenario, one of the devices may only perform one or more steps of the method of the embodiments of the present disclosure, and the devices may interact with each other to complete the method.
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.
FIG. 5 is a block diagram of a rules engine based business collation apparatus according to one or more embodiments of the present specification, and as shown in FIG. 5, the apparatus 50 includes: a first determining module 51, configured to determine a set of business rules that match a business to be checked; a second determining module 52, configured to traverse each service rule in the service rule set, and input the service data of the service to be checked into at least one data node, so that the at least one data node determines the service rule to be checked based on the service rule set and determines a service parameter corresponding to each service rule to be checked based on the service data; and the checking module 53 is configured to run each to-be-checked business rule according to the business parameter corresponding to each to-be-checked business rule, so as to obtain a business checking result corresponding to each to-be-checked business rule.
In one or more embodiments of the present description, the first determining module may be configured to: and determining a business rule set matched with the application identifier of the application to which the business to be checked belongs and/or the business scene of the business to be checked.
In one or more embodiments of the present specification, each data node obtains a service rule to be checked by screening from the service rule set based on a respective preset screening condition, and obtains a service parameter corresponding to the service rule to be checked by screening from the service data based on a respective preset value-taking expression.
In one or more embodiments of the present description, the verification module may include: the input unit is used for inputting the rule expression of the service rule to be checked and the service parameter corresponding to the service rule to be checked into the rule analyzer for analysis to obtain an analysis result; and the determining unit is used for determining a service checking result corresponding to the service rule to be checked according to the analysis result.
In one or more embodiments of the present description, the apparatus may further include: and the reloading module is used for reloading the rule analyzer with the support array as the operation symbol of the operation parameter before inputting the rule expression of the service rule to be checked and the service parameter corresponding to the service rule to be checked into the rule analyzer for analysis.
In one or more embodiments of the present description, the apparatus may further include: the storage module is used for putting the business rules to be checked into a queue and putting the business parameters into a rule engine context after the business rules to be checked and the business parameters are obtained; the checking module is used for: consuming the business rules to be checked in the queue, acquiring the business parameters corresponding to the business rules to be checked from the context of a rule engine, and inputting the business rules to be checked and the business parameters corresponding to the business rules to be checked into a rule analyzer to obtain an analysis result; the determining unit is used for determining that the service rule to be checked passes checking in response to the analysis result being analysis pass, and determining that the service rule to be checked fails checking in response to the analysis result being analysis failure.
In one or more embodiments of the present description, the apparatus may further include: the acquisition module is used for acquiring the service data from a service system before determining a service rule set matched with a service to be checked, wherein the service to be checked is a service which is processed and completed in the service system, and the service data is a service context generated in the process of processing the service to be checked.
In one or more embodiments of the present description, the apparatus may further include: and the conversion module is used for converting the service data into key-value pairs after the service data is acquired, wherein in the key-value pairs, keys comprise corresponding attribute information of the service data, and values represent values of the service data.
Fig. 6 is a schematic diagram illustrating a more specific hardware structure of an electronic device according to one or more embodiments of the present disclosure, where, as shown in fig. 6, the 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.
Computer-readable media of the present embodiments, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
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 present disclosure, features in the above embodiments or in different embodiments may also be combined, steps may be implemented in any order, and there are many other variations of the different aspects of the present disclosure 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 in the provided figures for simplicity of illustration and discussion, and so as not to obscure the disclosure. Furthermore, devices may be shown in block diagram form in order to avoid obscuring the disclosure, 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 disclosure 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 disclosure, it should be apparent to one skilled in the art that the disclosure 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 disclosure 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 (e.g., dynamic ram (dram)) may use the discussed embodiments.
The embodiments of the present disclosure are intended to embrace all such alternatives, modifications and variances that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalents, improvements, and the like that may be made within the spirit and principles of the disclosure are intended to be included within the scope of the disclosure.
Claims (17)
1. A business checking method based on a rule engine comprises the following steps:
determining a business rule set matched with a business to be checked;
traversing each service rule in the service rule set, and inputting the service data of the service to be checked into at least one data node, so that the at least one data node determines the service rule to be checked based on the service rule set and determines the service parameter corresponding to each service rule to be checked based on the service data;
and operating each business rule to be checked according to the business parameters corresponding to each business rule to be checked to obtain a business checking result corresponding to each business rule to be checked.
2. The method of claim 1, determining a set of business rules that match the business to be checked, comprising:
and determining a business rule set matched with the application identifier of the application to which the business to be checked belongs and/or the business scene of the business to be checked.
3. The method of claim 1, wherein the first and second light sources are selected from the group consisting of,
and each data node screens the service rule set to be checked based on respective preset screening conditions to obtain the service rule to be checked, and screens the service data to obtain the service parameter corresponding to the service rule to be checked based on respective preset value-taking expressions.
4. The method of claim 1, wherein the operating each business rule to be checked according to the business parameter corresponding to each business rule to be checked to obtain the business checking result corresponding to each business rule to be checked, comprises:
inputting a rule expression of the service rule to be checked and a service parameter corresponding to the service rule to be checked into a rule analyzer for analysis to obtain an analysis result;
and determining a service checking result corresponding to the service rule to be checked according to the analysis result.
5. The method of claim 4, further comprising:
before inputting a rule expression of a business rule to be checked and a business parameter corresponding to the business rule to be checked into a rule analyzer for analysis, the rule analyzer reloads a support array as an operation symbol of an operation parameter.
6. The method of claim 1, further comprising:
after obtaining the business rule to be checked and the business parameters, putting the business rule to be checked into a queue, and putting the business parameters into a rule engine context;
the method comprises the following steps of operating each business rule to be checked according to business parameters corresponding to each business rule to be checked to obtain a business checking result corresponding to each business rule to be checked, and comprises the following steps:
consuming the business rules to be checked in the queue, acquiring the business parameters corresponding to the business rules to be checked from the context of a rule engine, and inputting the business rules to be checked and the business parameters corresponding to the business rules to be checked into a rule analyzer to obtain an analysis result;
determining a service checking result corresponding to the service rule to be checked according to the analysis result, wherein the service checking result comprises the following steps:
and determining that the service rule to be checked passes checking in response to the analysis result being analysis pass, and determining that the service rule to be checked fails checking in response to the analysis result being analysis failure.
7. The method of claim 1, further comprising:
before determining a service rule set matched with a service to be checked, acquiring the service data from a service system, wherein the service to be checked is a service which is processed and completed in the service system, and the service data is a service context generated in the process of processing the service to be checked.
8. The method of claim 7, further comprising:
and after the business data is acquired, converting the business data into key-value pairs, wherein in the key-value pairs, keys comprise corresponding attribute information of the business data, and values represent values of the business data.
9. A rules engine based business collation apparatus comprising:
the first determining module is used for determining a business rule set matched with the business to be checked;
the second determining module is used for traversing each service rule in the service rule set and inputting the service data of the service to be checked into at least one data node so that the at least one data node determines the service rule to be checked based on the service rule set and determines the service parameter corresponding to each service rule to be checked based on the service data;
and the checking module is used for operating each business rule to be checked according to the business parameters corresponding to each business rule to be checked to obtain the business checking result corresponding to each business rule to be checked.
10. The apparatus of claim 9, the first determination module to:
and determining a business rule set matched with the application identifier of the application to which the business to be checked belongs and/or the business scene of the business to be checked.
11. The apparatus of claim 9, wherein the first and second electrodes are disposed on opposite sides of the substrate,
and each data node screens the service rule set to be checked based on respective preset screening conditions to obtain the service rule to be checked, and screens the service data to obtain the service parameter corresponding to the service rule to be checked based on respective preset value-taking expressions.
12. The apparatus of claim 9, the reconciliation module, comprising:
the input unit is used for inputting the rule expression of the service rule to be checked and the service parameter corresponding to the service rule to be checked into the rule analyzer for analysis to obtain an analysis result;
and the determining unit is used for determining a service checking result corresponding to the service rule to be checked according to the analysis result.
13. The apparatus of claim 12, the apparatus further comprising:
and the reloading module is used for reloading the rule analyzer with the support array as the operation symbol of the operation parameter before inputting the rule expression of the service rule to be checked and the service parameter corresponding to the service rule to be checked into the rule analyzer for analysis.
14. The apparatus of claim 9, the apparatus further comprising:
the storage module is used for putting the business rules to be checked into a queue and putting the business parameters into a rule engine context after the business rules to be checked and the business parameters are obtained;
the checking module is used for:
consuming the business rules to be checked in the queue, acquiring the business parameters corresponding to the business rules to be checked from the context of a rule engine, and inputting the business rules to be checked and the business parameters corresponding to the business rules to be checked into a rule analyzer to obtain an analysis result;
the determining unit is used for determining that the service rule to be checked passes checking in response to the analysis result being analysis pass, and determining that the service rule to be checked fails checking in response to the analysis result being analysis failure.
15. The apparatus of claim 9, the apparatus further comprising:
the acquisition module is used for acquiring the service data from a service system before determining a service rule set matched with a service to be checked, wherein the service to be checked is a service which is processed and completed in the service system, and the service data is a service context generated in the process of processing the service to be checked.
16. The apparatus of claim 15, the apparatus further comprising:
and the conversion module is used for converting the service data into key-value pairs after the service data is acquired, wherein in the key-value pairs, keys comprise corresponding attribute information of the service data, and values represent values of the service data.
17. 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 rules engine based business checking method of any one of claims 1 to 8 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010091156.0A CN111260336B (en) | 2020-02-13 | 2020-02-13 | Service checking method, device and equipment based on rule engine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010091156.0A CN111260336B (en) | 2020-02-13 | 2020-02-13 | Service checking method, device and equipment based on rule engine |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111260336A true CN111260336A (en) | 2020-06-09 |
| CN111260336B CN111260336B (en) | 2023-07-04 |
Family
ID=70954497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010091156.0A Active CN111260336B (en) | 2020-02-13 | 2020-02-13 | Service checking method, device and equipment based on rule engine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111260336B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112365236A (en) * | 2020-11-16 | 2021-02-12 | 浪潮云信息技术股份公司 | Method for handling recommended item list applied to investment item handling system |
| CN112380401A (en) * | 2021-01-14 | 2021-02-19 | 蚂蚁智信(杭州)信息技术有限公司 | Service data checking method and device |
| CN112527838A (en) * | 2020-12-10 | 2021-03-19 | 联通(浙江)产业互联网有限公司 | Business decision method, device, equipment and storage medium based on rule engine |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030084428A1 (en) * | 2001-06-26 | 2003-05-01 | International Business Machines Corporation | Rule based engine for validating financial transactions |
| US7340406B1 (en) * | 2000-09-21 | 2008-03-04 | Netscape Communications Corporation | Business rules system |
| CN103544074A (en) * | 2012-07-09 | 2014-01-29 | 阿里巴巴集团控股有限公司 | Method and device for verifying service |
| CN104915812A (en) * | 2014-03-13 | 2015-09-16 | 阿里巴巴集团控股有限公司 | Warehouse delivery routing method and device for service processing process |
| US20170039553A1 (en) * | 2015-08-04 | 2017-02-09 | Accenture Global Services Limited | Data reconciliation |
| CN108376064A (en) * | 2016-11-24 | 2018-08-07 | 阿里巴巴集团控股有限公司 | The correlation technique of rule engine system and regulation engine |
| CN108446143A (en) * | 2018-02-28 | 2018-08-24 | 万惠投资管理有限公司 | Event-handling method and device |
| CN109558134A (en) * | 2017-09-27 | 2019-04-02 | 北京京东尚科信息技术有限公司 | The method and apparatus of business datum verification |
| CN109614262A (en) * | 2018-09-25 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Business method of calibration, device and computer readable storage medium |
| CN109615384A (en) * | 2018-11-01 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Generation method, device and the server of timeliness verification rule |
| US20190129765A1 (en) * | 2017-10-30 | 2019-05-02 | Microsoft Technology Licensing, Llc | Dynamic rule-based transformation of api calls |
| WO2019179056A1 (en) * | 2018-03-18 | 2019-09-26 | 平安科技（深圳）有限公司 | Configurable system and method based on rule engine, device, and storage medium |
| CN110297840A (en) * | 2019-05-22 | 2019-10-01 | 平安银行股份有限公司 | Data processing method, device, equipment and the storage medium of rule-based engine |
-
2020
- 2020-02-13 CN CN202010091156.0A patent/CN111260336B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7340406B1 (en) * | 2000-09-21 | 2008-03-04 | Netscape Communications Corporation | Business rules system |
| US20030084428A1 (en) * | 2001-06-26 | 2003-05-01 | International Business Machines Corporation | Rule based engine for validating financial transactions |
| CN103544074A (en) * | 2012-07-09 | 2014-01-29 | 阿里巴巴集团控股有限公司 | Method and device for verifying service |
| CN104915812A (en) * | 2014-03-13 | 2015-09-16 | 阿里巴巴集团控股有限公司 | Warehouse delivery routing method and device for service processing process |
| US20170039553A1 (en) * | 2015-08-04 | 2017-02-09 | Accenture Global Services Limited | Data reconciliation |
| CN108376064A (en) * | 2016-11-24 | 2018-08-07 | 阿里巴巴集团控股有限公司 | The correlation technique of rule engine system and regulation engine |
| CN109558134A (en) * | 2017-09-27 | 2019-04-02 | 北京京东尚科信息技术有限公司 | The method and apparatus of business datum verification |
| US20190129765A1 (en) * | 2017-10-30 | 2019-05-02 | Microsoft Technology Licensing, Llc | Dynamic rule-based transformation of api calls |
| CN108446143A (en) * | 2018-02-28 | 2018-08-24 | 万惠投资管理有限公司 | Event-handling method and device |
| WO2019179056A1 (en) * | 2018-03-18 | 2019-09-26 | 平安科技（深圳）有限公司 | Configurable system and method based on rule engine, device, and storage medium |
| CN109614262A (en) * | 2018-09-25 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Business method of calibration, device and computer readable storage medium |
| CN109615384A (en) * | 2018-11-01 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Generation method, device and the server of timeliness verification rule |
| CN110297840A (en) * | 2019-05-22 | 2019-10-01 | 平安银行股份有限公司 | Data processing method, device, equipment and the storage medium of rule-based engine |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112365236A (en) * | 2020-11-16 | 2021-02-12 | 浪潮云信息技术股份公司 | Method for handling recommended item list applied to investment item handling system |
| CN112527838A (en) * | 2020-12-10 | 2021-03-19 | 联通(浙江)产业互联网有限公司 | Business decision method, device, equipment and storage medium based on rule engine |
| CN112527838B (en) * | 2020-12-10 | 2022-11-15 | 联通(浙江)产业互联网有限公司 | Business decision method, device, equipment and storage medium based on rule engine |
| CN112380401A (en) * | 2021-01-14 | 2021-02-19 | 蚂蚁智信(杭州)信息技术有限公司 | Service data checking method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111260336B (en) | 2023-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8359576B2 (en) | Using symbolic execution to check global temporal requirements in an application | |
| CN111260336B (en) | Service checking method, device and equipment based on rule engine | |
| CN112104709B (en) | Intelligent contract processing method, device, medium and electronic equipment | |
| CN103577168A (en) | Test case creation system and method | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN108415826B (en) | Application testing method, terminal device and computer readable storage medium | |
| CN112181804A (en) | Parameter checking method, equipment and storage medium | |
| CN112214210A (en) | Logistics business rule engine and configuration method, device, equipment and storage medium thereof | |
| CN114116496A (en) | Automatic testing method, device, equipment and medium | |
| CN111767217A (en) | JS unit test case generation method and device | |
| CN114579452A (en) | Interface influence detection method and related equipment | |
| CN117076338B (en) | Method and system for dynamically debugging Linux kernel based on kprobe | |
| US9064042B2 (en) | Instrumenting computer program code by merging template and target code methods | |
| CN115618363B (en) | Vulnerability path mining method and related equipment | |
| CN112861033A (en) | Method and device for executing service | |
| CN116755669A (en) | Low code development method and tool based on DSL language operation model | |
| CN116361793A (en) | Code detection method, device, electronic equipment and storage medium | |
| CN106528179B (en) | A kind of static recognition methods of java class dependence | |
| CN112861134B (en) | Vulnerability detection method, device, equipment and medium based on optimization variation strategy | |
| CN115022312A (en) | Method and device for realizing multiple intelligent contract engines, electronic equipment and storage medium | |
| CN113032256A (en) | Automatic test method, device, computer system and readable storage medium | |
| CN111639028A (en) | Account checking rule script test method, device, engine and storage medium | |
| CN111151008A (en) | Game operation data verification method, device, configuration background and medium | |
| CN111784521B (en) | Data processing method, device, equipment and system based on cash flow test | |
| CN116661758B (en) | Method, device, electronic equipment and medium for optimizing log framework configuration |
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 |