A business rule processing method, server and computer-readable storage medium

Abstract

The embodiment of the present application discloses a business rule processing method, a server and a computer-readable storage medium, wherein the method comprises: receiving a business rule import instruction, obtaining a rule document to be imported corresponding to the business rule import instruction; then, converting the content of the business rules in the rule document according to a preset semantic recognition conversion rule, obtaining a target rule document, the content of the target rule document meets the preset compilation condition; finally, compiling the target rule document, obtaining the first rule data, and storing the first rule data in the business system cache. Through the embodiment of the present application, the business staff can use natural language to edit and manage business rules, which can improve the user experience; in addition, directly calling business rules from the business system cache to process business can effectively improve business processing efficiency.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a business rule processing method, a server, and a computer-readable storage medium. Background Art

[0002] In the business system, there are many business rules. Since the market requires that business rules change frequently, the business system must update the business rules quickly and at low cost according to the changes in business rules. In order to update quickly and at low cost, business personnel should be able to directly manage the rules in the business system without the involvement of program developers. Traditional business systems use rule engines to meet the above requirements. Business rules that need to be updated or added are updated or added to the rule library, and then the new rules are called from the rule library through the rule engine. There are the following problems with the update or addition of traditional business rules: business rules must be edited, updated, and managed by database administrators, and the update or addition cycle of business rules is long. Summary of the invention

[0003] The embodiment of the present application provides a business rule processing method, which allows business personnel to use natural language to write business rules and add or update them, thereby realizing real-time and rapid addition or update of business rules and improving the efficiency of business rule processing.

[0004] In a first aspect, an embodiment of the present application provides a method for analyzing unemployment insurance loss assessment data, the method comprising:

[0005] Receiving a business rule import instruction, responding to the business rule import instruction, and acquiring a rule document to be imported corresponding to the business rule import instruction;

[0006] Convert the content of the business rules in the rule document according to the preset semantic recognition conversion rule to obtain a target rule document, wherein the content of the target rule document satisfies the preset compilation condition;

[0007] The target rule document is compiled to obtain the first rule data, and the first rule data is stored in a business system cache.

[0008] Optionally, after storing the rule data in the business system cache, the method further includes:

[0009] Establishing a correspondence between the service tag and the rule data;

[0010] receiving a service processing request, wherein the service processing request includes a first service and a service tag of the first service;

[0011] The target rule data corresponding to the service tag is called from the service system cache, and the first service is processed based on the target rule data.

[0012] Optionally, the method further includes:

[0013] Assigning rule tags to business rules in the target rule document;

[0014] Establishing a correspondence between the rule label and the target rule document;

[0015] The target rule document is stored in a rule document library;

[0016] Receiving an operation instruction for a business rule in the target rule document, wherein the operation instruction includes a second rule tag for a second business rule;

[0017] Execute the operation corresponding to the operation instruction, wherein the operation instruction includes an add instruction, an update instruction, and a delete instruction;

[0018] Acquire the target rule document from the rule document library according to the second rule tag;

[0019] The target rule document is compiled to obtain second rule data, and the first rule data in the business system cache is replaced with the second rule data.

[0020] Optionally, when the operation instruction is an add instruction, the executing the operation corresponding to the operation instruction includes:

[0021] receiving a second text business rule input by a salesperson, where the second text business rule is a text format of the second business rule;

[0022] The second text business rule is converted according to the semantic recognition conversion rule to obtain a converted second business rule, and the converted second business rule is added to the target rule document according to the second rule tag.

[0023] Optionally, when the operation instruction is an update instruction, the executing the operation corresponding to the operation instruction includes:

[0024] receiving a second text business rule input by a salesperson, where the second text business rule is a text format of the second business rule;

[0025] The second text business rule is converted according to the semantic recognition conversion rule to obtain a converted second business rule, and the original second business rule in the target rule document is updated to the converted second business rule according to the second rule tag.

[0026] Optionally, when the operation instruction is a delete instruction, the executing the operation corresponding to the operation instruction includes:

[0027] The second business rule corresponding to the second rule tag in the target rule document is deleted according to the second rule tag.

[0028] Optionally, converting the content of the business rule in the rule document according to the semantic recognition conversion rule includes:

[0029] Performing semantic recognition on the content of the business rules in the rule document, and extracting the execution conditions, execution objects, and execution actions of the business rules from the content of the business rules in the rule document;

[0030] According to the execution condition, the execution object, and the execution action, the content of the business rule in the rule document is edited according to a preset writing format to obtain the target rule document.

[0031] In a second aspect, an embodiment of the present application provides a server, the server including a unit for executing the method of the first aspect, the server including:

[0032] An acquisition unit, configured to receive a business rule import instruction, respond to the business rule import instruction, and acquire a rule document to be imported corresponding to the business rule import instruction;

[0033] A conversion unit, configured to convert the content of the business rules in the rule document according to a preset semantic recognition conversion rule to obtain a target rule document, wherein the content of the target rule document satisfies a preset compilation condition;

[0034] A compiling unit, used for compiling the target rule document to obtain the first rule data;

[0035] A storage unit is used to store the first rule data in a business system cache.

[0036] Optionally, the server further includes:

[0037] A creation unit, used to establish a corresponding relationship between the service tag and the rule data;

[0038] A first receiving unit, configured to receive a service processing request, wherein the service processing request includes a first service and a service tag of the first service;

[0039] The calling unit is used to call the target rule data corresponding to the service tag from the service system cache, and process the first service based on the target rule data.

[0040] Optionally, the server further includes:

[0041] an allocating unit, configured to allocate a rule tag to the business rule in the target rule document;

[0042] The creation unit is used to establish a corresponding relationship between the rule label and the target rule document;

[0043] The storage unit is used to store the target rule document in a rule document library;

[0044] The first receiving unit is used to receive an operation instruction for a business rule in the target rule document, wherein the operation instruction includes a second rule tag for a second business rule;

[0045] A rule processing unit, used to execute the operation corresponding to the operation instruction, wherein the operation instruction includes an add instruction, an update instruction, and a delete instruction;

[0046] The acquiring unit is configured to acquire the target rule document from the rule document library according to the second rule tag;

[0047] The first updating unit is used to compile the target rule document to obtain second rule data, and update the first rule data in the business system cache to the second rule data.

[0048] Optionally, when the operation instruction is an add instruction, the rule processing unit includes:

[0049] A second receiving unit, configured to receive an input of a second text business rule, wherein the second text business rule is a text format of the second business rule;

[0050] The adding unit is used to convert the second text business rule according to the semantic recognition conversion rule to obtain the converted second business rule, and add the converted second business rule to the target rule document according to the second rule tag.

[0051] Optionally, when the operation instruction is an update instruction,

[0052] The second receiving unit is used to receive an input of a second text business rule, where the second text business rule is a text format of the second business rule;

[0053] The rule processing unit also includes:

[0054] The second updating unit is used to convert the second text business rule according to the semantic recognition conversion rule to obtain the converted second business rule, and update the original second business rule in the target rule document to the converted second business rule according to the second rule tag.

[0055] Optionally, when the operation instruction is a delete instruction, the rule processing unit further includes:

[0056] A deleting unit is used to delete the second business rule corresponding to the second rule tag in the target rule document according to the second rule tag.

[0057] Optionally, the conversion unit includes:

[0058] An identification unit, used to perform semantic identification on the content of the business rules in the rule document, and extract the execution conditions, execution objects, and execution actions of the business rules from the content of the business rules in the rule document;

[0059] The editing unit is used to edit the content of the business rules in the rule document according to the execution condition, the execution object, and the execution action in accordance with a preset writing format to obtain the target rule document.

[0060] In a third aspect, an embodiment of the present application provides another server, comprising a processor, a memory and a communication module, wherein the memory is used to store program code, and the processor is used to call the program code to execute the method of the above-mentioned first aspect and any optional method thereof.

[0061] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the method of the above-mentioned first aspect and any optional method thereof.

[0062] It can be seen that in the embodiment of the present application, the salesperson can first use natural language to write the business rules in the rule document, and then convert the content of the business rules in the rule document into a target rule document that meets the preset compilation conditions through semantic recognition, and finally compile the business rules in the target rule document into rule data that can be used by the business system, and store the rule data in the business system cache. Through the embodiment of the present application, the salesperson uses natural language to edit and manage business rules, which can improve the user experience; in addition, directly calling business rule data from the business system cache to process business can effectively improve business processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for describing the embodiments.

[0064] Figure 1 is a schematic flow chart of a business rule processing method provided in an embodiment of the present application;

[0065] Figure 2 is a schematic flow chart of another business rule processing method provided in an embodiment of the present application;

[0066] Figure 3 is a schematic flow chart of another business rule processing method provided in an embodiment of the present application;

[0067] Figure 4 is a schematic block diagram of a server provided in an embodiment of the present application;

[0068] Figure 5 is a schematic block diagram of a device provided in an embodiment of the present application;

[0069] Figure 6 It is a schematic diagram of a server structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0070] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0071] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0072] It should also be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in this application specification and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0073] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0074] As used in this specification and the appended claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0075] See also Figure 1, is a schematic flow chart of a business rule processing method provided by an embodiment of the present application. As shown in the figure, the method may include:

[0076] 101: receiving a business rule import instruction, responding to the business rule import instruction, and obtaining a rule document to be imported corresponding to the business rule import instruction.

[0077] In an embodiment of the present application, when it is necessary to change or add business rules in a business system, the business operator can write the relevant business rules into a text file using a self-recognized language, and then update or add the new rules to the business system by reading the text file containing the business rule information.

[0078] The rule text file can be an Excel spreadsheet, a Word document, a text document, etc. A rule text document can contain multiple rules, and multiple rules can be classified according to different business types, that is, a rule text can contain multiple rules of a business process. One rule can be distinguished from another, and different types of rules can be distinguished in different ways according to the different rule text files used.

[0079] Take the liability and damage assessment rules in the accident insurance claim process as an example, and use Word document writing rules. Assuming that the above accident insurance has three liability and four damage assessment rules, first, you can save the Word document as accident insurance claim rules to facilitate the subsequent call index of accident insurance rules. Then write the liability and damage assessment rules separately, for example, the content is:

[0080] "Nuclear Liability Rules

[0081] Rule 1: Determine whether the insured's disease is the disease stipulated in the insurance contract;

[0082] Rule 2: Determine whether the insured is suffering from the above-mentioned disease for the first time;

[0083] Rule 3, **********.

[0084] "Nuclear Damage Rules"

[0085] Rule 1, **********;

[0086] Rule 2, **********;

[0087] Rule 3, **********;

[0088] Rule 4, **********. "

[0089] It can be understood that the above-mentioned Word rule file is only an example of a rule text file of an embodiment of the present application, and does not limit the rule text file writing format of the present application file.

[0090] Specifically, after the business operator writes the business rules in the rule document using natural language, an import instruction is initiated to import the written rule document to generate rule data in the cache of the business system. After receiving the business rule import instruction, the business rule server responds to the rule import instruction and obtains the rule document written by the business operator specified in the import instruction. After obtaining the rule document, step 102 is continued to process the rule document accordingly.

[0091] As an optional implementation, the above-mentioned import instruction may include an identifier of a rule document. When the business rule server receives the business rule import instruction, it obtains the rule document corresponding to the rule document identifier from the rule document library according to the above-mentioned rule document identifier, and then executes step 102.

[0092] 102: Convert the content of the business rules in the rule document according to a preset semantic recognition conversion rule to obtain a target rule document, wherein the content of the target rule document meets a preset compilation condition.

[0093] In the embodiment of the present application, after the business rule server obtains the rule document, the business rule server converts the content of the business rules in the rule document according to the semantic recognition conversion rule, so as to obtain a target rule document containing business rule content with a specific format that can be recognized. Among them, the semantic recognition conversion rule is a conversion rule that is set up for implementation and can convert the specific content of the business rules written by the salesperson into a specific format content that can be recognized.

[0094] Specifically, after the business rule server obtains the rule document, it performs semantic recognition on the content of the business rules in the rule document, for example, using Neuro-Linguistic Programming (NLP) technology to obtain semantic recognition results. Then, based on the semantic recognition results, the execution conditions, execution objects, execution actions, etc. of each business rule are extracted from the content of each business rule in the rule document. Finally, according to the execution conditions, execution objects, and execution actions of each business rule, a standardized rule statement is edited and generated according to a preset writing format to obtain the target rule document.

[0095] For example, there is a rule in the medical insurance liability verification rules: "If the insured is diagnosed with a major disease listed in this main insurance contract for the first time by the hospital, the insurer shall pay the insured insurance money according to the basic insurance amount. After semantic recognition, it is found that in this rule, "the insured" and "the insurer" are the execution objects, "the insured is diagnosed with a major disease listed in the insurance contract for the first time" is the execution condition, and "the insurer pays the insured insurance money according to the basic insurance amount" is the execution action. The standard rule statement generated according to the above rule content is: "If: insured + initial diagnosis + major disease listed in the insurance contract, then: insurer + payment + basic insurance money, otherwise: end." It can be understood that the above example of converting the medical insurance liability verification rules into standard rule statements is only an example of an embodiment of the present invention and is not limited in any way.

[0096] 103: Compile the target rule document to obtain the first rule data, and store the first rule data in the business system cache.

[0097] In an embodiment of the present application, after the business rule server converts the rule document into a target rule document, it uses the business system to compile the target rule document to obtain first rule data that can directly process the business, and then stores the first rule data in the cache of the business system. When the first rule data needs to be used, it can be directly called from the business system cache to improve the efficiency of business processing.

[0098] It can be seen that in the embodiment of the present application, the salesperson can first use natural language to write the business rules in the rule document, and then convert the content of the business rules in the rule document into a target rule document that meets the compilation conditions through semantic recognition, and finally compile the business rules in the target rule document into rule data that can be used by the business system, and store the rule data in the business system cache. Through the embodiment of the present application, the salesperson can use natural language to edit and manage business rules, which can improve the user experience.

[0099] See also Figure 2 , Figure 2 is a schematic flow chart of another business rule processing method provided by an embodiment of the present application, such as Figure 2 As shown, the method may include:

[0100] 201: receiving a business rule import instruction, responding to the business rule import instruction, and obtaining a rule document to be imported corresponding to the business rule import instruction.

[0101] 202: Convert the content of the business rules in the rule document according to the semantic recognition conversion rule to obtain a target rule document, wherein the content of the target rule document meets the compilation condition.

[0102] 203: Compile the target rule document to obtain the first rule data, and store the first rule data in the business system cache.

[0103] 204: Establish a corresponding relationship between the business tag and the above rule data.

[0104] In an embodiment of the present application, after the business rule server stores the above-mentioned first rule data in the cache of the business system, a correspondence between the business tag and the rule data is established according to the specific business, so that when the business needs to be processed, the corresponding rule data can be called from the cache of the business system according to the business tag of the business.

[0105] 205: Receive a service processing request, where the service processing request includes a first service and a service tag of the first service.

[0106] 206: Retrieve the target rule data corresponding to the service tag from the service system cache, and process the first service based on the target rule data.

[0107] In an embodiment of the present application, when a service processing request is received, the target rule data corresponding to the service tag of the first service in the service request is directly called from the service system cache, and then the first service is processed accordingly according to the called target rule data.

[0108] It can be seen that in the embodiment of the present application, the salesperson can first use natural language to write the business rules in the rule document, and then convert the content of the business rules in the rule document into a target rule document that meets the compilation conditions through semantic recognition, and finally compile the business rules in the target rule document into rule data that can be used by the business system, and store the rule data in the business system cache. When it is necessary to process the business, the corresponding business rule data can be directly called from the cache of the business system to process the business. Through the embodiment of the present application, the salesperson uses natural language to edit and manage business rules, which can improve the user experience; in addition, directly calling business rules from the business system cache to process business can effectively improve business processing efficiency.

[0109] See also Figure 3 , Figure 3 is a schematic flow chart of another business rule processing method provided in an embodiment of the present application, such as Figure 3 As shown, the method may include:

[0110] 301: Receive a business rule import instruction, respond to the business rule import instruction, and obtain a rule document to be imported corresponding to the business rule import instruction.

[0111] 302: Convert the content of the business rules in the rule document according to the semantic recognition conversion rule to obtain a target rule document, store the target rule document in a rule document library, and the content of the target rule document meets the compilation condition.

[0112] In an embodiment of the present application, after the business server converts the content of the business rules in the above-mentioned rule document according to the semantic recognition conversion rules and obtains the target rule document, the business server stores the above-mentioned target rule document in the rule document library so as to subsequently perform corresponding management of the business rules in the target rule document, for example, updating business rules, adding business rules, deleting business rules, etc.

[0113] 303: Compile the target rule document to obtain the first rule data, and store the first rule data in the business system cache.

[0114] 304: Assign rule tags to the business rules in the target rule document, and establish a corresponding relationship between the rule tags and the target rule document.

[0115] In an embodiment of the present application, after the business rule server stores the above-mentioned target rule document in the rule document library, it assigns a rule tag to each business rule in the above-mentioned target rule document, and creates a correspondence between the rule tag and the target rule document, so that the target rule document where the business rule corresponding to the rule tag is located can be found according to the rule tag, and then the business rule corresponding to the above-mentioned rule tag in the target rule document can be managed.

[0116] 305: Receive an operation instruction for the business rule in the target rule document, where the operation instruction includes a second rule tag for the second business rule.

[0117] As market operations are constantly changing, the corresponding business rules will also change with the changes in the business. Therefore, it is necessary to perform corresponding management operations on the business rule data in the business system cache, such as updating or deleting one or all business rules.

[0118] Specifically, in an embodiment of the present application, when the business rule server stores the above-mentioned target rule document in a rule document library, generates first rule data based on the target rule document, and stores the first rule data in a business system cache, it receives an operation instruction for the business rule in the above-mentioned target rule document, wherein the above-mentioned operation instruction includes a second rule tag of the second business rule, so as to find the second business rule according to the above-mentioned second rule tag and perform corresponding operations on it.

[0119] 306: Acquire the target rule document from the rule document library according to the second rule tag.

[0120] 307: Execute the operation corresponding to the above operation instruction, which includes adding instruction, updating instruction and deleting instruction.

[0121] In the embodiment of the present application, operations such as updating, deleting, and adding may be performed on the business rules in the target rule document.

[0122] Specifically, when a salesperson needs to add an operation to the above-mentioned target rule document, the salesperson only needs to initiate an operation instruction to add a business rule, and then enter the corresponding business rule to add the business rule to the above-mentioned target rule document. When the business rule server receives the instruction to add the second business rule, it receives the second text business rule entered by the salesperson, wherein the above-mentioned second text business rule is the text format of the above-mentioned second business rule. Then, the business rule server converts the above-mentioned second text business rule according to the semantic recognition conversion rule to obtain the converted second business rule. Then, according to the above-mentioned second rule tag, the above-mentioned converted second business rule is added to the above-mentioned target rule document to complete the operation of adding the second business rule to the above-mentioned target rule document.

[0123] When the salesperson needs to update an operation in the above-mentioned target rule document, the salesperson only needs to initiate an operation instruction to update the business rule, and then enter the corresponding business rule to update the corresponding business rule in the above-mentioned target rule document. When the business rule server receives the update instruction for the second business rule, it receives the second text business rule entered by the salesperson, wherein the above-mentioned second text business rule is the text format of the above-mentioned second business rule. Then, the business rule server converts the above-mentioned second text business rule according to the semantic recognition conversion rule to obtain the converted second business rule. Then, according to the above-mentioned second rule label, the original second business rule in the above-mentioned target rule document is updated to the above-mentioned converted second business rule to complete the update operation of the second business rule in the above-mentioned target rule document.

[0124] When the salesperson needs to delete an operation in the above-mentioned target rule document, the salesperson only needs to initiate an operation instruction to delete the business rule, and then delete the second business rule corresponding to the above-mentioned second rule tag in the above-mentioned target rule document according to the above-mentioned second rule tag to complete the deletion operation of the second business rule in the above-mentioned target rule document.

[0125] 308: Compile the target rule document to obtain second rule data, and replace the first rule data in the business system cache with the second rule data.

[0126] In an embodiment of the present application, after the business rule server executes the corresponding operation on the second business rule in the above-mentioned target rule document according to the above-mentioned operation instruction, the business rule server compiles the above-mentioned target rule document, obtains the second rule data, and replaces the first rule data in the above-mentioned business system cache with the above-mentioned second rule data so as to achieve the purpose of indirectly managing the corresponding second rule data in the business system cache through the management operation of the second business rule in the above-mentioned target rule document.

[0127] It can be seen that in the embodiment of the present application, the salesperson can first use natural language to write the business rules in the rule document, and then convert the content of the business rules in the rule document into a target rule document that meets the compilation conditions through semantic recognition, and store the target rule document in the rule document library; finally, by compiling the business rules in the target rule document into rule data that can be used by the business system, and storing the rule data in the business system cache, when it is necessary to add, update, delete, etc. to the business rule data in the business system, the corresponding operation can be performed on the target rule document in the rule document library, and then the target rule document is recompiled to obtain new rule data, and finally the old rule data in the business system is updated to the new rule data. Through the embodiment of the present application, the salesperson uses natural language to edit and manage business rules, which can improve the user experience; in addition, the salesperson can also quickly add, update and delete the rule data in the business system in real time by managing the target rule document in the rule document library, thereby improving the efficiency of business rule data management.

[0128] The embodiment of the present application also provides a server, which is used to execute any of the above methods. Figure 4 , is a schematic block diagram of a server provided in an embodiment of the present application. The server in this embodiment includes: an acquisition unit 401, a conversion unit 402, a compilation unit 403 and a storage unit 404.

[0129] The acquisition unit 401 is used to receive a business rule import instruction, respond to the business rule import instruction, and acquire a rule document to be imported corresponding to the business rule import instruction;

[0130] The conversion unit 402 is used to convert the content of the business rules in the rule document according to the semantic recognition conversion rule to obtain a target rule document, wherein the content of the target rule document meets the compilation condition;

[0131] A compiling unit 403 is used to compile the target rule document to obtain the first rule data.

[0132] The storage unit 404 is used to store the first rule data in the business system cache.

[0133] It can be seen that in the embodiment of the present application, the salesperson can first use natural language to write the business rules in the rule document, and then convert the content of the business rules in the rule document into a target rule document that meets the compilation conditions through semantic recognition, and finally compile the business rules in the target rule document into rule data that can be used by the business system, and store the rule data in the business system cache. Through the embodiment of the present application, the salesperson can use natural language to edit and manage business rules, which can improve the user experience.

[0134] Optionally, the server further includes:

[0135] A creation unit 405, used to establish a corresponding relationship between the service tag and the above rule data;

[0136] A first receiving unit 406 is configured to receive a service processing request, where the service processing request includes a first service and a service tag of the first service;

[0137] The calling unit 407 is used to call the target rule data corresponding to the service tag from the service system cache, and process the first service based on the target rule data.

[0138] It can be seen that in the embodiment of the present application, when business needs to be processed, the corresponding business rule data can be directly called from the cache of the business system to process the business. Through the embodiment of the present application, the business operator uses natural language to edit and manage business rules, which can improve the user experience; in addition, directly calling business rules from the business system cache to process business can effectively improve business processing efficiency.

[0139] Optionally, the server further includes:

[0140] An allocating unit 408 is used to allocate rule tags to the business rules in the target rule document;

[0141] The creating unit 405 is used to establish a corresponding relationship between the rule label and the target rule document;

[0142] The storage unit 404 is used to store the target rule document in a rule document library;

[0143] The first receiving unit 406 is configured to receive an operation instruction for a business rule in the target rule document, wherein the operation instruction includes a second rule tag for a second business rule;

[0144] A rule processing unit 409, configured to execute operations corresponding to the above-mentioned operation instructions, wherein the above-mentioned operation instructions include adding instructions, updating instructions, and deleting instructions;

[0145] The acquisition unit 401 is used to acquire the target rule document from the rule document library according to the second rule tag;

[0146] The first updating unit 410 is used to compile the target rule document to obtain second rule data, and update the first rule data in the business system cache to the second rule data.

[0147] Optionally, when the operation instruction is an add instruction, the rule processing unit includes:

[0148] The second receiving unit 4091 is used to receive an input of a second text business rule, where the second text business rule is a text format of the second business rule;

[0149] The adding unit 4092 is used to convert the second text business rule according to the semantic recognition conversion rule to obtain the converted second business rule, and add the converted second business rule to the target rule document according to the second rule tag.

[0150] Optionally, when the above operation instruction is an update instruction,

[0151] The second receiving unit 4091 is used to receive an input of a second text business rule, where the second text business rule is a text format of the second business rule;

[0152] The rule processing unit further includes:

[0153] The second updating unit 4093 is used to convert the above-mentioned second text business rule according to the semantic recognition conversion rule to obtain the converted second business rule, and update the original second business rule in the above-mentioned target rule document to the above-mentioned converted second business rule according to the above-mentioned second rule label.

[0154] Optionally, when the operation instruction is a delete instruction, the rule processing unit further includes:

[0155] The deleting unit 4094 is used to delete the second business rule corresponding to the second rule tag in the target rule document according to the second rule tag.

[0156] Optionally, the conversion unit includes:

[0157] The identification unit 4021 is used to perform semantic identification on the content of the business rules in the rule document, and extract the execution conditions, execution objects, and execution actions of the business rules from the content of the business rules in the rule document;

[0158] The editing unit 4022 is used to edit the content of the business rules in the above-mentioned rule document according to the above-mentioned execution conditions, the above-mentioned execution objects, and the above-mentioned execution actions in accordance with a preset writing format to obtain the above-mentioned target rule document.

[0159] It can be seen that in the embodiment of the present application, the salesperson can first use natural language to write the business rules in the rule document, and then convert the content of the business rules in the rule document into a target rule document that meets the compilation conditions through semantic recognition, and store the target rule document in the rule document library; finally, by compiling the business rules in the target rule document into rule data that can be used by the business system, and storing the rule data in the business system cache, when it is necessary to add, update, delete, etc. to the business rule data in the business system, the corresponding operation can be performed on the target rule document in the rule document library, and then the target rule document is recompiled to obtain new rule data, and finally the old rule data in the business system is updated to the new rule data. Through the embodiment of the present application, the salesperson uses natural language to edit and manage business rules, which can improve the user experience; in addition, the salesperson can also quickly add, update and delete the rule data in the business system in real time by managing the target rule document in the rule document library, thereby improving the efficiency of business rule data management.

[0160] See also Figure 5 , Figure 5 is a device provided in an embodiment of the present application, which may be a server, such as Figure 5 The device shown includes: one or more processors 501; one or more input devices 502, one or more output devices 503 and a memory 504. The processor 501, the input device 502, the output device 503 and the memory 504 are connected via a bus 505. The memory 504 is used to store instructions, and the processor 501 is used to execute the instructions stored in the memory 504.

[0161] In which, when the device is used as a server, the processor 501 is used to: receive a business rule import instruction, respond to the business rule import instruction, and obtain the rule document to be imported corresponding to the business rule import instruction; convert the content of the business rules in the rule document according to the semantic recognition conversion rule to obtain the target rule document, and the content of the target rule document meets the compilation conditions; compile the target rule document to obtain the first rule data, and store the first rule data in the business system cache.

[0162] It should be understood that in the embodiment of the present application, the processor 501 may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0163] The input device 502 may include a touch panel, a fingerprint sensor (for collecting the user's fingerprint information and fingerprint direction information), a microphone, etc., and the output device 503 may include a display (LCD, etc.), a speaker, etc.

[0164] The memory 504 may include a read-only memory and a random access memory, and provide instructions and data to the processor 501. A portion of the memory 504 may also include a non-volatile random access memory. For example, the memory 504 may also store information about the device type.

[0165] In a specific implementation, the processor 501, input device 502, and output device 503 described in the embodiments of the present application can execute the implementation method described in the first embodiment, the second embodiment, and the third embodiment of a business rule processing method provided in the embodiments of the present application, and can also execute the implementation method of the server described in the embodiments of the present application, which will not be repeated here.

[0166] In another embodiment of the present application, a computer-readable storage medium is provided, and the computer-readable storage medium stores a computer program. When the computer program is executed by a processor, it implements: receiving a business rule import instruction, responding to the business rule import instruction, and obtaining a rule document to be imported corresponding to the business rule import instruction; converting the content of the business rules in the rule document according to a semantic recognition conversion rule to obtain a target rule document, and the content of the target rule document meets the compilation conditions; compiling the target rule document to obtain the first rule data, and storing the first rule data in a business system cache.

[0167] The computer-readable storage medium may be an internal storage unit of the terminal in any of the aforementioned embodiments, such as a hard disk or memory of the terminal. The computer-readable storage medium may also be an external storage device of the terminal, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), etc. equipped on the terminal. Further, the computer-readable storage medium may also include both an internal storage unit of the terminal and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

[0168] Figure 6 6 is a schematic diagram of a server structure provided in an embodiment of the present application. The server 600 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 622 (for example, one or more processors) and a memory 632, and one or more storage media 630 (for example, one or more mass storage devices) storing application programs 642 or data 644. Among them, the memory 632 and the storage medium 630 may be short-term storage or permanent storage. The program stored in the storage medium 630 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the server. Furthermore, the central processing unit 622 may be configured to communicate with the storage medium 630 to execute a series of instruction operations in the storage medium 630 on the server 600.

[0169] The server 600 may also include one or more power supplies 626, one or more wired or wireless network interfaces 650, one or more input and output interfaces 658, and / or one or more operating systems 641, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0170] The steps performed by the server in the above embodiment can be based on the Figure 6 The server structure shown.

[0171] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0172] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described systems, servers, terminal devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0173] In the several embodiments provided in the present application, it should be understood that the disclosed systems, servers and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0174] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0175] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0176] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the above-mentioned methods of each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0177] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A business rule processing method, characterized in that: include: Receive a business rule import instruction, and obtain a rule document to be imported corresponding to the business rule import instruction; Convert the content of the business rules in the rule document according to the preset semantic recognition conversion rule to obtain a target rule document, wherein the content of the target rule document satisfies the preset compilation condition; Compiling the target rule document to obtain first rule data, and storing the first rule data in a business system cache; Establishing a correspondence between the service tag and the rule data; receiving a service processing request, wherein the service processing request includes a first service and a service tag of the first service; The target rule data corresponding to the service tag is called from the service system cache, and the first service is processed based on the target rule data.

2. The method according to claim 1, characterized in that After converting the content of the business rules in the rule document according to the preset semantic recognition conversion rule to obtain the target rule document, the method further includes: Assigning rule tags to business rules in the target rule document; Establishing a correspondence between the rule tag and the target rule document; Storing the target rule document in a rule document library; Receiving an operation instruction for a business rule in the target rule document, wherein the operation instruction includes a second rule tag for a second business rule; Acquire the target rule document from the rule document library according to the second rule tag; Execute the operation corresponding to the operation instruction, wherein the operation instruction includes an add instruction, an update instruction, and a delete instruction; The target rule document is compiled to obtain second rule data, and the first rule data in the business system cache is replaced with the second rule data.

3. The method according to claim 2, characterized in that In the case where the operation instruction is an add instruction, the operation corresponding to the execution of the operation instruction includes: receiving a second text business rule input by a salesperson, where the second text business rule is a text format of the second business rule; The second text business rule is converted according to the semantic recognition conversion rule to obtain a converted second business rule, and the converted second business rule is added to the target rule document according to the second rule tag.

4. The method according to claim 2, characterized in that: In the case where the operation instruction is an update instruction, the operation corresponding to the execution of the operation instruction includes: receiving a second text business rule input by a salesperson, where the second text business rule is a text format of the second business rule; The second text business rule is converted according to the semantic recognition conversion rule to obtain a converted second business rule, and the second business rule in the target rule document is updated to the converted second business rule according to the second rule tag.

5. The method according to claim 2, characterized in that: In the case where the operation instruction is a delete instruction, the operation corresponding to the execution of the operation instruction includes: The second business rule corresponding to the second rule tag in the target rule document is deleted according to the second rule tag.

6. The method according to any one of claims 1 to 5, characterized in that: The converting of the content of the business rules in the rule document according to the semantic recognition conversion rule comprises: Performing semantic recognition on the content of the business rules in the rule document, and extracting the execution conditions, execution objects, and execution actions of the business rules from the content of the business rules in the rule document; According to the execution condition, the execution object, and the execution action, the content of the business rule in the rule document is edited according to a preset writing format to obtain the target rule document.

7. A server, characterized in that: The method comprises means for executing the method according to any one of claims 1 to 6.

8. A server, characterized in that: The server comprises a processor, a memory and a communication module, wherein the memory is used to store program codes, and the processor is used to call the program codes to execute the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 6.

Images