Resource distribution system and method for cloud mobile phone

Abstract

The invention discloses a resource distribution system of a cloud mobile phone, which comprises a client, a resource management platform and an instance management platform, and is characterized in that the client is used for providing a cloud mobile phone function entrance and performing streaming use after cloud mobile phone instance scheduling; the resource management platform is used for providing a resource pool management function, a product tariff function, an instance time division multiplexing mechanism and an instance resource scheduling function for realizing scheduling multiplexing of instances; and the instance management platform is used for providing atomic functions of instance scheduling multiplexing, including instance management, instance backup data management, instance backup restoration capability and instance reset capability. Multi-user simultaneous reuse of cloud mobile phone resources can be realized, and the configuration of related strategies is adopted to avoid reduction of user experience to the maximum extent, including setting different reuse proportions, triggering conditions and recovery strategies for different cloud mobile phone manufacturers and different configuration cloud phones, adding an exemption list and avoiding the influence of oversell of the recovery strategies.

Description

Technical Field

[0001] The present application relates to the field of cloud phones, and in particular to a resource allocation system and method for cloud phones. Background Art

[0002] As an emerging service model, cloud virtual Android phones provide users with a solution to run the Android operating system without physical devices. Users can access cloud phones through cloud services to install, use and manage applications.

[0003] The allocation and utilization of existing cloud phone resources mainly include the following steps: Step 1: Resource pool management, building different resource pools, and allocating and placing cloud phone resources with different configurations; Step 2: User ordering, users order cloud phone resources through the purchase page; Step 3: Resource matching, the system matches the cloud phone resource pool with the corresponding configuration, and determines the remaining resources in the resource pool. If the resources are sufficient, the corresponding number of cloud phone resources will be called up; Step 4: Resource allocation, the system will allocate the called cloud phone resources to the user account and keep them allocated; Step 5: Expiration recovery, after the system recognizes that the user resource validity period has expired, it will execute the cloud phone resource recovery mechanism accordingly, reset the cloud phone, and put it into the resource pool.

[0004] The above-mentioned cloud phone resource allocation method has the following disadvantages:

[0005] 1. Low resource utilization. Once a cloud phone resource is bound to a certain user, other people cannot access and use the cloud phone resource before the expiration date. However, many users use cloud phone resources sporadically and not for a long time. In addition, users' demand for cloud phone resources changes dynamically, which will cause cloud phone resources to be idle for a long time, resulting in low resource utilization.

[0006] 2. Increased costs. For cloud phone platform operators, under the single binding mode, the returns created by a single cloud phone are limited, which will simultaneously restrict business development and resource expansion.

[0007] 3. Limiting market competitiveness: Failure to provide flexible and cost-effective solutions will restrict the market competitiveness of service providers

[0008] 4. Not conducive to environmental protection, low resource utilization will lead to more energy consumption and carbon emissions

[0009] It can be seen that the current technology is mainly concentrated on the functional level of cloud phones, and the resource cost is relatively high, while the actual resource usage of users is relatively scattered. Therefore, there is a relative lack of resource reuse technology for multiple people using cloud phones at the same time. A technical solution for resource allocation of cloud phones is needed to solve the above problems. Summary of the invention

[0010] In order to address the deficiencies of the prior art, the present application provides a resource allocation system, allocation method and server for a cloud phone, which can realize simultaneous multiple-user reuse of cloud phone resources, and adopt the configuration of relevant strategies to maximize the avoidance of degradation of user experience, including setting different reuse ratios, trigger conditions, and recycling strategies for different cloud phone manufacturers and cloud machines with different configurations, adding exemption lists, and avoiding the impact of oversold recycling strategies.

[0011] The technical effects to be achieved by this application are achieved through the following solutions:

[0012] According to a first aspect of the present application, a cloud phone resource allocation system is provided, including a client, a resource management platform and an instance management platform, wherein:

[0013] The client is used to provide an entry to the cloud phone function and to schedule the cloud phone instance for streaming use;

[0014] The resource management platform is used to provide resource pool management functions, product pricing functions, instance time-sharing reuse mechanisms, and instance resource scheduling functions to achieve instance scheduling and reuse;

[0015] The instance management platform is used to provide atomic functions for instance scheduling and reuse, including instance management, instance backup data management, instance backup and restore capabilities, and instance reset capabilities.

[0016] Preferably, the resource management platform includes a commodity configuration module, a policy configuration module and a resource recovery module, wherein:

[0017] The commodity configuration module is used to create a cloud phone according to the required configuration and associate the corresponding cloud phone resources;

[0018] The policy configuration module is used to set a reuse switch and a corresponding reuse ratio for different cloud phones according to the recycling strategy;

[0019] The resource recovery module is used to recover corresponding cloud phone resources according to a recovery strategy after the available resources are lower than a threshold.

[0020] Preferably, the policy configuration module can also enable a resource reuse function for a certain cloud phone, and can set a reuse ratio and a resource recovery strategy for the cloud phone with the resource reuse function enabled.

[0021] Preferably, in the resource recovery module, the corresponding cloud phone resources are recovered according to the recovery strategy as follows:

[0022] Reclaim the occupied cloud phone resources in order of priority;

[0023] When the recycling of cloud phone resources of any priority level is completed, it is determined whether the available number of cloud phone resources has recovered to the threshold. If so, recycling is stopped; otherwise, recycling of cloud phone resources of the next priority level is continued.

[0024] Preferably, the cloud phone resource types in order of priority from high to low include: recycling of free user resources after use, recycling of paid user resources after expiration, recycling of paid user resources that have not been used for a long time, recycling of paid user resources that have not been used for a short time, and recycling of paid user resources after use.

[0025] Preferably, the instance management platform includes a cloud phone data backup and recovery module, a cloud phone data recovery module and a whitelist module, wherein:

[0026] The cloud phone data backup and recovery module is used to back up data of cloud phone resources that meet the conditions after the recovery strategy is triggered;

[0027] The cloud phone data recovery module is used to match the cloud phone data corresponding to the user and perform data recovery when the user whose cloud phone resources have been reclaimed during the validity period re-enters the cloud phone client;

[0028] The whitelist module is used to store whitelist users, and the whitelist users are not included in the recycling strategy.

[0029] Preferably, after successfully backing up the data of the cloud phone, the cloud phone data backup and recovery module unbinds the cloud phone resources through the resource recovery module.

[0030] According to a second aspect of the present application, a resource allocation method for a cloud phone using the above-mentioned resource allocation system for a cloud phone is provided, comprising the following steps:

[0031] Step 1: The customer applies to the cloud phone operation platform for allocation of a cloud phone through the client;

[0032] Step 2: The cloud phone operation platform sends the application to the resource management platform to determine whether there are available cloud phone resources;

[0033] Step 3: If there are available cloud phone resources, the cloud phone list is directly returned to the client; otherwise, the cloud phone resources are recycled according to the resource recycling strategy and then the cloud phone list is returned to the client;

[0034] Step 4: Select the corresponding cloud phone in the cloud phone list to obtain the cloud phone connection information, and enter the cloud phone for use.

[0035] Preferably, in step 3, when the cloud phone resources are recycled according to the resource recycling strategy, the instance management platform first backs up the data of the cloud phone to be recycled, and then executes the resource recycling strategy after the data backup is completed.

[0036] Preferably, the method of resource recycling using the resource recycling strategy is: recycling the occupied cloud phone resources in order of priority, including deleting pre-installed applications, shutting down the cloud phone, restoring the cloud phone data interface, and restarting the cloud phone.

[0037] According to one embodiment of the present application, the beneficial effect of adopting the resource allocation system of the cloud phone is that it can back up and recycle data of occupied cloud phone resources according to the reuse ratio, recycling trigger conditions and cloud phone resource recycling strategy, so as to maximize the improvement of user experience and avoid the problem of poor experience caused by insufficient cloud phone resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present application or the existing technical solutions, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0039] Figure 1 This is a structural block diagram of a resource allocation system for a cloud phone in one embodiment of the present application;

[0040] Figure 2 This is a flow chart of a resource allocation method for a cloud phone in one embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0042] like Figure 1 As shown, a resource allocation system for a cloud phone in an embodiment of the present application includes a client, a resource management platform, and an instance management platform, wherein:

[0043] The client is used to provide an entry point for cloud phone functions and to stream the cloud phone instances after scheduling. The client is installed on terminals such as mobile phones, computers or tablets, and can access the cloud phone operation platform after connecting to the network to apply for cloud phone resources from the cloud phone operation platform.

[0044] Resource management platform, which is used to provide resource pool management, product pricing, instance time-sharing reuse mechanism and instance resource scheduling function to realize instance scheduling and reuse;

[0045] The platform can receive applications from cloud phone operation platforms, review user permissions based on the applications, and schedule corresponding cloud phone resources based on user permissions; if the current cloud phone resources are insufficient to be allocated to the user, the corresponding cloud phone resources will be recovered according to the instance time-sharing reuse mechanism until they are sufficient to be allocated to meet the current user's needs and ensure the user's experience.

[0046] The instance management platform is used to provide atomic functions for instance scheduling and reuse, including instance management, instance backup data management, instance backup and restore capabilities, and instance reset capabilities;

[0047] The platform can back up the usage data corresponding to the recovered cloud phone resources to ensure the data security of the recovered users. When the user comes back online, the data can be restored in time to ensure the user's usage experience.

[0048] In one embodiment of the present application, the resource management platform includes a commodity configuration module, a policy configuration module and a resource recovery module, wherein:

[0049] The product configuration module is used to create a cloud phone according to the required configuration and associate the corresponding cloud phone resources. The associated information includes the corresponding manufacturer and the corresponding configuration.

[0050] The policy configuration module is used to set the reuse switch and the corresponding reuse ratio for different cloud phones according to the recycling strategy. The reuse ratio means that after N cloud phones in a cloud phone resource pool are sold to N users, they can be sold to (N*reuse ratio) additional users, thereby maximizing profits while ensuring user experience.

[0051] This module supports setting whether to enable the resource reuse function for a certain cloud phone resource. After enabling it, you can further set the reuse ratio (i.e. how many additional people can use the cloud phone resource) and resource recycling strategy for the cloud machine product;

[0052] The resource recycling module is used to recycle the corresponding cloud phone resources according to the recycling strategy after the available resources are lower than the threshold, so as to support the need that the cloud phone resources can be used by multiple people; wherein: recycling the corresponding cloud phone resources according to the recycling strategy is specifically:

[0053] Reclaim the occupied cloud phone resources in order of priority;

[0054] When the recycling of cloud phone resources of any priority level is completed, it is determined whether the available number of cloud phone resources has recovered to the threshold. If so, recycling is stopped; otherwise, recycling of cloud phone resources of the next priority level is continued.

[0055] The cloud phone resource types in descending order of priority include: recycling of free user resources after use, recycling of paid user resources after expiration, recycling of paid user resources after long-term unused, recycling of paid user resources after short-term unused, and recycling of paid user resources after use. The triggering conditions and recycling strategies of each priority are as follows:

[0056] Priority 1: Free user resources are recycled after use;

[0057] Recycling strategy: Recycling of unused resources. Recycling of cloud machine resources (not outflowed) that have been unused for more than x minutes (configurable).

[0058] Priority 2: Expiration and recovery of paid user resources;

[0059] Trigger condition: After the priority 1 recycling action is completed, the available ratio is detected. If the available number of instances is still below the trigger ratio (inclusive), the priority 2 recycling action is initiated.

[0060] Recycling strategy: Recycling will be carried out after the payment period.

[0061] Priority 3: Reclaiming paid user resources that have not been used for a long time;

[0062] Trigger condition: If after the priority 2 recycling action is completed, the trigger ratio of the available number of instances is still not reached (inclusive), the priority 3 recycling action is initiated;

[0063] Recycling strategy: Recycling resources that have not been used for a long time. During the validity period, cloud machine resources that have not been used for more than X consecutive days (not outflowed) will be recycled.

[0064] Priority 4: Reclaiming paid user resources that have not been used for a short period of time;

[0065] Trigger condition: If after the priority 3 recycling action is completed, the trigger ratio of the available number of instances is still not reached (inclusive), the priority 3 recycling action is initiated;

[0066] Recycling strategy: Recycling of resources that have not been used for a short period of time. During the validity period, cloud machine resources that have not been used for more than X hours (not outflowed) will be recycled.

[0067] Priority 5: Reclaim paid user resources after they are no longer used;

[0068] Trigger condition: If after the priority 4 recycling action is completed, the trigger ratio of the number of available instances is still not reached (inclusive), the priority 5 recycling action is initiated;

[0069] Recycling strategy: Recycling resources after use. Cloud machine resources that have not been used for more than X minutes during the validity period (not outflowed) will be recycled.

[0070] In one embodiment of the present application, the instance management platform includes a cloud phone data backup and recovery module, a cloud phone data recovery module, and a whitelist module, wherein:

[0071] The cloud phone data backup and recycling module is used to back up the data of cloud phone resources that meet the recycling conditions after the recycling policy is triggered, and unbind the resources after successful backup, returning them to an idle and allocable state; the recycling conditions are set manually, such as recycling cloud phone resources that have not been used for more than 24 hours, and backing up the data. The backup data includes the cloud phone's application data, file data, cache data, etc.

[0072] The cloud phone data recovery module is used to automatically match the cloud phone data of the user's corresponding cloud phone and perform data recovery when the user whose cloud phone resources have been reclaimed during the validity period re-enters the cloud phone client and clicks to enter the cloud phone interface. After the recovery is completed, the user automatically enters the cloud phone operation interface;

[0073] Whitelist module: the cloud machine resources of users on this list are not included in the coverage of the oversold recovery policy. That is, when available resources are insufficient, if the cloud machine resources of users on this list are still within the validity period, they will not be recovered to meet the needs of different users.

[0074] like Figure 2 As shown, a resource allocation method for a cloud phone using the above-mentioned resource allocation system for a cloud phone in one embodiment of the present application includes the following steps:

[0075] Step 1: The customer applies to the cloud phone operation platform for allocation of a cloud phone through the client;

[0076] In this step, after the user opens the client and purchases a cloud phone, he or she applies to the cloud phone operation platform for allocation of the cloud phone. The application includes the configuration and manufacturer required for the cloud phone.

[0077] Step 2: The cloud phone operation platform sends the application to the resource management platform to determine whether there are available cloud phone resources;

[0078] In this step, the resource management platform first determines whether there are any saleable resources in the cloud phone resource pool. If there are available idle resources, proceed directly to step 3. If there are no available idle resources, determine whether the oversold limit has been reached. If the oversold limit has not been reached, implement the resource recovery strategy in step 3. If the oversold limit has been reached, provide a friendly prompt to the user.

[0079] Step 3: If there are available cloud phone resources, the cloud phone list is directly returned to the client; otherwise, the cloud phone resources are recycled according to the resource recycling strategy and then the cloud phone list is returned to the client;

[0080] In this step, when the cloud phone resources are recycled according to the resource recycling strategy, the instance management platform first backs up the data of the cloud phone to be recycled, and then executes the resource recycling strategy after the data backup is completed.

[0081] In the resource recycling strategy, cloud phone resources are released and recycled in descending order according to the priority until the required cloud phone resources are reached. If the cloud phone resources are not released and are being backed up, the user is reminded that the current cloud phone is being backed up and the user is not allowed to access the cloud phone;

[0082] If the current cloud phone backup is completed, after the cloud phone resources are released and recycled, the restore process of the cloud phone is started, that is, the pre-installed applications in the cloud phone are deleted, the data in the cloud phone is deleted, the cloud phone is shut down and the cloud phone data recovery interface is called, the cloud phone is restarted to complete the restoration, and the cloud phone is placed in the cloud phone list for users to select.

[0083] During the release and restoration process of the cloud phone, the current progress is displayed to the user in real time through the client.

[0084] Step 4: Select the corresponding cloud phone in the cloud phone list to obtain the cloud phone connection information, and enter the cloud phone for use.

[0085] In this step, the client obtains the connection information of the cloud phone, and determines whether the obtained cloud phone is normal. If it is normal, it enters the cloud phone; the cloud phone is displayed to the user through the client for the user to use.

[0086] It also includes the following steps: when the cloud phone resources are recycled, when the corresponding user goes back online and applies for a cloud phone, the backup of the cloud phone resources corresponding to the user is retrieved, and the previously backed up data is retrieved through the cloud phone data recovery module of the instance management platform for recycling, including reinstalling applications, program usage data, and saved file information, etc., to ensure the user experience.

[0087] The resource allocation system or method of the cloud phone can be applied to cloud devices such as cloud phones or virtual computers. It can back up and recycle the occupied cloud phone resources according to the reuse ratio, recycling trigger conditions and cloud machine recycling strategy configured by the operator, and restore the cloud machine data when the original user re-enters the cloud phone for the user to use.

[0088] Reclaim resources for free and paid users in order of priority and unused time to ensure the current user experience and maximize revenue;

[0089] Special users can be configured to the exemption list and exempted from resource recycling when the recycling policy is triggered, ensuring the different needs of different users;

[0090] After the recycling strategy is triggered, the backup capability will be called to back up the cloud phone data. When the user re-enters the cloud phone, the data recovery capability will be called to schedule idle cloud phone resources and restore the cloud phone data on them.

[0091] It should be noted that the above detailed descriptions are exemplary and are intended to provide further explanation of the present application. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present application belongs.

[0092] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should also be understood that when the terms "comprise" and / or "include" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0093] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0094] In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or inherent to these processes, methods, products, or apparatuses.

[0095] For ease of description, spatially relative terms, such as "above", "above", "on the upper surface of", "above", etc., may be used herein to describe the spatial positional relationship between a device or feature and other devices or features as shown in the figure. It should be understood that spatially relative terms are intended to include different orientations of the device in use or operation in addition to the orientation described in the figure. For example, if the device in the accompanying drawings is inverted, the device described as "above other devices or structures" or "above other devices or structures" will be positioned as "below other devices or structures" or "below other devices or structures". Thus, the exemplary term "above" may include both "above" and "below". The device may also be positioned in other different ways, such as rotated 90 degrees or in other orientations, and the spatially relative descriptions used herein are interpreted accordingly.

[0096] In the above detailed description, reference is made to the accompanying drawings, which form a part of this document. In the accompanying drawings, similar symbols typically identify similar components unless the context indicates otherwise. The illustrated embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be used, and other changes may be made, without departing from the spirit or scope of the subject matter presented herein.

[0097] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A resource allocation system for a cloud phone, characterized in that: It includes the client, resource management platform and instance management platform, among which: The client is used to provide an entry to the cloud phone function and to schedule the cloud phone instance for streaming use; The resource management platform is used to provide resource pool management functions, product pricing functions, instance time-sharing reuse mechanisms, and instance resource scheduling functions to achieve instance scheduling and reuse; The instance management platform is used to provide atomic functions for instance scheduling and reuse, including instance management, instance backup data management, instance backup and restore capabilities, and instance reset capabilities.

2. The resource allocation system for cloud phones according to claim 1, characterized in that: The resource management platform includes a commodity configuration module, a policy configuration module and a resource recovery module, wherein: The commodity configuration module is used to create a cloud phone according to the required configuration and associate the corresponding cloud phone resources; The policy configuration module is used to set a reuse switch and a corresponding reuse ratio for different cloud phones according to the recycling strategy; The resource recovery module is used to recover corresponding cloud phone resources according to a recovery strategy after the available resources are lower than a threshold.

3. The resource allocation system for cloud phones according to claim 2, characterized in that: The policy configuration module can also enable a resource reuse function for a certain cloud phone, and can set a reuse ratio and a resource recovery strategy for the cloud phone with the resource reuse function enabled.

4. The resource allocation system for cloud phones according to claim 2, characterized in that: In the resource recovery module, the corresponding cloud phone resources are recovered according to the recovery strategy as follows: Reclaim the occupied cloud phone resources in order of priority; When the recycling of cloud phone resources of any priority level is completed, it is determined whether the available number of cloud phone resources has recovered to the threshold. If so, recycling is stopped; otherwise, recycling of cloud phone resources of the next priority level is continued.

5. The resource allocation system for cloud phones according to claim 4, characterized in that: The cloud phone resource types, in order of priority from high to low, include: recycling of free user resources after use, recycling of paid user resources when they expire, recycling of paid user resources that have not been used for a long time, recycling of paid user resources that have not been used for a short time, and recycling of paid user resources after use.

6. The resource allocation system for cloud phones according to claim 4, characterized in that: The instance management platform includes a cloud phone data backup and recovery module, a cloud phone data recovery module, and a whitelist module, wherein: The cloud phone data backup and recovery module is used to back up the data of the cloud phone resources that meet the recovery conditions after the recovery policy is triggered; The cloud phone data recovery module is used to match the cloud phone data corresponding to the user and perform data recovery when the user whose cloud phone resources have been reclaimed during the validity period re-enters the cloud phone client; The whitelist module is used to store whitelist users, and the whitelist users are not included in the recycling strategy.

7. The cloud phone resource allocation system according to claim 6, characterized in that: After successfully backing up the data of the cloud phone, the cloud phone data backup and recovery module unbinds the cloud phone resources through the resource recovery module.

8. A method for allocating resources of a cloud phone using the resource allocation system of a cloud phone according to any one of claims 1 to 7, characterized in that: The steps include: Step 1: The customer applies to the cloud phone operation platform for allocation of a cloud phone through the client; Step 2: The cloud phone operation platform sends the application to the resource management platform to determine whether there are available cloud phone resources; Step 3: If there are available cloud phone resources, the cloud phone list is directly returned to the client; otherwise, the cloud phone resources are recycled according to the resource recycling strategy and then the cloud phone list is returned to the client; Step 4: Select the corresponding cloud phone in the cloud phone list to obtain the cloud phone connection information, and enter the cloud phone for use.

9. The resource allocation method of cloud phone according to claim 8, characterized in that: In step 3, when the cloud phone resources are recycled according to the resource recycling strategy, the instance management platform first backs up the data of the cloud phone to be recycled, and then executes the resource recycling strategy after the data backup is completed.

10. The resource allocation method of cloud phone according to claim 9, characterized in that: The method of resource recycling using the resource recycling strategy is: recycling the occupied cloud phone resources in order of priority, including deleting pre-installed applications, shutting down the cloud phone, restoring the cloud phone data interface, and restarting the cloud phone.

Images