CN110009173B - Business rule processing method and device - Google Patents
Business rule processing method and device Download PDFInfo
- Publication number
- CN110009173B CN110009173B CN201811512059.3A CN201811512059A CN110009173B CN 110009173 B CN110009173 B CN 110009173B CN 201811512059 A CN201811512059 A CN 201811512059A CN 110009173 B CN110009173 B CN 110009173B
- Authority
- CN
- China
- Prior art keywords
- rule
- business rule
- field
- business
- application scenario
- 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
-
- 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- 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/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- Finance (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Marketing (AREA)
- Computer Security & Cryptography (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Technology Law (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present disclosure provides a method for processing a business rule, including: determining at least one second application scenario to which the first business rule is applicable based on a rule type of the first business rule for the first application scenario; acquiring a field conversion rule of each field in the first service rule from a first application scene to each second application scene in at least one second application scene; and based on the obtained field conversion rule, performing field conversion from the first application scene to each second application scene in at least one second application scene on each field of the first business rule to obtain at least one second business rule, wherein each second business rule in the at least one second business rule corresponds to one second application scene. By the method, the second business rule applicable to other applicable second application scenes can be obtained based on the existing first business rule without rewriting, so that the universality of the business rule and the formulation efficiency of the business rule are improved.
Description
Technical Field
The present disclosure relates generally to the field of computer technology, and more particularly, to a method and apparatus for business rule processing.
Background
When an enterprise performs business processing, in order to improve the business processing efficiency of a business processing system, a business rule maker is usually required to write a large number of business processing strategies or business rules to guide the business processing system to perform business processing. Generally, the written business rules are all applicable to a specific application scenario, for example, the business rules applicable to a single country, the business rules applicable to credit card cashing, or the business rules for APP marketing ticket issuing.
In this case, even if the business processing logic of the business rules is the same, the specific form of the business rules in each application scenario may be different. For example, for a business transaction rule in which business processing logics are the same in different countries, assuming that the business rule includes limits of a transaction amount and a transaction time, for example, assuming that the transaction amount is limited to be greater than 10 ten thousand renminbi and the transaction time exceeds beijing time 16 00, the specific forms of the business rules may be different due to differences in currency units and time zones between china and the united states, for example, china employs renminbi and beijing time, and united states employs U.S. dollars and united states time. Therefore, for different application scenarios, in the case that the service processing logics of the service rules are the same, it is also necessary to rewrite new service rules for each application scenario, which requires a lot of time and effort, thereby resulting in inefficient business rule making.
Disclosure of Invention
In view of the foregoing, the present disclosure provides a business rule processing method and apparatus. By using the method and the device for processing the business rules, other applicable second application scenes of the rule types of the first business rules applicable to the first application scene are determined, and the field conversion rules from the first application scene to the other applicable second application scenes are utilized to carry out field conversion on each field in the first business rules so as to obtain the second business rules applicable to the other applicable second application scenes, so that the second business rules applicable to the other applicable second application scenes can be obtained based on the existing first business rules without rewriting, and the universality of the business rules and the formulation efficiency of the business rules are improved.
According to an aspect of the present disclosure, there is provided a method for business rule processing, comprising: determining at least one second application scenario to which a first business rule for a first application scenario is applicable based on a rule type of the first business rule, the first business rule comprising at least one field comprising at least a rule type field and an application scenario field; acquiring a field conversion rule of each field in the first service rule from the first application scene to each second application scene in the at least one second application scene; and performing field conversion from the first application scenario to each of the at least one second application scenario for each field of the first business rule based on the obtained field conversion rule to obtain at least one second business rule, wherein each of the at least one second business rule corresponds to one second application scenario.
Optionally, in an example of the above aspect, the method may further include: and recommending the obtained at least one second business rule to the user.
Optionally, in an example of the above aspect, before recommending the obtained at least one second business rule to the user, the method may further include: for each second business rule in the obtained at least one second business rule, obtaining at least one matching business rule from a business rule database, wherein recommending the obtained at least one second business rule to a user comprises: recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matched business rule to the user.
Optionally, in an example of the above aspect, before recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matching business rule to the user, the method may further include: providing each second business rule of the obtained at least one second business rule and the corresponding at least one matching business rule to a user for selection by the user, wherein recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matching business rule to the user comprises: and recommending the business rule selected by the user to the user.
Optionally, in an example of the above aspect, before obtaining a field conversion rule that each field in the first business rule is converted from the first application scenario to each of the at least one second application scenario, the method may further include: judging whether a second business rule corresponding to the first business rule and aiming at partial or all second application scenes in the at least one second application scene exists in a business rule database or not; and when second business rules corresponding to the first business rules and aiming at all second application scenes in the at least one second application scene exist in the business rule database, acquiring the second business rules corresponding to the at least one second application scene from the business rule database.
Optionally, in an example of the above aspect, before obtaining a field conversion rule that each field in the first business rule is converted from the first application scenario to each of the at least one second application scenario, the method may further include: when a second business rule corresponding to the first business rule exists in the business rule database and aiming at a part of second application scenes in the at least one second application scene, acquiring a second business rule corresponding to the part of second application scenes from the business rule database, wherein acquiring a field conversion rule for converting each field in the first business rule from the first application scene to each second application scene in the at least one second application scene comprises: obtaining a field conversion rule for converting each field in the first business rule from the first application scene to each of the remaining second application scenes in the at least one second application scene; and based on the determined field conversion rule, performing field conversion from the first application scenario to each of the at least one second application scenario for each field of the first business rule to obtain at least one second business rule comprises: based on the obtained field conversion rule, performing field conversion from the first application scenario to each of the remaining second application scenarios on each field of the first business rule to obtain a corresponding second business rule.
Optionally, in an example of the above aspect, the application scenario is a country-based application scenario, the first business rule includes at least a region field, the field conversion rule for the region field performs field conversion based on a region similarity, and the region similarity is determined based on a region attribute of a region indicated by a field value of the region field of the first business rule.
Optionally, in one example of the above aspect, the region attribute includes at least one of the following region attributes: a geographic location of the region; regional ethnic composition; size of the regional population; the influence degree of the region country; and income of people in the area.
According to another aspect of the present disclosure, there is provided an apparatus for business rule processing, comprising: an application scenario determination unit configured to determine at least one second application scenario to which a first business rule for a first application scenario is applicable based on a rule type of the first business rule, the first business rule comprising at least one field comprising at least a rule type field and an application scenario field; a field conversion rule obtaining unit configured to obtain a field conversion rule of each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario; and a rule conversion unit configured to perform field conversion from the first application scenario to each of the at least one second application scenario for each field of the first business rule based on the obtained field conversion rule to obtain at least one second business rule, wherein each of the at least one second business rule corresponds to one type of second application scenario.
Optionally, in an example of the above aspect, the apparatus may further include: and the rule recommending unit is configured to recommend the obtained at least one second business rule to the user.
Optionally, in an example of the above aspect, the apparatus may further include: a rule matching unit configured to obtain, for each of the obtained at least one second business rule, at least one matching business rule from a business rule database before recommending the obtained at least one second business rule to the user, and the rule recommending unit is configured to: recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matched business rule to the user.
Optionally, in an example of the above aspect, the apparatus may further include: a rule providing unit configured to provide each of the obtained at least one second business rule and the corresponding at least one matching business rule to a user for selection by the user before recommending each of the obtained at least one second business rule and the corresponding at least one matching business rule to the user, and the rule recommending unit is configured to: and recommending the business rules selected by the user to the user.
Optionally, in an example of the above aspect, the apparatus may further include: a determining unit, configured to determine whether a second business rule corresponding to the first business rule exists in a business rule database for a part or all of the at least one second application scenario before a field conversion rule for each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario is obtained; and a rule obtaining unit configured to obtain, when a second business rule corresponding to the first business rule exists in the business rule database for all second application scenarios in the at least one second application scenario, a second business rule corresponding to the at least one second application scenario from the business rule database.
Optionally, in an example of the above aspect, the rule obtaining unit is further configured to: when a second business rule corresponding to the first business rule exists in the business rule database and aiming at a part of second application scenes in the at least one second application scene, acquiring the second business rule corresponding to the part of second application scenes from the business rule database, wherein the field conversion rule acquisition unit is configured to: obtaining a field conversion rule for converting each field in the first business rule from the first application scene to each of the remaining second application scenes in the at least one second application scene; and the rule conversion unit is configured to: and performing field conversion from the first application scene to each of the remaining second application scenes on each field of the first business rule based on the acquired field conversion rule to obtain a corresponding second business rule.
According to another aspect of the present disclosure, there is provided a computing device comprising: at least one processor, and a memory coupled with the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform a method for business rule processing as described above.
According to another aspect of the present disclosure, there is provided a non-transitory machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the method for business rule processing as described above.
Drawings
A further understanding of the nature and advantages of the present disclosure may be realized by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals.
FIG. 1 shows a flow diagram of a business rule processing method according to an embodiment of the present disclosure;
FIG. 2 illustrates an example schematic of a business rule according to an embodiment of this disclosure;
FIG. 3 shows a flow diagram of a business rule processing method according to another embodiment of the present disclosure;
FIG. 4 shows a block diagram of a business rule processing apparatus according to an embodiment of the present disclosure;
FIG. 5 shows a block diagram of a business rule processing apparatus according to another embodiment of the present disclosure; and
FIG. 6 illustrates a block diagram of a computing device for business rule processing in accordance with an embodiment of the disclosure.
Detailed Description
The subject matter described herein will now be discussed with reference to example embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand the subject matter described herein and are not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as needed. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with respect to some examples may also be combined in other examples.
As used herein, the term "include" and its variants mean open-ended terms, meaning "including but not limited to. The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first," "second," and the like may refer to different or the same object. Other definitions, whether explicit or implicit, may be included below. Unless the context clearly dictates otherwise, the definition of a term is consistent throughout the specification.
When the existing business rules are customized, the customized business rules are all suitable for a certain specific application scene. In this case, even if the business processing logic of the business rules is the same, the specific form of the business rules in each application scenario may be different. Therefore, in the case that the business processing logics of the business rules are the same for different application scenarios, a new business rule needs to be rewritten for each application scenario, which requires a lot of time and effort, resulting in inefficient business rule making.
Considering that many business rules have universality and can be applied to many different application scenarios, the business processing logics of the business rules used in different application scenarios are the same, and the difference is only in the concrete expression form of the business rules. In view of this situation, the present disclosure provides a business rule processing scheme. In the service rule processing scheme, based on the existing service rule, other application scenes to which the service rule is applicable are determined by using the pre-established service rule-applicable application scene corresponding relation, the field conversion rule aiming at the service rule field between the current application scene and the applicable other application scenes of the service rule is determined, and then the service rule is converted into the corresponding service rule under each applicable other application scene by using the determined field conversion rule, so that the universality of the service rule and the formulation efficiency of the service rule are improved.
A business rule processing method and apparatus according to an embodiment of the present disclosure will be described in detail below with reference to the accompanying drawings.
FIG. 1 shows a flow diagram of one example 100 of a business rule processing method according to an embodiment of the disclosure.
As shown in fig. 1, at block 110, at least one second application scenario to which a first business rule is applicable is determined based on a rule type of the first business rule for the first application scenario. In the present disclosure, the first business rule may include at least one field including at least a rule type field and an application scenario field. The rule type field is used for recording rule type information of the business rule, and the application scenario field is used for recording an application scenario applied by the business rule. In the present disclosure, the business rule may be a business transaction rule, a business wind control rule, a business operation rule, or other business processing rule. Here, the first business rule may be a business rule input by, for example, a business operator or a business rule maker via an input device or a business rule written via a writing device.
FIG. 2 illustrates an example schematic of a business rule according to an embodiment of this disclosure. As shown in FIG. 2, a business rule 200 is a business transaction rule that includes 5 fields: a rule type field 210, an amount field 220, a time field 230, a region field 240, and an application scenario field 250. The rule type field 210 is used to record rule type information for the business rule 200. The amount field 220 is used to record transaction amount rule information for the business rule 200. The time field 230 is used to record transaction time rule information for the business rule 200. The region field 240 is used to record transaction region rule information for the business rule 200. The application context field 250 is used to record application context information applied by the business rule 200. Each field of the business rule 200 has a field value, e.g., the field value of the rule type field 210 is "offline Payment," which indicates that the business rule type of the business rule 200 is offline Payment. The value of the amount field 220 is "amount ≧ 100k", which indicates the transaction amount of the business transaction in the business rule 200 is 100k or more. The field value of the time field 230 is "transaction time ≧ 16 00", which indicates that the transaction time of the service transaction in the service rule 200 is equal to or greater than 16. The field value of the region field 240 is "{ national Tibet, sinkiang, china }", which indicates that the transaction region for the business transaction in the business rules 200 is national Tibet and Sinkiang. The field value of the application scenario field 250 is "China," which indicates that the business rule 200 applies to China.
In one example of the present disclosure, determining, based on a rule type of a first business rule for a first application scenario, at least one second application scenario to which the first business rule is applicable may include: based on the rule type of the first business rule, obtaining an applicable application scenario of the rule type from a rule type-applicable application scenario correspondence table/rule type-applicable application scenario correspondence database, thereby determining at least one second application scenario to which the first business rule is applicable. The rule type-applicable application scenario correspondence table/rule type-applicable application scenario correspondence database may be pre-created, for example, by business personnel or business rule making personnel. In the correspondence table/correspondence database, the correspondence between the rule type and the applicable application scenario may be a one-to-many correspondence or a many-to-many correspondence.
Further, in another example of the present disclosure, determining at least one second application scenario to which the first business rule is applicable based on the rule type of the first business rule for the first application scenario may include: the rule type of the first business rule is provided to an application scenario determination model to determine an applicable application scenario for the rule type. Here, the application scenario determination model may be trained using rule type information of the historical business rules after application scenario tagging.
After determining the at least one second application scenario to which the first business rule is applicable as described above, at block 120, a field transformation rule is obtained for each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario. For example, a field conversion rule from one application scenario to another is looked up from a field conversion rule table created in advance.
Then, at block 130, based on the obtained field conversion rule, field conversion from the first application scenario to each of the at least one second application scenario is performed on each field of the first business rule, thereby obtaining at least one second business rule. Each second business rule of the at least one second business rule corresponds to a second application scenario.
A business rule processing method according to an embodiment of the present disclosure is explained below by taking the business rule 200 shown in fig. 2 as an example.
For the business rule 200 shown in fig. 2, the rule type of the business rule 200 is "offline payment", and the application scenario of the business rule 200 is "china", i.e., the first application scenario is "china". In other words, the application scenario of the business rules 200 is a country-based application scenario. Further, since offline payment is currently applicable to, for example, the united states, europe, southeast asian countries, etc., application scenarios in which offline payment is applicable include china, the united states, europe, and southeast asian countries. For ease of explanation, the following description will be made with respect to china, the united states and europe as representative of offline payment applications. Accordingly, a business person or a business rule making person creates a correspondence in advance between the rule type "off-line payment" and the applicable application scenario "china", "usa" and "europe", and stores the created correspondence in the rule type-applicable application scenario correspondence table/rule type-applicable application scenario correspondence database.
After the business rule 200 is acquired, for example, after the business rule 200 input (or written) by the business rule making personnel is received, based on the rule type "offline payment" of the business rule 200, the corresponding application scenarios "china", "usa" and "europe" are found out from the rule type-applicable application scenario correspondence table, and then the application scenario "china" (i.e., the first application scenario) to which the business rule 200 belongs is taken out from the found corresponding application scenarios "china", "usa" and "europe", thereby obtaining at least one second application scenario "usa" and "europe" which are applicable.
After acquiring the applicable at least one second application scenario "us" and "europe", acquiring a field conversion rule of each field in the first business rule from the first application scenario "china" to the second application scenario "us" and "europe".
For example, for the rule type field 210, the field conversion rule from the first application scenario "china" to the second application scenarios "usa" and "europe" may be "language conversion," i.e., "convert from chinese to english. For the amount field 220, the field conversion rule from the first application scenario "china" to the second application scenario "usa" and "europe" may be "currency unit conversion", i.e., the field conversion rule from the first application scenario "china" to the second application scenario "usa" is "dollars in money amount converted from rmb to the equivalent", and the field conversion rule from the first application scenario "china" to the second application scenario "europe" is "euros in money amount converted from rmb to the equivalent". For the time field 230, the field conversion rule from the first application scenario "china" to the second application scenario "usa" and "europe" may be "time zone conversion", i.e., the field conversion rule from the first application scenario "china" to the second application scenario "usa" is "convert time from beijing time to us time", and the field conversion rule from the first application scenario "china" to the second application scenario "europe" is "convert time from beijing time to european time". For example, from Beijing hours 4 PM to U.S. hours 4 PM, and from Beijing hours 4 PM to European hours 4 PM.
For the region field 240, the field conversion rules from the first application scenario "china" to the second application scenarios "usa" and "europe" may include: region field conversion is performed based on region similarity. The region similarity is determined based on a region attribute of a region indicated by a field value of a region field of the first business rule. Specifically, in the field conversion for the region field 240, first, regions having high similarity to chinese tibetan and chinese Xinjiang (i.e., matching regions) among the respective regions of the united states and europe are determined based on region attributes of the regions indicated by the field values of the region field of the first business rule, for example, region attributes of chinese tibetan and chinese Xinjiang. And then, replacing the field value of the region field of the first business rule by using the determined matching region in each second application scene to obtain the field value of the region field corresponding to the second business rule in each second application scene. In the present disclosure, the regional attributes may include at least one of the following regional attributes: a geographic location of the region; regional ethnic composition; the size of the population in the region; the influence degree of the region country; and income of people in the area.
For the application scenario field 250, a field conversion rule from the first application scenario "china" to the second application scenarios "usa" and "europe" may be "application scenario conversion", i.e., converting a field value of the application scenario field from "china" to "usa" or "europe".
After the field conversion rule of each field in the first business rule from the first application scenario "china" to the second application scenario "usa" and "europe" is obtained, the obtained field conversion rule is used to perform field conversion on each field of the first business rule, so that the second business rule applicable to the usa and the second business rule applicable to europe are obtained. The resulting second business rule applicable to the united states is: "Offline Payments". Lambda "Amount ≧ 14400". Lambda "transition Hour ≧ 16". Lambda "District ∈ { Seattle }". USA ", and the second business rule obtained for the United states is: "Offline Payments" [ lambda ] Amount ≧ 12714 "[ lambda ] transformation Hour ≧ 16" [ lambda ] District ∈ { Paris B } "[ lambda" EP ".
Here, it is to be noted that, in the field conversion of each business rule described above, language conversion is included, that is, a language expression of a field value of each field is modified to be expressed in a country language of a corresponding country application scenario.
FIG. 3 shows a flow diagram of one example 300 of a business rule processing method according to another embodiment of the present disclosure.
As shown in fig. 3, at block 310, at least one second application scenario to which a first business rule is applicable is determined based on a rule type of the first business rule for the first application scenario. The operations of block 310 may refer to the operations of block 110 described above with reference to FIG. 1.
After determining the at least one second application scenario to which the first business rule is applicable, at block 320, it is determined whether a second business rule corresponding to the first business rule exists in the business rule database for some or all of the determined at least one second application scenario. Here, the business rule database is used for correspondingly storing the first business rule and the converted second business rule.
When it is determined at block 320 that the second business rules for all the second application scenarios exist in the business rule database, at block 330, each second business rule corresponding to the at least one second application scenario is obtained from the business rule database.
When it is determined at block 320 that there is no second business rule in the business rule database for any of the at least one second application scenario, at block 340, a field transformation rule is obtained for each field in the first business rule from the first application scenario to each of the at least one second application scenario. Next, at block 350, based on the obtained field transformation rules, field transformation from the first application scenario to each of the at least one second application scenario is performed on each field of the first business rule, thereby obtaining at least one second business rule.
When it is determined at block 320 that a second business rule corresponding to the first business rule exists in the business rule database for a portion of the at least one second application scenario, at block 360, a second business rule corresponding to the portion of the second application scenario is obtained from the business rule database. Next, at block 370, a field transformation rule is obtained for each field in the first business rule to be transformed from the first application scenario to each of the remaining second application scenarios in the at least one second application scenario.
Then, at block 380, based on the determined field transformation rules, field transformations are performed on the respective fields of the first business rule from the first application scenario to respective ones of the remaining second application scenarios to derive corresponding second business rules.
The business rule processing method according to the present disclosure is described above with reference to fig. 1 and 3. It should be noted that fig. 1 and 3 illustrate only one embodiment of the business rule processing method according to the present disclosure, and in other embodiments of the present disclosure, the insurance claim text processing method illustrated in fig. 1 and 3 may be modified.
For example, in another embodiment of the present disclosure, after obtaining at least one second business rule, the method may further include: and recommending the obtained at least one second business rule to the user. Furthermore, in another embodiment of the present disclosure, the method may further include: acquiring at least one matched service rule from a service rule database aiming at each second service rule in the obtained at least one second service rule; and recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matching business rule to the user. Here, for each of the obtained at least one second business rule, obtaining at least one matching business rule from the business rule database may include: and aiming at each second business rule in the obtained at least one second business rule, acquiring at least one matched business rule from a business rule database based on the text similarity.
In addition, in another embodiment of the present disclosure, before recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matching business rule to the user, the method may further include: and providing each second business rule in the obtained at least one second business rule and the corresponding at least one matching business rule for the user to select. Then, the business rule selected by the user is recommended to the user.
FIG. 4 shows a block diagram of a business rule processing apparatus 400 according to an embodiment of the present disclosure. As shown in fig. 4, the business rule processing apparatus 400 includes an application scenario determination unit 410, a field conversion rule acquisition unit 420, and a rule conversion unit 430.
The application scenario determination unit 410 is configured to determine at least one second application scenario to which a first traffic rule is applicable based on a rule type of the first traffic rule for a first application scenario, the first traffic rule comprising at least one field comprising at least a rule type field and an application scenario field. The operation of the application scenario determination unit 410 may refer to the operation of the block 110 described above with reference to fig. 1.
The field conversion rule obtaining unit 420 is configured to obtain a field conversion rule of each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario. The operation of the field conversion rule obtaining unit 420 may refer to the operation of the block 120 described above with reference to fig. 1.
The rule conversion unit 430 is configured to perform a field conversion for each field of the first business rule from the first application scenario to each of at least one second application scenario to obtain at least one second business rule, based on the determined field conversion rule, each of the at least one second business rule corresponding to one of the second application scenarios. The operation of the rule conversion unit 430 may refer to the operation of block 130 described above with reference to fig. 1.
FIG. 5 shows a block diagram of a business rule processing apparatus 500 according to another embodiment of the present disclosure. As shown in fig. 5, the business rule processing apparatus 500 includes an application scenario determining unit 510, a determining unit 520, a rule obtaining unit 530, a field conversion rule obtaining unit 540, a rule converting unit 550, a rule matching unit 560, a rule providing unit 570, and a rule recommending unit 580.
The application scenario determination unit 510 is configured to determine at least one second application scenario to which a first business rule is applicable based on a rule type of the first business rule for a first application scenario, the first business rule comprising at least one field comprising at least a rule type field and an application scenario field. The operation of the application scenario determination unit 510 may refer to the operation of block 310 described above with reference to fig. 3.
The determining unit 520 is configured to determine whether a second business rule corresponding to the first business rule exists in the business rule database for a part or all of the at least one second application scenario before acquiring a field conversion rule of each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario. The operation of the determination unit 520 may refer to the operation of the block 320 described above with reference to fig. 3.
The rule obtaining unit 530 is configured to obtain, when second business rules for all second application scenarios in the at least one second application scenario exist in the business rule database, a second business rule corresponding to the at least one second application scenario from the business rule database. Furthermore, the rule obtaining unit 530 is further configured to: when a second business rule aiming at a part of second application scenes in at least one second application scene exists in the business rule database, obtaining a second business rule corresponding to the part of second application scenes from the business rule database. The operation of the rule obtaining unit 530 may refer to the operations of blocks 330 and 360 described above with reference to fig. 3.
The field conversion rule obtaining unit 540 is configured to obtain the field conversion rule of each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario when the second business rule for any second application scenario in the at least one second application scenario does not exist in the business rule database. Furthermore, the field conversion rule obtaining unit 540 is further configured to obtain the field conversion rule of each field in the first business rule from the first application scenario to the remaining second application scenario in the at least one second application scenario when the second business rule exists in the business rule database for the partial second application scenario in the at least one second application scenario. The operation of the field conversion rule obtaining unit 540 may refer to the operations of blocks 340 and 370 described above with reference to fig. 3.
The rule conversion unit 550 is configured to, when there is no second business rule for any second application scenario in the at least one second application scenario in the business rule database, perform field conversion from the first application scenario to each second application scenario in the at least one second application scenario for each field of the first business rule based on the obtained field conversion rule to obtain the at least one second business rule, where each second business rule in the at least one second business rule corresponds to one second application scenario. Furthermore, the rule converting unit 550 is further configured to, when a second business rule for a part of the at least one second application scenario exists in the business rule database, perform field conversion from the first application scenario to remaining second application scenarios in the at least one second application scenario for each field of the first business rule based on the obtained field conversion rule to obtain a corresponding second business rule. The operation of the rule conversion unit 550 may refer to the operations of blocks 350 and 380 described above with reference to fig. 3.
The rule matching unit 560 is configured to obtain at least one matching business rule from the business rule database for each of the obtained at least one second business rule.
The rule providing unit 570 is configured to provide each of the obtained at least one second business rule and the corresponding at least one matching business rule to the user for selection by the user. The rule recommending unit 580 is configured to recommend the business rule selected by the user to the user.
It should be noted that fig. 4 and 5 illustrate only one embodiment of the business rule processing apparatus according to the present disclosure, and in other embodiments of the present disclosure, the business rule processing apparatus illustrated in fig. 5 and 6 may be modified.
For example, in another embodiment of the present disclosure, the business rule processing apparatus 500 may not include the rule matching unit 560 and the rule providing unit 570. Accordingly, the rule recommending unit 580 is configured to recommend the obtained at least one second business rule to the user.
Furthermore, in another embodiment of the present disclosure, the business rule processing apparatus 500 may not include the rule providing unit 570. Accordingly, the rule recommending unit 580 is configured to recommend the obtained at least one second business rule and the corresponding at least one matching rule to the user. Alternatively, in another embodiment of the present disclosure, the business rule processing apparatus 500 may not include the rule matching unit 560. Accordingly, the rule providing unit 570 is configured to provide each of the obtained at least one second business rule to the user for selection by the user.
As described above with reference to fig. 1 to 5, embodiments of the business rule processing method and the business rule processing apparatus according to the present disclosure are described. The business rule processing device can be realized by hardware, or can be realized by software or a combination of hardware and software.
FIG. 6 illustrates a hardware block diagram of a computing device 600 for business rule processing according to an embodiment of the disclosure. As shown in fig. 6, computing device 600 may include at least one processor 610, storage 620, memory 630, and communication interface 640, and at least one processor 610, storage 620, memory 630, and communication interface 640 are connected together via a bus 660. The at least one processor 610 executes at least one computer-readable instruction (i.e., the elements described above as being implemented in software) stored or encoded in the memory 620.
In one embodiment, computer-executable instructions are stored in the memory 620 that, when executed, cause the at least one processor 610 to: determining at least one second application scenario to which a first business rule for a first application scenario is applicable based on a rule type of the first business rule, the first business rule comprising at least one field comprising at least a rule type field and an application scenario field; acquiring a field conversion rule of each field in the first service rule from the first application scene to each second application scene in the at least one second application scene; and based on the obtained field conversion rule, performing field conversion from the first application scenario to each of the at least one second application scenario on each field of the first business rule to obtain at least one second business rule, wherein each of the at least one second business rule corresponds to one second application scenario.
It should be appreciated that the computer-executable instructions stored in the memory 620, when executed, cause the at least one processor 610 to perform the various operations and functions described above in connection with fig. 1-5 in the various embodiments of the present disclosure.
In the present disclosure, computing device 600 may include, but is not limited to: personal computers, server computers, workstations, desktop computers, laptop computers, notebook computers, mobile computing devices, smart phones, tablet computers, cellular phones, personal Digital Assistants (PDAs), handsets, messaging devices, wearable computing devices, consumer electronics, and the like.
According to one embodiment, a program product, such as a non-transitory machine-readable medium, is provided. A non-transitory machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-5 in various embodiments of the present disclosure. Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and which causes a computer or processor of the system or apparatus to read out and execute the instructions stored in the readable storage medium.
According to one embodiment, a program product, such as a non-transitory machine-readable medium, is provided. A non-transitory machine-readable medium may have instructions (i.e., the elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-5 in the various embodiments of the disclosure. Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
In this case, the program code itself read from the readable medium can realize the functions of any of the above-described embodiments, and thus the machine-readable code and the readable storage medium storing the machine-readable code form part of the present invention.
Examples of the readable storage medium include floppy disks, hard disks, magneto-optical disks, optical disks (e.g., CD-ROMs, CD-R, CD-RWs, DVD-ROMs, DVD-RAMs, DVD-RWs), magnetic tapes, nonvolatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or from the cloud via a communications network.
It will be understood by those skilled in the art that various changes and modifications may be made in the above-disclosed embodiments without departing from the spirit of the invention. Accordingly, the scope of the invention should be determined from the following claims.
It should be noted that not all steps and units in the above flows and system structure diagrams are necessary, and some steps or units may be omitted according to actual needs. The execution order of the steps is not fixed, and can be determined as required. The apparatus structures described in the foregoing embodiments may be physical structures or logical structures, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities separately, or some units may be implemented by some components in multiple independent devices together.
In the above embodiments, the hardware units or modules may be implemented mechanically or electrically. For example, a hardware unit, module or processor may comprise permanently dedicated circuitry or logic (such as a dedicated processor, FPGA or ASIC) to perform the corresponding operations. The hardware elements or processors may also comprise programmable logic or circuitry (e.g., a general-purpose processor or other programmable processor) that may be temporarily configured by software to perform corresponding operations. The specific implementation (mechanical, or dedicated permanent, or temporarily set) may be determined based on cost and time considerations.
The detailed description set forth above in connection with the appended drawings describes exemplary embodiments but does not represent all embodiments that may be practiced or fall within the scope of the claims. The term "exemplary" used throughout this specification means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous" over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (15)
1. A method for business rule processing, comprising:
determining at least one second application scenario to which a first business rule for a first application scenario is applicable based on a rule type of the first business rule, the first business rule comprising at least one field comprising a rule type field, an application scenario field, and a region field, the application scenario in question being a country-based application scenario;
acquiring a field conversion rule of each field in the first service rule from the first application scene to each second application scene in the at least one second application scene; and
based on the obtained field conversion rule, performing field conversion on each field of the first business rule from the first application scenario to each second application scenario of the at least one second application scenario to obtain at least one second business rule, wherein each second business rule of the at least one second business rule corresponds to one second application scenario, and the field conversion rule for the region field is subjected to field conversion based on region similarity determined based on region attributes of indicated regions of the region field of the first business rule.
2. The method of claim 1, further comprising:
and recommending the obtained at least one second business rule to the user.
3. The method of claim 2, wherein prior to recommending the resulting at least one second business rule to the user, the method further comprises:
for each second business rule of the obtained at least one second business rule, obtaining at least one matching business rule from a business rule database,
wherein recommending the obtained at least one second business rule to the user comprises: recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matched business rule to the user.
4. The method of claim 3, wherein prior to recommending each of the obtained at least one second business rule and the corresponding at least one matching business rule to the user, the method further comprises:
providing each second business rule in the obtained at least one second business rule and the corresponding at least one matching business rule to a user for selection,
recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matching business rule to a user comprises the following steps: and recommending the business rules selected by the user to the user.
5. The method of claim 1, wherein prior to obtaining a field transformation rule for transforming each field in the first business rule from the first application scenario to each of the at least one second application scenario, the method further comprises:
judging whether a second business rule corresponding to the first business rule exists in a business rule database aiming at part or all of the at least one second application scene; and
and when second business rules corresponding to the first business rules and aiming at all second application scenes in the at least one second application scene exist in the business rule database, acquiring the second business rules corresponding to the at least one second application scene from the business rule database.
6. The method of claim 5, wherein prior to obtaining a field transformation rule for transforming each field in the first business rule from the first application scenario to each of the at least one second application scenario, the method further comprises:
when a second business rule corresponding to the first business rule exists in the business rule database and aims at a part of second application scenes in the at least one second application scene, acquiring the second business rule corresponding to the part of second application scenes from the business rule database,
wherein obtaining a field transformation rule for transforming each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario comprises:
obtaining a field conversion rule for converting each field in the first business rule from the first application scene to each of the remaining second application scenes in the at least one second application scene; and
performing field conversion from the first application scenario to each of the at least one second application scenario for each field of the first business rule based on the obtained field conversion rule to obtain at least one second business rule comprises:
based on the obtained field conversion rule, performing field conversion from the first application scenario to each of the remaining second application scenarios on each field of the first business rule to obtain a corresponding second business rule.
7. The method of any one of claims 1 to 6, wherein the regional attributes comprise at least one of the following regional attributes: regional geographical location, regional ethnic composition, regional population scale, regional national influence and regional per capita income.
8. An apparatus for business rule processing, comprising:
an application scenario determination unit configured to determine at least one second application scenario to which a first business rule for a first application scenario is applicable based on a rule type of the first business rule, the first business rule comprising at least one field comprising a rule type field, an application scenario field, and a region field, the application scenario concerned being a country-based application scenario;
a field conversion rule obtaining unit configured to obtain a field conversion rule of each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario; and
a rule conversion unit configured to perform field conversion on each field of the first business rule from the first application scenario to each second application scenario of the at least one second application scenario based on the obtained field conversion rule to obtain at least one second business rule, wherein each second business rule of the at least one second business rule corresponds to one second application scenario, the field conversion rule for the region field is field-converted based on a region similarity, and the region similarity is determined based on a region attribute of a region indicated by a field value of the region field of the first business rule.
9. The apparatus of claim 8, further comprising:
and the rule recommending unit is configured to recommend the obtained at least one second business rule to the user.
10. The apparatus of claim 9, further comprising:
a rule matching unit configured to obtain at least one matching business rule from the business rule database for each of the obtained at least one second business rule before recommending the obtained at least one second business rule to the user, an
The rule recommending unit is configured to: recommending each second business rule of the obtained at least one second business rule and the corresponding at least one matched business rule to the user.
11. The apparatus of claim 10, further comprising:
a rule providing unit configured to provide each of the obtained at least one second business rule and the corresponding at least one matching business rule to a user for selection before recommending each of the obtained at least one second business rule and the corresponding at least one matching business rule to the user, and
the rule recommendation unit is configured to: and recommending the business rule selected by the user to the user.
12. The apparatus of claim 8, further comprising:
a determining unit, configured to determine whether a second business rule corresponding to the first business rule exists in a business rule database for a part or all of the at least one second application scenario before a field conversion rule for each field in the first business rule from the first application scenario to each second application scenario in the at least one second application scenario is obtained; and
a rule obtaining unit, configured to obtain, when a second service rule corresponding to the first service rule exists in the service rule database for all second application scenarios in the at least one second application scenario, a second service rule corresponding to the at least one second application scenario from the service rule database.
13. The apparatus of claim 12, wherein the rule acquisition unit is further configured to:
when a second business rule corresponding to the first business rule exists in the business rule database and aims at a part of second application scenes in the at least one second application scene, acquiring the second business rule corresponding to the part of second application scenes from the business rule database,
wherein the field conversion rule obtaining unit is configured to:
obtaining a field conversion rule for converting each field in the first business rule from the first application scene to each of the remaining second application scenes in the at least one second application scene; and
the rule conversion unit is configured to: based on the obtained field conversion rule, performing field conversion from the first application scenario to each of the remaining second application scenarios on each field of the first business rule to obtain a corresponding second business rule.
14. A computing device, comprising:
at least one processor, and
a memory coupled with the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method of any of claims 1-7.
15. A non-transitory machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811512059.3A CN110009173B (en) | 2018-12-11 | 2018-12-11 | Business rule processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811512059.3A CN110009173B (en) | 2018-12-11 | 2018-12-11 | Business rule processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110009173A CN110009173A (en) | 2019-07-12 |
| CN110009173B true CN110009173B (en) | 2023-04-18 |
Family
ID=67165121
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811512059.3A Active CN110009173B (en) | 2018-12-11 | 2018-12-11 | Business rule processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110009173B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706907A (en) * | 2009-11-26 | 2010-05-12 | 金蝶软件（中国）有限公司 | Method and device for adjusting data |
| CN101777143A (en) * | 2009-12-22 | 2010-07-14 | 金蝶软件（中国）有限公司 | Method, device and system for business bill conversion |
| CN106157141A (en) * | 2015-04-27 | 2016-11-23 | 阿里巴巴集团控股有限公司 | Numerical Methods and device |
| CN106897205A (en) * | 2015-12-18 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of test data generating method and device |
| CN107506181A (en) * | 2017-07-17 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Business processing, data processing method, device and electronic equipment |
| CN107992293A (en) * | 2017-12-11 | 2018-05-04 | 国云科技股份有限公司 | A kind of enterprise attributes dividing system and its implementation |
| CN108090755A (en) * | 2017-12-18 | 2018-05-29 | 深圳市快付通金融网络科技服务有限公司 | Billing model defines method, data system for settling account and computer readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010009520A (en) * | 2008-06-30 | 2010-01-14 | Canon Inc | Flow processor and message conversion method |
-
2018
- 2018-12-11 CN CN201811512059.3A patent/CN110009173B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101706907A (en) * | 2009-11-26 | 2010-05-12 | 金蝶软件（中国）有限公司 | Method and device for adjusting data |
| CN101777143A (en) * | 2009-12-22 | 2010-07-14 | 金蝶软件（中国）有限公司 | Method, device and system for business bill conversion |
| CN106157141A (en) * | 2015-04-27 | 2016-11-23 | 阿里巴巴集团控股有限公司 | Numerical Methods and device |
| CN106897205A (en) * | 2015-12-18 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of test data generating method and device |
| CN107506181A (en) * | 2017-07-17 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Business processing, data processing method, device and electronic equipment |
| CN107992293A (en) * | 2017-12-11 | 2018-05-04 | 国云科技股份有限公司 | A kind of enterprise attributes dividing system and its implementation |
| CN108090755A (en) * | 2017-12-18 | 2018-05-29 | 深圳市快付通金融网络科技服务有限公司 | Billing model defines method, data system for settling account and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110009173A (en) | 2019-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109887153B (en) | Finance and tax processing method and system | |
| US20230377032A1 (en) | System and method for processing transaction records for users | |
| US10614527B2 (en) | System and method for automatic generation of reports based on electronic documents | |
| US11288719B2 (en) | Identifying key-value pairs in documents | |
| CN110263157B (en) | Data risk prediction method, device and equipment | |
| CN111932363B (en) | Method, device, equipment and system for identifying and auditing rights and rights | |
| CN113657886A (en) | Payment system, method, server device, medium and device | |
| CN107077570A (en) | System and method for detecting the trial that sensitive information is sent by data distribution passage | |
| US20180032804A1 (en) | Optical character recognition utilizing hashed templates | |
| CN110046201B (en) | Method, device and system for processing general ledger subject data of business transaction | |
| CN111275037A (en) | Bill identification method and device | |
| CN112258306B (en) | Account information checking method, device, electronic equipment and storage medium | |
| CN113222726A (en) | Electronic certificate processing method, device and equipment | |
| CN111311328A (en) | Method and device for determining advertisement click rate of product under advertisement channel | |
| CN113779934B (en) | Multi-mode information extraction method, device, equipment and computer readable storage medium | |
| CN113254598B (en) | Document comparison method, device, server, medium and product | |
| CN110009173B (en) | Business rule processing method and device | |
| CN110717814B (en) | Method and device for generating risk message | |
| CN105808625A (en) | Document data processing method and device | |
| CN110008252B (en) | Data checking method and device | |
| US10558880B2 (en) | System and method for finding evidencing electronic documents based on unstructured data | |
| US11232161B1 (en) | Methods and apparatuses for electronically stamping document | |
| Karthick et al. | Novel method for energy consumption billing using optical character recognition | |
| CN109829150B (en) | Insurance claim text processing method and apparatus | |
| CN111210329A (en) | Accounting document generation method and device, storage medium and electronic equipment |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201013 Address after: English genus Applicant after: Innovative advanced technology Co.,Ltd. Address before: English genus Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201013 Address after: English genus Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |