Business system generation method and device, electronic equipment and storage medium

Abstract

The invention discloses a service system generation method and device, electronic equipment and a storage medium, the service system generation method can be applied to the technical field of computers, and the method comprises the following steps: in response to a service creation request sent by a user terminal, obtaining a target service identifier; determining a candidate service node matched with the target service identifier in the preset service nodes, and generating a matching result based on the service identifier of the candidate service node; the matching result is returned to the user terminal, so that the user terminal selects target service nodes based on the service identifiers of the candidate service nodes in the matching result, and node configuration information of the target service nodes and interaction logic among the target service nodes are returned; configuring a target service node based on the node configuration information; and based on the configured target service nodes and the interaction logic among the target service nodes, establishing a service process, and generating a target service system. According to the invention, the repeated development work is reduced, and the expansibility and maintainability of the service system are enhanced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and particularly to a method, apparatus, electronic device, and storage medium for generating a business system. Background Art

[0002] With the rapid development of information technology and the increasingly fierce market competition, enterprises are facing constantly changing business scenarios and customer needs. To maintain competitiveness, enterprises need to be able to quickly respond to market changes and flexibly adjust business strategies and service contents. However, in this context, the traditional business development model has become a bottleneck restricting the agility of enterprises.

[0003] In the traditional business development environment, there are generally problems such as long development cycles and insufficient adaptability. These bottlenecks limit the ability of enterprises to quickly respond to rapidly changing market conditions and customer needs. Whenever new services need to be deployed or existing processes need to be optimized, enterprises must invest significant resources in software customization development and system integration work. This model not only raises the operating costs but also may affect the timely launch of new businesses due to the lag in development progress. In addition, there are also many challenges in maintaining traditional business systems. Due to the tight coupling between different functional modules, the entire architecture lacks elasticity and flexibility, increasing the complexity of later maintenance and the risk of system upgrades. Summary of the Invention

[0004] To solve the problems of the prior art, embodiments of this application provide a method, apparatus, electronic device, and storage medium for generating a business system. The technical solutions are as follows:

[0005] On the one hand, a method for generating a business system is provided, and the method includes:

[0006] Respond to a business creation request sent by a user terminal, and obtain a target business identifier;

[0007] Determine a candidate business node that matches the target business identifier in a preset business node, and generate a matching result based on the business identifier of the candidate business node; the preset business node includes multiple business nodes and the business identifier corresponding to each business node; each business node is configured to perform different business operations;

[0008] Return the matching result to the user terminal, so that the user terminal selects a target business node based on the business identifier of the candidate business node in the matching result, returns the node configuration information of the target business node, and the interaction logic between each target business node;

[0009] Configure the target business node based on the node configuration information;

[0010] Based on the configured target service nodes and the interaction logic between each of the target service nodes, a service process is built to generate a target service system.

[0011] On the other hand, a device for generating a service system is provided. The device includes:

[0012] An identifier acquisition module, configured to acquire a target service identifier in response to a service creation request sent by a user terminal;

[0013] A candidate matching module, configured to determine candidate service nodes that match the target service identifier in preset service nodes, and generate a matching result based on the service identifiers of the candidate service nodes; the preset service nodes include a plurality of service nodes and the service identifier corresponding to each service node; each of the service nodes is configured to perform different service operations;

[0014] A target return module, configured to return the matching result to the user terminal, so that the user terminal selects target service nodes based on the service identifiers of the candidate service nodes in the matching result, returns the node configuration information of the target service nodes, and the interaction logic between each of the target service nodes;

[0015] A node configuration module, configured to configure the target service nodes based on the node configuration information;

[0016] A process building module, configured to build a service process based on the configured target service nodes and the interaction logic between each of the target service nodes, and generate a target service system.

[0017] In an exemplary embodiment, the candidate matching module includes:

[0018] A first identifier parsing module, configured to parse the target service identifier to obtain a first-level identifier and a second-level identifier under the first-level identifier;

[0019] A general screening module, configured to screen out service general nodes that match the first-level identifier in the preset service nodes;

[0020] A directional screening module, configured to screen out service directional nodes that match the second-level identifier in the preset service nodes;

[0021] A first candidate determination module, configured to determine the service general nodes and the service directional nodes as the candidate service nodes.

[0022] In an exemplary embodiment, the first identifier parsing module includes:

[0023] The second identification parsing module is configured to parse the target service identification to obtain the first-level identification, the second-level identification, and the customization identification;

[0024] Correspondingly, the first candidate determination module includes:

[0025] The customization screening module is configured to screen out service customization nodes that match the customization identification from the preset service nodes;

[0026] The second candidate determination module is configured to determine the service general node, the service directed node, and the service customization node as the candidate service nodes.

[0027] In an exemplary embodiment, the service node is online-bound to the service rule corresponding to the corresponding service operation; the node configuration module includes:

[0028] The information correction module is configured to correct the node configuration information based on the service rule corresponding to the target service node when there is a conflict between the node configuration information and the service rule corresponding to the target service node;

[0029] The corrected configuration module is configured to configure the target service node based on the corrected node configuration information.

[0030] In an exemplary embodiment, the apparatus further includes a rule update module for automatically updating the service node and the service system when the service rule is updated. The rule update module includes:

[0031] The configuration update module is configured to, in response to an update of the service rule corresponding to any service node in the preset service nodes, perform configuration update on the service node based on the updated service rule;

[0032] The first system update module is configured to update the target service system based on the target service node with the updated configuration.

[0033] In an exemplary embodiment, the identification acquisition module includes:

[0034] The identification selection module is configured to, in response to the service creation request sent by the user terminal, send a preset service identification to the user terminal so that the user terminal selects the target service identification from the preset service identifications.

[0035] In an exemplary embodiment, the apparatus further includes an adjustment request module for adjusting the service node and updating the service system when the user requests to adjust the service system. The adjustment request module includes:

[0036] An adjustment information module, configured to obtain adjustment information in response to an adjustment request for the target service system sent by the user terminal;

[0037] A node adjustment module, configured to adjust the target service node and the interaction logic between the target service nodes based on the adjustment information;

[0038] A second system update module, configured to update the target service system based on the adjusted target service node and the adjusted interaction logic.

[0039] On the other hand, an electronic device is provided, including a processor and a memory. At least one instruction or at least one program segment is stored in the memory, and the at least one instruction or the at least one program segment is loaded and executed by the processor to implement the generation method of the service system in any of the above aspects.

[0040] On the other hand, a computer-readable storage medium is provided. At least one instruction or at least one program segment is stored in the computer-readable storage medium, and the at least one instruction or the at least one program segment is loaded and executed by a processor to implement the generation method of the service system as described in any of the above aspects.

[0041] On the other hand, a computer program product or a computer program is provided. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the generation method of the service system in any of the above aspects.

[0042] In the embodiments of the present application, by responding to a service creation request, obtaining a target service identifier, screening out matching candidate service nodes from a preset service node library, and allowing a user to select and configure the target service nodes and their interaction logic according to specific requirements, a target service system is generated. This way of building a service process based on componentization and configuration not only reduces repetitive development work and operation costs, but also realizes low coupling and high reuse of service modules, enhances the scalability and maintainability of the service system, and thus can quickly respond to market changes and customer needs, accelerating the launch of new services; the user-participatory dynamic configuration method has flexibility and user-friendliness. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0044] Figure 1 It is a schematic flowchart of a method for processing a service creation request provided by an embodiment of the present application;

[0045] Figure 2 It is a schematic flowchart of a method for generating a service system provided by an embodiment of the present application;

[0046] Figure 3 It is a schematic structural diagram of an architecture for building a service process provided by an embodiment of the present application;

[0047] Figure 4 It is a schematic diagram of a service identifier encoding provided by an embodiment of the present application;

[0048] Figure 5 It is a schematic diagram of a service process provided by an embodiment of the present application;

[0049] Figure 6 It is a block diagram of the structure of a service system generation device provided by an embodiment of the present application;

[0050] Figure 7 It is a block diagram of the hardware structure of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0051] Next, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0052] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or server that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0053] It is understandable that in the specific embodiments of the present application, data related to user information and the like are involved. When the above embodiments of the present application are applied to specific products or technologies, user permission or consent needs to be obtained, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards in relevant countries and regions.

[0054] Please refer to Figure 1 , which shows a schematic flowchart of a method for processing a service creation request provided by an embodiment of the present application. Among them, the product center is responsible for product management, configuration management, service control, and process orchestration. Product management refers to defining and managing product information, including product attributes, service standards, etc. Configuration management refers to configuring product parameters according to business requirements to ensure that the product can meet specific business scenarios. Service control refers to monitoring and managing the execution of business processes to ensure business compliance and efficiency. Process orchestration means that through a visual interface, business personnel can drag and combine business nodes to orchestrate business processes. Among them, the product service standard interface serves as a unified entry for service creation requests, receives service creation requests (PRODUCT_CODE) from user terminals, and according to the service creation requests, calls corresponding product services to trigger the execution of business processes. The business orchestration engine or execution engine is responsible for the execution control of business processes. According to the configuration and interaction logic of business nodes, it intelligently determines the execution order of nodes, supports parallel execution and serial execution, and ensures the accuracy and integrity of business processes. The business node library stores a large number of independent and reusable business nodes, covering common operations and logics in target services, such as payment verification, exchange rate conversion, fund distribution, etc. in payment services. When modeling new services, appropriate business nodes can be directly selected from the business node library for combination and orchestration. The order center is used for comprehensive management of documents, uniformly maintaining business documents, including functions such as order creation, modification, query, and status tracking, to ensure the consistency and integrity of business data, and to facilitate business personnel and management personnel to monitor and manage business processes.

[0055] Specifically, the construction of the business node library is based on a comprehensive and in-depth business analysis of common business scenarios to understand business requirements, business processes, and involved business rules. Then, model the business process, break down the complex business process into independent and reusable business node units, and store these nodes in the business node library to form rich business node resources. When a new business is connected, the user terminal sends a business creation request, enters the system through the product service standard entrance. The product service calls the execution engine according to the received business creation request to conduct business analysis and modeling again. Then, select appropriate nodes from the business node library according to the user and perform combined coding to quickly construct a business process that meets the new business requirements and achieve the rapid launch of the business. At the same time, this system provides a friendly visual management interface. Business personnel can support the new business through simple page operations, such as drag-and-drop node combination, parameter setting, etc. Business nodes collaborate through standardized interfaces and data interaction specifications to ensure the smooth execution of the business process. During the execution of the business process, the order center records and updates business document information in real time, facilitating business personnel and management personnel to query and monitor the business status at any time. When business requirements change, the business orchestration engine has strong dynamic adjustment capabilities. Business personnel can directly modify the orchestrated business process on the visual interface, such as adding new business nodes to meet new regulatory requirements, deleting or replacing inapplicable business nodes, etc.

[0056] Please refer to Figure 2 , which shows a schematic flowchart of a method for generating a business system provided by an embodiment of the present application. It should be noted that this specification provides method operation steps such as in the embodiment or flowchart, but based on routine or non-creative labor, there may be more or fewer operation steps. The step order listed in the embodiment is only one way among the execution orders of numerous steps and does not represent the only execution order. When the actual system or product is executed, it can be executed in the order shown in the embodiment or the drawing or executed in parallel (for example, in an environment with parallel processors or multi-threaded processing). Specifically, as Figure 2 shown, the method may include:

[0057] S201, in response to a business creation request sent by a user terminal, obtain a target business identifier.

[0058] Among them, the user terminal refers to the device operated by the user, such as a computer, mobile phone, or other intelligent devices.

[0059] Among them, the business creation request is an instruction sent by the user terminal, indicating that the user hopes to create a new business system or business process.

[0060] Among them, the target service identifier is the unique identifier of the service requirement specified by the user, and is used to describe the service type or function that the user expects to create.

[0061] In an exemplary embodiment, the above step S201 may include the following steps:

[0062] In response to a service creation request sent by the user terminal, send a preset service identifier to the user terminal, so that the user terminal can select a target service identifier from the preset service identifiers.

[0063] Among them, the preset service identifier refers to a set of identifiers of predefined service types or function modules, and is used to describe the service scope supported by the system.

[0064] Among them, the target service identifier refers to the identifier of the specific service type or function module selected by the user from the preset service identifiers, and is used to clarify the user's requirements.

[0065] Specifically, the business personnel select a suitable service identifier at the product service standard entry according to the service requirement, and the system automatically invokes the service orchestration engine. As Figure 3 shown, the unified service interface for service access uses a distributed service framework such as dubbo to ensure that the upstream service party can access the system standardized through this interface. The design of this unified interface reduces the technical threshold and complexity of service access, enabling different business lines to interact with the system conveniently. By specifying different service identifiers, the system can automatically identify the service type and intelligently route to the corresponding service process. The service identifier, as the key identifier of the service creation request, ensures that the system can quickly and accurately match the correct service processing logic and realize the automatic guidance of the service process. Through the automated and standardized service access process, the system significantly reduces the service access failure rate caused by human operation errors.

[0066] It can be seen from the above technical solutions of the embodiments of the present application that by displaying the preset service identifier to the user when the user terminal sends a service creation request, the embodiments of the present application enable the user to intuitively select the required service type. This mechanism not only improves the friendliness of user interaction, but also ensures the accurate matching between user requirements and system functions. By presetting the service identifier, the user is guided to select the appropriate service module, thereby simplifying the service creation process and enhancing the user experience.

[0067] S203. Determine a candidate service node that matches the target service identifier in the preset service nodes, and generate a matching result based on the service identifier of the candidate service node.

[0068] Among them, the preset business nodes include multiple business nodes and the business identifiers corresponding to each business node, and each business node is configured to perform different business operations. Specifically, the preset business nodes are a set of predefined and reusable business function modules, and each business node has a unique business identifier for performing specific business operations.

[0069] Among them, the candidate business nodes refer to the nodes filtered from the preset business nodes that match the target business identifier for the user to select.

[0070] Specifically, based on the received target business identifier, the business orchestration engine selects the matching business nodes from the business node library. During the business modeling process, each business node is assigned specific functions and attribute labels, and the engine accurately filters out the relevant business node set by parsing the business requirements corresponding to the product code and using this label information. For example, for a business identifier of cross-border e-commerce payment, the engine can quickly locate the relevant business nodes including order processing, material verification, fund distribution, etc.

[0071] In specific implementation, the preset business nodes are stored and maintained in the form of a business node library. The establishment and maintenance of the business node library promote the reuse of business modules, reduce repetitive development work, improve the utilization rate of development resources, and lower development costs. Specifically, the business node library stores a large number of independent and reusable business nodes disassembled during business modeling. These nodes cover common business operations and logics in the target business, such as payment verification, exchange rate conversion, and fund distribution in the cross-border payment field. When building a new business model, appropriate business nodes can be directly selected from the business node library for combination and orchestration, reducing repetitive development work. The business node library is designed to achieve a high degree of business decoupling. Each node collaborates through standardized interfaces and data interaction specifications, enabling the development, maintenance, and upgrade of different nodes to be independent of each other. This feature allows different developers to work on different nodes simultaneously, significantly improving development efficiency. The development of nodes follows a simple and efficient standard template method. Developers only need to implement key business methods such as forward business processing, rollback operations, and asynchronous result processing according to this template to quickly create new business nodes. For example, in the development of a payment processing node, developers can complete the development of a reusable payment processing node and easily integrate it into the business node library by implementing the forward process of payment initiation, the fund rollback logic in case of payment failure, and the processing method for asynchronous notification of payment results according to the template. Through different combination methods, the nodes in the business node library can generally meet the construction requirements of the vast majority of new business products. When facing some more personalized business products, only a small number of specific nodes need to be supplemented for development, or existing nodes can be inherited and appropriately modified to implement special customized nodes, effectively meeting personalized business needs. For example, in cross-border payment business, for common collection business, the basic collection business process can be constructed by combining and orchestrating general nodes such as review nodes, risk control assessment nodes, and accounting processing nodes. For some personalized collection business with additional risk assessment requirements, the general risk assessment node can be inherited, its internal parameters or logics can be modified, or new nodes specifically for special requirements can be developed, such as compliance review nodes for specific regions. Then, by combining these nodes with existing general nodes, the development and launch of customized business products can be quickly realized, fully reflecting the high reusability of business nodes and greatly reducing repetitive labor and development costs in the process of new business development.

[0072] Specifically, a business node library is built through business analysis and modeling. Specifically, through in-depth analysis of the target business together, including aspects such as business processes and business rules. According to the analysis results, the key links of the business and reusable business logic units are determined to build a business model. For example, in the cross-border remittance business, links such as remittance applications, compliance reviews, exchange services, and fund distribution can be modeled as independent business nodes. The modeled business nodes are stored in the business node library according to certain classifications and specifications, providing basic resources for subsequent business orchestration.

[0073] In an exemplary embodiment, step S203 above may include the following steps:

[0074] Parse the target business identifier to obtain a first-level identifier and second-level identifiers under the first-level identifier;

[0075] Filter out business general nodes that match the first-level identifier from the preset business nodes;

[0076] Filter out business directed nodes that match the second-level identifier from the preset business nodes;

[0077] Determine the business general nodes and business directed nodes as candidate business nodes.

[0078] Among them, the target business identifier is the unique identifier of the business requirements specified by the user, usually a composite identifier containing multi-level information for accurately describing the business requirements.

[0079] Among them, the first-level identifier is the top-level classification information in the target business identifier, used to identify the major category or general function of the business.

[0080] Among them, the second-level identifier is the sub-classification information under the first-level identifier in the target business identifier, used to further refine the business requirements and describe specific business functions or scenarios.

[0081] Among them, the business general node is a node in the preset business node library that matches the first-level identifier, usually representing a general business function module.

[0082] Among them, the business directed node is a node in the preset business node library that matches the second-level identifier, usually representing a dedicated function module for a specific business scenario or requirement.

[0083] Among them, the candidate business nodes are a set of business general nodes and business directed nodes that match the target business identifier after screening, for the user to select.

[0084] Specifically, when parsing the target service identifier, a customization identifier may also be obtained. Correspondingly, service customization nodes that match the customization identifier are filtered out from the preset service nodes. It is determined that the service general nodes, service targeted nodes, and service customization nodes are candidate service nodes. Herein, the customization identifier is a personalized identifier added by the user according to specific requirements, used to describe unique functions or specific requirements in service needs. The service customization node is a node in the preset service node library that matches the customization identifier, usually representing a personalized function module designed to meet specific user needs. Correspondingly, the candidate service nodes refer to the set of service general nodes, service targeted nodes, and service customization nodes that match the target service identifier after screening, for the user to select. The introduction of the customization identifier supports highly personalized service needs and further enhances the flexibility and adaptability of the system.

[0085] Exemplarily, assume that the user hopes to create an e-commerce order processing system. The service general nodes are: order reception, order verification. The service targeted nodes are: inventory check, payment processing. The service customization node is: logistics distribution (for specific logistics needs).

[0086] Specifically, as Figure 4 shown, the product center is mainly responsible for the encoding of service identifiers after service modeling, as well as functions such as product maintenance, configuration maintenance, and service authorization. The service identifier is constructed through a three-level encoding system, including but not limited to the first-level identifier, the second-level identifier, and the customization identifier. The first-level encoding is used to define the major categories of services, representing different service areas or service types. The second-level encoding further refines on the basis of the first-level encoding to define specific standard service products. For example, "100" in the figure represents "financial services", and "001" represents "payment processing" under "financial services". The second-level encoding ensures the standardization and modularity of service products under the major category, facilitating management and expansion. The third-level encoding is customized for specific customer needs, representing personalized service products or services. The third-level encoding allows customization on the basis of standard service products to meet specific customer needs. For example, a collection product customized for a large enterprise with special handling fee discounts can be identified and managed through a specific third-level encoding (such as "000" in the figure).

[0087] It can be seen from the above technical solutions of the embodiments of the present application that by parsing the multi-level structure of the target service identifier, the embodiments of the present application can more accurately filter out service nodes that meet user needs from the preset service node library. This hierarchical parsing and filtering method not only improves the accuracy of matching, but also enhances the flexibility and scalability of the service system. By classifying service nodes into general nodes, targeted nodes, and customization nodes, it is possible to better balance generality, pertinence, and personalized needs.

[0088] S205. Return the matching results to the user terminal so that the user terminal selects a target service node based on the service identifiers of the candidate service nodes in the matching results, and returns the node configuration information of the target service node and the interaction logic between the target service nodes.

[0089] Among them, the node configuration information describes the specific parameters and settings of the target service node and is used to determine the behavior and functions of the node.

[0090] Among them, the interaction logic defines how the target service nodes cooperate, including data flow direction, execution order, etc.

[0091] Exemplarily, configure the maximum order quantity for the order receiving node, configure the payment method and handling fee for the payment processing node, and define the interaction logic as: order receiving → inventory check → payment processing → logistics distribution.

[0092] For the application of the target business system in different regions, different regions' business requirements can be quickly adapted by adding service nodes such as language support and exchange rate conversion.

[0093] Specifically, the service orchestration engine filters out relevant service nodes from the service node library according to the target service identifier and displays them on the visual orchestration interface. Business personnel can perform operations such as simple dragging, connecting, and combining on the service nodes to combine and orchestrate the service nodes, set node parameters, and build a personalized business process that meets business requirements.

[0094] S207. Configure the target service node based on the node configuration information.

[0095] In an exemplary implementation, the service node is online-bound to the service rules corresponding to the corresponding service operation; the above step S207 may include the following steps:

[0096] In the case of a conflict between the node configuration information and the service rules corresponding to the target service node, correct the node configuration information based on the service rules corresponding to the target service node;

[0097] Configure the target service node based on the corrected node configuration information.

[0098] Among them, the service node is a preset and reusable functional module in the service system, used to execute specific service operations.

[0099] Among them, the service rules define the logic, constraints, or operation specifications that must be followed when the service node runs. For example, the service rules of the payment node may include payment amount limits, supported payment methods, etc.

[0100] Among them, online binding refers to the dynamic association relationship between business nodes and business rules, that is, business rules can be loaded and updated at runtime without redeploying business nodes.

[0101] Among them, conflict refers to the situation where node configuration information is inconsistent with business rules, which may lead to business logic errors or non-compliance with regulatory requirements.

[0102] As can be seen from the above technical solutions of the embodiments of the present application, through the online binding of business nodes and business rules, the embodiments of the present application can dynamically load and update business rules without redeploying or modifying the code. When there is a conflict between node configuration information and business rules, the node configuration information is automatically corrected according to the business rules to ensure the correctness and compliance of business logic. This mechanism not only improves the flexibility of business system generation but also enhances stability and reliability.

[0103] S209. Based on the configured target business nodes and the interaction logic between the target business nodes, build a business process to generate a target business system.

[0104] Among them, the target business system is the final business system built according to the business nodes selected by the user, their configuration information, and interaction logic, and is composed of multiple configured business nodes for executing specific business processes.

[0105] Specifically, as Figure 3 shown, the business process orchestration engine is responsible for dynamically orchestrating and executing business processes. The orchestration engine can flexibly combine different business nodes, such as product centers, payers and payees, trade materials, etc., to support diverse business scenarios. Each functional module in the system (such as the order center, commission service, risk control service, etc.) serves as an independent business node and is called and combined through the business process orchestration engine. This modular design improves the flexibility and scalability of the system, enabling new businesses to go live quickly and simplifying the maintenance and adjustment of existing businesses. The system supports global distribution services, which can distribute business creation requests to different service nodes to achieve high availability and load balancing of the business. This distribution mechanism improves the concurrent processing ability of the system and ensures the continuity and stability of the business.

[0106] Specifically, the business orchestration engine is equipped with a powerful orchestration rule parser that can convert the business process logic built by business personnel on the visual interface into executable computer code logic. For example, when building a complex cross-border B2B (Business-to-Business) supplier payment business process, business personnel can connect and configure nodes such as "order review node", "declaration material assembly node", "risk assessment node", "handling fee calculation node", "fund distribution node", etc. in the order of business logic, and the engine will automatically generate the corresponding code logic to ensure the smooth execution of the business process.

[0107] In specific implementation, after generating the target business system, the business process is tested and verified to ensure the correctness and stability of the business logic. After passing the test, the target business system can be put into operation online to achieve rapid business deployment.

[0108] During the execution of the business process, the business orchestration engine has powerful execution control capabilities and can intelligently determine the execution order of nodes based on the characteristics of business nodes and business logic requirements. For business nodes that are independent of each other and have no data dependencies, the engine can drive them to execute in parallel, making full use of system resources and significantly improving the business processing efficiency; for nodes with data dependencies or logical sequence, they are executed serially in strict accordance with the set order to ensure the accuracy and integrity of the business process. For example, in the cross-border B2B supplier payment process, the risk assessment node and the handling fee calculation node can be executed in parallel, while the order review node and the fund distribution node need to be executed serially.

[0109] Furthermore, as Figure 5 shown, the orchestration rule parser inside the business orchestration engine can not only convert the business process logic built on the visual interface into executable computer code logic, but also handle complex business processes, including multi-node concurrent execution and failure reverse rollback. The parser supports multi-node concurrent execution and can promote the execution of multiple business nodes simultaneously to improve the execution efficiency of the business process. The orchestration engine advances the execution of each node according to the forward logic of the business process. The orchestration engine can flexibly handle errors during the execution process and supports custom error handling logic and rollback strategies. If any node fails during the execution of the business process, the orchestration engine supports the rollback of the executed link.

[0110] As can be seen from the above technical solutions of the embodiments of the present application, the embodiments of the present application can quickly generate and adjust business systems through modular and configurable methods. Through a preset business node library, business nodes can be dynamically matched and combined according to user requirements, thereby reducing repetitive development work, significantly shortening the development cycle, and improving development efficiency; the modular design of business nodes makes system maintenance simpler, and the update of a single node will not affect the operation of other nodes, enhancing the scalability and maintainability of the business system. Users can dynamically select and configure business nodes according to requirements to quickly adapt to market changes and business adjustments; through a visual interface and dynamic configuration, users can easily participate in the creation and adjustment of business systems, reducing dependence on technical personnel, improving the efficiency and convenience of business system management and maintenance, and at the same time reducing the operation and maintenance costs of business systems.

[0111] In an exemplary embodiment, when the business rules change, the following steps may further be included:

[0112] In response to the update of the business rules corresponding to any business node in the preset business nodes, based on the updated business rules, perform configuration update on the business nodes;

[0113] Based on the target business nodes after configuration update, update the target business system.

[0114] Among them, the update of business rules refers to the modification or adjustment of business rules, which may be due to reasons such as rule changes, business requirement adjustments, or optimizations.

[0115] Among them, configuration update refers to adjusting the configuration information of business nodes according to the updated business rules to ensure that the behavior of business nodes conforms to the new rules.

[0116] In specific implementation, business rules may include user-defined rules. Specifically, enterprise users can dynamically adjust business rules according to their own needs. For example, an enterprise may adjust the order processing logic according to customer feedback, and the system can update relevant business nodes in real time to ensure the optimization of business processes. Business rules may also include rules within relevant industries or regions, or rules applicable during a certain special period. For example, in the e-commerce industry, during promotional activities, it may be necessary to temporarily adjust payment limits or add new payment methods, and the system can quickly respond to these needs and dynamically update the configuration of business nodes without redeploying the entire system.

[0117] As can be seen from the above technical solutions of the embodiments of the present application, when the business rules change, the embodiments of the present application automatically detect and update the configuration of business nodes according to the new rules, so as to ensure that the operation of the entire business system conforms to the latest business requirements or rule requirements. This dynamic update mechanism enables the system to easily cope with changes in business rules, not only improving the flexibility and adaptability of the system, but also reducing the system maintenance costs and development workload caused by rule changes.

[0118] In an exemplary embodiment, when the business requirements change, the following steps may further be included:

[0119] In response to an adjustment request for a target business system sent by a user terminal, obtain adjustment information;

[0120] Based on the adjustment information, adjust the target business nodes and the interaction logic between the target business nodes;

[0121] Based on the adjusted target business nodes and the adjusted interaction logic, update the target business system.

[0122] Among them, the adjustment request refers to an instruction sent by a user through a user terminal for modifying, optimizing or updating a created target business system.

[0123] Among them, the adjustment information refers to the specific modification content provided by the user, including the adjustment of business nodes, parameter modification or business process change.

[0124] Specifically, the adjusted business system reflects the user's latest business requirements and optimization requirements.

[0125] Specifically, when the business requirements change, the business orchestration engine has strong dynamic adjustment capabilities. Business personnel can directly modify the orchestrated business processes on the visual interface, such as adding new business nodes to meet new regulatory requirements, deleting or replacing inapplicable business nodes, etc. The engine will monitor these changes in real time and automatically update the internal execution logic to ensure that the new business processes can take effect quickly in near real time. For example, when regulatory policies require adding a real-time anti-fraud detection node to cross-border payment services, business personnel can easily insert the node into the appropriate position in the business process, and the engine will automatically adapt the relevant data processing and logical judgment mechanisms to ensure the compliance and security of the business process. When business rules change or business optimization is required, business personnel can enter the visual management interface again. By modifying the parameters of business nodes, adjusting the node combination order or adding new special business nodes and other operations, quickly adapt to business changes.

[0126] As can be seen from the above technical solutions of the embodiments of the present application, the embodiments of the present application provide a dynamic adjustment mechanism that allows users to modify business nodes and interaction logics according to actual needs during the operation of the business system. This mechanism not only improves the flexibility and adaptability of the system, but also reduces the cost of re-developing the business system caused by changes in business requirements. Through a visual interface or configuration tool, users can easily adjust business nodes and interaction logics, and the business system will automatically update and apply these adjustments without large-scale re-development of the system, reducing the cost and risk of business adjustment.

[0127] The following takes the cross-border payment business as an example to illustrate the generation process of the business system.

[0128] When a new business for cross-border B2B supplier settlement payment needs to be created, business analysis and modeling of the cross-border payment business are carried out. The cross-border B2B supplier settlement payment business process is analyzed to determine key business nodes including order reception, order review, fund distribution, transaction end state notification nodes, etc. These nodes are modeled and stored in the business node library. Create a first-level identifier "Cross-border B2B Payment" and a second-level identifier "Cross-border B2B Supplier Settlement Payment Standard Product" in the product center, and set a customized identifier "Cross-border B2B Supplier Settlement Payment Standard Product - Specific Merchant Edition" according to market research and customer needs. Configure relevant parameters such as handling fees and payment limits, and grant operation permissions for this product to business personnel. Business personnel select the identifier "Cross-border B2B Supplier Settlement Payment Standard Product - Specific Merchant Edition" at the product service standard entry, and the business orchestration engine calls relevant business nodes. On the visual interface, business personnel connect the order reception node to the order review node, set the order review rules, then connect the fund distribution node and configure the distribution parameters, and finally connect the transaction end state notification node. After the orchestration is completed, testing is carried out, and after passing the test, the business is launched. If the relevant rules in a certain region change and an additional compliance review link is required for the cross-border B2B supplier settlement payment business. Business personnel select the compliance review node from the business node library in the management interface, add it to the appropriate position in the business process, and set the review rules and parameters to quickly complete the business adjustment to meet the new regulatory requirements.

[0129] Corresponding to the business system generation methods provided by the above several embodiments, the embodiments of the present application also provide a business system generation device. Since the business system generation device provided by the embodiments of the present application corresponds to the business system generation methods provided by the above several embodiments, the implementation manners of the foregoing business system generation methods are also applicable to the business system generation device provided by this embodiment and will not be described in detail in this embodiment.

[0130] Please refer to Figure 6, which shows a schematic structural diagram of a generating device for a service system provided by an embodiment of the present application. The device has the function of implementing the method for generating a service system in the above method embodiment. This function can be implemented by hardware or by hardware executing corresponding software. As Figure 6 shown, the device may include:

[0131] An identifier acquisition module 610, configured to acquire a target service identifier in response to a service creation request sent by a user terminal;

[0132] A candidate matching module 620, configured to determine candidate service nodes that match the target service identifier in preset service nodes, and generate a matching result based on the service identifiers of the candidate service nodes; the preset service nodes include a plurality of service nodes and the service identifiers corresponding to each service node; each service node is configured to perform different service operations;

[0133] A target return module 630, configured to return the matching result to the user terminal, so that the user terminal selects a target service node based on the service identifier of the candidate service node in the matching result, returns the node configuration information of the target service node, and the interaction logic between each target service node;

[0134] A node configuration module 640, configured to configure the target service node based on the node configuration information;

[0135] A process building module 650, configured to build a service process and generate a target service system based on the configured target service nodes and the interaction logic between each target service node.

[0136] In an exemplary embodiment, the candidate matching module includes:

[0137] A first identifier parsing module, configured to parse the target service identifier to obtain a first-level identifier and a second-level identifier under the first-level identifier;

[0138] A general screening module, configured to screen out service general nodes that match the first-level identifier in the preset service nodes;

[0139] A directional screening module, configured to screen out service directional nodes that match the second-level identifier in the preset service nodes;

[0140] A first candidate determination module, configured to determine the service general nodes and the service directional nodes as candidate service nodes.

[0141] In an exemplary embodiment, the first identifier parsing module includes:

[0142] A second identifier parsing module, configured to parse the target service identifier to obtain a first-level identifier, a second-level identifier, and a customization identifier;

[0143] Correspondingly, the first candidate determination module includes:

[0144] A customized screening module, configured to screen out business customization nodes that match the customization identifier among preset business nodes;

[0145] A second candidate determination module, configured to determine business general nodes, business targeted nodes, and business customization nodes as candidate business nodes.

[0146] In an exemplary embodiment, business nodes are online-bound to business rules corresponding to corresponding business operations; the node configuration module includes:

[0147] An information correction module, configured to correct the node configuration information based on the business rules corresponding to the target business node in the case where there is a conflict between the node configuration information and the business rules corresponding to the target business node;

[0148] A corrected configuration module, configured to configure the target business node based on the corrected node configuration information.

[0149] In an exemplary embodiment, the apparatus further includes a rule update module for automatically updating business nodes and business systems when business rules are updated. The rule update module includes:

[0150] A configuration update module, configured to, in response to the update of the business rules corresponding to any business node in the preset business nodes, perform configuration update on the business nodes based on the updated business rules;

[0151] A first system update module, configured to update the target business system based on the target business node with updated configuration.

[0152] In an exemplary embodiment, the identifier acquisition module includes:

[0153] An identifier selection module, configured to, in response to a business creation request sent by a user terminal, send a preset business identifier to the user terminal so that the user terminal selects a target business identifier from the preset business identifiers.

[0154] In an exemplary embodiment, the apparatus further includes an adjustment request module for adjusting business nodes and updating business systems when a user requests to adjust a business system. The adjustment request module includes:

[0155] An adjustment information module, configured to, in response to an adjustment request for a target business system sent by a user terminal, acquire adjustment information;

[0156] A node adjustment module, configured to adjust the target business nodes and the interaction logic between the target business nodes based on the adjustment information;

[0157] A second system update module, configured to update a target business system based on the adjusted target business nodes and the adjusted interaction logic.

[0158] It should be noted that, when implementing its functions, the device provided in the above embodiment is only illustrated by dividing the above functions into respective modules. In practical applications, the above functions may be allocated to different function modules according to needs, that is, the internal structure of the device is divided into different function modules to complete all or part of the functions described above. In addition, the device provided in the above embodiment and the method embodiment belong to the same concept. For the specific implementation process, please refer to the method embodiment, which will not be elaborated here.

[0159] An embodiment of the present application provides an electronic device, which includes a processor and a memory. At least one instruction or at least one program segment is stored in the memory, and the at least one instruction or the at least one program segment is loaded and executed by the processor to implement any one of the business system generation methods provided in the above method embodiments.

[0160] The memory can be used to store software programs and modules. The processor runs the software programs and modules stored in the memory to execute various functional applications and data processing. The memory mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for functions, etc.; the data storage area can store data created according to the use of the device, etc. In addition, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices. Correspondingly, the memory may also include a memory controller to provide the processor with access to the memory.

[0161] The method embodiments provided in the embodiments of the present application can be executed on a computer terminal, a server, or a similar computing device, that is, the above electronic device may include a computer terminal, a server, or a similar computing device. Figure 7 is a hardware structure block diagram of a computer device for running a business system generation method provided by an embodiment of the present invention. As Figure 7 shown, the internal structure of the computer device may include, but is not limited to: a processor, a network interface, and a memory. Among them, the processor, network interface, and memory in the computer device can be connected through a bus or other means. In the embodiments of the present specification Figure 7 it is taken as an example of being connected through a bus.

[0162] Among them, the processor (or CPU (Central Processing Unit)) is the computing core and control core of the computer device. The network interface may optionally include a standard wired interface, a wireless interface (such as WI-FI, a mobile communication interface, etc.). The memory is the memory device in the computer device, used to store programs and data. It can be understood that the memory here can be a high-speed RAM storage device, or a non-volatile memory device, such as at least one disk storage device; optionally, it can also be at least one storage device located far from the aforementioned processor. The memory provides a storage space that stores the operating system of the electronic device, which may include but is not limited to: Windows system (an operating system), Linux (an operating system), Android (a mobile operating system) system, IOS (a mobile operating system) system, etc., and the present invention does not make any limitations in this regard; and, one or more instructions suitable for being loaded and executed by the processor are also stored in this storage space, and these instructions can be one or more computer programs (including program codes). In the embodiments of this specification, the processor loads and executes one or more instructions stored in the memory to implement the method for generating a service system provided in the above method embodiments.

[0163] An embodiment of the present application further provides a computer-readable storage medium. The computer-readable storage medium can be set in the electronic device to store at least one instruction or at least one segment of a program related to implementing a method for generating a service system. The at least one instruction or the at least one segment of the program is loaded and executed by the processor to implement any one of the methods for generating a service system provided in the above method embodiments.

[0164] Optionally, in this embodiment, the above storage medium may include but is not limited to: various media that can store program codes such as USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical discs.

[0165] It should be noted that the above order of the embodiments of the present application is only for description and does not represent the superiority or inferiority of the embodiments. And the above specific embodiments of this specification have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0166] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the apparatus embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments.

[0167] Those of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by hardware or by a program instructing relevant hardware. The program can be stored in a computer-readable storage medium. The above-mentioned storage medium can be a read-only memory, a magnetic disk, an optical disk, etc.

[0168] The above are only the preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for generating a service system, characterized in that, The method includes: Upon receiving a service creation request sent by a user terminal, obtaining a target service identifier; Determining, in a preset service node, a candidate service node that matches the target service identifier, and generating a matching result based on the service identifier of the candidate service node; the preset service node includes a plurality of service nodes and the service identifier corresponding to each service node; each service node is configured to perform a different service operation; Returning the matching result to the user terminal, so that the user terminal selects a target service node based on the service identifier of the candidate service node in the matching result, returns the node configuration information of the target service node, and the interaction logic between the target service nodes; Configuring the target service node based on the node configuration information; Based on the configured target service node and the interaction logic between the target service nodes, building a service process to generate a target service system.

2. The method for generating the service system according to claim 1, wherein The determining, in the preset service node, a candidate service node that matches the target service identifier includes: Parsing the target service identifier to obtain a first-level identifier and a second-level identifier under the first-level identifier; Filtering out service general nodes that match the first-level identifier in the preset service node; Filtering out service directional nodes that match the second-level identifier in the preset service node; Determining the service general node and the service directional node as the candidate service nodes.

3. The method for generating the service system according to claim 2, wherein, The parsing the target service identifier to obtain a first-level identifier and a second-level identifier under the first-level identifier includes: Parsing the target service identifier to obtain the first-level identifier, the second-level identifier, and a customization identifier; Correspondingly, the determining the service general node and the service directional node as the candidate service nodes includes: Filtering out service customization nodes that match the customization identifier in the preset service node; Determining the service general node, the service directional node, and the service customization node as the candidate service nodes.

4. The method for generating a service system according to claim 1, wherein The service node is online-bound to the service rule corresponding to the corresponding service operation; The configuring the target service node based on the node configuration information includes: In the case where there is a conflict between the node configuration information and the service rule corresponding to the target service node, correcting the node configuration information based on the service rule corresponding to the target service node; Configuring the target service node based on the corrected node configuration information.

5. The method for generating the service system according to claim 4, wherein The method further includes: Upon receiving an update to the service rule corresponding to any service node in the preset service node, based on the updated service rule, performing a configuration update on the service node; Based on the target service node after the configuration update, updating the target service system.

6. The method for generating a service system according to claim 1, wherein The upon receiving a service creation request sent by a user terminal, obtaining a target service identifier includes: Upon receiving the service creation request sent by the user terminal, sending a preset service identifier to the user terminal, so that the user terminal selects the target service identifier from the preset service identifiers.

7. The method for generating a service system according to claim 1, wherein The method further includes: In response to an adjustment request for the target service system sent by the user terminal, obtain adjustment information; Based on the adjustment information, adjust the target service nodes and the interaction logic between the target service nodes; Based on the adjusted target service nodes and the adjusted interaction logic, update the target service system.

8. A generating device for a service system, characterized in that The device includes: An identifier acquisition module, configured to obtain a target service identifier in response to a service creation request sent by a user terminal; A candidate matching module, configured to determine candidate service nodes that match the target service identifier in preset service nodes, and generate a matching result based on the service identifiers of the candidate service nodes; the preset service nodes include a plurality of service nodes and the service identifiers corresponding to each service node; each service node is configured to perform different service operations; A target return module, configured to return the matching result to the user terminal, so that the user terminal selects a target service node based on the service identifier of the candidate service node in the matching result, returns the node configuration information of the target service node, and the interaction logic between the target service nodes; A node configuration module, configured to configure the target service nodes based on the node configuration information; A process building module, configured to build a service process based on the configured target service nodes and the interaction logic between the target service nodes, and generate a target service system.

9. An electronic device, characterized in that, It includes a processor and a memory, and at least one instruction or at least one program segment is stored in the memory, and the at least one instruction or the at least one program segment is loaded and executed by the processor to implement the method for generating a service system according to any one of claims 1 to 7.

10. A computer-readable storage medium, in which at least one instruction or at least one program segment is stored, and the at least one instruction or the at least one program segment is loaded and executed by a processor to implement the method for generating a service system according to any one of claims 1 to 7.

Images