Method and apparatus for resource scheduling based on a scheduling network

Abstract

Embodiments of the present specification provide a method and device for resource scheduling based on a scheduling network. The method is used to realize resource scheduling between different accounts by using the scheduling network. The scheduling network represents the association relationship between a plurality of accounts and includes a plurality of account nodes and connection edges between the account nodes. An execution subject receives a resource scheduling request, and the resource scheduling request is used to request the import or export of resources for a first account. Then, the execution subject can determine a plurality of second account nodes associated with the first account node from the scheduling network, and determine a plurality of target account nodes from the plurality of second account nodes based on the account information corresponding to the account nodes. Finally, based on the plurality of target account nodes, the resource scheduling between the first account and the plurality of target accounts is performed.

Description

Technical Field

[0001] This specification relates to the field of computer technology in one or more embodiments, and in particular to a method and apparatus for resource scheduling based on a scheduling network. Background Technology

[0002] In large corporations, resource allocation typically involves multiple accounts across multiple entities. These entities can be, for example, subsidiaries. Each account, as a resource carrier, holds the resources belonging to that entity. The group needs centralized management of these multiple entities' resources to ensure their full utilization. However, centralized management of resources across multiple entities usually requires manual analysis and allocation of funds, which is inefficient.

[0003] Therefore, we hope to find an improved solution that can more efficiently allocate resources across multiple accounts. Summary of the Invention

[0004] This specification describes one or more embodiments of a method and apparatus for resource scheduling based on a scheduling network, so as to achieve more efficient and reasonable scheduling of resources for multiple accounts. The specific technical solution is as follows.

[0005] In a first aspect, an embodiment provides a method for resource scheduling based on a scheduling network, used to realize resource scheduling between different accounts using the scheduling network, wherein the scheduling network represents the association relationship between multiple accounts and includes multiple account nodes and connection edges between account nodes; the method is executed by a computer and includes:

[0006] Receive a resource scheduling request, the resource scheduling request being used to request resource scheduling for the first account;

[0007] Identify several second account nodes from the scheduling network that are associated with the first account node;

[0008] Based on the account information corresponding to the account nodes, several target account nodes are determined from the several second account nodes;

[0009] Based on the aforementioned target account nodes, resource scheduling is performed between the first account and the target accounts.

[0010] In one implementation, the resource scheduling request is used to request resource scheduling of a first amount of resources for the first account; the account information of any account node includes the rate of change of resource gain when the resources are scheduled.

[0011] In one implementation, the step of determining a plurality of target account nodes from the plurality of second account nodes based on the account information corresponding to the account nodes includes:

[0012] Based on the first resource quantity and the change rate corresponding to the plurality of second account nodes, a plurality of target account nodes and corresponding resource scheduling quantities are determined from the plurality of second account nodes, so that the total resource gain quantity meets the preset conditions; the total resource gain quantity is determined based on the corresponding change rate and resource scheduling quantity.

[0013] In one implementation, the plurality of target account nodes includes a third account node, and the resources of the corresponding third account include the second resource quantity that has not yet been credited.

[0014] The step of performing resource scheduling between the first account and the plurality of target accounts based on the plurality of target account nodes includes:

[0015] Perform resource scheduling between the third account and the fourth account, so that the third account obtains the second amount of resources;

[0016] Based on the second resource quantity, resource scheduling is performed between the first account and the third account.

[0017] In one implementation, an account belongs to a corresponding institution, and multiple accounts correspond to different institutions; the association is used to characterize the contractual relationship between the institutions corresponding to the accounts.

[0018] In one implementation, the account information of any account node includes resource scheduling restrictions, which include at least one of the following:

[0019] The first resource scheduling limit set for the institution corresponding to the account node is used to limit the overall scheduling of several accounts corresponding to the institution;

[0020] The second resource scheduling restriction is set for the account corresponding to this account node.

[0021] In one implementation, the step of determining a plurality of target account nodes from the plurality of second account nodes based on the account information corresponding to the account nodes includes:

[0022] From the plurality of second account nodes, determine a plurality of target account nodes that meet the corresponding resource scheduling restrictions.

[0023] In one implementation, the scheduling network is a directed network; any connection edge contains resource flow information; the resource scheduling request carries first resource flow information for the first account;

[0024] The step of determining a plurality of second account nodes that are associated with the first account node from the scheduling network includes:

[0025] Several account nodes in the scheduling network that are associated with the first account node and whose resource flow information of the connection edge between them and the first account node is consistent with the first resource flow information are identified as second account nodes.

[0026] In one implementation, the step of performing resource scheduling between the first account and the plurality of target accounts based on the plurality of target account nodes includes:

[0027] Several transactions are submitted to the blockchain network. These transactions are generated based on resource scheduling between the first account and several target accounts, each of which corresponds to a target account node.

[0028] In one implementation, accounts belong to users, different accounts correspond to different users, and the association relationship is used to characterize the relationship between users corresponding to accounts.

[0029] Alternatively, multiple accounts may belong to the same organization, with different accounts corresponding to different business operations within that organization. The association relationship is used to characterize the relationship between the business operations corresponding to the accounts.

[0030] Secondly, the embodiment provides an apparatus for resource scheduling based on a scheduling network, used to realize resource scheduling between different accounts using the scheduling network, wherein the scheduling network represents the association relationship between multiple accounts and includes multiple account nodes and connection edges between account nodes; the apparatus is deployed in a computer and includes:

[0031] The request receiving module is configured to receive a resource scheduling request, wherein the resource scheduling request is used to request resource scheduling for a first account.

[0032] The node determination module is configured to determine, from the scheduling network, several second account nodes that are associated with the first account node;

[0033] The target determination module is configured to determine several target account nodes from the several second account nodes based on the account information corresponding to the account nodes;

[0034] The resource scheduling module is configured to perform resource scheduling between the first account and the target accounts based on the target account nodes.

[0035] In one implementation, the resource scheduling request is used to request resource scheduling of a first amount of resources for the first account; the account information of any account node includes the rate of change of resource gain when the resources are scheduled.

[0036] In one implementation, the target determination module is specifically configured as follows:

[0037] Based on the first resource quantity and the change rate corresponding to the plurality of second account nodes, a plurality of target account nodes and corresponding resource scheduling quantities are determined from the plurality of second account nodes, so that the total resource gain quantity meets the preset conditions; the total resource gain quantity is determined based on the corresponding change rate and resource scheduling quantity.

[0038] In one implementation, an account belongs to a corresponding institution, and multiple accounts correspond to different institutions; the association is used to characterize the contractual relationship between the institutions corresponding to the accounts.

[0039] In one implementation, the account information of any account node includes resource scheduling restrictions, which include at least one of the following:

[0040] The first resource scheduling limit set for the institution corresponding to the account node is used to limit the overall scheduling of several accounts corresponding to the institution;

[0041] The second resource scheduling restriction is set for the account corresponding to this account node.

[0042] In one implementation, the target determination module is specifically configured as follows:

[0043] From the plurality of second account nodes, determine a plurality of target account nodes that meet the corresponding resource scheduling restrictions.

[0044] Thirdly, the embodiment provides a system for resource scheduling based on a scheduling network, used to realize resource scheduling between different accounts using the scheduling network. The scheduling network represents the association relationship between multiple accounts and includes multiple account nodes and connection edges between account nodes. Accounts belong to corresponding institutions, and multiple accounts correspond to different institutions. The system includes a scheduling platform and multiple institutional devices.

[0045] The scheduling platform is configured to receive resource scheduling requests, which request resource scheduling for a first account; determine several second account nodes that are associated with the first account node from the scheduling network; determine several target account nodes from the several second account nodes based on the account information corresponding to the account nodes; and send resource scheduling instructions to the corresponding institutional equipment based on the several target account nodes.

[0046] The aforementioned equipment is used to receive resource scheduling instructions sent by the scheduling platform and to execute resource scheduling between the first account and several target accounts.

[0047] Fourthly, an embodiment provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method described in any one of the first aspects.

[0048] Fifthly, an embodiment provides a computing device including a memory and a processor, wherein the memory stores executable code, and the processor, when executing the executable code, implements the method described in any one of the first aspects.

[0049] In the methods and apparatus provided in the embodiments of this specification, when resource scheduling is required for a first account, several second account nodes can be determined by utilizing the association relationships between account nodes in the scheduling network. Based on account information, a target account node is determined from the second account nodes, and resource scheduling between the first account and the target account is executed. By using a computer to perform the above process, the account for resource scheduling of the first account can be quickly determined, and the connection relationships between account nodes in the scheduling network improve the process of determining account nodes. Therefore, it is possible to achieve more efficient and reasonable resource scheduling for multiple accounts. Attached Figure Description

[0050] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0051] Figure 1 This is a schematic diagram illustrating an implementation scenario of one embodiment disclosed in this specification;

[0052] Figure 2 A flowchart illustrating a method for resource scheduling based on a scheduling network, provided as an embodiment;

[0053] Figure 3 The diagram illustrates the relationship between account nodes, enterprises, and fund management institutions.

[0054] Figure 4 A schematic block diagram of a device for resource scheduling based on a scheduling network, provided for an embodiment;

[0055] Figure 5 This is a schematic block diagram of a system for resource scheduling based on a scheduling network, provided as an example. Detailed Implementation

[0056] The solution provided in this specification will now be described with reference to the accompanying drawings.

[0057] Figure 1 This is a schematic diagram illustrating an implementation scenario of one embodiment disclosed in this specification. It includes a scheduling platform and institutional devices. There can be two or more institutional devices. The institutional devices can send resource scheduling requests to the scheduling platform. The scheduling platform can determine the target account based on the resource scheduling request and the scheduling network, and send resource scheduling instructions to the corresponding institutional devices. The institutional devices then execute the resource scheduling, performing resource scheduling between different accounts. Figure 1 The illustration shown is merely an implementation scenario of one embodiment provided in this specification and does not constitute a limitation of this specification. Figure 1 The number of account nodes in the scheduling network shown is just one example.

[0058] The scheduling platform can be implemented using servers or other devices with certain computing capabilities. Institutional equipment, which corresponds to an institution, can be implemented using devices with certain computing power, clusters, etc.

[0059] The aforementioned account is a resource carrier, a tool used to hold and transfer resources. Resources can be diverse; any valuable object that can be represented in a certain form and can be transferred and scheduled can be called a resource. For example, resources can include funds, data traffic, carbon emissions, etc.

[0060] Accounts can belong to an organization, and multiple accounts can belong to different organizations. Multiple accounts corresponding to different organizations include: different accounts corresponding to different organizations, with a one-to-one correspondence between accounts and organizations; or, an organization can have one or more accounts, with all accounts corresponding to multiple organizations. Organizations perform data processing tasks through their corresponding organizational equipment. Organizations can include enterprises and public institutions. Enterprises can include companies, factories, farms, shops, etc., while public institutions can include schools, hospitals, research institutes, etc.

[0061] In one application scenario, within a large corporation, multiple subsidiaries may each have their own accounts. To maximize resource utilization efficiency, the corporation needs to centrally manage the resources within each subsidiary's accounts.

[0062] In another application scenario, multiple companies have cooperative relationships, and there may be resource allocation needs among these companies. For example, company A purchases services from company B, and company A needs to pay funds to company B's account.

[0063] In the above application scenarios, the account represents resources that can be allocated, such as funds or carbon emissions. A company's account can be either a financial account or a carbon emissions account. Having different carbon emissions means that a company can have different compliant production capacities. Allocating carbon emissions among different companies can optimize the resources of multiple companies.

[0064] Accounts can also belong to users, with different accounts belonging to different users. These accounts can also be user accounts, i.e., personal accounts. User accounts can be financial accounts (holding funds) or data traffic accounts (holding data flow). There is also a need for multiple users to rationally utilize and allocate resources.

[0065] Multiple accounts can belong to the same organization and correspond to different business operations. This includes situations where different accounts correspond to different business operations, with a one-to-one correspondence between accounts and business operations; or, one or more accounts can correspond to a single business operation, with all accounts covering multiple business operations. For example, accounts 1, 2, 3, and 4 belong to the same company. Funds in accounts 1 and 2 are used for new product research and development, funds in account 3 are used to repay loans, and funds in account 4 are used to pay salaries. This is just an example; in practice, the number of accounts can be very large.

[0066] To achieve more efficient and reasonable resource scheduling across multiple accounts, this specification provides a method for resource scheduling based on a scheduling network. In this method, the executing entity performs the following steps: Step S210, receiving a resource scheduling request; Step S220, determining several second account nodes associated with a first account node from the scheduling network; Step S230, determining several target account nodes from the several second account nodes based on the account information corresponding to the account nodes; Step S240, performing resource scheduling between the first account and the several target accounts based on the several target account nodes. This method utilizes the multiple account nodes included in the scheduling network and their associated relationships to quickly and reasonably determine the accounts to be scheduled with the first account, improving the processing efficiency of resource scheduling. The following detailed embodiments further illustrate this application.

[0067] Figure 2 This is a flowchart illustrating a method for resource scheduling based on a scheduling network, provided as an embodiment. This method can be executed by a computer; for example, the executing entity can be any device, equipment, platform, or device cluster with computing and processing capabilities. Figure 1 In the implementation scenario shown, the method can be executed by the scheduling platform, or it can be executed jointly by the scheduling platform and the institutional equipment.

[0068] This method utilizes a scheduling network to schedule resources between different accounts. An account is an object used to hold resources and perform operations such as storing and transferring those resources. Resources can be scheduled between different accounts.

[0069] The scheduling network is used to represent the relationships between multiple accounts and includes multiple account nodes and the connecting edges between them. There is a one-to-one correspondence between accounts and account nodes; an account node represents the account in the scheduling network. The relationships between accounts are the relationships between the corresponding account nodes. In different application scenarios, accounts can have different relationships. When multiple accounts correspond to different institutions, the relationships between accounts can reflect the contractual relationships between the institutions, such as service procurement relationships, equity relationships, or related lending relationships. When different accounts correspond to different users, the relationships between accounts can reflect the relationships between the users, such as friendships, tenant-landlord relationships, or parent-child relationships. When multiple accounts correspond to the same institution (e.g., a company), and different accounts correspond to different business operations within that institution, the relationships between accounts can reflect the relationships between the corresponding business operations.

[0070] Any account can have corresponding account information, which is also the account information of the corresponding account node.

[0071] Account information may include remaining resources, available resources, the rate of change of resource gain when resources are scheduled, and resource scheduling restrictions. When resources are in storage, they can have a certain rate of gain. For example, the yield on demand deposits or time deposits; unused carbon emissions over different periods will also generate incremental returns, thus encouraging the reduction of carbon emissions. Remaining resources can have different resource gains depending on the storage period. Correspondingly, resource gains may change when resources are scheduled. The aforementioned rates of change include loss rates and growth rates. For example, for funds in demand deposit status, if these funds are transferred out of the account, the rate of change of their gain is the loss rate, and the value of the loss rate is the demand deposit interest rate; if some funds are transferred into the account, the rate of change of their gain is the growth rate, and the value of the growth rate is the demand deposit interest rate. The basic information of the account changes with resource scheduling.

[0072] Resource scheduling limits can be restrictions set for resource scheduling of a specific account. For example, resource scheduling limits may include the maximum amount of resource scheduling for the account, the minimum amount of resource scheduling, and the maximum number of resource scheduling attempts within a specified time period.

[0073] The scheduling network can be pre-built based on multiple accounts and their relationships. The scheduling network can be built within the executing entity or on other devices. After construction, the scheduling network can be stored locally within the executing entity or on other devices.

[0074] The method in this embodiment includes the following steps S210 to S240.

[0075] Step S210: Receive a resource scheduling request, which requests resource scheduling for a first account (e.g., Ac1). The resource scheduling request may carry the identifier Ac1 of the first account.

[0076] In different implementation scenarios, the entity sending the resource scheduling request can be different. For example, in Figure 1 In the illustrated implementation scenario, the resource scheduling request can be sent from an institutional device to the scheduling platform. When the account is a user account, the resource scheduling request can also be sent by the device to the executing entity based on the user's input. Of course, the executing entity itself can also receive the resource scheduling request triggered by the user's input.

[0077] In one implementation, the resource scheduling request can specifically be used to request resource scheduling of a first resource quantity Q1 for a first account Ac1, and can also carry first resource flow information D1 for the first account Ac1. The first resource flow information D1 includes both inflow and outflow flow information. For example, the resource scheduling request can be used to request the transfer of the first resource quantity Q1 to the first account Ac1, or the resource scheduling request can be used to request the transfer of the first resource quantity Q1 from the first account Ac1.

[0078] The resource scheduling request may also omit the aforementioned first resource quantity Q1 and first resource flow information D1. Instead, the first resource quantity Q1 and first resource flow information D1 can be pre-set and stored as default settings in the execution entity. When the execution entity receives the resource scheduling request, it executes the subsequent process according to the default settings.

[0079] Resource scheduling requests can also carry specified associations. There can be multiple associations associated with the first account node, and the specified association is one or more of these associations.

[0080] In implementation scenarios where multiple accounts correspond to different institutions, resource scheduling requests can also carry a designated institution for resource scheduling of the first account Ac1. That is, the account of this designated institution is the object of resource scheduling with the first account Ac1, and this designated institution can have multiple accounts. Furthermore, there is an association relationship between this designated institution and the institution corresponding to the first account Ac1.

[0081] Step S220: Determine several second account nodes A2 that are associated with the first account node A1 from the scheduling network. The first account A1 corresponds to the first account node A1 in the scheduling network. The number of second account nodes A2 can be one or more.

[0082] When a resource scheduling request carries a specified association, several second account nodes A2 that have a specified association with the first account node A1 can be identified from the scheduling network. When a resource scheduling request carries a specified organization, the account nodes belonging to that specified organization in the scheduling network can be identified as second account nodes A2.

[0083] by Figure 1 Taking the scheduling network shown as an example, assuming that account node 1 represents the first account node A1, the second account nodes that are associated with A1 in the scheduling network include: account node 2, account node 3, account node 5 and account node 6.

[0084] When the scheduling network is stored locally on the execution entity, the execution entity can directly execute this step S220 locally. When the scheduling network is stored on other devices, the execution entity can send resource scheduling requests to other devices and receive feedback from several second account nodes from other devices.

[0085] Step S230: Based on the account information corresponding to the account nodes, determine several target account nodes TA from several second account nodes A2. There can be only one target account node TA, or two or more, or all the second account nodes.

[0086] When the account information includes available resources, the target account node TA can be determined based on the available resources of the second account node A2. For example, the target account node TA can be determined from several second account nodes A2 whose available resources are not less than the first resource Q1.

[0087] When the account information of any account node includes the rate of change of resource gain when resources are scheduled (denoted by η), and the resource scheduling request carries a first resource quantity Q1, when determining several target account nodes TA from several second account nodes A2, several target account nodes TA and corresponding resource scheduling quantities q can be determined from several second account nodes A2 based on the first resource quantity Q1 and the rate of change η corresponding to several second account nodes A2, so that the total resource gain W meets the preset conditions.

[0088] The total resource gain W is determined based on the corresponding rate of change and resource scheduling amount. It represents the total resource gain corresponding to the scheduled resources when the resources of several target account nodes TA are each scheduled with a corresponding resource scheduling amount q. This includes both total resource loss and total resource growth. The sum of the resource scheduling amounts q of several target account nodes TA equals the first resource amount Q1. For example, when the target account nodes include TA1 and TA2, and their corresponding resource scheduling amounts are q1 and q2, and their corresponding rates of change are η1 and η2, then q1 + q2 = Q1. The total resource gain can be determined based on the product of the rate of change and the resource scheduling amount.

[0089] When the resource scheduling direction for the first account Ac1 is to transfer the first resource quantity Q1 to the first account Ac1, the change rate is the loss rate, and the total resource gain represents the total resource loss. In this case, the above preset condition may include: the total resource loss takes the minimum value.

[0090] When the resource scheduling direction for the first account Ac1 is to allocate the first resource quantity Q1 from the first account Ac1, the change rate is the growth rate, and the total resource gain represents the total resource growth. In this case, the above preset condition may include: the total resource growth takes the maximum value.

[0091] When determining several target account nodes TA, several second account nodes A2 can be sorted according to the aforementioned rate of change. Based on the sorting and the first resource quantity Q1, several combinations of account nodes can be determined. Each combination can contain only one second account node A2 or multiple second account nodes, and the total available resource quantity of the accounts in each combination is not less than the first resource quantity Q1. Then, the total resource gain of each combination is determined, and the second account node A2 in the combination that meets the preset conditions is determined as the target account node TA.

[0092] The above steps can filter out a more reasonable and optimized target account node from several second account nodes based on account information, so that the resource scheduling between the first account and the target account in subsequent steps is also an optimized result.

[0093] Step S240: Based on several target account nodes TA, perform resource scheduling between the first account Ac1 and several target accounts Tc. Each target account Tc corresponds to a different target account node TA.

[0094] exist Figure 1 In the illustrated scenario, when the executing entity is a scheduling platform, during this step, the scheduling platform can send resource scheduling instructions to the corresponding institutional devices. Upon receiving the resource scheduling instructions from the scheduling platform, the institutional devices perform resource scheduling between the first account Ac1 and several target accounts Tc.

[0095] For example, the first account Ac1 is the account of organization 1, corresponding to account node 1; the determined target account nodes include account node 2 of organization 2 and account node 3 of organization 3. The scheduling platform can then send resource scheduling instructions to the institutional devices of organization 1, organization 2, and organization 3. Upon receiving the resource scheduling instructions, the institutional devices of organizations 1, 2, and 3 execute resource scheduling between account 1 and accounts 2 and 3.

[0096] The resource scheduling command can carry the resource allocation amount for each account. When an organization receives a resource scheduling command, it can perform resource scheduling between accounts based on the allocated resource allocation amount. Of course, the resource scheduling command can also omit the resource allocation amount, which is the default setting.

[0097] When an account corresponds to a user, the scheduling platform can send resource scheduling instructions to the corresponding user equipment. Upon receiving the resource scheduling instructions from the scheduling platform, the user equipment executes resource scheduling between the first account Ac1 and several target accounts Tc.

[0098] Whether it's user equipment or institutional equipment, resource scheduling between a first account Ac1 and several target accounts Tc can be achieved using a blockchain network. Equipment (including institutional and user equipment) can submit several transactions to the blockchain network. These transactions are generated based on the resource scheduling between the first account Ac1 and each of the target accounts Tc. For example, when there are two target accounts Tc1 and Tc2, the first account Ac1 performs resource scheduling with both target accounts Tc1 and Tc2 respectively, thus requiring only two transactions.

[0099] For a first account Ac1 and any target account Tc, when generating a transaction, the first account Ac1 and the target account Tc can be designated as the initiator and recipient of the transaction, respectively, and the transaction content can include the amount of resources to be scheduled. The device can also submit the initiator's digital signature along with the transaction to the blockchain network.

[0100] Let's review steps S230 and S240. It is known that several target account nodes Tc include a third account node A3. The resources of the corresponding third account Ac3 include a second resource quantity Q2 that has not yet been credited. "Not yet credited" refers to resources that should have been credited at some point in the past, or resources that will be credited at some point in the future, but have not yet been credited at the current moment. This means that the resource will flow into the third account Ac3 at some point in the future. These uncredited resources and their quantities can be recorded in the account information corresponding to the account, and categorized under the remaining resources or available resources.

[0101] The aforementioned second resource quantity Q2 can be either the resource owed by the fourth account Ac4 to the third account Ac3, or the resource owed by other accounts to the third account Ac3.

[0102] Therefore, when executing step S240, resource scheduling between the third account Ac3 and the fourth account Ac4 can be performed first, allowing the third account to obtain the second resource quantity Q2. Then, based on the second resource quantity Q2, resource scheduling between the first account Ac1 and the third account Ac3 can be performed. During the above resource scheduling, a blockchain network can also be used to submit transactions to the blockchain network to achieve resource scheduling between accounts.

[0103] After step S240 is completed, the account information of the corresponding accounts can be updated. For example, the account information of the first account, the target account (including the third account), and the fourth account can be updated, including the remaining resources and available resources in the account information.

[0104] Since the relationships between account nodes and account information in the scheduling network are considered private data, the executing entities (including the scheduling platform) can process this private data within their trusted space. When interacting with other devices, encryption can be used to ensure the security of private data.

[0105] In another embodiment of the invention, accounts belong to corresponding institutions, and multiple accounts correspond to different institutions. This association can be used to characterize the contractual relationship between the institutions corresponding to the accounts. In this embodiment, institutions may include those for executing business operations and specialized institutions (resource management institutions) for storing and scheduling resources. For example, when the resource is funds, the institutions may include enterprises and fund management institutions. Fund management institutions include banks and third-party payment platforms, etc.

[0106] Taking funds as an example, Figure 3 This diagram illustrates the relationships between account nodes, enterprises, and fund management institutions. Each account node and its corresponding account belongs to either the enterprise and bank, or the enterprise and a third-party payment platform. Related account nodes are connected using edges.

[0107] Businesses, banks, and third-party payment platforms can set corresponding restrictions on fund transfers for accounts. For example, a business can set overall fund transfer restrictions for one or more of its accounts, or for any single account. These restrictions might include minimum and maximum fund retention levels, and the concentration of funds across different banks or third-party payment platforms. Banks or third-party payment platforms can also set restrictions on their respective accounts, such as maximum single transaction amount, number of transactions, and total daily payment limits.

[0108] In summary, for any given account node, the resource scheduling restrictions on its account information can include at least one of the following two:

[0109] The first resource scheduling limit set for the institution corresponding to the account node is used to limit the overall scheduling of several accounts corresponding to the institution;

[0110] The second resource scheduling restriction is set for the account corresponding to this account node.

[0111] For step S230, when determining several target account nodes TA from several second account nodes A2 based on the account information corresponding to the account nodes, several target account nodes TA that satisfy the corresponding resource scheduling constraints can be determined from the several second account nodes A2. The resource scheduling constraints can be a first resource scheduling constraint, a second resource scheduling constraint, or a combination of both.

[0112] In other words, during the process of selecting target account nodes from the second account nodes, the resource scheduling restrictions corresponding to the second account nodes can also be taken into account. If the second account node meets its resource scheduling restrictions, it is determined to be the target account node.

[0113] When the resource scheduling request carries a first resource quantity Q1, during step S230, several target account nodes TA that satisfy the corresponding resource scheduling constraints and their corresponding resource scheduling quantities q can be determined from several second account nodes A2. Furthermore, the sum of the resource scheduling quantities q of the several target account nodes TA is made equal to the first resource quantity Q1.

[0114] In another embodiment of this specification, the scheduling network described above can be either a directed network or an undirected network. For an undirected network, bidirectional resource scheduling is possible between any related account nodes. In the following embodiments, the focus is on the case where the scheduling network is a directed network.

[0115] In a directed scheduling network, every connection edge contains information about the direction of resource flow. For example, Figure 3The arrows on the connecting edges between account nodes indicate resource flow information. Resources can flow in the direction of the arrows, and bidirectional arrows indicate that resources can flow between two account nodes.

[0116] exist Figure 3 In the example shown, Company 1 has two accounts, corresponding to account node 1 and account node 6 in the scheduling network. Company 1 and Company 2 have a loan relationship, meaning Company 1 can borrow funds from Company 2. Company 1 and Company 3 have a service purchase relationship; Company 1 purchases services from Company 3 and pays Company 3 for these services. Company 1 and Company 4 have an equity relationship; Company 4 is a shareholder of Company 1 and can make additional investments in Company 1, while Company 1 can receive dividends from Company 4. The flow of funds between the various account nodes can be as follows: Figure 3 As shown.

[0117] In this embodiment, the resource scheduling request may carry the first resource flow information D1 for the first account Ac1.

[0118] When performing step S220, when determining several second account nodes A2 that are associated with the first account node A1 from the scheduling network, several account nodes that are associated with the first account node A1 in the scheduling network and whose resource flow information of the connection edge between them and the first account node A1 is consistent with the first resource flow information D1 can be determined as second account nodes A2.

[0119] For example, in Figure 3 In the scheduling network shown, the nodes associated with account node 1 include account node 2, account node 3, account node 5 and account node 6. Among them, in the connection edge between account node 1, the arrow pointing to account node 1 is consistent with the flow direction in the resource scheduling request. Therefore, account node 2, account node 5 and account node 6 can be identified as the selected account nodes, namely the second account node A2.

[0120] Let's review the specific implementation methods of steps S220 and S230. When determining the second account node A2 from the scheduling network (as the first layer of filtering), the first layer of filtering can be performed based on the resource flow information of the connection edges between account nodes. Filtering can also be based on the condition that the available resource quantity of the account is not less than the first resource quantity Q1, or based on the specified association relationship or specified organization information carried in the resource scheduling request. The above filtering conditions can be selected individually or in combination according to business needs.

[0121] When determining the target account node TA from several second account nodes A2 (as a second-level filter), the filter can be based on the total resource gain rate W meeting a preset condition, or based on the account node meeting resource scheduling constraints, or a combination of the total resource gain rate W meeting a preset condition and the account node meeting resource scheduling constraints.

[0122] When combining filtering methods, one can first filter based on whether the total resource gain rate W meets preset conditions, and then further filter based on whether the account nodes in the filtered results meet resource scheduling restrictions. Alternatively, one can first filter based on whether the account nodes meet resource scheduling restrictions, and then further filter based on whether the total resource gain rate W meets preset conditions.

[0123] During the filtering process, the above-mentioned filtering conditions can be set with corresponding priorities, and the filtering can be performed based on these priorities.

[0124] As can be seen from the various embodiments in this specification, account nodes in the scheduling network can be added or deleted, or account information and relationships can be modified, according to business needs, offering a high degree of flexibility. Organizations can achieve more precise resource scheduling and distribution based on their own resource requirements, minimizing the risk of resource outages and maximizing resource gains.

[0125] In enterprise applications, scheduling networks can decouple enterprises from banks or third-party payment platforms. Enterprises can open accounts at any bank based on their optimal needs, reducing the risk of over-reliance on banks and account management costs. Enterprises can also more precisely allocate and manage their funds based on their inflows and outflows, minimizing the risk of cash flow disruptions and improving capital utilization and profitability.

[0126] In this specification, the terms "first," "first account," "first account node," and "first resource scheduling limit," as well as "second" in the text, are used merely for ease of distinction and description and do not have any limiting meaning.

[0127] The foregoing description describes specific embodiments of this specification; 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 those shown in the embodiments, and the desired result may still be achieved. Furthermore, the processes depicted in the drawings do not necessarily need to follow the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0128] Figure 4This is a schematic block diagram of an apparatus for resource scheduling based on a scheduling network, provided as an embodiment. The apparatus 400 is used to implement resource scheduling between different accounts using a scheduling network. This scheduling network represents the association relationships between multiple accounts and includes multiple account nodes and connection edges between the account nodes. This apparatus embodiment and... Figure 2 The method embodiment shown corresponds to this. The device 400 is deployed in a computer, which can be implemented using any device, equipment, platform, device cluster, etc., with computing and processing capabilities. The device 400 includes:

[0129] The request receiving module 410 is configured to receive a resource scheduling request, wherein the resource scheduling request is used to request resource scheduling for the first account.

[0130] The node determination module 420 is configured to determine, from the scheduling network, several second account nodes that are associated with the first account node;

[0131] The target determination module 430 is configured to determine several target account nodes from the several second account nodes based on the account information corresponding to the account nodes;

[0132] The resource scheduling module 440 is configured to perform resource scheduling between the first account and the several target accounts based on the several target account nodes.

[0133] In one implementation, the resource scheduling request is used to request resource scheduling of a first amount of resources for the first account; the account information of any account node includes the rate of change of resource gain when the resources are scheduled.

[0134] In one embodiment, the target determination module 430 is specifically configured to include:

[0135] Based on the first resource quantity and the change rate corresponding to the plurality of second account nodes, a plurality of target account nodes and corresponding resource scheduling quantities are determined from the plurality of second account nodes, so that the total resource gain quantity meets the preset conditions; the total resource gain quantity is determined based on the corresponding change rate and resource scheduling quantity.

[0136] In one implementation, the plurality of target account nodes includes a third account node, and the resources of the corresponding third account include the second resource quantity that has not yet been credited.

[0137] When the resource scheduling module 440 performs resource scheduling between the first account and several target accounts, it includes:

[0138] Perform resource scheduling between the third account and the fourth account, so that the third account obtains the second amount of resources;

[0139] Based on the second resource quantity, resource scheduling is performed between the first account and the third account.

[0140] In one implementation, an account belongs to a corresponding institution, and multiple accounts correspond to different institutions; the association is used to characterize the contractual relationship between the institutions corresponding to the accounts.

[0141] In one implementation, the account information of any account node includes resource scheduling restrictions, which include at least one of the following:

[0142] The first resource scheduling limit set for the institution corresponding to the account node is used to limit the overall scheduling of several accounts corresponding to the institution;

[0143] The second resource scheduling restriction is set for the account corresponding to this account node.

[0144] In one implementation, the specific configuration of the target determination module 430 includes:

[0145] From the plurality of second account nodes, determine a plurality of target account nodes that meet the corresponding resource scheduling restrictions.

[0146] In one implementation, the scheduling network is a directed network; any connection edge contains resource flow information; the resource scheduling request carries first resource flow information for the first account; the node determination module 420 is specifically configured as follows:

[0147] Several account nodes in the scheduling network that are associated with the first account node and whose resource flow information of the connection edge between them and the first account node is consistent with the first resource flow information are identified as second account nodes.

[0148] In one implementation, the specific configuration of the resource scheduling module 440 includes:

[0149] Several transactions are submitted to the blockchain network. These transactions are generated based on resource scheduling between the first account and several target accounts, each of which corresponds to a target account node.

[0150] In one implementation, accounts belong to users, different accounts correspond to different users, and the association relationship is used to characterize the relationship between users corresponding to accounts.

[0151] Alternatively, multiple accounts may belong to the same organization, with different accounts corresponding to different business operations within that organization. The association relationship is used to characterize the relationship between the business operations corresponding to the accounts.

[0152] The above-described apparatus embodiments correspond to the method embodiments, and detailed descriptions can be found in the description of the method embodiments section, which will not be repeated here. The apparatus embodiments are derived based on the corresponding method embodiments and have the same technical effects as the corresponding method embodiments; detailed descriptions can be found in the corresponding method embodiments.

[0153] Figure 5 This is a schematic block diagram of a resource scheduling system based on a scheduling network, provided as an embodiment. The system 500 is used to implement resource scheduling between different accounts using a scheduling network. The scheduling network represents the association relationships between multiple accounts and includes multiple account nodes and connection edges between account nodes. Accounts belong to corresponding institutions, and multiple accounts correspond to different institutions. The system 500 includes a scheduling platform 510 and multiple institutional devices 520, the number of which can be two or more.

[0154] The scheduling platform 510 is used to receive resource scheduling requests, which are requests to schedule resources for a first account; determine a number of second account nodes that are associated with the first account node from the scheduling network; determine a number of target account nodes from the number of second account nodes based on the account information corresponding to the account nodes; and send resource scheduling instructions to the corresponding institutional equipment 520 based on the number of target account nodes.

[0155] The device 520 is used to receive resource scheduling instructions sent by the scheduling platform 510 and to execute resource scheduling between the first account and several target accounts.

[0156] In one implementation, the resource scheduling request is used to request resource scheduling of a first amount of resources for the first account; the account information of any account node includes the rate of change of resource gain when the resources are scheduled.

[0157] In one implementation, the scheduling platform 510 is specifically used to determine a number of target account nodes and corresponding resource scheduling amounts from the number of second account nodes based on the first resource amount and the change rates corresponding to the number of second account nodes respectively, so that the total resource gain amount meets preset conditions; the total resource gain amount is determined based on the corresponding change rate and resource scheduling amount.

[0158] In one implementation, the plurality of target account nodes includes a third account node, and the resources of the corresponding third account include the second resource quantity that has not yet been credited.

[0159] The device 520 is specifically used to perform resource scheduling between the third account and the fourth account, so that the third account obtains the second resource quantity; and to perform resource scheduling between the first account and the third account based on the second resource quantity.

[0160] In one implementation, the association is used to characterize the contractual relationship between the institutions corresponding to the account.

[0161] In one implementation, the account information of any account node includes resource scheduling restrictions, which include at least one of the following:

[0162] The first resource scheduling limit set for the institution corresponding to the account node is used to limit the overall scheduling of several accounts corresponding to the institution;

[0163] The second resource scheduling restriction is set for the account corresponding to this account node.

[0164] In one implementation, the scheduling platform 510 is specifically used to determine, from the plurality of second account nodes, a plurality of target account nodes that meet the corresponding resource scheduling restrictions.

[0165] In one implementation, the scheduling network is a directed network; any connection edge contains resource flow information; the resource scheduling request carries first resource flow information for the first account;

[0166] The scheduling platform 510 is specifically used to identify several account nodes in the scheduling network that are associated with the first account node and whose resource flow information of the connection edge between them and the first account node is consistent with the first resource flow information as second account nodes.

[0167] In one implementation, the institutional device 520 is used to submit a plurality of transactions to a blockchain network, the plurality of transactions being generated based on resource scheduling between the first account and a plurality of target accounts, the plurality of target accounts corresponding to a plurality of target account nodes.

[0168] The above system embodiments are based on Figure 2 The method embodiments shown correspond to the content in the method embodiments. For more specific implementation details, please refer to the description in the method embodiments section, which will not be repeated here. The system embodiments are based on the corresponding method embodiments and have the same technical effects. For detailed explanations, please refer to the corresponding method embodiments.

[0169] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform... Figures 1 to 3 Any one of the methods described.

[0170] This specification also provides a computing device, including a memory and a processor, wherein the memory stores executable code, and the processor executes the executable code to implement... Figures 1 to 3 Any one of the methods described.

[0171] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for storage media and computing devices are basically similar to the method embodiments, so they are described more simply; relevant parts can be referred to the descriptions of the method embodiments.

[0172] Those skilled in the art will recognize that the functions described in the embodiments of the present invention in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium.

[0173] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, or improvements made based on the technical solutions of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for resource scheduling based on a scheduling network, used to realize carbon emission scheduling among different accounts using a scheduling network, wherein the scheduling network represents the association between multiple accounts and includes multiple account nodes and connecting edges between account nodes; the scheduling network is a directed network, and any connecting edge contains carbon emission flow direction information; Accounts belong to the corresponding institutions, and multiple accounts correspond to different institutions. The carbon emissions in the accounts are used to indicate the compliant production capacity of the corresponding institutions. The method is executed through a scheduling platform and multiple institutional devices, including: The scheduling platform receives a resource scheduling request, which is used to request resource scheduling for the carbon emissions of the first account. The resource scheduling request carries: a specified association between accounts or a specified organization to perform resource scheduling; the resource scheduling request also carries information on the flow of the first carbon emissions for the first account; The scheduling platform determines several second account nodes in the scheduling network that have the specified association with the first account node and whose carbon emission flow information of the connection edge between them and the first account node is consistent with the first carbon emission flow information, or determines account nodes in the scheduling network that belong to the specified institution as second account nodes. The scheduling platform determines several target account nodes from the several second account nodes based on the available carbon emission information corresponding to the account nodes; and sends resource scheduling instructions to the corresponding institutional equipment based on the several target account nodes. The device receives resource scheduling instructions sent by the scheduling platform and executes carbon emission scheduling between the first account and several target accounts.

2. The method according to claim 1, wherein the resource scheduling request is used to request the scheduling of carbon emissions of a first amount of resources for the first account; any account node further includes the rate of change of carbon emission gain when carbon emissions are scheduled.

3. The method according to claim 2, wherein the step of determining a plurality of target account nodes from the plurality of second account nodes based on the available carbon emission information corresponding to the account node includes: Based on the first resource quantity and the change rate corresponding to the plurality of second account nodes, a plurality of target account nodes and corresponding carbon emission scheduling quantities are determined from the plurality of second account nodes, so that the total carbon emission gain quantity meets the preset conditions; the total carbon emission gain quantity is determined based on the corresponding change rate and carbon emission scheduling quantity.

4. The method according to claim 3, wherein the plurality of target account nodes includes a third account node, and the carbon emissions of the corresponding third account include the second carbon emissions that have not yet been credited; The step of executing the carbon emission scheduling between the first account and several target accounts includes: Perform carbon emission scheduling between the third account and the fourth account, so that the third account receives the second carbon emission; Based on the second carbon emission amount, carbon emission scheduling is performed between the first account and the third account.

5. The method according to claim 1, wherein the association relationship is used to characterize the contractual relationship between the institutions corresponding to the account.

6. The method according to claim 5, wherein any account node further includes carbon emission scheduling restrictions, said carbon emission scheduling restrictions including at least one of the following: The first carbon emission scheduling limit set for the institution corresponding to the account node is used to limit the overall scheduling of several accounts corresponding to the institution; A second carbon emission scheduling limit is set for the account corresponding to this account node.

7. The method according to claim 6, wherein the step of determining a plurality of target account nodes from the plurality of second account nodes based on the available carbon emissions corresponding to the account node includes: From the aforementioned number of second account nodes, determine a number of target account nodes that meet the corresponding carbon emission scheduling limits.

8. The method according to claim 1, wherein the step of performing carbon emission scheduling between the first account and a plurality of target accounts comprises: Several transactions are submitted to the blockchain network. These transactions are generated based on the carbon emission scheduling between the first account and several target accounts, each of which corresponds to a target account node.

9. An apparatus for resource scheduling based on a scheduling network, used to realize carbon emission scheduling among different accounts using the scheduling network, wherein the scheduling network represents the association between multiple accounts and includes multiple account nodes and connecting edges between account nodes; the scheduling network is a directed network, and any connecting edge contains carbon emission flow direction information; Accounts belong to the corresponding institutions, and multiple accounts correspond to different institutions. The carbon emissions in the accounts are used to indicate the compliant production capacity of the corresponding institutions. The device includes a first device deployed in a scheduling platform and a second device deployed in multiple institutional devices; The first device includes: The request receiving module is configured to receive a resource scheduling request, which is used to request resource scheduling for the carbon emissions of a first account; the resource scheduling request carries: a specified association between accounts or a specified institution for resource scheduling; the resource scheduling request also carries the flow information of the first carbon emissions for the first account; The node determination module is configured to determine a number of second account nodes in the scheduling network that have the specified association relationship with the first account node and whose carbon emission flow information of the connection edge between them and the first account node is consistent with the first carbon emission flow information, or to determine the account nodes in the scheduling network that belong to the specified institution as second account nodes. The target determination module is configured to determine several target account nodes from the several second account nodes based on the available carbon emission information corresponding to the account nodes; The instruction sending module is configured to send resource scheduling instructions to the corresponding institutional devices based on the plurality of target account nodes; The second device includes: The instruction receiving module is configured to receive resource scheduling instructions sent by the scheduling platform; The resource scheduling module is configured to perform carbon emission scheduling between the first account and several target accounts.

10. The apparatus of claim 9, wherein the resource scheduling request is used to request the scheduling of carbon emissions of a first resource amount for the first account; any account node further includes the rate of change of carbon emission gain when carbon emissions are scheduled.

11. The apparatus according to claim 10, wherein the target determination module is specifically configured as follows: Based on the first resource quantity and the change rate corresponding to the plurality of second account nodes, a plurality of target account nodes and corresponding carbon emission scheduling quantities are determined from the plurality of second account nodes, so that the total carbon emission gain quantity meets the preset conditions; the total carbon emission gain quantity is determined based on the corresponding change rate and carbon emission scheduling quantity.

12. The apparatus according to claim 9, wherein the association is used to characterize the contractual relationship between the institutions corresponding to the account.

13. The apparatus of claim 12, wherein any account node further includes a carbon emission scheduling limit, the carbon emission scheduling limit comprising at least one of the following: The first carbon emission scheduling limit set for the institution corresponding to the account node is used to limit the overall scheduling of several accounts corresponding to the institution; A second carbon emission scheduling limit is set for the account corresponding to this account node.

14. The apparatus according to claim 13, wherein the target determination module is specifically configured as follows: From the aforementioned number of second account nodes, determine a number of target account nodes that meet the corresponding carbon emission scheduling limits.

15. A system for resource scheduling based on a scheduling network, used to realize carbon emission scheduling among different accounts using the scheduling network, wherein the scheduling network represents the association between multiple accounts and includes multiple account nodes and connecting edges between account nodes, the scheduling network is a directed network, and any connecting edge contains carbon emission flow direction information; Accounts belong to corresponding institutions, with multiple accounts corresponding to different institutions. The carbon emissions in each account are used to indicate the compliant production capacity of the corresponding institution. The system includes a scheduling platform and equipment from multiple institutions. The scheduling platform is used to receive resource scheduling requests, which request resource scheduling for the carbon emissions of a first account. The resource scheduling request carries: a specified association between accounts or a specified institution for resource scheduling, and the first carbon emission flow information for the first account. Several second account nodes in the scheduling network that have the specified association with the first account node and whose carbon emission flow information of the connection edge between them and the first account node is consistent with the first carbon emission flow information are identified as second account nodes, or account nodes in the scheduling network that belong to the specified institution are identified as second account nodes. Based on the available carbon emission information corresponding to the account nodes, several target account nodes are determined from the several second account nodes; based on the several target account nodes, resource scheduling instructions are sent to the corresponding institutional equipment; The aforementioned equipment is used to receive resource scheduling instructions sent by the scheduling platform and to execute carbon emission scheduling between the first account and several target accounts.

16. A computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method of any one of claims 1-8.

17. A computing device comprising a memory and a processor, wherein the memory stores executable code, and the processor, when executing the executable code, implements the method of any one of claims 1-8.

Images