Business processing method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a business processing method and device, equipment, a storage medium and a program product. The method comprises: in response to receiving at least one service message related to a service event, determining a virtual resource processing scheme matched with the at least one service message, the service event being configured to trigger processing of virtual resources; determining at least one target resource processing plug-in from a group of candidate resource processing plug-ins based on the virtual resource processing scheme and the at least one service message, each resource processing plug-in being configured to execute at least one action related to virtual resource processing; generating a calling scheme of at least one target resource processing plug-in based on the at least one service message; calling at least one target resource processing plug-in based on the calling scheme; and providing a response for the at least one service message based on a calling result of the at least one target resource processing plug-in. Therefore, the service processing quality and efficiency can be improved.

Description

Business processing methods, apparatus, equipment, storage media, and program products Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to methods, apparatus, devices, computer-readable storage media, and computer program products for business processing. Background Technology

[0002] With the development of network technology, various terminal devices can provide people with a variety of services in work and life. Many network-based services involve the consumption and transfer of virtual resources. These virtual resources can be funds, various assets, and various points. Because the consumption and transfer of virtual resources involve conversions between different entities, accounts, and even different types of virtual resources (e.g., the exchange of different currencies), this involves various financial actions and the conversion of financial information.

[0003] Summary of the Invention

[0004] In a first aspect of this disclosure, a method for business processing is provided. The method includes: in response to receiving at least one business message related to a business event, determining a virtual resource processing scheme matching the at least one business message, the business event being configured to trigger virtual resource processing; based on the virtual resource processing scheme and the at least one business message, determining at least one target resource processing plugin from a set of candidate resource processing plugins, each resource processing plugin being configured to perform at least one action related to virtual resource processing; generating a calling scheme for the at least one target resource processing plugin based on the at least one business message; invoking the at least one target resource processing plugin based on the calling scheme; and providing a response to the at least one business message based on the invocation result of the at least one target resource processing plugin.

[0005] In a second aspect of this disclosure, an apparatus for business processing is provided. The apparatus includes: a scheme determination module configured to determine a virtual resource processing scheme matching the at least one business message in response to receiving at least one business message related to a business event, wherein the business event is configured to trigger virtual resource processing; a plug-in determination module configured to determine at least one target resource processing plug-in from a set of candidate resource processing plug-ins based on the virtual resource processing scheme and the at least one business message, wherein each resource processing plug-in is configured to perform at least one action related to virtual resource processing; a scheme generation module configured to generate a calling scheme for the at least one target resource processing plug-in based on the at least one business message; a plug-in calling module configured to call the at least one target resource processing plug-in based on the calling scheme; and a response providing module configured to provide a response to the at least one business message based on the calling result of the at least one target resource processing plug-in.

[0006] In a third aspect of this disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the electronic device to perform the method of the first aspect.

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. The medium stores a computer program that, when executed by a processor, implements the method of the first aspect.

[0008] In a fifth aspect of this disclosure, a computer program product is provided. The product includes a computer program, wherein when executed by a processor, the computer program implements the method according to a first aspect of this disclosure.

[0009] It should be understood that the content described in this section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0011] Figure 1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;

[0012] Figure 2 illustrates a schematic diagram of an example architecture for business processing according to some embodiments of the present disclosure;

[0013] Figure 3 shows a block diagram of a resource orchestration system performing tasks according to some embodiments of the present disclosure;

[0014] Figure 4 illustrates an example diagram of the signaling flow for service processing according to some embodiments of the present disclosure;

[0015] Figure 5 illustrates examples of resource components according to some embodiments of the present disclosure;

[0016] Figures 6A to 6C illustrate examples of virtual resource orchestration schemes according to some embodiments of the present disclosure;

[0017] Figure 7 illustrates an example of an orchestration system link according to some embodiments of the present disclosure;

[0018] Figure 8 illustrates an example of a target virtual resource processing scheme according to some embodiments of the present disclosure;

[0019] Figure 9 illustrates an example diagram of signaling flow for orchestrating resource links according to some embodiments of the present disclosure;

[0020] Figure 10 illustrates an example of a resource flow according to some embodiments of the present disclosure;

[0021] Figure 11 illustrates an example of a record resource flow model according to some embodiments of the present disclosure;

[0022] Figure 12 shows an example of a visualization view corresponding to a virtual resource flow;

[0023] Figure 13 shows a flowchart of a method for business processing according to some embodiments of the present disclosure;

[0024] Figure 14 illustrates an exemplary structural block diagram of an apparatus for business processing according to some embodiments of the present disclosure; and

[0025] Figure 15 shows a block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented. Detailed Implementation

[0026] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0027] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0028] In this document, unless explicitly stated otherwise, performing a step in response to A does not mean that the step is performed immediately after A, but may include one or more intermediate steps.

[0029] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0030] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, relevant users should be informed of the type, scope of use, and usage scenarios of the information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and authorization should be obtained from the relevant users. Among them, relevant users may include any type of rights holder, such as individuals, enterprises, and groups.

[0031] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly inform the user that the requested operation will require obtaining and using the user's information, thereby enabling the relevant user to choose whether to provide information to the software or hardware such as the electronic device, application, server, or storage medium that performs the operation of the technical solution disclosed herein based on the prompt message.

[0032] As an optional but non-restrictive implementation, in response to a user's active request, a prompt message can be sent to the user, such as a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide information to the electronic device.

[0033] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0034] In financial systems, business-finance conversion refers to the conversion of financial information and the execution of financial actions based on business information, such as completing accounting and bookkeeping based on payment information. Funds arrangement is the specific implementation of business-finance conversion. In international scenarios and complex payment transactions, business-finance conversion not only involves calling accounting and bookkeeping, but also involves the coordination between various fund transactions (accounting, reconciliation, allocation, liquidity, inter-entity clearing, reporting, management and reporting, foreign exchange), hence it is also called funds arrangement. In addition to funds, other types of virtual resources, such as points provided by different businesses or online services, other types of assets, etc., also require a similar "business-finance conversion" process. Therefore, in the following text, "virtual resources" (or simply "resources") refer to resources that can be exchanged between different entities, and specific examples include different types of funds (different currencies), other resources recognized in different entities (such as points, physical or virtual assets), etc.

[0035] Figure 1 illustrates a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Example environment 100 involves at least one business system 120 and a resource orchestration system 110. The at least one business system 120 may include business systems 120-1, 120-2, ..., 120-N, where N is a positive integer. For ease of description, one or more business systems may be collectively referred to as business system 120 or individually. Business system 120 can receive business events from business parties. If a business event is associated with a resource, business system 120 can send a business message corresponding to the received business event to resource orchestration system 110.

[0036] The business party can include any suitable object, such as, but not limited to, one or more users, enterprises, applications, digital assistants, etc. Resources can be virtual resources, such as virtual currency, virtual funds, or any suitable virtual resource. Business events associated with resources can include resource consumption events (e.g., decrease in funds), resource increase events (e.g., increase in funds), resource conversion events (e.g., conversion of funds between different currencies), etc.

[0037] Resource orchestration system 110 can determine at least one resource processing action for processing a received business message from a plurality of resource processing actions 130 (which may include, for example, accounting, foreign exchange, invoicing, etc., any suitable actions). Resource orchestration system 110 can execute this at least one resource processing action to process the business message. Resource orchestration system 110 can also, for example, provide a response to business system 120 in response to the completion of processing the business message. The response to the business message can indicate the result of processing the business message.

[0038] Resource orchestration refers to the flow of resources (or funds) required to complete resource-related business activities. For example, funds may flow from accounting entity 1 through accounting entities 2 and 3 to accounting entity 4, i.e., accounting entity 1 → accounting entity 2 → accounting entity 3 → accounting entity 4. Accounting entities can be accounts, financial products such as funds, etc. Fund orchestration strategies can also include the timing of fund inflows or outflows in each accounting entity, and whether each accounting entity performs settlement. Resource orchestration system 110 can determine different orchestration strategies based on different parameters.

[0039] The business system 120 and the resource orchestration system 110 can be deployed on the same electronic device or on different electronic devices. For example, the business system 120 can be deployed locally on the user's terminal device, and the resource orchestration system 110 can be deployed on a remote device. The business system 120 and the resource orchestration system 110 can communicate via a communication connection between the terminal device and the remote device.

[0040] Business system 120 and / or resource orchestration system 110 may run on suitable electronic devices. These electronic devices can be any type of computing-capable device, including terminal devices or server devices. Terminal devices can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. Server devices may include, for example, computing systems / servers, such as mainframes, edge computing nodes, computing devices in cloud environments, and so on. In some embodiments, business processing system 110 may be implemented based on cloud services.

[0041] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0042] As mentioned earlier, if an application can provide business processing capabilities, users can provide business events to the application. The application can then process these business events and provide the results to the user. Traditionally, this often requires specialists to predefine different processing solutions for different business events. This necessitates a deep understanding of these different business events by the specialists, resulting in high manpower costs and low efficiency. Furthermore, traditional resource orchestration systems are often tightly coupled with business systems. When business events change, resource errors can occur without timely detection. This affects the accuracy of the resource orchestration system in processing business data.

[0043] In view of the above, according to embodiments of this disclosure, an improved solution for business processing is provided. According to the solution of embodiments of this disclosure, in response to receiving at least one business message related to a business event, a virtual resource processing scheme matching the at least one business message is determined, and the business event is configured to trigger virtual resource processing. Based on the virtual resource processing scheme and the at least one business message, at least one target resource processing plugin is determined from a set of candidate resource processing plugins, and each resource processing plugin is configured to perform at least one action related to virtual resource processing. Based on the at least one business message, a calling scheme for the at least one target resource processing plugin is generated. The at least one target resource processing plugin is called based on the calling scheme. Based on the calling result of the at least one target resource processing plugin, a response to the at least one business message is provided.

[0044] This approach enables the orchestration of virtual resource processing solutions, resource processing plugins, and resource chains, reducing business management costs, achieving unified information configuration, and improving configuration efficiency. It also reduces business complexity and improves processing efficiency. Furthermore, it allows for the construction of end-to-end resource flows, improving overall data quality and problem localization efficiency. Finally, it enhances the quality and efficiency of business processing.

[0045] Figure 2 illustrates a schematic diagram of an example architecture 200 for service processing according to some embodiments of the present disclosure. For ease of discussion, the architecture 200 will be described with reference to the environment 100 of Figure 1.

[0046] In architecture 200, business entity 202 can provide business event 210. Business event 210 can be configured to trigger the processing of virtual resources. For example, business event 210 can be a user's payment event. Business event 210 is provided to multiple business systems 120. The multiple business systems 120 can include any suitable business system, which may include, but is not limited to, e-commerce payment system, user payment system, channel settlement system, etc. In some embodiments, different business events can trigger different business systems. At least one business system for processing the business event can be determined from the multiple business systems 120 based on the business event.

[0047] In some embodiments, a mapping relationship between different business events and their corresponding business systems can be stored (e.g., business event A - business system A, business event B - business system B, ..., it should be noted that a business event can correspond to at least one business system, and a business system can also correspond to at least one business event). Based on the received business event 210 and this mapping relationship, at least one business system corresponding to business event 210 can be determined from multiple business systems 120.

[0048] Each business system can generate a business message in response to business event 210. Therefore, at least one business system corresponding to business event 210 can generate at least one business message 220 (for example, it may include business messages 220-1, 220-2, ..., 220-M, where M is a positive integer. For ease of description, one or more business messages can be collectively referred to as or individually referred to as business message 220). For example, if it can be determined that at least one business system corresponding to business event 210 includes business system A, business system B, and business system C, then at least one business message related to business event 210 may include business message A, business message B, and business message C generated by these three business systems respectively.

[0049] The business system 120 can be referred to as the upstream system of the resource orchestration system 110, that is, the resource orchestration system 110 can also be referred to as the downstream system of the business system 120. At least one business message 220 is provided to the resource orchestration system 110. In some embodiments, if the at least one business message 220 includes multiple business messages, these multiple business messages can be concatenated to obtain a concatenated business message. The concatenated business message is provided to the resource orchestration system 110. Alternatively or additionally, in some embodiments, multiple business messages can also be provided to the resource orchestration system 110 separately.

[0050] In architecture 200, resource orchestration system 110 involves a resource scheme orchestration layer 230, a resource link orchestration layer 240, a resource capability orchestration layer 250, and a resource capability layer 260. Resource scheme orchestration layer 230 and resource capability orchestration layer 250 can, in response to receiving at least one business message 220, determine a virtual resource processing scheme matching the at least one business message 220. A virtual resource processing scheme is also called a resource orchestration scheme, such as a funding orchestration scheme.

[0051] In embodiments of this disclosure, the hierarchical structure relates to the orchestration of resource schemes and the definition of resource capabilities. The resource capability orchestration layer 250 can determine at least one target resource processing plugin from a set of candidate resource processing plugins included in the resource capability layer 260, based on a virtual resource processing scheme and at least one business message. The resource capability orchestration layer 250 can also generate a calling scheme for at least one target resource processing plugin based on at least one business message, and invoke at least one target resource processing plugin of the resource capability layer 260 based on the calling scheme. The resource orchestration system 110 can, for example, provide a response to at least one business message based on the invocation result of at least one target resource processing plugin.

[0052] Resource processing plugins can also be referred to as resource capabilities. Resource capabilities can also be viewed as atomic capabilities at the system implementation level, representing abstractions specific to business scenarios. The resource capability layer 260 can include a set of candidate resource capabilities, that is, a set of candidate resource processing plugins. A set of candidate resource capabilities may include, for example, balance payment, payroll processing, transfer, reconciliation, accounting, foreign exchange, exchange, declaration, inter-entity clearing, etc. Each resource processing plugin can be configured to perform at least one action related to virtual resource processing. For example, taking the balance payment capability as an example, its corresponding resource processing plugin can be defined with field descriptions, field types, accounting logic, etc., of various information required in the action execution, for the balance payment function. As described below, each resource processing plugin can, for example, perform at least one action based on the configuration information in the virtual resource processing scheme. By defining resource processing plugins, resource processing capabilities can be flexibly combined and invoked by different business scenarios and resource processing schemes to complete resource processing tasks corresponding to different businesses.

[0053] The resource capability orchestration layer 250 can, for example, be based on the scenario corresponding to at least one target resource processing plugin, and the standard model and documents in the implementation scenario. The resource scheme orchestration layer 230 and the resource capability orchestration layer 250 can, for example, be based on the standard model and virtual resource processing scheme to jointly associate and orchestrate the virtual resource flow (which can be, for example, an end-to-end virtual resource flow) of the business event 210. The virtual resource flow is provided to the resource link orchestration layer 240. The resource link orchestration layer 240 can, for example, generate the resource link of the business event based on the virtual resource flow and verify the resource link.

[0054] This solution improves the efficiency of business-finance conversion and capital allocation through different dimensions and methods, ultimately achieving an overall efficiency improvement.

[0055] For example, in traditional solutions, the funds orchestration framework requires communication based on payment domain models when discussing business projects. This includes determining accounting entries, foreign exchange exposure levels, and inter-entity debt clearing based on upstream clearing and settlement document models. This involves logical conversions between different personnel; for instance, different individuals may have different understandings of clearing and settlement operations and their mapping to funds operations. In this disclosed solution, a set of standards and a common language for funds are defined and constrained based on the funds scheme and capabilities, such as standard funds documents for fund collection, fund disbursement, payment, and acquiring. This allows for communication and decision-making based on these defined common standards, reducing cognitive differences and communication costs.

[0056] Furthermore, traditional fund orchestration solutions require understanding the differences between upstream business operations and their impact on various fund areas. Fund capability-based orchestration, on the other hand, can uniformly convert upstream business information into fund capabilities and fund documents. From fund capabilities to the final fund orchestration logic, it is reusable or customizable through configuration and low-code implementation. The solution disclosed in this paper achieves configurability based on fund schemes, and reusability and low-code extension based on fund capabilities, ultimately improving overall development efficiency.

[0057] On the other hand, according to the solution disclosed herein, quality problems and risks scattered across various downstream nodes of funds can be identified and avoided in advance. Through proactive fund orchestration, problems are detected early, improving project quality. This is mainly achieved through several aspects, comprehensively enhancing the quality of business-finance conversion. For example, in traditional solutions, upstream errors directly impact all areas of funding. Incorrect assignment of key fields in transaction data or errors in system link associations can lead to errors in fund orchestration logic. The solution disclosed herein, through the construction of fund capabilities and fund document layers, completes pre-arrangement of system links and pre-verification of business information, proactively intercepting data errors and system risks. This reduces quality problems and risks downstream of funds.

[0058] Further details of the resource orchestration system 110 are described with reference to FIG3. FIG3 shows a block diagram 300 of the resource orchestration system 110 performing tasks according to some embodiments of the present disclosure. As shown in FIG3, at step 301, the resource capability orchestration layer 250 receives at least one service message 220.

[0059] At step 302, the resource capability orchestration layer 250 can extract the decision elements and information corresponding to the business event 210 from at least one business message 220, and query the resource scheme orchestration layer 230 for a virtual resource processing scheme that matches the at least one business message 220. The decision elements and information corresponding to the business event 210 may indicate, for example, the scenario, source, type, etc. of the business event 210.

[0060] Regarding the generation method of virtual resource processing solutions, the resource solution orchestration layer 230 may include solution templates for virtual resources, which may contain processing rules for virtual resources. The resource solution orchestration layer 230 may also include resource patterns for virtual resources. A single-point virtual resource processing solution can be generated based on a combination of solution templates and instantiated resource patterns. A virtual resource processing solution (also known as an end-to-end virtual resource processing solution) can be generated by combining at least one single-point virtual resource solution. Based on the decision elements and information corresponding to business event 210, a virtual resource processing solution matching at least one business message 220 can be queried from the pre-generated virtual resource processing solutions. The resource capability orchestration layer 250 can determine the query results as the virtual resource processing solution matching at least one business message 220.

[0061] At step 303, the resource capability orchestration layer 250 can determine at least one target resource processing plugin from a set of candidate resource processing plugins based on the configuration information of the virtual resource processing scheme and in combination with the scenario, source, and / or type of the business event 210. The resource capability orchestration layer 250 can also, for example, load at least one target resource processing plugin to complete the preparation for at least one target resource processing plugin.

[0062] At step 304, the resource capability orchestration layer 250 can orchestrate and schedule at least one target resource processing plugin, generating execution tasks and topologies for at least one target resource processing plugin. The orchestration and scheduling of the target resource processing plugins may specifically include the preceding and following calls and extension relationships of the plugins.

[0063] At step 305, the resource capability orchestration layer 250 invokes and executes at least one target resource processing plugin. The at least one target resource processing plugin is loosely coupled, and the resource capability orchestration layer 250 can execute at least one target resource processing plugin uniformly.

[0064] At step 3061, each of the at least one target resource processing plugins invoked by the resource capability orchestration layer 250 can perform a corresponding action (also referred to as a resource action or funding action). Each target resource processing plugin can, for example, perform the corresponding resource action based on the configuration in the virtual resource processing scheme.

[0065] In steps 3062 and 3063, under each action, each target resource processing plugin can call the atomic interface of the corresponding resource downstream based on the corresponding configuration to complete the overall resource orchestration.

[0066] At step 3064, the resource capability orchestration layer 250 can determine the virtual resource document corresponding to at least one business message 220 on a scenario-by-scenario basis.

[0067] At step 3065, the resource capability orchestration layer 250 can determine the standard model and document in the corresponding scenario based on the scenario corresponding to at least one target resource processing plugin.

[0068] At steps 3066 and 3067, the resource scheme orchestration layer 230 and the resource capability orchestration layer 250 can jointly associate and orchestrate the end-to-end virtual resource flow of the business event 210 based on the standard model and resource processing scheme.

[0069] At step 3068, the resource link orchestration layer 240 can perform account verification and physical verification based on virtual resource flows to verify the data quality of the integrated resource links and the correctness of the calling scheme configuration.

[0070] At step 3069, the resource link orchestration layer 240 can also build resource traceability capabilities based on virtual resource flows, quickly retrieve global resource data, and improve the efficiency of problem location and investigation.

[0071] The details of the service processing are described below with reference to Figure 4. Figure 4 shows an example diagram of a signaling flow 400 for service processing according to some embodiments of the present disclosure. The signaling flow 400 relates to a service system 120, a resource capability orchestration layer 250, a resource scheme orchestration layer 230, a resource capability layer 260, and a resource data layer 402.

[0072] As shown in Figure 4, at step 411, the business system 120 sends at least one business message to the resource capability orchestration layer 250.

[0073] At step 412, the resource capability orchestration layer 250 can parse and transform at least one business message to identify information such as business scenario and transaction type in at least one business message, and extract key business elements (such as merchant number, channel ID, etc.).

[0074] At step 413, the resource capability orchestration layer 250 can determine at least one resource component associated with at least one business message. Each resource component is associated with a business type and includes a definition of a resource processing object for that business type. A resource component is also defined according to the business scenario, and consists of atomic capabilities and basic templates for configuration (the basic template may exist, for example, in the form of a card, in which case it may also be called a basic card). Taking virtual resources as funds as an example, resource components may include, for example, a payment funds component, an acquiring funds component, and so on.

[0075] Referring to FIG5, FIG5 illustrates an example 500 of resource components according to some embodiments of the present disclosure. Example 500 may, for example, illustrate an example of a gateway payment resource component. As shown in Example 500, the resource component may include, for example, a pricing currency, a settlement currency, a payment entity, a receiving entity, a payment channel, a receiving method, a channel account, a payment receiving account, at least one channel abbreviation, at least one channel account corresponding to at least one channel abbreviation, at least one receiving bank, and a bank account corresponding to at least one receiving bank. It is understood that Example 500 shows only one example, and the resource component may include more or less information.

[0076] Regarding the configuration of resource components, in some embodiments, a new channel account is added in response to receiving a new service. Users (e.g., professionals) or electronic devices can configure according to the service type and determine whether to modify the content of an existing resource component or add a corresponding resource component. Further, if a new resource component needs to be added, information such as the service type, service entity, currency information, account information, and inflow / outflow protocol corresponding to that resource component can be filled into the basic card. If it is determined that an existing resource component needs to be modified, information such as the channel account can be added by editing the existing information in the basic card. If a channel account has not been created, the user can be directly redirected to the channel account configuration page based on the configuration service of the resource component to quickly complete the addition of the channel account.

[0077] In some embodiments, the full rules corresponding to a channel account can also be detected. If no full rules have been created, they can be entered via the full rule creation module. Furthermore, the corresponding clearing rules under the full rules can also be detected. If no clearing rules have been created, they can be entered via the clearing rule creation module. The billing rules corresponding to the full rules can also be detected. If no billing rules have been created, they can be created via the billing rule creation module. Thus, the configuration of a single resource component and its related protocols and basic information can be completed, achieving one-stop configuration and management of business access.

[0078] Referring back to FIG4, in some embodiments, each resource component may be included in one or more candidate virtual resource processing schemes. Each candidate virtual resource processing scheme may include at least one resource component, and multiple candidate virtual resource processing schemes may include the same resource component. Regarding the arrangement of virtual resource processing schemes, details of the arrangement are described below with reference to FIGS. 6A to 6C. FIGS. 6A to 6C illustrate examples 600A to 600C of arranging virtual resource processing schemes according to some embodiments of the present disclosure.

[0079] As shown in Example 600A, users (e.g., professionals) or electronic devices can select previously configured resource components from the resource component list. For example, as shown in Figure 6A, a platform acquiring resource component and a gateway payment resource component can be selected. The business entity of the platform acquiring resource component can be, for example, the acquiring entity, and the business entity of the gateway payment resource component can be, for example, the payment entity. For example, business orchestration for a single business scenario can be completed based on a canvas.

[0080] As shown in Example 600B, new resource components can be dynamically decided and supplemented based on the configuration content to achieve overall business integrity. If multiple resource components exist, and these components cross entities, a resource collection and payment resource component can be generated to create a delegating entity to describe the debt and creditor relationship between the entities. As shown in Figure 6B, since the platform acquiring resource component and the gateway payment resource component correspond to different business entities, and there is a cross-entity situation, a resource collection and payment resource component (such as the funds collection and payment resource component shown in the figure) can be generated to create a delegating entity to describe the debt and creditor relationship between the entities. It can be understood that the delegating entity can be, for example, the gateway payment resource component, and the entrusted entity can be, for example, the funds collection and payment resource component. In some embodiments, after the funds collection and payment resource component is generated, the user or electronic device can choose whether to add a new resource component (such as the funds center resource component shown in the figure).

[0081] As shown in Example 600C, users or electronic devices can further expand and add new resource components (such as the PIPOX payment collection resource component shown in the diagram) based on the dynamically supplemented funding plan. These new resource components, i.e., new entities, can further establish payment collection relationships with the original business entities. Through this configuration, funds can be further centralized and aggregated, impacting the overall fund flow.

[0082] Referring back to Figure 4, regarding the specific method of determining resource components, in some embodiments, the resource capability orchestration layer 250 can determine at least one of a business scenario type and a virtual resource processing type corresponding to at least one business message, and then extract business configuration information from the at least one business message. The business configuration information may specify business elements such as business lines, merchant information, and country. Furthermore, the resource capability orchestration layer 250 can determine at least one resource component based on at least one of the business scenario type and the virtual resource processing type, as well as the business configuration information.

[0083] At step 414, the resource capability orchestration layer 250 can select a virtual resource processing scheme that includes at least one resource component from a pre-configured set of candidate virtual resource processing schemes in the resource scheme orchestration layer 230. It should be noted that if multiple virtual resource processing schemes are selected, these multiple virtual resource processing schemes can be obtained from the resource scheme orchestration layer 230 at once.

[0084] At step 415, the resource capability orchestration layer 250 can determine at least one target resource processing plugin from a set of candidate resource processing plugins based on the virtual resource processing scheme and at least one business message. Specifically, the resource capability orchestration layer 250 can determine at least one target resource processing plugin from a set of candidate resource processing plugins based on at least one business message and at least one resource component included in the virtual resource processing scheme. For example, supported resource processing plugins can be selected based on resource components, business elements, etc. There may be dependencies between resource processing plugins; for example, a payment resource processing plugin may call a fund collection and payment resource processing plugin or a customer fund exchange capability resource processing plugin as needed. The resource capability orchestration layer 250 can generate a resource processing plugin call topology based on configuration and business requirements.

[0085] At step 416, the resource capability orchestration layer 250 can generate an invocation scheme for at least one target resource processing plugin based on at least one business message. Specifically, the resource capability orchestration layer 250 can generate an invocation scheme for at least one target resource processing plugin based on the configuration information of the virtual resource processing scheme and the plugin dependencies of at least one target resource processing plugin (e.g., resource processing plugin invocation topology). The invocation scheme may, for example, indicate the execution order of at least one target resource processing plugin (taking resource processing plugin A and resource processing plugin B as an example, the invocation scheme may indicate the invocation order of these two resource processing plugins), the capability invocation topology of one or more target resource processing plugins, the invocation parameters of each target resource processing plugin, and so on.

[0086] At step 417, the resource capability orchestration layer 250 can issue a virtual resource processing scheme to the resource capability layer 260, and execute at least one target resource processing plugin to invoke the resource capability layer 260.

[0087] At step 418, the resource capability layer 260 can determine the extensions of the resource processing plugin. Specifically, the resource capability layer 260 can provide extension interfaces, which are implemented by each business package. The resource component constrains the specific business identity and can be loaded into the corresponding business package. The business package implements the interface extensions provided by the resource processing plugin, thereby achieving platform and business isolation and supporting business customization needs without affecting the platform.

[0088] At step 419, the resource capability layer 260 can orchestrate system links. In some embodiments, since a resource processing plugin may correspond to multiple business messages, the connection and orchestration between system links must be completed to restore the complete resource elements and information. For example, system link orchestration can be performed based on a graph database. Specifically, after each business message is received, it can be determined whether a predecessor node for that message node exists in the graph database (e.g., based on attributes). If no predecessor node exists, it can be determined that the predecessor node for that business message has not arrived, and the business message can be temporarily not processed. If a predecessor node exists, it can be written to the current message node.

[0089] Each time a message node is written, information corresponding to a node of type "MSG_NODE" can be written to the graph, storing the message's identifier (ID), status, time, etc. A node of type "RELATE_NODE" can also be written, storing the associated nodes of this message and other upstream and downstream messages. An edge from node MSG_NODE to node RELATE_NODE can also be written. If the current node generates a resource document, a node of type "FUND_EVENT_NODE" is also generated, storing the corresponding resource document information. An edge from node MSG_NODE to node FUND_EVENT_NODE can also be written.

[0090] The details of the orchestration system link are described below with reference to Figure 7. Figure 7 shows an example diagram 700 of an orchestration system link according to some embodiments of the present disclosure. As shown in example 700, a business message corresponding to a resource processing plugin can be received. If three business messages are received respectively, business message nodes 730, 740, and 750 of type "MSG_NODE" can be created in Figure 700, and the information corresponding to the messages can be recorded. Business message nodes 730 and 740 are associated with ID number 100, and business message nodes 740 and 750 are associated with ID number 200. Business message node 730 can generate resource document node 710, and business message node 740 can generate resource document node 720. Example Figure 700 shows the storage structure of these three business messages in a graph database.

[0091] At step 420, the resource capability layer 260 can identify associated resource documents. For example, the resource capability layer 260 can identify associated resource documents by traversing the graph database when each message node is stored in the graph database (e.g., the graph database shown in Figure 7).

[0092] At step 421, the resource capability layer 260 can match a target virtual resource processing scheme. Specifically, each resource document can store one or more virtual resource processing schemes corresponding to a resource component. The final target virtual resource processing scheme can be determined by taking the intersection of multiple virtual resource processing schemes. Each virtual resource document corresponds to a resource component and indicates one or more candidate virtual resource processing schemes containing the resource component.

[0093] The details of determining a target virtual resource processing scheme are described below with reference to FIG8. FIG8 illustrates an example 800 of determining a target virtual resource processing scheme according to some embodiments of the present disclosure. In example 800, the virtual resource processing scheme corresponding to business message 220 may be, for example, end-to-end resource scheme 1 and end-to-end resource scheme 2 in resource scheme orchestration layer 230. End-to-end resource scheme 1 may include resource component A and resource component B, and end-to-end resource scheme 2 may include resource component A and resource component C. Resource capability layer 260 may include resource document 1 and resource document 2, resource document 1 may store end-to-end resource scheme 1 and end-to-end resource scheme 2, and resource document 2 may store end-to-end resource scheme 2 and end-to-end resource scheme 3. If business message 220 is associated with resource document 1, then the two end-to-end resource schemes stored in resource document 1 can be obtained, and the intersection of the two schemes forms a virtual resource processing scheme that matches business message 220.

[0094] In some embodiments, at least one virtual resource document associated with at least one business message can be determined based on the upstream and downstream relationships between at least one business message, and a target virtual resource processing scheme can be generated based on the virtual resource document. It is understood that if a virtual resource processing scheme can be determined based on a resource document, that virtual resource processing scheme can be directly identified as the target virtual resource processing scheme. If multiple virtual resource processing schemes can be determined, their intersection can be taken. For example, based on resource document 1 and resource document 2 shown in Figure 8, the target virtual resource processing scheme, micro-end-to-end resource scheme 2, can be determined. Alternatively or additionally, if no intersection is found, the process can enter a delay queue or report an error.

[0095] In step 422, the resource capability layer 260 can control the execution of actions in at least one target resource processing plugin based on the configuration information of the target virtual resource processing scheme. In step 423, the resource capability layer 260 can execute specific business logic and resource orchestration business according to the protocol. Specifically, the resource capability layer 260 can execute specific resource actions, complete downstream calls, and execute the final resource business logic based on the default rules and configuration information of the target virtual resource processing scheme. Taking the accounting and bookkeeping action as an example, the execution rules of different resource processing plugins are different. The actions of each resource processing plugin are relatively fixed, but the differences in the specific logic will be implemented according to the configuration information in the target virtual resource processing scheme.

[0096] This allows us to determine the target virtual resource processing scheme, at least one target resource processing plugin, and the resource actions of each plugin. Based on this information, complete business flows and resource flows can be orchestrated. Business flows refer to the relationships between resource documents, while resource flows include virtual resource flows (e.g., internal account bookkeeping) and physical resource flows (e.g., inter-entity transactions, bank deposit transfers, etc.). End-to-end resource flows can be used to verify accounts and documents, ensuring data quality. Resource traceability capabilities can be built to quickly locate and troubleshoot problems.

[0097] The details of orchestrating resource links are described below with reference to FIG9. FIG9 shows an example diagram of signaling flow 900 for orchestrating resource links according to some embodiments of the present disclosure. Signaling flow 900 relates to service system 120, resource capability layer 260, and resource data layer 402.

[0098] As shown in Figure 9, at step 901, the business system 120 sends at least one business message to the resource capability layer 260. At step 902, the resource capability layer 260 can match a virtual resource processing scheme and perform orchestration.

[0099] In some embodiments, in response to determining the completion of a virtual resource processing action by at least one target resource processing plugin, the resource capability layer 260 may trigger a data recording event associated with the virtual resource. For example, at step 903, the resource capability layer 260 may send a resource event to the resource data layer 402. The resource event may also correspond to a resource capability, that is, to a resource processing plugin.

[0100] Furthermore, the resource capability layer 260 can record at least one virtual resource flow corresponding to each target resource processing component based on recording rules matching data recording events and configuration information related to the inflow and outflow entities involved in the virtual resource. For example, at step 904, the resource capability layer 260 can record a first virtual resource flow (also referred to as a virtual resource flow) according to accounting rules. At step 905, the resource capability layer 260 can record a second virtual resource flow (also referred to as an entity resource flow) according to inflow, outflow, and inter-entity protocols. At step 906, the resource data layer 402 can complete the first virtual resource flow under the resource link, and at step 907, the resource data layer 402 can complete the second virtual resource flow under the resource link.

[0101] Referring to Figure 10, Figure 10 illustrates an example 1000 of a resource flow according to some embodiments of the present disclosure. As shown in Figure 10, taking virtual resources including funds as an example, the resource capability layer 260 includes a fund event 1011 and an accounting rule 1012. The resource capability layer 260 can record a virtual fund flow 1013 based on the accounting rule 1012. Accounting 1010 may include, for example, accounting entries 1021, internal accounts 1022, and internal account balances 1023. Accounting entries 1024 can be determined based on virtual fund flows 1013 and internal accounts 1022, and internal account balances 1023 can be determined based on accounting entries 1021. Thus, after matching resource events with accounting rules, the virtual resource flow corresponding to each resource processing plugin can be clearly defined. Through virtual resource flows, the connection between resource events and accounting entries can be completed.

[0102] Resource events can be recorded as resource flow models based on inflows, outflows, and inter-subject protocols associated in a virtual resource processing scheme. This allows for the connection of resource events to systems such as billing based on the resource flow. Referring to Figure 11, Figure 11 illustrates an example 1100 of recording a resource flow model according to some embodiments of this disclosure. Taking virtual resources including funds as an example, example 1100 involves fund management 1110 and a fund model 1120. Fund management 1110 may include, for example, fund events 1114 and fund schemes 1115, where fund scheme 1115 can be determined based on inflow protocol 1111, outflow protocol 1112, and inter-subject protocol 1113. Entity fund flows 1116 corresponding to fund scheme 1115 and fund events 1114 can be recorded. Entity fund flows 1116 can be recorded in the fund model 1120. Fund model 1120 may include, for example, settlement allocation 1121, incoming bill 1122, and passive clearing summary 1123 corresponding to entity fund flows 1116. Therefore, the funds database can store physical and virtual fund flow models, and can associate the stored models with corresponding fund events.

[0103] Referring back to Figure 9, in some embodiments, a visualization view (i.e., a complete resource link) corresponding to at least one virtual resource flow can be generated based on the association between at least one business message and the association between the business systems corresponding to at least one business message. Specifically, in step 908, the resource data layer 402 can orchestrate resource links based on resource events. In step 909, the resource data layer 402 can generate a visualization view corresponding to the virtual resource flow. Referring to Figure 12, Figure 12 shows an example 1200 of the visualization view corresponding to the virtual resource flow. The dashed lines in example 1200 represent the complete resource link. The resource link can connect the information flow, virtual resource flow, and physical resource flow of the entire business link, enabling traceability and verification between business data and resources across the entire domain.

[0104] Traditionally, due to the complexity of the financial sector and the isolation between different areas, data across various fields has been relatively fragmented. However, in the actual process of locating problems, data needs to be correlated and traced. For example, it is necessary to find related transaction details based on channel settlement statements; or to find the accounting results of related transactions based on a specific loan entry. Previously, tracing such correlated data required collaborative location and investigation by R&D teams from different fields, resulting in low overall efficiency and indirectly leading to numerous problems. The solution disclosed in this paper, through financial chain orchestration, connects transaction data with data from various financial sectors. By unifying data, it improves the efficiency of problem investigation, testing efficiency and quality, and indirectly promotes overall quality improvement.

[0105] In summary, according to the embodiments of this disclosure, orchestration of virtual resource processing schemes, resource processing plugins, and resource links can be achieved, reducing business management costs, enabling unified information configuration, and improving configuration efficiency. It can reduce business complexity and improve processing efficiency. It can construct end-to-end resource flows, improving overall data quality and problem localization efficiency. It can improve the quality and efficiency of business processing.

[0106] Figure 13 shows a flowchart of a method 1300 for business processing according to some embodiments of the present disclosure. Method 1300 may be implemented at a resource orchestration system 110.

[0107] In box 1310, resource orchestration system 110, in response to receiving at least one business message related to a business event, determines a virtual resource processing scheme that matches the at least one business message, the business event being configured to trigger the processing of the virtual resource.

[0108] In box 1320, resource orchestration system 110 determines at least one target resource processing plugin from a set of candidate resource processing plugins based on a virtual resource processing scheme and at least one business message, each resource processing plugin being configured to perform at least one action related to virtual resource processing.

[0109] In box 1330, resource orchestration system 110 generates a calling scheme for at least one target resource processing plugin based on at least one business message.

[0110] In box 1340, resource orchestration system 110 invokes at least one target resource processing plugin based on an invocation scheme.

[0111] In box 1350, resource orchestration system 110 provides a response to at least one business message based on the invocation result of at least one target resource processing plugin.

[0112] In some embodiments, determining a virtual resource processing scheme that matches at least one business message includes: determining at least one resource component associated with at least one business message, each resource component being associated with a business type and including a definition of a resource processing object for the business type; and selecting a virtual resource processing scheme that includes at least one resource component from a pre-configured set of candidate virtual resource processing schemes.

[0113] In some embodiments, determining at least one resource component associated with at least one business message includes: determining at least one of a business scenario type and a virtual resource processing type corresponding to at least one business message; extracting business configuration information from at least one business message; and determining at least one resource component based on at least one of the business scenario type and the virtual resource processing type, and the business configuration information.

[0114] In some embodiments, each resource component may be included in one or more candidate virtual resource processing schemes.

[0115] In some embodiments, determining at least one target resource processing plugin includes: determining at least one target resource processing plugin from a set of candidate resource processing plugins based on at least one business message and at least one resource component included in the virtual resource processing scheme.

[0116] In some embodiments, generating an invocation scheme for at least one target resource processing plugin includes: generating an invocation scheme for at least one target resource processing plugin based on the configuration information of the virtual resource processing scheme and the plugin dependencies of at least one target resource processing plugin, wherein the invocation scheme indicates at least one of the following: the execution order of at least one target resource processing plugin, the capability invocation topology of one or more target resource processing plugins, and the invocation parameters of each target resource processing plugin.

[0117] In some embodiments, invoking at least one target resource processing plugin based on an invocation scheme includes: determining at least one virtual resource document associated with at least one business message based on the upstream and downstream relationship between at least one business message; generating a target virtual resource processing scheme based on the virtual resource document, wherein each virtual resource document corresponds to a resource component and indicates one or more candidate virtual resource processing schemes containing the resource component; and controlling the execution of actions in at least one target resource processing plugin based on the configuration information of the target virtual resource processing scheme.

[0118] In some embodiments, providing a response to at least one business message includes: triggering a data recording event related to the virtual resource in response to determining the completion of the virtual resource processing action of at least one target resource processing plugin; and recording at least one virtual resource flow corresponding to each target resource processing component based on the recording rules matching the data recording event and the configuration information related to the inflow and outflow subjects involved in the virtual resource.

[0119] In some embodiments, providing a response to at least one business message further includes generating a visualization view corresponding to at least one virtual resource stream based on the association between at least one business message and the association between the business systems corresponding to at least one business message.

[0120] Embodiments of this disclosure also provide corresponding apparatus for implementing the methods or processes described above. FIG14 shows an exemplary structural block diagram of an apparatus 1400 for business processing according to some embodiments of this disclosure. Apparatus 1400 may be implemented as or included in resource orchestration system 110. Various modules / components in apparatus 1400 may be implemented by hardware, software, firmware, or any combination thereof.

[0121] As shown in Figure 14, the apparatus 1400 includes a scheme determination module 1410, configured to determine a virtual resource processing scheme matching the at least one business message in response to receiving at least one business message related to a business event, wherein the business event is configured to trigger virtual resource processing. The apparatus 1400 also includes a plug-in determination module 1420, configured to determine at least one target resource processing plug-in from a set of candidate resource processing plug-ins based on the virtual resource processing scheme and the at least one business message, wherein each resource processing plug-in is configured to perform at least one action related to virtual resource processing. The apparatus 1400 further includes a scheme generation module 1430, configured to generate a calling scheme for the at least one target resource processing plug-in based on the at least one business message. The apparatus 1400 also includes a plug-in calling module 1440, configured to call the at least one target resource processing plug-in based on the calling scheme. The apparatus 1400 further includes a response providing module 1450, configured to provide a response to the at least one business message based on the calling result of the at least one target resource processing plug-in.

[0122] In some embodiments, the scheme determination module 1410 is further configured to: determine at least one resource component associated with at least one business message, each resource component being associated with a business type and including a definition of a resource processing object for the business type; and select a virtual resource processing scheme that includes at least one resource component from a pre-configured set of candidate virtual resource processing schemes.

[0123] In some embodiments, the scheme determination module 1410 is further configured to: determine at least one of a business scenario type and a virtual resource processing type corresponding to at least one business message; extract business configuration information from at least one business message; and determine at least one resource component based on at least one of the business scenario type and the virtual resource processing type, and the business configuration information.

[0124] In some embodiments, each resource component may be included in one or more candidate virtual resource processing schemes.

[0125] In some embodiments, the scheme determination module 1410 is further configured to: determine at least one target resource processing plugin from a set of candidate resource processing plugins based on at least one business message and at least one resource component included in the virtual resource processing scheme.

[0126] In some embodiments, the scheme generation module 1430 is further configured to: generate a calling scheme for at least one target resource processing plugin based on the configuration information of the virtual resource processing scheme and the plugin dependencies of at least one target resource processing plugin, wherein the calling scheme indicates at least one of the following: the execution order of at least one target resource processing plugin, the capability calling topology of one or more target resource processing plugins, and the calling parameters of each target resource processing plugin.

[0127] In some embodiments, the plugin invocation module 1440 is further configured to: determine at least one virtual resource document associated with at least one business message based on the upstream and downstream relationship between at least one business message; generate a target virtual resource processing scheme based on the virtual resource document, wherein each virtual resource document corresponds to a resource component and indicates one or more candidate virtual resource processing schemes containing the resource component; and control the execution of actions in at least one target resource processing plugin based on the configuration information of the target virtual resource processing scheme.

[0128] In some embodiments, the response providing module 1450 is further configured to: trigger a data recording event related to the virtual resource in response to the completion of the virtual resource processing action of at least one target resource processing plugin; and record at least one virtual resource flow corresponding to each target resource processing component based on the recording rules matching the data recording event and the configuration information related to the inflow and outflow subjects involved in the virtual resource.

[0129] In some embodiments, the response providing module 1450 is further configured to generate a visual view corresponding to at least one virtual resource stream based on the association between at least one business message and the association between the business systems corresponding to at least one business message.

[0130] The units and / or modules included in device 1400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units and / or modules can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units and / or modules in device 1400 can be implemented at least partially by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0131] It should be understood that one or more steps in the above methods can be performed by appropriate electronic devices or combinations of electronic devices. Such electronic devices or combinations of electronic devices may, for example, include the resource orchestration system 110 in Figure 1.

[0132] Figure 15 shows a block diagram of an electronic device 1500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 1500 shown in Figure 15 is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. The electronic device 1500 shown in Figure 15 can be used to implement the resource orchestration system 110 of Figure 1 or the apparatus 1400 of Figure 14.

[0133] As shown in Figure 15, electronic device 1500 is in the form of a general-purpose electronic device. Components of electronic device 1500 may include, but are not limited to, one or more processors or processing units 1510, memory 1520, storage device 1530, one or more communication units 1540, one or more input devices 1550, and one or more output devices 1560. Processing unit 1510 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 1520. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 1500.

[0134] Electronic device 1500 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 1500, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 1520 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 1530 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data and can be accessed within electronic device 1500.

[0135] Electronic device 1500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 15, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks may be provided. In these cases, each drive may be connected to a bus (not shown) via one or more data media interfaces. Memory 1520 may include computer program product 1525 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

[0136] The communication unit 1540 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 1500 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 1500 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0137] Input device 1550 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 1560 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 1500 can also communicate with one or more external devices (not shown) via communication unit 1540 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 1500, or with any device that enables electronic device 1500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0138] According to an exemplary implementation of this disclosure, a computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. According to an exemplary implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.

[0139] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. 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-readable program instructions.

[0140] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0141] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

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

[0143] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for service processing, comprising: determining a virtual resource processing scheme matching the at least one service message in response to receiving at least one service message related to a service event, the service event being configured to trigger processing of a virtual resource; determining at least one target resource processing plug-in from a set of candidate resource processing plug-ins based on the virtual resource processing scheme and the at least one service message, each resource processing plug-in being configured to perform at least one action related to virtual resource processing; generating a calling scheme of the at least one target resource processing plug-in based on the at least one service message; invoking the at least one target resource processing plug-in based on the calling scheme; and providing a response to the at least one service message based on an invocation result of the at least one target resource processing plug-in. 2.The method of claim 1, wherein determining a virtual resource processing scheme matching the at least one service message comprises: determining at least one resource component associated with the at least one service message, each resource component being associated with a service type and comprising a definition of a resource processing object for the service type; selecting a virtual resource processing scheme comprising at least the at least one resource component from a pre-configured set of candidate virtual resource processing schemes. 3.The method of claim 2, wherein determining at least one resource component associated with the at least one service message comprises: determining at least one of a service scenario type and a virtual resource processing type corresponding to the at least one service message; extracting service configuration information from the at least one service message; and determining the at least one resource component based on at least one of the service scenario type and the virtual resource processing type, and the service configuration information. 4.The method of claim 2, wherein each resource component can be included in one or more candidate virtual resource processing schemes. 5.The method of claim 2, wherein determining at least one target resource processing plug-in comprises: determining at least one target resource processing plug-in from a set of candidate resource processing plug-ins based on the at least one service message and the at least one resource component included in the virtual resource processing scheme. 6.The method of claim 1, wherein generating a calling scheme of the at least one target resource processing plug-in comprises: generating the calling scheme of the at least one target resource processing plug-in based on configuration information of the virtual resource processing scheme and plug-in dependency relationships of the at least one target resource processing plug-in, wherein the calling scheme indicates at least one of: an execution order of the at least one target resource processing plug-in, a capability calling topology of one or more target resource processing plug-ins, and a calling parameter of each target resource processing plug-in. 7.The method of claim 1, wherein invoking the at least one target resource processing plug-in based on the calling scheme comprises: determining a virtual resource document associated with the at least one service message based on an upstream-downstream relationship between the at least one service message. ​ ​ ​ ​ ​ generating a target virtual resource processing scheme based on the virtual resource bill, each virtual resource bill corresponding to a resource component and indicating one or more candidate virtual resource processing schemes containing the resource component; and controlling execution of actions in the at least one target resource processing plug-in based on configuration information of the target virtual resource processing scheme.

8. The method of claim 1, wherein providing a response to the at least one business message comprises: triggering a data recording event related to a virtual resource in response to determining completion of actions of virtual resource processing of the at least one target resource processing plug-in; and recording at least one virtual resource flow corresponding to each target resource processing component based on a recording rule matching the data recording event and configuration information related to inflow and outflow subjects involved in the virtual resource.

9. The method of claim 8, wherein providing a response to the at least one business message further comprises: generating a visual view corresponding to the at least one virtual resource flow based on associations between the at least one business message and associations between business systems corresponding to the at least one business message.

10. An apparatus for business processing, comprising: a scheme determination module configured to determine a virtual resource processing scheme matching at least one business message related to a business event in response to receiving the at least one business message, the business event being configured to trigger processing of a virtual resource; a plug-in determination module configured to determine at least one target resource processing plug-in from a set of candidate resource processing plug-ins based on the virtual resource processing scheme and the at least one business message, each resource processing plug-in being configured to perform at least one action related to processing of a virtual resource; a scheme generation module configured to generate a calling scheme of the at least one target resource processing plug-in based on the at least one business message; a plug-in calling module configured to call the at least one target resource processing plug-in based on the calling scheme; and a response providing module configured to provide a response to the at least one business message based on a calling result of the at least one target resource processing plug-in.

11. An electronic device, comprising: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, cause the electronic device to perform the method of any of claims 1-9.

12. A computer-readable storage medium having stored thereon a computer program, the computer program being executable by a processor to implement the method of any of claims 1-9.

13. A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method of any of claims 1-9. ​ ​

Images