Resource configuration method and resource scheduling method for edge cloud

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

[0001] The present application relates to the field of cloud computing technology, and in particular to a resource configuration method and a resource scheduling method for edge cloud. Background Art

[0002] With the continuous development of Internet technology, more and more service providers use content delivery networks (CDN) to accelerate their services. CDN service providers can allocate resources to service providers according to their needs. Among them, resources can include: computing resources, storage resources and network resources (for example, bandwidth resources). Resource planning is very important in the CDN scheduling system, and it is necessary to solve the problem of which resources are covered by the service.

[0003] Services have various requirements for resource usage. The operation and maintenance team needs to manually configure resources for each service requirement, which is inefficient. In addition, it is necessary to develop resource scheduling strategies, which are costly to develop. Summary of the invention

[0004] The embodiments of the present application provide a resource configuration method and a resource scheduling method for edge cloud to improve resource configuration efficiency and save the cost of developing resource scheduling strategies.

[0005] In a first aspect, an embodiment of the present application provides a resource configuration method for an edge cloud, comprising:

[0006] Obtain service attribute information corresponding to a plurality of scheduling domains, resource attribute information corresponding to a plurality of edge cloud node resources, and matching rules between a plurality of scheduling domains and a plurality of edge cloud node resources; the scheduling domain includes at least one service;

[0007] According to the plurality of service attribute information, the plurality of resource attribute information, and the plurality of matching rules, at least one edge cloud node resource corresponding to each of the plurality of scheduling domains is configured;

[0008] According to at least one edge cloud node resource corresponding to the scheduling domain, a resource pool corresponding to the scheduling domain is configured, and the resource pool is used to schedule resources for the scheduling domain.

[0009] In a second aspect, an embodiment of the present application provides a resource scheduling method for an edge cloud, including:

[0010] In response to the resource scheduling request, determining a scheduling domain corresponding to the resource scheduling request;

[0011] Scheduling edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain;

[0012] Among them, the resource pool is configured for the scheduling domain according to the method of any embodiment of the present application.

[0013] In a third aspect, an embodiment of the present application provides a resource configuration device for an edge cloud, including:

[0014] An information acquisition module, used to acquire service attribute information corresponding to multiple scheduling domains, resource attribute information corresponding to multiple edge cloud node resources, and matching rules between multiple scheduling domains and multiple edge cloud node resources; a scheduling domain includes at least one service;

[0015] A first configuration module is used to configure at least one edge cloud node resource corresponding to each of the plurality of scheduling domains according to a plurality of service attribute information, a plurality of resource attribute information, and a plurality of matching rules;

[0016] The second configuration module is used to configure 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 to schedule resources for the scheduling domain.

[0017] In a fourth aspect, an embodiment of the present application provides a resource scheduling device for an edge cloud, including:

[0018] A request response module, used to respond to a resource scheduling request and determine a scheduling domain corresponding to the resource scheduling request;

[0019] A resource scheduling module, used to schedule edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain;

[0020] Among them, the resource pool is configured for the scheduling domain according to the method of any embodiment of the present application.

[0021] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory, wherein the processor implements any of the methods described above when executing the computer program.

[0022] Compared with the prior art, this application has the following advantages:

[0023] The present application provides a resource configuration method and resource scheduling method for edge cloud, which obtains service attribute information corresponding to multiple scheduling domains, resource attribute information corresponding to multiple edge cloud node resources, and matching rules between 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. In this embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted into a matching rule, and the resource pool corresponding to the scheduling domain is configured according to multiple service attribute information, multiple resource attribute information, and multiple matching rules, which reduces the workload of manual resource configuration and improves resource configuration efficiency; when performing resource scheduling, scheduling is performed directly in the resource pool corresponding to the configured scheduling domain, and there is no need to develop a new scheduling strategy for the scheduling domain, saving development costs.

[0024] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments according to the present application and should not be regarded as limiting the scope of the present application.

[0026] Figure 1 A schematic diagram of an application scenario of the resource configuration method for edge cloud provided in this application;

[0027] Figure 2 A schematic diagram of a resource pool corresponding to a configuration scheduling domain provided in an embodiment of the present application;

[0028] Figure 3 A schematic diagram of a resource scheduling method provided in an embodiment of the present application;

[0029] Figure 4 A flowchart of a resource configuration method for edge cloud provided in one embodiment of the present application;

[0030] Figure 5 A schematic diagram of a demand expression provided in an embodiment of the present application;

[0031] Figure 6 A schematic diagram of a matching rule provided in an embodiment of the present application;

[0032] Figure 7 A schematic diagram of a design idea of ​​a resource configuration method provided in an embodiment of the present application;

[0033] Figure 8 A schematic diagram of a design idea of ​​a resource configuration method provided in an embodiment of the present application;

[0034] Fig. 9 This is a flow chart of a resource scheduling method for edge cloud according to an embodiment of the present application;

[0035] Fig.10 It is a structural block diagram of a resource configuration device for edge cloud according to an embodiment of the present application;

[0036] Fig.11 is a structural block diagram of a resource scheduling device for edge cloud according to an embodiment of the present application; and

[0037] Fig.12 A block diagram of an electronic device used to implement an embodiment of the present application. DETAILED DESCRIPTION

[0038] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the concept or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary in nature and not restrictive.

[0039] To facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the related technologies of the embodiments of the present application. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0040] Figure 1 A schematic diagram of an application scenario of the resource configuration method for edge cloud provided in this application. Figure 1 As shown, the resource allocation center is used to configure resource pools and scheduling resources for the scheduling domain. The resource allocation center can implement resource configuration functions through components. The components can be deployed in computing devices, and the computing devices can include servers, user devices, etc. The resource pool includes edge cloud node resources, such as Figure 1Node 1, node 2...node n shown in . Wherein, the scheduling domain refers to the collection of objects that use edge cloud node resources. For example, objects that use edge cloud node resources may include services for enterprise users, and one service may correspond to a domain name. Wherein, edge cloud refers to a cloud computing platform that is relatively close to the terminal, or, in other words, it is different from the central cloud or traditional cloud computing platform. The central cloud or traditional cloud computing platform may include a data center with scaled resources and centralized locations, while the edge cloud node covers a wider network range and therefore has the characteristic of being closer to the terminal. The edge cloud includes multiple edge cloud nodes, and each edge cloud node includes a series of edge infrastructures, which include but are not limited to: distributed data centers, wireless computer rooms or clusters, operator communication networks, core network equipment, base stations, edge gateways, home gateways, computing devices or storage devices and other edge devices and corresponding network environments. It is explained here that the locations, capabilities and infrastructures of different edge cloud nodes may be the same or different. Edge cloud node resources refer to using edge cloud nodes as resources, which may specifically include at least one of computing resources, storage resources and network resources (e.g., bandwidth resources). The resource allocation center receives 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 sent by the terminal device of the operation and maintenance personnel. The matching rule includes at least one demand expression, and the demand expression represents the service's demand for resource usage. The resource allocation center configures at least one edge cloud node resource corresponding to the multiple scheduling domains according to the multiple service attribute information, the multiple resource attribute information, and the multiple matching rules, and configures the resource pool corresponding to the scheduling domain according to the at least one edge cloud node resource corresponding to the scheduling domain.

[0041] Figure 2 Schematic diagram of the resource pool corresponding to the configuration scheduling domain provided in the embodiment of the present application. Figure 2 As shown, the resource pool of scheduling domain A includes nodes 1, 2, 3, and 4; the resource pool of scheduling domain B includes nodes 2, 5, 6, and 7; the resource pool of scheduling domain C includes nodes 7 and 8; where nodes can be reused between different scheduling domains, such as Figure 2 As shown, the resource pool of scheduling domain A and the resource pool of scheduling domain B reuse node 2, and the resource pool of scheduling domain B and the resource pool of scheduling domain C reuse node 7.

[0042] Figure 3 Schematic diagram of the resource scheduling method provided in the embodiment of the present application. Figure 3As shown, the scheduling domain C includes domain name x, domain name y, and domain name z. After receiving the user content request, the resource allocation center parses the user content request, determines the scheduling domain C corresponding to the user content request according to the parsing result, and performs resource scheduling in nodes 7 and 8 of the resource pool corresponding to the scheduling domain C. Nodes 7 and 8 provide resources for the source stations of domain name x, domain name y, and domain name z, respectively.

[0043] The embodiment of the present application provides a resource configuration method for edge cloud. The method in this embodiment can be applied to a computing device, which may include: a server, a user terminal, etc. Figure 4 The flowchart of the resource configuration method for edge cloud according to an embodiment of the present application may include:

[0044] Step S401, obtaining service attribute information corresponding to multiple scheduling domains, resource attribute information corresponding to multiple edge cloud node resources, and matching rules between multiple scheduling domains and multiple edge cloud node resources; the scheduling domain includes at least one service.

[0045] Step S402: According to multiple service attribute information, multiple resource attribute information, and multiple matching rules, at least one edge cloud node resource corresponding to each of the multiple scheduling domains is configured.

[0046] Step S403: According to at least one edge cloud node resource corresponding to the scheduling domain, a resource pool corresponding to the scheduling domain is configured, and the resource pool is used to schedule resources for the scheduling domain.

[0047] In this embodiment, the server is used as the execution subject for introduction. Optionally, the server receives service attribute information corresponding to multiple scheduling domains, resource attribute information corresponding to multiple edge cloud node resources, and matching rules between multiple scheduling domains and multiple edge cloud node resources, sent by the terminal device of the operation and maintenance personnel. Optionally, the server obtains service attribute information corresponding to multiple scheduling domains, resource attribute information corresponding to multiple edge cloud node resources, and matching rules between multiple scheduling domains and multiple edge cloud node resources from a preset database.

[0048] The scheduling domain refers to a collection of objects that use edge cloud node resources. For example, objects that use edge cloud node resources may include services for enterprise users, and one service may correspond to one domain name.

[0049] Edge cloud node resources may include at least one of computing resources, storage resources, and network resources (e.g., bandwidth resources, etc.). Computing resources may include central processing unit (CPU) resources required when a computer program is running. Storage resources may include storage space capacity resources. Bandwidth resources may include the amount of data that can be transmitted in a fixed time.

[0050] Any scheduling domain may correspond to multiple service attribute information, and the service attribute information may be attribute information representing the services included in the scheduling domain. Resource attribute information may be attribute information representing edge cloud node resources.

[0051] Exemplarily, the service attribute information or resource attribute information may be in the form of a tag record, which is composed of a "tag key" (key) and a "tag value" (value), that is, in the form of {key:value}. The tag key value indicates the attribute type, and the tag value indicates the value of the attribute. The tag key value may include at least one of the tag source, the object to which it belongs, and the tag type.

[0052] Different scheduling domains have different requirements for edge cloud node resources. For example, some scheduling domains need to schedule edge cloud node resources for live broadcast services, and some scheduling domains need to use traffic-free edge cloud node resources. In order to realize the requirements of the scheduling domain through configuration, these requirements need to be abstracted into matching rules. Matching rules are used to connect the scheduling domain and edge cloud node resources to express the scheduling domain's requirements for the use of edge cloud node resources.

[0053] Exemplarily, the matching rule includes a demand expression corresponding to the service attribute information and a demand expression corresponding to the resource attribute information, and the matching rule is used to characterize the scheduling domain's demand for the use of edge cloud node resources.

[0054] The requirement expression (selector) is used to describe the requirements for the attribute value. For example, the requirement expression can be in the form of "tag key value + operator + tag value". Multiple requirement expressions support "and, or" logic and bracket operators. Bracket operators indicate priority. Multiple requirement expressions can be combined as a requirement expression. The operators supported by the requirement expression may include but are not limited to the following 10 types: !, ==, !=, in, notin, >=, <=, &, |, ().

[0055] Figure 5 A schematic diagram of a demand expression provided in an embodiment of the present application, such as Figure 5As shown in the figure, three requirement expressions, selector1, selector2 and selector3, are combined into an expression selector_1_2_3 through AND logic, OR logic and bracket operators. Among them, selector1 indicates that the node name of the edge cloud node resource belongs to the range of the set (cn1, cn2), selector2 indicates that the node's security capability is greater than 1G, and selector3 indicates that the node's physical capability is greater than 1G. The bracket operator indicates the priority. Selector2 and selector3 are combined first to form selector_2_3, which means "the node's security capability is greater than 1G and the node's physical capability is greater than 1G". After that, selector1 and selector_2_3 together form the final selector_1_2_3, which means "the node's security capability and physical capability are both greater than 1G, and the node is one of cn1 and cn2".

[0056] In one example, Figure 6 A schematic diagram of the matching rules provided in the embodiment of the present application, such as Figure 6 As shown in FIG. 1 , the matching rule includes the demand expression corresponding to the service attribute information and the demand expression corresponding to the resource attribute information. The demand expression corresponding to the service attribute information is as follows: Figure 6 The matching business selector1 shown in , the requirement expression corresponding to the resource attribute information is as follows Figure 6 The matching resource selector2 shown in . Among them, the business entity schedm represents the scheduling domain, and selector1 is used to match the tag key value and tag value of the scheduling domain; the resource entity cell represents the edge cloud node resource, and selector2 is used to match the tag key value and tag value of the edge cloud node resource.

[0057] In another example, the matching rule can be composed of three parts: the demand expression of the matching scheduling domain + the effective area + the demand expression of the matching resource. Among them, the demand expression of the matching scheduling domain, that is, the demand expression corresponding to the service attribute information, is used to match one or some types of scheduling domains; the effective area indicates the regional range of the edge cloud node resources where this matching rule is effective, and the resources outside the range are not subject to this matching rule; the demand expression of the matching resource, that is, the demand expression corresponding to the edge cloud node resources, is used to match one or some types of resources.

[0058] According to multiple matching rules, multiple service attribute information and multiple resource attribute information can be matched, and the resources that do not match the scheduling domain can be filtered out to obtain the edge cloud node resources corresponding to the scheduling domain. According to at least one edge cloud node resource corresponding to the scheduling domain, the resource pool corresponding to the scheduling domain is configured. Exemplarily, for any scheduling domain, the multiple edge cloud node resources corresponding to the scheduling domain can be used as resources in the resource pool, and redundant resources can be configured in addition to the multiple edge cloud node resources corresponding to the scheduling domain. The multiple edge cloud node resources and redundant resources corresponding to the scheduling domain are used to jointly form the resource pool corresponding to the scheduling domain. Redundant resources can be used for resource scheduling when the service volume of the scheduling domain increases.

[0059] In this embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted as a matching rule. The resource pool corresponding to the scheduling domain is configured according to multiple service attribute information, multiple resource attribute information, and multiple matching rules, thereby reducing the workload of manual resource configuration and improving resource configuration efficiency. When performing resource scheduling, scheduling is performed directly in the resource pool corresponding to the configured scheduling domain. There is no need to develop a new scheduling strategy for the scheduling domain, thus saving development costs.

[0060] In a possible implementation, the scheduling domain corresponds to a plurality of edge cloud node resources, and the method further includes:

[0061] Based on the resource preference information corresponding to the scheduling domain, the resource scheduling priorities corresponding to the multiple edge cloud node resources corresponding to the scheduling domain are determined.

[0062] In the case where the scheduling domain corresponds to multiple edge cloud node resources, the resource scheduling priority can be configured for the edge cloud node resources. Resource preference information indicates the preference information of the scheduling domain for resources when performing resource scheduling. For example, from the perspective of cost saving, the scheduling domain has a preference for resources with lower prices.

[0063] Exemplarily, the resource preference information may be in the form of a resource preference rule, which may be received from a terminal device or obtained from a preset database. For any scheduling domain, if the scheduling domain has a preference for lower-priced resources, the resource preference rules of the scheduling domain may be configured according to the preferences of the scheduling domain. The resource preference rules include 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, and a higher priority indicates that the edge cloud node resources in the resource preference rule are more in line with the preference requirements of the scheduling domain.

[0064] Exemplarily, the priority value range of the resource preference rule is set in [0, 999], and the smaller the value, the higher the 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, and the preference priority can take a value that is not a multiple of 3 in the interval [334, 666]; the other part is used for the default configuration of the resource allocation center.

[0065] The resource scheduling priorities corresponding to the multiple edge cloud node resources corresponding to the scheduling domain can be determined by scoring according to the resource preference rule. The higher the score of the resource preference rule corresponding to the edge cloud node resource, the higher the resource scheduling priority of the edge cloud node resource.

[0066] For example, there are 4 resource preference rules configured in area B of the resource pool corresponding to scheduling domain A, and the corresponding priorities are: [5, 23, 45, 323]; the priority of the resource preference rule satisfied by the resource unit cell1 of area B is: [5, 23], and the priority of the resource preference rule satisfied by the resource unit cell2 of area B is: [45, 323]. According to the pre-configured scoring rules, cell1 and cell2 are scored respectively. The score of cell1 is 12 / 15*100=80 points, and the score of cell2 is 20 points. Then the resource scheduling priority of cell1 is higher than that of cell2. Among them, the resource unit is a schedulable resource unit in the resource pool, which is a logical resource object extracted from the edge source node resources.

[0067] In this embodiment, the resource scheduling priority corresponding to the edge cloud node resources is configured. When performing resource scheduling, resources can be scheduled according to the resource scheduling priority, so that the scheduled resources can meet the preferences of the scheduling domain. For example, if the scheduling domain prefers lower-priced resources, scheduling is performed according to the resource scheduling priority, which can improve the utilization rate of low-priced resources and reduce the cost of resource use.

[0068] In a possible implementation, configuring a resource pool corresponding to the scheduling domain according to at least one edge cloud node resource corresponding to the scheduling domain includes:

[0069] Determine the specification information of the resource pool corresponding to the scheduling domain;

[0070] Configure a resource pool corresponding to the scheduling domain according to the specification information and at least one edge cloud node resource.

[0071] In practical applications, from the perspective of the hit rate of resource scheduling, the resource pool is configured with specification information, and the resource pool corresponding to the scheduling domain is configured according to the specification information and the edge cloud node resources that match the scheduling domain. Performing resource scheduling in the resource pool corresponding to the scheduling domain can prevent the traffic of the services in the scheduling domain from flowing arbitrarily on all available resources, resulting in uncontrollable return volume and low hit rate, which increases the resource scheduling cost. Therefore, it is necessary to configure a resource pool for the scheduling domain, which contains matching resources for the scheduling domain. When performing resource scheduling, the flow range of service traffic is limited to the edge cloud node resources in the resource pool, thereby ensuring the hit rate.

[0072] When configuring the resource pool corresponding to the scheduling domain, it is necessary to determine the specification information of the resource pool, consider meeting the needs of the services in the scheduling domain, and reserve redundant resources to meet the fluctuations in service volume. To avoid a sudden increase in service traffic, the newly added edge cloud node resources do not have the cache of the service, which may cause the traffic to return to the source station and require resource scheduling again, increasing the resource scheduling cost. By reserving redundant resources, the configured resource pool can not only carry the current service volume, but also leave enough redundancy. When the service volume suddenly increases, the resource pool still has enough capacity to carry it. Moreover, since redundant resources are always in the resource pool, the cache hit probability is much higher than that of newly added resources, ensuring the stability of the hit rate.

[0073] In this embodiment, the resource pool corresponding to the scheduling domain is configured according to the specification information of the resource pool. When performing resource scheduling, the hit rate of resource scheduling can be increased and the cost of resource scheduling can be reduced.

[0074] How to determine the specification information of the resource pool is specifically described in the following embodiment:

[0075] In a possible implementation, determining specification information of a resource pool corresponding to a scheduling domain includes:

[0076] Obtain the redundant resource amount of the resource pool, the effective area of ​​the resource pool specification configuration, and the resource demand information of the scheduling domain corresponding to the resource pool;

[0077] Determine the specification information of the resource pool based on the amount of redundant resources, the effective area of ​​the specification configuration, and the resource demand information.

[0078] In actual applications, the redundant resource amount of the resource pool, the effective area of ​​the specification configuration 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 obtained from a preset database.

[0079] The coverage requirements of services in the scheduling domain are diverse. Some services need to ensure the coverage of resources in the province, some services need to cover a large area, some need to add all resources of a certain type, and some need to configure redundant resources in a specified area in advance. According to the above different requirements of the service, determine the specification information of the resource pool.

[0080] In one example, the resource pool specification information includes multiple fields: resource pool name, specification type, specification value, applicable area type, and resource requirements. Among them, the specification type refers to the type of service in the scheduling domain, and the amount of redundant resources required for each service is adaptively calculated according to the size of different types of service volumes. The specification value corresponding to the specification type indicates how many times the amount of redundant resources is the amount of service. The amount of redundant resources can be calculated based on the specification type and specification value. The applicable area types may include regional coverage, provincial coverage, and custom areas, etc. Regional coverage means that the specification configuration is effective in each operator region. Provincial coverage means that the specification configuration is effective in each operator province.

[0081] In a possible implementation, configuring a resource pool corresponding to a scheduling domain according to specification information and at least one edge cloud node resource includes:

[0082] According to the specification information, edge cloud node resources are increased or decreased in at least one edge cloud node resource to obtain a resource pool corresponding to the scheduling domain.

[0083] In practical applications, redundant resources can be added to the edge cloud node resources that match the scheduling domain according to the specification information to obtain the resource pool corresponding to the scheduling domain to meet the needs of increased service volume in the scheduling domain. Resources can also be reduced from the edge cloud node resources that match the scheduling domain to obtain the resource pool corresponding to the scheduling domain, which can provide a hit rate for resource scheduling.

[0084] In a possible implementation, the method further includes:

[0085] Update multiple service attribute information, multiple resource attribute information, and multiple matching rules corresponding to multiple scheduling domains according to a preset time period;

[0086] Using the updated multiple service attribute information, multiple resource attribute information, and multiple matching rules, the specifications of the resource pools corresponding to the multiple scheduling domains are verified;

[0087] According to the specification verification result corresponding to the at least one resource pool, it is determined whether to generate a resource adjustment policy for the at least one resource pool.

[0088] In actual applications, the configuration data can be updated regularly according to a preset time period, wherein the configuration data includes multiple service attribute information, multiple resource attribute information, and multiple matching rules corresponding to multiple scheduling domains. The specifications of multiple resource pools are verified using the updated configuration data. If the specifications of one or more resource pools among the multiple resource pools do not match the updated configuration data, a resource adjustment policy for the resource pool is generated. The resource adjustment policy is used to adjust the specifications of the resource pool, for example, to increase or decrease edge cloud node resources in the resource pool.

[0089] In order to facilitate understanding of the technical ideas of the present application, the technical solution of the present application is introduced through two specific embodiments below. Figure 7 A schematic diagram of the design idea of ​​the resource allocation method provided in the embodiment of the present application. In this embodiment, resource allocation is performed through a resource allocation center, and the overall architecture of the resource allocation center is as follows:

[0090] Configuration module: used to configure the service attribute information corresponding to multiple scheduling domains, configure the resource attribute information corresponding to multiple edge cloud node resources, configure the matching rules of multiple scheduling domains and multiple edge cloud node resources, configure the resource scheduling priority of edge cloud node resources in the resource pool, and configure the specification information of the resource pool.

[0091] Indicator quantification layer: used to perceive the usage status of edge cloud node resources, calculate indicators related to resource scheduling costs and quality, and provide users with query and display interfaces. Resource adjustment strategies will also be formulated based on the information in the indicator quantification layer.

[0092] Resource adjustment strategy: Determine the resource adjustment strategy based on the demand information of resource scheduling cost, hit rate, flow control, supply chain, quality, stability, operation and maintenance of the services in the scheduling domain, the indicators provided by the indicator quantification layer, and the resource scheduling priority, and execute the resource adjustment strategy to adjust the edge cloud node resources in the resource pool. For example, adjust the specifications of the resource pool corresponding to any scheduling domain, increase or decrease the edge cloud node resources in the resource pool to meet the needs of the services in the scheduling domain.

[0093] Figure 8 Schematic diagram of the design idea of ​​the resource configuration method provided in the embodiment of the present application. Figure 8 As shown, the specific process includes the following:

[0094] 1. Read configuration information. Use various data loaders to periodically obtain information such as label records, matching rules, resource preference rules, resource pool specifications, etc. of scheduling domains and edge cloud node resources in the database. The database may include information such as label records, matching rules, resource preference rules, resource pool specifications, etc. of scheduling domains and edge cloud node resources, and the data therein may be added, deleted, and modified regularly as needed.

[0095] 2. Resource screening. After obtaining the label records and matching rules of the scheduling domain and edge cloud node resources, the resource screening conditions of each resource pool are determined according to the matching rules, and the resources of each resource pool are screened according to the screening conditions to filter out resources that do not meet the conditions.

[0096] 3. Resource preference scoring. After filtering out the available resources in each resource pool, they will be aggregated by region according to the resource preference rules matched by the resource pool, and then the available resources in each region will be given a preference score.

[0097] 4. Resource pool specification verification. According to the current resource status of each resource pool, compare it with the configured resource pool specification information to verify whether the resource pool specification configuration is met. If it is met, no operation is performed and step 1 is executed. If it is not met, step 5 is executed.

[0098] 5. Trigger resource pool specification adjustment. If the resource pool does not meet the configured resource pool specification information, the resource demand is calculated for each unsatisfied resource pool, and the corresponding resources are obtained from the available resources according to the demand.

[0099] 6. Output resource adjustment strategy. According to the calculation results in step 5, generate a resource pool adjustment strategy, execute the resource adjustment strategy in the database DB, adjust the specifications of the resource pool, and execute step 1.

[0100] The embodiment of the present application provides a resource scheduling method for edge cloud. The method in this embodiment can be applied to a computing device, which may include: a server, a user terminal, etc. Fig. 9 The flowchart of the resource scheduling method for edge cloud according to an embodiment of the present application may include:

[0101] Step S901: In response to a resource scheduling request, determine a scheduling domain corresponding to the resource scheduling request.

[0102] Step S902: Schedule edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain.

[0103] In this embodiment, the server is used as the execution subject for introduction. After receiving the resource scheduling request, the server parses the resource scheduling request, determines the scheduling domain corresponding to the resource scheduling request according to the parsing result, and schedules the edge cloud node resources for the scheduling domain in the resource pool corresponding to the scheduling domain. Among them, the resource pool is configured for the scheduling domain using the resource configuration method for edge cloud in any embodiment of the present application. The specific configuration process is shown in the above embodiment, which will not be repeated here.

[0104] In this embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted as a matching rule. The resource pool corresponding to the scheduling domain is configured according to multiple service attribute information, multiple resource attribute information, and multiple matching rules, thereby reducing the workload of manual resource configuration and improving resource configuration efficiency. When performing resource scheduling, scheduling is performed directly in the resource pool corresponding to the configured scheduling domain. There is no need to develop a new scheduling strategy for the scheduling domain, thus saving development costs.

[0105] In a possible implementation, a scheduling domain corresponds to a plurality of edge cloud node resources; scheduling edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain includes:

[0106] Based on the resource scheduling priorities respectively corresponding to the multiple edge cloud node resources, the edge cloud node resources are scheduled for the scheduling domain in the resource pool.

[0107] In practical applications, edge cloud node resources are scheduled for a scheduling domain according to resource scheduling priorities. Resource scheduling priorities are determined based on resource preference information corresponding to the scheduling domain.

[0108] Exemplarily, the resource preference information may be in the form of a resource preference rule, which may be received from a terminal device or obtained from a preset database. For any scheduling domain, if the scheduling domain has a preference for lower-priced resources, the resource preference rules of the scheduling domain may be configured according to the preferences of the scheduling domain. The resource preference rules include 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, and a higher priority indicates that the edge cloud node resources in the resource preference rule are more in line with the preference requirements of the scheduling domain.

[0109] The resource scheduling priorities corresponding to the multiple edge cloud node resources corresponding to the scheduling domain can be determined by scoring according to the resource preference rule. The higher the score of the resource preference rule corresponding to the edge cloud node resource, the higher the resource scheduling priority of the edge cloud node resource.

[0110] In this embodiment, resources are scheduled according to resource scheduling priorities, so that the scheduled resources meet the preferences of the scheduling domain. For example, if the scheduling domain prefers lower-priced resources, scheduling according to resource scheduling priorities can improve the utilization rate of low-priced resources and reduce the cost of resource use.

[0111] Corresponding to the application scenario and method of the method provided in the embodiment of the present application, the embodiment of the present application also provides a resource configuration device for edge cloud. Fig.10 The structure diagram of a resource configuration device for edge cloud according to an embodiment of the present application is shown. The resource configuration device for edge cloud may include:

[0112] The information acquisition module 1001 is used to obtain service attribute information corresponding to multiple scheduling domains, resource attribute information corresponding to multiple edge cloud node resources, and matching rules between multiple scheduling domains and multiple edge cloud node resources; the scheduling domain includes at least one service;

[0113] The first configuration module 1002 is used to configure at least one edge cloud node resource corresponding to each of the multiple scheduling domains according to multiple service attribute information, multiple resource attribute information, and multiple matching rules;

[0114] The second configuration module 1003 is used to configure 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 to schedule resources for the scheduling domain.

[0115] In this embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted as a matching rule. The resource pool corresponding to the scheduling domain is configured according to multiple service attribute information, multiple resource attribute information, and multiple matching rules, thereby reducing the workload of manual resource configuration and improving resource configuration efficiency. When performing resource scheduling, scheduling is performed directly in the resource pool corresponding to the configured scheduling domain. There is no need to develop a new scheduling strategy for the scheduling domain, thus saving development costs.

[0116] In a possible implementation, the scheduling domain corresponds to a plurality of edge cloud node resources, and the apparatus further includes a priority determination module, which is used to:

[0117] Based on the resource preference information corresponding to the scheduling domain, the resource scheduling priorities corresponding to the multiple edge cloud node resources corresponding to the scheduling domain are determined.

[0118] In a possible implementation, the second configuration module 1003 is configured to:

[0119] Determine the specification information of the resource pool corresponding to the scheduling domain;

[0120] Configure a resource pool corresponding to the scheduling domain according to the specification information and at least one edge cloud node resource.

[0121] In a possible implementation, when determining the specification information of the resource pool corresponding to the scheduling domain, the second configuration module 1003 is used to:

[0122] Obtain the redundant resource amount of the resource pool, the effective area of ​​the resource pool specification configuration, and the resource demand information of the scheduling domain corresponding to the resource pool;

[0123] Determine the specification information of the resource pool based on the amount of redundant resources, the effective area of ​​the specification configuration, and the resource demand information.

[0124] In a possible implementation, the second configuration module 1003 is configured to:

[0125] According to the specification information, edge cloud node resources are increased or decreased in at least one edge cloud node resource to obtain a resource pool corresponding to the scheduling domain.

[0126] In a possible implementation, the device further includes a verification module, which is used to:

[0127] Update multiple service attribute information, multiple resource attribute information, and multiple matching rules corresponding to multiple scheduling domains according to a preset time period;

[0128] Using the updated multiple service attribute information, multiple resource attribute information, and multiple matching rules, the specifications of the resource pools corresponding to the multiple scheduling domains are verified;

[0129] According to the specification verification result corresponding to the at least one resource pool, it is determined whether to generate a resource adjustment policy for the at least one resource pool.

[0130] In a possible implementation, the matching rule includes a demand expression corresponding to the service attribute information and a demand expression corresponding to the resource attribute information, and the matching rule is used to characterize the scheduling domain's demand for the use of edge cloud node resources.

[0131] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and have corresponding beneficial effects, which will not be repeated here.

[0132] Corresponding to the application scenario and method of the method provided in the embodiment of the present application, the embodiment of the present application also provides a resource scheduling device for edge cloud. Fig.11 The structure diagram of a resource scheduling device for edge cloud according to an embodiment of the present application is shown. The resource scheduling device for edge cloud may include:

[0133] The request response module 1101 is used to respond to the resource scheduling request and determine the scheduling domain corresponding to the resource scheduling request;

[0134] 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;

[0135] Among them, the resource pool is configured for the scheduling domain according to the method of any embodiment of the present application.

[0136] In this embodiment, the association relationship between the scheduling domain and the edge cloud node resources is abstracted as a matching rule. The resource pool corresponding to the scheduling domain is configured according to multiple service attribute information, multiple resource attribute information, and multiple matching rules, thereby reducing the workload of manual resource configuration and improving resource configuration efficiency. When performing resource scheduling, scheduling is performed directly in the resource pool corresponding to the configured scheduling domain. There is no need to develop a new scheduling strategy for the scheduling domain, thus saving development costs.

[0137] In a possible implementation, the resource scheduling module 1102 is specifically configured to:

[0138] Based on the resource scheduling priorities respectively corresponding to the multiple edge cloud node resources, the edge cloud node resources are scheduled for the scheduling domain in the resource pool.

[0139] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and have corresponding beneficial effects, which will not be repeated here.

[0140] Fig.12 FIG. 1 is a block diagram of an electronic device used to implement an embodiment of the present application. Fig.12 As shown, the electronic device includes: a memory 1210 and a processor 1220. The memory 1210 stores a computer program that can be run on the processor 1220. When the processor 1220 executes the computer program, the method in the above embodiment is implemented. The number of the memory 1210 and the processor 1220 can be one or more.

[0141] The electronic device also includes:

[0142] The communication interface 1230 is used to communicate with external devices and perform data exchange transmission.

[0143] If the memory 1210, the processor 1220 and the communication interface 1230 are implemented independently, the memory 1210, the processor 1220 and the communication interface 1230 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.12 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0144] Optionally, 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 can communicate with each other through an internal interface.

[0145] An embodiment of the present application provides a computer-readable storage medium storing a computer program, which implements the method provided in the embodiment of the present application when the program is executed by a processor.

[0146] An embodiment of the present application also provides a chip, which includes a processor for calling and executing instructions stored in the memory from the memory, so that a communication device equipped with the chip executes the method provided by the embodiment of the present application.

[0147] An embodiment of the present application also provides a chip, including: 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 via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the application.

[0148] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting the Advanced RISC Machines (ARM) architecture.

[0149] Further, optionally, the above-mentioned memory may include a read-only memory and a random access memory. The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may include a random access memory (RAM), which is used as an external cache. By way of exemplary but not limiting description, many forms of RAM are available. For example, static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DR RAM).

[0150] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can 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 process or function according to the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.

[0151] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.

[0152] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0153] Any process or method described in the flow chart or otherwise described herein can be understood as a module, fragment or portion of a code representing one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.

[0154] The logic and / or steps described in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or used in combination with these instruction execution systems, devices or apparatuses.

[0155] It should be understood that the various parts of the present application can be implemented with hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented with software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium, and when the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0156] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a disk or an optical disk, etc.

[0157] The above is only an exemplary embodiment of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope recorded in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A resource configuration method for edge cloud, characterized in that: The method comprises: Obtain service attribute information corresponding to a plurality of scheduling domains, resource attribute information corresponding to a plurality of edge cloud node resources, and matching rules between the plurality of scheduling domains and the plurality of edge cloud node resources; the scheduling domain includes at least one service; According to the plurality of service attribute information, the plurality of resource attribute information, and the plurality of matching rules, configure at least one edge cloud node resource corresponding to each of the plurality of scheduling domains; According to at least one edge cloud node resource corresponding to the scheduling domain, a resource pool corresponding to the scheduling domain is configured, and the resource pool is used to schedule resources for the scheduling domain; wherein, according to at least one edge cloud node resource corresponding to the scheduling domain, the resource pool corresponding to the scheduling domain is configured, including: 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 includes: obtaining the redundant resource amount of the resource pool, the effective area of ​​the specification configuration of the resource pool, and the resource demand information of the scheduling domain corresponding to the resource pool; determining the specification information of the resource pool according to the redundant resource amount, the effective area of ​​the specification configuration, and the resource demand information.

2. The method according to claim 1, characterized in that The scheduling domain corresponds to a plurality of edge cloud node resources, and the method further includes: Based on the resource preference information corresponding to the scheduling domain, the resource scheduling priorities respectively corresponding to the multiple edge cloud node resources corresponding to the scheduling domain are determined.

3. The method according to claim 1, characterized in that The configuring, according to the specification information and the at least one edge cloud node resource, a resource pool corresponding to the scheduling domain includes: According to the specification information, edge cloud node resources are added or reduced in the at least one edge cloud node resource to obtain a resource pool corresponding to the scheduling domain.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Update the plurality of service attribute information, the plurality of resource attribute information, and the plurality of matching rules respectively corresponding to the plurality of scheduling domains according to a preset time period; Verify the specifications of the resource pools respectively corresponding to the plurality of scheduling domains by using the updated plurality of service attribute information, the plurality of resource attribute information and the plurality of matching rules; According to a specification verification result corresponding to at least one resource pool, it is determined whether to generate a resource adjustment policy for the at least one resource pool.

5. The method according to any one of claims 1 to 3, characterized in that: The matching rule includes a demand expression corresponding to the service attribute information and a demand expression corresponding to the resource attribute information, and the matching rule is used to characterize the scheduling domain's demand for the use of the edge cloud node resources.

6. A resource scheduling method for edge cloud, characterized in that: The method comprises: In response to a resource scheduling request, 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; The resource pool is configured for the scheduling domain according to the method described in any one of claims 1-5.

7. The method according to claim 6, characterized in that The scheduling domain corresponds to a plurality of edge cloud node resources; and scheduling edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain includes: Based on the resource scheduling priorities respectively corresponding to the multiple edge cloud node resources, edge cloud node resources are scheduled for the scheduling domain in the resource pool.

8. A resource configuration device for edge cloud, characterized in that: include: An information acquisition module, used to acquire service attribute information corresponding to a plurality of scheduling domains, resource attribute information corresponding to a plurality of edge cloud node resources, and matching rules between the plurality of scheduling domains and the plurality of edge cloud node resources; the scheduling domain includes at least one service; A first configuration module is used to configure at least one edge cloud node resource corresponding to each of the plurality of scheduling domains according to a plurality of service attribute information, a plurality of resource attribute information, and a plurality of matching rules; The second configuration module is used to configure the 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 to schedule resources for the scheduling domain; wherein the second configuration module is also used to: determine the specification information of the resource pool corresponding to the scheduling domain; configure the resource pool corresponding to the scheduling domain according to the specification information and the at least one edge cloud node resource; the determination of the specification information of the resource pool corresponding to the scheduling domain includes: obtaining the redundant resource amount of the resource pool, the effective area of ​​the specification configuration of the resource pool and the resource demand information of the scheduling domain corresponding to the resource pool; determine the specification information of the resource pool according to the redundant resource amount, the effective area of ​​the specification configuration and the resource demand information.

9. A resource scheduling device for edge cloud, characterized in that: include: A request response module, configured to respond to a resource scheduling request and determine a scheduling domain corresponding to the resource scheduling request; A resource scheduling module, configured to schedule edge cloud node resources for the scheduling domain in a resource pool corresponding to the scheduling domain; The resource pool is configured for the scheduling domain according to the method described in any one of claims 1-5.

10. An electronic device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory, wherein the processor implements the method according to any one of claims 1 to 7 when executing the computer program.

Images