Method and apparatus for project shuffling between project owners

CN117372163BActive Publication Date: 2026-10-27ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311302616.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-10-08
Publication Date
2026-10-27
Estimated Expiration
2043-10-08

AI Technical Summary

Technical Problem

随着待处理的数据量的增大,求解的难度也相应增加

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117372163B_ABST
    Figure CN117372163B_ABST
Patent Text Reader

Abstract

Embodiments of the present specification provide a method and device for project shuffling among project owners. In the method for project shuffling among project owners, a set of project owners and projects belonging to each project owner are obtained, each project corresponding to a resource amount and a specific resource proportion, and each project owner who wants to increase or decrease projects corresponding to a target resource change amount; a target function indicating that the specific resource proportions corresponding to each project owner after project shuffling tend to be consistent and a relaxed constraint condition are determined, the relaxed constraint condition being that the resource change amount corresponding to each project owner after project shuffling and the target resource change amount corresponding to the project owner differ by no more than a threshold value; and project shuffling information indicating at least one to-be-shuffled project for shuffling from one project owner to another project owner is obtained by solving.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments in this specification generally relate to the field of computer technology, and more particularly to methods and apparatus for transferring projects between project owners. Background Technology

[0002] With the rapid development of computer technology, the scale of data processed by computers is also increasing. For NP-hard problems such as the generalized assignment problem (GAP), the difficulty of solving the problem increases accordingly with the increase in the amount of data to be processed.

[0003] The generalized allocation problem can be abstracted as a matching problem between m items and n knapsacks. In practical applications, there is also a need to solve the following problem: moving the m items, after being matched with n knapsacks, among these knapsacks to achieve a new matching target. Therefore, a method is needed that can be applied to large-scale data to solve this moving problem. Summary of the Invention

[0004] In view of the above, embodiments of this specification provide a method and apparatus for transferring projects between project owners. Using this method and apparatus, the aforementioned transfer problem can be successfully solved for large-scale data.

[0005] According to one aspect of an embodiment of this specification, a method for transferring projects between project owners is provided, comprising: obtaining a set of project owners and a corresponding set of projects, wherein each project in the set of projects corresponds to a resource quantity and a specific resource ratio, each project owner in the set of project owners corresponds to a target resource change, each project belongs to one of the project owners in the set of project owners, and each project owner belongs to a positive category of expected increase in projects or a negative category of expected decrease in projects; determining an objective function and relaxed constraints based on the set of project owners and the set of projects, wherein the objective function is used to indicate that the specific resource ratio corresponding to each project owner after project transfer tends to a desired ratio, and the relaxed constraints include that the difference between the resource change corresponding to each project owner after project transfer and the target resource change corresponding to the project owner is not greater than a threshold; and generating project transfer information according to the objective function and the relaxed constraints, wherein the project transfer information is used to indicate that at least one project to be transferred is determined from the set of projects to be transferred from a corresponding target negative project owner to a corresponding target positive project owner.

[0006] According to another aspect of the embodiments of this specification, a method for transferring users between institutions is provided, comprising: the method for transferring projects between project owners as described above, wherein the project owner includes financial institutions, the project includes users, the resource quantity includes loan amount, the specific resource ratio includes bad debt risk rate, the target resource change amount includes loan amount change, the positive category is used to indicate financial institutions that wish to increase users, and the negative category is used to indicate financial institutions that wish to decrease users.

[0007] According to another aspect of the embodiments of this specification, a method for relocating physical machines between cloud service scenarios is provided, comprising: the method for relocating projects between project owners as described above, wherein the project owner includes a cloud service scenario, the project includes physical machines, the resource quantity includes cloud service resources provided by the physical machines, the specific resource ratio includes the failure rate, the target resource change amount includes the change in cloud service resource demand, the positive category is used to indicate a cloud service scenario where physical machines are expected to be added, and the negative category is used to indicate a cloud service scenario where physical machines are expected to be reduced.

[0008] According to another aspect of the embodiments of this specification, an apparatus for transferring projects between project owners is provided, comprising: an information acquisition unit configured to acquire a set of project owners and a corresponding set of projects, wherein each project in the set of projects corresponds to a resource quantity and a specific resource ratio, each project owner in the set of project owners corresponds to a target resource change amount, each project belongs to one of the project owners in the set of project owners, and each project owner belongs to a positive category of desired project increase or a negative category of desired project decrease; and a modeling unit configured to determine an objective function and a relaxation function based on the set of project owners and the set of projects. The constraints include: the objective function indicating that the proportion of specific resources corresponding to each project owner after project relocation tends to the desired ratio; the relaxed constraints include that the difference between the resource change corresponding to each project owner after project relocation and the target resource change corresponding to the project owner is no greater than a threshold; and a relocation information generation unit configured to generate project relocation information based on the objective function and the relaxed constraints, wherein the project relocation information indicates that at least one project to be relocated is determined from the project set and moved from the corresponding target negative project owner to the corresponding target positive project owner.

[0009] According to another aspect of the embodiments of this specification, an apparatus is provided for transferring users between institutions, comprising: the apparatus as described above, wherein the project owner includes financial institutions, the project includes users, the resource quantity includes loan amount, the specific resource ratio includes bad debt risk rate, the target resource change amount includes loan amount change, the positive category is used to indicate financial institutions that wish to increase users, and the negative category is used to indicate financial institutions that wish to decrease users.

[0010] According to another aspect of the embodiments of this specification, an apparatus is provided for physical machine relocation between cloud service scenarios, comprising: the apparatus as described above, wherein the project owner includes a financial institution, the project includes users, the resource quantity includes loan amount, the specific resource ratio includes bad debt risk rate, the target resource change amount includes loan amount change, the positive category is used to indicate financial institutions that expect to increase users, and the negative category is used to indicate financial institutions that expect to decrease users.

[0011] According to another aspect of the embodiments of this specification, an apparatus for transferring projects between project owners is provided, comprising: at least one processor, and a memory coupled to the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method for transferring projects between project owners as described above, or to implement the method for transferring users between institutions as described above, or to implement the method for transferring physical machines between cloud service scenarios as described above.

[0012] According to another aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores a computer program, which, when executed by a processor, implements the method described above for transferring projects between project owners, or the method described above for transferring users between organizations, or the method described above for transferring physical machines between cloud service scenarios.

[0013] According to another aspect of the embodiments of this specification, a computer program product is provided, including a computer program that is executed by a processor to implement the method described above for transferring projects between project owners, or the method described above for transferring users between organizations, or the method described above for transferring physical machines between cloud service scenarios. Attached Figure Description

[0014] A further understanding of the nature and advantages of this specification can be achieved by referring to the following figures. In the figures, similar components or features may have the same reference numerals.

[0015] Figure 1 An exemplary architecture of a method and apparatus for transferring a project between project owners according to embodiments of this specification is shown.

[0016] Figure 2 A flowchart illustrating an example of a method for transferring a project between project owners according to an embodiment of this specification is shown.

[0017] Figure 3 A flowchart illustrating an example of a process for generating project relocation information according to an embodiment of this specification is shown.

[0018] Figure 4 A flowchart illustrating an example of a process for determining whether training execution conditions are met, according to an embodiment of this specification.

[0019] Figure 5 A flowchart illustrating an example of the process for determining alternative relocation items according to an embodiment of this specification is shown.

[0020] Figure 6 A schematic diagram illustrating an example of a maneuvering stopping condition according to an embodiment of this specification is shown.

[0021] Figure 7 A flowchart illustrating an example of a process for determining whether the owner of a first project meets the corresponding relocation cessation conditions according to an embodiment of this specification is provided.

[0022] Figure 8 A flowchart illustrating an example of a process for determining whether the owner of a second project meets the corresponding relocation cessation conditions, according to an embodiment of this specification.

[0023] Figure 9 A block diagram illustrating an example of an apparatus for transferring a project between project owners, according to an embodiment of this specification.

[0024] Figure 10 A block diagram of an example of a relocation information generation unit in an apparatus for relocating a project between project owners, according to an embodiment of this specification, is shown.

[0025] Figure 11 A block diagram illustrating an example of a device for user relocation between mechanisms according to an embodiment of this specification is shown.

[0026] Figure 12 A block diagram illustrating an example of an apparatus for relocating physical machines between cloud service scenarios, according to an embodiment of this specification.

[0027] Figure 13A block diagram illustrating an example of an apparatus for transferring a project between project owners, according to an embodiment of this specification. Detailed Implementation

[0028] The subject matter described herein will be discussed below with reference to exemplary embodiments. It should be understood that these embodiments are discussed merely to enable those skilled in the art to better understand and implement the subject matter described herein, and are not intended to limit the scope, applicability, or examples set forth in the claims. The function and arrangement of the elements discussed may be changed without departing from the scope of the embodiments described herein. Various processes or components may be omitted, substituted, or added as needed in the various examples. Furthermore, features described in some examples may be combined in other examples.

[0029] As used herein, the term "comprising" and its variations are open terms meaning "including but not limited to". The term "based on" means "at least partially based on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other definitions, whether explicit or implicit, may be included below. Unless explicitly indicated by the context, the definition of a term shall remain consistent throughout the specification.

[0030] In this specification, the term "transfer" can refer to transferring a project from a negative category project owner to a positive category project owner while satisfying the project owner's constraints on the number of projects.

[0031] The method and apparatus for transferring a project between project owners according to embodiments of this specification will now be described in detail with reference to the accompanying drawings.

[0032] Figure 1 An exemplary architecture 100 of a method and apparatus for transferring a project between project owners according to embodiments of this specification is shown.

[0033] exist Figure 1 In this context, network 110 is used to interconnect terminal device 120 and application server 130.

[0034] Network 110 can be any type of network capable of interconnecting network entities. Network 110 can be a single network or a combination of various networks. In terms of coverage, network 110 can be a local area network (LAN), a wide area network (WAN), etc. In terms of the carrying medium, network 110 can be a wired network, a wireless network, etc. In terms of data switching technology, network 110 can be a circuit-switched network, a packet-switched network, etc.

[0035] Terminal device 120 can be any type of electronic computing device capable of connecting to network 110, accessing servers or websites on network 110, processing data or signals, etc. For example, terminal device 120 can be a desktop computer, laptop computer, tablet computer, smartphone, etc. Although in Figure 1 Only one terminal device is shown in the diagram, but it should be understood that a different number of terminal devices may be connected to network 110.

[0036] In one implementation, terminal device 120 can be used by a user. Terminal device 120 may include an application client (e.g., application client 121) that can provide various services to the user. In some cases, application client 121 may interact with application server 130. For example, application client 121 may transmit user-inputted messages to application server 130 and receive responses associated with those messages from application server 130. However, it should be understood that, given sufficient computing power, application client 121 may also generate responses to user-inputted messages locally, instead of interacting with application server 130. In this document, "message" can refer to any input information, such as project owner information and project information input by the user. For example, project owner information and project information may include a set of project owners and a corresponding set of projects, the resource quantity and specific resource ratio corresponding to each project in the set, the target resource change amount and positive or negative category to which each project owner belongs, and the ownership relationship between each project and its project owner.

[0037] It should be understood that Figure 1 All network entities shown are exemplary, and any other network entities may be involved in Architecture 100 depending on the specific application requirements.

[0038] Figure 2 A flowchart of a method 200 for transferring a project between project owners according to an embodiment of this specification is shown.

[0039] like Figure 2 As shown in Figure 210, the project ownership set and the corresponding project set are obtained.

[0040] In this embodiment, each project in the project set can correspond to a resource quantity and a specific resource ratio. Each project owner in the project owner set can correspond to a target resource change amount. Each project can belong to one of the aforementioned project owner sets. Each project owner belongs to either the positive category of desired project increase or the negative category of desired project decrease.

[0041] In one example, the project attribution set can be represented by J. The project attribution set J can be further subdivided into a positive project attribution set J0. + and negative project attribution set J - Among them, the positive project attribution set J + The project owners in the list belong to the positive category. The set of negative project owners J... - The project owners in the set J belong to the negative category. The change in target resources corresponding to project owner j in the project owner set J can be represented by Δ. j This can be used to represent the category. It can be understood that items belonging to the positive category belong to the j-group. + The corresponding change in target resources Δ j+ ≥0, belonging to the negative category, the project's affiliation j - Corresponding change in target resources And satisfy ∑ j Δ j =0. Projects belonging to the various project owners in the above project owner set can form a project set corresponding to the above project owner set (e.g., represented by I). The resource quantity and specific resource proportion corresponding to project i in project set I can be represented by a, respectively. i and r i To express.

[0042] In one example, w can be used i,j and x i,j This represents the ownership relationship between project i and project owner j. For example, if project i belonged to project owner j before the transfer, then w i,j =1, otherwise w i,j =0. If project i belongs to project owner j after the relocation, then x i,j =1, otherwise x i,j =0.

[0043] In 220, the objective function and relaxed constraints are determined based on the item attribution set and the item set.

[0044] In this embodiment, the objective function described above can be used to indicate that the proportion of specific resources corresponding to each project owner after project relocation tends to the desired ratio. The relaxed constraints described above may include the difference between the change in resources corresponding to each project owner after project relocation and the change in the target resources corresponding to the project owner not exceeding a threshold.

[0045] In one example, the objective function and the corresponding constraints can be expressed as:

[0046]

[0047]

[0048]

[0049]

[0050]

[0051]

[0052] Here, r can be used to represent the expected ratio. This can be used to represent the percentage of specific resources belonging to project owner j. The meanings of the other symbols are as described above.

[0053] In one example, the above expected ratio can be a global-specific resource ratio, which can be expressed as:

[0054]

[0055] The meanings of the relevant symbols can be found above.

[0056] It can be proven that, due to the existence of the equality constraint in equation (2), the above objective function may not have a feasible solution, therefore, the above equality constraint needs to be relaxed. The relaxed constraint condition corresponding to equation (2) can be expressed as:

[0057]

[0058] Here, δ can be used to represent the above threshold, and the meanings of the other symbols can be found above.

[0059] In one example, the threshold mentioned above could be the maximum amount of resources corresponding to the items in the above item set, i.e., δ = max i∈I {a i In one example, the threshold mentioned above can also be a larger or smaller value based on the maximum amount of resources corresponding to the items in the above item set.

[0060] It can be proven that when the value of the above threshold δ is not less than max i∈I {a i When the threshold δ is less than the maximum value, the above objective function will definitely have a feasible solution. Furthermore, it can be proven that when the threshold δ is less than the maximum value... i∈I {a i When the threshold δ is slightly less than the maximum value, the objective function may not have a feasible solution. i∈I {a i When the threshold δ is slightly greater than the maximum value, a feasible solution is more likely to exist while achieving better constraint effects. i∈I {a iWhen using this method, it can guarantee the existence of a feasible solution while also providing a good constraint effect.

[0061] Based on this, the value of the aforementioned threshold δ is determined to be max. i∈i {a i} can guarantee that the relaxed constraint conditions are still the tightest while ensuring that there is a feasible solution, so that the constraint conditions satisfied by the solution obtained according to the relaxed constraint conditions (Equation (7)) are similar to the original constraint conditions (Equation (2)).

[0062] It is understandable that when solving the above objective function, the above constraints (equations (3) to (6)) can remain unchanged and do not need to be relaxed.

[0063] Optionally, the aforementioned expected ratios can be target ratios corresponding to each project owner. Each target ratio can be the ratio of the target specific resource quantity to the target resource quantity corresponding to the project owner. The target specific resource quantity can include the sum of the specific resource quantities corresponding to each project belonging to the project owner before the project relocation and the sum of the change in the target specific resource quantity corresponding to the project owner. The target specific resource quantity can also include the sum of the resource quantities corresponding to each project belonging to the project owner before the project relocation and the sum of the change in the target resource quantity corresponding to the project owner. The change in the target specific resource quantity can be obtained using a linear programming method. The objective function of the aforementioned linear programming method can be determined based on the difference between the target ratio corresponding to each project owner and the global specific resource ratio corresponding to the project owner set.

[0064] In one example, the expected ratio r can be the target ratio R corresponding to the project owner j. j In one example, the target ratio R corresponding to project owner j is... j It can be represented as:

[0065]

[0066] Among them, B j It can be used to represent the sum of specific resource quantities corresponding to each project belonging to the project owner j before the project relocation, i.e. y j It can be used to represent the change in a specific target resource corresponding to the project owner j. A j It can be used to represent the sum of the resources corresponding to each project belonging to the project owner j before the project was transferred, i.e. Δ j This can be used to represent the change in target resources corresponding to project owner j. It can be understood that for project owner j∈J belonging to the negative category... - A needs to be satisfied j +Δ j≥0.

[0067] In one example, the target-specific resource change y corresponding to the project owner j mentioned above. j This can be obtained using linear programming methods. In one example, the objective function and corresponding constraints of the linear programming method can be expressed as:

[0068]

[0069] st∑ j∈J y j =0

[0070]

[0071] Where r can be a specific global resource proportion as mentioned above. j and l j They can be used to represent the change in a specific resource, y. j The preset upper and lower limits. The meanings of the other symbols can be found above.

[0072] Based on this, due to B j A j Δ j As can be seen, this scheme can approximately transform the objective function in the form of integer programming (Equation (1)) into the objective function in the form of linear programming with continuous variables (Equation (8)), thereby significantly reducing the amount of computation and improving the computation speed while obtaining an approximate solution that meets the requirements.

[0073] Optionally, the expected ratio may include a subset average specific resource ratio. This subset average specific resource ratio may include the ratio of the sum of specific resource amounts corresponding to each project of each project owner in a subset of the aforementioned project owner set to the sum of resource amounts corresponding to each project of each project owner in that subset. Here, the specific resource amount is the product of the corresponding resource amount and the specific resource ratio.

[0074] In one example, the expected ratio r can be the subset average specific resource ratio R. In another example, the subset average specific resource ratio R of the subset J′ of the project affiliation set. J′ It can be represented as:

[0075]

[0076] Among them, I j This symbol represents the set of projects belonging to project owner j. The meanings of the other symbols can be found above.

[0077] Based on this, the present solution can provide a method for determining the expected ratio as similar to the local specific resource ratio. Compared with the aforementioned global specific resource ratio, the expected ratio can change with the change of the elements contained in the subset J′ of the project owner set (e.g., deleting project owner j from the aforementioned subset J′), thereby allowing for dynamic adjustment based on the elements contained in the subset J′ of the project owner set.

[0078] In step 230, project relocation information is generated based on the objective function and the relaxed constraints.

[0079] In this embodiment, the objective function can be solved based on the relaxed constraints, and the obtained x i,j and the corresponding w i,j The relative changes between them yield project relocation information. This project relocation information can be used to indicate at least one project to be relocated from the project set to the corresponding target negative project owner to the corresponding target positive project owner. In one example, project owner j belonging to the positive category can be selected from the project owner set J. + And the project belonging to the negative category j - By continuously attributing items to negative categories, j - Projects belonging to the positive category (j) + Project i (i.e., by) Change to ), until the project owner j - or j + The above-mentioned relaxed constraints are satisfied. Therefore, project relocation information can be obtained based on at least one of the aforementioned relocation items.

[0080] Optionally, continue to refer to Figure 3 , Figure 3 A flowchart illustrating an example of a process 300 for generating project relocation information according to an embodiment of this specification is shown.

[0081] like Figure 3 As shown in 310, the project ownership set is determined as the current project ownership set.

[0082] At step 320, determine whether the current project ownership set meets the conditions for cyclic execution.

[0083] In one example, the loop execution condition could be that the number of project owners contained in the current project owner set (e.g., represented by J′) is greater than a first predetermined value. In another example, the loop execution condition could be the current forward project owner set (e.g., represented by J′) partitioned according to the current project owner set J′. ′+ (to represent) and the current negative project attribution set (e.g., can be represented by J) ′-(represented by) are all non-empty sets.

[0084] Alternatively, see below. Figure 4 , Figure 4 A flowchart illustrating an example of a process 400 for determining whether training execution conditions are met according to an embodiment of this specification is provided.

[0085] like Figure 4 As shown in step 410, determine whether the current project ownership set contains the target project ownership pair.

[0086] In this embodiment, the target project owner includes two project owners belonging to positive and negative categories, respectively, and the relative sizes of the specific resource proportions corresponding to the two project owners are inconsistent with their corresponding expected ratios. In one example, the expected ratio can be the global specific resource proportion. In another example, the expected ratio can be the target ratio corresponding to the project owner. In yet another example, the expected ratio can be the average specific resource ratio of a subset corresponding to the current project owner set.

[0087] In one example, a project owner belonging to category I and a project owner belonging to category IV can form a target project owner pair. In another example, a project owner belonging to category II and a project owner belonging to category III can form a target project owner pair. Specifically, for project owner j, if project owner j belongs to the positive category J... + And the proportion of the corresponding specific resources If the ratio is less than the corresponding expected ratio r, then the project owner j belongs to category I; if the project owner j belongs to the positive category J... + If the proportion of the corresponding specific resources is greater than or equal to the corresponding expected ratio r, then the project owner j belongs to category II; if the project owner j belongs to category J... - If the proportion of the specific resources involved is less than the expected ratio r, then the project owner j belongs to category III; if the project owner j belongs to category J... - If the proportion of the corresponding specific resources is greater than or equal to the corresponding expected ratio r, then the project owner j belongs to category IV.

[0088] If not included, in step 420, it is determined that the current project's ownership set does not meet the conditions for cyclic execution.

[0089] In one example, if included, at 440, it is determined that the current project ownership set satisfies the loop execution condition.

[0090] In one example, if the target project owner set contains a number of target project owner pairs, at step 430, it is determined whether the number of such pairs is greater than a second predetermined value. If it is greater, at step 440, it is determined that the current project owner set satisfies the loop execution condition. If it is not greater, at step 420, it is determined that the current project owner set does not satisfy the loop execution condition.

[0091] Back Figure 3 If the conditions for cyclic execution are met, the following item relocation process (330-379) will be executed.

[0092] In step 330, select the first project owner from the project owners that belong to the positive category in the current project owner set.

[0093] In this embodiment, the first project owner can be the project owner whose difference between the proportion of a specific resource and the corresponding expected proportion is the largest. In one example, the first project owner can be represented as:

[0094]

[0095] The meanings of the relevant symbols can be found above.

[0096] In step 340, based on whether the proportion of specific resources corresponding to the owner of the first project is less than the corresponding expected proportion, projects with a specific resource proportion greater than or equal to or less than the target proportion value are determined from the project set corresponding to the current candidate project owners that match the owner of the first project as candidate projects to be transferred.

[0097] In this embodiment, the target ratio value can be the proportion of specific resources corresponding to the first project owner. The relative size between the proportion of specific resources corresponding to each project owner in the current set of candidate project owners and the corresponding expected ratio is not consistent with the relative size corresponding to the first project owner. In one example, the expected ratio can be the global specific resource ratio. In another example, the expected ratio can be the target ratio corresponding to the project owner. In yet another example, the expected ratio can be the average specific resource ratio of a subset corresponding to the current set of project owners.

[0098] In one example, the candidate projects to be relocated can be represented by i1. If the proportion of specific resources corresponding to the first project owner j1 is less than the corresponding expected proportion, projects with a specific resource proportion greater than or equal to the target proportion can be determined from the project set corresponding to the current candidate project owner set matching the first project owner j1 as candidate projects to be relocated. Wherein, the proportion of specific resources corresponding to each project owner in the current candidate project owner set matching the first project owner j1 is greater than or equal to the corresponding expected proportion. If the proportion of specific resources corresponding to the first project owner j1 is not less than the corresponding expected proportion, projects with a specific resource proportion less than the target proportion can be determined from the project set corresponding to the current candidate project owner set matching the first project owner j1 as candidate projects to be relocated. Wherein, the proportion of specific resources corresponding to each project owner in the current candidate project owner set matching the first project owner j1 is less than the corresponding expected proportion. It can be understood that the project set corresponding to the project owner set (e.g., J) (e.g., I) J This means that the project belongs to the various project owners in the project owner set (e.g., ...). The collection formed by the projects.

[0099] Optionally, see [link to relevant documentation] Figure 5 , Figure 5 A flowchart illustrating an example of a process 500 for determining alternative relocation items according to an embodiment of this specification is shown.

[0100] like Figure 5 As shown in Figure 510, it is determined whether the proportion of specific resources corresponding to the owner of the first project is less than the corresponding expected proportion.

[0101] If the determination is yes, in step 520, the project with the largest proportion of specific resources in the current set of candidate project owners that matches the first project owner will be identified as the candidate project to be relocated.

[0102] In one example, the result of step 510 is that j1 belongs to the aforementioned category I, and therefore the current set of candidate project owners matching the first project owner can be a set formed by project owners belonging to the aforementioned category IV. In one example, the candidate project to be moved can be represented as...

[0103] If the judgment is negative, in step 530, the project with the smallest proportion of specific resources in the current set of candidate project owners that matches the first project owner is identified as the candidate project to be relocated.

[0104] In one example, a negative result in step 510 means that j1 belongs to the aforementioned Category II, and therefore the current set of candidate project owners matching the first project owner can be a set of project owners belonging to the aforementioned Category III. In one example, the candidate projects to be moved can be represented as...

[0105] Based on this, this solution determines the projects with the largest or smallest specific resource ratios from the project sets corresponding to the matching current candidate project owner sets as candidate transfer items, which helps to more quickly meet the requirements of each project owner regarding the change in target resources, thereby improving the calculation speed.

[0106] Back Figure 3 In 350, the project owner to which the alternative project to be relocated belongs is determined as the second project owner.

[0107] In 360, based on the relationship between the current resource change amount and the corresponding target resource change amount and the threshold of the first project owner and the second project owner respectively, it is determined whether the first project owner and the second project owner meet the corresponding transfer stop conditions.

[0108] In one example, based on the relaxed constraints (Equation (7)), the maneuver stopping condition can be expressed as follows: in, This can be used to represent the current resource change corresponding to project owner j. The meanings of the other symbols are as described above. It can be understood that the initial values ​​of the current resource changes corresponding to the first and second project owners can both be set to 0. During project relocation, the current resource change can be updated based on the resource quantity corresponding to the determined project to be relocated.

[0109] Optionally, see [link to relevant documentation] Figure 6 , Figure 6 A schematic diagram of an example of a maneuvering stop condition 600 according to an embodiment of this specification is shown.

[0110] like Figure 6 As shown in Figure 610, with the advancement of the project relocation process (i.e. (Shift right), items belonging to the positive category belong to the j-side. + Corresponding current resource change It starts from 0 and gradually increases. This is understandable, when... Located in the interval When, it means that the optimal matching value has been exceeded. And it satisfies the relaxed constraint condition (Equation (7)). Therefore, the transfer stopping condition corresponding to the first project owner can be: the corresponding current resource change is greater than or equal to the corresponding target resource change and less than or equal to the sum of the corresponding target resource change and the threshold.

[0111] Similarly, as shown in 620, as the project relocation process progresses (i.e. (Shift left), items belonging to the negative category are assigned to j. - Corresponding current resource change It gradually decreases from 0. This is understandable, when... Located in the interval When, it means that the optimal matching value has been exceeded. And it satisfies the relaxed constraint condition (Equation (7)). Therefore, the relocation stopping condition corresponding to the second project owner can be: the corresponding current resource change is greater than or equal to the difference between the corresponding target resource change and the threshold and is less than or equal to the corresponding target resource change.

[0112] Based on this, this solution provides a more detailed method for determining whether a project owner meets the relocation cessation conditions. During the project relocation process, the project owner who meets the relocation cessation conditions for the first time can be identified as the project owner who has met the target resource change amount.

[0113] Optionally, see [link to relevant documentation] Figure 7 , Figure 7 A flowchart illustrating an example of a process 700 for determining whether the first project owner meets the corresponding relocation cessation conditions according to an embodiment of this specification is provided.

[0114] In step 710, determine whether the current resource change corresponding to the owner of the first project is greater than or equal to the corresponding target resource change and less than or equal to the sum of the corresponding target resource change and the threshold.

[0115] If 710 is incorrect, then in 720, determine whether the current resource change corresponding to the first project owner is greater than or equal to the difference between the corresponding target resource change and the threshold, and less than or equal to the corresponding target resource change.

[0116] If 720 is determined to be yes, then at 730, determine whether the current accumulated error value is less than 0.

[0117] In this embodiment, the current accumulated error value can be used to indicate the accumulated value of the resource change error corresponding to the project owner who meets the corresponding relocation stopping condition. In one example, for project owner j who meets the corresponding relocation stopping condition... s ∈J′, the current error can be expressed as It is understandable that the initial value of the current error accumulation value can be set to 0. During the project relocation process, whenever a project owner that meets the corresponding relocation stopping condition appears, the error accumulation value of the previous round can be updated based on the difference between the target resource change amount corresponding to the project owner that meets the corresponding relocation stopping condition and the corresponding current resource change amount. Furthermore, it can be proven that the current accumulated error value t satisfies |t|≤δ.

[0118] The following is combined Figure 6 Further explanation of the judgment condition for the current error accumulation value, as shown in 610, is given when it is located in the interval... At that time, as the project relocation process progressed (i.e. (Right shift), current error Since it is always positive, the current accumulated error value t gradually increases. It can be understood that within this interval, on the basis of satisfying the relaxed constraint condition (Equation (7)), only under the premise that t < 0, it can be guaranteed that it will gradually approach 0 as t gradually increases, that is, satisfy the constraint condition of Equation (2) as much as possible.

[0119] If 710 or 730 is determined to be yes, then in 740, it is determined that the owner of the first project meets the corresponding transfer cessation conditions.

[0120] If 720 or 730 is incorrect, then at 750, it is determined that the owner of the first project does not meet the corresponding transfer cessation conditions.

[0121] Based on this, this solution provides a more detailed method for determining whether the owner of the first project meets the transfer cessation conditions, so that the obtained result, while satisfying the relaxed constraints, minimizes the deviation from the original constraints.

[0122] Optionally, see [link to relevant documentation] Figure 8 , Figure 8 A flowchart illustrating an example of a process 800 for determining whether the second project owner meets the corresponding relocation cessation conditions according to an embodiment of this specification is provided.

[0123] In step 810, determine whether the current resource change corresponding to the second project owner is greater than or equal to the difference between the corresponding target resource change and the threshold, and less than or equal to the corresponding target resource change.

[0124] If 810 is incorrect, then in 820, determine whether the current resource change corresponding to the second project owner is greater than or equal to the corresponding target resource change and less than or equal to the sum of the corresponding target resource change and the threshold.

[0125] If 820 is determined to be yes, then at 830, it is determined whether the current accumulated error value is greater than or equal to 0.

[0126] In this embodiment, the current error accumulation value can be referred to the relevant description of step 720 above.

[0127] The following is combined Figure 6 Further explanation of the judgment condition for the current error accumulation value, as shown in 620, is given when it is located in the interval... At that time, as the project relocation process progressed (i.e. (Left shift), current error Since the value is always negative, the current accumulated error value t gradually decreases. It can be understood that within this interval, on the basis of satisfying the relaxed constraint condition (Equation (7)), only under the premise that t≥0, it can be guaranteed that the value will gradually approach 0 as t gradually decreases, that is, the constraint condition of Equation (2) can be satisfied as much as possible.

[0128] If 810 or 830 is determined to be yes, then in 840, it is determined that the owner of the second project meets the corresponding transfer cessation conditions.

[0129] If 820 or 830 is incorrect, then at 850, it is determined that the owner of the second project does not meet the corresponding transfer cessation conditions.

[0130] Based on this, this solution provides a more detailed method for determining whether the owner of the second project meets the transfer cessation conditions, so that the obtained results, while satisfying the relaxed constraints, minimize the deviation from the original constraints.

[0131] Back Figure 3 In 370, determine whether at least one of the owners of the first project and the owners of the second project satisfies the corresponding transfer cessation condition.

[0132] If the determination is yes, in step 371, remove the project owners that meet the corresponding transfer cessation conditions from the current project owner set to update the current project owner set.

[0133] In this embodiment, the updated current project owner set does not contain any project owners that meet the corresponding transfer cessation conditions.

[0134] Optionally, in 373, the current error accumulation value is updated to the sum of the difference between the target resource change corresponding to the removed project owner and the corresponding current resource change value and the previous round error accumulation value.

[0135] In one example, the update process of the current accumulated error value t can be represented as:

[0136] Optionally, step 373 can also be performed before step 371.

[0137] If the result is negative, proceed with steps 375-379.

[0138] In 375, the alternative projects to be relocated were identified as projects to be relocated.

[0139] At 377, generate project relocation information to indicate the relocation of projects from the second project owner to the first project owner, and update the ownership relationship between the current project owner set and the projects.

[0140] In this embodiment, the project relocation information may include the identifier of the project to be relocated (e.g., project 3) and the identifiers of the corresponding first project owner (e.g., project owner A) and second project owner (e.g., project owner E). The identifier of the project to be relocated (e.g., project 3) can be updated from belonging to the second project owner (e.g., project owner E) to belonging to the first project owner (e.g., project owner A). It is understood that after the ownership relationship is updated, the sum of resources and the sum of specific resources corresponding to each project belonging to that project owner will also be updated accordingly.

[0141] In 379, based on the resource quantity corresponding to the project to be transferred, update the current resource change quantity corresponding to the owner of the first project and the owner of the second project respectively.

[0142] In this embodiment, the current resource change amount corresponding to the owner of the first project can be updated to the sum of the resource amount corresponding to the project to be relocated and the current resource change amount in the previous round. The current resource change amount corresponding to the owner of the second project can be updated to the sum of the resource amount corresponding to the project to be relocated and the current resource change amount in the previous round.

[0143] In one example, the update process for the current resource changes corresponding to the first project owner and the second project owner can be represented as follows: and The meanings of the relevant symbols can be found above.

[0144] In this embodiment, after the current project ownership set or the ownership relationship between the current project ownership set and the project is updated, the updated current project ownership set can serve as the current project ownership set for the next round of project relocation, and the updated current resource change can serve as the current resource change for the next round of project relocation. We can return to step 320 to further determine whether the current project ownership set meets the cyclic execution condition. If the cyclic execution condition is met, the project relocation process can be executed cyclically.

[0145] If the conditions for cyclic execution are not met, in step 380, generate project relocation information based on the generated project relocation information.

[0146] In one example, the generated project relocation information can be integrated to generate project relocation information. In one example, the project relocation information may include the identifier of at least one project to be relocated and the identifiers of the first project owner and the second project owner corresponding to each project to be relocated.

[0147] Based on this, this scheme determines whether to perform a project transfer by selecting the corresponding first and second project owners and determining whether the corresponding transfer stopping conditions are met during each transfer process, effectively reducing computational complexity. Furthermore, by combining the aforementioned reasonable selection of thresholds and appropriate selection of transfer stopping conditions, the determined objective function can decrease as the size of the itemset increases, thus ensuring the feasibility of computation for large-scale data.

[0148] use Figures 1-8 The method disclosed in the paper for transferring projects between project owners can model project transfer schemes as integer programming problems and reduce the difficulty of solving them by relaxing the equality constraints, thereby making it easier to obtain feasible solutions that meet the requirements (i.e., the generated project transfer information).

[0149] Understandably, in one example, the project owner can include financial institutions, the project can include users, the resource quantity can include loan amounts, a specific resource ratio can include bad debt risk rates, the target resource change can include changes in loan amounts, positive categories can be used to indicate financial institutions that expect to increase users, and negative categories can be used to indicate financial institutions that expect to decrease users. (See reference...) Figures 1-8 The method disclosed in the paper for transferring projects between project owners can be used to transfer users between institutions. By transferring users from financial institutions that expect to reduce loan amounts to financial institutions that expect to increase loan amounts according to user transfer information, each financial institution can increase or decrease its expected loan amount as much as possible, and the overall bad debt risk rate of each financial institution tends to be consistent.

[0150] Similarly, in one example, the project owner can include a cloud service scenario, the project can include physical machines, the resource quantity can include the cloud service resources provided by the physical machines, the specific resource ratio can include the failure rate, the target resource change can include the change in cloud service resource demand, positive categories can be used to indicate cloud service scenarios that expect to increase physical machines, and negative categories can be used to indicate cloud service scenarios that expect to decrease physical machines. (See reference...) Figures 1-8The method disclosed in the paper for transferring projects between project owners can be used to transfer physical machines between cloud service scenarios. By transferring physical machines from cloud service scenarios that expect to reduce cloud service resources to cloud service scenarios that expect to increase cloud service resources according to the physical machine transfer information, each cloud service scenario can increase or decrease its expected cloud service resources as much as possible and make the overall failure rate of each cloud service scenario tend to be consistent.

[0151] The following is for reference. Figure 9 , Figure 9 A block diagram illustrating an example of an apparatus 900 for transferring a project between project owners according to an embodiment of this specification. This apparatus embodiment can be used with... Figures 2-8 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0152] like Figure 9 As shown, the apparatus 900 for transferring projects between project owners may include an information acquisition unit 910, a modeling unit 920, and a transfer information generation unit 930.

[0153] Information acquisition unit 910 is configured to acquire a set of project owners and a corresponding set of projects. Each project in the set of projects corresponds to a resource quantity and a specific resource ratio. Each project owner in the set of project owners corresponds to a target resource change. Each project belongs to one of the project owner sets, and each project owner belongs to either a positive category (expecting an increase in projects) or a negative category (expecting a decrease in projects). The operation of information acquisition unit 910 can be referred to above. Figure 2 The operation described in section 210.

[0154] Modeling unit 920 is configured to determine an objective function and relaxed constraints based on the project owner set and the project set. The objective function indicates that the proportion of specific resources corresponding to each project owner after project relocation tends to a desired ratio. The relaxed constraints include ensuring that the difference between the resource change corresponding to each project owner after project relocation and the target resource change corresponding to that project owner is no greater than a threshold. The operation of modeling unit 920 can be referenced above. Figure 2 The operation described in section 220.

[0155] In one example, the threshold includes the maximum amount of resources corresponding to the items in the project set.

[0156] In one example, the expected ratio can be the target ratio corresponding to each project owner. Each target ratio can be the ratio of the target specific resource quantity to the target resource quantity corresponding to the project owner. The target specific resource quantity can include the sum of the specific resource quantities corresponding to each project belonging to the project owner before the project relocation and the sum of the target specific resource change quantity corresponding to the project owner. The target specific resource change quantity can be obtained using a linear programming method. The objective function of the above linear programming method can be determined based on the difference between the target ratio corresponding to each project owner and the global specific resource ratio corresponding to the project owner set.

[0157] In one example, the expected ratio may include a subset average specific resource ratio. This subset average specific resource ratio may include the ratio of the sum of the specific resource amounts corresponding to each project of each project owner in a subset of the aforementioned project owner set to the sum of the resource amounts corresponding to each project of each project owner in that subset. Here, the specific resource amount is the product of the corresponding resource amount and the specific resource ratio.

[0158] The above content can be used as a reference. Figure 2 Description of the optional implementation of step 220 in the embodiments.

[0159] The relocation information generation unit 930 is configured to generate project relocation information based on the objective function and relaxed constraints. This project relocation information indicates that at least one project identified from the project set is to be relocated from its corresponding negative target project owner to its corresponding positive target project owner. The operation of the relocation information generation unit 930 can be referenced above. Figure 2 The operation described in section 230.

[0160] In one example, optionally, continue to refer to Figure 10 , Figure 10 A block diagram illustrating an example of a relocation information generation unit 1000 in an apparatus for relocating projects between project owners, according to an embodiment of this specification. This apparatus embodiment can be used with... Figure 3 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0161] like Figure 10 As shown, the maneuver information generation unit 1000 may include an initialization module 1010, a condition judgment module 1020, a loop execution module 1030, and an information generation module 1040.

[0162] Initialization module 1010 is configured to determine the project owner set as the current project owner set. The operation of initialization module 1010 can be referred to above. Figure 3 The operation described in section 310.

[0163] In one example, the initialization module 1010 is further configured to initialize the current resource change amount corresponding to the first project owner and the second project owner to 0 respectively.

[0164] In one example, initialization module 1010 is further configured to initialize the current error accumulation value to 0.

[0165] The loop condition judgment module 1020 is configured to determine whether the current project ownership set satisfies the loop execution condition. The operation of the loop condition judgment module 1020 can be referred to above. Figure 3 The operation described in section 320.

[0166] In one example, the loop condition judgment module 1020 can be further configured to: determine whether the current project owner set contains the target project owner pair, wherein the two project owners contained in the target project owner pair belong to the positive category and the negative category respectively, and the relative size between the proportion of specific resources corresponding to the two project owners and the corresponding expected ratio is inconsistent; if not, determine that the current project owner set does not satisfy the loop execution condition.

[0167] In one example, the loop condition judgment module 1020 can be further configured to: if included, determine that the current project ownership set satisfies the loop execution condition.

[0168] The operation of the loop condition judgment module 1020 described above can be referenced. Figure 4 The operation described in section 410-440.

[0169] The loop execution module 1030 is configured to execute the project relocation process through the project selection submodule 1031, the project owner selection submodule 1032, the relocation condition judgment submodule 1033, and the update submodule 1034 if the loop execution conditions are met.

[0170] The project selection submodule 1031 is configured to determine, based on whether the proportion of specific resources corresponding to the first project owner is less than the corresponding expected proportion, projects with a specific resource proportion greater than or equal to or less than the target proportion from the project set corresponding to the current set of candidate project owners matching the first project owner, as candidate projects to be relocated. The operation of the project selection submodule 1031 can be referenced above. Figure 3 The operation described in section 340.

[0171] In one example, the project selection submodule 1031 is further configured as follows: if the proportion of specific resources corresponding to the first project owner is less than the corresponding expected proportion, the project with the largest proportion of specific resources in the project set corresponding to the current candidate project owner set matching the first project owner is determined as a candidate project to be relocated; if the proportion of specific resources corresponding to the first project owner is not less than the corresponding expected proportion, the project with the smallest proportion of specific resources in the project set corresponding to the current candidate project owner set matching the first project owner is determined as a candidate project to be relocated. The operation of the project selection submodule 1031 can be referenced above. Figure 5 The operation described in section 510-530.

[0172] The project owner selection submodule 1032 is configured to select the first project owner from those belonging to the positive category in the current project owner set; and to determine the project owner of the candidate project to be relocated as the second project owner. The operation of the project owner selection submodule 1032 can be found in [reference needed]. Figure 3 The operations described are 330 and 350.

[0173] The relocation condition judgment submodule 1033 is configured to determine whether the first project owner and the second project owner meet the corresponding relocation stop conditions based on the relationship between the current resource change amount and the corresponding target resource change amount and the threshold, respectively. The operation of the relocation condition judgment submodule 1033 can be found in [reference needed]. Figure 3 The description of 360's operations.

[0174] In one example, the relocation stopping condition for the first project owner includes: the current resource change for the first project owner is greater than or equal to the corresponding target resource change and less than or equal to the sum of the corresponding target resource change and the threshold; the relocation stopping condition for the second project owner includes: the current resource change for the second project owner is greater than or equal to the difference between the corresponding target resource change and the threshold and less than or equal to the corresponding target resource change.

[0175] In one example, the relocation stopping condition for the first project owner includes: the current resource change for the first project owner is greater than or equal to the difference between the corresponding target resource change and the threshold and is less than or equal to the corresponding target resource change, and the current error accumulation value for the first project owner is less than 0; the relocation stopping condition for the second project owner includes: the current resource change for the second project owner is greater than or equal to the corresponding target resource change and is less than or equal to the sum of the corresponding target resource change and the threshold, and the current error accumulation value for the second project owner is greater than or equal to 0.

[0176] The above content can be used as a reference. Figure 6 , Figure 7 Related descriptions.

[0177] The update submodule 1034 is configured to, in response to at least one of the first project owner and the second project owner satisfying the corresponding relocation stop condition, remove project owners that satisfy the corresponding relocation stop condition from the current project owner set to update the current project owner set; in response to neither the first project owner nor the second project owner satisfying the corresponding relocation stop condition, determine the candidate project to be relocated as the project to be relocated; generate project relocation information to indicate that the candidate project to be relocated is to be relocated from the second project owner to the first project owner, and update the ownership relationship between the current project owner set and the project; and update the current resource change amount corresponding to the first project owner and the second project owner respectively according to the resource amount corresponding to the project to be relocated; wherein, the updated current project owner set serves as the current project owner set for the next project relocation process, and the updated current resource change amount serves as the current resource change amount for the next project relocation process. The operation of the update submodule 1034 can be referred to above. Figure 3 The operations described in 370-379.

[0178] In one example, the update submodule 1034 is further configured to: in response to at least one of the first project owner and the second project owner satisfying the corresponding transfer stop condition, update the current error accumulation value to the sum of the difference between the target resource change amount corresponding to the removed project owner and the corresponding current resource change amount and the previous round error accumulation value.

[0179] The information generation module 1040 is configured to generate project relocation information based on the generated project relocation information if the cyclic execution condition is not met. The operation of the information generation module 1040 can be referred to above. Figure 3 The operation described in the 380.

[0180] Figure 11 A block diagram of an example of a device 1100 for user relocation between mechanisms according to an embodiment of this specification is shown. Figure 11 As shown, the device 1100 for transferring users between organizations may include a device 1110 for transferring projects between project owners. The device 1110 for transferring projects between project owners may refer to... Figure 9 or Figure 10 The relevant description is as follows. In one example, the project owner may include a financial institution, the project may include users, the resource quantity may include the loan amount, the specific resource ratio may include the bad debt risk rate, the target resource change may include the change in the loan amount, positive categories may be used to indicate financial institutions that expect to increase users, and negative categories may be used to indicate financial institutions that expect to decrease users.

[0181] Figure 12 A block diagram of an example of an apparatus 1200 for relocating physical machines between cloud service scenarios, according to an embodiment of this specification, is shown. Figure 12 As shown, the apparatus 1200 for relocating physical machines between cloud service scenarios may include an apparatus 1210 for relocating projects between project owners. The apparatus 1210 for relocating projects between project owners can be referenced from... Figure 9 or Figure 10 The relevant description is as follows. In one example, the project owner may include a cloud service scenario, the project may include physical machines, the resource quantity may include the cloud service resources provided by the physical machines, the specific resource ratio may include the failure rate, the target resource change may include the change in cloud service resource demand, positive categories may be used to indicate cloud service scenarios that expect to increase physical machines, and negative categories may be used to indicate cloud service scenarios that expect to decrease physical machines.

[0182] Reference above Figures 1 to 12 Embodiments of methods and apparatus for transferring projects between project owners, for transferring users between organizations, and for transferring physical machines between cloud service scenarios, according to embodiments of this specification, have been described.

[0183] The devices for transferring projects between project owners, transferring users between organizations, and transferring physical machines between cloud service scenarios described in this specification can be implemented in hardware, software, or a combination of both. Taking software implementation as an example, as a logical device, it is formed by the processor of its host device reading the corresponding computer program instructions from the memory into memory and executing them. In the embodiments of this specification, the devices for transferring projects between project owners, transferring users between organizations, and transferring physical machines between cloud service scenarios can, for example, be implemented using electronic devices.

[0184] Figure 13 A schematic diagram of an apparatus 1300 for transferring a project between project owners, according to an embodiment of this specification, is shown.

[0185] like Figure 13 As shown, the apparatus 1300 for transferring projects between project owners may include at least one processor 1310, a memory (e.g., non-volatile memory) 1320, a RAM 1330, and a communication interface 1340, and the at least one processor 1310, memory 1320, RAM 1330, and communication interface 1340 are connected together via a bus 1350. At least one processor 1310 executes at least one computer-readable instruction (i.e., the elements implemented in software described above) stored or encoded in the memory.

[0186] In one embodiment, computer-executable instructions are stored in memory, which, when executed, cause at least one processor 1310 to: acquire a set of project owners and a corresponding set of projects, wherein each project in the set of projects corresponds to a resource quantity and a specific resource ratio, each project owner in the set of project owners corresponds to a target resource change, each project belongs to one of the project owners, and each project owner belongs to a positive category of expected increase in projects or a negative category of expected decrease in projects; determine an objective function and relaxed constraints based on the set of project owners and the set of projects, wherein the objective function indicates that the specific resource ratio corresponding to each project owner after project relocation tends to a desired ratio, and the relaxed constraints include that the difference between the resource change corresponding to each project owner after project relocation and the target resource change corresponding to that project owner is no greater than a threshold; and generate project relocation information according to the objective function and the relaxed constraints, wherein the project relocation information indicates that at least one project to be relocated is determined from the set of projects to be relocated from its corresponding target negative project owner to its corresponding target positive project owner.

[0187] It should be understood that the computer-executable instructions stored in memory, when executed, cause at least one processor 1310 to perform the above-described combinations in the various embodiments of this specification. Figure 1-8 The description includes various operations and functions.

[0188] Specifically, a system or apparatus equipped with a readable storage medium may be provided, on which software program code implementing the functions of any of the embodiments described above is stored, and the computer or processor of the system or apparatus can read and execute the instructions stored in the readable storage medium.

[0189] In this case, the program code itself, which can be read from a readable medium, can perform the functions of any of the above embodiments. Therefore, the machine-readable code and the readable storage medium storing the machine-readable code constitute a part of the present invention.

[0190] The computer program code required for the operation of each part of this manual can be written in any one or more programming languages, including object-oriented programming languages ​​such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB, .NET, and Python; conventional procedural programming languages ​​such as C, Visual Basic 2003, Perl, COBOL 2002, PHP, and ABAP; dynamic programming languages ​​such as Python, Ruby, and Groovy; or other programming languages. This program code can run on the user's computer, or as a standalone software package on the user's computer, or partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any network, such as a local area network (LAN) or wide area network (WAN), or connected to an external computer (e.g., via the Internet), or in a cloud computing environment, or used as a service, such as Software as a Service (SaaS).

[0191] Examples of readable storage media include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD-RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, program code can be downloaded from a server computer or the cloud via a communication network.

[0192] The foregoing has described 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 that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0193] Not all steps and units in the above process and system structure diagrams are mandatory; some steps or units can be omitted as needed. The execution order of each step is not fixed and can be determined as required. The device structure described in the above embodiments can be a physical structure or a logical structure. That is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or they may be jointly implemented by certain components in multiple independent devices.

[0194] The term "exemplary" as used throughout this specification means "serving as an example, instance, or illustration" and does not imply that it is "preferred" or "advantageous" over other embodiments. Detailed descriptions are included for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these detailed descriptions. In some instances, well-known structures and apparatuses are shown in block diagram form to avoid obscuring the concepts of the described embodiments.

[0195] The optional embodiments of the present specification have been described in detail above with reference to the accompanying drawings. However, the embodiments of the present specification are not limited to the specific details in the above embodiments. Within the scope of the technical concept of the embodiments of the present specification, various simple modifications can be made to the technical solutions of the embodiments of the present specification, and these simple modifications all fall within the protection scope of the embodiments of the present specification.

[0196] The foregoing description of this specification is provided to enable any person skilled in the art to implement or use the content of this specification. Various modifications to the content of this specification will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of protection of this specification. Therefore, this specification is not limited to the examples and designs described herein, but is consistent with the widest scope of the principles and novel features disclosed herein.

Claims

1. A method for transferring a project between project owners, comprising: Obtain the project owner set and the corresponding project set, wherein each project in the project set corresponds to a resource quantity and a specific resource ratio, each project owner in the project owner set corresponds to a target resource change amount, each project belongs to one of the project owner sets, and each project owner belongs to either the positive category of expected increase in projects or the negative category of expected decrease in projects. Based on the project owner set and the project set, an objective function and relaxed constraints are determined. The objective function indicates that the proportion of specific resources corresponding to each project owner after project relocation tends to a desired ratio. The relaxed constraints include that the difference between the resource change corresponding to each project owner after project relocation and the target resource change corresponding to that project owner is no greater than a threshold. Based on the objective function and the relaxed constraints, project relocation information is generated, wherein the project relocation information is used to indicate that at least one project to be relocated from the project set is moved from the corresponding target negative project owner to the corresponding target positive project owner.

2. The method as described in claim 1, wherein, The threshold includes the maximum amount of resources corresponding to the projects in the project set.

3. The method as described in claim 1, wherein, The expected ratios include the target ratios corresponding to each project owner. Each target ratio is the ratio of the target specific resource quantity to the target resource quantity corresponding to the project owner. The target specific resource quantity includes the sum of the specific resource quantities corresponding to each project belonging to the project owner before the project relocation and the sum of the target specific resource change quantity corresponding to the project owner. The target specific resource change quantity is obtained using a linear programming method. The objective function of the linear programming method is determined based on the difference between the target ratio corresponding to each project owner and the global specific resource ratio corresponding to the project owner set.

4. The method of claim 1, wherein, The expected ratio includes the subset average specific resource ratio, which is the ratio of the sum of the specific resource amounts corresponding to each project of each project owner in the subset of the project owner set to the sum of the resource amounts corresponding to each project of each project owner in the subset, wherein the specific resource amount is the product of the corresponding resource amount and the specific resource ratio.

5. The method as described in any one of claims 1 to 4, wherein, The process of generating project relocation information based on the objective function and relaxed constraints includes: The project ownership set is determined as the current project ownership set; Determine whether the current project ownership set satisfies the loop execution condition; If the aforementioned cyclic execution conditions are met, the project relocation process will be executed: Select the first project owner from the project owners belonging to the positive category in the current project owner set, wherein the first project owner is the project owner whose difference between the corresponding specific resource proportion and the corresponding expected proportion is the largest. Based on whether the proportion of specific resources corresponding to the first project owner is less than the corresponding expected ratio, projects with a specific resource proportion greater than or equal to or less than the target ratio are determined from the project set corresponding to the current candidate project owner set matched with the first project owner as candidate projects to be transferred. The target ratio includes the proportion of specific resources corresponding to the first project owner. The relative size between the proportion of specific resources corresponding to each project owner in the matched current candidate project owner set and the corresponding expected ratio is inconsistent with the relative size corresponding to the first project owner. The project owner to which the candidate projects to be relocated belong is determined as the second project owner; Based on the relationship between the current resource change amount and the target resource change amount corresponding to the first project owner and the second project owner, respectively, and the threshold, it is determined whether the first project owner and the second project owner meet the corresponding transfer stop condition. In response to at least one of the first project owner and the second project owner satisfying the corresponding relocation cessation condition, the project owner that satisfies the corresponding relocation cessation condition is removed from the current project owner set to update the current project owner set; In response to the fact that neither the owner of the first project nor the owner of the second project meets the corresponding relocation cessation conditions. The aforementioned alternative relocation projects were identified as relocation projects. Generate project relocation information to indicate the relocation of the project from the second project owner to the first project owner, and update the ownership relationship between the current project owner set and the projects; and Based on the resource quantity corresponding to the project to be relocated, the current resource change quantity corresponding to the first project owner and the second project owner is updated respectively; wherein, the updated current project owner set serves as the current project owner set for the next project relocation process, and the updated current resource change quantity serves as the current resource change quantity for the next project relocation process. If the loop execution conditions are not met, the project relocation information is generated based on the generated project relocation information.

6. The method of claim 5, wherein, Determining whether the current project ownership set satisfies the loop execution condition includes: Determine whether the current project affiliation set contains the target project affiliation pair, wherein the two project affiliations contained in the target project affiliation pair belong to the positive category and the negative category respectively, and the relative sizes of the specific resource proportions corresponding to the two project affiliations and the corresponding expected ratios are inconsistent; If not included, it is determined that the current project affiliation set does not satisfy the loop execution condition.

7. The method of claim 6, wherein, The step of determining whether the current project ownership set satisfies the loop execution condition also includes: If included, determine that the current project ownership set satisfies the loop execution condition.

8. The method of claim 5, wherein, The step of determining, based on whether the proportion of specific resources corresponding to the first project owner is less than the corresponding expected proportion, projects with a specific resource proportion greater than or equal to or less than the target proportion value from the project set corresponding to the current set of candidate project owners matching the first project owner as candidate projects to be relocated includes: If the proportion of specific resources corresponding to the first project owner is less than the corresponding expected ratio, the project with the largest proportion of specific resources in the project set corresponding to the current candidate project owner set that matches the first project owner will be identified as the candidate project to be transferred. If the proportion of specific resources corresponding to the owner of the first project is not less than the corresponding expected ratio, the project with the smallest proportion of specific resources in the project set corresponding to the current candidate project owner set that matches the owner of the first project will be identified as the candidate project to be transferred.

9. The method of claim 5, wherein, The relocation cessation conditions corresponding to the owner of the first project include: the current resource change amount corresponding to the owner of the first project is greater than or equal to the corresponding target resource change amount and less than or equal to the sum of the corresponding target resource change amount and the threshold; The relocation cessation conditions corresponding to the owner of the second project include: the current resource change amount corresponding to the owner of the second project is greater than or equal to the difference between the corresponding target resource change amount and the threshold, and is less than or equal to the corresponding target resource change amount.

10. The method of claim 5, wherein, In response to at least one of the first project owner and the second project owner satisfying the corresponding relocation cessation condition, the method further includes: Update the current error accumulation value to the sum of the difference between the target resource change amount corresponding to the owner of the removed project and the corresponding current resource change amount, and the previous round error accumulation value; The relocation cessation conditions corresponding to the first project owner include: the current resource change amount corresponding to the first project owner is greater than or equal to the difference between the corresponding target resource change amount and the threshold and is less than or equal to the corresponding target resource change amount, and the current error accumulation value is less than 0; The relocation cessation conditions corresponding to the second project owner include: the current resource change amount corresponding to the second project owner is greater than or equal to the corresponding target resource change amount and less than or equal to the sum of the corresponding target resource change amount and the threshold, and the current error accumulation value is greater than or equal to 0.

11. A method for transferring users between institutions, comprising: The method as described in any one of claims 1 to 10, wherein the project owner includes a financial institution, the project includes users, the resource quantity includes loan amount, the specific resource ratio includes bad debt risk rate, the target resource change quantity includes loan amount change, the positive category is used to indicate financial institutions that expect to increase users, and the negative category is used to indicate financial institutions that expect to decrease users.

12. A method for relocating physical machines between cloud service scenarios, comprising: The method as described in any one of claims 1 to 10, wherein the project owner includes a cloud service scenario, the project includes physical machines, the resource quantity includes cloud service resources provided by the physical machines, the specific resource ratio includes the failure rate, the target resource change amount includes the change in cloud service resource demand, the positive category is used to indicate a cloud service scenario that expects to increase physical machines, and the negative category is used to indicate a cloud service scenario that expects to decrease physical machines.

13. An apparatus for transferring a project between project owners, comprising: The information acquisition unit is configured to acquire a set of project owners and a corresponding set of projects, wherein each project in the set of projects corresponds to a resource quantity and a specific resource ratio, each project owner in the set of project owners corresponds to a target resource change, each project belongs to one of the project owners in the set of project owners, and each project owner belongs to a positive category of expected increase of projects or a negative category of expected decrease of projects. A modeling unit is configured to determine an objective function and relaxed constraints based on the project owner set and the project set. The objective function indicates that the proportion of specific resources corresponding to each project owner after project relocation tends to a desired ratio. The relaxed constraints include that the difference between the resource change corresponding to each project owner after project relocation and the target resource change corresponding to that project owner is no greater than a threshold. The relocation information generation unit is configured to generate project relocation information based on the objective function and the relaxed constraints, wherein the project relocation information is used to indicate that at least one project to be relocated from the project set is moved from the corresponding target negative project owner to the corresponding target positive project owner.

14. An apparatus for facilitating user relocation between facilities, comprising: The apparatus of claim 13, wherein the project owner includes a financial institution, the project includes users, the resource quantity includes loan amount, the specific resource ratio includes bad debt risk rate, the target resource change quantity includes loan amount change, the positive category is used to indicate financial institutions that expect to increase users, and the negative category is used to indicate financial institutions that expect to decrease users.

15. An apparatus for relocating physical machines between cloud service scenarios, comprising: The apparatus of claim 13, wherein the project owner includes a financial institution, the project includes users, the resource quantity includes loan amount, the specific resource ratio includes bad debt risk rate, the target resource change quantity includes loan amount change, the positive category is used to indicate financial institutions that expect to increase users, and the negative category is used to indicate financial institutions that expect to decrease users.

16. An apparatus for transferring a project between project owners, comprising: At least one processor, a memory coupled to the at least one processor, and a computer program stored on the memory, wherein the at least one processor executes the computer program to implement the method as claimed in any one of claims 1 to 10 or to implement the method as claimed in claim 11 or 12.

Citation Information

Patent Citations

  • Dual-target robust resource allocation method under resource transfer view angle

    CN110070305A

  • Resource quantity determination method and device, equipment and storage medium

    CN116432915A