CN113888148A

CN113888148A - Method and device for scheduling resources based on scheduling network

Info

Publication number: CN113888148A
Application number: CN202111235722.1A
Authority: CN
Inventors: 黄凌燕; 曹亮; 蔡嘉娴; 周丹
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2021-10-22
Filing date: 2021-10-22
Publication date: 2022-01-04

Abstract

The embodiment of the specification provides a method and a device for scheduling resources based on a scheduling network. The method is used for realizing resource scheduling among different accounts by using a scheduling network. The dispatch network characterizes associations between a plurality of accounts and includes a plurality of account nodes and connecting edges between the account nodes. The execution main body receives a resource scheduling request, and the resource scheduling request is used for requesting to call in or call out resources aiming at the first account. Then, the execution subject may determine, from the scheduling network, a plurality of second account nodes having an association relationship with the first account node, and determine, based on account information corresponding to the account nodes, a plurality of target account nodes from the plurality of second account nodes; and finally, based on the target account nodes, executing resource scheduling between the first account and the target accounts.

Description

Method and device for scheduling resources based on scheduling network

Technical Field

One or more embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a method and an apparatus for resource scheduling based on a scheduling network.

Background

In a corporate enterprise, scheduling of resources among multiple accounts of multiple principals is often involved. The plurality of principals may be, for example, a plurality of subsidiaries. And the account is used as a resource carrier and can bear the resource amount belonging to the main body. The group needs to perform centralized overall management on resources of a plurality of main bodies, so that the resources are fully utilized. When the resources of multiple subjects are managed in a centralized and overall manner, the funds of the multiple subjects need to be analyzed and allocated manually, and the efficiency is low.

Therefore, improved schemes are desired to more efficiently implement the rational scheduling of multi-account resources.

Disclosure of Invention

One or more embodiments of the present specification describe a method and an apparatus for resource scheduling based on a scheduling network, so as to more efficiently implement reasonable scheduling of resources for multiple accounts. The specific technical scheme is as follows.

In a first aspect, an embodiment provides a method for resource scheduling based on a scheduling network, which is used for implementing resource scheduling between different accounts by using the scheduling network, where the scheduling network represents an association relationship between multiple accounts and includes multiple account nodes and connection edges between the account nodes; the method is executed by a computer and comprises the following steps:

receiving a resource scheduling request, wherein the resource scheduling request is used for requesting resource scheduling aiming at a first account;

determining a plurality of second account nodes which have incidence relation with the first account node from the scheduling network;

determining a plurality of target account nodes from the plurality of second account nodes based on account information corresponding to the account nodes;

and executing resource scheduling between the first account and a plurality of target accounts based on the plurality of target account nodes.

In one embodiment, the resource scheduling request is for requesting resource scheduling for a first amount of resources for the first account; the account information for any one account node includes a rate of change of resource gain when the resource is scheduled.

In one embodiment, 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:

determining a plurality of target account nodes and corresponding resource adjusting amounts from the plurality of second account nodes based on the first resource amount and the change rates respectively corresponding to the plurality of second account nodes, so that the total resource gain amount meets a preset condition; the total resource gain amount is determined based on the corresponding slew rate and resource scheduling amount.

In one embodiment, the plurality of target account nodes includes a third account node, and the resources of the corresponding third account include the second resource amount resources that are not yet billed;

the step of executing resource scheduling between the first account and a plurality of target accounts based on the plurality of target account nodes includes:

executing resource scheduling between the third account and a fourth account, so that the third account obtains the second resource amount resource;

and executing resource scheduling between the first account and the third account based on the second resource amount resource.

In one embodiment, the accounts are attributed to corresponding institutions, and the plurality of accounts correspond to different institutions; the incidence relation is used for representing the contract relation between mechanisms corresponding to the account.

In one embodiment, the account information of any one account node includes resource scheduling restrictions, the resource scheduling restrictions including at least one of:

a first resource scheduling limit set for a mechanism corresponding to the account node is used for limiting the overall scheduling of a plurality of accounts corresponding to the mechanism;

and setting a second resource scheduling limit aiming at the account corresponding to the account node.

and determining a plurality of target account nodes meeting corresponding resource scheduling limits from the plurality of second account nodes.

In one embodiment, the scheduling network is a directed network; any one connection edge has resource flow direction information; the resource scheduling request carries first resource flow direction information aiming at the first account;

the step of determining a plurality of second account nodes having association relations with the first account node from the dispatch network includes:

and determining a plurality of account nodes which have an association relationship with a first account node in the scheduling network and have the resource flow direction information of a connection edge between the scheduling network and the first account node consistent with the first resource flow direction information as second account nodes.

In one embodiment, the step of performing resource scheduling between the first account and a plurality of target accounts based on the plurality of target account nodes includes:

submitting 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 respectively corresponding to the plurality of target account nodes.

In one embodiment, the account is attributed to a user, different accounts correspond to different users, and the association relationship is used for representing the relationship between the users corresponding to the account;

or, a plurality of accounts belong to the same organization, different accounts correspond to different services in the organization, and the association relationship is used for representing the relationship between the services corresponding to the accounts.

In a second aspect, an embodiment provides an apparatus for resource scheduling based on a scheduling network, configured to implement resource scheduling between different accounts by using the scheduling network, where the scheduling network characterizes an association relationship between multiple accounts and includes multiple account nodes and connection edges between the account nodes; the device is disposed in a computer and comprises:

the system comprises a request receiving module, a resource scheduling module and a resource scheduling module, wherein the request receiving module is configured to receive a resource scheduling request which is used for requesting resource scheduling aiming at a first account;

the node determining module is configured to determine a plurality of second account nodes which have incidence relations with the first account node from the scheduling network;

the target determining module is configured to determine a plurality of target account nodes from the plurality of second account nodes based on account information corresponding to the account nodes;

and the resource scheduling module is configured to execute resource scheduling between the first account and a plurality of target accounts based on the plurality of target account nodes.

In one embodiment, the goal determining module is specifically configured to:

In a third aspect, an embodiment provides a system for performing resource scheduling based on a scheduling network, configured to implement resource scheduling between different accounts by using the scheduling network, where the scheduling network represents an association relationship between multiple accounts and includes multiple account nodes and connection edges between the account nodes, an account belongs to a corresponding mechanism, and multiple accounts correspond to different mechanisms; the system comprises a dispatching platform and a plurality of mechanism devices:

the scheduling platform is used for receiving a resource scheduling request, and the resource scheduling request is used for requesting resource scheduling aiming at a first account; determining a plurality of second account nodes which have incidence relation with the first account node from the scheduling network; determining a plurality of target account nodes from the plurality of second account nodes based on account information corresponding to the account nodes; based on the target account nodes, sending a resource scheduling instruction to corresponding mechanism equipment;

the mechanism device is used for receiving the resource scheduling instruction sent by the scheduling platform and executing resource scheduling between the first account and the target accounts.

In a fourth aspect, embodiments provide 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 of the first aspect.

In a fifth aspect, an embodiment provides a computing device, including a memory and a processor, where the memory stores executable code, and the processor executes the executable code to implement the method of any one of the first aspect.

In the method and the apparatus provided in the embodiments of the present specification, when resource scheduling needs to be performed for a first account, a plurality of second account nodes may be determined by using an association relationship between account nodes in a scheduling network, a target account node may be determined from the second account nodes based on account information, and resource scheduling between the first account and the target account may be performed. The computer is utilized to execute the process, the account for the first account to carry out resource scheduling can be quickly determined, and the connection relation among the account nodes in the scheduling network improves the processing process of determining the account nodes, so that the reasonable scheduling of the resources of the multiple accounts can be more efficiently realized.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. It is obvious that the drawings in the following description are only some embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.

FIG. 1 is a schematic diagram illustrating an implementation scenario of an embodiment disclosed herein;

fig. 2 is a flowchart illustrating a method for scheduling resources based on a scheduling network according to an embodiment;

FIG. 3 is a schematic diagram showing the relationship between account nodes, enterprises, and fund authorities;

fig. 4 is a schematic block diagram of an apparatus for resource scheduling based on a scheduling network according to an embodiment;

fig. 5 is a schematic block diagram of a system for resource scheduling based on a scheduling network according to an embodiment.

Detailed Description

The scheme provided by the specification is described below with reference to the accompanying drawings.

Fig. 1 is a schematic view of an implementation scenario of an embodiment disclosed in this specification. The system comprises a dispatching platform and a mechanism device. The mechanism devices may be two or more. The mechanism equipment can send a resource scheduling request to the scheduling platform, the scheduling platform can determine a target account based on the resource scheduling request and the scheduling network, and send a resource scheduling instruction to the corresponding mechanism equipment, and the mechanism equipment executes resource scheduling and performs resource scheduling among different accounts. Fig. 1 shows an implementation scenario of an embodiment provided in this specification, and does not constitute a limitation to this specification. The number of account nodes in the dispatch network shown in figure 1 is also merely an example.

The scheduling platform may be implemented by a server or other device having some computing capability. The mechanism device is a device corresponding to the mechanism, and can be implemented by a device with certain computing processing capacity, a cluster, and the like.

The account is a resource carrier and is a tool for carrying and transferring resources. The resource may include various kinds, and any valuable object that can be represented in a certain form and can be transferred and scheduled may be referred to as a resource. For example, resources may include funds, data traffic, carbon emissions, and the like.

An account may be attributed to an institution, and multiple accounts may be correspondingly attributed to different institutions. The plurality of accounts correspond to different institutions, including: different accounts correspond to different institutions, and the accounts correspond to the institutions one by one; alternatively, one institution may have one or more accounts, all of which correspond to multiple institutions. The organization performs data processing tasks through its corresponding organization device. An organization may include a business entity and a business entity. Business entities may include companies, factories, farms, stores, etc., and business entities may include schools, hospitals, research institutes, etc.

In one application scenario, in a corporate enterprise, multiple subsidiaries may each own their accounts. In order to maximize the utilization efficiency of resources, there is a need for a group to perform overall management on resources in accounts of respective subsidiaries.

In another application scenario, a cooperative relationship exists between multiple enterprises, and scheduling requirements for resources also exist between different enterprises. For example, business a purchases business B's services and business a needs to pay funds to business B's account.

In each of the above application scenarios, the account carries resources that can be scheduled, and may be, for example, funds or carbon emission, and the account of the enterprise may be a fund account or a carbon emission account. Having different carbon emissions means that an enterprise may have different compliance capacities. The carbon emission is scheduled among different enterprises, so that the resources of a plurality of enterprises can achieve a more optimized result.

The accounts may also be attributed to users, with different accounts being correspondingly attributed to different users. The account may also be a user account, i.e. a personal account. The user account may be a funding account carrying funds or a traffic account carrying data traffic. There are also demands for rational utilization and allocation of resources among a plurality of users.

Multiple accounts may also be attributed to the same institution and correspond to different services. The plurality of accounts correspond to different services, including: different accounts correspond to different services, and the accounts correspond to the services one by one; alternatively, one or more accounts may correspond to one service, with all accounts corresponding to multiple services. For example, account 1, account 2, account 3, and account 4 belong to the same business, the funds in account 1 and account 2 are used to develop new products, the funds in account 3 are used to repay loans, and the funds in account 4 are used to pay. The above is merely an example, and in practical applications, the number of accounts may be very large.

In order to more efficiently realize reasonable scheduling of resources of multiple accounts, the embodiments of the present specification provide a method for performing resource scheduling based on a scheduling network. In the method, the executing entity may perform the steps of: step S210, receiving a resource scheduling request; step S220, determining a plurality of second account nodes which have incidence relation with the first account node from the scheduling network; step S230, determining a plurality of target account nodes from a plurality of second account nodes based on account information corresponding to the account nodes; step S240, based on the target account nodes, executing resource scheduling between the first account and the target accounts. According to the method, the account nodes contained in the scheduling network and the incidence relation between the account nodes are utilized, the account which is used for resource scheduling with the first account can be determined rapidly and reasonably, and the processing efficiency of resource scheduling is improved. The present application will be described in detail with reference to specific examples.

Fig. 2 is a flowchart illustrating a method for scheduling resources based on a scheduling network according to an embodiment. The method can be executed by a computer, for example, the execution subject can be any device, apparatus, platform, apparatus cluster, etc. with computing and processing capability. In the implementation scenario shown in fig. 1, the method may be performed by a scheduling platform, or may be performed by both the scheduling platform and the facility device.

The method is used for realizing resource scheduling among different accounts by using a scheduling network. The account is an object for bearing resources and realizing operations such as storage and transfer of the resources. Resources may be scheduled between different accounts.

The scheduling network is used for characterizing incidence relations among a plurality of accounts and comprises a plurality of account nodes and connecting edges among the account nodes. The account nodes are used for representing the account in the scheduling network. The association relationship between the accounts is the association relationship between the corresponding account nodes. In different application scenarios, the accounts may have different associations. When a plurality of accounts correspond to different institutions, the association relationship between the accounts can represent the contract relationship between the institutions corresponding to the accounts, such as a service purchase relationship, a share relationship, an association loan relationship and the like; when different accounts correspond to different users, the incidence relation between the accounts can embody the incidence relation between the users corresponding to the accounts, such as a friendship, a relation between a tenant and a house east, a parent-child relation and the like; when multiple accounts correspond to the same organization (e.g., an enterprise) and different accounts correspond to different services in the organization, the association between the accounts may represent the association between the services corresponding to the accounts.

Corresponding account information may exist in any account, and the account information is also account information of a corresponding account node.

The account information may include a remaining resource amount, an available resource amount, a resource gain variation rate when the resource is scheduled, a resource scheduling limit, and the like. The resource may have a certain gain rate when in the storage state. For example, the current profitability of the fund, the periodic profitability, etc.; carbon emissions that are not used for different periods of time also receive a gain in revenue that encourages reduced use of carbon emissions. The remaining resource amount may have different resource gains according to the storage term. Correspondingly, when resources are scheduled, the resource gain may also vary. The above-mentioned fluctuation rates include a loss rate and an increase rate. For example, for the fund in the current status, if the part of the fund is called out of the account, the change rate of the fund gain is the loss rate, and the value of the loss rate is the current interest rate; if a part of funds are transferred into the account, the change rate of the fund gain is the growth rate, and the value of the growth rate is the current interest rate. The basic information of the account will vary with the scheduling of resources.

The resource scheduling limit may be a limit condition set for resource scheduling for the account. For example, the resource scheduling limit may include a maximum resource scheduling amount for the account, a minimum resource scheduling amount, a maximum number of resource scheduling times within a specified duration, and the like.

The scheduling network may be constructed in advance according to a plurality of accounts and the association relationship therebetween. The scheduling network may be constructed in the execution body, or may be constructed in other devices. After the completion of the construction, the scheduling network may be stored locally in the execution entity or in another device.

The method of the present embodiment includes the following steps S210 to S240.

Step S210, receiving a resource scheduling request, where the resource scheduling request is used to request resource scheduling for a first account (e.g., Ac 1). The resource scheduling request may carry an identification Ac1 of the first account.

In different implementation scenarios, the transmission subject of the resource scheduling request may be different. For example, in the implementation scenario shown in fig. 1, the resource scheduling request may be sent to the scheduling platform by the agency device. When the account is a user account, the resource scheduling request may be sent to the execution subject by the device according to an input operation of the user. Of course, the execution main body itself may also receive the resource scheduling request under the trigger of the input operation of the user.

In an embodiment, the resource scheduling request may specifically be used to request resource scheduling of the first resource amount Q1 for the first account Ac1, and may also carry first resource flow information D1 for the first account Ac 1. The first resource flow information D1 includes both ingress and egress flow information. For example, the resource scheduling request may be for requesting that the first resource amount Q1 be called into the first account Ac1, or the resource scheduling request may be for requesting that the first resource amount Q1 be called out from the first account Ac 1.

Instead of carrying the first resource amount Q1 and the first resource flow information D1, the resource scheduling request may be preset with the first resource amount Q1 and the first resource flow information D1, and these pieces of information may be stored as default in the execution body. And when the execution main body receives the resource scheduling request, executing the subsequent flow according to default setting.

The resource scheduling request may also carry a specified association relationship. There may be a plurality of associations relating to the first account node, the specified association being one or more of the plurality of associations.

In an implementation scenario where the multiple accounts correspond to different institutions, the resource scheduling request may also carry a specified institution for performing resource scheduling on the first account Ac1, that is, an account of the specified institution is an object of resource scheduling with the first account Ac1, and the specified institution may have multiple accounts. And the designated institution is associated with the institution corresponding to the first account Ac 1.

In step S220, several second account nodes a2 associated with the first account node a1 are determined from the dispatch network. The first account Ac1 corresponds to the first account node a1 in the dispatch network. The number of second account nodes a2 may be one or more.

When the resource scheduling request carries a specified incidence relation, a plurality of second account nodes A2 with the specified incidence relation with the first account node A1 can be determined from the scheduling network. When a specified institution is carried in the resource scheduling request, the account node belonging to the specified institution in the scheduling network may be determined as the second account node a 2.

Taking the dispatch network shown in fig. 1 as an example, assuming account node 1 is taken to represent the first account node a1, determining the second account node associated with a1 from the dispatch network includes: account node 2, account node 3, account node 5, and account node 6.

When the scheduling network is stored locally in the execution agent, the execution agent may directly execute this step S220 locally. When the scheduling network is stored in other devices, the executing body may send the resource scheduling request to the other devices, and receive several second account nodes fed back by the other devices.

In step S230, a plurality of target account nodes TA are determined from a plurality of second account nodes a2 based on the account information corresponding to the account nodes. The target account node TA may have only one, two or more, or all the second account nodes.

When the available resource amount is included in the account information, the target account node TA may be determined based on the available resource amount of the second account node a 2. For example, the target account node TA may be determined from among the account nodes having the available resource amount not less than the first resource amount Q1 among the number of second account nodes a 2.

When the account information of any account node includes a resource gain variation rate (represented by η) when a resource is scheduled, and a first resource amount Q1 is carried in a resource scheduling request, and a plurality of target account nodes TA are determined from a plurality of second account nodes a2, a plurality of target account nodes TA and a corresponding resource scheduling amount Q may be determined from a plurality of second account nodes a2 based on the variation rates η corresponding to the first resource amount Q1 and the plurality of second account nodes a2, respectively, so that the total resource gain amount W meets a preset condition.

The total resource gain W is determined based on the corresponding change rate and the resource scheduling amount, and represents the total resource gain corresponding to the scheduled resource, including the total resource loss and the total resource increase, when the corresponding resource scheduling amount q is respectively scheduled for the resources of the target account nodes TA. The sum of the resource scheduling amounts Q of the several target account nodes TA is equal to the first resource amount Q1. For example, when the target account nodes include TA1 and TA2, and their corresponding resource allocation amounts are Q1 and Q2, respectively, and corresponding volatility rates are η 1 and η 2, respectively, Q1+ Q2 is Q1. The total resource gain amount may be determined based on a product of the variation rate and the resource modulation amount.

When the resource scheduling direction for the first account Ac1 is to call the first resource amount Q1 into the first account Ac1, the change rate is a loss rate, and the total resource gain amount represents the total resource loss amount. At this time, the preset condition may include: the total resource loss is taken to the minimum.

When the resource scheduling direction for the first account Ac1 is to call the first resource amount Q1 from the first account Ac1, the change rate is an increase rate, and the total resource gain amount represents the total resource increase amount. At this time, the preset condition may include: the total resource increase is taken to be the maximum.

When determining a plurality of target account nodes TA, the plurality of second account nodes a2 may be sorted according to the above change rate, and a plurality of account node combinations may be determined according to the sort and the first resource amount Q1, where the combination may have only one second account node a2, or may include a plurality of second account nodes, and the sum of the available resource amounts of the accounts in each combination is not less than the first resource amount Q1. Then, the total resource gain amount of each combination is determined, and the second account node a2 in the combination meeting the preset condition is determined as the target account node TA.

In the above steps, more reasonable and optimized target account nodes can be screened from the plurality of second account nodes based on the account information, so that the resource scheduling between the first account and the target account in the subsequent steps is also an optimization result.

Step S240, based on the target account nodes TA, performs resource scheduling between the first account Ac1 and the target accounts Tc. The plurality of target accounts Tc correspond to the plurality of target account nodes TA, respectively.

In the scenario diagram shown in fig. 1, when the execution subject is a scheduling platform, the scheduling platform may send a resource scheduling instruction to a corresponding mechanism device when executing this step. And when receiving the resource scheduling instruction sent by the scheduling platform, the mechanism device executes resource scheduling between the first account Ac1 and the target accounts Tc.

For example, the first account Ac1 is an account of institution 1, corresponding to account node 1; the determined target account nodes include account node 2 of institution 2, and account node 3 of institution 3. The scheduling platform may send resource scheduling instructions to the facility device of facility 1, the facility device of facility 2, and the facility device of facility 3. And after receiving the resource scheduling instruction, the institution devices of the institution 1, the institution 2 and the institution 3 execute resource scheduling between the account 1 and the

accounts

2 and 3.

The resource scheduling instruction may carry the resource scheduling amount of each account. In this way, when the mechanism device receives the resource scheduling instruction, the resource scheduling between the accounts can be executed based on the resource scheduling amount carried by the mechanism device. Of course, the resource scheduling instruction may not carry the resource scheduling amount, which is a default setting.

When the account corresponds to a user, the scheduling platform may send a resource scheduling instruction to the corresponding user equipment. And when receiving the resource scheduling instruction sent by the scheduling platform, the user equipment executes resource scheduling between the first account Ac1 and the target accounts Tc.

Whether it is the user equipment or the institution equipment, when performing resource scheduling between the first account Ac1 and several target accounts Tc, the resource scheduling may be implemented by using the blockchain network. Devices (including institution devices and user devices) may submit transactions to the blockchain network. The number of transactions are generated based on a resource schedule between the first account Ac1 and the number of target accounts Tc, respectively. For example, when there are two target accounts Tc1 and Tc2, the first account Ac1 performs resource scheduling with the target accounts Tc1 and Tc2, respectively, and thus can be implemented with two transactions.

For the first account Ac1 and any one target account Tc, when a transaction is generated, the first account Ac1 and the target account Tc may be respectively used as an initiator and a receiver of the transaction, and resource scheduling amounts to be scheduled are carried in transaction contents. The device may also submit a digital signature of the initiator while submitting the transaction to the blockchain network.

Refer back to steps S230 and S240. Given that the target account nodes Tc include the third account node a3, the resources of the corresponding third account Ac3 include the second resource amount resource Q2 that is not yet billed. Not yet billed is the resource that should be billed at a certain time in the past or the resource that will be billed at a certain time in the future, but the resource is not yet billed at the present time. This means that the resource will flow into the third account Ac3 at some time in the future. Such resources and resource amounts that have not yet been billed may be recorded in account information corresponding to the account and attributed to remaining resource amounts or available resource amounts.

The second resource amount resource Q2 may be a resource owed by the fourth account Ac4 to the third account Ac3, or a resource owed by another account to the third account Ac 3.

Therefore, in executing step S240, the resource scheduling between the third account Ac3 and the fourth account Ac4 may be executed first, so that the third account gets the second resource amount resource Q2, and then the resource scheduling between the first account Ac1 and the third account Ac3 may be executed based on the second resource amount resource Q2. When the resource scheduling is executed, the block chain network can also be utilized to submit transactions to the block chain network, so that the resource scheduling between accounts is realized.

After the execution of step S240 is completed, the account information of the corresponding account may also be updated. For example, the account information of the first account, the target account (including the third account), and the fourth account may be updated, and the remaining resource amount, the available resource amount, and the like in the account information may be updated.

Since the incidence relation between the account nodes in the scheduling network and the account information belong to private data, the execution subject (including the scheduling platform) can process the private data in the trusted space of the execution subject when processing the private data. When data interaction is carried out with other equipment, the data interaction can be carried out in an encryption mode so as to ensure the safety of private data.

In another embodiment of the invention, the accounts are attributed to corresponding institutions and the plurality of accounts correspond to different institutions. The association relationship may be used to characterize a contractual relationship between the institutions corresponding to the account. In this embodiment, the mechanism may include a mechanism for executing a service and a dedicated mechanism (resource management mechanism) for storing and scheduling resources. For example, when the resource is funds, the institution may include an enterprise and a funds management institution. The fund management institution comprises banks and third party payment platforms and the like.

For fund, fig. 3 is a schematic diagram illustrating the relationship between account nodes, enterprises, and fund management organizations. Any account node and the corresponding account thereof belong to the corresponding enterprise and bank or belong to the enterprise and a third party payment platform. And connecting the account nodes with the association relationship by using the connecting edges.

The enterprise, bank or third party payment platform may set corresponding restrictions for fund scheduling of the account. For example, an enterprise may set an overall fund schedule of one or more accounts to which the enterprise belongs, or may set a fund schedule for any account. For example, a minimum level of funds remaining, a maximum level of funds remaining, a concentration of funds in various banks or third party payment platforms, etc. for an account may be set. The bank or the third party payment platform may also set the account number to which the platform belongs, such as the maximum single payment fund, the payment times, the total payment limit of the current day, and the like.

To summarize, for any account node, the resource scheduling constraint of the account information may include at least one of the following two:

For step S230, when several target account nodes TA are determined from several second account nodes a2 based on the account information corresponding to the account nodes, several target account nodes TA meeting the corresponding resource scheduling restrictions may be determined from several second account nodes a 2. The resource scheduling restriction may be the first resource scheduling restriction or the second resource scheduling restriction, or a combination of the two.

That is, in the process of screening the target account node from the second account node, the resource scheduling limit corresponding to the second account node may also be referred to, and the second account node is determined to be the target account node under the condition that the second account node satisfies the resource scheduling limit.

When the first resource amount Q1 is carried in the resource scheduling request, in step S230, a number of target account nodes TA satisfying the corresponding resource scheduling restrictions and a corresponding resource scheduling amount Q may be determined from a number of second account nodes a 2. And, the sum of the resource scheduling amounts Q of the several target account nodes TA is made equal to the first resource amount Q1.

In another embodiment of the present specification, the scheduling network may be a directed network or an undirected network. For the undirected network, bidirectional resource scheduling can be performed between any account nodes with association relation. In the following embodiments, the case where the scheduling network is a directed network is explained.

In a directed scheduling network, there is resource flow information on any one connection edge. For example, the arrows connecting edges between account nodes in fig. 3 show resource flow information, resources may flow along the direction of the arrows, and the double-headed arrows indicate that resources may flow between two account nodes.

In the example shown in fig. 3, it is known that enterprise 1 has two account numbers, corresponding to account node 1 and account node 6 in the dispatch network. Enterprise 1 is associated with enterprise 2 in a loan relationship, i.e., enterprise 1 may borrow funds from enterprise 2. Business 1 is in a service procurement relationship with Business 3, and Business 1 procures the services of Business 3 and pays the procurement funds to Business 3. Enterprise 1 is in a equity relationship with Enterprise 4, Enterprise 4 is a shareholder of Enterprise 1, and may add additional investment to Enterprise 1, and Enterprise 1 may be red towards Enterprise 4. The flow of funds between the various account nodes may be as shown in fig. 3.

In this embodiment, the resource scheduling request may carry first resource flow information D1 for the first account Ac 1.

In step S220, when several second account nodes a2 associated with the first account node a1 are determined from the scheduling network, several account nodes in the scheduling network associated with the first account node a1 and having resource flow information of a connection edge with the first account node a1 consistent with the first resource flow information D1 may be determined as the second account node a 2.

For example, in the scheduling network shown in fig. 3, the nodes that have an association relationship with account node 1 include account node 2, account node 3, account node 5, and account node 6, where in the connecting edge between account node 1, the flow direction of the arrow pointing to account node 1 is consistent with the flow direction in the resource scheduling request, then account node 2, account node 5, and account node 6 may be determined as the screened-out account node, that is, the second account node a 2.

A review of the specific implementation of steps S220 and S230 follows. When the second account node a2 is determined from the dispatch network (as a first level screening), the first level screening may be performed based on resource flow information for the connection edges between the account nodes. The screening can also be performed based on the condition that the available resource amount of the account is not less than the first resource amount Q1, or based on the specified association carried in the resource scheduling request, or based on information such as a specified mechanism. The screening conditions may be selected alternatively or in combination according to the service requirements.

When a target account node TA is determined from the plurality of second account nodes a2 (as a second-level screening), the screening may be performed based on the total resource gain rate W satisfying a preset condition, or based on the account nodes satisfying a resource scheduling restriction, or based on the total resource gain rate W satisfying a preset condition, and the screening may be performed based on the account nodes satisfying a resource scheduling restriction in combination.

When the screening is combined, the screening can be performed based on the fact that the total resource gain rate W meets the preset condition, and the screening is performed based on the fact that the account nodes in the screening result meet the resource scheduling limitation according to the screening result. Or, screening is performed based on the account node satisfying the resource scheduling restriction, and then screening is performed based on the total resource gain rate W satisfying the preset condition according to the screening result.

In the screening process, the screening conditions may be set to have corresponding priorities, and the screening may be performed by using the priorities.

It can be seen from the embodiments of the present description that account nodes in a scheduling network can be added and deleted according to business needs, or account information and association relationships can be modified, and the flexibility is very high. The mechanism can achieve more accurate resource scheduling and distribution according to the requirement of the mechanism on resources, avoid the risk of resource cutoff as far as possible and improve the resource gain.

In the enterprise application field, the binding between an enterprise and a bank or a third-party payment platform can be decoupled by utilizing a scheduling network, the enterprise can open an account in any bank according to the self optimal requirement, and the risk of excessive dependence on the bank and the account management cost are reduced. Enterprises can implement the scheduling and layout of funds more accurately according to the inflow and outflow of the funds, reduce the risk of fund flow interruption to the maximum extent, and improve the fund utilization rate and the yield.

In this specification, "first" in the first account, the first account node, the first resource scheduling constraint, etc., and "second" in the text are for convenience of distinction and description only, and do not have any limiting meaning.

The foregoing describes certain embodiments of the present specification, and other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily have to be in the particular order shown or in sequential order to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Fig. 4 is a schematic block diagram of an apparatus for resource scheduling based on a scheduling network according to an embodiment. The apparatus 400 is configured to implement resource scheduling between different accounts using a scheduling network, which characterizes associations between a plurality of accounts and includes a plurality of account nodes and connection edges between the account nodes. This embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2. The apparatus 400 is deployed in a computer, which may be implemented by any device, apparatus, platform, cluster of devices, etc. having computing and processing capabilities. The apparatus 400 comprises:

a request receiving module 410 configured to receive a resource scheduling request, where the resource scheduling request is used to request resource scheduling for a first account;

a node determining module 420 configured to determine, from the scheduling network, a number of second account nodes having an association relationship with the first account node;

a target determination module 430 configured to determine a plurality of target account nodes from the plurality of second account nodes based on account information corresponding to the account nodes;

a resource scheduling module 440 configured to perform resource scheduling between the first account and a number of target accounts based on the number of target account nodes.

In one embodiment, the specific configuration of the goal determining module 430 includes:

the resource scheduling module 440, when performing resource scheduling between the first account and a plurality of target accounts, includes:

In one embodiment, the specific configuration of the goal determination module 430 includes:

In one embodiment, the scheduling network is a directed network; any one connection edge has resource flow direction information; the resource scheduling request carries first resource flow direction information aiming at the first account; the node determining module 420 is specifically configured to:

In one embodiment, the specific configuration of the resource scheduling module 440 includes:

The above device embodiments correspond to the method embodiments, and specific descriptions may refer to descriptions of the method embodiments, which are not repeated herein. The device embodiment is obtained based on the corresponding method embodiment, has the same technical effect as the corresponding method embodiment, and for the specific description, reference may be made to the corresponding method embodiment.

Fig. 5 is a schematic block diagram of a system for resource scheduling based on a scheduling network according to an embodiment. The system 500 is configured to implement resource scheduling between different accounts by using a scheduling network, where the scheduling network represents an association relationship between multiple accounts and includes multiple account nodes and connection edges between the account nodes, an account belongs to a corresponding institution, and multiple accounts correspond to different institutions; the system 500 includes a scheduling platform 510 and a plurality of facility devices 520, and the number of facility devices 520 may be two or more.

The scheduling platform 510 is configured to receive a resource scheduling request, where the resource scheduling request is used to request resource scheduling for a first account; determining a plurality of second account nodes which have incidence relation with the first account node from the scheduling network; determining a plurality of target account nodes from the plurality of second account nodes based on account information corresponding to the account nodes; based on the target account nodes, sending resource scheduling instructions to the corresponding mechanism devices 520;

the mechanism device 520 is configured to receive a resource scheduling instruction sent by the scheduling platform 510, and execute resource scheduling between the first account and a plurality of target accounts.

In an embodiment, the scheduling platform 510 is specifically configured to determine, based on the first resource amount and the variation rates corresponding to the second account nodes, a plurality of target account nodes and corresponding resource adjustment amounts from the second account nodes, so that a total resource gain amount meets a preset condition; the total resource gain amount is determined based on the corresponding slew rate and resource scheduling amount.

the mechanism device 520 is specifically configured to perform resource scheduling between the third account and a fourth account, so that the third account obtains the second resource amount resource; and executing resource scheduling between the first account and the third account based on the second resource amount resource.

In one embodiment, the association is used to characterize a contractual relationship between the institutions to which the account corresponds.

In an embodiment, the scheduling platform 510 is specifically configured to determine, from the plurality of second account nodes, a plurality of target account nodes that satisfy corresponding resource scheduling restrictions.

the scheduling platform 510 is specifically configured to determine, as a second account node, a plurality of account nodes in the scheduling network that have an association relationship with the first account node and whose resource flow direction information of a connection edge between the scheduling network and the first account node is consistent with the first resource flow direction information.

In one embodiment, the institution device 520 is configured to submit a plurality of transactions to the blockchain network, the plurality of transactions being generated based on resource scheduling between the first account and a plurality of target accounts, respectively, the plurality of target accounts corresponding to the plurality of target account nodes, respectively.

The system embodiment is obtained based on the method embodiment shown in fig. 2, and corresponds to the content in the method embodiment, and for a more specific implementation, reference may be made to the description of the method embodiment, and details are not repeated here. The system embodiment is obtained based on the corresponding method embodiment, and has the same technical effect as the corresponding method embodiment, and specific description can be found in the corresponding method embodiment.

Embodiments of the present specification also provide 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 fig. 1 to 3.

The embodiment of the present specification further provides a computing device, which includes a memory and a processor, where the memory stores executable code, and the processor executes the executable code to implement the method described in any one of fig. 1 to 3.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the storage medium and the computing device embodiments, since they are substantially similar to the method embodiments, they are described relatively simply, and reference may be made to some descriptions of the method embodiments for relevant points.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in connection with the embodiments of the invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.

The above-mentioned embodiments further describe the objects, technical solutions and advantages of the embodiments of the present invention in detail. It should be understood that the above description is only exemplary of the embodiments of the present invention, and is not intended to limit the scope of the present invention, and any modification, equivalent replacement, or improvement made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

Claims

1. A method for scheduling resources based on a scheduling network is used for realizing resource scheduling among different accounts by using the scheduling network, wherein the scheduling network represents the incidence relation among a plurality of accounts and comprises a plurality of account nodes and connecting edges among the account nodes; the method is executed by a computer and comprises the following steps:

2. The method of claim 1, the resource scheduling request to request resource scheduling of a first amount of resources for the first account; the account information for any one account node includes a rate of change of resource gain when the resource is scheduled.

3. The method of claim 2, wherein 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 comprises:

4. The method of claim 3, wherein the number of target account nodes includes a third account node, and the resources of the corresponding third account include outstanding resources of a second resource amount;

5. The method of claim 1, an account being attributed to a corresponding institution, a plurality of accounts corresponding to different institutions; the incidence relation is used for representing the contract relation between mechanisms corresponding to the account.

6. The method of claim 5, the account information for any one account node comprising resource scheduling restrictions, the resource scheduling restrictions comprising at least one of:

7. The method of claim 6, wherein 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 comprises:

8. The method of claim 1, the scheduling network being a directed network; any one connection edge has resource flow direction information; the resource scheduling request carries first resource flow direction information aiming at the first account;

9. The method of claim 1, the step of performing resource scheduling between the first account and a number of target accounts based on the number of target account nodes, comprising:

10. The method of claim 1, wherein the account is attributed to a user, different accounts correspond to different users, and the association is used to characterize a relationship between users corresponding to the account;

11. A device for scheduling resources based on a scheduling network is used for realizing resource scheduling among different accounts by using the scheduling network, wherein the scheduling network represents the incidence relation among a plurality of accounts and comprises a plurality of account nodes and connecting edges among the account nodes; the device is disposed in a computer and comprises:

12. The apparatus of claim 11, the resource scheduling request to request resource scheduling of a first amount of resources for the first account; the account information for any one account node includes a rate of change of resource gain when the resource is scheduled.

13. The apparatus of claim 12, the goal determination module being specifically configured to:

14. The apparatus of claim 11, an account being attributed to a corresponding institution, a plurality of accounts corresponding to different institutions; the incidence relation is used for representing the contract relation between mechanisms corresponding to the account.

15. The apparatus of claim 14, the account information of any one account node comprising resource scheduling restrictions, the resource scheduling restrictions comprising at least one of:

16. The apparatus of claim 15, the goal determination module being specifically configured to:

17. A resource scheduling system based on a scheduling network is used for realizing resource scheduling among different accounts by utilizing the scheduling network, wherein the scheduling network represents the incidence relation among a plurality of accounts and comprises a plurality of account nodes and connecting edges among the account nodes, the accounts belong to corresponding mechanisms, and the accounts correspond to different mechanisms; the system comprises a dispatching platform and a plurality of mechanism devices:

18. A computer-readable storage medium, on which a computer program is stored which, when executed in a computer, causes the computer to carry out the method of any one of claims 1-10.

19. A computing device comprising a memory having executable code stored therein and a processor that, when executing the executable code, implements the method of any of claims 1-10.