Business processing method and device, computer device, readable storage medium and program product

Abstract

The application relates to a service processing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: in response to the triggering of a service request, preset scene mapping parameters, preset service control rule parameters and request attribute information of the service request are acquired; the preset scene mapping parameters are matched with the request attribute information in multiple levels based on a preset level matching rule, and a target service control rule is obtained according to a first level matching result and the preset service control rule parameters; a target service processing strategy corresponding to the service request is constructed based on the target service control rule; and the target service processing strategy is used for processing the service request. The method can improve the efficiency of service processing.

Description

Technical Field

[0001] This application relates to the field of business processing technology, and in particular to a business processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] As financial institutions develop their businesses, their business processing logic becomes increasingly complex and varied, often requiring differentiated processing based on different transaction types, channels, customer attributes, and other multi-dimensional conditions.

[0003] In traditional technologies, hard-coding is typically used. Developers write the entire set of business processing logic into the business code based on business requirements, forming multiple complete business processing strategies. In applications, the business system updates the business processing logic on a relatively long time cycle. Specifically, the business system determines the target business processing strategy based on attributes such as the type and channel of the business request through hard-coded conditional statements. The target business processing strategy is then used to process the business request.

[0004] However, since the business processing logic hard-coded in the business code is fixed, updating the business processing logic requires modifying the code, compiling and testing. Moreover, the update cycle of the business processing logic is long and there is a lag, resulting in poor efficiency of business processing. Summary of the Invention

[0005] Therefore, it is necessary to provide a business processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product to address the aforementioned technical problems.

[0006] Firstly, this application provides a business processing method, including:

[0007] In response to the triggering of a business request, obtain preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request;

[0008] Based on the preset hierarchical matching rules, the preset scenario mapping parameters are used to perform multi-level matching on the request attribute information, and hierarchical matching is performed according to the first-level matching result and the preset business control rule parameters to obtain the target business control rule;

[0009] Based on the target business control rules, a target business processing strategy corresponding to the business request is constructed; the target business processing strategy is used to process the business request.

[0010] In one embodiment, the request attribute information includes an event identifier and a dimension identifier;

[0011] The method involves performing multi-level matching of the request attribute information using the preset scenario mapping parameters based on preset hierarchical matching rules, and performing hierarchical matching based on the first-level matching result and the preset business control rule parameters to obtain the target business control rule, including:

[0012] Based on the event identifier and the dimension identifier, a first-level match is performed in the preset scene mapping parameters according to the first association relationship to obtain the scene code;

[0013] Based on the scenario code, a second-level matching is performed on the preset business control rule parameters according to the second association relationship to obtain the target business control rule.

[0014] In one embodiment, the method further includes:

[0015] Obtain event configuration data and dimension configuration data; the event configuration data includes event identifiers, and the dimension configuration data includes dimension identifiers.

[0016] A scene combination is constructed based on the event identifier and the dimension identifier, and the correspondence between the event identifier, the dimension identifier and the scene code corresponding to the scene combination is stored in the scene definition table to obtain the first association relationship;

[0017] Receive the business control rule configuration data corresponding to the scenario code, store the correspondence between the scenario code and the business control rule configuration data in the business control rule table, and obtain the second association relationship.

[0018] In one embodiment, the step of performing a first-level matching in the preset scene mapping parameters according to the event identifier and the dimension identifier, based on a first association relationship, to obtain the scene code includes:

[0019] Based on the event identifier and the first association relationship, determine the candidate scene code corresponding to the event identifier in the preset scene mapping parameters;

[0020] The target scene code is determined from the candidate scene codes based on the dimensional identifier.

[0021] In one embodiment, the step of performing a second-level matching based on the scenario code and the preset business control rule parameters according to the second association relationship to obtain the target business control rule includes:

[0022] Based on the scenario code and the second association relationship, a set of candidate business control rules corresponding to the scenario code is determined from the preset business control rule parameters;

[0023] Based on preset rule filtering conditions, the target business control rule is determined from the set of candidate business control rules.

[0024] In one embodiment, the method further includes:

[0025] Receive a rule update request, the rule update request including parameter type identifier and update data;

[0026] Based on the parameter type identifier and the update data, update the preset scene mapping parameters and / or the preset business control rule parameters to obtain the updated preset scene mapping parameters and / or preset business control rule parameters.

[0027] In one embodiment, after constructing the target business processing strategy corresponding to the business request based on the target business control rule, the method further includes:

[0028] Store the target business processing strategy and the association between the business request and the target business processing strategy in the business processing strategy table;

[0029] In response to the re-triggering of the service request, the target service processing strategy for the service request is determined based on the service processing strategy table, and the service request is processed based on the target service processing strategy.

[0030] Secondly, this application also provides a business processing apparatus, comprising:

[0031] The first acquisition module is used to acquire preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request in response to the triggering of a business request.

[0032] The matching module is used to perform multi-level matching of the request attribute information with the preset scenario mapping parameters based on preset hierarchical matching rules, and to perform hierarchical matching based on the first-level matching result and the preset business control rule parameters to obtain the target business control rule;

[0033] A construction module is used to construct a target business processing strategy corresponding to the business request based on the target business control rules; the target business processing strategy is used to process the business request.

[0034] In one embodiment, the request attribute information includes an event identifier and a dimension identifier;

[0035] The matching module is specifically used to perform a first-level matching in the preset scene mapping parameters according to the event identifier and the dimension identifier, based on a first association relationship, to obtain a scene code;

[0036] Based on the scenario code, a second-level matching is performed on the preset business control rule parameters according to the second association relationship to obtain the target business control rule.

[0037] In one embodiment, the device further includes:

[0038] The second acquisition module is used to acquire event configuration data and dimension configuration data; the event configuration data includes an event identifier, and the dimension configuration data includes a dimension identifier.

[0039] The first storage module is used to construct a scene combination based on the event identifier and the dimension identifier, and store the correspondence between the event identifier, the dimension identifier and the scene code corresponding to the scene combination in the scene definition table to obtain the first association relationship;

[0040] The second storage module is used to receive the business control rule configuration data corresponding to the scene code, store the correspondence between the scene code and the business control rule configuration data in the business control rule table, and obtain the second association relationship.

[0041] In one embodiment, the matching module is specifically used to determine the candidate scene code corresponding to the event identifier in the preset scene mapping parameters based on the event identifier and the first association relationship;

[0042] The target scene code is determined from the candidate scene codes based on the dimensional identifier.

[0043] In one embodiment, the matching module is specifically used to determine a set of candidate business control rules corresponding to the scene code from the preset business control rule parameters based on the scene code and the second association relationship;

[0044] Based on preset rule filtering conditions, the target business control rule is determined from the set of candidate business control rules.

[0045] In one embodiment, the device further includes:

[0046] The receiving module is used to receive rule update requests, wherein the rule update requests include parameter type identifiers and update data;

[0047] The update module is used to update the preset scene mapping parameters and / or the preset business control rule parameters according to the parameter type identifier and the update data, so as to obtain the updated preset scene mapping parameters and / or preset business control rule parameters.

[0048] In one embodiment, the device further includes:

[0049] The third storage module is used to store the target business processing strategy and the association between the business request and the target business processing strategy in the business processing strategy table;

[0050] The response module is used to respond to the re-triggering of the business request, determine the target business processing strategy for the business request based on the business processing strategy table, and perform business processing on the business request based on the target business processing strategy.

[0051] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0052] In response to the triggering of a business request, obtain preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request;

[0053] Based on the preset hierarchical matching rules, the preset scenario mapping parameters are used to perform multi-level matching on the request attribute information, and hierarchical matching is performed according to the first-level matching result and the preset business control rule parameters to obtain the target business control rule;

[0054] Based on the target business control rules, a target business processing strategy corresponding to the business request is constructed; the target business processing strategy is used to process the business request.

[0055] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0056] In response to the triggering of a business request, obtain preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request;

[0057] Based on the preset hierarchical matching rules, the preset scenario mapping parameters are used to perform multi-level matching on the request attribute information, and hierarchical matching is performed according to the first-level matching result and the preset business control rule parameters to obtain the target business control rule;

[0058] Based on the target business control rules, a target business processing strategy corresponding to the business request is constructed; the target business processing strategy is used to process the business request.

[0059] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0060] In response to the triggering of a business request, obtain preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request;

[0061] Based on the preset hierarchical matching rules, the preset scenario mapping parameters are used to perform multi-level matching on the request attribute information, and hierarchical matching is performed according to the first-level matching result and the preset business control rule parameters to obtain the target business control rule;

[0062] Based on the target business control rules, a target business processing strategy corresponding to the business request is constructed; the target business processing strategy is used to process the business request.

[0063] The aforementioned business processing methods, apparatus, computer equipment, computer-readable storage media, and computer program products, by decomposing business processing logic into mutually independent preset scenario mapping parameters and preset business control rule parameters, and performing multi-level matching of request attribute information with these two types of parameters, achieve the extraction of business rules from fixed code and transform them into parameterized multi-level matching. This enables the dynamic construction of a target business processing strategy adapted to the current business request based on request attribute information. Therefore, when business requirements change, only the corresponding preset scenario mapping parameters and preset business control rule parameters need to be updated, without modifying, recompiling, or testing the business code. This reduces the complexity of updating business processing strategies and, upon receiving each business request, constructs a target business processing strategy matching the current business request in real time, improving the timeliness of the target business processing strategy and thus enhancing the flexibility and efficiency of business processing. Attached Figure Description

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

[0065] Figure 1 This is a flowchart illustrating a business processing method in one embodiment;

[0066] Figure 2 This is a flowchart illustrating multi-level matching based on event identifiers and dimension identifiers in one embodiment.

[0067] Figure 3 This is a flowchart illustrating the process of configuring preset scene mapping parameters and preset business control rule parameters in one embodiment.

[0068] Figure 4This is a flowchart illustrating the first-level matching process based on event identifier and dimension identifier in one embodiment.

[0069] Figure 5 This is a flowchart illustrating the second-level matching process based on scene codes in one embodiment;

[0070] Figure 6 This is a flowchart illustrating an example of a business processing method in one embodiment;

[0071] Figure 7 This is a flowchart illustrating the process of updating preset scene mapping parameters and preset business control rule parameters in one embodiment.

[0072] Figure 8 This is a structural block diagram of a service processing device in one embodiment;

[0073] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0074] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0075] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0076] In one embodiment, such as Figure 1 As shown, a business processing method is provided. This embodiment illustrates the method applied to a server. It is understood that this method can also be applied to a terminal, or to a system including both a terminal and a server, and is implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0077] Step 102: In response to the triggering of a business request, obtain the preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request.

[0078] In this embodiment, the server includes a business processing system and a scenario-based parameter platform. The business processing system can be the core system of a financial institution used to process business requests. The scenario-based parameter platform is used to parameterize the business processing logic and provide the core system with real-time target business processing strategies. A business request can be a request initiated by a teller in a counter system based on a user's business needs, or it can be a business request initiated by a channel such as mobile banking. After receiving a business request from the counter system, the server responds to the triggering of the business request by parsing the request to obtain the request attribute information contained in the request. Furthermore, the server obtains preset scenario mapping parameters and preset business control rule parameters from the scenario-based parameter platform.

[0079] In a specific embodiment, the request attribute information of the business request may include an event identifier and a dimension identifier. The event identifier is used to identify the type of the current transaction, such as a deposit transaction, a withdrawal transaction, an account opening event, or a loss reporting event. The unread information is used to describe the context of the current transaction, such as dimension information such as channel type, institution code, customer type, and account attributes. The channel type may be counter banking, mobile banking, online banking, etc., the customer type may be corporate or personal banking, and the account attribute may be a Class I account, a Class II account, or a Class III account.

[0080] The scenario-based parameter platform is a configuration management component independent of the core system. Business personnel can use the platform to maintain the relationships between events, dimensions, and scenario codes, as well as the relationships between scenario codes and specific business control rules (limits, charges, and status control), in a visual manner. The core system sends parameter retrieval requests to the parameter platform, loading preset scenario mapping parameters and preset business control rule parameters into local memory or cache. The preset scenario mapping parameters record the correspondence between candidate events, candidate dimensions, and scenario codes in the form of a data table; the preset business control rule parameters can record the limit rule identifier, charge rule identifier, and status control rule identifier bound to each scenario code.

[0081] Step 104: Based on the preset hierarchical matching rules, perform multi-level matching of the preset scenario mapping parameters to the request attribute information, and perform hierarchical matching according to the first-level matching result and the preset business control rule parameters to obtain the target business control rule.

[0082] In this embodiment, the preset hierarchical matching rule can be a multi-level independent matching rule. The server performs a first-level matching for scene positioning based on preset scene mapping parameters and request attribute information to obtain a first-level matching result. The first-level matching result represents the scene-specific matching result of the current business request. Then, the server performs a second-level matching of business rules based on the first-level matching result and preset business control rule parameters to determine the target business control rule corresponding to the scene to which the current business request belongs. Each level of matching is performed based on the association relationships in the parameter table, which consists of the parameter table corresponding to the preset scene mapping parameters and the parameter table corresponding to the preset business control rule parameters. The first-level matching level is higher than the second-level matching level; that is, the terminal prioritizes performing a first-level matching on the request attribute information of the business request and uses the first-level matching result as one of the matching conditions for the second-level matching. The first-level matching result and the preset business control rule parameters are then used for the second-level matching to achieve multi-level matching.

[0083] Step 106: Construct the target business processing strategy corresponding to the business request based on the target business control rules.

[0084] The target business processing strategy is used to process business requests.

[0085] In this embodiment, the server dynamically constructs the target business processing strategy corresponding to the current business request based on the target business control rules. These target business control rules include limit control rules (e.g., "single transaction limit of 50,000 yuan, daily cumulative limit of 200,000 yuan"), fee control rules (e.g., "a handling fee of 0.1% of the transaction amount, minimum 2 yuan, maximum 50 yuan"), and status control rules (e.g., "account status must be normal and not frozen, voucher status must be valid"). The server constructs a structured target business processing strategy based on the business semantics of the target business control rules and the preset execution order.

[0086] Specifically, the server can construct the target business processing policy by filling the metadata in the target business control rules into the preset business processing policy template. For example, the server can determine the preset business processing policy template based on the event identifier or scenario code. The replaceable metadata in the preset business processing policy templates corresponding to different events or different scenarios are different.

[0087] In a specific embodiment, taking a deposit transaction request as an example, the target business processing strategy corresponding to the request can be to first execute the status verification rule (checking whether the account is allowed to deposit), then execute the limit verification rule (checking whether the limit has been exceeded), and finally execute the fee rule (calculating and deducting the handling fee). This execution order can be determined by the priority field pre-configured by the parameter platform or the default order of the rule type, that is, there is no need to hardcode it in the code.

[0088] In one embodiment, the server dynamically constructs and executes business processing strategies based on target business control rules. Specifically, when a transaction request is a deposit event and the matched scenario code corresponds to the "document expiration deposit restriction scenario," the server first obtains the status word code of the current account subject from the status code description table according to the status control rules associated with the scenario code. Then, it uses the status attribute code parameter table to map the status word code to a recognizable status attribute value and compares it with the actual status value of the account in the transaction. Next, based on the matched status word code and the deposit event, the server queries the status event lookup table to obtain the default allow flag. For example, if the account status is normal, deposit is allowed by default. However, since this scenario is configured with a scenario exception flag, the server needs to further query the status scenario parameter table according to the scenario code to determine that the status word allow flag is overridden to "not allowed" in this scenario, and finally executes the process of rejecting the deposit.

[0089] In an optional embodiment, in a smart home device linkage control scenario, when the control terminal receives a "start movie viewing mode" service request, it first obtains preset scene mapping parameters, preset service control rule parameters, and event information (e.g., "movie viewing mode started") and dimension information (e.g., time period "evening", light intensity "low", user identity "adult") contained in the request. Then, it performs a first-level matching between the event and dimension information and the first association relationship in the preset scene mapping parameters to obtain the corresponding scene code. Next, based on this scene code, it matches specific device control rules from the preset device control rule parameters through a second association relationship. Examples include: projector turning on, screen lowering, audio input switching, lights dimming to 30%, and air conditioner set to 24°C. Finally, it dynamically constructs a target control strategy containing these action sequences and executes them sequentially, thereby achieving automated deployment of the movie viewing mode. The entire service processing process does not require modification of the control program code; only the association relationships in the parameter platform need to be adjusted to flexibly adapt to newly added dimensions or device rules, improving the efficiency of service request processing.

[0090] In the aforementioned business processing method, by decomposing the business processing logic into mutually independent preset scenario mapping parameters and preset business control rule parameters, and performing multi-level matching between request attribute information and these two types of parameters, the business rules are extracted from fixed code and transformed into parameterized multi-level matching. This allows for the dynamic construction of a target business processing strategy adapted to the current business request based on request attribute information. Therefore, when business requirements change, only the corresponding preset scenario mapping parameters and preset business control rule parameters need to be updated, without modifying, recompiling, or testing the business code. This reduces the complexity of updating the business processing strategy. Furthermore, upon receiving each business request, a target business processing strategy matching the current business request is constructed in real time, improving the timeliness of the target business processing strategy and thus enhancing the flexibility and efficiency of business processing.

[0091] In one exemplary embodiment, the requested attribute information includes an event identifier and a dimension identifier, such as... Figure 2 As shown, step 104 includes steps 202 to 204. Wherein:

[0092] Step 202: Based on the event identifier and dimension identifier, perform first-level matching in the preset scene mapping parameters according to the first association relationship to obtain the scene code.

[0093] In this embodiment, the server first performs a first-level matching for scene localization. The server uses the extracted event identifier and dimension identifier as input and searches for matching records in a preset scene mapping parameter. The preset scene mapping parameter can be a data table storing the first association between candidate events, candidate dimensions, and scene codes. For the first-level matching, the server first performs a precise match between the event information and the candidate event field in the table, filtering out all event matching results containing the event identifier. Then, in the filtered event matching results, the server matches the dimension information with the candidate dimension combination defined for each event matching result. The server uses the scene code corresponding to the time matching result as the first-level matching result. If multiple records are matched, for example, if there is a generalized scene limited to "channel = counter" and a refined scene limited to "channel = counter + customer type = individual + account attribute = type one account", the server selects one according to a preset priority rule. For example, the server can select the refined scene with the most dimensions, or select the scene with the highest value according to the scene priority field pre-configured in the parameter table. If no record is matched, the server can return the default scene code or trigger an exception handling process.

[0094] In an optional embodiment, when matching dimension information with candidate dimension combinations, the server can employ an exact matching strategy, determining a successful match only when all dimension fields in the request completely match the dimension combinations in the record; the server can also employ a subset matching strategy, considering a match as long as the dimension information in the business request contains all dimension fields defined in the record, allowing requests to carry additional dimensions; the server can also configure a weight value for each dimension field, calculate a weighted score based on the matched dimension fields, and use results exceeding a preset threshold as event matching results.

[0095] Step 204: Based on the scenario code, perform second-level matching in the preset business control rule parameters according to the second association relationship to obtain the target business control rule.

[0096] In this embodiment, after completing the first-level matching, the server performs the second-level matching corresponding to the business rule. The server takes the scenario code obtained from the first-level matching as input and searches for the business control rule record associated with that scenario code in the preset business control rule parameters. The preset business control rule parameters are also stored in a data table, recording the second association between the scenario code and the limit control rule identifier, fee control rule identifier, and status control rule identifier. The server performs a precise query based on the scenario code to obtain all business control rule identifiers configured under that scenario, thus obtaining the target business control rule. A scenario may be associated with multiple types of control rules simultaneously (e.g., a deposit scenario may be associated with limit rules, fee rules, and status rules simultaneously), or it may be associated with only one or two of them. The server loads the specific rule content corresponding to these rule identifiers (e.g., limit threshold, fee rate value, allowed status value) from the rule definition table to form the target business control rule set. If multiple rules of the same type are configured under the same scenario code (for example, multiple charging rules are associated with the same scenario, each applicable to different amount ranges), the server will further perform secondary filtering based on additional attributes in the business request (e.g., transaction amount, customer level), or select the only applicable target business control rule according to rule priority.

[0097] In this embodiment, a two-layer parameterized matching mechanism is used to obtain scene code through first-level matching of event identifiers and dimension identifiers, and then to obtain business control rules through second-level matching based on scene code. This mechanism removes the matching path from hard-coded code, so that no program code needs to be modified when adding or adjusting business dimensions and rules. This reduces the maintenance complexity of the bank's core system and improves the response efficiency of business needs.

[0098] In one exemplary embodiment, such as Figure 3As shown, before constructing the target business control rules in real time, it is also necessary to pre-configure the first association relationship and the second association relationship to match the preset scenario mapping parameters and the preset business control rule parameters. The method also includes steps 302 to 306. Among them:

[0099] Step 302: Obtain event configuration data and dimension configuration data.

[0100] The event configuration data includes event identifiers, and the dimension configuration data includes dimension identifiers.

[0101] In this embodiment, before the core system performs business processing, parameter configuration needs to be pre-configured in the server's scenario-based parameter platform. The parameter configuration required for scenario-based processing includes scenario-based common parameter configuration, which controls scenario settings for scenario-based parameters. Scenario-based internal parameter configuration includes event configuration, dimension configuration, and scenario configuration. Event configuration includes core system events such as account opening, account closing, account suspension, account unblocking, fee collection time, and deposit / withdrawal transaction events. Dimension configuration includes fields or certain interfaces during transactions.

[0102] Step 304: Construct scene combinations based on event identifiers and dimension identifiers, and store the correspondence between event identifiers, dimension identifiers and scene codes corresponding to scene combinations in the scene definition table to obtain the first association relationship.

[0103] In this embodiment of the application, the scenario configuration can be a combination of event configuration and dimension configuration. For example, the card object corresponding to the card replacement event is a personal card (the attribute value corresponding to the dimension configuration), and the account attribute is the scenario code corresponding to a type of account (the attribute value corresponding to the dimension configuration). As a pre-configured scenario, the user can also pre-configure the application scope of each scenario. For example, if the application scope is set to chargeable, it means that the scenario is available.

[0104] Then, the server constructs scene combinations based on event identifiers and dimension identifiers, and stores the correspondence between event identifiers, dimension identifiers and scene codes corresponding to scene combinations in the scene definition table to obtain the first association relationship.

[0105] Step 306: Receive the business control rule configuration data corresponding to the scenario code, store the correspondence between the scenario code and the business control rule configuration data in the business control rule table, and obtain the second association relationship.

[0106] In this embodiment, the business control rule configuration data can be scenario-based deposit parameter configuration. After completing the first association configuration of the scenario mapping parameters, the server further constructs the second association of the business control rule parameters. Specifically, the server receives business control rule configuration data configured for the generated scenario code. This business control rule configuration data can be entered by business personnel through the configuration interface of the parameter platform. The business control rule configuration data includes limit control rules, fee control rules, and status control rules. Each of the limit control rules, fee control rules, and status control rules corresponds to one or more business control rule tables. Specifically, status control parameters are stored in a status attribute code parameter table, a status event lookup table, a status scenario parameter table, and a status code description table. Limit control rules correspond to a limit prototype parameter table, and fee control rules correspond to a scenario fee rate lookup table.

[0107] In one specific embodiment, the prototype parameter table for the limit is shown in Table 1 below:

[0108] Table 1

[0109]

[0110] The scenario fee rate comparison table is shown in Table 2 below:

[0111] Table 2

[0112]

[0113] The status code description table is shown in Table 3 below:

[0114] Table 3

[0115]

[0116] If the status code is the same as the status event lookup table, then the status scenario parameter table and the status event lookup table can be associated. This table is for setting scenario exception codes. For example, if the status control is to prevent certain errors, then the scenario will be excluded from the exception. If the status code is a normal status, then certain scenarios can also be subject to exception control. The error message can be "Normal status XXxxx do not want NNNNN to be withdrawn", where NNNNN is the parameter description field.

[0117] The status attribute code parameter table is shown in Table 4 below:

[0118] Table 4

[0119]

[0120] The status event mapping table is shown in Table 5 below:

[0121] Table 5

[0122]

[0123] The state scenario parameter table is shown in Table 6 below:

[0124] Table 6

[0125]

[0126] The server receives configuration data for business control rules configured for the generated scenario codes. This configuration data associates scenario codes with three types of control rules: limit, charge, and status. Limit control rules are stored in the limit prototype parameter table (dpd_lmt_protp), which establishes a correspondence between the scenario code and the "scenario number combination" field. Charge control rules are stored in the scenario rate lookup table (dpd_sce_codf), which is directly associated with the scenario code through the "scenario code" field. Status control rules are indirectly associated with the scenario code through fields such as "transaction event code" and "status word scenario code" in the status event lookup table (dpd_stswd_event) and the status scenario parameter table (dpd_stswd_scen), and are further supplemented by the status code description table (dpd_stswd) and the status attribute code parameter table (dpd_stswd_value) to complete the mapping of status values. The server stores the correspondence between scenario codes and rule identifiers in the corresponding business control rule table, forming a second association relationship.

[0127] For example, when a business transaction is initiated, the business request itself includes dimension identifiers, including but not limited to customer information, voucher information, and common transaction information (institution, channel, transaction code value, service ID, and region of occurrence). When a transaction is initiated, the server triggers corresponding business events. For example, opening an account may trigger multiple business events (account opening event, deposit event, voucher sale, etc.). Each event may involve different scenario-based deposit parameter controls. For example, the deposit event involves limits, fees, and status control parameter rules, while voucher sale only involves fee control. Furthermore, scenario configuration involves combining event identifiers and dimension identifiers (which can be multiple dimensions combined or a single dimension depending on business needs) into a scenario and configuring the scenario code, such as a scenario with restrictions on deposits upon document expiration.

[0128] In a specific embodiment, for scenario code 001, business personnel can associate it with a single transaction limit of 500,000 in the limit prototype parameter table, a fee rate of 0.1% in the scenario fee rate lookup table, and "account must be normal and not frozen" in the status event lookup table. After receiving the business rule configuration data, the server stores the correspondence between scenario codes and various business control rule identifiers in a preset business control rule parameter table, thereby establishing a second association between scenario codes and specific control rules. This second association, together with the first association, constitutes a complete parameterized matching foundation; that is, the first association is used to map event identifiers and dimension identifiers to scenario codes, and the second association is used to map scenario codes to specific limit, fee, or status control rules.

[0129] In this embodiment, by using parameterized pre-configuration, the scenario definition and rule binding in the business processing logic are stored in the parameter platform in the form of data table association, which realizes the separation of business rules and system code. When adding or adjusting business dimensions and control rules in the future, only the configuration data needs to be modified without changing any program code, thereby reducing the maintenance complexity of business processing rules.

[0130] In one exemplary embodiment, such as Figure 4 As shown, step 202 includes steps 402 to 404. Wherein:

[0131] Step 402: Based on the event identifier and the first association relationship, determine the candidate scene code corresponding to the event identifier in the preset scene mapping parameters.

[0132] In this embodiment, the server first filters all table data containing the event identifier extracted from the business request from preset scene mapping parameters, as a set of candidate scene codes. For example, if the event identifier is "storage event", the server searches for all table data with "storage event" as the candidate event in the first association relationship, and determines the scene code corresponding to "storage event". For example, if the scene codes corresponding to "storage event" include 001, 002, and 003, then scene codes 001, 002, and 003 are used as candidate scene codes.

[0133] Step 404: Determine the target scene code from the candidate scene codes based on the dimension identifier.

[0134] In this embodiment, the server checks each candidate scenario code and its associated candidate dimension combination one by one, matches the dimension identifier carried by the business request with each candidate dimension combination, and selects the scenario code that matches the dimension identifier of the business request from the candidate dimension combinations as the target scenario code. For example, if the requested dimension identifier includes "channel=counter" and "customer type=individual", while candidate scenario code 001 only requires "channel=counter" and candidate scenario code 002 requires "channel=counter + customer type=individual", then the server matches the more precise candidate scenario code 002. Optionally, if there are multiple matching results, a preset matching rule is followed, for example, the candidate scenario code with the most dimensions or the highest priority field is selected as the target scenario code.

[0135] In a specific embodiment, when a business transaction is initiated, the server first identifies the business events triggered by the current transaction. For example, an account opening event may simultaneously trigger multiple sub-events such as account opening, deposit, and certificate sale, as well as the dimension identifier carried by the transaction. The dimension identifier may include customer information, certificate information, institution, channel, transaction code value, service ID, and the region where the event occurred.

[0136] In this embodiment, a two-stage matching strategy of coarse screening by event identifiers and precise positioning by dimension identifiers narrows the matching range of scene codes, improving matching efficiency and accuracy. At the same time, it eliminates the need to write complex nested condition judgments in the code. Matching scene codes based on the scene definition table and the business control rule table can improve matching efficiency.

[0137] In one exemplary embodiment, such as Figure 5 As shown, step 204 includes steps 502 to 504. Wherein:

[0138] Step 502: Based on the scenario code and the second association relationship, determine the set of candidate business control rules corresponding to the scenario code in the preset business control rule parameters.

[0139] In this embodiment, the server first searches for all business control rule data associated with the scenario code in the preset business control rule parameters based on the scenario code obtained from the first-level matching. It then collects the corresponding limit control rules, charging control rules, or status control rules to form a candidate business control rule set. This candidate business control rule set can contain multiple rules; for example, multiple charging rules with different amount ranges may be configured under the same scenario code, or both limit rules and status rules may be configured simultaneously.

[0140] Step 504: Based on the preset rule filtering conditions, determine the target business control rule from the candidate business control rule set.

[0141] In this embodiment of the application, the server determines the final target business control rule from the candidate business control rule set based on preset rule filtering conditions; the preset rule filtering conditions include matching conditions based on additional attributes in the business request (e.g., transaction amount, customer level, timestamp), or selecting the rule with the highest priority based on the priority field pre-configured in the rule definition table.

[0142] In a specific embodiment, such as Figure 6 As shown, the business requests initiated by tellers include transaction requests such as withdrawals and deposits, account opening and closing, reporting and unblocking lost cards, and charging. After receiving the business request, the server performs scenario-based processing, invokes scenario matching, and performs multi-level matching on pre-configured preset scenario mapping parameters and preset business control rule parameters to obtain the target business control rule. Based on the target business control rule, the server dynamically constructs the target business processing strategy. The preset scenario mapping parameters include event configuration, dimension configuration, and scenario configuration; the preset business control rule parameters include status scenario control configuration, limit scenario control, and scenario fee type control. The preset scenario mapping parameters and preset business control rule parameters can be maintained through technical development analysis and BA (Business Analytics) business analysis.

[0143] In this embodiment, a two-stage rule matching process is implemented, which first coarsely filters candidate rules by scenario code and then precisely locates them by business attributes or priorities. This achieves a flexible and configurable mapping from scenario to specific business control rules, avoiding hard coding of rule acquisition logic.

[0144] In one exemplary embodiment, such as Figure 7 As shown, the method further includes steps 702 to 704. Wherein:

[0145] Step 702: Receive a rule update request. The rule update request includes parameter type identifier and update data.

[0146] In this embodiment, the server receives a rule update request triggered by a parameter platform or business personnel. The rule update request includes a parameter type identifier and update data. The parameter type identifier indicates that the update operation targets preset scenario mapping parameters (i.e., the first association relationship) and / or preset business control rule parameters (i.e., the second association relationship). The update data includes specific additions, deletions, or modifications, such as event identifiers, dimension identifiers, scenario codes, business control rule identifiers, or association relationship field values ​​to be modified.

[0147] Step 704: Based on the parameter type identifier and update data, update the preset scene mapping parameters and / or preset business control rule parameters to obtain the updated preset scene mapping parameters and / or preset business control rule parameters.

[0148] In this embodiment, the server updates the preset scenario mapping parameters and / or preset business control rule parameters based on the parameter type identifier and update data to obtain the updated preset scenario mapping parameters and / or preset business control rule parameters. If the parameter type identifier indicates updating the preset scenario mapping parameters, the server adds, deletes, or modifies the first association record between candidate events, candidate dimensions, and scenario codes in the scenario definition table; if the parameter type identifier indicates updating the preset business control rule parameters, the server adds, deletes, or modifies the second association record between scenario codes and business control rule identifiers in the corresponding business control rule table (limit prototype parameter table, scenario rate comparison table, status event comparison table, etc.).

[0149] In this embodiment, the update process of preset scenario mapping parameters and / or preset business control rule parameters directly modifies the parameter data stored in the parameter platform at runtime, without restarting the core system or recompiling the code. The updated parameters take effect immediately, and subsequent business requests will automatically use the latest parameters for multi-level matching, which improves the timeliness of parameter updates and realizes the real-time construction of target business processing strategies that match the current business request, thereby improving the flexibility and efficiency of business processing.

[0150] In an exemplary embodiment, the method further includes steps 1061 to 1062. Wherein:

[0151] Step 1061: Store the target business processing strategy and the relationship between the business request and the target business processing strategy in the business processing strategy table.

[0152] In this embodiment, the server stores the dynamically constructed target business processing strategy and the association between the target business processing strategy and the current business request in a preset business processing strategy table. This business processing strategy table records historical business processing strategies that have been matched and constructed. The server can store the corresponding target business processing strategy based on the hash value of the business request, the combination key of the event identifier and dimension identifier, or the scenario code as an index. Therefore, when the same business request arrives again, the server does not need to repeat the first-level matching and second-level matching; it can directly read the constructed target business processing strategy from the business processing strategy table, thereby improving the processing efficiency of repetitive business requests.

[0153] Step 1062: In response to the re-triggering of the business request, determine the target business processing strategy for the business request based on the business processing strategy table, and perform business processing on the business request based on the target business processing strategy.

[0154] In this embodiment, when the server receives a business request with the same attribute information as a historical request, in response to the re-triggering of the business request, it first queries the business processing strategy table. Based on the event information and dimension information of the request or a preset index key, it searches the business processing strategy table to see if a corresponding target business processing strategy exists. If the cache is hit, the target business processing strategy is directly obtained and applied to the business processing of the current request without re-executing the scenario matching and rule matching process; if the cache is not hit, it falls back to steps 104 and 106 for dynamic matching and construction.

[0155] In this embodiment, by introducing a policy caching mechanism, while maintaining the flexibility of parameterized matching, the matching calculation overhead is reduced for high-frequency and repetitive business requests, thereby improving the efficiency of business processing for repetitive business requests.

[0156] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0157] Based on the same inventive concept, this application also provides a business processing apparatus for implementing the business processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more business processing apparatus embodiments provided below can be found in the limitations of the business processing method described above, and will not be repeated here.

[0158] In one exemplary embodiment, such as Figure 8 As shown, a business processing device 800 is provided, including: a first acquisition module 801, a matching module 802, and a construction module 803, wherein:

[0159] The first acquisition module 801 is used to acquire preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request in response to the triggering of a business request.

[0160] The matching module 802 is used to perform multi-level matching of the request attribute information based on the preset scenario mapping parameters according to the preset hierarchical matching rules, and to perform hierarchical matching based on the first-level matching result and the preset business control rule parameters to obtain the target business control rule;

[0161] Module 803 is used to construct the target business processing strategy corresponding to the business request based on the target business control rules; the target business processing strategy is used to process the business request.

[0162] In one embodiment, the requested attribute information includes an event identifier and a dimension identifier;

[0163] The matching module 802 is specifically used to perform first-level matching in the preset scene mapping parameters according to the event identifier and dimension identifier and the first association relationship to obtain the scene code;

[0164] Based on the scenario code, a second-level match is performed in the preset business control rule parameters according to the second association relationship to obtain the target business control rule.

[0165] In one embodiment, the device 800 further includes:

[0166] The second acquisition module is used to acquire event configuration data and dimension configuration data; the event configuration data includes event identifiers, and the dimension configuration data includes dimension identifiers.

[0167] The first storage module is used to construct scene combinations based on event identifiers and dimension identifiers, and store the correspondence between event identifiers, dimension identifiers and scene codes corresponding to scene combinations in the scene definition table to obtain the first association relationship;

[0168] The second storage module is used to receive the business control rule configuration data corresponding to the scenario code, store the correspondence between the scenario code and the business control rule configuration data in the business control rule table, and obtain the second association relationship.

[0169] In one embodiment, the matching module 802 is specifically used to determine the candidate scene code corresponding to the event identifier in the preset scene mapping parameters based on the event identifier and the first association relationship;

[0170] The target scene code is determined from the candidate scene codes based on dimension identifiers.

[0171] In one embodiment, the matching module 802 is specifically used to determine the set of candidate business control rules corresponding to the scene code in the preset business control rule parameters based on the scene code and the second association relationship.

[0172] Based on preset rule filtering conditions, the target business control rule is determined from the set of candidate business control rules.

[0173] In one embodiment, the device 800 further includes:

[0174] The receiving module is used to receive rule update requests, which include parameter type identifiers and update data.

[0175] The update module is used to update the preset scenario mapping parameters and / or preset business control rule parameters according to the parameter type identifier and update data, so as to obtain the updated preset scenario mapping parameters and / or preset business control rule parameters.

[0176] In one embodiment, the device 800 further includes:

[0177] The third storage module is used to store the target business processing strategy and the relationship between the business request and the target business processing strategy in the business processing strategy table;

[0178] The response module is used to respond to the re-triggering of business requests. It determines the target business processing strategy for the business request based on the business processing strategy table, and performs business processing on the business request based on the target business processing strategy.

[0179] Each module in the aforementioned business processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0180] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 9As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a business processing method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0181] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0182] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0183] In response to a business request, obtain preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request;

[0184] Based on the preset hierarchical matching rules, the preset scenario mapping parameters are used to perform multi-level matching on the request attribute information, and hierarchical matching is performed based on the first-level matching result and the preset business control rule parameters to obtain the target business control rule;

[0185] The target business processing strategy is constructed based on the target business control rules; the target business processing strategy is used to process the business request.

[0186] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0187] Based on the event identifier and dimension identifier, a first-level match is performed in the preset scene mapping parameters according to the first association relationship to obtain the scene code;

[0188] Based on the scenario code, a second-level match is performed in the preset business control rule parameters according to the second association relationship to obtain the target business control rule.

[0189] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0190] Retrieve event configuration data and dimension configuration data; event configuration data includes event identifiers, and dimension configuration data includes dimension identifiers.

[0191] Scenario combinations are constructed based on event identifiers and dimension identifiers, and the correspondence between event identifiers, dimension identifiers and the corresponding scenario codes of the scenario combinations is stored in the scenario definition table to obtain the first association relationship;

[0192] Receive the business control rule configuration data corresponding to the scenario code, store the correspondence between the scenario code and the business control rule configuration data in the business control rule table, and obtain the second association relationship.

[0193] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0194] Based on the event identifier and the first association relationship, determine the candidate scene code corresponding to the event identifier from the preset scene mapping parameters;

[0195] The target scene code is determined from the candidate scene codes based on dimension identifiers.

[0196] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0197] Based on the scenario code and the second association relationship, determine the set of candidate business control rules corresponding to the scenario code from the preset business control rule parameters;

[0198] Based on preset rule filtering conditions, the target business control rule is determined from the set of candidate business control rules.

[0199] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0200] Receive rule update requests, which include parameter type identifiers and update data;

[0201] Based on the parameter type identifier and update data, update the preset scenario mapping parameters and / or preset business control rule parameters to obtain the updated preset scenario mapping parameters and / or preset business control rule parameters.

[0202] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0203] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0204] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0205] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0206] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0207] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A business processing method, characterized in that, The method includes: In response to the triggering of a business request, obtain preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request; Based on the preset hierarchical matching rules, the preset scenario mapping parameters are used to perform multi-level matching on the request attribute information, and hierarchical matching is performed according to the first-level matching result and the preset business control rule parameters to obtain the target business control rule; Based on the target business control rules, a target business processing strategy corresponding to the business request is constructed; the target business processing strategy is used to process the business request.

2. The method according to claim 1, characterized in that, The request attribute information includes an event identifier and a dimension identifier; The method involves performing multi-level matching of the request attribute information using the preset scenario mapping parameters based on preset hierarchical matching rules, and performing hierarchical matching based on the first-level matching result and the preset business control rule parameters to obtain the target business control rule, including: Based on the event identifier and the dimension identifier, a first-level match is performed in the preset scene mapping parameters according to the first association relationship to obtain the scene code; Based on the scenario code, a second-level matching is performed on the preset business control rule parameters according to the second association relationship to obtain the target business control rule.

3. The method according to claim 2, characterized in that, The method further includes: Obtain event configuration data and dimension configuration data; the event configuration data includes event identifiers, and the dimension configuration data includes dimension identifiers. A scene combination is constructed based on the event identifier and the dimension identifier, and the correspondence between the event identifier, the dimension identifier and the scene code corresponding to the scene combination is stored in the scene definition table to obtain the first association relationship; Receive the business control rule configuration data corresponding to the scenario code, store the correspondence between the scenario code and the business control rule configuration data in the business control rule table, and obtain the second association relationship.

4. The method according to claim 2, characterized in that, The step of performing a first-level match in the preset scene mapping parameters according to the event identifier and the dimension identifier, based on a first association relationship, to obtain the scene code includes: Based on the event identifier and the first association relationship, determine the candidate scene code corresponding to the event identifier in the preset scene mapping parameters; The target scene code is determined from the candidate scene codes based on the dimensional identifier.

5. The method according to claim 2, characterized in that, Based on the scenario code, the second-level matching is performed on the preset business control rule parameters according to the second association relationship to obtain the target business control rule, including: Based on the scenario code and the second association relationship, a set of candidate business control rules corresponding to the scenario code is determined from the preset business control rule parameters; Based on preset rule filtering conditions, the target business control rule is determined from the set of candidate business control rules.

6. The method according to claim 1, characterized in that, The method further includes: Receive a rule update request, the rule update request including parameter type identifier and update data; Based on the parameter type identifier and the update data, update the preset scene mapping parameters and / or the preset business control rule parameters to obtain the updated preset scene mapping parameters and / or preset business control rule parameters.

7. The method according to claim 1, characterized in that, After constructing the target business processing strategy corresponding to the business request based on the target business control rules, the method further includes: Store the target business processing strategy and the association between the business request and the target business processing strategy in the business processing strategy table; In response to the re-triggering of the service request, the target service processing strategy for the service request is determined based on the service processing strategy table, and the service request is processed based on the target service processing strategy.

8. A business processing device, characterized in that, The device includes: The first acquisition module is used to acquire preset scenario mapping parameters, preset business control rule parameters, and request attribute information of the business request in response to the triggering of a business request. The matching module is used to perform multi-level matching of the request attribute information with the preset scenario mapping parameters based on preset hierarchical matching rules, and to perform hierarchical matching based on the first-level matching result and the preset business control rule parameters to obtain the target business control rule; A construction module is used to construct a target business processing strategy corresponding to the business request based on the target business control rules; the target business processing strategy is used to process the business request.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images