CN112737827A - Resource allocation method, device and system - Google Patents
Resource allocation method, device and system Download PDFInfo
- Publication number
- CN112737827A CN112737827A CN202011548295.8A CN202011548295A CN112737827A CN 112737827 A CN112737827 A CN 112737827A CN 202011548295 A CN202011548295 A CN 202011548295A CN 112737827 A CN112737827 A CN 112737827A
- Authority
- CN
- China
- Prior art keywords
- resource
- resource allocation
- user
- current user
- target
- 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
- 238000013468 resource allocation Methods 0.000 title claims abstract description 183
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000007726 management method Methods 0.000 claims description 73
- 230000006870 function Effects 0.000 claims description 32
- 238000013507 mapping Methods 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 claims description 6
- 238000005457 optimization Methods 0.000 claims description 6
- 230000001133 acceleration Effects 0.000 claims description 5
- 238000011084 recovery Methods 0.000 claims description 3
- 239000003795 chemical substances by application Substances 0.000 description 9
- 238000010586 diagram Methods 0.000 description 7
- 239000000243 solution Substances 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000005265 energy consumption Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0889—Techniques to speed-up the configuration process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Abstract
The invention discloses a resource allocation method, a device and a system. Wherein, the method comprises the following steps: receiving a resource allocation request from a terminal device, wherein the resource allocation request comprises a user identifier, a user type and a resource use level of a current user of the terminal device; judging whether a resource allocation strategy associated with the user identification exists in a local database; and if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource use level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database. The invention solves the technical problem that the efficiency of resource allocation is poor because the cloud office resources cannot be allocated effectively in the prior art.
Description
Technical Field
The invention relates to the technical field of cloud office, in particular to a resource allocation method, device and system.
Background
A basic structure of a cloud office system in the prior art can refer to fig. 1, and as shown in fig. 1, the cloud office system is based on a VGTP image transmission protocol and mainly includes a zero terminal (a built-in VGTP-R terminal, referred to as an R terminal for short) and a cloud server terminal (a built-in VGTP-S terminal, referred to as an S terminal for short). The R end is used for receiving the image of the virtual desktop from the cloud end, transmitting the local mouse and keyboard information to the cloud end in a reverse mode, and injecting the information into the virtual desktop corresponding to the current R end through the cloud end, wherein the virtual desktop is generated by virtual machines distributed to the current zero terminal by a cloud server; and the S end is an image acquisition and coding module running in the cloud virtual OS and is responsible for performing an injection function of user input data.
The cloud server is generally based on an IAAS architecture, is a server with a strong virtual host, and can provide management functions of a plurality of virtual machines through hypervisor to provide a running hardware environment for the virtual machines. The virtual machine is provided with S-end software, the zero terminal is provided with R-end software, the S-end software is used for collecting, coding and sending images, and the R-end software is used for receiving and decoding the images. However, the existing cloud office structure diagram only shows a basic image transmission structure in the current cloud office system, and actually, very many system-level management services, such as authentication management, update management, license management, resource management, etc., are also involved in enterprise-level applications, and it is actually troublesome if such a complete and bulky system is to be built in an enterprise.
Therefore, a solution idea in the prior art is that a service provider provides services of the entire cloud office system, and after an enterprise purchases corresponding services, the service provider performs personalized customized services according to needs of the enterprise, but this method is still a code-level process, because management and configuration of different servers, such as an authentication management server, an update management server, a license management server, a resource management server, and the like, are involved, and the management and configuration are completely performed in the background, this method is still not simple and convenient enough, and on one hand, management and allocation of various resources are dispersed and independent, and efficiency is lacked; on the other hand, it is not intuitive for the user.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides a resource allocation method, a resource allocation device and a resource allocation system, which are used for at least solving the technical problem that the efficiency of resource allocation is poor due to the fact that cloud office resources cannot be allocated effectively in the prior art.
According to an aspect of the embodiments of the present invention, there is provided a resource allocation method, including: receiving a resource allocation request from a terminal device, wherein the resource allocation request comprises a user identifier, a user type and a resource use level of a current user of the terminal device; judging whether a resource allocation strategy associated with the user identification exists in a local database; and if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource use level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database.
Optionally, receiving a resource allocation request from a terminal device includes: and after the terminal equipment is connected to the connection proxy service component, receiving the resource allocation request sent by the terminal equipment through the connection proxy service component.
Optionally, the user type and the resource usage level are obtained as follows: sending the resource allocation request to an authentication server through the connection proxy service component, and receiving a user type and a resource usage level of the current user returned by the authentication server, where the authentication server is configured to authenticate the current user to determine the user type and the resource usage level, and the user type includes: and the resource use level corresponds to the level of the resource allocation cost selected by the current user when the terminal equipment is accessed to the connection agent service component.
Optionally, allocating a target resource to the current user according to the user type and the resource usage level includes: determining the resource demand information of the current user according to the user type and the resource use level; reading the use state information of each target resource from the local database; matching the resource demand information with the use state information to obtain a matching result; and allocating the target resource to the current user based on the matching result, and updating the use state information of the target resource in the local database.
Optionally, the generating the resource allocation policy based on the target resource allocated to the current user includes: establishing a mapping relation between the current user and the target resource through a connection proxy service component; and generating the resource allocation policy based on the mapping relationship, wherein the resource allocation policy is used for indicating that the target resource is allocated to the current user having the mapping relationship with the target resource.
Optionally, the target resource includes at least one of: virtual machines, physical workstations, zero-end devices, desktop sessions, and application windows.
According to another aspect of the embodiments of the present invention, there is also provided a resource allocation system, including: an access gateway, connected to a terminal device, configured to receive a resource allocation request from the terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device; at least one connection proxy service component, connected to the access gateway, and configured to receive the resource allocation request forwarded by the access gateway, determine whether a resource allocation policy associated with the user identifier exists in a local database, and if the determination result indicates that the resource allocation policy does not exist, allocate a target resource to the current user according to the user type and the resource usage level, generate the resource allocation policy based on the target resource allocated to the current user, and store the resource allocation policy in the local database.
Optionally, the system further includes: an authentication server, connected to the connection broker service component, configured to receive the resource allocation request forwarded by the connection broker service component, authenticate the current user based on the resource allocation request, determine the user type and the resource usage level, and return the user type and the resource usage level to the connection broker service component, where the user type includes: and the resource use level corresponds to the level of the resource allocation cost selected by the current user when the terminal equipment is accessed to the connection agent service component.
Optionally, the connection broker service component is further configured to determine resource demand information of the current user according to the user type and the resource usage level, and read usage state information of each target resource from the local database; and matching the resource demand information and the use state information, allocating the target resource to the current user based on the matching result, and updating the use state information of the target resource in the local database.
Optionally, the connection broker service component is further configured to provide a global management function, where the global management function includes at least one of: user management, resource access management, connection management, configuration management, resource state management, a dashboard and a universal external API (application program interface); the connection broker service component is further configured to perform lifecycle management on the target resource in a resource pool of the local database, where the lifecycle management includes at least one of: creation, maintenance, recovery, and removal.
Optionally, the system further includes: the access gateway is further configured to provide an access port for accessing the resource pool of the local database to the terminal device when the current user is a public network user; the access gateway is further configured to maintain data connection and session connection between the terminal device and the connection broker service component, and provide a network optimization acceleration function and a network security function.
Optionally, the system further includes: when there are a plurality of connection broker service components, the plurality of connection broker service components share the local database, and each access gateway is connected to each connection broker service component, or each access gateway is connected to a plurality of connection broker service components; the access gateway is further configured to perform automatic load balancing on each connection broker service component according to a preset load balancing policy.
According to another aspect of the embodiments of the present invention, there is also provided a resource allocation apparatus, including: a receiving module, configured to receive a resource allocation request from a terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device; the judging module is used for judging whether a resource allocation strategy associated with the user identification exists in a local database; and the allocation module is used for allocating target resources to the current user according to the user type and the resource use level if the judgment result indicates that the resource allocation strategy does not exist, generating the resource allocation strategy based on the target resources allocated to the current user, and storing the resource allocation strategy in the local database.
According to another aspect of the embodiments of the present invention, there is also provided a non-volatile storage medium, which stores a plurality of instructions, the instructions being adapted to be loaded by a processor and to execute any one of the above resource allocation methods.
According to another aspect of the embodiments of the present invention, there is also provided a processor, configured to execute a program, where the program is configured to execute any one of the above resource allocation methods when running.
According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including a memory and a processor, where the memory stores a computer program, and the processor is configured to execute the computer program to perform any one of the above resource allocation methods.
In the embodiment of the present invention, a resource allocation request is received from a terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device; judging whether a resource allocation strategy associated with the user identification exists in a local database; if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource usage level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database, so that the purpose of effectively allocating cloud office resources is achieved, the technical effect of improving the allocation efficiency of the cloud office resources is achieved, and the technical problem that the efficiency of resource allocation is lack due to the fact that the cloud office resources cannot be effectively allocated in the prior art is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow chart of a resource allocation method according to the prior art;
FIG. 2 is a flow chart of a resource allocation method according to an embodiment of the present invention;
fig. 3 is an overall architecture diagram of an alternative vBroker component based cloud management system according to an embodiment of the present invention;
fig. 4 is a flow diagram of an exemplary session establishment in accordance with an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a resource allocation apparatus according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Cloud office is a resource integration and application mode based on cloud computing, mutual cooperation of mechanisms at all levels is realized by building a cloud platform, optimization and integration of resources of all parties are realized, and the rise of cloud economy is a necessary result under the condition of double-wheel drive of technical innovation and demand change.
The user group of cloud official working is huge working clan, and on the one hand office space itself possesses diversified characteristic, and intelligent transformation of official working under the technical drive is the basic theory of modern official working always, and on the other hand epidemic situation influences and impels a large amount of users to be gushed into in the cloud official working market in the short-term, and the degree of depth experience of cloud official working and core advantage bring the thorough change of user's consciousness and user custom more easily to make cloud official working subvert traditional official working become future official working normality.
Simultaneously, compare traditional PC official working mode, cloud official working has following advantage at least: 1. high safety: the zero terminal guarantees that data does not go out, the network does not transmit secret, and the terminal does not store the secret; 2. high availability: the cloud desktop cluster is highly available, and zero downtime of desktop office is guaranteed; 3. flexibility: the hardware resources are elastically stretched, and the waste of the hardware resources is reduced; 4. the cost of ownership is low: zero operation and maintenance, low energy consumption, low emission and low overall cost of ownership.
Example 1
In accordance with an embodiment of the present invention, there is provided an embodiment of a resource allocation method, it should be noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
Fig. 2 is a flowchart of a resource allocation method according to an embodiment of the present invention, as shown in fig. 2, the method includes the following steps:
step S102, receiving a resource allocation request from a terminal device, wherein the resource allocation request comprises a user identifier, a user type and a resource use level of a current user of the terminal device;
step S104, judging whether a resource allocation strategy associated with the user identification exists in a local database;
step S106, if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource usage level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database.
In the embodiment of the present invention, a resource allocation request is received from a terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device; judging whether a resource allocation strategy associated with the user identification exists in a local database; if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource usage level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database, so that the purpose of effectively allocating cloud office resources is achieved, the technical effect of improving the allocation efficiency of the cloud office resources is achieved, and the technical problem that the efficiency of resource allocation is lack due to the fact that the cloud office resources cannot be effectively allocated in the prior art is solved.
It should be noted that the resource allocation method provided in the embodiment of the present application may be applied to, but not limited to, a cloud office scene, for example, to a cloud management system, and is used to allocate a target resource, for example, a computing resource, to a terminal device accessing to the cloud office system.
In an alternative embodiment, the target resource includes at least one of: virtual machines, physical workstations, zero-end devices, desktop sessions, and application windows.
In an optional embodiment, receiving a resource allocation request from a terminal device includes: and after the terminal equipment is connected to the connection proxy service component, receiving the resource allocation request sent by the terminal equipment through the connection proxy service component.
The resource allocation policy is used to instruct the target resource to be allocated to the current user having a mapping relationship with the target resource.
Optionally, in the embodiment of the present application, the connection broker service component, that is, the vBroker component, integrates various system resource configurations and schedules by providing a unified vBroker component, and the vBroker provides various types of interfaces to outside, so as to interface with various types of terminal devices in an enterprise (including but not limited to ZC terminals, TC terminals, PC terminals, mobile terminals, Html5), and provide various types of target resources for users (including but not limited to physical entities and virtual entities or services such as virtual machines, physical PCs, physical workstations, Zero Server devices, desktop sessions, and application windows). Moreover, the vBroker component also provides various interfaces which can be connected with various types of management servers, so that various types of services are provided for users, the vBroker has very good expandability, and the new management server can also be conveniently accessed into the vBroker component and is uniformly scheduled and managed by the vBroker component.
The invention provides an overall architecture diagram of an optional cloud management system based on a vBroker component, as shown in FIG. 3, the vBroker component (such as vBroker1 and vBroker2 … … vBroker N shown in FIG. 3) is connected with an R-side device (such as R1, R2 and R3 … … RN shown in FIG. 3) through a gateway device getway or gateway group; meanwhile, the vBroker is connected with a data center server, each S-side device (such as S1, S2 and S3 … … SN shown in FIG. 3), a computing platform and various management servers (an authentication server, a license server, an upgrade server and a network resource platform).
In the embodiment of the application, a server end and a client end of a vGTP protocol are referred to as an S end and an R end for short, a host (system/device) where the S end is located is referred to as a resource server end, and a host (system/device) where the R end is located is referred to as a terminal.
As an alternative embodiment, the number of vBroker components may be one or more, and the number of Gateway getways may also be one or more, each Gateway being associated with one or more vbrokers when there are more than one vBroker and Gateway. It should be noted that, in the cloud management system, the vBroker component may be separately arranged, or may be directly integrated in the data center server.
The vBroker is used for providing a global management function, and specifically, the vBroker may provide a global management function including: a series of functions such as user management, resource access management, connection management, configuration management, resource state management, a Dashboard (Dashboard), a general external API and the like; meanwhile, the vBroker is also used for providing desktop connection and control functions for the terminal user, implementing various operation requests of the terminal user to the backend service, providing operation, maintenance and management for a front-end user (manager) of the resource platform, and providing a corresponding API (application programming interface) for a third-party service program, wherein the API is an information and control center for connecting the terminal user and the backend resource.
As another alternative embodiment, the vBroker component is also used for lifecycle management of resources in the resource pool, including creating, maintaining, recovering, and removing resources.
In an alternative embodiment, the user type and the resource usage level are obtained as follows:
and sending the resource allocation request to an authentication server through the connection proxy service component, and receiving the user type and the resource use level of the current user returned by the authentication server.
Wherein, the authentication server is used for authenticating the current user to determine the user type and the resource usage level, and the user type includes: and the resource use level corresponds to the level of the resource allocation cost selected by the current user when the terminal equipment is accessed to the connection agent service component.
It should be noted that, as shown in fig. 3, Gateway (access Gateway: GW) is the only portal for the end user to access the resource pool (e.g., virtual desktop service) from the Internet. The Gateway front end is connected with a terminal user on the Internet, the back end is connected with a vBroker and used for forwarding all data between the user terminal and the vBroker, maintaining the connection between the user terminal and the vBroker, maintaining the conversation between the user terminal and the vBroker, and providing corresponding network optimization acceleration functions (such as load balancing of service flow, QoS and the like) and network security functions (such as a firewall random open port).
As an optional embodiment, a plurality of vBroker components may be set in the cloud management system, and when there are a plurality of vBroker components in the system, all vBroker components share one database. Each Gateway can be associated/disassociated to a vbaker or vbaker group, which can be managed by the vbaker component. The vBroker component needs to report its working state and load condition to the Gateway, and then the Gateway can direct the terminal request to the appropriate vBroker component according to the actual load condition of the vBroker component, that is, the Gateway is responsible for the docking of the terminal user with the vBroker, and can dock the terminal user with the appropriate vBroker component according to the user type or demand and the current load condition of the vBroker component. Each Gateway can automatically perform load balancing on each vBroker according to a preset load balancing strategy. Gateway is a connection medium between public network users and vBroker, public network end users can only connect vBroker service through Gateway, and intranet (under the same VLAN) end users can directly connect vBroker service without passing Gateway.
As an alternative embodiment, when the vbaker component is provided separately, it may use its own database; when the vBroker component is integrated in the user's data center server, it can use the data center server's own database; the cooperative party can also comprise an authentication server, a license server, a cloud platform service, an upgrade server, resources and a computing platform.
When the resource allocation scheme provided by the application is actually implemented, the communication data between the vBroker component and the proxy server agent and the client are transmitted by SSL encryption; agent and S end interaction can adopt lightweight json serialized data.
In the embodiment of the present application, the computing platform is used to provide various computing services for users, including but not limited to physical entities and virtual entities or services such as virtual machines, physical PCs, physical workstations, Zero Server devices, desktop sessions, and application windows. The computing platform of the present invention is implemented by a mix of different operating system architectures including x86 and ARM.
In an optional embodiment, allocating a target resource to the current user according to the user type and the resource usage level includes:
step S202, determining the resource demand information of the current user according to the user type and the resource usage level;
step S204, reading the use state information of each target resource from the local database;
step S206, matching the resource requirement information and the use state information to obtain a matching result;
step S208, allocating the target resource to the current user based on the matching result, and updating the use status information of the target resource in the local database.
Optionally, in the embodiment of the present application, all target resources need to be automatically registered with the vbaker component, and meanwhile, the vbaker component continuously obtains the usage status of each target resource and records the real-time usage status information in the database. When the terminal device is connected to the vBroker component, the vBroker component allocates resources to the user according to the current user level and the usage requirement, reads the usage state of each resource from the database, for example, whether the resource is already used by other users, acquires the resource that is not occupied from the database, matches the resource requirement information based on the resource that is not occupied, that is, matches the resource requirement usage information of the current user with the resource information that can be currently used, and allocates appropriate resources to the current user according to the matching result, and performs allocation of user resources in the following manner: after determining the resources allocated to the user, the vBroker component maps the current user with the resources allocated to the current user, establishes an effective use relationship between the resources and the user, and after the resource mapping is completed, the vBroker component needs to update the resource use state in the database.
In an optional embodiment, the generating the resource allocation policy based on the target resource allocated to the current user includes:
step S302, establishing a mapping relation between the current user and the target resource through a connection proxy service component;
step S304, generating the resource allocation policy based on the mapping relationship.
The resource allocation policy is used to instruct the target resource to be allocated to the current user having a mapping relationship with the target resource.
In the embodiment of the present application, the vbbroker component further provides multiple mapping types, which can enable allocation of resource services to be more flexible and diverse, and the mapping types generally include 1-to-1 mapping, 1-to-N mapping, and M-to-N mapping. Therefore, the resource allocation policy may be generated based on the mapping relationship established by the connection broker service component between the current user and the target resource.
In a use phase of computing resources, for example, after configuring resource use policies of a user, the vBroker component may locally record a resource use policy corresponding to the current user and a mapping relationship between allocated resources, and then manage (establish/reconnect/destroy) a session between the R-side device and the S-side device according to the resource use policy and the resource mapping relationship corresponding to a user account, where a typical session establishment procedure is shown in FIG. 4.
As an alternative embodiment, the following schematically illustrates an embodiment of the present application by an alternative resource allocation method:
and S401, the terminal equipment is connected to the vBroker component and reports the user information to the vBroker component, and the vBroker component authenticates the current user through the authentication server and determines the user type and the resource allocation level.
Step S402, inquiring the resource strategy of the current user in a local database, if so, allocating resources for the user according to the existing resource strategy of the user, and if the resource strategy is not set for the user, turning to step S403;
specifically, an intranet user is directly connected with the vBroker component, and a public network user is connected with the vBroker component through Gateway; in practice, public network users first connect to the Gateway, and the Gateway interfaces the current user to the appropriate vBroker component according to the user type and the current connection and load condition of each vBroker component.
And S403, allocating resources for the current user according to different types and grades of the current user by the vBroker component, and generating a resource allocation strategy.
It should be noted that the resource allocation level of the user is related to the tariff selected by the user when accessing, different tariffs correspond to different resource allocation levels, and different resource allocation levels correspond to different resource usage rights.
Specifically, the user types include: administrator users and general users; and the authority is distributed according to the level of the ordinary user.
It should be noted that, in the embodiment of the present application, office resources allocated to users are mainly allocated to common users according to user classes thereof. Office resources that may be allocated to a user include, but are not limited to: physical entities and virtual entities or services such as virtual machines, physical PCs, physical workstations, Zero Server devices, desktop sessions and application windows.
As another optional embodiment, in the resource using process, in the scheme of the application, when the vbaker component receives a resource allocation request sent by the terminal device, resource allocation or adjustment is performed for the user according to the resource allocation request.
For example, when a current user sends a resource allocation request through terminal equipment and applies for resource increase, the vBroker component first determines whether the quantity of resources requested by the user exceeds the upper limit of resources available to the user, and if not, queries the use state of corresponding resources from a database, and allocates the idle resources available to the current user; for another example, in the using process, if the user applies for adjusting the resource type or quantity, the vbbroker component also first determines whether the resource type and quantity applied by the user are within the resource type and quantity range available to the user, if so, queries the use condition of the current corresponding type of resource in the database to determine whether there are idle resources available to be allocated to the current user, if not, notifies the user that the current resource is insufficient, and if so, allocates the corresponding type and quantity of resources to the user.
As an optional embodiment, a specific implementation manner of resource allocation in the embodiment of the present application is: firstly, the resources currently used by the users are released, and then the mapping relation between the current users and the newly allocated resources is established, so that the effective use relation between the current resources and the users is formed.
Example 2
According to an embodiment of the present invention, there is also provided a system embodiment for implementing the resource allocation method, where the resource allocation system includes: wherein:
an access gateway, connected to a terminal device, configured to receive a resource allocation request from the terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device;
at least one connection proxy service component, connected to the access gateway, and configured to receive the resource allocation request forwarded by the access gateway, determine whether a resource allocation policy associated with the user identifier exists in a local database, and if the determination result indicates that the resource allocation policy does not exist, allocate a target resource to the current user according to the user type and the resource usage level, generate the resource allocation policy based on the target resource allocated to the current user, and store the resource allocation policy in the local database.
In the embodiment of the present invention, the access gateway is connected to a terminal device, and is configured to receive a resource allocation request from the terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device; and the connection proxy service component is connected with the access gateway and used for receiving the resource allocation request forwarded by the access gateway, judging whether a resource allocation strategy associated with the user identifier exists in a local database or not, and if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource usage level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database, so that the aim of effectively allocating cloud office resources is fulfilled, the technical effect of improving the allocation efficiency of the cloud office resources is achieved, and the technical problem that the cloud office resources cannot be effectively allocated in the prior art and the resource allocation is lack of efficiency is solved.
It should be noted that the resource allocation system provided in the embodiment of the present application may be applied to, but not limited to, a cloud office scene, and may be substantially understood as a cloud management system, which is used for allocating target resources, such as computing resources, to terminal devices accessing to the cloud office system.
In an alternative embodiment, the target resource includes at least one of: virtual machines, physical workstations, zero-end devices, desktop sessions, and application windows.
In an optional embodiment, receiving a resource allocation request from a terminal device includes: and after the terminal equipment is connected to the connection proxy service component, receiving the resource allocation request sent by the terminal equipment through the connection proxy service component.
The resource allocation policy is used to instruct the target resource to be allocated to the current user having a mapping relationship with the target resource.
Optionally, in the embodiment of the present application, the connection broker service component, that is, the vBroker component, integrates various system resource configurations and schedules by providing a unified vBroker component, and the vBroker provides various types of interfaces to outside, so as to interface with various types of terminal devices in an enterprise (including but not limited to ZC terminals, TC terminals, PC terminals, mobile terminals, Html5), and provide various types of target resources for users (including but not limited to physical entities and virtual entities or services such as virtual machines, physical PCs, physical workstations, Zero Server devices, desktop sessions, and application windows). Moreover, the vBroker component also provides various interfaces which can be connected with various types of management servers, so that various types of services are provided for users, the vBroker has very good expandability, and the new management server can also be conveniently accessed into the vBroker to be uniformly scheduled and managed by the vBroker.
The overall architecture diagram of the cloud management system based on the vBroker component provided by the invention is shown in FIG. 3, wherein vBroker is connected with R-side equipment (such as R1, R2 and R3 … … Rn shown in FIG. 3) through a Geteway (access Gateway: GW) or a Gateway group; meanwhile, the vBroker is connected with a data center server, each S-side device (such as S1, S2 and S3 … … SN shown in FIG. 3), a computing platform and various management servers (an authentication server, a license server, an upgrade server, a cloud platform service and a network resource platform).
In the embodiment of the application, a server end and a client end of a vGTP protocol are referred to as an S end and an R end for short, a host (system/device) where the S end is located is referred to as a resource server end, and a host (system/device) where the R end is located is referred to as a terminal.
As an alternative embodiment, the vBroker may be one or more, and the Gateway may be one or more, and when there are more vbrokers and gateways, each Gateway is associated with one or more vbrokers. It should be noted that, in the cloud management system, the vBroker component may be separately arranged, or may be directly integrated in the data center server;
the vBroker is used for providing a global management function, and specifically, the vBroker may provide a global management function including: a series of functions such as user management, resource access management, connection management, configuration management, resource state management, a Dashboard (Dashboard), a general external API and the like; meanwhile, the vBroker is also used for providing desktop connection and control functions for the terminal user, implementing various operation requests of the terminal user to the backend service, providing operation, maintenance and management for a front-end user (manager) of the resource platform, and providing a corresponding API (application programming interface) for a third-party service program, wherein the API is an information and control center for connecting the terminal user and the backend resource.
As another alternative embodiment, the vBroker component is also used for lifecycle management of resources in the resource pool, including creating, maintaining, recovering, and removing resources.
It should be noted that, as also shown in fig. 3, Gateway is connected to the R-side device through WLAN, and Gateway is the only entrance for the end user to access the resource pool (e.g. virtual desktop service) from Internet. The Gateway front end is connected with a terminal user on the Internet, the back end is connected with the vBroker component and used for forwarding all data between the user terminal and the vBroker component, maintaining connection between the user terminal and the vBroker component, maintaining conversation between the terminal and the vBroker, and providing corresponding network optimization acceleration functions (such as load balancing of service flow, QoS and the like) and network security functions (such as a firewall random open port).
In an optional embodiment, the system further includes: an authentication server, connected to the connection broker service component, configured to receive the resource allocation request forwarded by the connection broker service component, authenticate the current user based on the resource allocation request, determine the user type and the resource usage level, and return the user type and the resource usage level to the connection broker service component, where the user type includes: and the resource use level corresponds to the level of the resource allocation cost selected by the current user when the terminal equipment is accessed to the connection agent service component.
In an optional embodiment, the connection broker service component is further configured to determine resource demand information of the current user according to the user type and the resource usage level, and read usage state information of each target resource from the local database; and matching the resource demand information and the use state information, allocating the target resource to the current user based on the matching result, and updating the use state information of the target resource in the local database.
In an optional embodiment, the connection broker service component is further configured to provide a global management function, where the global management function includes at least one of: user management, resource access management, connection management, configuration management, resource state management, a dashboard and a universal external API (application program interface); the connection broker service component is further configured to perform lifecycle management on the target resource in a resource pool of the local database, where the lifecycle management includes at least one of: creation, maintenance, recovery, and removal.
In an optional embodiment, the system further includes: the access gateway is further configured to provide an access port for accessing the resource pool of the local database to the terminal device when the current user is a public network user; the access gateway is further configured to maintain data connection and session connection between the terminal device and the connection broker service component, and provide a network optimization acceleration function and a network security function.
In an optional embodiment, the system further includes: when there are a plurality of connection broker service components, the plurality of connection broker service components share the local database, and each access gateway is connected to each connection broker service component, or each access gateway is connected to a plurality of connection broker service components; the access gateway is further configured to perform automatic load balancing on each connection broker service component according to a preset load balancing policy.
As an optional embodiment, a plurality of vBroker components may be set in the cloud management system, and when there are a plurality of vBroker components in the system, all vBroker components share one database. Each Gateway can be associated/disassociated to a vbaker or vbaker group, which can be managed by the vbaker component. The vBroker component needs to report its working state and load condition to the Gateway, and then the Gateway can direct the terminal request to the appropriate vBroker component according to the actual load condition of the vBroker component, that is, the Gateway is responsible for the docking of the terminal user with the vBroker, and can dock the terminal user with the appropriate vBroker component according to the user type or demand and the current load condition of the vBroker component. Each Gateway can automatically perform load balancing on each vBroker according to a preset load balancing strategy. Gateway is a connection medium between public network users and vBroker, public network end users can only connect vBroker service through Gateway, and intranet (under the same VLAN) end users can directly connect vBroker service without passing Gateway.
As an alternative embodiment, when the vbaker component is provided separately, it may use its own database; when the vBroker component is integrated in the user's data center server, it can use the data center server's own database; the cooperative party can also comprise an authentication server, a license server, a cloud platform service, an upgrade server, resources and a computing platform.
When the resource allocation scheme provided by the application is actually implemented, the communication data between the vBroker component and the Agent of the proxy server and the Client are transmitted by SSL encryption; agent and S end interaction can adopt lightweight json serialized data.
In the embodiment of the present application, the computing platform is used to provide various computing services for users, including but not limited to physical entities and virtual entities or services such as virtual machines, physical PCs, physical workstations, Zero Server devices, desktop sessions, and application windows. The computing platform of the present invention is implemented by a mix of different operating system architectures including x86 and ARM.
It should be noted that any optional or preferred resource allocation method in embodiment 1 above may be implemented or realized in the resource allocation system provided in this embodiment.
In addition, it should be noted that, for alternative or preferred embodiments of the present embodiment, reference may be made to the relevant description in embodiment 1, and details are not described herein again.
Example 3
According to an embodiment of the present invention, an embodiment of an apparatus for implementing the resource allocation method is further provided, and fig. 5 is a schematic structural diagram of a resource allocation apparatus according to an embodiment of the present invention, as shown in fig. 5, the resource allocation apparatus includes: a receiving module 400, a determining module 402, and an assigning module 404, wherein:
a receiving module 400, configured to receive a resource allocation request from a terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device; a determining module 402, configured to determine whether a resource allocation policy associated with the user identifier exists in a local database; an allocating module 404, configured to allocate, if the determination result indicates that the resource allocation policy does not exist, a target resource for the current user according to the user type and the resource usage level, generate the resource allocation policy based on the target resource allocated to the current user, and store the resource allocation policy in the local database.
It should be noted that the above modules may be implemented by software or hardware, for example, for the latter, the following may be implemented: the modules can be located in the same processor; alternatively, the modules may be located in different processors in any combination.
It should be noted here that the receiving module 400, the determining module 402 and the allocating module 404 correspond to steps S102 to S106 in embodiment 1, and the modules are the same as the corresponding steps in the implementation example and application scenarios, but are not limited to the disclosure in embodiment 1. It should be noted that the modules described above may be implemented in a computer terminal as part of an apparatus.
It should be noted that, reference may be made to the relevant description in embodiment 1 for alternative or preferred embodiments of this embodiment, and details are not described here again.
The resource allocation apparatus may further include a processor and a memory, where the receiving module 400, the determining module 402, the allocating module 404, and the like are stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions.
The processor comprises a kernel, and the kernel calls a corresponding program unit from the memory, wherein one or more than one kernel can be arranged. The memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
According to an embodiment of the present application, there is also provided an embodiment of a non-volatile storage medium. Optionally, in this embodiment, the nonvolatile storage medium includes a stored program, and the apparatus in which the nonvolatile storage medium is located is controlled to execute any one of the resource allocation methods when the program runs.
Optionally, in this embodiment, the nonvolatile storage medium may be located in any one of a group of computer terminals in a computer network, or in any one of a group of mobile terminals, and the nonvolatile storage medium includes a stored program.
Optionally, the apparatus in which the non-volatile storage medium is controlled to perform the following functions when the program is executed: receiving a resource allocation request from a terminal device, wherein the resource allocation request comprises a user identifier, a user type and a resource use level of a current user of the terminal device; judging whether a resource allocation strategy associated with the user identification exists in a local database; and if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource use level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database.
Optionally, the apparatus in which the non-volatile storage medium is controlled to perform the following functions when the program is executed: and after the terminal equipment is connected to the connection proxy service component, receiving the resource allocation request sent by the terminal equipment through the connection proxy service component.
Optionally, the apparatus in which the non-volatile storage medium is controlled to perform the following functions when the program is executed: sending the resource allocation request to an authentication server through the connection proxy service component, and receiving a user type and a resource usage level of the current user returned by the authentication server, where the authentication server is configured to authenticate the current user to determine the user type and the resource usage level, and the user type includes: and the resource use level corresponds to the level of the resource allocation cost selected by the current user when the terminal equipment is accessed to the connection agent service component.
Optionally, the apparatus in which the non-volatile storage medium is controlled to perform the following functions when the program is executed: determining the resource demand information of the current user according to the user type and the resource use level; reading the use state information of each target resource from the local database; matching the resource demand information with the use state information to obtain a matching result; and allocating the target resource to the current user based on the matching result, and updating the use state information of the target resource in the local database.
Optionally, the apparatus in which the non-volatile storage medium is controlled to perform the following functions when the program is executed: establishing a mapping relation between the current user and the target resource through a connection proxy service component; and generating the resource allocation policy based on the mapping relationship, wherein the resource allocation policy is used for indicating that the target resource is allocated to the current user having the mapping relationship with the target resource.
According to an embodiment of the present application, there is also provided an embodiment of a processor. Optionally, in this embodiment, the processor is configured to execute a program, where the program executes any one of the resource allocation methods.
According to an embodiment of the present application, there is also provided an embodiment of an electronic device, including a memory and a processor, where the memory stores a computer program, and the processor is configured to execute the computer program to perform any one of the resource allocation methods.
There is further provided, in accordance with an embodiment of the present application, an embodiment of a computer program product, which, when executed on a data processing device, is adapted to execute a program that initializes the steps of the resource allocation method of any of the above.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable non-volatile storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a non-volatile storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned nonvolatile storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (16)
1. A method for resource allocation, comprising:
receiving a resource allocation request from a terminal device, wherein the resource allocation request comprises a user identifier, a user type and a resource use level of a current user of the terminal device;
judging whether a resource allocation strategy associated with the user identification exists in a local database;
if the judgment result indicates that the resource allocation strategy does not exist, allocating target resources for the current user according to the user type and the resource use level, generating the resource allocation strategy based on the target resources allocated for the current user, and storing the resource allocation strategy in the local database.
2. The method of claim 1, wherein receiving a resource allocation request from a terminal device comprises:
and after the terminal equipment is connected to a connection proxy service component, receiving the resource allocation request sent by the terminal equipment through the connection proxy service component.
3. The method of claim 2, wherein the user type and the resource usage level are obtained by:
and sending the resource allocation request to an authentication server through the connection proxy service component, and receiving the user type and the resource use level of the current user returned by the authentication server, wherein the authentication server is used for authenticating the current user so as to determine the user type and the resource use level.
4. The method of claim 1, wherein allocating target resources for the current user according to the user type and the resource usage level comprises:
determining the resource demand information of the current user according to the user type and the resource use level;
reading the use state information of each target resource from the local database;
matching the resource demand information and the use state information to obtain a matching result;
and distributing the target resource for the current user based on the matching result, and updating the use state information of the target resource in the local database.
5. The method of claim 1, wherein generating the resource allocation policy based on the target resource allocated for the current user comprises:
establishing a mapping relation between the current user and the target resource through a connection proxy service component;
generating the resource allocation policy based on the mapping relationship, wherein the resource allocation policy is used for indicating that the target resource is allocated to the current user having the mapping relationship with the target resource.
6. The method of any one of claims 1 to 5, wherein the target resource comprises at least one of: virtual machines, physical workstations, zero-end devices, desktop sessions, and application windows.
7. A resource allocation system, comprising:
the access gateway is connected with the terminal equipment and is used for receiving a resource allocation request from the terminal equipment, wherein the resource allocation request comprises a user identifier, a user type and a resource use level of a current user of the terminal equipment;
at least one connection agent service component, connected to the access gateway, and configured to receive the resource allocation request forwarded by the access gateway, determine whether a resource allocation policy associated with the user identifier exists in a local database, and if the determination result indicates that the resource allocation policy does not exist, allocate a target resource to the current user according to the user type and the resource usage level, generate the resource allocation policy based on the target resource allocated to the current user, and store the resource allocation policy in the local database.
8. The system of claim 7, further comprising:
an authentication server, connected to the connection broker service component, configured to receive the resource allocation request forwarded by the connection broker service component, authenticate the current user based on the resource allocation request, determine the user type and the resource usage level, and return the user type and the resource usage level to the connection broker service component, where the user type includes: and the resource use level corresponds to the level of the resource allocation cost selected by the current user when the terminal equipment is accessed to the connection agent service component.
9. The system of claim 7,
the connection agent service component is also used for determining the resource demand information of the current user according to the user type and the resource use level and reading the use state information of each target resource from the local database; and matching the resource demand information and the use state information, allocating the target resource to the current user based on the matching result, and updating the use state information of the target resource in the local database.
10. The system of claim 7,
the connection broker service component is further configured to provide global management functions, wherein the global management functions include at least one of: user management, resource access management, connection management, configuration management, resource state management, a dashboard and a universal external API (application program interface);
the connection broker service component is further configured to perform lifecycle management on the target resource in a resource pool of the local database, wherein the lifecycle management includes at least one of: creation, maintenance, recovery, and removal.
11. The system of claim 7, further comprising:
the access gateway is further configured to provide the terminal device with an access port for accessing a resource pool of the local database when the current user is a public network user;
the access gateway is further configured to maintain data connection and session connection between the terminal device and the connection broker service component, and provide a network optimization acceleration function and a network security function.
12. The system of claim 7, further comprising:
when the connection agent service components are multiple, the multiple connection agent service components share the local database, and each access gateway is respectively connected with each connection agent service component, or each access gateway is connected with the multiple connection agent service components;
and the access gateway is also used for automatically balancing the load of each connection agent service component according to a preset load balancing strategy.
13. A resource allocation apparatus, comprising:
a receiving module, configured to receive a resource allocation request from a terminal device, where the resource allocation request includes a user identifier, a user type, and a resource usage level of a current user of the terminal device;
the judging module is used for judging whether a resource allocation strategy associated with the user identification exists in a local database;
and the allocation module is used for allocating target resources to the current user according to the user type and the resource use level if the judgment result indicates that the resource allocation strategy does not exist, generating the resource allocation strategy based on the target resources allocated to the current user, and storing the resource allocation strategy in the local database.
14. A non-volatile storage medium, characterized in that it stores a plurality of instructions adapted to be loaded by a processor and to perform the resource allocation method according to any one of claims 1 to 6.
15. A processor for running a program, wherein the program is arranged to perform the resource allocation method of any one of claims 1 to 6 when running.
16. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and the processor is configured to execute the computer program to perform the resource allocation method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011548295.8A CN112737827A (en) | 2020-12-23 | 2020-12-23 | Resource allocation method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011548295.8A CN112737827A (en) | 2020-12-23 | 2020-12-23 | Resource allocation method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112737827A true CN112737827A (en) | 2021-04-30 |
Family
ID=75605202
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011548295.8A Pending CN112737827A (en) | 2020-12-23 | 2020-12-23 | Resource allocation method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112737827A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225714A (en) * | 2022-06-06 | 2022-10-21 | 阿里巴巴（中国）有限公司 | Resource processing method and system for cloud service |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080032729A1 (en) * | 2005-04-07 | 2008-02-07 | Huawei Technologies Co., Ltd. | Method for managing communication resource assignment and resource assignment policy system |
| CN102291452A (en) * | 2011-08-09 | 2011-12-21 | 北京星网锐捷网络技术有限公司 | Virtual machine management method, cloud management server and cloud system based on cloud strategy |
| CN104679595A (en) * | 2015-03-26 | 2015-06-03 | 南京大学 | Application-oriented dynamic resource allocation method for IaaS (Infrastructure As A Service) layer |
| WO2016022925A2 (en) * | 2014-08-08 | 2016-02-11 | Oracle International Corporation | Policy based resource management and allocation system |
| CN109213597A (en) * | 2018-08-01 | 2019-01-15 | 平安科技（深圳）有限公司 | Resource allocation methods, device, computer equipment and computer readable storage medium |
| CN110769015A (en) * | 2018-07-27 | 2020-02-07 | 深圳市立信创源科技有限公司 | Method for allocating fixed point resources |
-
2020
- 2020-12-23 CN CN202011548295.8A patent/CN112737827A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080032729A1 (en) * | 2005-04-07 | 2008-02-07 | Huawei Technologies Co., Ltd. | Method for managing communication resource assignment and resource assignment policy system |
| CN102291452A (en) * | 2011-08-09 | 2011-12-21 | 北京星网锐捷网络技术有限公司 | Virtual machine management method, cloud management server and cloud system based on cloud strategy |
| WO2016022925A2 (en) * | 2014-08-08 | 2016-02-11 | Oracle International Corporation | Policy based resource management and allocation system |
| CN104679595A (en) * | 2015-03-26 | 2015-06-03 | 南京大学 | Application-oriented dynamic resource allocation method for IaaS (Infrastructure As A Service) layer |
| CN110769015A (en) * | 2018-07-27 | 2020-02-07 | 深圳市立信创源科技有限公司 | Method for allocating fixed point resources |
| CN109213597A (en) * | 2018-08-01 | 2019-01-15 | 平安科技（深圳）有限公司 | Resource allocation methods, device, computer equipment and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225714A (en) * | 2022-06-06 | 2022-10-21 | 阿里巴巴（中国）有限公司 | Resource processing method and system for cloud service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220222593A1 (en) | Portable network interfaces for authentication and license enforcement | |
| CN110730153B (en) | Account configuration method, device and system of cloud equipment and data processing method | |
| JP7058654B2 (en) | Resource sharing methods, equipment and systems | |
| CN106462467B (en) | Integrated API and UI for consuming services over different distributed networks | |
| AU2004288532B2 (en) | Method and system for accessing and managing virtual machines | |
| CN109067877B (en) | Control method for cloud computing platform deployment, server and storage medium | |
| KR102328193B1 (en) | Apparatus and method for virtual desktop service | |
| CN111934918A (en) | Network isolation method and device for container instances in same container cluster | |
| US20120131193A1 (en) | Systems and methods for identifying service dependencies in a cloud deployment | |
| CN105378659A (en) | Method and system for enabling access of client device to remote desktop | |
| US20130086234A1 (en) | Cloud management system and method | |
| CN109246201B (en) | Cloud resource delivery method, processor and storage medium | |
| KR20010088528A (en) | A portable storage device and Method for using a remote storage device in the network as auxiliary memory of the local computer system by using the same device | |
| US7657945B2 (en) | Systems and arrangements to adjust resource accessibility based upon usage modes | |
| KR101674619B1 (en) | Virtualized services providing system for providing supervisory control function of client terminal | |
| CN106375442A (en) | Cross-platform device information management method and apparatus | |
| CN108462752B (en) | Method and system for accessing shared network, VPC management equipment and readable storage medium | |
| US11689636B2 (en) | Delegating network data exchange | |
| CN114296953A (en) | Multi-cloud heterogeneous system and task processing method | |
| CN112737827A (en) | Resource allocation method, device and system | |
| US20130007841A1 (en) | Client server communication system | |
| CN110753093B (en) | Method and device for managing equipment in cloud computing system | |
| US20130086140A1 (en) | Cloud management system and method | |
| CN109040066B (en) | Method and device for docking cloud security management platform with cloud security product | |
| KR20060087758A (en) | Internet disk system for moblie devices and method thereof |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210430 |
|
| RJ01 | Rejection of invention patent application after publication |