Financial service scene identification method, device, medium and system

Abstract

The invention provides a financial service scene identification method and device, a medium and a system. According to the method, the name of the target financial service scene is determined at least according to the service rule code and the dimension code in the financial service scene code set, the identification of multiple service scenes under the same service rule code is realized, and the service scene can be identified through different values of the service parameters under the service rule code. According to the method, a specific and applicable business scene is controlled in a permutation and combination manner, so that a manner of judging by writing a large number of codes can be replaced for identification, and respective control is performed according to different business dimensions, thereby solving the problems of complex program logic, high efficiency and the like caused by direct implementation through program coding in the prior art. And therefore, the identification flexibility of the financial scene business is relatively poor.

Description

Technical Field

[0001] The present application relates to the technical field of business scenario identification, and in particular, to a method, device, medium and system for identifying a financial business scenario. Background Art

[0002] There are many complex business scenarios in the financial business system. Different business rule controls may need to be executed for different business scenarios, or the same business rule control may need to be executed for certain business scenarios. In addition, the business scenarios may be dynamic and change frequently. Therefore, if the existing technology is directly implemented through program coding, it will lead to complex program logic, many code logic control branches, poor code readability, extremely high subsequent maintenance costs, inability to adapt to frequent changes in business needs, and the system is not flexible enough. Summary of the invention

[0003] The main purpose of this application is to provide a method, device, medium and system for identifying financial business scenarios, so as to at least solve the problem that the existing technology is directly implemented through program coding, which leads to complex program logic and thus poor flexibility in identifying financial scenario businesses.

[0004] In order to achieve the above objective, according to one aspect of the present application, a method for identifying a financial business scenario is provided, the method comprising:

[0005] Acquire a financial business scenario code set, wherein the financial business scenario code set includes a business rule code and a dimension code, wherein the dimension code represents the dimension in which the business rule code is located, and the business rule code represents a unique identifier of the business rule;

[0006] The target financial business scenario name is determined at least according to the business rule code and the dimension code in the financial business scenario code set.

[0007] Optionally, the financial business scenario code set further includes a target parameter pre-conversion value, and determining a target financial business scenario name at least according to the business rule code and the dimension code in the financial business scenario code set includes:

[0008] Determine the target parameter conversion rule code according to the business rule code and the dimension code;

[0009] Determine the target parameter post-conversion value according to the target parameter conversion rule code and the target parameter pre-conversion value;

[0010] Combining all the converted values ​​of the target parameters to obtain a business rule control code;

[0011] The target financial business scenario name is determined according to the business rule control code.

[0012] Optionally, determining the target parameter post-conversion value according to the target parameter conversion rule code and the target parameter pre-conversion value includes:

[0013] Acquire a conversion mapping relationship, where the conversion mapping relationship represents a mapping relationship between a parameter conversion rule code, a parameter value before conversion, and a parameter value after conversion;

[0014] The post-conversion value of the target parameter is determined according to the conversion mapping relationship, the target parameter conversion rule code and the pre-conversion value of the target parameter.

[0015] Optionally, determining the target financial business scenario name according to the business rule control code includes:

[0016] According to the business rule control code, determine the corresponding target business rule scenario code;

[0017] The target financial business scenario name is determined to be a financial business scenario name corresponding to the target business rule scenario code.

[0018] Optionally, after determining the name of the target financial business scenario, the method further includes:

[0019] Determine a first target business rule control code, where the first target business rule control code is the business rule control code with a wildcard, where the wildcard represents a symbol belonging to the same business scenario;

[0020] All of the first target business rule control codes are controlled in the same financial business scenario.

[0021] Optionally, after determining the name of the target financial business scenario, the method further includes:

[0022] Determine a second target business rule control code, where the second target business rule control code is the business rule control code with a weight symbol, where the weight symbol represents a symbol for priority execution;

[0023] The financial business scenario corresponding to the second target business rule control code is preferentially identified.

[0024] Optionally, after determining the name of the target financial business scenario, the method further includes:

[0025] Determine a third target business rule control code, wherein the third target business rule control code is the business rule control code having a weight symbol and a wildcard;

[0026] In the process of executing the business rule control code having the same wildcard as the third target business rule control code, the financial business scenario corresponding to the third target business rule control code is preferentially identified.

[0027] According to another aspect of the present application, a device for identifying a financial business scenario is provided, the device comprising:

[0028] An acquisition unit, used to acquire a financial business scenario code set, wherein the financial business scenario code set includes a business rule code and a dimension code, wherein the dimension code represents the dimension in which the business rule code is located, and the business rule code represents a unique identifier of the business rule;

[0029] The first processing unit is used to determine a target financial business scenario name according to at least the business rule code and the dimension code in the financial business scenario code set.

[0030] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the methods described.

[0031] According to another aspect of the present application, a system for identifying financial business scenarios is provided, the system comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include means for executing any one of the methods described.

[0032] By applying the technical solution of the present application, the name of the target financial business scenario is determined based on at least the business rule code and the dimension code in the financial business scenario code set, thereby realizing the identification of multiple business scenarios under the same business rule code. Under the business rule code, different values ​​of business parameters can be used to control a specific applicable business scenario in an arrangement and combination manner, thereby replacing the identification method of judging by writing a large amount of code, and performing separate control according to different business dimensions, thereby solving the problem that the prior art directly implements through program coding, which will lead to complex program logic and poor flexibility in identifying financial scenario business. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0034] Figure 1A schematic diagram of a process of identifying a financial business scenario provided according to an embodiment of the present application is shown;

[0035] Figure 2 A schematic diagram showing a flow chart of another method for identifying a financial business scenario provided according to an embodiment of the present application;

[0036] Figure 3 A structural block diagram of a financial business scenario identification device provided according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0037] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0038] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0039] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0040] As introduced in the background technology, there are many complex business scenarios in the financial business system. Different business rule controls may need to be executed for different business scenarios, or the same business rule control may need to be executed for certain business scenarios. Moreover, the business scenarios may be dynamic and change frequently. Therefore, if the existing technology is directly implemented through program coding, it will lead to complex program logic, many code logic control branches, poor code readability, and extremely high subsequent maintenance costs. It cannot adapt to frequent changes in business needs, and the system is not flexible enough. In order to solve the problem that the existing technology is directly implemented through program coding, which will lead to complex program logic and poor flexibility in identifying financial scenario business, the embodiments of the present application provide a method, device, medium and system for identifying financial business scenarios.

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

[0042] In this embodiment, a method for identifying financial business scenarios is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0043] Figure 1 It is a flowchart of a method for identifying a financial business scenario provided according to an embodiment of the present application.

[0044] like Figure 1 As shown, the method comprises the following steps:

[0045] Step S101, obtaining a financial business scenario code set, the financial business scenario code set including a business rule code and a dimension code, the dimension code represents the dimension in which the business rule code is located, and the business rule code represents a unique identifier of the business rule;

[0046] Step S102, determining the name of the target financial business scenario at least according to the business rule code and the dimension code in the financial business scenario code set.

[0047] In the above steps, the name of the target financial business scenario is determined based on at least the business rule code and dimension code in the financial business scenario code set, thereby realizing the identification of multiple business scenarios under the same business rule code. Under the business rule code, different values ​​of business parameters can be used to control a specific applicable business scenario in an arrangement and combination manner, thereby replacing the identification method of judging by writing a large amount of code, and performing separate control according to different business dimensions, thereby solving the problem that the prior art is directly implemented through program coding, which will lead to complex program logic and poor flexibility in identifying financial scenario business.

[0048] The financial business scenario code set also includes a target parameter pre-conversion value. Step S102, i.e., determining a target financial business scenario name at least according to the business rule code and the dimension code in the financial business scenario code set, includes:

[0049] According to the above business rule code and the above dimension code, determine the target parameter conversion rule code;

[0050] Specifically, according to the business rule code and the dimension code, a parameter conversion rule code corresponding to the business rule code and the dimension code can be found from the corresponding mapping relationship, and the parameter conversion rule code is used as the target parameter conversion rule code.

[0051] Determine the target parameter post-conversion value according to the target parameter conversion rule code and the target parameter pre-conversion value;

[0052] Specifically, a conversion mapping relationship is obtained, wherein the conversion mapping relationship represents a mapping relationship between a parameter conversion rule code, a parameter value before conversion, and a parameter value after conversion;

[0053] The post-conversion value of the target parameter is determined according to the conversion mapping relationship, the target parameter conversion rule code and the pre-conversion value of the target parameter.

[0054] By setting the conversion mapping relationship, it is convenient to find the parameter post-conversion value corresponding to the above-mentioned target parameter conversion rule code and the above-mentioned target parameter pre-conversion value from the mapping relationship, and use the parameter post-conversion value as the target parameter post-conversion value.

[0055] Combining all the converted values ​​of the above target parameters to obtain the business rule control code;

[0056] Specifically, the converted values ​​are string-concatenated in order according to the parameter sequence number of each business parameter in the business rule parameter configuration table;

[0057] For example: the parameter sequence number of the business parameter currency is 0;

[0058] The parameter sequence number of the business parameter category identification code is 1;

[0059] The parameter sequence number of the business parameter access flag is 2;

[0060] If the currency conversion value is 9; the category identification code conversion value is 8; the access flag conversion value is 7;

[0061] Then concatenate in the order of 0-1-2 to get 987 as the business rule control code.

[0062] The parameter sequence numbers are not necessarily consecutive numbers. During the processing, the parameters will be sorted in order according to their sequence numbers. When the converted values ​​of each parameter are spliced, they will be spliced ​​in this order.

[0063] According to the above business rule control coding, the name of the above target financial business scenario is determined.

[0064] Specifically, according to the above-mentioned business rule control code, the corresponding target business rule scenario code is determined; and the above-mentioned target financial business scenario name is determined to be the financial business scenario name corresponding to the above-mentioned target business rule scenario code.

[0065] By setting the corresponding mapping relationship, the target business rule scenario code corresponding to the business rule control code is found, and the target financial business scenario name is determined to be the financial business scenario name corresponding to the above target business rule scenario code. The process is also carried out through the mapping relationship, which will not be repeated here.

[0066] In one embodiment of the present application, after determining the name of the target financial business scenario, the method further includes:

[0067] Determine a first target business rule control code, where the first target business rule control code is the business rule control code with a wildcard, where the wildcard represents a symbol belonging to the same business scenario;

[0068] All of the above first target business rule control codes are controlled in the same financial business scenario.

[0069] Specifically, the wildcard character "*" can be used to indicate that the specific value of a business parameter is not important, and all values ​​are uniformly matched to a certain scenario.

[0070] For example, the current withdrawal scenario of the first currency needs to be identified by three parameters: currency, account type, and access flag. When the currency is the first currency, the account type is current, and the access flag is withdrawal, it can be identified as a current withdrawal scenario of the first currency. However, if you want to identify only the current withdrawal scenario on this basis, the converted value of the currency parameter in the business rule control code can be wildcarded with "*". In this scenario, the currency value is not concerned, and identification only needs to be based on the account type and access flag.

[0071] In one embodiment of the present application, after determining the name of the target financial business scenario, the method further includes:

[0072] Determine a second target business rule control code, wherein the second target business rule control code is the business rule control code with a weight symbol, and the weight symbol represents a symbol for priority execution;

[0073] Prioritize identifying the financial business scenario corresponding to the second target business rule control code.

[0074] Specifically, “#” indicates that in a certain scenario identification, the business rule control code after parameter conversion matches multiple business scenarios. In this case, the weight symbol “#” is used to identify which business scenario is hit first.

[0075] For example, if the business rule control code for the current withdrawal scenario of the first currency is "001" and the current withdrawal business scenario is "*01", then the current withdrawal of the first currency can also hit the current withdrawal scenario. At this time, you can add "#" after the business rule control code to let the program hit one of the scenarios first.

[0076] In one embodiment of the present application, after determining the name of the target financial business scenario, the method further includes:

[0077] Determine a third target business rule control code, wherein the third target business rule control code is the business rule control code having a weight symbol and a wildcard;

[0078] In the process of executing the business rule control code having the same wildcard as the third target business rule control code, the financial business scenario corresponding to the third target business rule control code is preferentially identified.

[0079] Specifically, as shown in Table 1, Table 2 and Table 3, the conversion from encoding to specific scene can be completed.

[0080] Table 1

[0081]

[0082]

[0083] Table 2

[0084]

[0085] Table 3

[0086]

[0087]

[0088]

[0089] In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the method for identifying financial business scenarios of the present application will be described in detail below in conjunction with specific embodiments.

[0090] This embodiment relates to a specific method for identifying financial business scenarios, such as Figure 2 As shown, the following steps are included:

[0091] Obtain a financial business scenario code set, the financial business scenario code set includes a business rule code and a dimension code, the dimension code represents the dimension in which the business rule code is located, and the business rule code represents a unique identifier of the business rule;

[0092] According to the above business rule code and the above dimension code, determine the target parameter conversion rule code;

[0093] Obtaining a conversion mapping relationship, wherein the conversion mapping relationship represents a mapping relationship between a parameter conversion rule code, a parameter pre-conversion value, and a parameter post-conversion value; determining the target parameter post-conversion value according to the conversion mapping relationship, the target parameter conversion rule code, and the target parameter pre-conversion value, wherein the financial business scenario code set also includes the target parameter pre-conversion value;

[0094] Combining all the converted values ​​of the above target parameters to obtain the business rule control code;

[0095] According to the above business rule control code, the corresponding target business rule scenario code is determined; and the above target financial business scenario name is determined to be the financial business scenario name corresponding to the above target business rule scenario code.

[0096] After determining the name of the above-mentioned target financial business scenario, determine the first target business rule control code, the above-mentioned first target business rule control code is the above-mentioned business rule control code with a wildcard, and the above-mentioned wildcard represents a symbol belonging to the same business scenario; all the above-mentioned first target business rule control codes are controlled in the same financial business scenario.

[0097] Determine a second target business rule control code, wherein the second target business rule control code is the business rule control code with a weight symbol, and the weight symbol represents a symbol for priority execution; and preferentially identify the financial business scenario corresponding to the second target business rule control code.

[0098] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0099] The embodiment of the present application also provides an identification device for a financial business scenario. It should be noted that the identification device for the financial business scenario of the embodiment of the present application can be used to execute the identification method for the financial business scenario provided by the embodiment of the present application. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0100] The following is an introduction to the identification device for financial business scenarios provided in an embodiment of the present application.

[0101] Figure 3 is a structural block diagram of a financial business scenario identification device provided according to an embodiment of the present application. Figure 3 As shown, the device comprises:

[0102] The acquisition unit 31 is used to acquire a financial business scenario code set, wherein the financial business scenario code set includes a business rule code and a dimension code, wherein the dimension code represents the dimension in which the business rule code is located, and the business rule code represents a unique identifier of the business rule;

[0103] The first processing unit 32 is used to determine the name of the target financial business scenario according to at least the business rule code and the dimension code in the financial business scenario code set.

[0104] In the above-mentioned device, the name of the target financial business scenario is determined based on at least the business rule code and dimension code in the financial business scenario code set, thereby realizing the identification of multiple business scenarios under the same business rule code. Different values ​​of business parameters can be used under the business rule code to control a specific applicable business scenario in an arrangement and combination manner, thereby replacing the identification method of judging by writing a large amount of code, and performing separate control according to different business dimensions, thereby solving the problem that the prior art is directly implemented through program coding, which will lead to complex program logic and poor flexibility in identifying financial scenario business.

[0105] In one embodiment of the present application, the financial business scenario code set further includes a target parameter pre-conversion value, the first processing unit includes a first determination module, a second determination module, a first processing module and a third determination module,

[0106] The first determination module is used to determine the target parameter conversion rule code according to the business rule code and the dimension code;

[0107] The second determination module is used to determine the target parameter post-conversion value according to the target parameter conversion rule code and the target parameter pre-conversion value;

[0108] The first processing module is used to combine all the converted values ​​of the above target parameters to obtain the business rule control code;

[0109] The third determination module is used to control the coding according to the above business rules and determine the name of the above target financial business scenario.

[0110] In one embodiment of the present application, the second determination module includes an acquisition submodule and a first determination submodule.

[0111] The acquisition submodule is used to acquire a conversion mapping relationship, wherein the conversion mapping relationship represents a mapping relationship between a parameter conversion rule encoding, a parameter value before conversion, and a parameter value after conversion;

[0112] The first determination submodule is used to determine the post-conversion value of the target parameter according to the conversion mapping relationship, the target parameter conversion rule code and the pre-conversion value of the target parameter.

[0113] In one embodiment of the present application, the third determination module includes a second determination submodule and a third determination submodule.

[0114] The second determination submodule is used to determine the corresponding target business rule scenario code according to the above business rule control code;

[0115] The third determination submodule is used to determine that the target financial business scenario name is a financial business scenario name corresponding to the target business rule scenario code.

[0116] In one embodiment of the present application, the apparatus further includes a second processing unit and a third processing unit, which, after determining the name of the target financial service scenario,

[0117] The second processing unit is used to determine a first target business rule control code, where the first target business rule control code is the business rule control code with a wildcard, where the wildcard represents a symbol belonging to the same business scenario;

[0118] The third processing unit is used to control all the above-mentioned first target business rule control codes in the same financial business scenario.

[0119] In one embodiment of the present application, the apparatus further includes a fourth processing unit and a fifth processing unit, which, after determining the name of the target financial service scenario,

[0120] The fourth processing unit is used to determine a second target business rule control code, wherein the second target business rule control code is the business rule control code with a weight symbol, and the weight symbol represents a symbol for priority execution;

[0121] The fifth processing unit is used to preferentially identify the financial business scenario corresponding to the second target business rule control code.

[0122] In one embodiment of the present application, the apparatus further includes a sixth processing unit and a seventh processing unit, which, after determining the name of the target financial service scenario,

[0123] The sixth processing unit is used to determine a third target business rule control code, where the third target business rule control code is the business rule control code with a weight symbol and a wildcard;

[0124] The seventh processing unit is used to preferentially identify the financial business scenario corresponding to the third target business rule control code during the execution of the business rule control code having the same wildcard as the third target business rule control code.

[0125] The above-mentioned identification device for financial business scenarios includes a processor and a memory, and the above-mentioned acquisition unit and the first processing unit are stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to implement corresponding functions. The above-mentioned modules are all located in the same processor; or, the above-mentioned modules are located in different processors in any combination.

[0126] The processor contains a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and the kernel parameters can be adjusted to solve the problem that the existing technology is directly implemented through program coding, which will lead to complex program logic and poor identification flexibility of financial scenario services.

[0127] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0128] An embodiment of the present invention provides a computer-readable storage medium, which includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method for identifying the financial business scenario.

[0129] An embodiment of the present invention provides a processor, which is used to run a program, wherein the program executes the above-mentioned financial business scenario identification method when running.

[0130] The embodiment of the present invention provides a device, the device includes a processor, a memory and a program stored in the memory and can be run on the processor, and the processor implements at least the following steps when executing the program: obtaining a financial business scenario code set, the financial business scenario code set includes a business rule code and a dimension code, the dimension code represents the dimension in which the business rule code is located, and the business rule code represents the unique identifier of the business rule; at least according to the business rule code and the dimension code in the financial business scenario code set, determining the target financial business scenario name. The device in this article can be a server, a PC, a PAD, a mobile phone, etc.

[0131] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes at least the following method steps: obtaining a financial business scenario code set, the financial business scenario code set including a business rule code and a dimension code, the dimension code representing the dimension in which the business rule code is located, and the business rule code representing the unique identifier of the business rule; determining the target financial business scenario name based on at least the business rule code and the dimension code in the financial business scenario code set.

[0132] The present application also provides a financial business scenario identification system, the system includes: one or more processors, memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include methods for executing any of the above methods. By determining the name of the target financial business scenario at least according to the business rule code and dimension code in the financial business scenario code set, the identification of multiple business scenarios under the same business rule code is achieved, and the specific applicable business scenario can be controlled by the different values ​​of the business parameters under the business rule code in the way of permutation and combination, thereby replacing the identification method of judging by writing a large amount of code, and controlling separately according to different business dimensions, thereby solving the problem that the prior art is directly implemented through program coding, which will lead to complex program logic, thereby making the identification flexibility of financial scenario business poor.

[0133] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0134] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0135] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0136] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0137] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0138] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0139] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0140] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0141] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0142] From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

[0143] 1) The financial business scenario identification method of the present application determines the name of the target financial business scenario based on at least the business rule code and dimension code in the financial business scenario code set, thereby realizing the identification of multiple business scenarios under the same business rule code. Different values ​​of business parameters can be used under the business rule code to control a specific applicable business scenario in an arrangement and combination manner, thereby replacing the identification method of judging by writing a large amount of code, and performing separate control according to different business dimensions, thereby solving the problem that the prior art is directly implemented through program coding, which will lead to complex program logic and poor flexibility in identifying financial scenario business.

[0144] 2) The financial business scenario identification device of the present application determines the name of the target financial business scenario based on at least the business rule code and dimension code in the financial business scenario code set, thereby realizing the identification of multiple business scenarios under the same business rule code. Under the business rule code, different values ​​of business parameters can be used to control a specific applicable business scenario in an arrangement and combination manner, thereby replacing the identification method of judging by writing a large amount of code, and performing separate control according to different business dimensions, thereby solving the problem that the prior art is directly implemented through program coding, which will lead to complex program logic and poor flexibility in identifying financial scenario business.

[0145] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for identifying financial business scenarios, characterized in that: include: Acquire a financial business scenario code set, wherein the financial business scenario code set includes a business rule code and a dimension code, wherein the dimension code represents the dimension in which the business rule code is located, and the business rule code represents a unique identifier of the business rule; The target financial business scenario name is determined at least according to the business rule code and the dimension code in the financial business scenario code set.

2. The method according to claim 1, characterized in that The financial business scenario code set also includes a target parameter pre-conversion value, and determining a target financial business scenario name based at least on the business rule code and the dimension code in the financial business scenario code set includes: Determine the target parameter conversion rule code according to the business rule code and the dimension code; Determine the target parameter post-conversion value according to the target parameter conversion rule code and the target parameter pre-conversion value; Combining all the converted values ​​of the target parameters to obtain a business rule control code; The target financial business scenario name is determined according to the business rule control code.

3. The method according to claim 2, characterized in that Determining a target parameter post-conversion value according to the target parameter conversion rule code and the target parameter pre-conversion value includes: Acquire a conversion mapping relationship, where the conversion mapping relationship represents a mapping relationship between a parameter conversion rule code, a parameter value before conversion, and a parameter value after conversion; The post-conversion value of the target parameter is determined according to the conversion mapping relationship, the target parameter conversion rule code and the pre-conversion value of the target parameter.

4. The method according to claim 2, characterized in that: Determining the target financial business scenario name according to the business rule control code includes: According to the business rule control code, determine the corresponding target business rule scenario code; The target financial business scenario name is determined to be a financial business scenario name corresponding to the target business rule scenario code.

5. The method according to claim 2, characterized in that: After determining the name of the target financial business scenario, the method further includes: Determine a first target business rule control code, where the first target business rule control code is the business rule control code with a wildcard, where the wildcard represents a symbol belonging to the same business scenario; All of the first target business rule control codes are controlled in the same financial business scenario.

6. The method according to claim 2, characterized in that After determining the name of the target financial business scenario, the method further includes: Determine a second target business rule control code, where the second target business rule control code is the business rule control code with a weight symbol, where the weight symbol represents a symbol for priority execution; The financial business scenario corresponding to the second target business rule control code is preferentially identified.

7. The method according to claim 2, characterized in that After determining the name of the target financial business scenario, the method further includes: Determine a third target business rule control code, wherein the third target business rule control code is the business rule control code having a weight symbol and a wildcard; In the process of executing the business rule control code having the same wildcard as the third target business rule control code, the financial business scenario corresponding to the third target business rule control code is preferentially identified.

8. A device for identifying financial business scenarios, characterized in that: include: An acquisition unit, used to acquire a financial business scenario code set, wherein the financial business scenario code set includes a business rule code and a dimension code, wherein the dimension code represents the dimension in which the business rule code is located, and the business rule code represents a unique identifier of the business rule; The first processing unit is used to determine a target financial business scenario name according to at least the business rule code and the dimension code in the financial business scenario code set.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

10. A financial business scene recognition system, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of claims 1 to 7.

Images