Service request processing method and device, electronic equipment and storage medium

Abstract

The invention discloses a service request processing method and device, electronic equipment and a storage medium, and relates to the technical field of computers. The method comprises the following steps: receiving a to-be-processed service request sent by a service request source organization; determining an organization level path from the business request source organization to a main control organization according to a preset organization structure and the organization identifier of the business request source organization; obtaining a target service rule corresponding to the service request in a baseline layer corresponding to the main control organization; traversing according to an organization level path, and reading a target difference fragment corresponding to the target business rule from a differentiation layer coverage layer corresponding to a subordinate organization when traversing to the subordinate organization of a certain level; combining the target business rule with the target difference fragment by adopting a rule tree dynamic combination algorithm, and outputting a final execution rule; and processing the service request according to the final execution rule, and outputting a service request processing result. According to the invention, the accuracy of the service request processing result can be effectively improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a business request processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] In large enterprises, the group typically maintains unified business rules for certain core operations. These rules are usually written into program code, enabling them to take effect simultaneously across the group and all its subsidiaries. However, large enterprises are characterized by multi-level, multi-organizational, multi-segment, and multi-mode management. Different subsidiaries, due to varying management models and industry targets, may encounter inaccurate processing results if all business requests are handled according to the same rules. Furthermore, since these business rules are implemented through program code, their configuration efficiency is low. Therefore, a new method for handling business requests is urgently needed. Summary of the Invention

[0003] This invention provides a business request processing method, apparatus, electronic device, storage medium, and computer program product.

[0004] According to one aspect of the present invention, a business request processing method is provided, comprising:

[0005] Receive pending business requests sent by the business request source organization; wherein, the business request source organization is the main control organization or subordinate organizations of different levels under the main control organization;

[0006] Based on the preset organizational structure and the organizational identifier of the business request source organization, determine the organizational hierarchy path from the business request source organization to the main control organization;

[0007] In the baseline layer corresponding to the main control organization, the target business rule corresponding to the business request is obtained; wherein, the baseline layer is used to store at least one globally effective business rule configured through visual configuration technology;

[0008] The process traverses the organizational hierarchy, and at each level of subordinate organization, it reads the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization. The differential layer overlay layer is used to store the difference fragments that are different from the business rule and are configured through visual configuration technology.

[0009] A rule tree dynamic merging algorithm is used to merge the target business rules and the target difference fragments to output the final execution rules;

[0010] According to the final execution rules, the business requests are processed and the processing results are output.

[0011] According to another aspect of the present invention, a business request processing apparatus is provided, comprising:

[0012] The request receiving module is used to receive pending business requests sent by the business request source organization; wherein, the business request source organization is the main control organization or subordinate organizations of different levels under the main control organization;

[0013] The path determination module is used to determine the organizational hierarchy path from the business request source organization to the main control organization based on the preset organizational structure and the organization identifier of the business request source organization.

[0014] The first acquisition module is used to acquire the target business rule corresponding to the business request from the baseline layer corresponding to the main control organization; wherein, the baseline layer is used to store at least one globally effective business rule configured through visual configuration technology;

[0015] The second acquisition module is used to traverse according to the organizational hierarchy path, and each time a subordinate organization at a certain level is traversed, it reads the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization; wherein, the differential layer overlay layer is used to store the difference fragments that are different from the business rule configured through visual configuration technology.

[0016] The merging module is used to merge the target business rules and the target difference fragments using a rule tree dynamic merging algorithm, and output the final execution rules.

[0017] The processing module is used to process business requests according to the final execution rules and output the business request processing results.

[0018] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0019] At least one processor; and

[0020] A memory that is communicatively connected to at least one processor; wherein,

[0021] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to execute the service request processing method of the present invention.

[0022] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions for causing a processor to execute and implement the service request processing method of the embodiments of the present invention.

[0023] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the steps in the above-described method.

[0024] The technical solution of this invention can improve the accuracy and efficiency of business request processing; at the same time, business rule configuration can be completed through visual operation, reducing reliance on professional technical personnel and improving the efficiency of rule configuration.

[0025] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a flowchart illustrating a business request processing method provided in an embodiment of the present invention;

[0028] Figure 2 This is a flowchart illustrating another business request processing method provided in an embodiment of the present invention;

[0029] Figure 3 This is a flowchart illustrating another business request processing method provided in an embodiment of the present invention;

[0030] Figure 4 This is a schematic diagram of the structure of a business request processing device provided in an embodiment of the present invention;

[0031] Figure 5 This is a schematic diagram of the structure of an electronic device that implements the service request processing method of this invention. Detailed Implementation

[0032] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0033] Example 1

[0034] Figure 1This is a flowchart of a business request processing method provided in an embodiment of the present invention. This embodiment is applicable to scenarios of processing business requests in large enterprises. The method can be executed by a business request processing device, which can be implemented in hardware and / or software and can be configured in an electronic device.

[0035] like Figure 1 As shown, the business request processing methods include:

[0036] S101. Receive pending business requests sent by the business request source organization; wherein, the business request source organization is the main control organization or subordinate organizations of different levels under the main control organization.

[0037] In this embodiment of the invention, the business request source organization refers to the organizational entity that initiates the business request, encompassing two categories: 1. the main controlling organization (such as the group headquarters); and 2. subordinate organizations at different levels (such as first-level subsidiaries and second-level branches), which are the core basis for subsequent location of hierarchical paths. The business request to be processed refers to the specific requirement initiated by the business request source organization that needs to be processed according to business rules, including core identification information (such as business type: contract change / procurement approval; organization identifier: the unique identifier of the business request source organization; business data: such as contract amount, change ratio, etc.), which is the basis for subsequent matching of business rules.

[0038] In some embodiments, step S101 may be implemented by: receiving pending business requests initiated by the business request source organization through a preset request receiving interface (such as an API interface); performing structured parsing on the business requests, extracting key information such as business type, organization identifier, and business data, and completing preliminary verification of the legality of the business requests (such as whether they carry a valid organization identifier and whether the business data is complete), providing basic data support for subsequently determining the organizational hierarchy path and matching business rules.

[0039] The beneficial effects of step S101 include: by parsing organizational identifiers and business data, it avoids the inability to proceed with subsequent steps due to ambiguous request sources or missing key data, laying the foundation for hierarchical path positioning and rule matching; it also supports request reception from both the main management organization and subordinate organizations, adapting to two core scenarios: group management and subsidiary personalized processing, eliminating the need to develop separate receiving modules for different organizations and reducing system complexity; and by reducing invalid requests entering subsequent processes (such as requests with non-existent organizational identifiers or missing data) through preliminary verification, it improves system processing efficiency and avoids resource waste.

[0040] S102. Based on the preset organizational structure and the organizational identifier of the business request source organization, determine the organizational hierarchy path from the business request source organization to the main control organization.

[0041] In this embodiment of the invention, the preset organizational structure refers to a structured data model (usually a tree structure) that stores the multi-level organizational relationships of an enterprise. It includes information such as organizational identifier, parent organizational identifier, organizational level, and affiliated sector. For example, the main controlling organization (Group, ID: G001) → first-level subsidiary (Company B, ID: A01) → second-level branch (Company B East China Branch, ID: A01-B02) is the core basis for determining the hierarchical path. The organizational hierarchical path refers to the complete hierarchical link from the business request source organization to the main controlling organization, represented as an ordered list of business request source organization → superior organization → ... → main controlling organization. For example, when the request source organization is A01-B02 (East China Branch), the path is A01-B02 → A01 (Company B) → G001 (Group), used for subsequent traversal of the differentiated overlay layer of subordinate organizations.

[0042] In some embodiments, the process of determining the organizational hierarchy path includes: based on a tree-structured data model of a preset organizational architecture, starting with the organizational identifier of the organization from which the business request originates, and tracing upwards layer by layer to the main controlling organization through recursive queries or parent index matching, generating an ordered list of paths containing all intermediate level organizations. Additionally, the generated paths can be validated for legality (e.g., whether they ultimately point to the main controlling organization, and whether cyclical hierarchies exist) to ensure that the paths are complete and unique.

[0043] Understandably, by clearly defining the superior-subordinate relationship of the requesting organization through structured paths, the system avoids omitting or incorrectly selecting organizations when traversing the differentiated overlay layers, ensuring the completeness of personalized rule collection. It adapts to multi-level management scenarios, supporting the generation of complex hierarchical paths from main control to first-level, second-level, ..., N-level subordinate organizations, meeting the management characteristics of multi-level and multi-organizational organizations in large enterprises without requiring adjustments to logic due to the increase in levels; and providing a basis for differentiated rule traversal.

[0044] S103. In the baseline layer corresponding to the main control organization, obtain the target business rule corresponding to the business request.

[0045] In this embodiment of the invention, the baseline layer is used to store at least one globally effective business rule configured through visual configuration technology. That is, the baseline layer is a unified business rule layer configured by the main management organization and effective across the entire group. It is generated using visual configuration technology (such as a drag-and-drop rule editor or form parameter configuration). The stored business rules include unmodifiable core logic (such as process nodes for contract changes) and adjustable baseline parameters. The target business rule refers to a specific business rule in the baseline layer that completely matches the business type of the business request to be processed. For example, when the business request is a contract change, the target business rule is the contract change price constraint rule in the baseline layer, which may contain structured information such as rule ID, core logic, baseline parameters, and scope of effectiveness.

[0046] In some embodiments, the implementation process of this step may include: performing index matching (e.g., by business type) in the baseline layer rule base of the main control organization based on the business type of the business request to be processed (e.g., contract change, procurement approval); and extracting the matched target business rules.

[0047] Understandably, all business requests are processed based on the target business rules of the baseline layer, preventing subordinate organizations from deviating from the group's unified standards. The baseline layer rules are configured through visual technology, and the main management organization can adjust the baseline parameters without relying on technical personnel to modify the program code, thereby improving the efficiency of rule maintenance and responding to changes in the group's management needs.

[0048] S104. Traverse the organization according to the hierarchical path, and when traversing to a subordinate organization at a certain level, read the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization.

[0049] In this embodiment of the invention, the differentiation overlay layer is used to store the difference segments configured through visual configuration technology that differ from the business rules. That is, the differentiation overlay layer is a personalized rule layer configured by each subordinate organization (such as first-level subsidiaries and second-level branches) based on the baseline layer rules. It is generated using visual configuration technology and is used to store the differences (not the complete rules) between the baseline layer target business rules and the actual rules. For example, if Company A changes the threshold of a certain business rule from 10% to 9%, the differentiation overlay layer stores the threshold as 9%, avoiding rule redundancy. The target difference segment refers to the difference portion in the differentiation overlay layer that matches the target business rule. This is manifested as structured segments such as parameter modifications (e.g., threshold adjustment) and range reduction, and serves as personalized input for subsequent rule merging. In addition, the differentiation overlay layer also stores multi-condition differentiation strategies corresponding to the target business rules. These multi-condition differentiation strategies include differentiated parameter configurations based on conditions such as business type and region. In some embodiments, traversing according to the organizational hierarchy path, and reading the target difference fragment corresponding to the target business rule from the differentiation layer overlay corresponding to the subordinate organization at a certain level, includes: traversing according to the organizational hierarchy path, and when traversing to a subordinate organization at a certain level, if the differentiation layer overlay corresponding to the subordinate organization at that level has a difference fragment corresponding to the target business rule, then outputting the difference fragment as the target difference fragment; if the differentiation layer overlay corresponding to the subordinate organization at that level does not have a difference fragment corresponding to the target business rule, then traversing the subordinate organizations at the next higher level, and reading the target difference fragment corresponding to the target business rule from the differentiation layer overlay corresponding to the subordinate organization at the next higher level.

[0050] That is, the organizational hierarchy path is traversed in the order from bottom to top (business request source organization → superior organization → ... → the level before the main control organization); for each subordinate organization traversed, its differential overlay rule base is accessed, and the corresponding target differential fragment is extracted by matching the rule ID; all extracted differential fragments are sorted in the traversal order to form a differential fragment list.

[0051] Understandably, traversing all relevant subordinate organizations along the hierarchical path avoids missing any differentiated configurations at any level, ensuring that the final rules include the personalized needs of all levels; the differentiated overlay layer only stores difference fragments rather than complete rules, which significantly reduces data storage compared to storing complete personalized rules, and improves the efficiency of rule reading and merging.

[0052] S105. Using a rule tree dynamic merging algorithm, the target business rules and target difference fragments are merged to output the final execution rules.

[0053] In this embodiment of the invention, the rule tree dynamic merging algorithm refers to an algorithm that dynamically merges target business rules and target difference fragments based on a rule tree structure (a tree model of target business rule transformation) according to the priority of differentiated fragments (upper level > lower level). The core logic includes parameter overriding, i.e., replacing the corresponding parameters in the target business rule with the parameters of the difference fragments. The final execution rule refers to the complete rule generated after merging the target business rule with all target difference fragments, which can be directly used to process business requests.

[0054] In some embodiments, the implementation process of this step may include: using the target business rule tree generated in step S103 as the base tree. For example, the specific content of the target business rule is as follows: Core logic: Contract change ratio ≥ threshold → Sign supplementary agreement; < threshold → Economic certificate; Change ratio threshold (i.e., benchmark parameter) is 10%; Effective range is 8%-12%. Then the nodes of the base tree are as follows: Root node (node ​​type: rule root node; node ID: RT-CR001; node value: core rule for contract change); Second-level nodes under the root node include core logic branch nodes (node ​​type: logic branch; node ID: LB-1; node value: condition judgment and execution action); Child nodes under the core logic branch nodes include condition nodes (node ​​type: judgment condition; node ID: CN-1; node value: contract change ratio ≥ threshold in [parameter node]), execution action node 1 (node ​​type: result action; node ID: AC-1; node value: generate supplementary agreement), execution action 2 (node ​​type: result action; node ID: AC-2; node value (Generate economic certificate); the child nodes of the condition node are parameter nodes (node ​​type: configurable parameter; node ID: PN-1; node value: 10%; parameter type: threshold), and the second-level nodes under the root node also include effective scope branch nodes (node ​​type: scope branch; node ID: RB-1; node value: rule applicable organization scope); then, according to the difference fragment priority from low to high (lower level first, then upper level), the target difference fragments are integrated into the base tree one by one: for parameter modification type differences, the corresponding parameter node in the rule tree is directly replaced; for scope constraint type differences, the effective scope node of the rule tree is narrowed; after the merging is completed, the integrity of the rule tree is verified (if there is no logical conflict), and the structured final execution rule is output. For example, if the difference fragment content: change ratio threshold from 10% → 9% (node ​​type: parameter modification type; associated node ID: PN-1). The merging operation is as follows: locate PN-1 (parameter node) in the rule tree, read its current node value of 10%; replace the node value of PN-1 with the difference fragment of 9% (because it is a parameter modification type difference, only the parameter node is modified, and the condition logic is not changed).

[0055] Understandably, the final execution rules after the merger retain the core logic of the group's business rules while incorporating the personalized configurations of subordinate organizations, perfectly balancing the group's control and the flexibility demands of its subsidiaries. If a subordinate organization adjusts its differentiated configuration, it only needs to re-merge that differentiated segment without modifying the baseline rules or the configurations of other organizations, demonstrating high flexibility in responding to changes.

[0056] S106. Process the business request according to the final execution rules and output the business request processing result.

[0057] In some embodiments, the rule execution engine is invoked, and the structured data of the business request to be processed and the final execution rule are input. The rule execution engine performs condition judgments on the business data included in the business request according to the logic of the final execution rule (such as calculating the change ratio and judging whether the exemption conditions are met), triggers the corresponding execution actions (such as process invocation and document generation), collects the results of the execution actions, generates a structured processing result containing status, records and descriptions, feeds it back to the business request source organization, and stores the result in the processing log library.

[0058] To facilitate understanding of this solution, an example is provided: Assume the business request originating from the East China branch of Company B (organization ID: A01-B02, a second-level subordinate organization) of the group. When initiating a contract change request, the data submitted via the interface must include at least the following: Business type: Contract Change; Organization ID: A01-B02; Original contract number: CT-XXXX-XX; Original contract amount: XXX million yuan; Changed amount: XXX million yuan; Change percentage: 8%; Request time: XXXX-XX-XX. The received business request data is parsed. If organization IDs A01-B02 exist within the preset organizational structure, and the original contract amount and change percentage are not missing from the business data, the request is deemed legitimate and proceeds to the next step. If the change percentage is missing from the request, a message indicating data deficiency is returned, requesting the addition of the contract change percentage, thus blocking invalid requests.

[0059] Furthermore, the pre-defined organizational structure is a tree structure (partial nodes): Group (main management organization, ID: G001) → Company B (first-level subsidiary, ID: A01) → East China Branch (second-level branch, ID: A01-B02). The system recursively queries the parent organizations, starting from the business request source organization IDs: A01-B02.

[0060] Step 1: The parent ID of A01-B02 is A01 (Company B);

[0061] Step 2: The parent ID of A01 is G001 (Group).

[0062] Termination at the main control organization G001, generating the organizational hierarchy path: A01-B02 (East China Branch) → A01 (Company B) → G001 (Group).

[0063] Furthermore, based on the business type "Contract Change", the target business rule (rule ID: CR-001) is matched from the group baseline layer (G001). The specific content of the target business rule is as follows: Core logic: Contract change ratio ≥ threshold → sign supplementary agreement; < threshold → economic certificate; Change ratio threshold (i.e., benchmark parameter) is 10%; Effective range is 8%-12%.

[0064] Furthermore, traversing along the hierarchical path A01-B02→A01→G001, the differentiated overlay layers of each subordinate organization are read:

[0065] East China Branch (A01-B02): No difference in CR-001 (unmodified);

[0066] Company B (A01): Differentiated overlay storage of CR-001's differential segments, specifically "change ratio threshold = 9%" (not exceeding the standard range of 8%-12%).

[0067] The final target difference segment obtained: [{Organization ID: A01, Parameter: Change Ratio Threshold, Value: 9%}].

[0068] Furthermore, a rule tree dynamic merging algorithm is adopted, which incorporates the difference segments from Company B based on the baseline rule tree:

[0069] The baseline rule tree threshold node is set to 10%, and replaced with 9% of the difference segment;

[0070] The core logic (signing supplementary agreements / economic certificates) remains unchanged;

[0071] The final execution rules after the merger: Contract change ratio ≥ 9% → Sign a supplementary agreement; < 9% → Economic certificate (threshold 9%, core logic inherits the baseline).

[0072] Finally, the system calls the rule execution engine, inputting the business request data (change rate 8%) and the final execution rule (threshold 9%):

[0073] Condition judgment: 8% < 9%, triggering the execution action of generating economic certificates and generating processing results; the results can be pushed to the business system interface of the East China branch.

[0074] In this embodiment of the invention, the merged final execution rule retains the core logic of the group's business rules while incorporating the personalized configurations of subordinate organizations. This allows for the processing of business requests using the merged final execution rule, improving the accuracy of business request processing. Furthermore, the business rules at the baseline layer and the differences in the differentiated overlay layer are configured through visual technology, eliminating the need for technical personnel to modify program code and improving rule maintenance efficiency.

[0075] Example 2

[0076] Figure 2 A flowchart illustrating a business request processing method is provided in this embodiment of the invention. See also... Figure 2 The method includes the following steps:

[0077] S201. In response to the business rule configuration request from the main control organization, enter the first visual configuration interface.

[0078] Among them, the business rule configuration request is a technical request initiated by the main control organization (such as the group headquarters) to configure baseline business rules that are effective across the entire group. It must carry core parameters such as the main control organization identifier and the configuration type (add / modify baseline rule), and is the technical trigger condition for redirecting to the configuration interface. The first visual configuration interface is a graphical interactive interface specifically designed for the main control organization to configure baseline-level business rules. It supports complete rule logic configuration (such as dragging and dropping conditions / execution nodes) and global parameter settings.

[0079] In some embodiments, a preset request listening module captures business rule configuration requests initiated by the main management organization; verifies whether the organization identifier carried in the request is the main management organization identifier (such as matching the preset group ID); after the verification is successful, the front-end interface is routed and redirected, loading and displaying the first visual configuration interface designed specifically for baseline configuration, providing an interactive entry point for subsequent baseline business rule configuration.

[0080] Understandably, by replacing code writing with a graphical (drag and drop, form input) interface, business personnel in the main control organization can complete the baseline rule configuration without a technical background, thus improving configuration efficiency.

[0081] S202. In response to the business rule configuration operation of the main control organization in the first visual configuration interface, the configured business rules are persistently stored in the baseline layer corresponding to the main control organization.

[0082] In some embodiments, the monitoring organization submits the configuration on the first visual configuration interface, performs structured parsing on the configured business rules (e.g., converting the graphical configuration into a machine-readable rule model); performs integrity verification on the parsed rules (e.g., whether core logic is missing, whether the baseline parameters are valid); after the verification is passed, the structured rule data is persistently stored in the database table corresponding to the baseline layer, and a unique rule ID is generated for subsequent indexing.

[0083] Understandably, persistent storage prevents rules from being lost due to system restarts or memory release, and structured storage formats (such as JSON) facilitate direct calls in subsequent steps without the need for secondary parsing.

[0084] S203. In response to a business rule configuration request from any subordinate organization at any level, enter the second visual configuration interface.

[0085] The second visual configuration interface is a graphical interactive interface designed specifically for subordinate organizations to configure differentiated rules. Its core features are associating with baseline rules and only opening the modifiable scope. It can include a business rule display area, a modifiable parameter editing area, and a difference preview area, but does not support modifying the core logic of business rules.

[0086] In some embodiments, the request listening module captures business rule configuration requests initiated by subordinate organizations, verifies whether the organization identifier in the request belongs to the subordinate organization level (excluding the main control organization); after the verification is successful, a second visual configuration interface designed for differentiated configuration is loaded and displayed. The interface is associated by default with the list of configurable business rules of the subordinate organization, providing an interactive basis for subsequent modifications based on business rules.

[0087] S204. In response to detecting that a subordinate organization has the authority to modify business rules, retrieve the configured business rules from the baseline layer and display them on the second visual configuration interface.

[0088] In some embodiments, the system receives an operation instruction from a subordinate organization to select a certain business rule, performs a permission check based on the subordinate organization's identifier and the preset modifiable permissions of the business rule, and if the check passes (the subordinate organization has the permission to modify the rule), it calls the corresponding structured rule data from the baseline layer, parses the rule data into a graphical format, and displays it on the second interface in a modifiable / non-modifiable category, providing clear guidance for the subordinate organization's modification operation.

[0089] Understandably, permission checks can intercept unauthorized operations (such as when subordinate organizations attempt to modify core logic), preventing the core control attributes of business rules from being compromised and technically ensuring that the group's standardization requirements are not violated.

[0090] S205. In response to a subordinate organization's modification and submission of any displayed business rule, determine the differences between the modified business rule and the original business rule, and persistently store the differences in the corresponding differential overlay layer of the subordinate organization.

[0091] In some embodiments, the rule modification submission operation of subordinate organizations is captured, and the modified rule data and the original baseline rule data are obtained; the rule comparison algorithm is invoked to automatically extract the difference fields between the two and generate structured difference fragments; the difference fragments are associated with the subordinate organization identifier and business rule ID, and persistently stored in the database table corresponding to the difference overlay layer.

[0092] The solution of this invention requires no code development and can be configured through visual operation, reducing reliance on professional technical personnel and improving the efficiency of rule configuration. The baseline layer of the main control organization ensures the consistency of global business rules, and subordinate organizations only need to store the differences, which avoids the duplication of storing all rules and optimizes storage resources.

[0093] In some embodiments, the baseline layer stores the standard value range of the rule parameters corresponding to each business rule. Correspondingly, after generating structured difference fragments, the difference fragments undergo validity verification. For example, if the rule parameter values ​​included in a difference fragment exceed the standard value range of the rule parameters, the difference fragment submitted by the subordinate organization is intercepted, and the subordinate organization is reminded to reconfigure via a prompt message. In this way, abnormal parameters are intercepted upfront during the difference rule configuration stage, technically addressing the issue of invalid / abnormal configurations flowing into downstream processes.

[0094] For example, the original business rules were as follows: Core logic: Contract change ratio ≥ threshold → Sign supplementary agreement; < threshold → Economic certificate; Change ratio threshold is 10%; Effective range is 8%-12%. The revised business rules are as follows: Contract change ratio ≥ threshold → Sign supplementary agreement; < threshold → Economic certificate; Change ratio threshold is 7%; Effective range is 8%-12%. The differentiated segment is: Change ratio threshold is 7%. Because the value of the differentiated segment is lower than the effective range (8%-12%), it needs to be intercepted, and subordinate organizations should be reminded to reconfigure via a notification message. An example notification message is as follows:

[0095] 1. Abnormal parameter: Contract change ratio threshold.

[0096] 2. Current value: 7%.

[0097] 3. Standard value range: 8% ≤ value ≤ 12%.

[0098] 4. Violation type: The current value is below the lower limit of the standard range.

[0099] 5. Operation Guidelines: Please adjust the contract change ratio to the range of 8%-12% and resubmit; if special adjustments are required, please contact the group's management department to apply for a scope change.

[0100] In some embodiments, in response to triggering the comparison function, subordinate organizations that differ from the main managing organization are highlighted. This visual highlighting enables rapid identification of differing organizations, technically solving the problem of locating discrepancies among a vast number of organizations.

[0101] Example 3

[0102] Figure 3 A flowchart illustrating a business request processing method is provided in this embodiment of the invention. See also... Figure 3 The method includes the following steps:

[0103] S301. Receive pending business requests sent by the business request source organization; wherein, the business request source organization is the main control organization or subordinate organizations of different levels under the main control organization.

[0104] S302. Based on the preset organizational structure and the organizational identifier of the business request source organization, determine the organizational hierarchy path from the business request source organization to the main control organization.

[0105] S303. In the baseline layer corresponding to the main control organization, obtain the target business rule corresponding to the business request.

[0106] S304. Traverse the organization according to the hierarchical path, and when traversing to a subordinate organization at a certain level, read the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization.

[0107] S305. The rule tree dynamic merging algorithm is adopted to merge the target business rules and the target difference fragments, and output the final execution rules.

[0108] In this embodiment of the invention, the specific implementation process of steps S301-S305 can be found in the description of the above embodiments, and will not be repeated here.

[0109] S306. Store the final execution rules obtained after merging into a multi-level cache.

[0110] In some embodiments, a two-level caching architecture can be adopted, consisting of a local memory cache (such as Caffeine) and a distributed cache (such as Redis). The local cache is used for fast access on a single node, while the distributed cache is used for sharing rules across multiple nodes. The structured final execution rules (such as rule tree objects) are serialized into a storable format (such as JSON) and then cached.

[0111] S307. Process the business request according to the final execution rules and output the business request processing result.

[0112] S308. In response to receiving another pending business request of the same type from the business request source organization, retrieve the final execution rule from the multi-level cache and process the business request according to the final execution rule.

[0113] In some embodiments, a new request is identified as a similar request by comparing its organization identifier and business type with those of historical requests. For similar business requests, the local memory cache is queried first to obtain the corresponding final execution rule. If the local cache is not found, the distributed cache is queried. If the distributed cache is found, the corresponding final execution rule is obtained and synchronously updated to the local cache. Then, the final execution rule obtained from the cache is used to repeat the processing logic of S307, without needing to re-execute the "hierarchical path determination → difference fragment reading → rule merging" process, and quickly outputs the processing result.

[0114] By using this invention, business requests of the same type issued by the same organization can directly invoke the corresponding final execution rule in the cache, which can not only improve the efficiency of business request processing, but also reduce real-time computing overhead.

[0115] Example 4

[0116] Figure 4 This is a schematic diagram of a service request processing apparatus provided in an embodiment of the present invention. This apparatus can execute any service request processing method of the present invention. For example... Figure 4 As shown, the service request processing device includes:

[0117] The request receiving module 401 is used to receive pending business requests sent by the business request source organization; wherein the business request source organization is the main control organization or subordinate organizations of different levels under the main control organization.

[0118] The path determination module 402 is used to determine the organizational hierarchy path from the business request source organization to the main control organization based on the preset organizational structure and the organizational identifier of the business request source organization.

[0119] The first acquisition module 403 is used to acquire the target business rule corresponding to the business request from the baseline layer corresponding to the main control organization; wherein, the baseline layer is used to store at least one globally effective business rule configured through visual configuration technology;

[0120] The second acquisition module 404 is used to traverse according to the organizational hierarchy path, and each time a subordinate organization at a certain level is traversed, it reads the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization; wherein, the differential layer overlay layer is used to store the difference fragments that are different from the business rule configured through visual configuration technology.

[0121] The merging module 405 is used to merge the target business rules and the target difference fragments using a rule tree dynamic merging algorithm, and output the final execution rules.

[0122] Processing module 406 is used to process business requests according to the final execution rules and output the business request processing results.

[0123] In some embodiments, when traversing according to the organizational hierarchy path, and reading the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization at a certain level, the second acquisition module 404 is specifically used for:

[0124] The process traverses the organizational hierarchy path, and when it reaches a subordinate organization at a certain level, if the differential layer overlay corresponding to that subordinate organization has a differential fragment that corresponds to the target business rule, then that differential fragment is output as the target differential fragment.

[0125] If the differential layer overlay corresponding to the subordinate organization at this level does not contain a differential fragment corresponding to the target business rule, then the subordinate organizations at the previous level are traversed, and the target differential fragment corresponding to the target business rule is read from the differential layer overlay corresponding to the subordinate organization at the previous level.

[0126] In some embodiments, it also includes:

[0127] The first configuration response module is used to respond to the business rule configuration request from the main management organization and enter the first visual configuration interface;

[0128] The first configuration module is used to respond to the business rule configuration operation of the main control organization in the first visual configuration interface, and to persistently store the configured business rules in the baseline layer corresponding to the main control organization.

[0129] In some embodiments, it also includes:

[0130] The second configuration response module is used to respond to business rule configuration requests from any subordinate organization at any level and enter the second visual configuration interface;

[0131] The display module is used to retrieve the configured business rules from the baseline layer and display them on the second visual configuration interface in response to the detection that a subordinate organization has the authority to modify business rules.

[0132] The second configuration module is used to respond to any modification and submission of the business rule displayed by the subordinate organization, determine the difference between the modified business rule and the original business rule, and persistently store the difference in the corresponding differential overlay layer of the subordinate organization.

[0133] In some embodiments, the baseline layer stores the standard value range of the rule parameters corresponding to each business rule;

[0134] Correspondingly, it also includes:

[0135] The interception module is used to intercept the difference fragments submitted by subordinate organizations when the values ​​of the rule parameters included in the difference fragments exceed the standard value range of the rule parameters, and to remind the subordinate organizations to reconfigure through a prompt message.

[0136] In some embodiments, it also includes:

[0137] The comparison module is used to highlight subordinate organizations that differ from the main management organization in response to the triggering of the comparison function.

[0138] In some embodiments, it also includes:

[0139] The caching module is used to store the final execution rules obtained after merging into a multi-level cache;

[0140] The request fast processing module is used to respond to the same type of pending business requests sent by the business request source organization, retrieve the final execution rule from the multi-level cache, and process the business request according to the final execution rule.

[0141] The service request processing apparatus provided in the embodiments of the present invention can execute the service request processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0142] According to embodiments of the present invention, the present invention also provides an electronic device, a readable storage medium, and a computer program product.

[0143] Example 5

[0144] Figure 5 A schematic diagram of the structure of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the invention described and / or claimed herein.

[0145] like Figure 5 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory 12 or a random access memory 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 12 or loaded from storage unit 18 into the random access memory 13. The random access memory 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, read-only memory 12, and random access memory 13 are interconnected via a bus 14. An input / output interface 15 is also connected to the bus 14.

[0146] Multiple components in electronic device 10 are connected to input / output interface 15, including: input unit 16; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disks, optical disks, etc.; and communication unit 19, such as network interface cards, modems, wireless transceivers, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0147] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing units, graphics processing units, various special-purpose artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as performing business request processing methods.

[0148] In some embodiments, the service request processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via read-only memory 12 and / or communication unit 19. When the computer program is loaded into random access memory 13 and executed by processor 11, one or more steps of the service request processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to execute the service request processing method by any other suitable means (e.g., by means of firmware).

[0149] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), application-specific standard products (ASICs), systems-on-a-chip (SoCs), complex programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0150] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable business request processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0151] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, optical fibers, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0152] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device or liquid crystal display for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0153] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0154] A computing system can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product within the cloud computing service system to address the shortcomings of traditional physical hosts and virtual private servers, such as high management difficulty and weak business scalability.

[0155] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0156] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A business request processing method, characterized in that, include: Receive pending business requests sent by a business request source organization; wherein, the business request source organization is the main control organization or subordinate organizations of different levels under the main control organization; Based on the preset organizational structure and the organizational identifier of the business request source organization, determine the organizational hierarchy path from the business request source organization to the main control organization; In the baseline layer corresponding to the main control organization, the target business rule corresponding to the business request is obtained; wherein, the baseline layer is used to store at least one globally effective business rule configured through visual configuration technology; The process traverses the organizational hierarchy path, and at each level of subordinate organization, it reads the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization; wherein, the differential layer overlay layer is used to store the difference fragments that are different from the business rule and configured through visual configuration technology. A rule tree dynamic merging algorithm is used to merge the target business rule with the target difference fragment, and output the final execution rule; The business request is processed according to the final execution rules, and the business request processing result is output.

2. The method according to claim 1, characterized in that, The step of traversing according to the organizational hierarchy path, and reading the target difference fragment corresponding to the target business rule from the differential layer overlay layer corresponding to the subordinate organization at each level, includes: The process is traversed according to the organizational hierarchy path. When a subordinate organization at a certain level is encountered, if the differential layer overlay corresponding to the subordinate organization at that level has a differential fragment that corresponds to the target business rule, then the differential fragment is output as the target differential fragment. If the differential layer overlay corresponding to the subordinate organization at this level does not contain a differential fragment corresponding to the target business rule, then the subordinate organizations at the previous level are traversed, and the target differential fragment corresponding to the target business rule is read from the differential layer overlay corresponding to the subordinate organization at the previous level.

3. The method according to claim 1, characterized in that, Also includes: In response to the business rule configuration request from the main management organization, the first visual configuration interface is entered; In response to the business rule configuration operation performed by the main management organization on the first visual configuration interface, the configured business rules are persistently stored in the baseline layer corresponding to the main management organization.

4. The method according to claim 3, characterized in that, Also includes: In response to a business rule configuration request from any subordinate organization at any level, enter the second visual configuration interface; In response to detecting that the subordinate organization has the authority to modify business rules, the configured business rules are retrieved from the baseline layer and displayed on the second visual configuration interface; In response to any modification and submission of the business rule displayed by the subordinate organization, the difference segment between the modified business rule and the original business rule is determined, and the difference segment is persistently stored in the differential overlay layer corresponding to the subordinate organization.

5. The method according to claim 4, characterized in that, The baseline layer stores the standard value range of the rule parameters corresponding to each business rule; the method further includes: If the value of the rule parameter included in the difference fragment exceeds the standard value range of the rule parameter, the difference fragment submitted by the subordinate organization is intercepted, and the subordinate organization is reminded to reconfigure via a prompt message.

6. The method according to claim 4, characterized in that, Also includes: In response to the trigger comparison function, subordinate organizations that differ from the main management organization will be highlighted.

7. The method according to claim 1, characterized in that, Also includes: The final execution rules obtained after merging are stored in a multi-level cache; In response to receiving another pending business request of the same type from the business request source organization, the final execution rule is obtained from the multi-level cache, and the business request is processed according to the final execution rule.

8. A service request processing apparatus, characterized in that, include: The request receiving module is used to receive pending business requests sent by a business request source organization; wherein, the business request source organization is the main control organization or subordinate organizations of different levels under the main control organization; The path determination module is used to determine the organizational hierarchy path from the business request source organization to the main control organization based on the preset organizational structure and the organization identifier of the business request source organization; The first acquisition module is used to acquire the target business rule corresponding to the business request from the baseline layer corresponding to the main control organization; wherein, the baseline layer is used to store at least one globally effective business rule configured through visual configuration technology; The second acquisition module is used to traverse according to the organizational hierarchy path, and each time a subordinate organization at a certain level is traversed, it reads the target difference fragment corresponding to the target business rule from the difference layer overlay layer corresponding to the subordinate organization; wherein, the difference layer overlay layer is used to store difference fragments that are different from the business rule configured through visual configuration technology. The merging module is used to merge the target business rule with the target difference fragment using a rule tree dynamic merging algorithm, and output the final execution rule; The processing module is used to process the business request according to the final execution rules and output the business request processing result.

9. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to perform the method of any one of claims 1-7.

Images