Transfer mode expansion method and device, equipment and storage medium

Abstract

The invention discloses a transfer mode expansion method and device, equipment and a storage medium, relates to the technical field of financial science and technology, is applied to a back end, and comprises the steps that a front-end service address is received, the front-end service address is a corresponding page component developed by a front end according to a business demand of a target transfer mode, and the page component is a page component; after the page component is packaged into a static file through a general module definition specification, the static file is deployed; a verification interface and an execution interface are developed according to the business requirements of the target allocation mode, and a target allocation service is constructed based on the verification interface and the execution interface; deploying the target allocation service in a server, and allocating the target allocation service to obtain a rear-end service address; and configuring the target allocation mode in a preset plugging configuration table, and adding the front-end service address and the rear-end service address to the plugging configuration table, so that the allocation mode expansion efficiency can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of financial technology, and particularly relates to a transfer mode expansion method and device, equipment and a storage medium. BACKGROUND

[0002] Under the background of globalization, different country and region subsidiaries of a multinational enterprise group hold local currencies, leading to fragmentation of funds within the group, increased cost and difficulty of fund management, and emergence of transfer agreements, and the transfer mode is an implementation way of the transfer agreement.

[0003] However, the prior art needs to modify the old transfer mode related code when expanding a new transfer mode, which affects the old transfer mode that is already in effect and running, and the efficiency is low.

[0004] The above content is only used to assist in understanding the technical solutions of the present application and does not represent the acknowledgement of the above content as prior art. SUMMARY

[0005] The main purpose of the present application is to provide a transfer mode expansion method, device, equipment and storage medium, which aims to solve the technical problem that the prior art needs to modify the old transfer mode related code when expanding a new transfer mode, which affects the old transfer mode that is already in effect and running, and the efficiency is low.

[0006] To achieve the above purpose, the present application provides a transfer mode expansion method applied to a back end, which comprises the following steps:

[0007] Receiving a front-end service address, which is obtained after a front end develops a corresponding page component according to the business requirements of a target transfer mode, packs the page component into a static file through a general module definition specification, and deploys the static file;

[0008] Developing a verification interface and an execution interface according to the business requirements of the target transfer mode, and constructing a target transfer service based on the verification interface and the execution interface;

[0009] Deploying the target transfer service in a server, and assigning a back-end service address to the target transfer service;

[0010] Configuring the target transfer mode in a preset plug-in configuration table, and adding the front-end service address and the back-end service address to the plug-in configuration table, so as to realize expansion of the target transfer mode.

[0011] In an embodiment, the step of configuring the target transfer mode in a preset plug-in configuration table, and maintaining the front-end service address and the back-end service address in the plug-in configuration table comprises:

[0012] receiving a transfer mode selected by the target client;

[0013] configuring a transfer agreement based on the transfer mode selected by the target client;

[0014] running the transfer agreement in response to a transfer task triggering instruction.

[0015] In an embodiment, the step of configuring a transfer agreement based on the transfer mode selected by the target client comprises:

[0016] receiving an interface element returned by the target client at the front end;

[0017] calling a verification interface corresponding to the transfer mode selected by the target client, and verifying the integrity of the interface element through the verification interface;

[0018] if the integrity verification fails, a pop-up window is prompted to the target user;

[0019] if the integrity verification passes, corresponding business processing is performed through the execution interface;

[0020] generating a transfer agreement based on the transfer mode selected by the target client and the information of the business processing;

[0021] storing the transfer agreement to a database.

[0022] In an embodiment, the step of running the transfer agreement in response to a transfer task triggering instruction comprises:

[0023] obtaining a transfer mode type in response to the transfer task triggering instruction;

[0024] calling a corresponding execution interface based on the transfer mode type to obtain preset specific element information and corresponding account balance situation;

[0025] judging whether a preset first condition is met based on the specific element information and the corresponding account balance situation;

[0026] if not, recording a transfer task failure state and a transfer task failure reason;

[0027] if yes, generating a transfer amount based on the specific element information and the corresponding account balance situation;

[0028] generating a transfer transaction based on the transfer amount and a preset transfer element.

[0029] The application further proposes a transfer mode expansion method, characterized by being applied to a front end, and comprising the following steps:

[0030] According to the business requirement of the target allocation mode, a corresponding page component is developed, and the page component is packaged into a static file through a general module definition specification;

[0031] The static file is deployed through the front end to obtain a front-end service address;

[0032] The front-end service address is sent to the back end, so that the back end develops a verification interface and an execution interface according to the business requirement of the target allocation mode, constructs a target allocation service based on the verification interface and the execution interface, deploys the target allocation service in a server, allocates a back-end service address for the target allocation service, and after a preset plug-in configuration table is configured with the target allocation mode, the front-end service address and the back-end service address are added to the plug-in configuration table, so that the target allocation mode is expanded.

[0033] In an embodiment, after the front-end service address and the back-end service address are maintained in the plug-in configuration table, the following is included:

[0034] The plug-in configuration table is queried to obtain a list of allocation modes available to a target customer, and the list of allocation modes is returned to the target customer, so that the target customer selects an allocation mode.

[0035] In an embodiment, the query of the plug-in configuration table to obtain a list of allocation modes available to a target customer includes:

[0036] A plug-in configuration table query request is sent to the back end, so that the back end queries the plug-in configuration table based on the plug-in configuration table query request to obtain a query result, and returns the query result to the front end;

[0037] The query result is received;

[0038] Based on the query result, a list of allocation modes available to the target customer is obtained.

[0039] In addition, to achieve the above-mentioned purpose, the application also provides a allocation mode expansion device, which is arranged in the back end, and the device comprises:

[0040] An address receiving module is configured to receive a front-end service address, wherein the front-end service address is obtained after the front end develops a corresponding page component according to the business requirement of a target allocation mode, and packs the page component into a static file through a general module definition specification, and then deploys the static file;

[0041] An interface implementation module is configured to develop a verification interface and an execution interface according to the business requirement of the target allocation mode, and construct a target allocation service based on the verification interface and the execution interface;

[0042] a service deployment module, configured to deploy the target allocation service in a server, and assign a backend service address to the target allocation service;

[0043] a mode configuration module, configured to configure the target allocation mode in a preset plug-in configuration table, and add the front-end service address and the backend service address to the plug-in configuration table, so as to realize the extension of the target allocation mode.

[0044] In addition, to achieve the above-mentioned purpose, the present application also provides an allocation mode extension device, which comprises a memory, a processor and a computer program stored on the memory and executable on the processor, and the computer program is configured to realize the steps of the allocation mode extension method as described above.

[0045] In addition, to achieve the above-mentioned purpose, the present application also provides a storage medium, which is a computer readable storage medium, and the storage medium stores a computer program, and the computer program is executed by a processor to realize the steps of the allocation mode extension method as described above.

[0046] The one or more technical solutions provided by the present application have at least the following technical effects:

[0047] The present application receives the front-end service address through the backend, realizes and deploys the target allocation service, configures the target allocation mode in the preset plug-in configuration table through the backend, and maintains the front-end service address and the backend service address to the plug-in configuration table, so as to realize the plug-in registration of the target allocation mode. Thus, the scheme of dynamically loading the front-end page and the backend rule based on the plug-in configuration table can be realized. The new allocation mode can be quickly extended without changing the old allocation mode, the plug-in extension of the allocation mode is realized, and each allocation mode runs independently, which can improve the demand response speed and reduce the influence on the existing business process. BRIEF DESCRIPTION OF DRAWINGS

[0048] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present application and, together with the specification, serve to explain the principles of the application.

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0050] Figure 1 a flowchart provided by the allocation mode extension method embodiment one of the present application;

[0051] Figure 2 A service deployment topology diagram for the allocation mode expansion method of the present application;

[0052] Figure 3 A flowchart for the allocation mode expansion method of the present application;

[0053] Figure 4 A module structure diagram for the allocation mode expansion device of the present application;

[0054] Figure 5 A device structure diagram for the hardware operating environment involved in the allocation mode expansion method of the present application.

[0055] The object implementation, functional features and advantages of the present application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0056] It should be understood that the specific embodiments described herein are merely intended to explain the technical solutions of the present application, and are not intended to limit the present application.

[0057] In order to better understand the technical solutions of the present application, the following will be described in detail in conjunction with the drawings and specific embodiments.

[0058] The main solution of the present application is: receiving a front-end service address, the front-end service address being obtained after a front-end develops a corresponding page component according to a business requirement of a target allocation mode, and packs the page component into a static file through a general module definition specification, and then deploys the static file; developing a verification interface and an execution interface according to the business requirement of the target allocation mode, and constructing a target allocation service based on the verification interface and the execution interface; deploying the target allocation service in a server, and assigning a back-end service address to the target allocation service; configuring the target allocation mode in a preset plug-in configuration table, and adding the front-end service address and the back-end service address to the plug-in configuration table, so as to realize expansion of the target allocation mode.

[0059] In the present embodiment, the following is described with the business system as the execution subject for the sake of description.

[0060] Since the prior art has the shortcomings of high coupling degree and poor expansibility when implementing the allocation mode expansion function, the prior art generally mixes the elements related to the allocation mode and other elements of the allocation rules together, and when expanding a new allocation mode, the original code needs to be modified, which affects the old mode that is already in effect and running, and the prior art needs to return to test the original function, which is low in efficiency.

[0061] This application provides a solution that receives the front-end service address through a back-end, implements and deploys the target allocation service, configures the target allocation mode in a preset pluggable configuration table through the back-end, and maintains the front-end service address and the back-end service address in the pluggable configuration table to achieve pluggable registration of the target allocation mode. This enables a solution that dynamically loads the front-end page and back-end rules based on the pluggable configuration table, and can quickly expand the allocation mode without changing the old allocation mode, realizing pluggable expansion of allocation modes. Moreover, each allocation mode runs independently, which can improve the response speed of demand and reduce the impact on existing business processes.

[0062] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone; or an electronic device or allocation mode extension device capable of realizing the above functions; or an electronic system or business system capable of realizing the above functions. The following description uses a business system as an example to illustrate this embodiment and the subsequent embodiments.

[0063] Based on this, embodiments of this application provide a method for expanding allocation patterns, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the allocation mode extension method in this application.

[0064] In this embodiment, applied to the backend, the allocation mode expansion method includes steps S10 to S40:

[0065] Step S10: Receive the front-end service address. The front-end service address is obtained by the front-end developing the corresponding page components according to the business requirements of the target allocation mode, packaging the page components into static files through the general module definition specification, and then deploying the static files.

[0066] When a new allocation mode needs to be extended, the front end develops corresponding page components according to the business requirements of the new mode, packages them into static files using UMD (Universal Module Definition), and deploys the packaged static files to a web server or CDN to generate a front-end service entry point that users can access.

[0067] Step S20: Develop a verification interface and an execution interface according to the business requirements of the target allocation mode, and construct the target allocation service based on the verification interface and the execution interface;

[0068] Based on the business logic of the fund allocation model, the backend develops two corresponding interfaces: validate and execute. A complete fund allocation service is built based on the validation interface and the execution interface.

[0069] Step S30: Deploy the target allocation service on the server and allocate a backend service address to the target allocation service;

[0070] In this process, the backend service is deployed to an application server or cloud platform, and an API address that can be called by the frontend is allocated to the target allocation service.

[0071] Step S40: Configure the target allocation mode in the preset plug-in configuration table, and add the front-end service address and the back-end service address to the plug-in configuration table to realize the expansion of the target allocation mode.

[0072] After the front-end and back-end services are deployed, a new allocation mode is configured in the plug-in configuration table, and the service addresses of the front-end and back-end are maintained in the plug-in configuration table to realize the configuration of plug-in registration and discovery.

[0073] This embodiment provides a method for extending allocation modes. The application receives the front-end service address from the back-end, implements and deploys the target allocation service, configures the target allocation mode in a preset pluggable configuration table through the back-end, and maintains the front-end service address and the back-end service address in the pluggable configuration table to achieve pluggable registration of the target allocation mode. This enables a solution based on the pluggable configuration table to dynamically load the front-end page and back-end rules, allowing for rapid expansion of new allocation modes without modifying the old ones. This achieves pluggable expansion of allocation modes, and each allocation mode operates independently, improving demand response speed and reducing the impact on existing business processes.

[0074] This application embodiment utilizes a dynamic plug-and-play allocation configuration table to achieve rapid expansion of allocation modes. The front-end and back-end services of each mode are deployed independently and decoupled from each other, improving development efficiency and enriching the protocol support capabilities of overseas cash pools.

[0075] Based on Embodiment 1 of this application, in Embodiment 2 of this application, the content that is the same as or similar to that in Embodiment 1 can be referred to the above description, and will not be repeated hereafter. Based on this, after configuring the target allocation mode in the preset plug-in configuration table and maintaining the front-end service address and the back-end service address in the plug-in configuration table in step S40, steps S50 to S70 are further included:

[0076] Step S50: Receive the allocation mode selected by the target customer;

[0077] In one implementation, when the backend receives the allocation mode selected by the target customer and sends the allocation mode selected by the target customer to the backend, it can call the backend interface to verify the current availability of the mode.

[0078] Step S60: Configure the allocation protocol based on the allocation mode selected by the target customer;

[0079] The backend retrieves the associated backend service address from the plug-and-play configuration table based on the mode encoding selected by the user.

[0080] Step S70: In response to the allocation task triggering command, the allocation protocol is executed.

[0081] Among them, the triggering instructions for the allocation task include user-submitted (such as clicking the "Confirm Allocation" button), triggered by a scheduled task (such as automatically executing every morning), and triggered by an event-driven mechanism.

[0082] As one implementation method, running the transfer protocol may include: calling the verification interface to check preconditions (such as account status and balance); calling the execution interface to complete the fund transfer and record the transaction flow to the database; returning the execution result (success / failure reason) to the front end and triggering subsequent processes (such as sending SMS notification).

[0083] As one implementation method, the optimal transfer path can be automatically selected based on real-time exchange rates and fee comparisons.

[0084] As another implementation method, the allocation agreement and transaction records can be submitted to the blockchain for evidence storage to ensure immutability and traceability.

[0085] This application embodiment utilizes a dynamic plug-and-play allocation configuration table to achieve rapid expansion of allocation modes. The front-end and back-end services of each mode are deployed independently and decoupled from each other, improving development efficiency and enriching the protocol support capabilities of overseas cash pools.

[0086] Based on the above application embodiments, in this third embodiment, the content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter. On this basis, step S60, configuring the transfer protocol based on the transfer mode selected by the target customer, further includes steps S61 to S66:

[0087] Step S61: Receive the interface elements returned by the target customer on the front end;

[0088] It should be noted that after the target customer selects the corresponding allocation mode, the front end uses the general module definition specifications and script tags to dynamically load the corresponding static resources, realizing the plug-and-play effect of the front end interface. Then the target customer can fill in the corresponding interface elements, submit and save.

[0089] When a target customer fills in the corresponding interface elements, the system can recommend element values ​​based on the target customer's historical behavior and mark them for the target customer's confirmation.

[0090] Step S62: Call the verification interface corresponding to the allocation mode selected by the target customer, and verify the integrity of the interface elements through the verification interface;

[0091] The backend dynamically calls the verification interface of the mode implementation based on the mode type submitted by the target customer, judges the integrity of the interface elements, and completes the saving of the allocation agreement.

[0092] As one implementation method, verifying the integrity of the interface elements through the verification interface can be used to check whether the submitted interface elements meet the rule requirements of the mode (such as whether the required fields are complete, whether the format is correct, whether the amount exceeds the limit, etc.).

[0093] Step S63: If the integrity verification fails, a pop-up message is displayed to the target user.

[0094] For example, if the verification fails (e.g., missing required fields or incorrect format), a pop-up window will be displayed to the target customer to provide specific error information and guide them to correct and resubmit.

[0095] Step S64: If the integrity verification passes, perform the corresponding business processing through the execution interface;

[0096] After successful verification, the backend calls the execution interface (such as the payment gateway or bank interface) to complete the actual transfer operation and returns the processing result (such as success / failure status and transaction serial number).

[0097] Step S65: Generate an allocation agreement based on the allocation mode selected by the target customer and the information of the business processing.

[0098] The backend automatically generates an electronic transfer agreement based on the transfer mode and business processing results (such as amount, time, and accounts of both parties), clarifying the rights and obligations of both parties (such as transfer time, handling fee, and liability for breach of contract).

[0099] Step S66: Store the allocation agreement in the database.

[0100] This application reduces manual intervention and operational risks by using API calls and rule verification. Furthermore, it supports multiple allocation modes to adapt to different business scenarios. In this embodiment, the front-end, without affecting existing functionality, utilizes a general module definition specification and script tags to dynamically load static configuration pages for different allocation modes, achieving decoupling between them.

[0101] Based on the above application embodiments, in this application embodiment four, the same or similar content as the above embodiments can be referred to the above description, and will not be repeated hereafter. On this basis, step S70, responding to the allocation task triggering command, running the allocation protocol includes steps S71 to S76:

[0102] Step S71: In response to the allocation task triggering command, obtain the allocation mode type;

[0103] The backend receives allocation task trigger instructions initiated by users or external systems (such as clicking the "Submit Allocation" button, triggering a scheduled task, etc.) and parses the allocation mode type contained in the instructions.

[0104] Among these features, machine learning can be used to analyze the historical behavior of users or external systems and dynamically recommend the optimal allocation mode to users so that users or external systems can trigger allocation tasks.

[0105] As one implementation method, the priority of the transfer mode can be adjusted by combining external data (such as exchange rate fluctuations, target bank system load, and holiday arrangements), and the optimal transfer mode can be recommended to users according to the priority of the transfer mode.

[0106] As another implementation method, the optimal allocation mode can be adaptively selected by combining external data (such as exchange rate fluctuations, target bank system load, and holiday arrangements).

[0107] Step S72: Based on the allocation mode type, call the corresponding execution interface to obtain the preset specific element information and the corresponding account balance.

[0108] Depending on the transfer mode type, the backend calls different backend service interfaces to obtain the specific element information required for that mode (such as the payee's account, transfer amount, transfer conditions, etc.) and account balance (such as the payer's account available balance, frozen amount, etc.).

[0109] Step S73: Determine whether the preset first condition is met based on the specific element information and the corresponding account balance.

[0110] The backend verifies specific information elements and account balances based on the first conditions preset by the business rules (such as balance adequacy, transfer limit, account status, etc.).

[0111] Step S74: If not, record the allocation task failure status and the reason for the allocation task failure.

[0112] Step S75: If yes, then generate the transfer amount based on the specific element information and the corresponding account balance.

[0113] Step S76: Generate a transfer transaction based on the transfer amount and preset transfer elements.

[0114] Specifically, when the transfer agreement is executed, the system dynamically requests the execute interface provided by each mode according to the mode type. Based on the specific information set by the customer and the account balance, it determines whether the transfer can be initiated and the specific amount to be transferred. If the transfer can be initiated, the transfer amount is returned. Combined with other transfer elements filled in when setting up the timed transfer, such as payer information and payee information, the system generates the corresponding transfer transaction, realizing the plug-in operation of the transfer mode.

[0115] This application embodiment dynamically calls interfaces based on allocation mode types, adapting to various business scenarios and reducing manual intervention. In this embodiment, each backend mode runs independently, and the main service dynamically calls interfaces for different allocation modes according to a strategy, executing the corresponding allocation rules, thus achieving decoupling.

[0116] Based on the above-described embodiments, in Embodiment 5 of this application, the content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter. Furthermore, a method for extending the allocation mode is proposed and applied to the front end. The method includes steps S100 to S300:

[0117] Step S100: Develop corresponding page components according to the business requirements of the target allocation mode, and package the page components into static files through the general module definition specification;

[0118] When it is necessary to expand to a new allocation mode, the front end develops corresponding page components according to the business requirements of the new mode, and packages them into static files using UMD (Universal Module Definition).

[0119] Step S200: Deploy the static file through the front-end to obtain the front-end service address;

[0120] This involves deploying the packaged static files to a web server or CDN to generate a front-end service entry point that users can access.

[0121] Step S300: The front-end service address is sent to the back-end so that the back-end develops a verification interface and an execution interface according to the business requirements of the target allocation mode, constructs a target allocation service based on the verification interface and the execution interface, deploys the target allocation service on the server, allocates a back-end service address to the target allocation service, configures the target allocation mode in a preset plug-and-play configuration table, and then adds the front-end service address and the back-end service address to the plug-and-play configuration table to realize the expansion of the target allocation mode.

[0122] Based on the business logic of the fund allocation model, the backend develops two corresponding interfaces: validate and execute. A complete fund allocation service is built based on the validation and execution interfaces.

[0123] This involves deploying backend services to application servers or cloud platforms, and allocating API addresses that can be called by the frontend to the target allocation service.

[0124] After the front-end and back-end services are deployed, a new allocation mode is configured in the plug-in configuration table, and the service addresses of the front-end and back-end are maintained in the plug-in configuration table to realize the configuration of plug-in registration and discovery.

[0125] This application embodiment achieves complete decoupling of the model by utilizing front-end and back-end plug-in configuration, improving the speed of demand response, reducing the impact on existing business processes, and enriching the protocol support capabilities of overseas cash pools.

[0126] Based on the above application embodiments, in this application embodiment six, the content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter. On this basis, the step of maintaining the front-end service address and the back-end service address in the plug-in configuration table includes step S400:

[0127] Step S400: Query the plug-in configuration table to obtain a list of allocation modes available to the target customer, and return the allocation mode list to the target customer so that the target customer can select an allocation mode.

[0128] In one implementation method, the allocation mode list includes the allocation mode code and its corresponding front-end static resource address.

[0129] In one implementation, the front-end calls the back-end configuration query interface, passing in the target customer identifier (such as customer ID or account type). The back-end filters the allocation modes that the customer is authorized to use from the plug-and-play configuration table (e.g., filtering by customer level or region restrictions), and returns a list containing allocation mode codes and front-end static resource addresses. The front-end dynamically renders the mode selection interface (such as a drop-down menu or card list) based on the allocation mode codes and static resource addresses.

[0130] Step S400 includes steps S401 to S403:

[0131] Step S401: Send a plug-in configuration table query request to the backend, so that the backend queries the plug-in configuration table based on the plug-in configuration table query request, obtains the query result, and returns the query result to the frontend;

[0132] Among them, reference Figure 2 , Figure 2 This is a service deployment topology diagram for the allocation mode extension method in this application. The front-end can query the allocation mode configuration table from the back-end to obtain a list of allocation modes currently available to the customer, which includes the mode's code and its corresponding front-end static resource address.

[0133] Step S402: Receive the query result;

[0134] Step S403: Obtain a list of allocation modes available to the target customer based on the query results.

[0135] This application embodiment achieves complete decoupling of the model by utilizing front-end and back-end plug-in configuration, improving the speed of demand response, reducing the impact on existing business processes, and enriching the protocol support capabilities of overseas cash pools.

[0136] For example, to help understand the implementation process of the above embodiments, please refer to Figure 3 , Figure 3 This is a flowchart illustrating the allocation mode extension method of this application. Specifically, the process is divided into three stages: allocation mode plug-in setting, allocation protocol configuration, and allocation protocol operation.

[0137] When setting up the allocation mode as a plug-in, the process involves front-end interface development, back-end interface development, front-end and back-end service deployment, and adding new mode plug-in configurations.

[0138] Specifically, when configuring the allocation protocol, the front end sets the allocation protocol and queries the plug-and-play configuration table from the back end to obtain a list of allocation modes available to the target customer. The allocation mode list is then returned to the target customer so that the target customer can select an allocation mode. After the target customer selects an allocation mode, the interface is dynamically loaded based on the front end static file corresponding to the allocation mode selected by the target customer.

[0139] After the target customer submits the form on the interface, the backend receives the interface elements returned by the target customer on the frontend, calls the verification interface corresponding to the allocation mode selected by the target customer, and verifies the integrity of the interface elements through the verification interface. If the integrity verification fails, a pop-up prompt is displayed to the target user. If the integrity verification passes, the execution interface performs the corresponding business processing, generates an allocation protocol based on the allocation mode selected by the target customer and the information of the business processing, and stores the allocation protocol in the database.

[0140] During the execution of the transfer protocol, the backend responds to the transfer task triggering command, queries the configuration details, obtains the transfer mode type, and calls the corresponding execution interface based on the transfer mode type to obtain preset specific element information and corresponding account balance information. Based on the specific element information and the corresponding account balance information, it is determined whether a preset first condition is met. If not, the transfer task failure status and reason for failure are recorded. If yes, the transfer amount is generated based on the specific element information and the corresponding account balance information. Based on the transfer amount and preset transfer elements, a transfer transaction is generated.

[0141] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the allocation mode extension method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0142] This application also provides an allocation mode expansion device, please refer to... Figure 4 Located at the rear end, the allocation mode expansion device includes:

[0143] Address receiving module 10 is used to receive front-end service address, which is obtained by the front-end developing corresponding page components according to the business requirements of the target allocation mode, packaging the page components into static files through the general module definition specification, and deploying the static files.

[0144] Interface implementation module 20 is used to develop verification interfaces and execution interfaces according to the business requirements of the target allocation mode, and to construct the target allocation service based on the verification interfaces and the execution interfaces;

[0145] The service deployment module 30 is used to deploy the target allocation service in the server and allocate a backend service address to the target allocation service.

[0146] The mode configuration module 40 is used to configure the target allocation mode in a preset plug-in configuration table, and add the front-end service address and the back-end service address to the plug-in configuration table to realize the expansion of the target allocation mode.

[0147] The allocation mode expansion device provided in this application, employing the allocation mode expansion method in the above embodiments, can solve the technical problem of low efficiency in the prior art when expanding to a new allocation mode, which requires modifying the relevant code of the old allocation mode and affects the old allocation mode already in operation. Compared with the prior art, the beneficial effects of the allocation mode expansion device provided in this application are the same as those of the allocation mode expansion method provided in the above embodiments, and other technical features in the allocation mode expansion device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0148] This application provides an allocation mode expansion device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the allocation mode expansion method in the above embodiment 1.

[0149] The following is for reference. Figure 5 The diagram illustrates a structural schematic suitable for implementing the allocation mode extension device of the embodiments of this application. The allocation mode extension device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The allocation mode extension device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0150] like Figure 5As shown, the allocation mode extension device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that can perform various appropriate actions and processes according to a program stored in the read-only memory 1002 or a program loaded from the storage device 1003 into the random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the allocation mode extension device. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the allocation mode extension device to communicate wirelessly or wiredly with other devices to exchange data. Although the figures show allocation mode extension devices with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0151] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0152] The allocation mode expansion device provided in this application, employing the allocation mode expansion method in the above embodiments, can solve the technical problem of low efficiency in the prior art when expanding to a new allocation mode, which requires modifying the relevant code of the old allocation mode and affects the old allocation mode already in operation. Compared with the prior art, the beneficial effects of the allocation mode expansion device provided in this application are the same as those of the allocation mode expansion method provided in the above embodiments, and other technical features in this allocation mode expansion device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0153] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0154] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0155] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the allocation mode expansion method in the above embodiments.

[0156] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0157] The aforementioned computer-readable storage medium may be included in the allocation mode expansion device; or it may exist independently and not assembled into the allocation mode expansion device.

[0158] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by the allocation mode extension device, the allocation mode extension device: receives a front-end service address, which is obtained by deploying the static file after the front-end develops corresponding page components according to the business requirements of the target allocation mode and packages the page components into a static file according to the general module definition specification; develops a verification interface and an execution interface according to the business requirements of the target allocation mode, and constructs a target allocation service based on the verification interface and the execution interface; deploys the target allocation service in the server and allocates a back-end service address to the target allocation service; configures the target allocation mode in a preset plug-and-play configuration table, and adds the front-end service address and the back-end service address to the plug-and-play configuration table to realize the extension of the target allocation mode.

[0159] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0160] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0161] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0162] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described allocation mode expansion method. This solves the technical problem in the prior art where, when expanding to a new allocation mode, the original code needs to be modified, affecting existing, running modes and resulting in low efficiency. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the allocation mode expansion method provided in the above embodiments, and will not be repeated here.

[0163] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for expanding allocation patterns, characterized in that, Applied to the backend, the method includes the following steps: Receive the front-end service address, which is obtained by the front-end developing corresponding page components according to the business requirements of the target allocation mode, packaging the page components into static files through the general module definition specification, and then deploying the static files. Develop verification and execution interfaces according to the business requirements of the target allocation mode, and construct the target allocation service based on the verification and execution interfaces; Deploy the target allocation service on the server and allocate a backend service address to the target allocation service; Configure the target allocation mode in the preset plug-in configuration table, and add the front-end service address and the back-end service address to the plug-in configuration table to expand the target allocation mode.

2. The method as described in claim 1, characterized in that, The step of configuring the target allocation mode in the preset plug-in configuration table and maintaining the front-end service address and the back-end service address in the plug-in configuration table includes: Receive the allocation mode selected by the target customer; Configure the allocation protocol based on the allocation mode selected by the target customer; In response to the allocation task trigger command, the allocation protocol is executed.

3. The method as described in claim 2, characterized in that, The steps for configuring the allocation protocol based on the allocation mode selected by the target customer include: Receive interface elements returned by the target customer on the front end; Call the verification interface corresponding to the allocation mode selected by the target customer, and verify the integrity of the interface elements through the verification interface; If the integrity verification fails, a pop-up message will be displayed to the target user. If the integrity verification passes, the corresponding business processing is performed through the execution interface; A transfer agreement is generated based on the transfer mode selected by the target customer and the information of the business processing. The allocation agreement is stored in the database.

4. The method as described in claim 2, characterized in that, The step of running the allocation protocol in response to the allocation task triggering command includes: In response to the allocation task trigger command, obtain the allocation mode type; Based on the allocation mode type, the corresponding execution interface is called to obtain the preset specific element information and the corresponding account balance. Based on the specific element information and the corresponding account balance, determine whether the preset first condition is met; If not, record the failure status and reason for the allocation task. If so, the transfer amount is generated based on the specific element information and the corresponding account balance. Based on the allocated amount and preset allocation elements, an allocation transaction is generated.

5. A method for expanding allocation patterns, characterized in that, Applied to the front end, the method includes the following steps: Develop corresponding page components according to the business requirements of the target allocation model, and package the page components into static files through the general module definition specification; The static files are deployed through the front-end to obtain the front-end service address; The front-end service address is sent to the back-end so that the back-end can develop verification and execution interfaces according to the business requirements of the target allocation mode, construct the target allocation service based on the verification and execution interfaces, deploy the target allocation service on the server, allocate a back-end service address to the target allocation service, configure the target allocation mode in a preset plug-and-play configuration table, and then add the front-end service address and the back-end service address to the plug-and-play configuration table to realize the expansion of the target allocation mode.

6. The method as described in claim 5, characterized in that, The step of maintaining the front-end service address and the back-end service address in the plug-in configuration table includes: The plug-in configuration table is queried to obtain a list of allocation modes available to the target customer, and the list of allocation modes is returned to the target customer so that the target customer can select an allocation mode.

7. The method as described in claim 6, characterized in that, The query of the plug-in configuration table to obtain the list of allocation modes available to the target customer includes: Send a plug-in configuration table query request to the backend, so that the backend can query the plug-in configuration table based on the plug-in configuration table query request, obtain the query result, and return the query result to the frontend; Receive the query results; Based on the query results, obtain a list of allocation modes available to the target customer.

8. A method for expanding allocation patterns, characterized in that, Located at the rear end, the device includes: The address receiving module is used to receive the front-end service address. The front-end service address is obtained by the front-end developing corresponding page components according to the business requirements of the target allocation mode, packaging the page components into static files through the general module definition specification, and then deploying the static files. The interface implementation module is used to develop verification and execution interfaces according to the business requirements of the target allocation mode, and to construct the target allocation service based on the verification and execution interfaces. The service deployment module is used to deploy the target allocation service on the server and allocate a backend service address to the target allocation service. The mode configuration module is used to configure the target allocation mode in a preset plug-in configuration table, and add the front-end service address and the back-end service address to the plug-in configuration table to realize the expansion of the target allocation mode.

9. A device for expanding allocation modes, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the allocation mode expansion method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the allocation mode expansion method as described in any one of claims 1 to 7.

Images