Business component management method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a business component management method and device, equipment, a storage medium and a program product, and relates to the field of financial science and technology. The method comprises the following steps: acquiring a to-be-processed service; screening a plurality of target components corresponding to the to-be-processed business from a pre-established component library according to the business process of the to-be-processed business; according to the business process of the to-be-processed business and preset execution logic, the target components are combined, a target business process execution program corresponding to the to-be-processed business is obtained, and the preset execution logic comprises a data flow dependency relationship and an execution sequence between different components. According to the method provided by the invention, the business is abstracted into the components, and the business process meeting the business demand is spliced by flexibly combining the components, so that the development cost of business demand change is reduced, and the online speed of the new business is improved. In addition, due to the fact that the components have reusability, the executable programs corresponding to the requirements can be quickly assembled through the service components, repeated development is not needed, and resource waste is reduced.

Description

Technical Field

[0001] This application relates to the field of financial technology, and more particularly to a business component management method, apparatus, device, storage medium, and program product. Background Technology

[0002] Traditional banking system development typically employs a customized approach, meaning that each new business requirement is developed and deployed independently. When faced with constantly changing business needs, this necessitates writing and testing the relevant business code from scratch.

[0003] Traditional business development processes often require redevelopment for each change in requirements or the launch of new services. This leads to a lengthy cycle from requirements analysis to system deployment, resulting in slow business response times and an inability to meet rapid market changes. Furthermore, the repetitive development of similar business logic in traditional processes wastes resources, increases development costs, and further exacerbates resource waste. Summary of the Invention

[0004] This application provides a business component management method, apparatus, device, storage medium, and product to solve the technical problems of slow development speed and resource waste in existing banking business systems.

[0005] Firstly, this application provides a business component management method, including:

[0006] Get pending business;

[0007] Based on the business process of the business to be processed, select several target components corresponding to the business to be processed from the pre-established component library;

[0008] Based on the business process and preset execution logic of the business to be processed, the target components are combined to obtain the target business process execution program corresponding to the business to be processed. The preset execution logic includes the data flow dependencies and execution order between different components.

[0009] Secondly, this application provides a business component management device, comprising:

[0010] The acquisition module is used to acquire pending business requests.

[0011] The filtering module is used to filter several target components corresponding to the business to be processed from a pre-established component library based on the business process of the business to be processed.

[0012] The splicing module is used to combine target components according to the business process of the business to be processed and the preset execution logic to obtain the target business process execution program corresponding to the business to be processed. The preset execution logic includes the data flow dependencies and execution order between different components.

[0013] Thirdly, this application provides an electronic device, including: a processor and a memory communicatively connected to the processor;

[0014] The memory stores the instructions that the computer executes;

[0015] The processor executes computer-executable instructions stored in memory to implement any of the methods of the first aspect.

[0016] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method of any one of the first aspects.

[0017] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method of any one of the first aspects.

[0018] The business component management method, apparatus, device, storage medium, and program product provided in this application automatically select the components and execution logic corresponding to different business processes. Based on the execution logic, the components are automatically assembled into an executable business process execution program. This abstracts business processes into atomic business components. By flexibly combining these atomic business components, business processes that meet various business needs can be constructed, significantly reducing development costs for changing business requirements and increasing the speed of new business deployment. Furthermore, due to the reusability of business components, when new business needs arise, the corresponding executable program can be quickly assembled using these components, eliminating the need for repeated development and greatly reducing resource waste. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] Figure 1 A schematic diagram illustrating a scenario for developing an existing banking business system;

[0021] Figure 2 A flowchart illustrating a business component management method provided in an embodiment of this application;

[0022] Figure 3 A schematic diagram of the structure of a business component management device provided in an embodiment of this application;

[0023] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0024] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0025] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0026] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation access points for users to choose to authorize or refuse.

[0027] Furthermore, the technical solution involved in this application, which involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.) and the use of artificial intelligence technology for automated decision-making, and makes decisions that have a significant impact on personal rights based on the results of automated decision-making, provides users with corresponding operation entry points for users to choose to agree to or reject the results of automated decision-making; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0028] It should be noted that the business component management method, apparatus, equipment, storage medium and program product provided in this application can be used in the field of financial technology, or in any field other than financial technology. This application does not limit the application field of the business component management method, apparatus, equipment, storage medium and program product.

[0029] The specific application scenario of this application is the development of banking business systems. Existing banking business system development usually adopts a customized approach, that is, independent development and deployment are carried out for each new business requirement. Figure 1 A schematic diagram illustrating a scenario for developing an existing banking business system, such as... Figure 1As shown, the development of banking business systems typically follows a customized process. When new business requirements arise, developers need to start from scratch, writing new business process execution programs based on the description of the new business requirements to implement the corresponding business logic. This usually involves multiple aspects such as adjusting the database structure, writing business logic, and designing the user interface.

[0030] The development of existing banking business systems suffers from the following drawbacks: Customized development: Every time business requirements change or new business functions are added, developers need to write code from scratch, including business logic, database operations, and user interface. Low reusability: Due to the lack of a standardized component management mechanism, similar business logic cannot be reused across businesses or systems, leading to redundant development. High coupling: Business logic is tightly coupled with the system architecture, resulting in poor system scalability and difficulty in adapting to rapidly changing business needs. Long development cycle: From requirements analysis to system deployment, a long time is required, failing to meet the demands of a rapidly changing market.

[0031] The business component management method, apparatus, equipment, storage medium, and program product provided in this application automatically select the components and execution logic corresponding to the business process according to different businesses, and automatically assemble the business components into an executable business process according to the execution logic, aiming to solve the above-mentioned technical problems of the prior art.

[0032] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0033] Figure 2 This is a flowchart illustrating a business component management method provided in an embodiment of this application, such as... Figure 2 As shown, the method includes:

[0034] S201. Obtain pending business.

[0035] In one example, after obtaining the business to be processed, the business process of the business to be processed (such as transfer, account opening, loan application, etc., the specific business process is not limited in this application) is analyzed. The business process of the business to be processed is decomposed into functionally independent business process units with the smallest granularity. Each business process unit has a corresponding component, and each component is responsible for implementing a specific business function.

[0036] S202. Based on the business process of the business to be processed, select several target components corresponding to the business to be processed from the pre-established component library.

[0037] In one example, taking a banking system's transaction workflow as an example, the components may include: a transaction input acquisition component, used to capture raw transaction request data (such as account number, amount, currency, etc.) from the user interface, API (Application Programming Interface), or external systems; a user authentication component, used to call identity authentication services (such as password verification, biometrics, documents, etc.) to verify the user's identity; an account balance query component, used to connect to the core banking system to query the real-time available balance of a specified account; a transaction risk control component, used to apply a preset risk control rule engine (such as anti-fraud models, limit checks, blacklist matching, etc.) to determine transaction risks; a transaction execution component, used to interact with the back-end accounting system to execute actual fund transfers, status updates, and other operations; and a result feedback and display component, used to generate transaction results (success / failure, reference number, balance update, etc.) and format them before returning them to the front-end UI or the caller. The above components are for illustrative purposes only, and their functionality is not limited in this application.

[0038] Optionally, the components include: predefined input and output interfaces, wherein the data format of the input and output interfaces is a structured data format.

[0039] In one example, standardized input and output interfaces are defined for each component. Specifically, the input interface explicitly specifies all data items required for component execution (name, type, format, whether required, etc.; specific data items are not limited in this application). For example, the input for the account balance query component should be account information and currency information. The output interface explicitly specifies all result data items generated after component execution (name, type, format, etc.; specific data items are not limited in this application). For example, the output of the account balance query component is: available balance, currency information, and update time. Both input and output data are defined and constrained using a structured data format.

[0040] By using predefined standardized input / output interfaces, it is easy to connect subsequent components, thus standardizing the input / output methods of components and improving their reusability.

[0041] Optionally, the component encapsulates component logic. The component is used to obtain input data through the input interface, process the input data according to the component logic, obtain output data, and output the output data to the next component through the output interface. The component execution logic includes the business rules, algorithms, or service call logic corresponding to the component.

[0042] In one example, each component is responsible for implementing a specific business function. The component encapsulates its own logic, which may include:

[0043] Get Input: After the component starts, get the input data required by the component from the predefined input interface of the component.

[0044] Business logic processing: The component encapsulates specific business rules, algorithms, or service call logic. For example: Transaction risk control: Calls the rule engine API, inputting transaction data (amount, counterparty, user behavior information, etc.), executes rule calculations, and obtains a risk score and decision result (pass / reject / requires manual review, etc.). Transaction execution: Calls the transaction service interface of the core banking system, inputting necessary accounting instructions, executes deduction / credit operations, and captures execution results and error codes. Specific business logic processing is not limited in this application. Based on the business logic processing, the input data is processed to obtain internal processing results.

[0045] Data processing and transformation: During or after business logic processing, data may need to be cleaned, formatted, encrypted / decrypted, etc., to obtain the final internal processing result. For example, sensitive information entered by some users (such as personally identifiable information, passwords, etc.) needs to be encrypted. Specific operations are not limited in this application.

[0046] Output generation: Based on the internal processing results, convert the internal processing results into output data that conforms to the predefined output interface format.

[0047] Error handling: The component also includes a robust error capture and handling mechanism that returns standardized error messages that conform to a predefined output interface format.

[0048] By creating different components based on the steps corresponding to the business, and for different business rules, algorithms, or service call logic, each component has the corresponding function and can independently execute the business steps. Combined with standardized input and output interfaces, the created components can be assembled to form an executable program corresponding to the business process, thereby improving the speed of new business launch and reducing development costs.

[0049] Optionally, the component also includes feature tags; before obtaining the business to be processed, the method further includes: labeling the component with features and generating feature tags corresponding to the component. The feature tags are used to characterize the component's functional type, applicable scenarios, performance characteristics and data dependencies.

[0050] In one example, the component also includes feature tags for feature recognition and labeling. These feature tags can include: metadata annotation, business rule association, usage behavior analysis, etc. Specifically, the feature tags generated for the component can include:

[0051] During the component creation or deployment phase, metadata is extracted from the component as feature tags. Metadata annotations may include: Functional tags: identity authentication, balance inquiry, transfer execution, result display, data encryption, etc. The specific content of functional tags is not limited in this application. Applicable scenario tags: mobile banking, ATM, cross-border payment, etc. The specific content of applicable scenario tags is not limited in this application. Performance characteristics: high concurrency, low latency, CPU-intensive, IO-intensive, etc. The specific content of performance characteristics is not limited in this application. Data dependency tags: used to indicate the core data source that the component depends on (such as the core account system, risk control system, etc.). The specific content of data dependency tags is not limited in this application.

[0052] Business rule association: The specific business rule ID or type implemented by the associated component (such as large transaction monitoring, etc.). This application does not restrict the specific content of the business rule association.

[0053] Usage behavior analysis: used to record runtime metrics such as the actual call frequency, success rate, and response time of components, and dynamically generate behavior tags such as high frequency of use, high reliability, and high efficiency. This application does not limit the specific content of usage behavior analysis.

[0054] All the above feature label information is stored in the component's metadata database and bound to the component's version, serving as a key input to the intelligent recommendation engine.

[0055] By annotating components with features, corresponding feature labels are generated for each component. The functional type, applicable scenarios, performance characteristics and data dependencies of each component are described, which facilitates the subsequent selection of components that meet business requirements and then splices them into an executable program that meets the business requirements.

[0056] Optionally, before obtaining the business to be processed, the method further includes: determining the component logic of the component according to the preset atomic component design specifications; testing the component, storing the component in the component library after the component passes the test, and reviewing the component; assigning a version number to the component after the component passes the review, and publishing the component with the version number to the component library.

[0057] In one example, a complete component management process is established, including component creation, release, review, and version control. A standardized management process ensures component quality and security, and improves component reusability. Component building can include:

[0058] Component creation and development: In the specified development environment, implement the component logic according to the atomic component design specification (the component design specification may include input / output definitions, interface standards, etc., and this application does not restrict the atomic component design specification), and submit the initial version of the component value component library.

[0059] Component testing and verification: Components undergo unit testing, integration testing, performance testing, and security testing in a test environment. This application does not restrict the testing and verification methods.

[0060] Component review: After a component passes testing, it is submitted to the component library, triggering a component review process, including code quality, security, functional correctness, and tag accuracy. This application does not restrict the specific content of the component review process.

[0061] Component version release: After approval, the component is assigned a version number, which can include major version, minor version, revision number, etc. This application does not restrict the content of the version number. The component and its version number are then released to the component library. Specifically, version control for components can include assigning each component a globally unique version ID, with each version having an independent version number. The component library stores historical versions of components, including the component's code, configuration, input / output definitions, tag metadata, etc. Components can declare dependencies on specific version ranges of other components.

[0062] In another example, components can also be generated with the aid of a large model. By constructing prompts related to business requirements and calling the large model, components can be automatically generated based on those requirements. Components can also include exception pattern recognition at runtime. Through programmatic synthesis techniques, vulnerabilities in the components can be automatically generated to enable self-healing. Relationships between components can also be built using knowledge graphs to intelligently analyze the impact between components. For example, modifying component A might prompt that it affects components B and / or C.

[0063] By generating components and establishing a component library according to component design specifications for different business needs, it is easier to use the components in the component library to assemble the executable program corresponding to the new business needs when developing new businesses, thus improving the reusability of components. By conducting test machine audits on components, the quality and security of components are ensured, thereby improving the usability and security of executable programs.

[0064] Optionally, if a component in an updated version fails, the updated version of the component can be rolled back to the version before the update, based on the component library and the version number of the updated version of the component.

[0065] In one example, the component version number is incremented after the component developer fixes a bug; or the minor version number is incremented when the component developer adds backward compatibility features, a new version is released, triggering a component version update. Specific update options may include: system administrators or workflow orchestration tools can choose to: automatically update to the latest compatible version; manually specify an update to a specific version; or not update. Important updates can be pushed to a subset of traffic or environments for verification first.

[0066] For example, if a problem or failure occurs after a new version of a component is launched, the deployment status of all versions of the component is recorded in the component library, allowing for a quick rollback to the previous stable version of the component.

[0067] By setting a version number for each component, and based on the various versions of components and their version numbers stored in the component library, if an anomaly occurs after a new version component is launched, the version rollback mechanism can be used to revert the abnormal new version component to a historical stable version, further improving the stability of the executable program obtained by splicing components.

[0068] Optionally, the method also includes: marking the component as deprecated or archived after a component fails, and taking the component offline.

[0069] In one example, the decommissioning and archiving of components may include: for obsolete or critically vulnerable versions of components, performing a decommissioning operation and marking the component as deprecated or archived, prohibiting its use in new processes, while historical processes may still retain references.

[0070] By marking faulty components as deprecated or archived and taking them offline, we ensure that all available components in the component library are usable and archive faulty components, thereby improving the security and availability of the executable program obtained by piecing together components.

[0071] Optionally, several target components corresponding to the business to be processed can be selected from a pre-established component library, including: obtaining a set of components related to the business to be processed based on the component's feature tags; scoring and sorting the components in the set; and selecting target components from the set based on the sorting.

[0072] In one example, an intelligent push mechanism is introduced to automatically select appropriate target components for push notifications based on information such as business rules, user behavior data, and real-time transaction data. This mechanism can adjust and optimize business processes in real time, improving business processing efficiency and user experience.

[0073] Specifically, the selection of target components may include: 1) Context information collection: When the business process starts or reaches a decision node, taking the business process as a transaction business process as an example, the following data is collected in real time: business rules, which may include the current transaction type, transaction amount, customer level, channel source, etc.; user behavior data, which may include the user's historical operation habits, current session behavior, etc.; real-time transaction data, such as the specific data of the current transaction request, system load, and risk event triggering status.

[0074] 2) Feature Matching and Component Filtering: Based on the feature tags of components, including their functions, scenarios, data dependencies, performance characteristics, etc., and preset matching rules, preliminary filtering is performed to obtain a set of components related to the business to be processed. Taking a transaction business process as an example, the rule IF (Transaction Type == Transfer) AND (Channel == Mobile Banking) AND (Amount > 50,000) THEN must include an enhanced authentication component.

[0075] This paper utilizes a component recommendation model, based on content, to score and rank components in a pre-selected set of components relevant to the business to be processed. Target components are then selected from this set based on the ranking. The component recommendation model considers factors including: the semantic matching degree between component tags and the current context; the success rate and performance (response time) of component calls under similar historical contexts; the current user's personalized preferences, such as frequently used components; historical composition relationships between components, such as which components are frequently called together; and real-time system status, such as prioritizing lightweight components under high load. The specific factors considered by the machine learning model are not limited in this application.

[0076] In another example, not only can individual target components be recommended, but also combinations of target components that meet current business needs and have been validated or predicted to be effective can be recommended. For example, for "large mobile banking transfers," the following combination might be recommended: [Get input -> Enhanced authentication (e.g., facial recognition) -> Balance / limit inquiry -> Real-time risk control check -> Transfer execution -> Result display]. The above combination is only used as an example in this application, and the specific combination method is not limited in this application.

[0077] By using the feature tags of the components, a collection of different types of components related to the business is obtained. The target components that are closest to the business needs are selected from the collection by scoring and sorting. The selected target components are then used for subsequent splicing, so that the spliced ​​executable program is closer to the business needs, further improving the user experience.

[0078] S203. Based on the business process and preset execution logic of the business to be processed, combine the target components to obtain the target business process execution program corresponding to the business to be processed.

[0079] In this embodiment of the application, the preset execution logic includes the data flow dependencies and execution order between different components.

[0080] Optionally, the preset execution logic also includes a component combination template corresponding to the business to be processed, which contains the component combination rules of the business; according to the business process of the business to be processed and the preset execution logic, the target components are combined to obtain the target business process execution program corresponding to the business to be processed, including: according to the component combination template, combined with the data flow dependency relationship and execution order between the target components, the input data and output data between different target components are concatenated to obtain the target business process execution program corresponding to the business to be processed.

[0081] In one example, based on the business process and preset execution logic of the business to be processed, target components are combined to obtain the target business process execution program corresponding to the business to be processed. This can automate and intelligentize banking business processes, improving business processing efficiency and service quality. At the same time, by managing and sharing components in a unified manner, the reusability of components can be greatly improved, thereby reducing business development and maintenance costs.

[0082] Specifically, combining target components can include: the system pushing recommended target components, and / or combinations of target components, along with component combination templates corresponding to the business to be processed, to the workflow orchestration engine. The workflow orchestration engine instantiates the target components, and / or combinations of target components, and executes them sequentially, including: starting the first target component and inputting initial data into it; passing standardized output data from upstream target components as input data to downstream target components; managing data flow dependencies between target components to ensure data is delivered to the correct component at the right time; and monitoring component execution status in real time and handling component exceptions and timeouts.

[0083] In another example, a feedback and optimization process is also included, which records data such as the context of each smart push to the target component, the recommendation results, and the actual execution effect (including success rate, time consumption, etc.). This recorded data can be used to periodically retrain the component recommendation model and continuously optimize the accuracy of the component recommendation model.

[0084] By using component composition templates, components are combined with the input and output data of different target components according to the data flow dependencies and execution order of the target components to obtain the executable program corresponding to the business process. This realizes dynamic component composition, eliminating the need for manual component assembly and further improving the speed of new business launch and the efficiency of new business development.

[0085] The business component management method provided in this embodiment automatically selects the components and execution logic corresponding to different business processes, and automatically assembles the business components into an executable business process execution program based on the execution logic. This abstracts business processes into atomic business components. By flexibly combining these atomic business components, business processes that meet various business needs can be assembled, greatly reducing the development cost of changing business requirements and improving the speed of launching new businesses. At the same time, because business components are reusable, when new business needs arise, the corresponding executable program can be quickly assembled using business components without repeated development, greatly reducing resource waste.

[0086] Figure 3 This is a schematic diagram of the structure of a business component management device provided in an embodiment of this application, such as... Figure 3 As shown, the business component management device 30 provided in this embodiment includes:

[0087] Module 301 is used to acquire pending business data.

[0088] The filtering module 302 is used to filter several target components corresponding to the business to be processed from a pre-established component library according to the business process of the business to be processed.

[0089] The splicing module 303 is used to combine target components according to the business process of the business to be processed and the preset execution logic to obtain the target business process execution program corresponding to the business to be processed. The preset execution logic includes the data flow dependencies and execution order between different components.

[0090] In one possible implementation, the component includes: predefined input and output interfaces, wherein the data format of the input and output interfaces is a structured data format.

[0091] In one possible implementation, the component encapsulates component logic. The component is used to obtain input data through an input interface, process the input data according to the component logic, obtain output data, and output the output data to the next component through an output interface. The component execution logic includes the business rules, algorithms, or service call logic corresponding to the component.

[0092] In one possible implementation, the component also includes feature tags; the business component management device is further specifically used to: annotate the component with features and generate feature tags corresponding to the component, the feature tags being used to characterize the component's functional type, applicable scenarios, performance characteristics, and data dependencies.

[0093] In one possible implementation, the filtering module 302 is specifically used to: obtain a set of components related to the business to be processed based on the feature tags of the components; score and sort the components in the set; and filter the target components from the set based on the sorting.

[0094] In one possible implementation, the preset execution logic also includes a component combination template corresponding to the business to be processed. The component combination template contains the component combination rules of the business. The splicing module 303 is specifically used to: according to the component combination template, combined with the data flow dependency relationship and execution order between the target components, splice the input data and output data between different target components to obtain the target business process execution program corresponding to the business to be processed.

[0095] In one possible implementation, the business component management device is further specifically used to: determine the component logic of the component according to the preset atomic component design specifications; test the component, and after the component passes the test, store the component in the component library and review the component; after the component passes the review, assign a version number to the component and publish the component with the version number to the component library.

[0096] In one possible implementation, the business component management device is also specifically used to: when a component in an updated version fails, roll back the updated version of the component to the version before the update, based on the component library and the version number of the updated version of the component.

[0097] In one possible implementation, the business component management device is also specifically used to: mark the component as deprecated or archived after a component fails, and take the component offline.

[0098] The business component management device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0099] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 4 As shown, the electronic device 40 may include a memory 401 and a processor 402. Optionally, the electronic device may also include a transceiver 403, wherein the memory 401 and the processor 402 communicate with each other; for example, the memory 401, the processor 402 and the transceiver 403 may communicate via a communication bus 404, the memory 401 is used to store a computer program, and the processor 402 executes the computer program to implement the method of the above embodiments.

[0100] Optionally, the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps in the method embodiments disclosed in this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0101] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the methods in any of the above method embodiments.

[0102] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods in any of the above method embodiments.

[0103] All or part of the steps in the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0104] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0105] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0106] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0107] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

[0108] In this application, the term "comprising" and its variations can refer to non-limiting inclusion; the term "or" and its variations can refer to "and / or". The terms "first", "second", etc., in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0109] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0110] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0111] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0112] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0113] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0114] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, 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 memory 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 of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0115] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0116] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0117] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A business component management method, characterized in that, The method includes: Get pending business; Based on the business process of the business to be processed, select several target components corresponding to the business to be processed from the pre-established component library; Based on the business process and preset execution logic of the business to be processed, the target components are combined to obtain the target business process execution program corresponding to the business to be processed. The preset execution logic includes the data flow dependencies and execution order between different components.

2. The method according to claim 1, characterized in that, The component includes: a predefined input interface and an output interface, wherein the data format of the input interface and the output interface is a structured data format.

3. The method according to claim 2, characterized in that, The component encapsulates component logic. The component is used to obtain input data through the input interface, process the input data according to the component logic to obtain output data, and output the output data to the next component through the output interface. The component execution logic includes the business rules, algorithms or service call logic corresponding to the component.

4. The method according to claim 1, characterized in that, The component also includes feature tags; Prior to acquiring the pending service, the method further includes: The components are labeled with features to generate feature tags corresponding to the components. The feature tags are used to characterize the functional type, applicable scenarios, performance characteristics and data dependencies of the components.

5. The method according to claim 4, characterized in that, The step of selecting several target components corresponding to the business to be processed from a pre-established component library includes: Based on the feature tags of the components, obtain a set of components related to the business to be processed; The components in the set are scored and sorted, and the target component is selected from the set based on the sorting.

6. The method according to claim 1, characterized in that, The preset execution logic also includes a component combination template corresponding to the business to be processed, and the component combination template contains the component combination rules of the business; The step of combining the target components according to the business process and preset execution logic of the pending business to obtain the target business process execution program corresponding to the pending business includes: Based on the component combination template, and combined with the data flow dependencies and execution order between the target components, the input and output data between different target components are concatenated to obtain the target business process execution program corresponding to the business to be processed.

7. The method according to claim 1, characterized in that, Prior to acquiring the pending service, the method further includes: The component logic of the component is determined according to the preset atomic component design specifications; The component is tested, and after the component passes the test, it is stored in the component library and reviewed. After the component passes the review, a version number is assigned to the component, and the component with the version number is published to the component library.

8. The method according to claim 7, characterized in that, When a component in an updated version fails, the updated version of the component is rolled back to the version before the update, based on the component library and the version number of the updated version of the component.

9. The method according to claim 7, characterized in that, The method further includes: After a component malfunctions, the component is marked as deprecated or archived and taken offline.

10. A business component management device, characterized in that, The device includes: The acquisition module is used to acquire pending business requests. The filtering module is used to filter several target components corresponding to the business to be processed from a pre-established component library according to the business process of the business to be processed. The splicing module is used to combine the target components according to the business process of the business to be processed and the preset execution logic to obtain the target business process execution program corresponding to the business to be processed. The preset execution logic includes the data flow dependencies and execution order between different components.

11. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 9.

13. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 9.

Images