A service request execution method, device, electronic device and storage medium

Abstract

The present invention discloses a method, device, electronic device and storage medium for executing a business request, the method comprising: obtaining the type of the corresponding inventory management scenario according to the type of the business request; obtaining the inventory management operation sequence according to the type of the inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action; executing the inventory management action sequence to obtain the business data corresponding to the business request. Through the two-layer mapping relationship between the business scenario and the inventory management scenario, and the inventory management scenario and the inventory management action sequence, the inventory management action sequence to be executed can be determined according to the type of the business request, and the business data corresponding to the business request can be obtained, and when a new request needs to be added, it is only necessary to reorganize the corresponding inventory management scenario or inventory management action without modifying a large amount of code, thereby improving the execution efficiency of the business request and the user experience effect.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of communication technology, and in particular to a service request execution method, device, electronic device and storage medium. Background Art

[0002] In the physical gold system inventory management in the financial field, the existing configuration method is to correspond to a specified code for each business scenario, and when a user's business request is received, the specified code is executed for the business request.

[0003] Based on the existing inventory management configuration method, when executing business requests, although the corresponding business data can be obtained, the business requests usually directly correspond to fixed complex codes. Therefore, once a new business request is added, a large amount of code needs to be modified again. The system reusability is poor, and the execution efficiency of business requests is reduced due to system upgrades, which affects the user experience. Summary of the invention

[0004] The embodiments of the present invention provide a service request execution method, apparatus, device and storage medium to obtain corresponding service data according to the service request.

[0005] In a first aspect, an embodiment of the present invention discloses a service request execution method, comprising:

[0006] Obtaining the type of the corresponding inventory management scenario according to the type of the business request, wherein the inventory management scenario supports the execution of the business request;

[0007] Acquire an inventory management operation sequence according to the type of the inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action;

[0008] Execute the inventory management action sequence to obtain the business data corresponding to the business request.

[0009] In a second aspect, an embodiment of the present invention provides a service request execution device, including:

[0010] An inventory management scenario type acquisition module is used to acquire the type of the corresponding inventory management scenario according to the type of the business request, wherein the inventory management scenario supports the execution of the business request;

[0011] An inventory management operation sequence acquisition module, used to acquire an inventory management operation sequence according to the type of inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action;

[0012] The business data acquisition module is used to execute the inventory management action sequence to obtain the business data corresponding to the business request.

[0013] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0014] one or more processors;

[0015] A storage device for storing one or more programs;

[0016] When one or more programs are executed by one or more processors, the one or more processors implement the method of any embodiment of the present invention.

[0017] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a method of any embodiment of the present invention.

[0018] In the embodiments of the present invention, through the two-layer mapping relationship between the business scenario and the inventory management scenario, and the inventory management scenario and the inventory management action sequence, it is possible to determine the inventory management action sequence that needs to be executed according to the type of business request, and obtain the business data corresponding to the business request, and when a new request needs to be added, it is only necessary to reorganize the corresponding inventory management scenario or inventory management action without modifying a large amount of code, thereby improving the execution efficiency of the business request and the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a flowchart of a method for executing a service request provided in Embodiment 1 of the present invention;

[0020] Figure 2 is a flow chart of a method for executing a business request provided in Embodiment 2 of the present invention;

[0021] Figure 3 is a schematic diagram of the structure of a service request execution device provided in Embodiment 3 of the present invention;

[0022] Figure 4 This is a structural block diagram of a device provided in Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0023] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0024] Embodiment 1

[0025] Figure 1This is a flowchart of a service request execution method provided in Embodiment 1 of the present invention. This embodiment is applicable to the case where corresponding service data is obtained according to a service request. The method can be executed by a service request execution device in the embodiment of the present invention, which can be implemented in software and / or hardware. The method in the embodiment of the present invention specifically includes the following steps:

[0026] Step 101: Obtain the type of the corresponding inventory management scenario according to the type of the business request.

[0027] Among them, the inventory management scenario supports the execution of business requests, and each inventory management scenario supports at least one type of business request, that is, the business request can only run normally in the corresponding inventory management scenario, otherwise an error will be reported.

[0028] Optionally, obtaining the type of corresponding inventory management scenario according to the type of business request may include: obtaining a first mapping table from a database, wherein the first mapping table contains a correspondence between business requests and inventory management scenarios, and each inventory management scenario corresponds to at least one business request; and querying the first mapping table according to the type of business request to obtain the type of inventory management scenario.

[0029] Optionally, the types of inventory management scenarios may include: inventory warning, physical sale, physical repurchase, pending withdrawal sale, and pending withdrawal non-designated repurchase.

[0030] The first mapping table is shown in Table 1 below:

[0031] Table 1

[0032]

[0033] Among them, the first mapping table shown in Table 1 is an explanation of different business requests in the physical precious metals scenario. It can be concluded from the table that each inventory management scenario corresponds to at least one business request, and the first mapping table also includes an identifier corresponding to each business request and an identifier corresponding to each inventory management scenario. Due to space limitations, only part of the content of the first mapping table is displayed in this implementation.

[0034] In a specific implementation, when it is determined that the type of the business request input by the user is the exchange of account funds for physical sales identified as 0903, a query is performed from the first mapping table shown in Table 1 according to the type of the business request, and the type of inventory management scenario obtained is the physical sale identified as A001.

[0035] Optionally, before obtaining the first mapping table from the database, the method further includes: obtaining a first configuration instruction; and configuring the first mapping table according to the first configuration instruction.

[0036] Specifically, in this embodiment, before obtaining the first mapping table from the database, the first mapping table needs to be configured according to the first configuration instruction input by the user. The configuration instruction may include the correspondence between each business request and the inventory management scenario, and the correspondence is added to the first mapping table to complete the configuration process.

[0037] Step 102: Obtain an inventory management operation sequence according to the type of inventory management scenario.

[0038] The inventory management action sequence includes at least one inventory management action.

[0039] Optionally, obtaining an inventory management action sequence according to the type of inventory management scenario may include: obtaining a second mapping table from a database, wherein the second mapping table contains a correspondence between inventory management scenarios and inventory management operation sequences; and querying the second mapping table according to the type of inventory management scenario to obtain the inventory management action sequence.

[0040] The second mapping table is shown in Table 2 below:

[0041] Table 2

[0042]

[0043] Among them, as shown in Table 2, each inventory management scenario in the second mapping table corresponds to an inventory management action sequence, and each inventory management action sequence includes at least one inventory management action. Each inventory management action in the inventory management action sequence is executed sequentially, and the second mapping table also includes an identifier corresponding to each inventory management scenario and an identifier of each inventory management action.

[0044] Specifically, in this embodiment, a two-layer mapping relationship is established to determine the inventory management action that needs to be executed corresponding to the business request, and when adding or deleting a business request, only the existing mapping relationship needs to be adjusted without modifying the original system code, so it is easier to expand functions.

[0045] Optionally, before obtaining the second mapping table from the database, the method may further include: obtaining a second configuration instruction; and configuring the second mapping table according to the second configuration instruction.

[0046] Specifically, in this embodiment, before obtaining the second mapping table from the database, the second mapping table needs to be configured according to the user's second configuration instruction, specifically, selecting a specified type of inventory management action from the inventory management action set for a specified inventory management scenario, and combining them in a specified order to obtain an inventory management action sequence.

[0047] It should be noted that the inventory management actions included in the above inventory management action set can specifically be: account funds exchanged for physical sales, accumulated funds exchanged for physical sales, easily deposited funds exchanged for physical sales, account funds exchanged for pending withdrawal sales, accumulated funds exchanged for pending withdrawal sales, easily deposited funds exchanged for pending withdrawal sales, judicial liquidation, pending withdrawal repurchase, mortgage liquidation, judicial liquidation under frozen state, and mortgage liquidation under frozen state. Of course, this embodiment is only an example for illustration, and does not limit the inventory management actions included in the inventory management action set. And the user can select the specified inventory management actions from them as needed and combine them in order to obtain the inventory management operation sequence corresponding to the specified type of inventory management scenario.

[0048] Optionally, querying from the second mapping table according to the type of inventory management scenario to determine the inventory management action sequence may include: querying from the second mapping table according to the type of inventory management scenario; determining whether a inventory management action sequence corresponding to the type of inventory management scenario is found in the second mapping table, and if so, directly determining the inventory management action sequence; otherwise, receiving an update instruction from the user for the second mapping table, and updating the second mapping table according to the update instruction, and determining the inventory management action sequence according to the updated second mapping table.

[0049] It should be noted that when querying from the second mapping table according to the type of inventory management scenario, if the inventory management action sequence corresponding to the specified type of inventory management scenario is directly queried in the second mapping table, it means that the specified type of inventory management action has been configured in the previous second mapping table configuration process; if it is not queried, it means that the specified type of inventory management scenario has not been configured before, but the update instruction of the user can be received, and the update instruction includes the inventory management action selected from the inventory management action set and the identifier of each inventory management action, and the second mapping table is updated according to the update instruction, and the inventory management action sequence is re-determined according to the updated second mapping table. In this way, the expansion of the inventory management function can be achieved according to actual needs without changing the original mapping relationship.

[0050] Step 103: execute the inventory management action sequence to obtain the business data corresponding to the business request.

[0051] Optionally, executing an inventory management action sequence to obtain business data corresponding to a business request may include: obtaining an identifier of an inventory management action included in the inventory management action sequence; obtaining parameters of the inventory management action from an inventory management action component library based on the identifier of the inventory management action; and executing the inventory management action based on the parameters to obtain business data corresponding to the business request.

[0052] Optional parameters include: component identifier, component name, component call class, component entry method, component message information and component reversal flag.

[0053] For example, when it is determined that the type of business request is the exchange of account funds for physical sales identified as 0903, the corresponding inventory management scenario is determined to be the physical sale identified as A001 according to the first mapping table, and then the corresponding inventory management action sequence can be further determined according to the second mapping table as: T006 quota processing + T001 physical inventory processing + T004 pending inventory query + T005 reserve ratio check, that is, executed in the order of the action combination shown. Since each inventory management action corresponds to the implementation of an independent component, the execution of the action is completed based on the implementation of the component. The component in this embodiment can specifically be the coding logic corresponding to the inventory management action. During the specific execution, the identifier T006 of the first inventory management action in the inventory management action sequence is sequentially obtained, and the parameters of the inventory management action-quota processing are obtained from the inventory management action construction library according to T006. The inventory management action component library contains the inventory management action parameters corresponding to each component. As shown in Table 3, the parameters of the inventory management action-quota processing are displayed in the form of an information table:

[0054] Field Number Field Name Field Type 1 Inventory management action ID: T006 CHAR(4) 2 Component ID: 001 CHAR(6) 3 Component name: Quota processing VARCHAR2(50) 4 Component calling class: Person VARCHAR2(50) 5 Component entry method: X1 VARCHAR2(20) 6 Component message information: aabbcc VARCHAR2(50) 7 Component correction mark: + CHAR(2)

[0055] In this embodiment, only the parameters of the quota processing are illustrated, and the specific values ​​of the parameters are not limited. The parameter forms of other types of inventory management actions are roughly the same as Table 1, so they are not repeated in this embodiment. And each inventory management action in the inventory management action sequence is executed in sequence according to each inventory management action parameter, so as to obtain the business data corresponding to the business request-account gold exchange for physical sale.

[0056] Optionally, executing an inventory management action according to the parameters to obtain business data corresponding to the business request, including: executing the inventory management action according to the parameters and obtaining an execution number; determining whether the inventory management action is executed successfully, and if so, executing the remaining inventory management actions in the inventory management action sequence in sequence until the business data corresponding to the business request is obtained, otherwise, reversing the inventory management actions that have been executed in the inventory management action sequence according to the execution number, and re-executing the inventory management operation sequence after the reversal is completed, until the business data corresponding to the business request is determined to be obtained.

[0057] In a specific implementation, the inventory management action sequence is: T006 quota processing + T001 physical inventory processing + T004 inventory query to be withdrawn + T005 reserve ratio check. When the reserve ratio check action is executed according to the parameters of the reserve ratio check, the execution number, that is, the transaction serial number, is obtained as 100000. When it is determined that the reserve ratio check action is executed successfully, the business data corresponding to the business request-account gold exchange for physical sales is directly obtained; when it is determined that the reserve ratio check action fails to execute, the inventory management actions that have been executed in the inventory management action sequence are reversed according to the transaction serial number, and specifically, it is determined whether the component reversal flag in the parameters of each inventory management action is "+". If so, the reversal is performed. For example, it is determined that only the component reversal flag in T006 quota processing and T001 physical inventory processing is "+" in the actions before T005 reserve ratio check, then the data values ​​before the quota processing and physical inventory processing actions are restored, that is, the original data of the quota processing and physical inventory processing before this transaction are restored.

[0058] In the embodiments of the present invention, through the two-layer mapping relationship between the business scenario and the inventory management scenario, and the inventory management scenario and the inventory management action sequence, it is possible to determine the inventory management action sequence that needs to be executed according to the type of business request, and obtain the business data corresponding to the business request, and when a new request needs to be added, it is only necessary to reorganize the corresponding inventory management scenario or inventory management action without modifying a large amount of code, thereby improving the execution efficiency of the business request and the user experience.

[0059] Embodiment 2

[0060] Figure 2 It is a flow chart of a business request execution method provided by the second implementation of the present invention. This embodiment is based on the above embodiment. After executing the inventory management action sequence to obtain the business data corresponding to the business request, it also includes: detecting the business data, and issuing an alarm prompt when it is determined that the business data is abnormal based on the detection results.

[0061] like Figure 2 As shown, the method of the embodiment of the present disclosure specifically includes:

[0062] Step 201, obtaining the type of corresponding inventory management scenario according to the type of business request.

[0063] Optionally, obtaining the type of corresponding inventory management scenario according to the type of business request may include: obtaining a first mapping table from a database, wherein the first mapping table contains a correspondence between business requests and inventory management scenarios, and each inventory management scenario corresponds to at least one business request; and querying the first mapping table according to the type of business request to obtain the type of inventory management scenario.

[0064] Optionally, the types of inventory management scenarios may include: inventory warning, physical sale, physical repurchase, pending withdrawal sale, and pending withdrawal non-designated repurchase.

[0065] Optionally, before obtaining the first mapping table from the database, the method further includes: obtaining a first configuration instruction; and configuring the first mapping table according to the first configuration instruction.

[0066] Step 202: Obtain an inventory management operation sequence according to the type of inventory management scenario.

[0067] The inventory management action sequence includes at least one inventory management action.

[0068] Optionally, obtaining an inventory management action sequence according to the type of inventory management scenario may include: obtaining a second mapping table from a database, wherein the second mapping table contains a correspondence between inventory management scenarios and inventory management operation sequences; and querying the second mapping table according to the type of inventory management scenario to obtain the inventory management action sequence.

[0069] Optionally, before obtaining the second mapping table from the database, the method may further include: obtaining a second configuration instruction; and configuring the second mapping table according to the second configuration instruction.

[0070] Step 203: execute the inventory management action sequence to obtain the business data corresponding to the business request.

[0071] Optionally, executing an inventory management action sequence to obtain business data corresponding to a business request may include: obtaining an identifier of an inventory management action included in the inventory management action sequence; obtaining parameters of the inventory management action from an inventory management action component library based on the identifier of the inventory management action; and executing the inventory management action based on the parameters to obtain business data corresponding to the business request.

[0072] Optional parameters include: component identifier, component name, component call class, component entry method, component message information and component reversal flag.

[0073] Step 204: detect the business data, and issue an alarm if the business data is abnormal according to the detection result.

[0074] Specifically, after obtaining the business data corresponding to the business request, the present embodiment needs to detect the business data, specifically whether there are obvious errors in the business data, for example, garbled characters, or the business data is obviously inconsistent with the business request. The reason for the above situation may be that there is a configuration error in the process of configuring the mapping relationship, or a problem with the device hardware itself. Therefore, when it is determined that the business data is abnormal, an alarm prompt can be issued to instruct the operation and maintenance personnel to perform inspection and maintenance in a timely manner, thereby further improving the processing efficiency of business requests.

[0075] Specifically, the alarm can be given in the form of voice broadcast or text display. The specific form of the alarm is not limited in this embodiment. As long as it can serve as a reminder to the operation and maintenance personnel, it is within the protection scope of this application and is not limited in this embodiment.

[0076] In the embodiment of the present invention, through the two-layer mapping relationship between the business scenario and the inventory management scenario, and the inventory management scenario and the inventory management action sequence, it is possible to determine the inventory management action sequence to be executed according to the type of business request, and obtain the business data corresponding to the business request, and when a new request needs to be added, it is only necessary to reorganize the corresponding inventory management scenario or inventory management action without modifying a large amount of code, thereby improving the execution efficiency of the business request and the user experience. In the case of determining that the business data is abnormal, the alarm prompt can be issued to instruct the operation and maintenance personnel to perform inspection and maintenance in time, thereby further improving the processing efficiency of the business request.

[0077] Embodiment 3

[0078] Figure 3 It is a business request execution device provided by the fourth embodiment of the present invention, which specifically includes: an inventory management scenario type acquisition module 301, an inventory management operation sequence acquisition module 302 and a business data acquisition module 303.

[0079] The inventory management scenario type acquisition module 301 is used to acquire the type of the corresponding inventory management scenario according to the type of the business request, wherein the inventory management scenario supports the execution of the business request;

[0080] An inventory management operation sequence acquisition module 302 is used to acquire an inventory management operation sequence according to the type of inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action;

[0081] The business data acquisition module 303 is used to execute the inventory management action sequence to acquire the business data corresponding to the business request.

[0082] Optionally, the inventory management scenario type acquisition module 301 is used to acquire a first mapping table from a database, wherein the first mapping table contains a correspondence between business requests and inventory management scenarios, and each inventory management scenario corresponds to at least one business request;

[0083] According to the type of the business request, a query is performed from the first mapping table to obtain the type of the inventory management scenario.

[0084] Optionally, the device further includes a first configuration module, configured to obtain a first configuration instruction;

[0085] The first mapping table is configured according to the first configuration instruction.

[0086] Optionally, the inventory management operation sequence acquisition module 302 includes:

[0087] A second mapping table acquisition submodule is used to acquire a second mapping table from a database, wherein the second mapping table contains a correspondence between inventory management scenarios and inventory management operation sequences;

[0088] The inventory management action sequence acquisition submodule is used to query from the second mapping table according to the type of inventory management scenario to obtain the inventory management action sequence.

[0089] Optionally, the device further includes a second configuration module, configured to obtain a second configuration instruction;

[0090] The second mapping table is configured according to the second configuration instruction.

[0091] Optionally, the business data acquisition module 303 includes:

[0092] The inventory management action identification acquisition submodule is used to acquire the identification of the inventory management action included in the inventory management action sequence;

[0093] The parameter acquisition submodule of the inventory management action is used to acquire the parameters of the inventory management action from the inventory management action component library according to the identifier of the inventory management action;

[0094] The business data acquisition submodule is used to execute inventory management actions according to parameters to obtain business data corresponding to the business request.

[0095] Optional parameters include: component identifier, component name, component call class, component entry method, component message information and component reversal flag.

[0096] Optionally, a business data acquisition submodule is used to execute the inventory management action according to the parameters and obtain the execution number;

[0097] Determine whether the inventory management action is executed successfully. If so, execute the remaining inventory management actions in the inventory management action sequence in sequence until the business data corresponding to the business request is obtained. Otherwise, reverse the inventory management actions that have been executed in the inventory management action sequence according to the execution number, and re-execute the inventory management operation sequence after the correction is completed until the business data corresponding to the business request is obtained.

[0098] Optionally, an inventory management action sequence acquisition submodule is used to query from the second mapping table according to the type of inventory management scenario;

[0099] Determine whether a stock management action sequence corresponding to the type of stock management scenario is found in the second mapping table. If so, directly determine the stock management action sequence.

[0100] Otherwise, an update instruction from the user for the second mapping table is received, the second mapping table is updated according to the update instruction, and the inventory management action sequence is determined according to the updated second mapping table.

[0101] Optionally, the device further includes a detection module, configured to detect the service data;

[0102] When business data is determined to be abnormal based on the detection results, an alarm will be issued.

[0103] Optional, the type of inventory management scenario, including: inventory warning, physical sale, physical repurchase, pending withdrawal sale, and pending withdrawal non-designated repurchase.

[0104] Optional inventory management actions include: exchanging account funds for physical sales, exchanging accumulated funds for physical sales, exchanging easy-to-deposit funds for physical sales, exchanging account funds for pending withdrawal sales, exchanging accumulated funds for pending withdrawal sales, exchanging easy-to-deposit funds for pending withdrawal sales, judicial liquidation, pending withdrawal repurchase, mortgage liquidation, judicial liquidation under frozen status, and mortgage liquidation under frozen status.

[0105] The above device can execute the service request execution method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. For technical details not described in detail in this embodiment, please refer to the method provided by any embodiment of the present invention.

[0106] Embodiment 4

[0107] Figure 4 It is a structural schematic diagram of an electronic device provided by an embodiment of the present invention. Figure 4 A block diagram of an exemplary electronic device 412 suitable for use in implementing embodiments of the present invention is shown. Figure 4 The electronic device 412 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0108] like Figure 4 As shown, the electronic device 412 appears in the form of a general-purpose computing device. The components of the electronic device 412 may include, but are not limited to: one or more processors 412, a memory 428, and a bus 418 connecting different system components (including the memory 428 and the processor 416).

[0109] Bus 418 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0110] The electronic device 412 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 412, including volatile and non-volatile media, removable and non-removable media.

[0111] The memory 428 is used to store instructions. The memory 428 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 430 and / or cache memory 432. The electronic device 412 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 434 may be used to read and write non-removable, non-volatile magnetic media ( Figure 4 not shown, usually called a "hard drive"). Although Figure 4 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 418 via one or more data medium interfaces. The memory 428 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0112] A program / utility 440 having a set (at least one) of program modules 442 may be stored, for example, in memory 428, such program modules 442 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 442 generally perform the functions and / or methods of the embodiments described herein.

[0113] The electronic device 412 may also communicate with one or more external devices 414 (e.g., keyboards, pointing devices, displays 424, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 412, and / or may communicate with any device that enables the electronic device 412 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface 422. Furthermore, the electronic device 412 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 420. As shown, the network adapter 420 communicates with other modules of the electronic device 412 via a bus 418. It should be understood that although Figure 4 Not shown, other hardware and / or software modules may be used in conjunction with electronic device 412, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0114] The processor 416 executes instructions stored in the memory 428 to perform various functional applications and data processing, such as performing the following operations:

[0115] The type of the corresponding inventory management scenario is obtained according to the type of the business request, wherein the inventory management scenario supports the execution of the business request; the inventory management operation sequence is obtained according to the type of the inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action; and the inventory management action sequence is executed to obtain the business data corresponding to the business request.

[0116] Embodiment 5

[0117] Embodiment 5 of the present invention further provides a storage medium including computer executable instructions, and when the computer executable instructions are executed by a computer processor, the method for executing a service request includes:

[0118] The type of the corresponding inventory management scenario is obtained according to the type of the business request, wherein the inventory management scenario supports the execution of the business request; the inventory management operation sequence is obtained according to the type of the inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action; and the inventory management action sequence is executed to obtain the business data corresponding to the business request.

[0119] Of course, the computer executable instructions of a storage medium including computer executable instructions provided by an embodiment of the present invention are not limited to the operations of the method described above, and can also execute related operations in the service request execution method provided by any embodiment of the present invention.

[0120] Through the above description of the implementation method, the technicians in the relevant field can clearly understand that the present invention can be implemented by means of software and necessary general hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for an electronic device (which can be a personal computer, a server, or a network device, etc.) to execute the service request execution method described in each embodiment of the present invention.

[0121] It is worth noting that the various units and modules included in the above embodiments are only divided according to functional logic, but are not limited to the above divisions, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0122] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for executing a business request, characterized in that: include: Acquire a type of a corresponding inventory management scenario according to the type of the business request, wherein the inventory management scenario supports execution of the business request; Acquire an inventory management action sequence according to the type of the inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action; wherein the inventory management actions in the inventory management action sequence are executed sequentially; Execute the inventory management action sequence to obtain business data corresponding to the business request; Wherein, obtaining the type of the corresponding inventory management scenario according to the type of the business request includes: Obtaining a first mapping table from a database, wherein the first mapping table contains a correspondence between business requests and inventory management scenarios, and each inventory management scenario corresponds to at least one business request; Querying the first mapping table according to the type of the business request to obtain the type of the inventory management scenario; Wherein, acquiring the inventory management action sequence according to the type of the inventory management scenario includes: Obtaining a second mapping table from a database, wherein the second mapping table contains a correspondence between inventory management scenarios and inventory management action sequences; querying the second mapping table according to the type of the inventory management scenario to obtain the inventory management action sequence; The types of inventory management scenarios include: Inventory warning, physical sale, physical repurchase, pending withdrawal sale and pending withdrawal non-designated repurchase; The inventory management actions include: Exchange of account funds for physical sales, exchange of accumulated funds for physical sales, exchange of easy-to-deposit funds for physical sales, exchange of account funds for pending withdrawal sales, exchange of accumulated funds for pending withdrawal sales, exchange of easy-to-deposit funds for pending withdrawal sales, judicial liquidation, pending withdrawal repurchase, mortgage and pledge liquidation, judicial liquidation under frozen status, and mortgage and pledge liquidation under frozen status; The querying from the second mapping table according to the type of the inventory management scenario to obtain the inventory management action sequence includes: querying from the second mapping table according to the type of the inventory management scenario; determining whether an inventory management action sequence corresponding to the type of the inventory management scenario is found in the second mapping table; if so, directly determining the inventory management action sequence; otherwise, receiving an update instruction from the user for the second mapping table, updating the second mapping table according to the update instruction, and determining the inventory management action sequence according to the updated second mapping table; wherein the update instruction includes an inventory management action selected from the inventory management action set and an identifier of each inventory management action; Wherein, after executing the inventory management action sequence to obtain the business data corresponding to the business request, the method further includes: Detecting the business data; When it is determined according to the detection result that the business data is abnormal, an alarm prompt is issued; wherein, the alarm prompt is issued in a voice broadcast or text display.

2. The method according to claim 1, characterized in that Before obtaining the first mapping table from the database, the method further includes: Obtaining a first configuration instruction; The first mapping table is configured according to the first configuration instruction.

3. The method according to claim 1, characterized in that Before obtaining the second mapping table from the database, the method further includes: Obtain a second configuration instruction; The second mapping table is configured according to the second configuration instruction.

4. The method according to claim 1, characterized in that: The executing the inventory management action sequence to obtain the business data corresponding to the business request includes: Obtaining identifiers of inventory management actions included in the inventory management action sequence; Acquire parameters of the inventory management action from an inventory management action component library according to the identifier of the inventory management action; The inventory management action is executed according to the parameters to obtain business data corresponding to the business request.

5. The method according to claim 4, characterized in that the parameters include: Component identification, component name, component call class, component entry method, component message information and component correction flag.

6. The method according to claim 4, characterized in that The performing the inventory management action according to the parameter to obtain the business data corresponding to the business request includes: Execute the inventory management action according to the parameters and obtain an execution number; Determine whether the inventory management action is executed successfully. If so, execute the remaining inventory management actions in the inventory management action sequence in sequence until the business data corresponding to the business request is obtained. Otherwise, reverse the inventory management actions that have been executed in the inventory management action sequence according to the execution number, and re-execute the inventory management operation sequence after the reversal is completed until it is determined that the business data corresponding to the business request is obtained.

7. A service request execution device, characterized in that: The device comprises: An inventory management scenario type acquisition module, used to acquire the type of the corresponding inventory management scenario according to the type of the business request, wherein the inventory management scenario supports the execution of the business request; An inventory management action sequence acquisition module, used to acquire an inventory management action sequence according to the type of the inventory management scenario, wherein the inventory management action sequence includes at least one inventory management action; wherein the inventory management actions in the inventory management action sequence are executed sequentially; A business data acquisition module, used for executing the inventory management action sequence to acquire business data corresponding to the business request; The type acquisition module of the inventory management scenario includes: A first mapping table acquisition submodule is used to acquire a first mapping table from a database, wherein the first mapping table contains a correspondence between business requests and inventory management scenarios, and each inventory management scenario corresponds to at least one business request; An inventory management scenario type acquisition submodule, configured to query the first mapping table according to the type of the business request to obtain the type of the inventory management scenario; Wherein, the inventory management action sequence acquisition module includes: A second mapping table acquisition submodule, used to acquire a second mapping table from a database, wherein the second mapping table contains a correspondence between inventory management scenarios and inventory management action sequences; An inventory management action sequence acquisition submodule, configured to query the second mapping table according to the type of the inventory management scenario to obtain the inventory management action sequence; The types of inventory management scenarios include: Inventory warning, physical sale, physical repurchase, pending withdrawal sale and pending withdrawal non-designated repurchase; The inventory management actions include: Exchange of account funds for physical sales, exchange of accumulated funds for physical sales, exchange of easy-to-deposit funds for physical sales, exchange of account funds for pending withdrawal sales, exchange of accumulated funds for pending withdrawal sales, exchange of easy-to-deposit funds for pending withdrawal sales, judicial liquidation, pending withdrawal repurchase, mortgage and pledge liquidation, judicial liquidation under frozen status, and mortgage and pledge liquidation under frozen status; The inventory management action sequence acquisition submodule is used to: query from the second mapping table according to the type of the inventory management scenario; determine whether the inventory management action sequence corresponding to the type of the inventory management scenario is queried in the second mapping table, and if so, directly determine the inventory management action sequence; otherwise, receive an update instruction from a user for the second mapping table, and update the second mapping table according to the update instruction, and determine the inventory management action sequence according to the updated second mapping table; wherein the update instruction includes an inventory management action selected from the inventory management action set, and an identifier of each inventory management action; Wherein, the device further comprises: The detection module is used to detect the business data; if the business data is determined to be abnormal based on the detection result, an alarm prompt is issued; wherein the alarm prompt is issued in a voice broadcast or text display.

8. An electronic device, characterized in that: The electronic device comprises: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images