CN115514818B - Resource configuration method and resource scheduling method for edge cloud - Google Patents
Resource configuration method and resource scheduling method for edge cloud Download PDFInfo
- Publication number
- CN115514818B CN115514818B CN202211160189.1A CN202211160189A CN115514818B CN 115514818 B CN115514818 B CN 115514818B CN 202211160189 A CN202211160189 A CN 202211160189A CN 115514818 B CN115514818 B CN 115514818B
- Authority
- CN
- China
- Prior art keywords
- resource
- scheduling
- edge cloud
- domain
- resource pool
- 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.)
- Active
Links
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/0893—Assignment of logical groups to network elements
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供了一种用于边缘云的资源配置方法和资源调度方法，涉及云计算技术领域，资源配置方法包括：获取多个调度域分别对应的服务属性信息、多个边缘云节点资源分别对应的资源属性信息、以及多个调度域和多个边缘云节点资源的匹配规则；调度域包括至少一个服务；根据多个服务属性信息、多个资源属性信息、以及多个匹配规则，配置多个调度域分别对应的至少一个边缘云节点资源；根据调度域对应的至少一个边缘云节点资源，配置调度域对应的资源池。依据本实施例，可以提高资源配置效率，节省开发资源调度策略的成本。
The present application provides a resource configuration method and resource scheduling method for edge cloud, which relates to the field of cloud computing technology. The resource configuration method includes: obtaining service attribute information corresponding to multiple scheduling domains, resource attribute information corresponding to multiple edge cloud node resources, and matching rules of multiple scheduling domains and multiple edge cloud node resources; the scheduling domain includes at least one service; according to multiple service attribute information, multiple resource attribute information, and multiple matching rules, at least one edge cloud node resource corresponding to multiple scheduling domains is configured; according to at least one edge cloud node resource corresponding to the scheduling domain, a resource pool corresponding to the scheduling domain is configured. According to this embodiment, the resource configuration efficiency can be improved and the cost of developing resource scheduling strategies can be saved.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a resource allocation method and a resource scheduling method for an edge cloud.
Background
With the continued development of internet technology, more and more service providers are using content delivery networks (Content Delivery Network, CDNs) to accelerate their services. The CDN server may allocate resources for the service provider according to its needs. The resources may include, among other things, computing resources, storage resources, and network resources (e.g., bandwidth resources). Resource planning is important in CDN scheduling systems to solve the problem of which resources are covered by a service.
The service has various use demands on the resources, and the operation and maintenance team is required to manually configure the resources according to the demands of each service, so that the resource configuration efficiency is low. And the resource scheduling strategy needs to be developed, and the development cost of the resource scheduling strategy is high.
Disclosure of Invention
The embodiment of the application provides a resource allocation method and a resource scheduling method for edge cloud, which are used for improving the resource allocation efficiency and saving the cost of developing a resource scheduling strategy.
In a first aspect, an embodiment of the present application provides a resource allocation method for an edge cloud, including:
Acquiring service attribute information corresponding to a plurality of scheduling domains respectively, resource attribute information corresponding to a plurality of edge cloud node resources respectively, and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources;
According to the service attribute information, the resource attribute information and the matching rules, configuring at least one edge cloud node resource corresponding to the scheduling domains respectively;
And configuring a resource pool corresponding to the scheduling domain according to at least one edge cloud node resource corresponding to the scheduling domain, wherein the resource pool is used for scheduling resources for the scheduling domain.
In a second aspect, an embodiment of the present application provides a resource scheduling method for an edge cloud, including:
responding to the resource scheduling request, and determining a scheduling domain corresponding to the resource scheduling request;
scheduling edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain;
wherein the resource pool is configured for the scheduling domain according to the method of any embodiment of the application.
In a third aspect, an embodiment of the present application provides a resource allocation apparatus for an edge cloud, including:
the information acquisition module is used for acquiring service attribute information corresponding to a plurality of scheduling domains respectively, resource attribute information corresponding to a plurality of edge cloud node resources respectively and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources;
The first configuration module is used for configuring at least one edge cloud node resource corresponding to each of the plurality of scheduling domains according to the plurality of service attribute information, the plurality of resource attribute information and the plurality of matching rules;
The second configuration module is used for configuring a resource pool corresponding to the scheduling domain according to at least one edge cloud node resource corresponding to the scheduling domain, and the resource pool is used for scheduling resources for the scheduling domain.
In a fourth aspect, an embodiment of the present application provides a resource scheduling apparatus for an edge cloud, including:
the request response module is used for responding to the resource scheduling request and determining a scheduling domain corresponding to the resource scheduling request;
the resource scheduling module is used for scheduling the edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain;
wherein the resource pool is configured for the scheduling domain according to the method of any embodiment of the application.
In a fifth aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory, the processor implementing any one of the methods described above when the computer program is executed.
Compared with the prior art, the application has the following advantages:
The application provides a resource allocation method and a resource scheduling method for an edge cloud, which are used for acquiring service attribute information corresponding to a plurality of scheduling domains respectively, resource attribute information corresponding to a plurality of edge cloud node resources respectively and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources, wherein the scheduling domains comprise at least one service, at least one edge cloud node resource corresponding to the plurality of scheduling domains is configured according to the plurality of service attribute information, the plurality of resource attribute information and the plurality of matching rules, and a resource pool corresponding to the scheduling domains is configured according to at least one edge cloud node resource corresponding to the scheduling domains. In the embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted into the matching rule, the resource pool corresponding to the scheduling domain is configured according to the service attribute information, the resource attribute information and the matching rule, the workload of manually configuring the resources is reduced, the resource configuration efficiency is improved, when the resource is scheduled, the scheduling is directly performed in the resource pool corresponding to the configured scheduling domain, a new scheduling strategy is not required to be developed aiming at the scheduling domain, and the development cost is saved.
The foregoing description is only an overview of the present application, and is intended to provide a better understanding of the technical means of the present application, as it is embodied in the present specification, and is intended to provide a better understanding of the above and other objects, features and advantages of the present application, as it is embodied in the following description.
Drawings
In the drawings, the same reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily drawn to scale. It is appreciated that these drawings depict only some embodiments according to the application and are not therefore to be considered limiting of its scope.
Fig. 1 is a schematic diagram of an application scenario of a resource allocation method for an edge cloud provided by the present application;
Fig. 2 is a schematic diagram of a resource pool corresponding to a configuration scheduling domain according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a resource scheduling method according to an embodiment of the present application;
FIG. 4 is a flowchart of a method for configuring resources for an edge cloud according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a demand expression according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a matching rule according to an embodiment of the present application;
FIG. 7 is a schematic diagram illustrating a design idea of a resource allocation method according to an embodiment of the present application;
FIG. 8 is a schematic diagram illustrating a design idea of a resource allocation method according to an embodiment of the present application;
FIG. 9 is a flow chart of a method for resource scheduling for edge clouds according to an embodiment of the present application;
FIG. 10 is a block diagram of a resource allocation apparatus for an edge cloud according to an embodiment of the present application;
FIG. 11 is a block diagram of a resource scheduler for edge clouds according to one embodiment of the application, and
Fig. 12 is a block diagram of an electronic device used to implement an embodiment of the application.
Detailed Description
Hereinafter, only certain exemplary embodiments are briefly described. As will be recognized by those skilled in the pertinent art, the described embodiments may be modified in numerous different ways without departing from the spirit or scope of the present application. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes related technologies of the embodiments of the present application. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application.
Fig. 1 is a schematic diagram of an application scenario of a resource allocation method for edge cloud provided by the present application. As shown in fig. 1, the resource allocation center is configured to allocate a resource pool and schedule resources for a scheduling domain, and the resource allocation center may implement a resource allocation function through a component, where the component may be deployed in a computing device, and the computing device may include a server, a user device, and so on. The resource pool includes edge cloud node resources, such as node 1, node 2. Where a dispatch domain refers to a collection of objects that use edge cloud node resources, for example, the objects that use edge cloud node resources may include services of enterprise users, one of which may correspond to one domain name. The edge cloud is a cloud computing platform relatively close to the terminal, or is different from a central cloud or a traditional cloud computing platform, which can include a data center with large-scale resources and concentrated positions, and the network range covered by the edge cloud node is wider, so that the edge cloud node has the characteristic of being closer to the terminal. The edge cloud includes a plurality of edge cloud nodes, and each edge cloud node includes a series of edge infrastructures including, but not limited to, a distributed data center, a wireless machine room or cluster, an edge device such as a communication network, a core network device, a base station, an edge gateway, a home gateway, a computing device or a storage device of an operator, and a corresponding network environment. Here, the location, capability, and inclusion infrastructure of different edge cloud nodes may be the same or different. The edge cloud node resource refers to an edge cloud node as a resource, and specifically may include at least one of a computing resource, a storage resource, and a network resource (e.g., a bandwidth resource). The resource allocation center receives service attribute information respectively corresponding to a plurality of scheduling domains, resource attribute information respectively corresponding to a plurality of edge cloud node resources and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources, which are sent by terminal equipment of operation and maintenance personnel. The matching rules include at least one demand expression that characterizes the service's usage demand for resources. The resource allocation center configures at least one edge cloud node resource corresponding to each of the plurality of scheduling domains according to the plurality of service attribute information, the plurality of resource attribute information and the plurality of matching rules, and configures a resource pool corresponding to the scheduling domain according to the at least one edge cloud node resource corresponding to the scheduling domain.
Fig. 2 is a schematic diagram of a resource pool corresponding to a configuration scheduling domain according to an embodiment of the present application. As shown in fig. 2, the resource pool of the scheduling domain a comprises a node 1, a node 2, a node 3 and a node 4, the resource pool of the scheduling domain B comprises a node 2, a node 5, a node 6 and a node 7, the resource pool of the scheduling domain C comprises a node 7 and a node 8, wherein the nodes can be multiplexed between different scheduling domains, as shown in fig. 2, the resource pool of the scheduling domain a and the resource pool of the scheduling domain B are multiplexed with the node 2, and the resource pool of the scheduling domain B and the resource pool of the scheduling domain C are multiplexed with the node 7.
Fig. 3 is a schematic diagram of a resource scheduling method according to an embodiment of the present application. As shown in fig. 3, the scheduling domain C includes a domain name x, a domain name y, and a domain name z, after the resource allocation center receives the user content request, the resource allocation center analyzes the user content request, determines that the user content request corresponds to the scheduling domain C according to the analysis result, performs resource scheduling in a node 7 and a node 8 of a resource pool corresponding to the scheduling domain C, and the node 7 and the node 8 respectively provide resources for a source station of the domain name x, a source station of the domain name y, and a source station of the domain name z.
The embodiment of the application provides a resource allocation method for edge cloud, which can be applied to computing equipment, wherein the computing equipment can comprise a server, a user terminal and the like. Fig. 4 is a flowchart of a resource allocation method for an edge cloud according to an embodiment of the present application, which may include:
Step S401, service attribute information corresponding to a plurality of scheduling domains respectively, resource attribute information corresponding to a plurality of edge cloud node resources respectively, and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources are obtained, wherein the scheduling domains comprise at least one service.
Step S402, at least one edge cloud node resource corresponding to each of the plurality of scheduling domains is configured according to the plurality of service attribute information, the plurality of resource attribute information and the plurality of matching rules.
Step S403, a resource pool corresponding to the scheduling domain is configured according to at least one edge cloud node resource corresponding to the scheduling domain, and the resource pool is used for scheduling resources for the scheduling domain.
In this embodiment, a server is described as an execution subject. Optionally, the server receives service attribute information, resource attribute information and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources, wherein the service attribute information and the resource attribute information respectively correspond to the plurality of scheduling domains, the resource attribute information respectively correspond to the plurality of edge cloud node resources, and the matching rules are sent by the terminal equipment of the operation and maintenance personnel. Optionally, the server acquires service attribute information corresponding to each of the plurality of scheduling domains, resource attribute information corresponding to each of the plurality of edge cloud node resources, and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources from a preset database.
Where a dispatch domain refers to a collection of objects that use edge cloud node resources, for example, the objects that use edge cloud node resources may include services of enterprise users, one of which may correspond to one domain name.
The edge cloud node resources may include at least one of computing resources, storage resources, and network resources (e.g., bandwidth resources, etc.). The computing resources may include, among other things, central processing unit (Central Processing Unit, CPU) resources required by the computer program when running. The storage resources may include storage space capacity resources. The bandwidth resources may include an amount of data that can be transmitted at a fixed time.
Any scheduling domain may correspond to a plurality of service attribute information, and the service attribute information may be attribute information characterizing a service included in the scheduling domain. The resource attribute information may be attribute information characterizing an edge cloud node resource.
For example, the service attribute information or the resource attribute information may be in the form of a tag record composed of a "tag key value" (key) and a "tag value" (value), i.e., in the form of { key: value }. Wherein the tag key value represents the attribute type and the tag value represents the value of the attribute. The tag key value may include at least one of a tag source, an object to which the tag belongs, and a tag class.
The requirements of different scheduling domains for the edge cloud node resources are various, for example, some scheduling domains need to schedule the edge cloud node resources for live services, some scheduling domains need to use traffic-free edge cloud node resources, etc. In order for the requirements of the scheduling domain to be fulfilled by the configuration, these requirements need to be abstracted to matching rules. The matching rule is used for connecting the scheduling domain and the edge cloud node resources to express the use requirement of the scheduling domain on the edge cloud node resources.
Illustratively, the matching rule includes a requirement expression corresponding to the service attribute information and a requirement expression corresponding to the resource attribute information, and the matching rule is used for representing the use requirement of the scheduling domain on the edge cloud node resource.
Wherein a requirement expression (selector) is used to describe the requirement for the attribute value, for example, the requirement expression may be in the form of "tag key value+operator+tag value", and or logic is supported among the multiple requirement expressions, a bracket operator is supported, and the bracket operator indicates priority. A combination of a plurality of demand expressions may be regarded as one demand expression. The operators supported by the demand expression may include, but are not limited to, the following 10 types |, =, |=, in, non, > =, < =, |, ().
FIG. 5 is a schematic diagram of the demand expression provided in the embodiment of the present application, as shown in FIG. 5, the 3 demand expressions, selector1, selector2 and selector3, are combined into one expression, selector_1_2_3 by AND logic OR and bracket operators. Wherein selector1 indicates that node names of edge cloud node resources belong to a range of sets (cn 1, cn 2), selector2 indicates that security capability of the node is greater than 1G, and selector3 indicates that physical capability of the node is greater than 1G. The bracket operator indicates priority, and selector2 and selector3 are combined preferentially, so that "selector_2_3 with node security capability greater than 1G and node physical capability greater than 1G" is formed, and then selector1 and selector_2_3 together form the final selector_1_2_3, and the final meaning indicates that "the security capability and physical capability of the node are both greater than 1G, and the node is one of cn1 and cn 2".
In an example, fig. 6 is a schematic diagram of a matching rule provided by an embodiment of the present application, where, as shown in fig. 6, the matching rule includes a requirement expression corresponding to service attribute information and a requirement expression corresponding to resource attribute information. The requirement expression corresponding to the service attribute information is shown as a matching service selector1 in fig. 6, and the requirement expression corresponding to the resource attribute information is shown as a matching resource selector2 in fig. 6. The service entity schedm represents a scheduling domain, the selector1 is used for matching a label key value and a label value of the scheduling domain, the resource entity cell represents an edge cloud node resource, and the selector2 is used for matching a label key value and a label value of the edge cloud node resource.
In another example, the matching rule may consist of three parts, a demand expression of the matching scheduling field + an effective region + a demand expression of the matching resource. The method comprises the steps of matching a demand expression of a scheduling domain, namely a demand expression corresponding to service attribute information, for matching a scheduling domain of a certain type or a certain types, wherein an effective area represents an area range of an edge cloud node resource in which the matching rule is effective, resources out of the range are not constrained by the matching rule, and the demand expression of the matching resource, namely the demand expression corresponding to the edge cloud node resource, is used for matching the resource of the certain type or the certain types.
According to the multiple matching rules, the multiple service attribute information and the multiple resource attribute information can be matched, and resources which are not matched in the scheduling domain are filtered, so that the edge cloud node resources corresponding to the scheduling domain are obtained. According to at least one edge cloud node resource corresponding to a scheduling domain, a resource pool corresponding to the scheduling domain is configured, and for any scheduling domain, for example, a plurality of edge cloud node resources corresponding to the scheduling domain can be used as resources in the resource pool, and redundant resources can be configured outside a plurality of edge cloud node resources corresponding to the scheduling domain, so that the resource pool corresponding to the scheduling domain is formed by utilizing the plurality of edge cloud node resources corresponding to the scheduling domain and the redundant resources. The redundant resources may be used for resource scheduling when the service volume of the scheduling domain increases.
In the embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted into the matching rule, the resource pool corresponding to the scheduling domain is configured according to the service attribute information, the resource attribute information and the matching rule, the workload of manually configuring the resources is reduced, the resource configuration efficiency is improved, when the resource is scheduled, the scheduling is directly performed in the resource pool corresponding to the configured scheduling domain, a new scheduling strategy is not required to be developed aiming at the scheduling domain, and the development cost is saved.
In one possible implementation, the scheduling domain corresponds to a plurality of edge cloud node resources, and the method further includes:
And determining resource scheduling priorities corresponding to the plurality of edge cloud node resources corresponding to the scheduling domain respectively based on the resource preference information corresponding to the scheduling domain.
Under the condition that the scheduling domain corresponds to a plurality of edge cloud node resources, resource scheduling priority can be configured for the edge cloud node resources. The resource preference information indicates preference information of the scheduling domain for resources when scheduling the resources, for example, the scheduling domain has preference for resources having a low price from the viewpoint of saving costs.
The resource preference information may be in the form of resource preference rules, which may be received from the terminal device or may be obtained from a preset database. For any scheduling domain, if the scheduling domain has preference for resources with lower price, the resource preference rule of the scheduling domain can be configured according to the preference of the scheduling domain. The resource preference rule comprises a demand expression corresponding to the service attribute information, a demand expression corresponding to the resource attribute information and an effective area. A priority may be set for each resource preference rule, with higher priority indicating that the edge cloud node resources in the resource preference rule meet the preference requirements of the scheduling domain.
The priority value range of the resource preference rule is set at [0,999] in an exemplary way, the smaller value represents the higher priority, the interval [0,999] is divided into two parts, one part is used for the priority setting of the user-defined resource preference rule, the preference priority can take a value which is not 3 times in the interval [334,666], and the other part is used for the default configuration of the resource allocation center.
The resource scheduling priorities corresponding to the plurality of edge cloud node resources corresponding to the scheduling domain can be determined by scoring according to the resource preference rules, and the higher the score of the resource preference rule corresponding to the edge cloud node resource is, the higher the resource scheduling priority of the edge cloud node resource is.
The resource preference rules configured by the area B of the resource pool corresponding to the scheduling domain A are provided with 4 corresponding priorities of [5,23,45,323], the priority of the resource preference rules satisfied by the resource unit cell1 of the area B is [5,23], the priority of the resource preference rules satisfied by the resource unit cell2 of the area B is [45,323], the cell1 and the cell2 are respectively scored according to the preconfigured scoring rules, the score of the cell1 is 12/15 x 100=80, the score of the cell2 is 20, and the resource scheduling priority of the cell1 is higher than that of the cell2. The resource unit is a schedulable resource unit in the resource pool, and is a logic resource object extracted from the edge source node resource.
In this embodiment, the resource scheduling priority corresponding to the edge cloud node resource is configured, and when the resource scheduling is performed, the resource can be scheduled according to the resource scheduling priority, so that the scheduled resource accords with the preference of the scheduling domain, for example, the scheduling domain prefers the resource with lower price, and scheduling is performed according to the resource scheduling priority, so that the utilization rate of the low-price resource can be improved, and the cost of using the resource can be reduced.
In a possible implementation manner, the configuring the resource pool corresponding to the scheduling domain according to at least one edge cloud node resource corresponding to the scheduling domain includes:
determining specification information of a resource pool corresponding to a scheduling domain;
and configuring a resource pool corresponding to the scheduling domain according to the specification information and at least one edge cloud node resource.
In practical application, from the point of hit rate of resource scheduling, specification information is configured for the resource pool, and the resource pool corresponding to the scheduling domain is configured according to the specification information and the edge cloud node resources matched with the scheduling domain. The resource scheduling is carried out in the resource pool corresponding to the scheduling domain, so that the situation that the traffic of the service in the scheduling domain flows on all available resources at will can be avoided, the source return quantity cannot be controlled, the hit rate is low, and the resource scheduling cost is increased. Therefore, a resource pool needs to be configured for the scheduling domain, the resource pool contains the matched resources of the scheduling domain, and when the resource scheduling is carried out, the flow range of the service flow is limited on the edge cloud node resources in the resource pool, so that the hit rate is ensured.
When configuring a resource pool corresponding to a scheduling domain, determining specification information of the resource pool is needed, considering meeting the requirement of service in the scheduling domain, and reserving redundant resources to meet the fluctuation of service quantity. When the service traffic suddenly increases, the newly increased edge cloud node resources have no cache of the service, which may cause the traffic to return to the source station, and the resource scheduling needs to be performed again, so that the resource scheduling cost is increased. By adopting the method for reserving redundant resources, the configured resource pool not only can bear the current service quantity, but also can leave enough redundant quantity, and when the service quantity suddenly increases, the resource pool still has enough capacity to bear. In addition, the redundant resources are always in the resource pool, so that the cache hit probability is much higher than that of newly added resources, and the stability of the hit rate is ensured.
In this embodiment, the resource pool corresponding to the scheduling domain is configured according to the specification information of the resource pool, so that the hit rate of resource scheduling can be increased and the cost of resource scheduling can be reduced when resource scheduling is performed.
How to determine the specification information of the resource pool is specifically described in the following embodiments:
in one possible implementation manner, determining the specification information of the resource pool corresponding to the scheduling domain includes:
acquiring redundant resource quantity of a resource pool, a specification configuration effective area of the resource pool and resource demand information of a scheduling domain corresponding to the resource pool;
and determining the specification information of the resource pool according to the redundant resource quantity, the specification configuration effective area and the resource demand information.
In practical application, the redundant resource amount of the resource pool, the specification configuration effective area of the resource pool and the resource demand information of the scheduling domain corresponding to the resource pool may be received from the terminal device or may be obtained from a preset database.
The coverage requirements of services in a scheduling domain are various, some services need to ensure the resource coverage of the present province, some services need to cover a large area, some services need to join all resources of a certain type, and some services need to configure redundant resources of a designated area in advance. And determining the specification information of the resource pool according to the different requirements of the service.
In one example, the resource pool specification information includes a plurality of fields including a resource pool name, a specification type, a specification value, a region type of effect, and a requirement for a resource. The specification type refers to the type of service in the scheduling domain, and the redundant resource amount required by each service is calculated adaptively according to the size of the service amount of different types. The specification value corresponding to the specification type indicates how many times the amount of redundant resources is the amount of service. The redundant resource amount can be calculated according to the specification type and the specification value. The types of regions of action may include large area coverage, provincial coverage, custom regions, and the like. The large area coverage means that the specification configuration is valid from each operator large area. The provincial coverage means that the specification configuration is effective from each operator province.
In a possible implementation manner, according to the specification information and at least one edge cloud node resource, configuring a resource pool corresponding to the scheduling domain includes:
and adding or reducing the edge cloud node resources in at least one edge cloud node resource according to the specification information to obtain a resource pool corresponding to the scheduling domain.
In practical application, redundant resources can be added in the edge cloud node resources matched with the scheduling domain according to the specification information, so as to obtain a resource pool corresponding to the scheduling domain, and the requirement of increasing the service amount in the scheduling domain is met. The resources can be reduced in the edge cloud node resources matched with the scheduling domain, a resource pool corresponding to the scheduling domain is obtained, and the hit rate of resource scheduling can be provided.
In one possible implementation, the method further includes:
Updating a plurality of service attribute information, a plurality of resource attribute information and a plurality of matching rules respectively corresponding to a plurality of scheduling domains according to a preset time period;
Checking the specification of the resource pool corresponding to each of the plurality of scheduling domains by utilizing the updated plurality of service attribute information, the updated plurality of resource attribute information and the updated plurality of matching rules;
And determining whether to generate a resource adjustment strategy of at least one resource pool according to the specification verification result corresponding to the at least one resource pool.
In practical application, the configuration data may be updated periodically according to a preset time period, where the configuration data includes a plurality of service attribute information, a plurality of resource attribute information, and a plurality of matching rules corresponding to a plurality of scheduling domains, respectively. And checking the specifications of the plurality of resource pools by using the updated configuration data, and if one or more of the plurality of resource pools does not accord with the updated configuration data, generating a resource adjustment strategy of the resource pool, wherein the resource adjustment strategy is used for adjusting the specifications of the resource pool, for example, adding or reducing the edge cloud node resources in the resource pool.
In order to facilitate understanding of the technical idea of the present application, the technical scheme of the present application is described below by two specific embodiments. Fig. 7 is a schematic diagram of a design idea of a resource allocation method according to an embodiment of the present application. In this embodiment, the resource allocation is performed by the resource allocation center, and the overall architecture of the resource allocation center is as follows:
The configuration module is used for configuring service attribute information corresponding to the plurality of scheduling domains respectively, configuring resource attribute information corresponding to the plurality of edge cloud node resources respectively, configuring matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources, configuring resource scheduling priority of the edge cloud node resources in the resource pool and configuring specification information of the resource pool.
And the index quantization layer is used for sensing the use state of the edge cloud node resources, calculating indexes associated with resource scheduling cost, quality and the like, and providing a query and display interface for a user. The resource adjustment strategy also makes strategy formulation according to the information of the index quantization layer.
And the resource adjustment strategy is determined according to the resource scheduling cost, hit rate, flow control, supply chain, quality, stability, operation and maintenance requirement information of the service in the scheduling domain, indexes provided by the index quantization layer, resource scheduling priority and the like, and the resource adjustment strategy is executed to adjust the edge cloud node resources in the resource pool. For example, the specification of the resource pool corresponding to any scheduling domain is adjusted, and the edge cloud node resources are increased or reduced in the resource pool so as to meet the requirements of services in the scheduling domain.
Fig. 8 is a schematic diagram of a design idea of a resource allocation method according to an embodiment of the present application. As shown in fig. 8, the method specifically comprises the following steps:
1. And reading the configuration information. And (3) acquiring information such as label records, matching rules, resource preference rules, resource pool specifications and the like of the scheduling domain and the edge cloud node resources in the database by utilizing various data loaders at regular time. The database can comprise label records, matching rules, resource preference rules, resource pool specifications and other information of the scheduling domain and the edge cloud node resources, and data in the database can be added, deleted and modified periodically according to requirements.
2. And (5) resource screening. After the label records and the matching rules of the dispatching domain and the edge cloud node resources are obtained, the resource screening conditions of each resource pool are determined according to the matching rules, the resources of each resource pool are screened according to the screening conditions, and the resources which do not meet the conditions are filtered.
3. Resource preference scoring. After the available resources of each resource pool are screened out, the available resources are gathered according to the regional dimension according to the resource preference rules matched with the resource pools, and then preference scoring is carried out on the available resources of each region.
4. And (5) checking the specification of the resource pool. And (3) checking whether the specification configuration of the resource pool is met or not according to the state of the current resource in each resource pool and the configured specification information of the resource pool, and if so, not operating and executing the step (1). If not, step 5 is performed.
5. And triggering the specification adjustment of the resource pool. If the resource pool does not meet the configured resource pool specification information, calculating the resource demand for each resource pool which does not meet the resource pool, and acquiring corresponding resources from available resources according to the demand.
6. And outputting a resource adjustment strategy. And (3) generating a resource pool adjustment strategy according to the calculation result in the step (5), executing the resource adjustment strategy in the database DB, adjusting the specification of the resource pool, and executing the step (1).
The embodiment of the application provides a resource scheduling method for edge cloud, which can be applied to computing equipment, wherein the computing equipment can comprise a server, a user terminal and the like. Fig. 9 is a flowchart of a resource scheduling method for edge cloud according to an embodiment of the present application, which may include:
In step S901, in response to the resource scheduling request, a scheduling domain corresponding to the resource scheduling request is determined.
Step S902, scheduling edge cloud node resources for a scheduling domain in a resource pool corresponding to the scheduling domain.
In this embodiment, the description is made with the server as the execution body. After receiving the resource scheduling request, the server analyzes the resource scheduling request, determines a scheduling domain corresponding to the resource scheduling request according to the analysis result, and schedules the edge cloud node resource for the scheduling domain in a resource pool corresponding to the scheduling domain. The resource pool is configured for the scheduling domain by utilizing the resource configuration method for the edge cloud according to any embodiment of the present application, and the specific configuration process is described in the above embodiment, which is not repeated herein.
In the embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted into the matching rule, the resource pool corresponding to the scheduling domain is configured according to the service attribute information, the resource attribute information and the matching rule, the workload of manually configuring the resources is reduced, the resource configuration efficiency is improved, when the resource is scheduled, the scheduling is directly performed in the resource pool corresponding to the configured scheduling domain, a new scheduling strategy is not required to be developed aiming at the scheduling domain, and the development cost is saved.
In one possible implementation, the scheduling domain corresponds to a plurality of edge cloud node resources, and the scheduling of the edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain includes:
and scheduling the edge cloud node resources for the scheduling domain in the resource pool based on the resource scheduling priorities respectively corresponding to the plurality of edge cloud node resources.
In practical application, the edge cloud node resources are scheduled for the scheduling domain according to the resource scheduling priority. The resource scheduling priority is determined according to the resource preference information corresponding to the scheduling domain.
The resource preference information may be in the form of resource preference rules, which may be received from the terminal device or may be obtained from a preset database. For any scheduling domain, if the scheduling domain has preference for resources with lower price, the resource preference rule of the scheduling domain can be configured according to the preference of the scheduling domain. The resource preference rule comprises a demand expression corresponding to the service attribute information, a demand expression corresponding to the resource attribute information and an effective area. A priority may be set for each resource preference rule, with higher priority indicating that the edge cloud node resources in the resource preference rule meet the preference requirements of the scheduling domain.
The resource scheduling priorities corresponding to the plurality of edge cloud node resources corresponding to the scheduling domain can be determined by scoring according to the resource preference rules, and the higher the score of the resource preference rule corresponding to the edge cloud node resource is, the higher the resource scheduling priority of the edge cloud node resource is.
In this embodiment, the resources are scheduled according to the resource scheduling priority, so that the scheduled resources conform to the preference of the scheduling domain, for example, the scheduling domain prefers resources with lower price, and scheduling is performed according to the resource scheduling priority, so that the utilization rate of low-price resources can be improved, and the cost of using the resources can be reduced.
Corresponding to the application scene and the method of the method provided by the embodiment of the application, the embodiment of the application also provides a resource allocation device for the edge cloud. Fig. 10 is a block diagram of a resource allocation device for an edge cloud according to an embodiment of the present application, where the resource allocation device for an edge cloud may include:
The information obtaining module 1001 is configured to obtain service attribute information corresponding to each of a plurality of scheduling domains, resource attribute information corresponding to each of a plurality of edge cloud node resources, and a matching rule of the plurality of scheduling domains and the plurality of edge cloud node resources;
A first configuration module 1002, configured to configure at least one edge cloud node resource corresponding to each of the plurality of scheduling domains according to the plurality of service attribute information, the plurality of resource attribute information, and the plurality of matching rules;
The second configuration module 1003 is configured to configure a resource pool corresponding to the scheduling domain according to at least one edge cloud node resource corresponding to the scheduling domain, where the resource pool is used to schedule resources for the scheduling domain.
In the embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted into the matching rule, the resource pool corresponding to the scheduling domain is configured according to the service attribute information, the resource attribute information and the matching rule, the workload of manually configuring the resources is reduced, the resource configuration efficiency is improved, when the resource is scheduled, the scheduling is directly performed in the resource pool corresponding to the configured scheduling domain, a new scheduling strategy is not required to be developed aiming at the scheduling domain, and the development cost is saved.
In a possible implementation manner, the scheduling domain corresponds to a plurality of edge cloud node resources, and the apparatus further includes a priority determining module, configured to:
And determining resource scheduling priorities corresponding to the plurality of edge cloud node resources corresponding to the scheduling domain respectively based on the resource preference information corresponding to the scheduling domain.
In one possible implementation, the second configuration module 1003 is configured to:
determining specification information of a resource pool corresponding to a scheduling domain;
and configuring a resource pool corresponding to the scheduling domain according to the specification information and at least one edge cloud node resource.
In one possible implementation manner, the second configuration module 1003 is configured to, when determining the specification information of the resource pool corresponding to the scheduling domain:
acquiring redundant resource quantity of a resource pool, a specification configuration effective area of the resource pool and resource demand information of a scheduling domain corresponding to the resource pool;
and determining the specification information of the resource pool according to the redundant resource quantity, the specification configuration effective area and the resource demand information.
In one possible implementation, the second configuration module 1003 is configured to:
and adding or reducing the edge cloud node resources in at least one edge cloud node resource according to the specification information to obtain a resource pool corresponding to the scheduling domain.
In one possible implementation manner, the apparatus further includes a verification module, configured to:
Updating a plurality of service attribute information, a plurality of resource attribute information and a plurality of matching rules respectively corresponding to a plurality of scheduling domains according to a preset time period;
Checking the specification of the resource pool corresponding to each of the plurality of scheduling domains by utilizing the updated plurality of service attribute information, the updated plurality of resource attribute information and the updated plurality of matching rules;
And determining whether to generate a resource adjustment strategy of at least one resource pool according to the specification verification result corresponding to the at least one resource pool.
In one possible implementation, the matching rule includes a requirement expression corresponding to the service attribute information and a requirement expression corresponding to the resource attribute information, and the matching rule is used for characterizing a use requirement of the scheduling domain on the edge cloud node resource.
The functions of each module in each device of the embodiment of the present application may be referred to the corresponding descriptions in the above methods, and have corresponding beneficial effects, which are not described herein.
Corresponding to the application scene and the method of the method provided by the embodiment of the application, the embodiment of the application also provides a resource scheduling device for the edge cloud. Fig. 11 is a block diagram of a resource scheduling device for an edge cloud according to an embodiment of the present application, where the resource scheduling device for an edge cloud may include:
A request response module 1101, configured to determine a scheduling domain corresponding to the resource scheduling request in response to the resource scheduling request;
A resource scheduling module 1102, configured to schedule edge cloud node resources for a scheduling domain in a resource pool corresponding to the scheduling domain;
wherein the resource pool is configured for the scheduling domain according to the method of any embodiment of the application.
In the embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted into the matching rule, the resource pool corresponding to the scheduling domain is configured according to the service attribute information, the resource attribute information and the matching rule, the workload of manually configuring the resources is reduced, the resource configuration efficiency is improved, when the resource is scheduled, the scheduling is directly performed in the resource pool corresponding to the configured scheduling domain, a new scheduling strategy is not required to be developed aiming at the scheduling domain, and the development cost is saved.
In one possible implementation, the resource scheduling module 1102 is specifically configured to:
and scheduling the edge cloud node resources for the scheduling domain in the resource pool based on the resource scheduling priorities respectively corresponding to the plurality of edge cloud node resources.
The functions of each module in each device of the embodiment of the present application may be referred to the corresponding descriptions in the above methods, and have corresponding beneficial effects, which are not described herein.
Fig. 12 is a block diagram of an electronic device used to implement an embodiment of the application. As shown in fig. 12, the electronic device includes a memory 1210 and a processor 1220, the memory 1210 having stored therein a computer program executable on the processor 1220. Processor 1220, when executing the computer program, implements the methods of the embodiments described above. The number of memory 1210 and processor 1220 may be one or more.
The electronic device further includes:
The communication interface 1230 is used for communicating with external devices for data interactive transmission.
If the memory 1210, the processor 1220 and the communication interface 1230 are implemented separately, the memory 1210, the processor 1220 and the communication interface 1230 may be connected to each other and perform communication with each other through buses. The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 12, but not only one bus or one type of bus.
Alternatively, in a specific implementation, if the memory 1210, the processor 1220 and the communication interface 1230 are integrated on a chip, the memory 1210, the processor 1220 and the communication interface 1230 may perform communication with each other through internal interfaces.
The embodiment of the application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the method provided in the embodiment of the application.
The embodiment of the application also provides a chip, which comprises a processor and is used for calling the instructions stored in the memory from the memory and running the instructions stored in the memory, so that the communication equipment provided with the chip executes the method provided by the embodiment of the application.
The embodiment of the application also provides a chip which comprises an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected through an internal connection path, the processor is used for executing codes in the memory, and when the codes are executed, the processor is used for executing the method provided by the application embodiment.
It should be appreciated that the Processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be a processor supporting an advanced reduced instruction set machine (ADVANCED RISC MACHINES, ARM) architecture.
Further alternatively, the memory may include a read-only memory and a random access memory. The memory may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), programmable ROM (PROM), erasable Programmable ROM (EPROM), electrically Erasable EPROM (EEPROM), or flash Memory, among others. Volatile memory can include random access memory (Random Access Memory, RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available. For example, static random access memory (STATIC RAM, SRAM), dynamic random access memory (Dynamic Random Access Memory, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNC LINK DRAM, SLDRAM), and Direct memory bus random access memory (DR RAM).
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are fully or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
Any process or method described in flow charts or otherwise herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present application includes additional implementations in which functions may be performed in a substantially simultaneous manner or in an opposite order from that shown or discussed, including in accordance with the functions that are involved.
Logic and/or steps described in the flowcharts or otherwise described herein, e.g., may be considered a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the methods of the embodiments described above may be performed by a program that, when executed, comprises one or a combination of the steps of the method embodiments, instructs the associated hardware to perform the method.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules described above, if implemented in the form of software functional modules and sold or used as a stand-alone product, may also be stored in a computer-readable storage medium. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.
The above description is merely an exemplary embodiment of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of various changes or substitutions within the technical scope of the present application, and these should be covered in the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.
Claims (10)
1. A method of resource allocation for an edge cloud, the method comprising:
Acquiring service attribute information corresponding to a plurality of scheduling domains respectively, resource attribute information corresponding to a plurality of edge cloud node resources respectively, and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources, wherein the scheduling domains comprise at least one service;
Configuring at least one edge cloud node resource corresponding to each of the plurality of scheduling domains according to the plurality of service attribute information, the plurality of resource attribute information and the plurality of matching rules;
the method comprises the steps of configuring a resource pool corresponding to a dispatching domain according to at least one edge cloud node resource corresponding to the dispatching domain, wherein the resource pool is used for dispatching resources for the dispatching domain, the configuration of the resource pool corresponding to the dispatching domain according to at least one edge cloud node resource corresponding to the dispatching domain comprises the steps of determining specification information of the resource pool corresponding to the dispatching domain, configuring the resource pool corresponding to the dispatching domain according to the specification information and the at least one edge cloud node resource, and determining specification information of the resource pool corresponding to the dispatching domain comprises the steps of obtaining redundant resource quantity of the resource pool, specification configuration effective area of the resource pool and resource demand information of the dispatching domain corresponding to the resource pool, and determining the specification information of the resource pool according to the redundant resource quantity, the specification configuration effective area and the resource demand information.
2. The method of claim 1, wherein the scheduling domain corresponds to a plurality of edge cloud node resources, the method further comprising:
and determining resource scheduling priorities corresponding to a plurality of edge cloud node resources corresponding to the scheduling domain respectively based on the resource preference information corresponding to the scheduling domain.
3. The method according to claim 1, wherein the configuring the resource pool corresponding to the scheduling domain according to the specification information and the at least one edge cloud node resource includes:
and adding or reducing edge cloud node resources in the at least one edge cloud node resource according to the specification information to obtain a resource pool corresponding to the scheduling domain.
4. A method according to any one of claims 1-3, wherein the method further comprises:
updating a plurality of service attribute information, a plurality of resource attribute information and a plurality of matching rules respectively corresponding to a plurality of scheduling domains according to a preset time period;
Verifying the specification of the resource pool corresponding to each of the plurality of scheduling domains by using the updated plurality of service attribute information, the updated plurality of resource attribute information and the updated plurality of matching rules;
and determining whether to generate a resource adjustment strategy of at least one resource pool according to the specification verification result corresponding to the at least one resource pool.
5. A method according to any one of claims 1-3, wherein the matching rule includes a requirement expression corresponding to the service attribute information and a requirement expression corresponding to the resource attribute information, and the matching rule is used to characterize a requirement of the scheduling domain for use of the edge cloud node resource.
6. A resource scheduling method for an edge cloud, the method comprising:
responding to a resource scheduling request, and determining a scheduling domain corresponding to the resource scheduling request;
Scheduling edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain;
wherein the resource pool is configured for the scheduling domain according to the method of any of claims 1-5.
7. The method of claim 6, wherein the scheduling domain corresponds to a plurality of edge cloud node resources, and wherein the scheduling edge cloud node resources for the scheduling domain in the resource pool corresponding to the scheduling domain comprises:
And scheduling the edge cloud node resources for the scheduling domain in the resource pool based on the resource scheduling priorities respectively corresponding to the plurality of edge cloud node resources.
8. A resource allocation apparatus for an edge cloud, comprising:
The information acquisition module is used for acquiring service attribute information corresponding to a plurality of scheduling domains respectively, resource attribute information corresponding to a plurality of edge cloud node resources respectively and matching rules of the plurality of scheduling domains and the plurality of edge cloud node resources;
the first configuration module is used for configuring at least one edge cloud node resource corresponding to each of the plurality of scheduling domains according to the plurality of service attribute information, the plurality of resource attribute information and the plurality of matching rules;
the second configuration module is used for configuring a resource pool corresponding to the scheduling domain according to at least one edge cloud node resource corresponding to the scheduling domain, wherein the resource pool is used for scheduling resources for the scheduling domain, the second configuration module is further used for determining specification information of the resource pool corresponding to the scheduling domain, configuring the resource pool corresponding to the scheduling domain according to the specification information and the at least one edge cloud node resource, determining the specification information of the resource pool corresponding to the scheduling domain comprises the steps of obtaining redundant resource quantity of the resource pool, a specification configuration effective area of the resource pool and resource demand information of the scheduling domain corresponding to the resource pool, and determining the specification information of the resource pool according to the redundant resource quantity, the specification configuration effective area and the resource demand information.
9. A resource scheduling apparatus for an edge cloud, comprising:
A request response module, configured to respond to a resource scheduling request, and determine a scheduling domain corresponding to the resource scheduling request;
the resource scheduling module is used for scheduling the edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain;
wherein the resource pool is configured for the scheduling domain according to the method of any of claims 1-5.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory, the processor implementing the method of any one of claims 1-7 when the computer program is executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211160189.1A CN115514818B (en) | 2022-09-22 | 2022-09-22 | Resource configuration method and resource scheduling method for edge cloud |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211160189.1A CN115514818B (en) | 2022-09-22 | 2022-09-22 | Resource configuration method and resource scheduling method for edge cloud |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115514818A CN115514818A (en) | 2022-12-23 |
| CN115514818B true CN115514818B (en) | 2025-05-13 |
Family
ID=84506169
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211160189.1A Active CN115514818B (en) | 2022-09-22 | 2022-09-22 | Resource configuration method and resource scheduling method for edge cloud |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115514818B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118488587B (en) * | 2024-07-12 | 2024-11-12 | 北京中网华通设计咨询有限公司 | Wireless communication network scheduling method and system based on artificial intelligence |
| CN119155355B (en) * | 2024-11-11 | 2025-03-25 | 西安旭阳通讯设备有限公司 | Communication performance optimization method and system based on Internet of Things |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104252390B (en) * | 2013-06-28 | 2018-08-14 | 华为技术有限公司 | Resource regulating method, device and system |
| KR20160109300A (en) * | 2015-03-10 | 2016-09-21 | 한국전자통신연구원 | Method and Apparatus for managing distributed cloud |
| CN116170316B (en) * | 2019-04-08 | 2025-09-26 | 阿里巴巴集团控股有限公司 | Network system, instance management method, device and storage medium |
| CN110737442B (en) * | 2019-09-24 | 2021-06-22 | 厦门网宿有限公司 | Edge application management method and system |
| CN112367370A (en) * | 2020-10-27 | 2021-02-12 | 中国光大银行股份有限公司 | Management method, device, equipment and medium for hybrid cloud resource data |
| CN113242319A (en) * | 2021-07-09 | 2021-08-10 | 军事科学院系统工程研究院网络信息研究所 | Cloud edge cooperative work method and system based on video cloud service architecture |
| CN114625965A (en) * | 2022-03-15 | 2022-06-14 | 拉扎斯网络科技（上海）有限公司 | Resource information recommendation method and device and electronic equipment |
-
2022
- 2022-09-22 CN CN202211160189.1A patent/CN115514818B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN115514818A (en) | 2022-12-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10826799B2 (en) | Apparatus for providing cloud service based on cloud service brokerage and method thereof | |
| CN110769038B (en) | Server scheduling method and device, storage medium and electronic equipment | |
| WO2021233391A1 (en) | Routing information sending method, routing information receiving method, network element and node device | |
| US10481935B2 (en) | Management system, overall management node, and management method for managing virtualization resources in a mobile communication network | |
| CN115514818B (en) | Resource configuration method and resource scheduling method for edge cloud | |
| US9185006B2 (en) | Exchange of server health and client information through headers for request management | |
| CN111010426A (en) | Message pushing method and device | |
| CN104348647B (en) | Multi-source bandwidth scheduling method, apparatus and system | |
| US11064041B2 (en) | Apparatus for providing cloud service using cloud service brokerage based on multiple clouds and method thereof | |
| US10152449B1 (en) | User-defined capacity reservation pools for network-accessible resources | |
| US11102145B2 (en) | Resource sharing method, computer device, and storage medium | |
| CN113691575B (en) | Communication method, device and system | |
| CN110830604B (en) | DNS scheduling method and device | |
| CN114844791B (en) | Cloud service automatic management and distribution method and system based on big data and storage medium | |
| CN117176502A (en) | Computing power network operation method, equipment and storage medium based on computing power message bus | |
| WO2025076899A1 (en) | Distributed computing power resource scheduling method and system | |
| CN103561092A (en) | Method and device for managing resources under private cloud environment | |
| CN112003957B (en) | Method, device, server and storage medium for scheduling access point | |
| CN115514777B (en) | Resource management method and device, electronic device and storage medium | |
| CN115529310B (en) | Communication method, device, related equipment and storage medium | |
| CN116233027A (en) | CDN resource scheduling method and device, electronic equipment and storage medium | |
| US20220012657A1 (en) | Scheduler for jobs during off peak hours | |
| CN114053689A (en) | Service scheduling method, device, device and storage medium for cloud games | |
| CN112019442B (en) | Data distribution method, system, equipment and medium based on bounded consistency Hash algorithm | |
| CN112291103A (en) | Network scheduling method and device, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |