CN112131003A - Resource allocation method, device and equipment - Google Patents
Resource allocation method, device and equipment Download PDFInfo
- Publication number
- CN112131003A CN112131003A CN202011022418.4A CN202011022418A CN112131003A CN 112131003 A CN112131003 A CN 112131003A CN 202011022418 A CN202011022418 A CN 202011022418A CN 112131003 A CN112131003 A CN 112131003A
- Authority
- CN
- China
- Prior art keywords
- user
- application user
- core
- resource
- resources
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the specification provides a resource allocation method, a resource allocation device and resource allocation equipment. The method comprises the following steps: receiving a resource acquisition request sent by an application user; the resource acquisition request comprises the information of the application user; judging whether the application user is a core user or not according to the application user information; the core users include users having a right to invoke resources; determining whether the application user has a corresponding relation with at least one core user based on the application user information under the condition that the application user is not the core user; and if so, feeding back the resources to the application user. By the method, under the condition that the application user does not have the authority of directly acquiring the resources, the corresponding resources are distributed to the application user according to the relation between the application user and the core user, so that the normal execution of the service corresponding to the core user is guaranteed.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a resource allocation method, a resource allocation device and resource allocation equipment.
Background
In the process of daily processing business, in order to ensure the normal implementation of the corresponding business, project or task, it is generally required to utilize corresponding resources, for example, different types of resources such as currency resources or computing resources. Under the condition of limited resources, in order to avoid service progress caused by abuse of the resources, a user requesting the resources needs to be audited according to the importance degree of the service processed by the user, and the user after the audition can request to call the required resources; and the user who fails the audit can only call a small amount of resources or cannot call the resources.
However, in practical applications, the status of service processing is changing, and the degree of cooperation between users is increasing. In the process of processing the business, the user who fails to pass the audit may need to use the resource to provide the service for the user who passes the audit, but under the condition of not allocating the resource, the service provided by the user who fails to pass the audit may be affected to a certain extent, so that the business processed by the user who passes the audit is interfered, and the processing progress of the business is delayed. Therefore, a resource allocation method for guaranteeing the service processing progress is needed.
Disclosure of Invention
An object of the embodiments of the present specification is to provide a method, an apparatus, and a device for resource allocation, so as to solve a problem how to allocate resources to ensure normal processing of a service.
To solve the foregoing technical problem, an embodiment of the present application provides a resource allocation method, including:
receiving a resource acquisition request sent by an application user; the resource acquisition request comprises application user information corresponding to the application user;
judging whether the application user is a core user or not according to the application user information; the core users include users having a right to invoke resources;
determining whether the application user has a corresponding relation with at least one core user based on the application user information under the condition that the application user is not the core user;
and if so, feeding back the resources to the application user.
An embodiment of the present specification further provides a resource allocation apparatus, including:
the resource acquisition request receiving module is used for receiving a resource acquisition request sent by an application user; the resource acquisition request comprises application user information corresponding to the application user;
the core user judging module is used for judging whether the application user is a core user according to the application user information; the core users include users having a right to invoke resources;
the corresponding relation determining module is used for determining based on the application user information under the condition that the application user is not the core user;
and the resource feedback module is used for feeding back resources to the application user when the application user has a corresponding relationship with at least one core user.
The embodiment of the present specification further provides a resource allocation device, including a memory and a processor; the memory to store computer program instructions; the processor to execute the computer program instructions to implement the steps of: receiving a resource acquisition request sent by an application user; the resource acquisition request comprises application user information corresponding to the application user; judging whether the application user is a core user or not according to the application user information; the core users include users having a right to invoke resources; determining whether the application user has a corresponding relation with at least one core user based on the application user information under the condition that the application user is not the core user; and if so, feeding back the resources to the application user.
As can be seen from the technical solutions provided in the embodiments of the present specification, after receiving a resource acquisition request submitted by an application user, if the application user is not a core user, the embodiments of the present specification may determine whether a corresponding relationship exists between the application user and the core user. If the resource exists, certain resources can be allocated to the application user. By the method, under the condition that the application user is not the core user, certain resources can be acquired based on the relation between the application user and the core user, so that the normal execution of the service of the application user is ensured under the condition that the application user provides corresponding service for the core user. Correspondingly, under the condition that the corresponding relation exists between the application user and the core user, the resources are distributed for the application user, and the normal execution of the service of the core user is also ensured, so that the effective processing of the service of the core user is ensured, and the reasonable distribution of the resources is realized.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the specification, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart illustrating a resource allocation method according to an embodiment of the present disclosure;
FIG. 2 is a flowchart illustrating a resource allocation method according to an embodiment of the present disclosure;
FIG. 3 is a block diagram of a resource allocation apparatus according to an embodiment of the present disclosure;
fig. 4 is a block diagram of a resource allocation apparatus according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort shall fall within the protection scope of the present specification.
A resource allocation method according to an embodiment of the present disclosure is described below with reference to fig. 1. The execution main body of the method is resource distribution equipment, and the resource distribution equipment comprises but is not limited to a server, an industrial personal computer, a PC (personal computer) and the like. The resource allocation method comprises the following specific implementation steps.
S110: receiving a resource acquisition request sent by an application user; the resource acquisition request comprises the information of the application user.
The application user is a user who applies for resources. The application user may be an independent individual user or a user represented by a company, organization, or the like.
In the case that the application user is a request resource, the qualification of the application user is not limited. For example, the application user may be a user having a right to call a resource, or may not have a right to directly call a resource.
The resource may be an entity resource or a virtual resource.
In the case where the resource is an entity resource, the resource management server may be configured to manage allocation and usage of the resource. For example, in the case that the resource is an actual material, the resource management server may include owners corresponding to the actual materials, and usage of the corresponding actual materials by the owners. Correspondingly, when the entity resource is distributed to the user, the resource management server may send a corresponding instruction to the corresponding terminal device or the operator to complete the distribution of the entity resource.
In the case where the resource is a virtual resource, the resource management server may be used only for managing the allocation and usage of the resource, or may be used for a corresponding virtual resource. For example, in the case that the virtual resource is a computing resource, the virtual management server may be a server cluster including a plurality of servers, and the servers in the cluster may provide computing services for clients or other servers. Accordingly, the resource management server can handle the distribution of the virtual resource by itself.
In the case where the resource is a virtual resource, the resource may also be digital currency. The resource management server may be configured to manage accounts corresponding to a plurality of users and provide corresponding transfer services to the users from the corresponding accounts when the users make a demand for payment. For example, after the drawer provides the corresponding electronic bank acceptance draft to the resource management server of the bank, the resource management server can cash a certain amount of money to the drawer according to the electronic bank acceptance draft.
The application mode of the resource may be adjusted based on the requirement in the actual application, and is not limited to the above example, and is not described herein again.
The resource obtaining request is a request submitted to the resource allocation device by the application user for obtaining resources. The resource acquisition request may be for requesting a fixed amount of resources or may be for requesting resources only, and the amount of resources requested is determined by the resource allocation device.
In some embodiments, the resource acquisition request may be a request for a user to acquire a resource from the resource allocation device by mortgage of an item.
The mortgage articles can be physical resources or virtual resources. In the case that the mortgage articles are entity resources, the entity resources may be valuable articles such as actual goods and equipment, and correspondingly, the resource acquisition request may include specific information of the entity resources and a certificate requesting to replace the corresponding resource with the entity resource; in the case where the collateral item is a virtual resource, the virtual resource may be, for example, an electronic draft, which may draw certain funds when the draft expires, but the application user may mortgage the electronic draft to the resource distribution device to displace certain resources in advance before the electronic draft expires. In practical applications, when the mortgage articles are virtual resources, the mortgage articles are not limited to the electronic draft in the above example, and other valuable virtual resources can be used as the mortgage articles to replace the corresponding resources, which is not described herein again.
The resource obtaining request may include application user information of the application user. The application user information may include information of the application user itself. For example, in the case that the application user is an individual user, the application user information may include information such as a name, a birth year and month, a work condition, a home address, and the like of the application user; in the case that the application user is a company, an organization or an organization, the application user information may include information such as establishment time, a company type, employees included in the company, and specific information of the employees. In practical application, other information may also be added to the application user information according to specific needs, which is not described herein again.
The application user information may also include corresponding relationship information between the application user and other individuals and/or groups, for example, the application user provides a service to user a, the application user receives a service provided by user B, and the application user and user C are in an opposite relationship. In practical applications, the relationship between the application user and other individuals and/or groups is not limited to the above example, and the specific relationship may be expanded according to the situation in practical applications, and is not described herein again.
S120: judging whether the application user is a core user or not according to the application user information; the core users include users having a right to invoke a resource.
After the application user information is acquired, whether the application user is a core user can be judged according to the application user information. The core user may be a user having a right to invoke the resource, that is, the request for invoking the resource by the core user may be directly granted when the application user is determined to be the core user. The core user may have the right to acquire a certain amount of resources; when the resource acquisition request is to replace the resource by applying for the mortgage item of the user, the core user may also have the right to replace the resource by directly using the mortgage item. In practical applications, the manner for allocating the authority of the core user to invoke the resource may not be limited to the above example, and is not described herein again.
In some embodiments, the core user may be a user who submits a corresponding core user application to the resource allocation device in advance, and the resource allocation device performs an audit on the user. After the resource allocation device passes the user audit, it may be determined that the user is a core user.
The specific way of determining the core user may be that the user adds user information of the user and information such as specific use of the applied resource in the core user application, and the resource allocation device performs an audit on the user according to the information and by using a preset audit condition. Determining the user as a core user under the condition that the user meets the preset auditing condition; and if the user does not meet the preset auditing condition, rejecting the request of the user for becoming the core user. The specific preset auditing conditions can be adjusted according to the requirements of practical application, and are not described herein again.
After obtaining the application user information of the application user, the resource allocation device may determine whether the application user is a core user according to the application user information. Specifically, the data table including all the core users and the user information corresponding to the core users may be stored in the resource allocation device. After acquiring the application user information, the resource allocation device may search in the data table according to the application user information, and if a core user corresponding to the application user information can be found in the data table, it may be determined that the application user is a core user; and if the core user matched with the application user information cannot be found in the data table, determining that the application user is a non-core user.
In some embodiments, the information about whether the application user is a core user may be directly included in the information about the application user. After receiving the information of the application user, the resource allocation device can directly determine whether the application user is a core user, thereby saving corresponding judgment time.
In practical applications, the manner of determining whether the application user is the core user may be adjusted according to practical situations, and is not limited to the above example, and is not described herein again.
S130: and determining whether the application user has a corresponding relation with at least one core user based on the application user information under the condition that the application user is not the core user.
And if the application user is determined not to be the core user according to the application user information of the application user, corresponding resources cannot be directly allocated to the application user. However, in the case of only allocating resources to a core user, if the application user is a user serving the core user, the service processing progress of the core user may be affected by the application user in the case of lacking the allocated resources. Therefore, if the application user is not a core user, whether the application user has a corresponding relationship with at least one core user can be further determined.
In some embodiments, after determining that the application user is not a core user, it may be determined whether a correspondence relationship exists between the application user and at least one core user according to the application user information.
The corresponding relationship may be used to indicate one or more specific relationships between the application user and the core user. The application user can obtain the corresponding resources based on the corresponding relation.
In some specific examples, the correspondence may refer to a relationship in which the application user serves the core user. The applying user serving as the core user service may refer to that the applying user may be configured to process the service submitted by the core user, or the core user divides a certain sub-service from the service processed by the core user and processes the sub-service by the applying user, or the core user is configured to obtain a resource to generate another resource required by the core user. In practical applications, the condition that the application user serves the core user may not be limited to the above example, and may be adjusted according to the condition of practical applications, which is not described herein again.
In some specific embodiments, the correspondence relationship may also only refer to that the core user agrees to the application user to invoke a certain resource on its behalf. For example, in a case where the resource acquisition request is a request for replacing a certain resource by a ticket, if the ticket is a ticket related to at least one core user, the request for replacing the resource by the ticket may be granted to the application user.
In some specific embodiments, the corresponding relationship may also be a relationship determined after the application user sends the corresponding application user information to a core user, and the core user performs an audit on the application user based on a certain audit rule and the audit is passed. The specific audit rule may be set by the core user according to the corresponding requirement, which is not described herein again.
In practical application, other relationships may also be set as the corresponding relationships according to specific requirements, and are not limited to the above examples, which are not described again.
In practical application, only one relationship between the application user and the core user may be set as the corresponding relationship, or relationships between multiple application users and the core user may be set as the corresponding relationship, which is not limited to this. The corresponding relationship may also be set according to the requirements of practical applications, and is not limited to the above example, and is not described herein again.
In some embodiments, in order to enable the resource allocation device to determine whether the application user has a correspondence with at least one core user, the application user information of the application user may also include relationships between the application user and other users. Accordingly, the other users having a relationship with the application user may be individual users, or users of companies, organizations, or organizations. After the resource allocation device determines that the application user is not the core user, the resource allocation device may search whether there is a correspondence between the application user and the core user according to a relationship between the application user and another user included in the application user information.
In other embodiments, the resource allocation device may store a data table containing relationships between different users. After determining that the application user is not a core user, the resource allocation device may search, according to the application user information, other users having a correspondence with the application user in the data table. If there is a core user among the users, it can be determined that the application user and at least one core user have a corresponding relationship.
In practical applications, whether the application user and the core user have a corresponding relationship may also be determined by other methods according to specific requirements, which is not limited to the above examples and is not described herein again.
S140: and if so, feeding back the resources to the application user.
If the corresponding relationship exists between the application user and at least one core user, the application user is indicated to call corresponding resources depending on the credit of the core user, or the application user provides services for the core user by acquiring the resources. In this case, allocating resources to the application user can also ensure smooth execution of the service of the core user or the core user can accelerate the progress of processing the service. Therefore, if it is determined that the corresponding relationship exists between the application user and at least one core user, resources can be fed back to the application user.
In some embodiments, when the application user requests a resource from the resource allocation device, the resource acquisition request may include an amount of the resource that the application user desires to acquire, for example, the resource acquisition request may be used to request a resource corresponding to a first allocation amount. Correspondingly, when the application user is not a core user but a corresponding relationship exists between the application user and at least one core user, a certain resource may be allocated to the application user, the amount of the allocated resource may be a fourth allocation amount, and the fourth allocation amount is smaller than the first allocation amount.
Using one specific example for illustration, where the applicant user wishes to obtain certain funds by mortgaging an electronic draft associated with a core user, the amount of funds corresponding to the electronic draft is a first amount. The amount of funds that the applicant wishes to replace in the resource acquisition request submitted by the user is the first amount. And after the resource allocation device checks the resource acquisition request and the electronic draft, the resource quantity provided for the application user is a fourth quantity, and the fourth quantity is smaller than the first quantity.
Based on the above embodiment, after determining whether the application user has a corresponding relationship with at least one core user, if the application user does not have the corresponding relationship with any core user, the application user may also select to provide resources for the application user, where the amount of the provided resources is a fifth allocation amount, and the fifth allocation amount is smaller than the fourth allocation amount.
By way of a specific example, when replacing resources with the same mortgage item, a non-core user who has a correspondence relationship with at least one core user may replace more resources than a non-core user who does not have a correspondence relationship with any core user.
In some embodiments, the resource allocation device stores therein a resource conversion ratio. When the resource acquisition request is that the application user acquires resources by mortgage articles, the resource conversion proportion can have different sizes corresponding to different corresponding relations, that is, different quantities of resources are allocated to the application user for the same mortgage article. For example, in the case that the correspondence only indicates that the core user allows to obtain the corresponding resource on its behalf, the correspondence may correspond to a smaller resource conversion ratio, i.e., allocate less resources to the application user; in a case where the corresponding relationship indicates that the application user is configured to assist the core user in processing the corresponding service, the corresponding relationship may have a higher resource conversion ratio, that is, more resources are allocated to the application user. In practical application, corresponding resources may also be allocated to the application user according to a specific situation of implementing the service based on the correspondence between the application user and the core user, which is not limited to the above example and is not described herein again.
By the embodiment of the method, after the resource acquisition request submitted by the application user is received, if the application user is not the core user, whether the corresponding relationship exists between the application user and the core user can be judged. If the resource exists, certain resources can be allocated to the application user. By the method, under the condition that the application user is not the core user, certain resources can be acquired based on the relation between the application user and the core user, so that the normal execution of the service of the application user is ensured under the condition that the application user provides corresponding service for the core user. Correspondingly, under the condition that the corresponding relation exists between the application user and the core user, the resources are distributed for the application user, and the normal execution of the service of the core user is also ensured, so that the effective processing of the service of the core user is ensured, and the reasonable distribution of the resources is realized.
In practical applications, when determining whether the application user is the core user and determining the corresponding relationship between the non-core user and other core users, other situations may occur, for example, the application user is the core user or there is no corresponding relationship between the application user and other core users. In view of the above situation, an embodiment of the present specification further provides a resource allocation method. The execution subject of the resource allocation method may also be the resource allocation apparatus. As shown in fig. 2, the resource allocation method includes the following specific implementation steps.
S210: receiving a resource acquisition request sent by an application user; the resource acquisition request comprises the information of the application user; the resource acquisition request is used for acquiring a first allocated amount of resources.
The application user is a user who applies for resources. The application user may be an independent individual user or a user represented by a company, organization, or the like.
In the case that the application user is a request resource, the qualification of the application user is not limited. For example, the application user may be a user having a right to call a resource, or may not have a right to directly call a resource.
The resource may be an entity resource or a virtual resource.
In the case where the resource is an entity resource, the resource management server may be configured to manage allocation and usage of the resource. For example, in the case that the resource is an actual material, the resource management server may include owners corresponding to the actual materials, and usage of the corresponding actual materials by the owners. Correspondingly, when the entity resource is distributed to the user, the resource management server may send a corresponding instruction to the corresponding terminal device or the operator to complete the distribution of the entity resource.
In the case where the resource is a virtual resource, the resource management server may be used only for managing the allocation and usage of the resource, or may be used for a corresponding virtual resource. For example, in the case that the virtual resource is a computing resource, the virtual management server may be a server cluster including a plurality of servers, and the servers in the cluster may provide computing services for clients or other servers. Accordingly, the resource management server can handle the distribution of the virtual resource by itself.
In the case where the resource is a virtual resource, the resource may also be digital currency. The resource management server may be configured to manage accounts corresponding to a plurality of users and provide corresponding transfer services to the users from the corresponding accounts when the users make a demand for payment. For example, after the drawer provides the corresponding electronic bank acceptance draft to the resource management server of the bank, the resource management server can cash a certain amount of money to the drawer according to the electronic bank acceptance draft.
The application mode of the resource may be adjusted based on the requirement in the actual application, and is not limited to the above example, and is not described herein again.
The resource obtaining request is a request submitted to the resource allocation device by the application user for obtaining resources. The resource acquisition request may be for requesting a fixed amount of resources or may be for requesting resources only, and the amount of resources requested is determined by the resource allocation device.
In some embodiments, the resource acquisition request may be a request for a user to acquire a resource from the resource allocation device by mortgage of an item.
The mortgage articles can be physical resources or virtual resources. In the case that the mortgage articles are entity resources, the entity resources may be valuable articles such as actual goods and equipment, and correspondingly, the resource acquisition request may include specific information of the entity resources and a certificate requesting to replace the corresponding resource with the entity resource; in the case where the collateral item is a virtual resource, the virtual resource may be, for example, an electronic draft, which may draw certain funds when the draft expires, but the application user may mortgage the electronic draft to the resource distribution device to displace certain resources in advance before the electronic draft expires. In practical applications, when the mortgage articles are virtual resources, the mortgage articles are not limited to the electronic draft in the above example, and other valuable virtual resources can be used as the mortgage articles to replace the corresponding resources, which is not described herein again.
The resource obtaining request may include application user information of the application user. The application user information may include information of the application user itself. For example, in the case that the application user is an individual user, the application user information may include information such as a name, a birth year and month, a work condition, a home address, and the like of the application user; in the case that the application user is a company, an organization or an organization, the application user information may include information such as establishment time, a company type, employees included in the company, and specific information of the employees. In practical application, other information may also be added to the application user information according to specific needs, which is not described herein again.
The application user information may also include corresponding relationship information between the application user and other individuals and/or groups, for example, the application user provides a service to user a, the application user receives a service provided by user B, and the application user and user C are in an opposite relationship. In practical applications, the relationship between the application user and other individuals and/or groups is not limited to the above example, and the specific relationship may be expanded according to the situation in practical applications, and is not described herein again.
The resource obtaining request may include the number of resources that the application user desires to obtain, that is, the first allocation number. The first allocation amount may be the amount of the resource allocated to the resource allocation device requested by the application user, or may be the amount of the resource that the application user wants to obtain when replacing the resource by a collateral item. The resource allocation device may determine, according to the specific situation of the application user and the first allocation amount, the specific amount of the resource allocated to the application user.
S220: and judging whether the application user is a core user or not according to the application user information.
After the application user information is acquired, whether the application user is a core user can be judged according to the application user information. The core user may be a user having a right to invoke the resource, that is, the request for invoking the resource by the core user may be directly granted when the application user is determined to be the core user. The core user may have the right to acquire a certain amount of resources; when the resource acquisition request is to replace the resource by applying for the mortgage item of the user, the core user may also have the right to replace the resource by directly using the mortgage item. In practical applications, the manner for allocating the authority of the core user to invoke the resource may not be limited to the above example, and is not described herein again.
In some embodiments, the core user may be a user who submits a corresponding core user application to the resource allocation device in advance, and the resource allocation device performs an audit on the user. After the resource allocation device passes the user audit, it may be determined that the user is a core user.
The specific way of determining the core user may be that the user adds user information of the user and information such as specific use of the applied resource in the core user application, and the resource allocation device performs an audit on the user according to the information and by using a preset audit condition. Determining the user as a core user under the condition that the user meets the preset auditing condition; and if the user does not meet the preset auditing condition, rejecting the request of the user for becoming the core user. The specific preset auditing conditions can be adjusted according to the requirements of practical application, and are not described herein again.
After obtaining the application user information of the application user, the resource allocation device may determine whether the application user is a core user according to the application user information. Specifically, the data table including all the core users and the user information corresponding to the core users may be stored in the resource allocation device. After acquiring the application user information, the resource allocation device may search in the data table according to the application user information, and if a core user corresponding to the application user information can be found in the data table, it may be determined that the application user is a core user; and if the core user matched with the application user information cannot be found in the data table, determining that the application user is a non-core user.
In some embodiments, the information about whether the application user is a core user may be directly included in the information about the application user. After receiving the information of the application user, the resource allocation device can directly determine whether the application user is a core user, thereby saving corresponding judgment time.
In practical applications, the manner of determining whether the application user is the core user may be adjusted according to practical situations, and is not limited to the above example, and is not described herein again.
If the determination result is that the application user is not the core user, executing step S230; if the determination result is that the application user is the core user, step S260 is executed.
S230: and judging whether the application user has a corresponding relation with at least one core user.
And if the application user is determined not to be the core user according to the application user information of the application user, corresponding resources cannot be directly allocated to the application user. However, in the case of only allocating resources to a core user, if the application user is a user serving the core user, the service processing progress of the core user may be affected by the application user in the case of lacking the allocated resources. Therefore, if the application user is not a core user, whether the application user has a corresponding relationship with at least one core user can be further determined.
In some embodiments, after determining that the application user is not a core user, it may be determined whether a correspondence relationship exists between the application user and at least one core user according to the application user information.
The corresponding relationship may be used to indicate one or more specific relationships between the application user and the core user. The application user can obtain the corresponding resources based on the corresponding relation.
In some specific examples, the correspondence may refer to a relationship in which the application user serves the core user. The applying user serving as the core user service may refer to that the applying user may be configured to process the service submitted by the core user, or the core user divides a certain sub-service from the service processed by the core user and processes the sub-service by the applying user, or the core user is configured to obtain a resource to generate another resource required by the core user. In practical applications, the condition that the application user serves the core user may not be limited to the above example, and may be adjusted according to the condition of practical applications, which is not described herein again.
In some specific embodiments, the correspondence relationship may also only refer to that the core user agrees to the application user to invoke a certain resource on its behalf. For example, in a case where the resource acquisition request is a request for replacing a certain resource by a ticket, if the ticket is a ticket related to at least one core user, the request for replacing the resource by the ticket may be granted to the application user.
In some specific embodiments, the corresponding relationship may also be a relationship determined after the application user sends the corresponding application user information to a core user, and the core user performs an audit on the application user based on a certain audit rule and the audit is passed. The specific audit rule may be set by the core user according to the corresponding requirement, which is not described herein again.
In practical application, other relationships may also be set as the corresponding relationships according to specific requirements, and are not limited to the above examples, which are not described again.
In practical application, only one relationship between the application user and the core user may be set as the corresponding relationship, or relationships between multiple application users and the core user may be set as the corresponding relationship, which is not limited to this. The corresponding relationship may also be set according to the requirements of practical applications, and is not limited to the above example, and is not described herein again.
In some embodiments, in order to enable the resource allocation device to determine whether the application user has a correspondence with at least one core user, the application user information of the application user may also include relationships between the application user and other users. Accordingly, the other users having a relationship with the application user may be individual users, or users of companies, organizations, or organizations. After the resource allocation device determines that the application user is not the core user, the resource allocation device may search whether there is a correspondence between the application user and the core user according to a relationship between the application user and another user included in the application user information.
In other embodiments, the resource allocation device may store a data table containing relationships between different users. After determining that the application user is not a core user, the resource allocation device may search, according to the application user information, other users having a correspondence with the application user in the data table. If there is a core user among the users, it can be determined that the application user and at least one core user have a corresponding relationship.
In practical applications, whether the application user and the core user have a corresponding relationship may also be determined by other methods according to specific requirements, which is not limited to the above examples and is not described herein again.
If the determination result is that the corresponding relationship exists between the application user and at least one core user, executing step S240; if the determination result is that there is no correspondence between the application user and any core user, step S270 is executed.
It should be noted that, in some embodiments, the number of resources held by the resource allocation device may be limited. After allocating resources to core users, there may not be more resources that can be allocated. If resources are allocated to the application user based on the correspondence between the application user and the core user, the resources allocated to the core user may be reduced. Therefore, in some embodiments, after determining that the application user is not the core user, the resource acquisition request of the application user may be directly rejected.
Specifically, a judgment switch may be preset, and the judgment switch is turned on when it is determined that a certain resource may be allocated to the non-core user, and step S230 is executed when it is determined that the application user is not the core user; and under the condition that the resource is not required to be allocated to the non-core user, the judgment switch is closed, and under the condition that the application user is not the core user, the resource acquisition request of the application user is directly refused.
The above-described embodiments guarantee the number of resources allocated to the non-core users in the case of a small number of resources, thereby being able to ensure normal execution of services corresponding to the non-core users.
S240: and judging whether the corresponding relation contains a service relation.
If there is a corresponding relationship between the application user and at least one core user, it can also be determined whether the corresponding relationship includes a service relationship. And the service relation is used for expressing that the application user provides service for the core user based on the acquired resources. Specifically, the applying user may output other resources for the core user to use based on the acquired resources, or assist the core user in processing corresponding services based on the acquired resources. In practical application, the service relationship may also be set based on specific requirements, which is not limited to the above example and is not described in detail here.
And under the condition that the application user and the core user are in a service relationship, the application user can promote the execution of the service of the core user after acquiring the resources. Correspondingly, more resources are allocated to the application user, and the service processing progress of the core user can be accelerated. Therefore, the amount of resources allocated to the application user can be determined according to whether the corresponding relationship includes a service relationship.
If the corresponding relationship includes the service relationship, executing step S250; if the corresponding relationship does not include the service relationship, step S280 is executed.
S250: and allocating a second allocated amount of resources to the application user.
When a corresponding relationship exists between the application user and at least one core user and the corresponding relationship includes a service relationship, a second allocated amount of resources may be allocated to the application user. In a case where the application user requests the first allocated amount of resources in the resource acquisition request, the second allocated amount may be a resource amount that is not greater than the first allocated amount, that is, the second allocated amount may be equal to the first allocated amount, or may be smaller than the first allocated amount. The specific setting of the second allocation quantity may be adjusted according to the requirement of the actual application, and is not limited to the above example, and is not described herein again.
S260: and allocating the first allocated amount of resources to the application user.
If it is determined that the application user is the core user based on the determination result in step S220, the corresponding resource may be directly allocated to the application user. Specifically, when the resource acquisition request submitted by the application user is used to acquire the first allocated amount of resources, the first allocated amount of resources may be directly allocated to the application user.
S270: and rejecting the resource acquisition request of the application user.
If it is determined that no corresponding relationship exists between the application user and any core user based on the determination result in step S230, the resource acquisition request of the application user may be directly received without allocating any resource to the application user, thereby ensuring the requirement of the core user for the resource and ensuring the execution of the service of the core user.
S280: and allocating the third allocation amount of resources to the application user.
If it is determined that a corresponding relationship exists between the application user and at least one core user based on the determination result in step S240, but the corresponding relationship does not include a service relationship, that is, the application user may not directly provide corresponding services for the core user after acquiring resources, and if more resources are allocated to the application user, allocation of resources to the core user or other users having a closer relationship with the core user may be affected.
Therefore, when there is a corresponding relationship between the application user and at least one core user, but the corresponding relationship does not include a service relationship, a third allocation amount of resources may be allocated to the application user. The third allocation amount is less than the second allocation amount. By using a specific example, in the case of replacing resources by using the same mortgage article, an application user having a service relationship with a core user can replace more resources than an application user having no service relationship with the core user. When a service relationship exists between an application user and a core user, the application user can better guarantee the execution of the service of the core user after acquiring the resources. Therefore, setting the size relationship between the second allocation quantity and the third allocation quantity can better ensure the service execution of the core user.
According to the embodiment of the resource allocation method, whether the relation exists between the application user and the core user or not and the specific relation between the application user and the core user is different, whether the resource is provided for the application user or not can be selected, and the quantity of the resource allocated to the application user can be adjusted, so that the resource is effectively and reasonably allocated, the resource utilization of the corresponding user is guaranteed, and the execution of the service is facilitated.
A resource allocation apparatus according to an embodiment of the present disclosure is introduced based on a resource allocation method corresponding to fig. 1. The resource allocation device may be disposed in the resource allocation apparatus. As shown in fig. 3, the resource allocation apparatus includes the following modules.
A resource obtaining request receiving module 310, configured to receive a resource obtaining request sent by an application user; the resource acquisition request comprises application user information corresponding to the application user;
a core user determining module 320, configured to determine whether the application user is a core user according to the application user information; the core users include users having a right to invoke resources;
a corresponding relationship determining module 330, configured to determine based on the application user information if the application user is not a core user;
the resource feedback module 340 is configured to feed back resources to the application user when the application user has a corresponding relationship with at least one core user.
Based on the resource allocation method corresponding to fig. 1, an embodiment of the present specification provides a resource allocation apparatus. As shown in fig. 4, the resource allocation device may include a memory and a processor.
In this embodiment, the memory may be implemented in any suitable manner. For example, the memory may be a read-only memory, a mechanical hard disk, a solid state disk, a U disk, or the like. The memory may be used to store computer program instructions.
In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth. The processor may execute the computer program instructions to perform the steps of: receiving a resource acquisition request sent by an application user; the resource acquisition request comprises application user information corresponding to the application user; judging whether the application user is a core user or not according to the application user information; the core users include users having a right to invoke resources; determining whether the application user has a corresponding relation with at least one core user based on the application user information under the condition that the application user is not the core user; and if so, feeding back the resources to the application user.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as ABEL (Advanced Boolean Expression Language), AHDL (alternate Hardware Description Language), traffic, CUPL (core universal Programming Language), HDCal, jhddl (Java Hardware Description Language), Lava, Lola, HDL, PALASM, rhyd (Hardware Description Language), and vhigh-Language (Hardware Description Language), which is currently used in most popular applications. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
From the above description of the embodiments, it is clear to those skilled in the art that the present specification can be implemented by software plus the necessary first hardware platform. Based on such understanding, the technical solutions of the present specification may be essentially or partially implemented in the form of software products, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and include instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The description is operational with numerous first or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
While the specification has been described with examples, those skilled in the art will appreciate that there are numerous variations and permutations of the specification that do not depart from the spirit of the specification, and it is intended that the appended claims include such variations and modifications that do not depart from the spirit of the specification.
Claims (15)
1. A method for resource allocation, comprising:
receiving a resource acquisition request sent by an application user; the resource acquisition request comprises the information of the application user;
judging whether the application user is a core user or not according to the application user information; the core users include users having a right to invoke resources;
determining whether the application user has a corresponding relation with at least one core user based on the application user information under the condition that the application user is not the core user;
and if so, feeding back the resources to the application user.
2. The method of claim 1, wherein the resource acquisition request is used to replace a resource by applying for a mortgage item of a user.
3. The method of claim 1, wherein the corresponding relationship comprises a relationship determined after the application user sends the application user information to a core user, and the core user reviews the application user information.
4. The method of claim 1, wherein the correspondence includes a partnership and an affiliation; after determining whether the application user has a corresponding relationship with at least one core user based on the application user information, the method further includes:
if the application user has a corresponding relationship with at least one core user and the corresponding relationship is a service relationship, feeding back resources to the application user; and the service relation is used for expressing that the application user provides service for the core user based on the acquired resources.
5. The method of claim 4, wherein the resource acquisition request is for acquiring a first allocated amount of resources; if the application user has a corresponding relationship with at least one core user, and the corresponding relationship is a service relationship, feeding back resources to the application user, including:
if the application user has a corresponding relationship with at least one core user and the corresponding relationship is a service relationship, feeding back a second distributed amount of resources to the application user; the second allocation quantity is not greater than the first allocation quantity.
6. The method of claim 5, wherein after determining whether the application user has a correspondence with at least one core user based on the application user information, further comprising:
if the application user and at least one core user have a corresponding relationship and the corresponding relationship does not contain a service relationship, feeding back a third allocation amount of resources to the application user; the third allocation amount is less than the second allocation amount.
7. The method of claim 1, wherein after determining whether the application user is a core user according to the application user information, the method further comprises:
and rejecting the resource acquisition request of the application user.
8. The method of claim 1, wherein the resource acquisition request is for acquiring a first allocated amount of resources; the feedback of resources to the application user comprises:
feeding back the fourth distributed amount of resources to the application user; the fourth allocated quantity is less than the first allocated quantity.
9. The method of claim 8, wherein after determining whether the application user has a correspondence with at least one core user based on the application user information, further comprising:
if not, feeding back the resources of the fifth allocation quantity to the application user; the fifth dispense quantity is less than the fourth dispense quantity.
10. The method of claim 1, wherein after determining whether the application user is a core user according to the application user information, the method further comprises:
and under the condition that the application user is a core user, feeding back the resource to the core user.
11. The method of claim 10, wherein the resource acquisition request is for acquiring a first allocated amount of resources, and wherein the feeding back the resources to the core users comprises:
feeding back the first allocated amount of resources to the core user.
12. The method of claim 1, wherein after determining whether the application user has a correspondence with at least one core user based on the application user information, further comprising:
and if the request does not exist, rejecting the resource acquisition request of the application user.
13. The method of claim 1, wherein the feeding back resources to the requesting user comprises:
feeding back resources to the application user based on the resource conversion proportion corresponding to the corresponding relation; the resource conversion proportion comprises the proportion of the resource quantity applied by the application user to the resource quantity fed back to the application user.
14. A resource allocation apparatus, comprising:
the resource acquisition request receiving module is used for receiving a resource acquisition request sent by an application user; the resource acquisition request comprises application user information corresponding to the application user;
the core user judging module is used for judging whether the application user is a core user according to the application user information; the core users include users having a right to invoke resources;
the corresponding relation determining module is used for determining based on the application user information under the condition that the application user is not the core user;
and the resource feedback module is used for feeding back resources to the application user when the application user has a corresponding relationship with at least one core user.
15. A resource allocation apparatus comprising a memory and a processor;
the memory to store computer program instructions;
the processor to execute the computer program instructions to implement the steps of: receiving a resource acquisition request sent by an application user; the resource acquisition request comprises application user information corresponding to the application user; judging whether the application user is a core user or not according to the application user information; the core users include users having a right to invoke resources; determining whether the application user has a corresponding relation with at least one core user based on the application user information under the condition that the application user is not the core user; and if so, feeding back the resources to the application user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011022418.4A CN112131003A (en) | 2020-09-25 | 2020-09-25 | Resource allocation method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011022418.4A CN112131003A (en) | 2020-09-25 | 2020-09-25 | Resource allocation method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112131003A true CN112131003A (en) | 2020-12-25 |
Family
ID=73840633
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011022418.4A Pending CN112131003A (en) | 2020-09-25 | 2020-09-25 | Resource allocation method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112131003A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117931399A (en) * | 2024-01-15 | 2024-04-26 | 北京石境科技有限公司 | Distributed rendering method, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8495197B1 (en) * | 2011-09-29 | 2013-07-23 | Amazon Technologies, Inc. | Resource pooling and subletting from user to another user |
| US20180041449A1 (en) * | 2016-08-08 | 2018-02-08 | Bank Of America Corporation | Resource assignment system |
| CN109584028A (en) * | 2017-09-25 | 2019-04-05 | 上海策赢网络科技有限公司 | A kind of virtual resource allocation method and device |
| CN110175824A (en) * | 2019-05-22 | 2019-08-27 | 上海盛付通电子支付服务有限公司 | For carrying out the equipment and resource allocation method of resource distribution |
| CN110533522A (en) * | 2019-07-12 | 2019-12-03 | 平安普惠企业管理有限公司 | Resource allocation checking method, electronic device and computer readable storage medium |
| CN111191221A (en) * | 2019-12-30 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Method and device for configuring authority resources and computer readable storage medium |
| CN111681092A (en) * | 2020-04-22 | 2020-09-18 | 上海淇玥信息技术有限公司 | Resource scheduling method, server, electronic device and storage medium |
-
2020
- 2020-09-25 CN CN202011022418.4A patent/CN112131003A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8495197B1 (en) * | 2011-09-29 | 2013-07-23 | Amazon Technologies, Inc. | Resource pooling and subletting from user to another user |
| US20180041449A1 (en) * | 2016-08-08 | 2018-02-08 | Bank Of America Corporation | Resource assignment system |
| CN109584028A (en) * | 2017-09-25 | 2019-04-05 | 上海策赢网络科技有限公司 | A kind of virtual resource allocation method and device |
| CN110175824A (en) * | 2019-05-22 | 2019-08-27 | 上海盛付通电子支付服务有限公司 | For carrying out the equipment and resource allocation method of resource distribution |
| CN110533522A (en) * | 2019-07-12 | 2019-12-03 | 平安普惠企业管理有限公司 | Resource allocation checking method, electronic device and computer readable storage medium |
| CN111191221A (en) * | 2019-12-30 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Method and device for configuring authority resources and computer readable storage medium |
| CN111681092A (en) * | 2020-04-22 | 2020-09-18 | 上海淇玥信息技术有限公司 | Resource scheduling method, server, electronic device and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117931399A (en) * | 2024-01-15 | 2024-04-26 | 北京石境科技有限公司 | Distributed rendering method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109783229B (en) | Thread resource allocation method and device | |
| KR100322724B1 (en) | Apparatus and method for scheduling and dispatching queued client requests within a server in a client/server computer system | |
| WO2020042290A1 (en) | Risk management method, and apparatus and computer-readable storage medium | |
| CN107070858A (en) | A kind of method for processing business and device | |
| CN111552945B (en) | Resource processing method, device and equipment | |
| CN110381150B (en) | Data processing method and device on block chain, electronic equipment and storage medium | |
| CN108171488B (en) | Data processing method, apparatus and system | |
| CN110706093A (en) | Accounting processing method and device | |
| CN112686528B (en) | Method, device, server and medium for distributing customer service resources | |
| US10324907B2 (en) | Genomic application data storage | |
| CN110992011A (en) | Data splitting method and device, electronic equipment and storage medium | |
| WO2024032356A1 (en) | Payment processing method and apparatus based on prepayment voucher | |
| CN112131003A (en) | Resource allocation method, device and equipment | |
| CN107147610B (en) | Resource processing method and device | |
| CN114285906B (en) | Message processing method and device, electronic equipment and storage medium | |
| CN107301550B (en) | Methods for obtaining quota information, methods and devices for establishing quota control rules | |
| CN113114678B (en) | Service execution method and device | |
| CN113472687A (en) | Data processing method and device | |
| CN113221177A (en) | Data access method, device and system in distributed system | |
| CN109426561A (en) | A kind of task processing method, device and equipment | |
| CN111754332B (en) | Service request processing method and device, storage medium and electronic equipment | |
| CN109657179A (en) | A kind of method for processing business, system and storage medium | |
| CN112181643B (en) | A method and device for resource allocation | |
| CN112085419B (en) | Resource acquisition method, device and equipment | |
| CN115795097A (en) | Data processing method and device based on XML logic rules |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |