Financial service processing method and device, electronic equipment and program product
By breaking down system functions into independent minimum business units and managing them using a registry center and routing gateway, the problems of inconsistent functions and difficulty in maintenance in traditional software development are solved, enabling flexible and efficient business processing and maintenance.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-07
- Publication Date
- 2026-03-27
AI Technical Summary
Traditional software development methods struggle to meet the demands of rapid iteration and flexible market response in large enterprise applications, especially when sharing functionality across applications, which can lead to inconsistencies and difficulties in maintenance.
The system functions are broken down into independent minimum business units, and managed and invoked through a registry center and routing gateway mechanism, so as to achieve flexible combination and embedding of functions and avoid duplicate coding.
It enables independent development, testing, and deployment of business functions, ensuring functional consistency and simplifying maintenance, thereby improving development efficiency and system stability.
Smart Images

Figure CN121742802A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of financial technology or other related fields, and more specifically, to a financial business processing method and apparatus, electronic device, and program product. Background Technology
[0002] In software development, with the increasing complexity of business operations and the dynamic changes in the IT environment, traditional software architectures and development models face growing challenges. This is especially true for large enterprise applications, such as the core business systems of financial institutions, where the sheer number of functional modules, the complexity of business logic, and the tight dependencies between systems make it difficult for traditional development methods to meet the demands of rapid iteration and flexible response to market needs.
[0003] Currently, the main reuse mechanism commonly used in the industry is source code copying. However, although source code copying can achieve cross-application function sharing to a certain extent, it is prone to causing inconsistencies and difficulties in maintenance due to the lack of effective version control and change management mechanisms.
[0004] There is currently no effective solution to the above problems. Summary of the Invention
[0005] This invention provides a financial business processing method and apparatus, electronic device, and program product to at least solve the technical problem that in the process of software development, when using source code copying strategies for cross-application function sharing, inconsistencies in functionality and difficulty in maintenance are likely to occur.
[0006] To achieve the above objectives, according to one aspect of this application, a financial business processing method is provided, comprising: receiving a business processing request from a calling application, and extracting a business scenario and multiple business processing flows from the business processing request; selecting multiple minimum business units required for each business processing flow based on the business scenario and the business processing flows, wherein the minimum business unit includes the minimum executable module with business functions after decomposing system functions; arranging and combining all the minimum business units according to the business processing flows to obtain a business development function combination; embedding the business development function combination into the calling application system, and having the calling application system execute each business processing flow.
[0007] Optionally, before receiving the business processing request from the calling application system, the method further includes: obtaining each system sub-function of the target application system; splitting the system sub-functions to obtain at least one minimum module including each business function; packaging the minimum module into an executable module to form multiple minimum business units; registering each minimum business unit to a registration center, whereby the registration center stores the network address of each minimum business unit.
[0008] Optionally, the step of decomposing the system sub-functions to obtain at least one minimum module including each business function includes: analyzing all the system sub-functions and determining functional modules that can operate independently and have clear business boundaries based on the analysis results; evaluating each identified functional module to obtain a module reuse evaluation result, wherein the module reuse evaluation result includes whether the functional module can be reused as a minimum business unit; for functional modules whose module reuse evaluation result indicates that they can be reused as minimum business units, decomposing the functional module into the minimum module that can implement a business function.
[0009] Optionally, after decomposing the system sub-functions to obtain at least one minimum module including each business capability, the method further includes: configuring the user interface of the minimum module through a preset code platform or preset code development tool; establishing a mapping relationship between the user interface and the business functions implemented by the minimum module; and adding the minimum module to the function module tree using the user interface, wherein the function module tree is used to display the business functions corresponding to each minimum module in a tree structure.
[0010] Optionally, the step of selecting multiple minimum business units required for each business process based on the business scenario and the business processing flow includes: linking to a target routing gateway corresponding to the calling application; subscribing to the multiple minimum business units required by the target routing gateway, and sending the minimum business unit subscription information to the registration center through the target routing gateway; and obtaining the multiple minimum business units fed back by the registration center through the target routing gateway.
[0011] Optionally, after obtaining the plurality of minimum service units fed back by the registration center through the target routing gateway, the method further includes: updating the current state of each of the minimum service units to an available state through the target routing gateway.
[0012] Optionally, the step of embedding the business development function combination into the caller application system includes: embedding each of the smallest business units in the business development function combination into the caller application system, and reusing the business functions of the smallest business units.
[0013] According to another aspect of the present invention, a financial business processing apparatus is also provided, comprising: a request receiving unit, configured to receive a business processing request from a calling application, and extract a business scenario and multiple business processing flows from the business processing request; a minimum business unit selection unit, configured to select multiple minimum business units required for each business processing flow based on the business scenario and the business processing flow, wherein the minimum business unit includes the minimum executable module having business functions after decomposing system functions; a combination unit, configured to arrange and combine all the minimum business units according to the business processing flow to obtain a business development function combination; and an execution unit, configured to embed the business development function combination into the calling application system, and have the calling application system execute each business processing flow.
[0014] Optionally, the financial business processing device further includes: a system function acquisition unit, used to acquire each system sub-function of the target application system before receiving a business processing request from the calling application system; a function splitting unit, used to split the system sub-functions to obtain at least one minimum module including each business function; a module packaging unit, used to package the minimum module into an executable module to form multiple minimum business units; and a registration unit, used to register each minimum business unit to a registration center, whereby the registration center stores the network address of each minimum business unit.
[0015] Optionally, the function decomposition unit includes: a function analysis module, used to analyze all the sub-functions of the system and determine, based on the analysis results, functional modules that can operate independently and have clear business boundaries; an evaluation module, used to evaluate each identified functional module to obtain a module reuse evaluation result, wherein the module reuse evaluation result includes whether the functional module can be reused as a minimum business unit; and a decomposition module, used to decompose the functional modules that can be reused as minimum business units based on the module reuse evaluation result into the minimum modules that can implement a business function.
[0016] Optionally, the financial business processing device further includes: a user interface configuration module, used to configure the user interface of the minimum module through a preset code platform or preset code development tool after the system sub-functions are broken down to obtain at least one minimum module including various business capabilities; a mapping relationship establishment module, used to establish a mapping relationship between the user interface and the business functions implemented by the minimum module; and a module tree addition module, used to add the minimum module to the functional module tree using the user interface, wherein the functional module tree is used to display the business functions corresponding to each minimum module in a tree structure.
[0017] Optionally, the minimum service unit selection unit includes: a linking module for linking to a target routing gateway corresponding to the calling application; a subscription module for subscribing to the required multiple minimum service units through the target routing gateway and sending the minimum service unit subscription information to the registration center through the target routing gateway; and a minimum service unit acquisition module for acquiring the multiple minimum service units fed back by the registration center through the target routing gateway.
[0018] Optionally, the financial business processing apparatus further includes: a status update unit, configured to update the current status of each of the minimum business units to an available status via the target routing gateway after obtaining the plurality of minimum business units fed back by the registration center through the target routing gateway.
[0019] Optionally, the execution unit includes an embedding module, used to embed each of the smallest business units in the business development function combination into the calling application system, and reuse the business functions of the smallest business units.
[0020] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the financial business processing method described above.
[0021] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the financial business processing method described above.
[0022] According to another aspect of the present invention, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps of the financial business processing method described in any one of the above embodiments.
[0023] In this disclosure, a business processing request from a calling application is received, and a business scenario and multiple business processing flows are extracted from the request. Based on the business scenario and business processing flows, multiple minimum business units required for each business processing flow are selected. Each minimum business unit includes the minimum executable module with business functions after the system functions are broken down. All minimum business units are arranged and combined according to the business processing flows to obtain a business development function combination. The business development function combination is embedded into the calling application system, and the calling application system executes each business processing flow.
[0024] Based on the above-mentioned publicly available information, the system functions can be subdivided into independent minimum business units. Each unit encapsulates specific business logic and data processing capabilities, ensuring functional consistency. Each calling application system can flexibly select and combine the minimum business units according to the business scenario, and embed them into the business process through simple configuration without additional coding and compilation work. This simplifies the construction and adjustment of business logic, breaks the coupling caused by traditional source code copying, and makes business functions independent entities that can be developed, tested, and deployed. This facilitates code maintenance and solves the technical problems that easily arise when using source code copying strategies for cross-application function sharing during software development, such as inconsistent functions and difficulty in maintenance. Attached Figure Description
[0025] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:
[0026] Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing financial business processing methods is shown.
[0027] Figure 2 This is a flowchart of an optional financial business processing method according to an embodiment of the present invention;
[0028] Figure 3 This is a schematic diagram of an optional development apparatus based on a minimum business unit according to an embodiment of the present invention;
[0029] Figure 4 This is a flowchart illustrating another development method based on the minimum business unit according to an embodiment of the present invention.
[0030] Figure 5 This is a schematic diagram of an optional financial transaction processing device according to an embodiment of the present invention;
[0031] Figure 6 This is a structural block diagram of an electronic device for performing a financial business processing method according to an embodiment of this application. Detailed Implementation
[0032] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0033] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0034] To facilitate understanding of the present invention by those skilled in the art, some terms or nouns involved in the various embodiments of the present invention are explained below:
[0035] The Service Registry (SR) is a service node responsible for storing and managing the address information and service status of all the smallest business units. As a central directory for these smallest business units, it enables other services to discover, register, and query the location of these units, thereby facilitating inter-service communication and functional reuse.
[0036] A routing gateway (RG) is a service node that subscribes to the smallest business unit, receives information change notifications from the registry center, and controls the accessibility of the smallest business unit based on this information.
[0037] User Interface (UI) refers to the part of a system that interacts with the user, including various visual elements, input / output mechanisms, and operational processes. In this invention, the smallest business units are incorporated into the UI and packaged into executable modules. These business units are then integrated with the graphical user interface, enabling end users to intuitively operate these units and perform business processing.
[0038] The Hypertext Transfer Protocol, or HTTP for short, is a protocol used to transfer hypertext from a World Wide Web server to a local browser. In this invention, the application system retrieves its subscribed smallest business unit via the HTTP protocol.
[0039] An Application Programming Interface (API) defines the rules for communication between applications, allowing different software modules to interact with each other without needing to know the internal implementation details of each other.
[0040] It should be noted that the financial business processing method and apparatus disclosed herein can be used in the financial technology field when software development is based on the smallest business unit, and can also be used in any field other than the financial technology field when software development is based on the smallest business unit. This disclosure does not limit the application field of the financial business processing method and apparatus.
[0041] It should be noted that the information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data) collected in this public disclosure are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with the relevant laws, regulations, and standards of the relevant regions, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse. For example, this system has interfaces with relevant users or organizations. Before obtaining relevant information, a request to obtain the information needs to be sent to the aforementioned user or organization through the interface, and the relevant information is obtained only after receiving consent from the aforementioned user or organization.
[0042] It should be noted that in this disclosure, customer information is collected and analyzed, and users are provided with corresponding operation entry points to choose whether to agree to or reject the automated decision results; if the user chooses to reject, the process will proceed to the expert decision-making process.
[0043] The following embodiments of the present invention can be applied to various financial business processing systems / applications / devices. The present invention is applicable to the field of software development, especially to enterprise-level application systems that pursue efficient development, flexible business processing, and functional reuse.
[0044] This invention reduces development time from scratch and accelerates the time to market for new products or features by reusing the smallest business unit. Simultaneously, once the smallest business unit changes, all application systems subscribed to that unit will automatically synchronize and update, avoiding repetitive manual modifications and testing, and reducing long-term maintenance costs. It ensures functional consistency across all application systems using the same smallest business unit, eliminating business logic discrepancies caused by version differences.
[0045] The present invention will now be described in detail with reference to various embodiments.
[0046] Example 1
[0047] According to an embodiment of the present invention, an embodiment of a financial business processing method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.
[0048] The financial business processing method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, computer terminal or similar computing device. Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing financial business processing methods is shown. Figure 1 As shown, computer terminal 10 (or mobile device) may include one or more ( Figure 1 The processor 102 (which may include, but is not limited to, a microprocessor MCU (Microcontroller Unit) or a programmable gate array (FPGA)) is shown as 102a, 102b, ..., 102n. It also includes a memory 104 for storing data and a transmission device 106 for communication functions. In addition, it may include: a display, an input / output interface (I / O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.
[0049] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).
[0050] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the financial business processing method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the aforementioned financial business processing method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0051] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.
[0052] The display can be, for example, a touchscreen liquid crystal display (LCD), which allows the user to interact with the user interface of the computer terminal 10 (or mobile device).
[0053] Under the aforementioned operating environment, this application provides the following: Figure 2 The financial transaction processing method shown. Figure 2 This is a flowchart of an optional financial transaction processing method according to an embodiment of the present invention, such as... Figure 2 As shown, the method includes the following steps S201 to S204. The present invention will be described in detail below with reference to each implementation step.
[0054] Step S201: Receive the business processing request from the calling application, and extract the business scenario and multiple business processing flows from the business processing request.
[0055] In this embodiment, when the development team develops code through the calling application, they seek to utilize the smallest business units to execute specific tasks or business processes, which can generate business processing requests. Next, this embodiment extracts key information from the business processing requests, mainly including the business scenario and multiple business processing flows. The business scenario can be a description of the business environment or specific problem currently faced by the calling application, which helps determine the most suitable set of smallest business units for the current needs. On the other hand, the business processing flows specifically specify the processing steps and sequence, helping to build the most efficient business logic flow and ensuring that business requests are executed according to the predetermined plan.
[0056] It's important to note that parsing the business scenario and process within a business processing request ensures that the calling application can accurately obtain the minimum required business unit. This also facilitates a deeper understanding and optimization of business needs. For example, if the business scenario involves quickly completing a transfer in a complex transaction environment, the extracted information will help select the minimum business units focused on high-speed transaction processing and security checks, rather than general account information query modules.
[0057] It is worth noting that this embodiment is not limited to a fixed process or scenario parsing template. On the contrary, it can flexibly parse and reorganize the business processing flow according to the specific needs and context of the calling application. Even when facing similar business scenarios, different business processing flows can be customized according to subtle differences, thereby better adapting to changes in user needs or business rules, which helps to improve the application's adaptability and user satisfaction.
[0058] In this embodiment, to address the issues of functional inconsistency and maintenance difficulties encountered in software development, a scheme for generating and registering minimum business units is provided. Optionally, before receiving a business processing request from a calling application system, the method further includes: obtaining various system sub-functions of the target application system; decomposing the system sub-functions to obtain at least one minimum module including each business function; packaging the minimum module into an executable module to form multiple minimum business units; and registering each minimum business unit to a registration center, whereby the registration center stores the network address of each minimum business unit.
[0059] First, a comprehensive understanding of the target application system's structure is required, meticulously identifying each independent system sub-function. Next, the identified sub-functions are finely broken down, ensuring each decomposed module has clear boundaries and independent business processing capabilities. This decomposition process emphasizes module cohesion and standardized external interfaces. The smallest decomposed modules are then further packaged into executable modules, forming multiple minimum business units. This packaging process includes not only the business logic code but also related data structures, configuration files, and user interface components, ensuring that the smallest business unit can be directly called by other application systems as a complete business processing unit.
[0060] Each newly formed minimum business unit is registered with a unified registry center, which is responsible for storing the metadata of the minimum business units, including but not limited to network address, version information, and function description. This registration process establishes global visibility for the minimum business units, allowing other user applications to obtain and utilize these units through a subscription mechanism, enabling rapid reuse and flexible combination of functions.
[0061] Optionally, the step of decomposing the system sub-functions to obtain at least one minimum module including each business function includes: analyzing all system sub-functions and determining functional modules that can operate independently and have clear business boundaries based on the analysis results; evaluating each identified functional module to obtain a module reuse evaluation result, wherein the module reuse evaluation result includes whether the functional module can be reused as a minimum business unit; for functional modules whose module reuse evaluation result indicates that they can be reused as minimum business units, decomposing the functional module into a minimum module that can implement a business function.
[0062] In this embodiment, the process of breaking down system sub-functions into minimum business units begins with a comprehensive analysis of all system sub-functions. This helps identify sub-functions that can operate independently and have clear business boundaries, providing intuitive guidance for subsequent modular decomposition. Through this analysis, it can be determined which functional modules are suitable as the basis for the minimum business units. The minimum business units possess high cohesion and clear business logic, thereby facilitating function reuse and system scalability.
[0063] Subsequently, each identified functional module is thoroughly evaluated to obtain module reuse assessment results. The evaluation process focuses on whether the module can be effectively reused as the smallest business unit, considering not only the module's independence and business boundaries, but also technical implementation, security, and performance. For functional modules whose evaluation results indicate they can be reused as the smallest business unit, this embodiment further decomposes these modules into smallest modules, each focusing on implementing a single business function. This decomposition helps improve the flexibility and efficiency of business processing. When other application systems call these smallest modules, their specific business needs can be precisely met without additional development work.
[0064] After the decomposition and evaluation are completed, this embodiment also involves configuring the user interface of the minimum module through a preset code platform or preset code development tool, which helps to enhance the usability and user experience of the minimum business unit and ensure that even the smallest business function can be operated and managed through an intuitive interface. Optionally, after decomposing the system sub-functions to obtain at least one minimum module including various business capabilities, the method further includes: configuring the user interface of the minimum module through a preset code platform or preset code development tool; establishing a mapping relationship between the user interface and the business functions implemented by the minimum module; and adding the minimum module to the function module tree using the user interface, wherein the function module tree is used to display the business functions corresponding to each minimum module in a tree structure.
[0065] It should be noted that this embodiment utilizes the established mapping relationship. Through the user interface, the smallest modules are added to the functional module tree, and a tree structure is used to display the business functions corresponding to each smallest module. The construction of the functional module tree helps to intuitively present the hierarchical structure and relationships of all business functions in the system. This not only greatly assists developers in understanding the system architecture but also facilitates business analysts and users in identifying and selecting the required business functions without delving into technical details. Furthermore, the tree structure display method simplifies the management and maintenance of the smallest modules, enabling calling application systems to more efficiently discover and subscribe to the required smallest business units, thereby combining them into new business processes.
[0066] Step S202: Based on the business scenario and business processing flow, select multiple minimum business units required for each business processing flow. The minimum business unit includes the minimum executable module with business functions after the system functions are broken down.
[0067] Optionally, based on the business scenario and business processing flow, the steps for selecting multiple minimum business units required for each business processing flow are selected, including: linking to the target routing gateway corresponding to the calling application; subscribing to the multiple minimum business units required on the target routing gateway, and sending the minimum business unit subscription information to the registration center through the target routing gateway; and obtaining the multiple minimum business units fed back by the registration center through the target routing gateway.
[0068] The smallest business unit, as a product of system function decomposition, each carries specific business functions and can be executed and invoked independently. This helps the calling application system quickly integrate the required business capabilities without rewriting or significantly modifying existing code, thereby accelerating the design and implementation of business processes.
[0069] At the operational level, in this embodiment, the calling application system first connects to its corresponding target routing gateway. This connection can be seen as establishing a direct channel to the minimum business unit market, enabling the calling application system to easily access various registered minimum business units. Next, the calling application system can subscribe to multiple required minimum business units at the target routing gateway. The subscription action is not a simple request but includes a crucial step—sending the minimum business unit subscription information to the registration center. This helps maintain the real-time and accuracy of the registration center's information, ensuring that any operation involving minimum business unit updates can be quickly perceived and responded to by other parts of the system.
[0070] Finally, through the target routing gateway, the calling application system can obtain multiple minimum business units fed back by the registry center, meaning that the calling application system has clearly identified the specific business capabilities it needs and their sources. These minimum business units can then be directly embedded into the calling application system, combined and executed according to the established business processing flow, thus eliminating the need to rewrite code or perform complex integration work, greatly improving development efficiency and flexibility.
[0071] Optionally, after obtaining multiple minimum service units from the registry center through the target routing gateway, the method further includes: updating the current state of each minimum service unit to an available state through the target routing gateway.
[0072] It should be noted that this embodiment utilizes a subscription mechanism, allowing the target routing gateway to receive notifications of changes to the smallest business unit information from the registry center, including status changes such as unit online, offline, update, or deletion. Once the caller application successfully acquires the smallest business unit, the target routing gateway is responsible for updating the status of these units to "available," ensuring they can immediately participate in the construction and execution of the business process. In a software system, the status of a unit directly affects its ability to be called and executed. Setting the status to "available" means that these units are ready and can be seamlessly integrated into the caller application's business process. This helps avoid call failures or business interruptions due to unsynchronized unit statuses, thereby improving the overall system stability and user experience.
[0073] Step S203: According to the business processing flow, arrange and combine all the smallest business units to obtain the business development function combination.
[0074] In this embodiment, step S203 focuses on the precise arrangement and combination of all the acquired minimum business units according to a predetermined business processing flow, which helps to construct a specific combination of business development functions. Simultaneously, this embodiment can flexibly arrange the execution order and interaction methods of different business units to form business logic chains that meet actual needs. Each minimum business unit is an independently encapsulated specific business capability, and the arrangement and combination connect these dispersed capabilities to form a complete business processing flow. This mechanism can greatly enrich the flexibility of business development, enabling diverse functional expressions to be derived even from different arrangements and combinations of the same set of business units, meeting the needs of different scenarios.
[0075] Step S204: The business development functions are embedded into the calling application system, and the calling application system executes each business processing flow.
[0076] Optionally, the step of embedding the business development function combination into the caller's application system includes: embedding each of the smallest business units in the business development function combination into the caller's application system, and reusing the business functions of the smallest business units.
[0077] When embedding business development functionalities into the calling application system, the key is to directly embed the smallest business units within the combination into the application system and immediately begin reusing the existing business functions of these smallest business units. This not only helps to quickly build business logic but also ensures the consistency and accuracy of business functions. Through direct embedding and reuse, the calling application system can establish complex business processes in a very short time to meet rapidly changing market demands while ensuring software quality and stability.
[0078] In this embodiment, the calling application system does not need to write or maintain these business functions from scratch. Instead, it can directly utilize the smallest business units that have been arranged and combined, which significantly improves development efficiency and reduces maintenance costs.
[0079] Through the above steps, business processing requests from the calling application can be received, and business scenarios and multiple business processing flows can be extracted from the requests. Based on the business scenarios and business processing flows, multiple minimum business units required for each business processing flow are selected. Each minimum business unit includes the smallest executable module with business functions after the system functions have been broken down. All minimum business units are arranged and combined according to the business processing flow to obtain a business development function combination. This business development function combination is embedded into the calling application system, which then executes each business processing flow. In this embodiment, system functions can be subdivided into independent minimum business units. Each unit encapsulates specific business logic and data processing capabilities, ensuring functional consistency. Each calling application system can flexibly select and combine minimum business units according to the business scenario and embed them into the business process through simple configuration, without additional coding and compilation work. This simplifies the construction and adjustment of business logic, breaks the coupling caused by traditional source code copying, and makes business functions independent entities that can be developed, tested, and deployed, facilitating code maintenance. This solves the technical problem of inconsistent and difficult-to-maintain functions that easily occur when using source code copying strategies for cross-application function sharing during software development.
[0080] The following describes in detail another optional implementation method.
[0081] To address the low efficiency and inflexibility of software development in related technologies, this invention provides a development method based on minimum business units. First, the system functionality is broken down into one or more minimum modules with specific business capabilities. Then, each of these sub-modules is added to the user interface (UI) and packaged into an executable module using a low-code platform or other development tools, forming minimum business processing units. Next, these minimum business processing units are registered with a registry center. Each calling application system subscribes to the required minimum business units at its corresponding routing gateway. Then, each calling application system retrieves its subscribed minimum business units. Finally, each calling application system simply selects the required minimum business units according to its business scenario needs, and through permutation and combination, strings them together in an orderly manner to complete the corresponding business processing flow, thereby achieving flexible, convenient, and efficient development.
[0082] Figure 3 This is a schematic diagram of an optional development apparatus based on a minimum business unit according to an embodiment of the present invention, such as... Figure 3As shown, the development apparatus may include: application X100, including: minimum business unit X101; application Y200, including: minimum business unit Y201; application Z300; routing gateway 400; and registration center 500.
[0083] First, the business functions of applications X100 and Y200 are broken down into small modules that can achieve the minimum business processing capability. These small modules are then added to the UI and packaged into independently executable software units, called minimum business units. In this embodiment, minimum business unit X101 and minimum business unit Y201 are respectively one of the minimum business units of applications X100 and Y200.
[0084] Then, applications X100 and Y200 register the smallest service unit X101 and the smallest service unit Y201 with the registration center 500, respectively. The registration center 500 stores information such as the network address of each smallest service unit.
[0085] Subsequently, suppose applications X100, Y200, and Z300 need to reuse the smallest business units of other applications based on their own requirements. For example, application X100 wants to reuse the smallest business unit Y201 of application Y200, application Y200 wants to reuse the smallest business unit X101 of application X100, and application Z300 wants to reuse both the smallest business units X101 of application X100 and Y201 of application Y200. In this case, applications X100, Y200, and Z300 only need to subscribe to the smallest business units they need in the routing gateway 400.
[0086] Registration center 500 notifies routing gateway 400 of the online status of minimum service unit X101 of application X100 and minimum service unit Y201 of application Y200. Routing gateway 400 updates the status of minimum service unit X101 and minimum service unit Y201 to available.
[0087] Application X100 retrieves its required minimum business unit Y201 from routing gateway 400 via HTTP. Application Y200 retrieves its required minimum business unit X101 from routing gateway 400 via HTTP. Application Z300 retrieves its required minimum business unit X101 and minimum business unit Y201 from routing gateway 400 via HTTP.
[0088] Finally, Application X100 directly embeds the smallest business unit Y201 into its own application system, reusing the functionality of the smallest business unit Y201 of Application Y200 without additional coding or compilation; Application Y200 directly embeds the smallest business unit X101 into its own application system, reusing the functionality of the smallest business unit X101 of Application X100 without additional coding or compilation; Application Z300, according to the needs of the business usage scenario, arranges and strings the smallest business units X101 and Y201 in an orderly manner, embedding them into its own application system, while reusing the functionality of the smallest business units X101 of Application X100 and Y201 of Application Y200 without additional coding or compilation.
[0089] To further illustrate, let's take application Z300 as an example. Suppose application Z300 wants to implement a business process for paying labor remuneration. The business function of the smallest business unit X101 of application X100 is "paying labor fees", and the business function of the smallest business unit Y201 of application Y200 is "confirming the amount of labor". Then, the permutation and combination "Z (smallest business unit X101, smallest business unit Y201)" realizes the "prepayment" business process, while the permutation and combination "Z (smallest business unit Y201, smallest business unit X101)" realizes the "settlement" business process.
[0090] Figure 4 This is a flowchart illustrating another development method based on the minimum business unit according to an embodiment of the present invention, such as... Figure 4 As shown, the development method includes:
[0091] Step S401: Decompose the system functions into one or more minimum modules with specific business capabilities.
[0092] Step S402 involves developing the functionality of each of the split modules using a low-code platform or other development tools.
[0093] Step S403: Add the completed small modules to the UI and package them into an executable module to form the smallest business processing unit.
[0094] Step S404: Register the smallest business processing unit to the registration center (business unit market).
[0095] Step S405: Each calling application subscribes to the minimum service unit required by the corresponding routing gateway.
[0096] In step S406, the registration center notifies the routing gateway of the change information of the smallest business unit.
[0097] In step S407, each calling application retrieves its own subscribed minimum business unit.
[0098] In step S408, each calling application will embed the smallest business unit it calls into its own system in an orderly manner, and combine them to implement the relevant functions.
[0099] Through the above implementation method, the system functions can be divided into independent and specific minimum business units, which can not only significantly improve the reusability of functions, but also ensure a high degree of consistency of the same functions among various applications. Changes to the minimum business unit will be automatically synchronized to all subscribed applications, eliminating potential inconsistencies and errors caused by manual modification and compilation.
[0100] Furthermore, the direct embedding and combination of the smallest business units significantly reduces the coding and debugging work involved in the development process, helping to shorten the development cycle and achieve rapid prototyping and feature iteration. Using this invention, development teams no longer need to repeatedly write code for similar functions, thus saving significant development costs. It also allows application systems to flexibly select and combine the smallest business units according to different business scenarios, greatly enhancing the flexibility and customizability of business processes. Developers can quickly adjust business logic according to specific needs without building from scratch, greatly improving the system's applicability and scalability.
[0101] Due to the independence of the smallest business unit, system maintenance and upgrades become simpler. When a function needs to be modified or upgraded, only the corresponding smallest business unit needs to be updated, without affecting other functions, thus ensuring the long-term stable operation of the entire system.
[0102] The following is a detailed description with reference to another embodiment.
[0103] Example 2
[0104] The financial business processing device provided in this embodiment includes multiple implementation units, each of which corresponds to a specific implementation step in the above embodiment one. The specific implementation method and beneficial effects can be referred to the foregoing method embodiment, and will not be repeated here.
[0105] Figure 5 This is a schematic diagram of an optional financial transaction processing apparatus according to an embodiment of the present invention, such as... Figure 5 As shown, the financial business processing device may include: a request receiving unit 51, a minimum business unit selection unit 52, a combination unit 53, and an execution unit 54.
[0106] Among them, the request receiving unit 51 is used to receive the business processing request from the calling application and extract the business scenario and multiple business processing processes from the business processing request.
[0107] The minimum business unit selection unit 52 is used to select multiple minimum business units required for each business process based on the business scenario and business process. The minimum business unit includes the smallest executable module with business functions after the system functions are broken down.
[0108] Combination unit 53 is used to arrange and combine all the smallest business units according to the business processing flow to obtain the business development function combination;
[0109] The execution unit 54 is used to embed business development functions into the calling application system, and the calling application system executes each business processing flow.
[0110] The aforementioned financial business processing device can receive business processing requests from the calling application through the request receiving unit 51, and extract business scenarios and multiple business processing flows from the business processing requests. Based on the business scenarios and business processing flows, the minimum business unit selection unit 52 selects multiple minimum business units required for each business processing flow. The minimum business unit includes the minimum executable module with business functions after the system functions are broken down. The combination unit 53 arranges and combines all the minimum business units according to the business processing flow to obtain a business development function combination. The execution unit 54 embeds the business development function combination into the calling application system, and the calling application system executes each business processing flow. In this embodiment, the system functions can be subdivided into independent minimum business units. Each unit encapsulates specific business logic and data processing capabilities to ensure functional consistency. Each calling application system can flexibly select and combine the minimum business units according to the business scenario and embed them into the business process through simple configuration without additional coding and compilation work. This simplifies the construction and adjustment of business logic, breaks the coupling caused by traditional source code copying, and makes the business functions independent entities that can be developed, tested, and deployed. This facilitates code maintenance and solves the technical problem that inconsistencies and difficulties in maintenance often occur when using source code copying strategies for cross-application function sharing during software development.
[0111] Optionally, the financial business processing device further includes: a system function acquisition unit, used to acquire each system sub-function of the target application system before receiving a business processing request from the calling application system; a function decomposition unit, used to decompose the system sub-functions to obtain at least one minimum module including each business function; a module packaging unit, used to package the minimum module into an executable module to form multiple minimum business units; and a registration unit, used to register each minimum business unit to a registration center, whereby the registration center stores the network address of each minimum business unit.
[0112] Optionally, the functional decomposition unit includes: a functional analysis module, used to analyze all system sub-functions and determine functional modules that can operate independently and have clear business boundaries based on the analysis results; an evaluation module, used to evaluate each identified functional module and obtain a module reuse evaluation result, wherein the module reuse evaluation result includes whether the functional module can be reused as the smallest business unit; and a decomposition module, used to decompose the functional modules that can be reused as the smallest business unit based on the module reuse evaluation result into the smallest modules that can implement a business function.
[0113] Optionally, the financial business processing device further includes: a user interface configuration module, used to configure the user interface of the minimum module through a preset code platform or preset code development tool after the system sub-functions are broken down to obtain at least one minimum module including each business capability; a mapping relationship establishment module, used to establish a mapping relationship between the user interface and the business functions implemented by the minimum module; and a module tree addition module, used to add the minimum module to the functional module tree using the user interface, wherein the functional module tree is used to display the business functions corresponding to each minimum module in a tree structure.
[0114] Optionally, the minimum business unit selection unit includes: a linking module, used to link with the target routing gateway corresponding to the calling application; a subscription module, used to subscribe to multiple required minimum business units on the target routing gateway and send the minimum business unit subscription information to the registration center through the target routing gateway; and a minimum business unit acquisition module, used to acquire multiple minimum business units fed back by the registration center through the target routing gateway.
[0115] Optionally, the financial business processing device further includes: a status update unit, used to update the current status of each minimum business unit to an available status through the target routing gateway after obtaining multiple minimum business units fed back by the registration center through the target routing gateway.
[0116] Optionally, the execution unit includes an embedding module for embedding each of the smallest business units in the business development function combination into the calling application system and reusing the business functions of the smallest business units.
[0117] The aforementioned financial business processing device may also include a processor and a memory. The aforementioned request receiving unit 51, minimum business unit selection unit 52, combination unit 53, execution unit 54, etc., are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to realize the corresponding functions.
[0118] The aforementioned processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and software development can be based on the smallest functional units by adjusting kernel parameters.
[0119] The aforementioned memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.
[0120] Example 3
[0121] Embodiments of this application may provide an electronic device. Figure 6 This is a structural block diagram of an electronic device for performing a financial transaction processing method according to an embodiment of this application. Figure 6 As shown, the electronic device may include: one or more ( Figure 6 (Only one is shown) Processor 602, memory 604, memory controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.
[0122] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the financial business processing method and apparatus in this application embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby realizing the aforementioned financial business processing method. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0123] The processor can access information and applications stored in memory via a transmission device to perform the following steps: receiving a business processing request from the calling application and extracting a business scenario and multiple business processing flows from the request; selecting multiple minimum business units required for each business processing flow based on the business scenario and business processing flows, wherein each minimum business unit includes the minimum executable module with business functions after decomposing the system functions; arranging and combining all minimum business units according to the business processing flows to obtain a business development function combination; embedding the business development function combination into the calling application system, and having the calling application system execute each business processing flow.
[0124] Those skilled in the art will understand that Figure 6 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones, tablets, handheld computers, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 6 This does not limit the structure of the aforementioned electronic device. For example, electronic devices may also include components that are more... Figure 6 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 6 The different configurations shown.
[0125] Those skilled in the art will understand that all or part of the steps in the various financial business processing methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0126] Example 4
[0127] Embodiments of this application also provide a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the financial transaction processing method provided in Embodiment 1.
[0128] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located to execute any of the financial business processing methods in the first embodiment described above.
[0129] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.
[0130] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the financial business processing method described in various embodiments of this application.
[0131] This application also provides a computer program product, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the financial business processing method described in various embodiments of this application.
[0132] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0133] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0134] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.
[0135] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0136] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0137] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0138] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.
Claims
1. A financial transaction processing method, characterized in that, include: Receive business processing requests from the calling application, and extract the business scenario and multiple business processing flows from the business processing requests; Based on the business scenario and the business processing flow, select multiple minimum business units required for each business processing flow, wherein the minimum business unit includes the minimum executable module with business functions after the system functions are broken down; According to the business processing flow, all the smallest business units are arranged and combined to obtain the business development function combination. The business development functions are combined and embedded into the calling application system, and the calling application system executes each business processing flow.
2. The method according to claim 1, characterized in that, Before receiving the business processing request from the calling application system, it also includes: Obtain the various system sub-functions of the target application system; The system sub-functions are broken down to obtain at least one minimum module that includes each business function; The minimum module is packaged into an executable module to form multiple minimum business units; Each of the minimum business units is registered to the registration center, which stores the network address of each of the minimum business units.
3. The method according to claim 2, characterized in that, The step of breaking down the system's sub-functions to obtain at least one minimum module comprising each business function includes: All the system sub-functions are analyzed, and based on the analysis results, functional modules that can operate independently and have clear business boundaries are identified. Each identified functional module is evaluated to obtain a module reuse evaluation result, wherein the module reuse evaluation result includes whether the functional module can be reused as a minimum business unit; For functional modules that can be reused as the smallest business unit according to the module reuse evaluation results, the functional modules are decomposed into the smallest modules that can implement a business function.
4. The method according to claim 2, characterized in that, After breaking down the system's sub-functions to obtain at least one minimum module comprising each business capability, the system also includes: Configure the user interface of the minimum module using a preset code platform or preset code development tools; Establish a mapping relationship between the user interface and the business functions implemented by the minimum module; The user interface is used to add the minimum module to the functional module tree, wherein the functional module tree is used to display the business functions corresponding to each minimum module in a tree structure.
5. The method according to claim 1, characterized in that, Based on the business scenario and the business processing flow, the steps for selecting multiple minimum business units required for each business processing flow include: Link the target routing gateway corresponding to the calling application; The target routing gateway subscribes to the required multiple minimum service units and sends the minimum service unit subscription information to the registration center through the target routing gateway; The target routing gateway obtains the multiple smallest business units fed back by the registration center.
6. The method according to claim 5, characterized in that, After obtaining the plurality of minimum service units fed back by the registration center through the target routing gateway, the method further includes: The target routing gateway updates the current status of each of the smallest service units to an available state.
7. The method according to claim 1, characterized in that, The steps of embedding the aforementioned business development functions into the calling application system include: Each of the smallest business units in the business development function combination is embedded into the calling party application system, and the business functions of the smallest business units are reused.
8. A financial transaction processing device, characterized in that, include: The request receiving unit is used to receive the business processing request from the calling application and extract the business scenario and multiple business processing flows from the business processing request. The minimum business unit selection unit is used to select multiple minimum business units required for each business process based on the business scenario and the business process, wherein the minimum business unit includes the minimum executable module with business functions after the system functions are broken down. A combination unit is used to arrange and combine all the smallest business units according to the business processing flow to obtain a business development function combination. The execution unit is used to embed the business development functions into the calling application system, and the calling application system executes each business processing flow.
9. An electronic device, characterized in that, It includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the financial business processing method according to any one of claims 1 to 7.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the financial business processing method according to any one of claims 1 to 7.