Cloud resource allocation method, device, medium and product

CN122802455APending Publication Date: 2026-09-22ZHEJIANG GEELY HLDG GRP CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610982698.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-02
Publication Date
2026-09-22

AI Technical Summary

Technical Problem

[0005]有鉴于此,本申请致力于提供一种云端资源的分配方法、设备、介质及产品,以解决传统相关技术中云端资源分配不合理的问题

Benefits of technology

[0017]本申请提供的云端资源的分配方法、设备、介质及产品,该方法中,确定各终端群体的初始资源分配比例;实时监测各终端群体的群体规模的变化事件;根据变化事件,调整各终端群体的初始资源分配比例,得到目标资源分配比例;基于目标资源分配比例,将云端资源分配给各终端群体。通过将资源分配比例与群体规模的变化事件进行关联,能够在监测到各终端群体的群体规模的变化事件时,自动调整各终端群体对应的资源分配比例,而非维持固定的资源分配比例,实现了云端资源在不同终端群体间的合理化分配。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122802455A_ABST
    Figure CN122802455A_ABST
Patent Text Reader

Abstract

The application provides a cloud resource allocation method, device, medium and product. The method comprises the following steps: determining initial resource allocation ratios of terminal groups; monitoring changes of group sizes of the terminal groups in real time; adjusting the initial resource allocation ratios of the terminal groups according to the changes to obtain target resource allocation ratios; and allocating cloud resources to the terminal groups based on the target resource allocation ratios. Through the method, the rationality of cloud resource allocation is realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, specifically to a method, device, medium, and product for allocating cloud resources. Background Technology

[0002] With the rapid development of vehicle-to-everything (V2X) technology, deploying terminal applications in the cloud has become an inevitable trend. The integrated vehicle-cloud cluster environment needs to provide shared cloud resources for different terminal groups. In this scenario, achieving the rational allocation of cloud resources among multiple terminal groups is a pressing issue that needs to be addressed.

[0003] Currently, in order to achieve the allocation of cloud resources among different terminal groups, a static resource allocation ratio is usually set for each terminal group.

[0004] However, due to the static nature of its mechanism, this fixed allocation strategy suffers from the problem of unreasonable allocation of cloud resources. Summary of the Invention

[0005] In view of this, this application aims to provide a method, device, medium and product for allocating cloud resources, so as to solve the problem of unreasonable allocation of cloud resources in traditional related technologies.

[0006] The first aspect of this application provides a method for allocating cloud resources, including: determining the initial resource allocation ratio for each terminal group; monitoring changes in the group size of each terminal group in real time; adjusting the initial resource allocation ratio for each terminal group based on the changes to obtain a target resource allocation ratio; and allocating cloud resources to each terminal group based on the target resource allocation ratio.

[0007] In one possible implementation of this application, adjusting the initial resource allocation ratio of each terminal group according to a change event to obtain a target resource allocation ratio includes: if the change event is that the group size of each terminal group increases simultaneously, then acquiring the business activity data of the target terminal application; adjusting the initial resource allocation ratio of each terminal group according to the business activity data to obtain the target resource allocation ratio; if the change event is that the group size of any terminal group decreases while the group size of the remaining terminal groups remains unchanged, or the group size of any terminal group increases while the group size of the remaining terminal groups remains unchanged, then adjusting the initial resource allocation ratio of each terminal group according to the current group size of each terminal group to obtain the target resource allocation ratio.

[0008] In one possible implementation of this application, adjusting the initial resource allocation ratio of each terminal group based on business activity data to obtain a target resource allocation ratio includes: extracting multiple business activity features from the business activity data; and adjusting the initial resource allocation ratio of each terminal group based on the multiple business activity features to obtain a target resource allocation ratio.

[0009] In one possible implementation of this application, multiple business activity characteristics include operational activity intensity, target terminal volume, group size of each terminal group within a preset time period, and historical activity conversion rate. Accordingly, based on these multiple business activity characteristics, the initial resource allocation ratio for each terminal group is adjusted to obtain the target resource allocation ratio. This includes: constructing an input sequence by arranging the operational activity intensity, target terminal volume, group size of each terminal group within a preset time period, and historical activity conversion rate in chronological order; and inputting the input sequence into a pre-built resource ratio prediction model, so that the pre-built resource ratio prediction model outputs the target resource allocation ratio based on the input sequence.

[0010] In one possible implementation of this application, the terminal group includes a newly registered terminal group and a registered terminal group. Accordingly, based on business activity data, the initial resource allocation ratio of each terminal group is adjusted to obtain a target resource allocation ratio, including: obtaining an operational objective from the business activity data; when the operational objective focuses on increasing the scale of the newly registered terminal group, the initial resource allocation ratio of the registered terminal group is reduced by half to obtain a target resource allocation ratio for the registered terminal group; and the reduced portion of the initial resource allocation ratio of the registered terminal group is added to the initial resource allocation ratio of the newly registered terminal group to obtain a target resource allocation ratio for the newly registered terminal group; when the operational objective focuses on increasing the recall scale of the registered terminal group, the initial resource allocation ratio of the newly registered terminal group is reduced by half to obtain a target resource allocation ratio for the newly registered terminal group; and the reduced portion of the initial resource allocation ratio of the newly registered terminal group is added to the initial resource allocation ratio of the registered terminal group to obtain a target resource allocation ratio for the registered terminal group.

[0011] In one possible implementation of this application, the terminal group includes two types of terminal groups; accordingly, based on the target resource allocation ratio, cloud resources are allocated to each terminal group, including: dividing the cloud resources into an ordered resource sequence; allocating the resource area corresponding to the beginning of the resource sequence to one type of terminal group according to the target resource allocation ratio; and allocating the resource area corresponding to the end of the resource sequence to the other type of terminal group.

[0012] In one possible implementation of this application, determining the initial resource allocation ratio for each terminal group includes: obtaining the total size of multiple terminal groups; and for each terminal group, determining the ratio of the current terminal group's size to the total group size as the initial resource allocation ratio for each terminal group.

[0013] In one possible implementation of this application, the terminal group includes a newly registered terminal group and an already registered terminal group; the size of the newly registered terminal group is the average daily registration volume, and the size of the already registered terminal group is the average daily active volume.

[0014] A second aspect of this application provides an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform a cloud resource allocation method as described in the first aspect and possible implementations thereof.

[0015] A third aspect of this application provides a computer storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement a cloud resource allocation method as described in the first aspect and possible implementations thereof.

[0016] The fourth aspect of this application provides a computer program product, comprising: a computer program that, when executed by a processor, implements a cloud resource allocation method as described in the first aspect and possible implementations of the first aspect.

[0017] This application provides a cloud resource allocation method, device, medium, and product. The method involves determining the initial resource allocation ratio for each terminal group; monitoring real-time changes in the group size of each terminal group; adjusting the initial resource allocation ratio for each terminal group based on the changes to obtain a target resource allocation ratio; and allocating cloud resources to each terminal group based on the target resource allocation ratio. By correlating the resource allocation ratio with changes in group size, the method automatically adjusts the resource allocation ratio for each terminal group upon detecting changes in their group size, rather than maintaining a fixed ratio, thus achieving a rational allocation of cloud resources among different terminal groups. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the specific embodiments or related technologies of this application, the drawings used in the description of the specific embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram illustrating an application scenario of the cloud resource allocation method provided in the embodiments of this application.

[0020] Figure 2A flowchart illustrating the cloud resource allocation method provided in this application embodiment. Figure 1 .

[0021] Figure 3 A flowchart illustrating the cloud resource allocation method provided in this application embodiment. Figure 2 .

[0022] Figure 4 This is a schematic diagram of the structure of the cloud resource allocation device provided in the embodiments of this application.

[0023] Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] In the field of cloud resource allocation, especially in scenarios involving multiple terminal groups sharing the same cloud resources, a commonly used technical solution to achieve the rational utilization of resources such as computing, storage, or network connectivity is static resource quota allocation. Specifically, this involves pre-setting a fixed percentage of cloud resources for each terminal group, for example, allocating a 60% resource cap for terminal group A and a 40% resource cap for terminal group B, as the basic basis for cloud resource scheduling.

[0026] However, this solution performs poorly when applied to terminal groups with dynamically changing group sizes and shared cloud resources among these groups. Static quota mechanisms, designed for management certainty and simplicity, have fixed allocation boundaries that cannot keep pace with real-time changes in the external environment and the composition of the terminal group, resulting in unreasonable resource allocation.

[0027] To address the aforementioned technical problems, this application proposes the following technical concept: constructing a dynamic correlation mechanism between resource allocation ratios and changes in the group size of terminal groups. By monitoring changes in the group size of each terminal group in real time, adjustments to the resource allocation ratio are triggered, ultimately obtaining and allocating cloud resources to each terminal group according to the target resource allocation ratio. This achieves the technical effect of rationally allocating cloud resources based on changes in group size among different terminal groups.

[0028] Figure 1 This is a schematic diagram illustrating an application scenario of the cloud resource allocation method provided in an embodiment of this application. (See reference...) Figure 1This scenario includes: a newly registered terminal group 101, a group of already registered terminals 102, and electronic devices 103.

[0029] In this embodiment, the terminal group includes a newly registered terminal group 101 and a registered terminal group 102. The newly registered terminal group 101 includes multiple newly registered terminals, and the registered terminal group 102 includes multiple registered terminals.

[0030] In this embodiment, the electronic device 103 determines the initial resource allocation ratio of each terminal group; monitors in real time the change events of the group size of the newly registered terminal group 101 and the change events of the group size of the already registered terminal group 102; adjusts the initial resource allocation ratio of each terminal group according to the change events to obtain the target resource allocation ratio; and allocates cloud resources to the newly registered terminal group 101 and the already registered terminal group 102 based on the target resource allocation ratio.

[0031] Figure 2 A flowchart illustrating the cloud resource allocation method provided in this application embodiment. Figure 1 The execution entity in this embodiment can be... Figure 1 The electronic device in the illustrated embodiment. (As shown) Figure 2 As shown, the method includes: S201: Determine the initial resource allocation ratio for each terminal group.

[0032] Specifically, the total size of multiple terminal groups is obtained; for each terminal group, the proportion of the current terminal group's size to the total size is determined as the initial resource allocation ratio for each terminal group.

[0033] In this embodiment, the terminal group includes newly registered terminal group and already registered terminal group; the group size of the newly registered terminal group is the average daily registration volume, and the group size of the already registered terminal group is the average daily active volume.

[0034] In this embodiment, during the initial operation of the cloud resource scheduling system, or after a cloud resource reset, an initial allocation benchmark needs to be set for each group of terminals accessing cloud resources. The initial resource allocation ratio reflects a basic judgment by the cloud resource scheduling system on the share of cloud resources that each group of terminals should enjoy before any disturbances occur due to changes in group size.

[0035] In this embodiment, the group size of newly registered terminals and the group size of already registered terminals are obtained, and their sum is taken as the total group size. Then, the proportion of the newly registered terminal group's size to the total group size is determined as the initial resource allocation ratio for the newly registered terminal group; correspondingly, the proportion of the already registered terminal group's size to the total group size is determined as the initial resource allocation ratio for the already registered terminal group. Using this method, an objective starting point can be established that is linked in real-time with the group size of each terminal group.

[0036] For example, the average daily registration volume of the newly registered terminal group is 200, the average daily activity of the registered terminal group is 10,000, and the total group size is 10,200. The initial resource allocation ratio for the newly registered terminal group is 200 / 10,200, and the initial resource allocation ratio for the registered terminal group is 10,000 / 10,200.

[0037] For example, if the concurrency of cloud resources is 3000, then the cloud resources allocated to the newly registered terminal group are 3000×200 / 10200, and the cloud resources allocated to the already registered terminal group are 3000×10000 / 10200.

[0038] Alternatively, a fixed initial resource allocation ratio can be pre-set for each terminal group.

[0039] S202: Real-time monitoring of changes in the group size of each terminal group.

[0040] In this embodiment, during the process of each terminal group using cloud resources, it is necessary to continuously sense the dynamic increase or decrease in the group size of each terminal group.

[0041] In this embodiment, real-time monitoring of changes in group size can specifically involve periodically calculating the average daily registration volume of newly registered terminals and the average daily activity volume of already registered terminals. When the average daily registration volume or average daily activity volume for any given statistical period changes by more than a preset trigger threshold (e.g., 10%) relative to the baseline value of one or more previous statistical periods, a change event is determined to have occurred. For example, in a vehicle-cloud service scenario, if an operational activity causes the average daily registration volume of newly registered terminals to surge from 100 to 500, this would capture a change event indicating an increase in the group size of newly registered terminals. This approach filters out random noise, ensuring that adjustments are triggered only by meaningful trend changes, thus avoiding instability caused by frequent fine-tuning of the system.

[0042] Alternatively, monitoring changes in group size can be achieved in various ways. For example, including but not limited to: near real-time event-driven methods based on message queues, batch comparative analysis based on sliding time windows, and streaming computation based on embedded logs, all of which can capture dynamic group size.

[0043] S203: Based on the changing events, adjust the initial resource allocation ratio of each terminal group to obtain the target resource allocation ratio.

[0044] In this embodiment, when a change in the size of a group is detected, an adjustment process is triggered. The core objective of this process is to generate a resource allocation ratio that is adapted to the current group size, in order to replace the initial resource allocation ratio.

[0045] In this embodiment, if the change event is caused by the operational activities of the target terminal application, resulting in a simultaneous increase in the group size of each terminal group, then the business activity data of the target terminal application will be acquired. Based on the business activity data, the initial resource allocation ratio will be adjusted to generate a target resource allocation ratio, thereby tilting cloud resources towards the operational target. If the change event is caused by the natural shrinkage of the group size of any terminal group, then the target resource allocation ratio will be recalculated and generated based on the current group size of each terminal group, realizing the recovery and reallocation of redundant resources. This scenario-based adjustment method can ensure critical business operations when global resource demand is high, and prevent idle resources from being ineffectively occupied when local demand is weak.

[0046] Specifically, step S203 includes S2031~S2032: S2031: If the change event is that the group size of each terminal group increases simultaneously, then obtain the business activity data of the target terminal application; based on the business activity data, adjust the initial resource allocation ratio of each terminal group to obtain the target resource allocation ratio.

[0047] In this embodiment, the simultaneous increase in the group size of each terminal group can lead to insufficient cloud resources and queuing, requiring the allocation of cloud resources according to operational goals.

[0048] Specifically, multiple business activity features are extracted from the business activity data; based on these features, the initial resource allocation ratio for each terminal group is adjusted to obtain the target resource allocation ratio.

[0049] In this embodiment, business activity data is further processed into structured business activity features, aiming to transform vague operational objectives into quantitative inputs that can be understood and calculated by machines.

[0050] In this embodiment, raw business activity data related to current operational activities and terminal behavior is retrieved from the business database, including operational plan data, time-series data, and historical conversion data. The business activity data is then cleaned, removing null values ​​and outliers.

[0051] In this embodiment, structured features for resource ratio adjustment are screened and extracted from the above-mentioned business activity data, specifically including: operational activity intensity, target terminal volume, scale of newly registered terminal group within a preset time, scale of already registered terminal group within a preset time, and historical activity conversion rate.

[0052] The preset time can be 1, 3, 5, 7, 10, or 14 days in advance.

[0053] Among them, the intensity of the operation activities refers to activities such as new user acquisition and recall of registered terminals. An intensity of 1 means that there are no regular operation activities. The target user volume refers to the number of terminals that the operation activities are planned to target. The historical activity conversion rate refers to the terminal conversion brought about by the operation activities, such as a 15% conversion rate for regular registrations and a 20% conversion rate for registrations through operation activities.

[0054] In this embodiment, multiple business activity characteristics include the intensity of operational activities, the target number of terminals, the group size of each terminal group within a preset time period, and the historical activity conversion rate.

[0055] Specifically, the intensity of operational activities, the target number of terminals, the group size of each terminal group within a preset time period, and the historical activity conversion rate are constructed into an input sequence in chronological order. The input sequence is then input into a pre-built resource ratio prediction model, which outputs the target resource allocation ratio based on the input sequence.

[0056] In this embodiment, the adjustment process does not rely on a fixed mathematical formula, but rather utilizes a resource allocation prediction model that has learned from historical allocation data patterns. This model is pre-trained to automatically characterize the complex mapping function between multidimensional features and resource allocation ratios.

[0057] In this embodiment, multiple business activity features are arranged in chronological order to construct an input sequence that adapts to a pre-built resource ratio prediction model.

[0058] In this embodiment, the completed input sequence is input into a pre-built resource ratio prediction model; the pre-built resource ratio prediction model learns the correlation between the characteristics of each business activity and the resource allocation ratio, and outputs the target resource allocation ratio.

[0059] In this embodiment, the pre-constructed resource ratio prediction model is a long short-term memory network model.

[0060] In this embodiment, the construction process of the pre-built resource ratio prediction model is as follows: relying on historical business activity data, the historically predetermined resource allocation ratio is used as the model training label (target value), and the intensity of operational activities, the number of target terminals, the group size of each terminal group within a preset time period, and the historical activity conversion rate are used as input features to back-train and fit the long short-term memory network model; after training, multiple business activity features can be input in real time to automatically generate a resource allocation ratio that is suitable for the current scenario.

[0061] Optionally, if the change event is a simultaneous increase in the size of each terminal group, the target resource allocation ratio can also be obtained in the following way. Here, the terminal groups include newly registered terminal groups and already registered terminal groups.

[0062] Specifically, operational goals are obtained from business activity data. When the operational goal is to increase the scale of the newly registered terminal group, the initial resource allocation ratio of the already registered terminal group is reduced by half to obtain the target resource allocation ratio of the already registered terminal group. The reduced portion of the initial resource allocation ratio of the already registered terminal group is then added to the initial resource allocation ratio of the newly registered terminal group to obtain the target resource allocation ratio of the newly registered terminal group. When the operational goal is to increase the recall scale of the already registered terminal group, the initial resource allocation ratio of the newly registered terminal group is reduced by half to obtain the target resource allocation ratio of the newly registered terminal group. The reduced portion of the initial resource allocation ratio of the newly registered terminal group is then added to the initial resource allocation ratio of the already registered terminal group to obtain the target resource allocation ratio of the already registered terminal group.

[0063] For example, the initial resource allocation ratio for newly registered terminal groups is 40%, and the initial resource allocation ratio for already registered terminal groups is 60%.

[0064] For example, when the operational objective is to focus on increasing the size of the newly registered terminal group, the initial resource allocation ratio of the already registered terminal group is reduced to 30%, resulting in a target resource allocation ratio of 30% for the already registered terminal group; and the 30% reduction in the initial resource allocation ratio of the already registered terminal group is added to the initial resource allocation ratio of the newly registered terminal group, resulting in a target resource allocation ratio of 70% for the newly registered terminal group.

[0065] For example, when the operational objective is to focus on increasing the recall scale of the registered terminal group, the initial resource allocation ratio of the newly registered terminal group is reduced to 20%, resulting in a target resource allocation ratio of 20% for the newly registered terminal group; and the 20% reduction in the initial resource allocation ratio of the newly registered terminal group is added to the initial resource allocation ratio of the registered terminal group, resulting in a target resource allocation ratio of 80% for the registered terminal group.

[0066] S2032: If the change event is that the group size of any terminal group decreases while the group size of the remaining terminal groups remains unchanged, or the group size of any terminal group increases while the group size of the remaining terminal groups remains unchanged, then the initial resource allocation ratio of each terminal group is adjusted according to the current group size of each terminal group to obtain the target resource allocation ratio.

[0067] In this embodiment, if the change event is a decrease in the size of any terminal group while the size of the remaining terminal groups remains unchanged, or an increase in the size of any terminal group while the size of the remaining terminal groups remains unchanged, the current resource allocation ratio is recalculated. The target resource allocation ratio for any terminal group = current group size ÷ current total group size. A decrease in the size of a newly registered terminal group → a decrease in the resource allocation ratio corresponding to the newly registered terminal group → cloud resources automatically shift towards the registered terminal group; a decrease in the size of an already registered terminal group → a decrease in the resource allocation ratio corresponding to the already registered terminal group → cloud resources automatically shift towards the newly registered terminal group.

[0068] S204: Based on the target resource allocation ratio, allocate cloud resources to each terminal group.

[0069] As described above, the process involves determining the initial resource allocation ratio for each terminal group; monitoring changes in the group size of each terminal group in real time; adjusting the initial resource allocation ratio based on these changes to obtain the target resource allocation ratio; and allocating cloud resources to each terminal group based on the target resource allocation ratio. By linking the resource allocation ratio to changes in group size, the system can automatically adjust the resource allocation ratio for each terminal group when changes in group size are detected, rather than maintaining a fixed ratio, thus achieving a rational allocation of cloud resources among different terminal groups.

[0070] refer to Figure 3 , Figure 3 A flowchart illustrating the cloud resource allocation method provided in this application embodiment. Figure 2 Based on the above embodiments, this embodiment describes the specific process of allocating cloud resources to various terminal groups, as detailed below: S301: Divide cloud resources into an ordered resource sequence.

[0071] In this embodiment, the terminal group includes two types of terminal groups.

[0072] In this embodiment, cloud resources provide schedulable virtual resources such as concurrent connections, computing power, and bandwidth, with a fixed total amount of resources. The cloud resources are uniformly numbered and arranged in order to form an ordered resource sequence, for example, labeled as virtual resource bits 1, 2, 3...N. The resource sequence is continuous without gaps, representing all available resources that the cloud can provide.

[0073] S302: According to the target resource allocation ratio, allocate the resource area corresponding to the beginning of the resource sequence to one type of terminal group; allocate the resource area corresponding to the end of the resource sequence to another type of terminal group.

[0074] In this embodiment, based on the target resource allocation ratio, the number of resource bits that each of the two types of terminal groups should occupy is calculated; from the beginning of the resource sequence (the first position), a corresponding number of consecutive resource bits, i.e., the corresponding resource area, are extracted and allocated to one type of terminal group; from the end of the resource sequence (counting backwards from the last position), a corresponding number of consecutive resource bits, i.e., the corresponding resource area, are extracted and allocated to the other type of terminal group.

[0075] In this embodiment, the two types of terminal groups are newly registered terminal groups and already registered terminal groups. If a resource region corresponding to the beginning of the resource sequence is allocated to the newly registered terminal group, then a resource region corresponding to the end of the resource sequence is allocated to the already registered terminal group; conversely, if a resource region corresponding to the beginning of the resource sequence is allocated to the already registered terminal group, then a resource region corresponding to the end of the resource sequence is allocated to the newly registered terminal group.

[0076] For example, if N=3000, the target resource allocation ratio for the newly registered terminal group is 6%, then the number of resource slots to be occupied is 180. If the target resource allocation ratio for the already registered terminal group is 94%, then the number of resource slots to be occupied is 2820. In this case, starting from the first virtual resource slot at the beginning of the resource sequence, resource slots 1-180 are allocated to the newly registered terminal group. Starting from the 3000th virtual resource slot at the end of the resource sequence, resource slots 181-3000 are allocated to the already registered terminal group.

[0077] As described above, cloud resources are divided into ordered resource sequences. According to the target resource allocation ratio, the resource area corresponding to the beginning of the sequence is allocated to one type of terminal group, and the resource area corresponding to the end of the sequence is allocated to another type of terminal group. By defining cloud resources as ordered sequences and stipulating that different terminal groups occupy resources from the beginning and end of the sequence respectively, the resource areas available to the two types of terminal groups are physically isolated. This solves the resource conflict and cross-occupancy problems that may occur during resource sharing, achieving orderliness and clarity in resource allocation, avoiding direct competition for the same resources between different terminal groups, and further realizing the rationality of cloud resource allocation.

[0078] Figure 4 This is a schematic diagram of the structure of a cloud resource allocation device provided in an embodiment of this application. Figure 4 As shown, the cloud resource allocation device is applied to an electronic device and includes: a determination module 401, a monitoring module 402, an adjustment module 403, and an allocation module 404.

[0079] The determination module 401 is used to determine the initial resource allocation ratio for each terminal group.

[0080] Monitoring module 402 monitors changes in the group size of each terminal group in real time.

[0081] The adjustment module 403 is used to adjust the initial resource allocation ratio of each terminal group according to the change event to obtain the target resource allocation ratio.

[0082] The allocation module 404 is used to allocate cloud resources to various terminal groups based on the target resource allocation ratio.

[0083] In one possible implementation of this application, the adjustment module 403 is specifically used for: if the change event is that the group size of each terminal group increases simultaneously, then obtaining the business activity data of the target terminal application; adjusting the initial resource allocation ratio of each terminal group according to the business activity data to obtain the target resource allocation ratio; if the change event is that the group size of any terminal group decreases while the group size of the remaining terminal groups remains unchanged, or the group size of any terminal group increases while the group size of the remaining terminal groups remains unchanged, then adjusting the initial resource allocation ratio of each terminal group according to the current group size of each terminal group to obtain the target resource allocation ratio.

[0084] In one possible implementation of this application, the adjustment module 403 is further configured to: extract multiple business activity features from the business activity data; and adjust the initial resource allocation ratio of each terminal group according to the multiple business activity features to obtain the target resource allocation ratio.

[0085] In one possible implementation of this application, multiple business activity characteristics include operational activity intensity, target terminal volume, group size of each terminal group within a preset time period, and historical activity conversion rate; correspondingly, the adjustment module 403 is further configured to: construct an input sequence by arranging the operational activity intensity, target terminal volume, group size of each terminal group within a preset time period, and historical activity conversion rate in chronological order; and input the input sequence into a pre-built resource ratio prediction model, so that the pre-built resource ratio prediction model outputs the target resource allocation ratio based on the input sequence.

[0086] In one possible implementation of this application, the terminal group includes a newly registered terminal group and an already registered terminal group; correspondingly, the adjustment module 403 is further configured to: obtain operational objectives from business activity data; when the operational objective is to focus on increasing the scale of the newly registered terminal group, the initial resource allocation ratio of the already registered terminal group is reduced by half to obtain the target resource allocation ratio of the already registered terminal group; and the reduced portion of the initial resource allocation ratio of the already registered terminal group is added to the initial resource allocation ratio of the newly registered terminal group to obtain the target resource allocation ratio of the newly registered terminal group; when the operational objective is to focus on increasing the recall scale of the already registered terminal group, the initial resource allocation ratio of the newly registered terminal group is reduced by half to obtain the target resource allocation ratio of the newly registered terminal group; and the reduced portion of the initial resource allocation ratio of the newly registered terminal group is added to the initial resource allocation ratio of the already registered terminal group to obtain the target resource allocation ratio of the already registered terminal group.

[0087] In one possible implementation of this application, the terminal group includes two types of terminal groups; correspondingly, the allocation module 404 is specifically used to: divide the cloud resources into an ordered resource sequence; according to the adjusted resource allocation ratio, allocate the resource area corresponding to the beginning of the resource sequence to one type of terminal group, and allocate the resource area corresponding to the end of the resource sequence to the other type of terminal group.

[0088] In one possible implementation of this application, the determining module 401 is specifically used to: obtain the total size of multiple terminal groups; and for each terminal group, determine the proportion of the current terminal group's size to the total group size as the initial resource allocation ratio for each terminal group.

[0089] In one possible implementation of this application, the terminal group includes a newly registered terminal group and an already registered terminal group; the size of the newly registered terminal group is the average daily registration volume, and the size of the already registered terminal group is the average daily active volume.

[0090] The apparatus provided in this application embodiment can be used to execute the technical solutions of the above method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0091] Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device of this embodiment includes a processor 501 and a memory 502.

[0092] The memory 502 stores computer-executed instructions; the processor 501 executes the computer-executed instructions stored in the memory to implement the various steps performed by the electronic device in the above embodiments. For details, please refer to the relevant descriptions in the foregoing method embodiments.

[0093] Alternatively, the memory 502 can be either standalone or integrated with the processor 501.

[0094] When the memory 502 is set up independently, the electronic device also includes a bus 503 for connecting the memory 502 and the processor 501.

[0095] This application embodiment also provides a vehicle, which includes: a vehicle body, the vehicle body being configured with the above-described vehicle-mounted terminal, the vehicle-mounted terminal being used to execute the above-described cloud resource allocation method.

[0096] This application also provides a computer storage medium storing computer execution instructions. When the processor executes the computer execution instructions, the above-described cloud resource allocation method is implemented.

[0097] This application also provides a computer program product, including a computer program, which, when executed by a processor, implements the above-described cloud resource allocation method.

[0098] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0099] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0100] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0101] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0102] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0103] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.

[0104] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0105] The aforementioned storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0106] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. Both the processor and the storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic device or host device.

[0107] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0108] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for allocating cloud resources, characterized in that, include: Determine the initial resource allocation ratio for each terminal group; Real-time monitoring of changes in the group size of each terminal group; Based on the change events, adjust the initial resource allocation ratio of each terminal group to obtain the target resource allocation ratio; Based on the target resource allocation ratio, the cloud resources are allocated to each terminal group.

2. The method according to claim 1, characterized in that, The step of adjusting the initial resource allocation ratio of each terminal group according to the change event to obtain the target resource allocation ratio includes: If the change event is that the group size of each terminal group increases simultaneously, then the business activity data of the target terminal application is obtained; based on the business activity data, the initial resource allocation ratio of each terminal group is adjusted to obtain the target resource allocation ratio; If the change event is a decrease in the size of any terminal group while the size of the remaining terminal groups remains unchanged, or an increase in the size of any terminal group while the size of the remaining terminal groups remains unchanged, then the initial resource allocation ratio of each terminal group is adjusted according to the current size of each terminal group to obtain the target resource allocation ratio.

3. The method according to claim 2, characterized in that, The step of adjusting the initial resource allocation ratio of each terminal group based on the business activity data to obtain the target resource allocation ratio includes: Extract multiple business activity features from the business activity data; Based on the characteristics of the multiple business activities, the initial resource allocation ratio of each terminal group is adjusted to obtain the target resource allocation ratio.

4. The method according to claim 3, characterized in that, The characteristics of the multiple business activities include the intensity of the operational activities, the target number of terminals, the group size of each terminal group within a preset time period, and the historical activity conversion rate; Accordingly, adjusting the initial resource allocation ratio of each terminal group based on the characteristics of the multiple business activities to obtain the target resource allocation ratio includes: The input sequence is constructed by arranging the operational activity intensity, the target number of terminals, the group size of each terminal group within the preset time period, and the historical activity conversion rate in chronological order. The input sequence is fed into a pre-built resource ratio prediction model, which outputs the target resource allocation ratio based on the input sequence.

5. The method according to claim 2, characterized in that, The terminal group includes newly registered terminals and already registered terminals; Accordingly, adjusting the initial resource allocation ratio of each terminal group based on the business activity data to obtain the target resource allocation ratio includes: Obtain operational objectives from the aforementioned business activity data; When the operational objective is to focus on increasing the size of the newly registered terminal group, the initial resource allocation ratio of the already registered terminal group is reduced by half to obtain the target resource allocation ratio of the already registered terminal group; and the reduced portion of the initial resource allocation ratio of the already registered terminal group is added to the initial resource allocation ratio of the newly registered terminal group to obtain the target resource allocation ratio of the newly registered terminal group. When the operational objective is to focus on increasing the recall scale of the registered terminal group, the initial resource allocation ratio of the newly registered terminal group is reduced by half to obtain the target resource allocation ratio of the newly registered terminal group; and the reduced portion of the initial resource allocation ratio of the newly registered terminal group is added to the initial resource allocation ratio of the registered terminal group to obtain the target resource allocation ratio of the registered terminal group.

6. The method according to claim 1, characterized in that, The terminal group includes two types of terminal groups; Accordingly, allocating the cloud resources to each terminal group based on the target resource allocation ratio includes: The cloud resources are divided into an ordered resource sequence; According to the target resource allocation ratio, the resource area corresponding to the beginning of the resource sequence is allocated to one type of terminal group; and the resource area corresponding to the end of the resource sequence is allocated to another type of terminal group.

7. The method according to claim 1, characterized in that, Determining the initial resource allocation ratio for each terminal group includes: Obtain the total size of multiple terminal groups; For each terminal group, the proportion of the current terminal group's size to the total size of the group is determined as the initial resource allocation ratio for each terminal group.

8. The method according to any one of claims 1-7, characterized in that, The terminal group includes newly registered terminals and already registered terminals; the size of the newly registered terminal group is the average daily number of registrations, and the size of the already registered terminal group is the average daily number of active users.

9. An electronic device, characterized in that, include: At least one processor; And a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform the cloud resource allocation method according to any one of claims 1-8.

10. A computer storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the cloud resource allocation method as described in any one of claims 1-8.

11. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the cloud resource allocation method according to any one of claims 1-8.