CN114827147B - Method and system for realizing time sharing of cloud mobile phone - Google Patents

Method and system for realizing time sharing of cloud mobile phone Download PDF

Info

Publication number
CN114827147B
CN114827147B CN202210460151.XA CN202210460151A CN114827147B CN 114827147 B CN114827147 B CN 114827147B CN 202210460151 A CN202210460151 A CN 202210460151A CN 114827147 B CN114827147 B CN 114827147B
Authority
CN
China
Prior art keywords
user
data
mobile phone
cloud mobile
recovery
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210460151.XA
Other languages
Chinese (zh)
Other versions
CN114827147A (en
Inventor
雷大明
区锦棠
罗洪胜
陈春攀
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Yuewuji Network Technology Co ltd
Original Assignee
Guangdong Yuewuji Network Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Yuewuji Network Technology Co ltd filed Critical Guangdong Yuewuji Network Technology Co ltd
Priority to CN202210460151.XA priority Critical patent/CN114827147B/en
Publication of CN114827147A publication Critical patent/CN114827147A/en
Application granted granted Critical
Publication of CN114827147B publication Critical patent/CN114827147B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method and a system for realizing time sharing of a cloud mobile phone, wherein the method comprises the following steps: step S1, when the cloud mobile phone is in an idle state, counting the customized data of the current user, determining the category of the current user according to the counting result, carrying out corresponding backup processing on the customized data of the current user according to the determined category, restarting the cloud mobile phone after the data backup is completed, and recovering the initial data of the system; and step S2, when a request for distributing the cloud machine is received from the user, the cloud machine is redistributed according to the user type, and cloud mobile phone redistribution processing is carried out according to the category of the user.

Description

Method and system for realizing time sharing of cloud mobile phone
Technical Field
The invention relates to the technical field of cloud mobile phones, in particular to a method and a system for realizing time sharing of a cloud mobile phone.
Background
The cloud mobile phone divides a cloud server into a plurality of virtual machines to independently operate android systems through a virtual container at a cloud server end, and then remote operation is provided to enable terminal equipment such as the mobile phone to be operated and used, so that various applications can be operated at a cloud end, management is convenient, and consumption of local resources of a real mobile phone can be greatly reduced.
Currently, cloud mobile phones have more and more application scenes, including games, offices, education, videos, entertainment and the like. When a user orders a cloud mobile phone, after the cloud mobile phone is allocated to a certain user for use, because the data of the user is always stored on the cloud mobile phone, the cloud mobile phone cannot be allocated for use again even if the user does not use the cloud mobile phone for a long time during the ordering period, so that the waste of cloud mobile phone resources is caused, the cloud mobile phone can only adopt operation methods such as package days, package months and the like, the operation mode is inflexible, the operation cost of the cloud mobile phone is higher at present, and the popularization and the use of the cloud mobile phone are not facilitated.
If the cloud mobile phone can be separated from the data of the user, according to the use condition of the current user, backing up the user data in idle time, and releasing the cloud mobile phone for other users to use; and when the user needs to access the cloud machine again, the cloud machine is redistributed, the user data is quickly recovered, and the cloud machine is quickly re-entered. The utilization rate of the cloud mobile phone is greatly improved, so that the operation cost of the cloud mobile phone is reduced. How to enable the user who releases the cloud machine to quickly use the cloud machine again can influence the experience of the user, and becomes a key whether the cloud machine can be shared. Therefore, according to different scenes and situations of using the cloud machine by a user, a corresponding processing method is adopted, so that the quick recovery of the use is ensured, and the sharing of the cloud machine is realized.
The Chinese patent application with the publication number of CN111988409A discloses a method and a system for realizing the starting of the cloud mobile phone mounted external storage, the method provides a method for realizing the starting of the cloud mobile phone mounted external storage, the app and the data among different users are backed up to a system cluster configured as an associated user account, when the users use the cloud mobile phone, the cloud mobile phone is powered on to be started, the external storage is connected, the rbd corresponding to the users is found according to the information of the users, and the rbd is loaded into the cloud mobile phone to be used as the internal storage. After logging in, the user starts to use the cloud mobile phone, and if the app is newly installed or user data is modified, the user data is stored in the rbd; when the user does not use the cloud machine, the cloud machine is released, restarted, and the rbd of another user is loaded to the cloud mobile phone for use, so that the use scene with a fixed use time period is realized, the cloud mobile phone time division multiplexing method is suitable for time division multiplexing of the cloud mobile phone, and the comprehensive use efficiency of the cloud mobile phone can be improved.
The scheme completely separates the system and the user data through external storage, and can achieve release redistribution of the cloud machine in theory, but the following problems still exist in practice:
1. the scheme does not consider the conditions of a system and preset application, the data are distributed in various catalogues of the system and cannot be realized in a mode of mounting external storage, and the scheme cannot completely extract and backup the user data;
2. When a user connects a cloud machine, the cloud machine needs to be restarted, a user partition is mapped, user data is loaded to the system, the whole system starting process is long, the user needs to wait for tens of seconds to reenter the cloud machine, and the user experience is seriously affected.
3. All user data and applications are stored in external storage, frequent use of I/O can be caused by access of the applications, the I/O performance requirement on the cloud machine is high, operation blocking can be caused under serious conditions, and no response can occur to the applications.
Disclosure of Invention
In order to overcome the defects in the prior art, one of the purposes of the invention is to provide a method and a system for realizing time sharing of a cloud mobile phone, which fully considers various use scenes of the cloud mobile phone, considers the situation of self installation of applications of users and the situation of preset applications of the system, performs classified backup processing and quick recovery on user data, and ensures the integrity of the user data.
The invention also aims to provide a method and a system for realizing time sharing of the cloud mobile phone, which can ensure user experience and achieve the effect of cloud mobile phone sharing by quickly recovering user data without restarting the cloud mobile phone and ensuring that user clients do not feel difference when connecting a new cloud mobile phone.
The invention further aims to provide a method and a system for realizing time sharing of the cloud mobile phone, aiming at the condition of storing the cloud mobile phone into external storage, the use condition of the system I/O is fully considered, system blocking is avoided, and user experience is enhanced.
The invention also aims to provide a method and a system for realizing time sharing of the cloud mobile phone, which can selectively release and redistribute the cloud mobile phone by analyzing the content modified by the user data, so that different users can use the same cloud mobile phone in a time sharing way, thereby greatly improving the utilization rate of the cloud mobile phone, reducing the operation cost of the cloud mobile phone and also flexibly operating the cloud mobile phone.
In order to achieve the above purpose, the present invention provides a method for implementing time sharing of a cloud mobile phone, comprising the following steps:
step S1, when the cloud mobile phone is in an idle state, counting the customized data of the current user, determining the category of the current user according to the counting result, carrying out corresponding backup processing on the customized data of the current user according to the determined category, restarting the cloud mobile phone after the data backup is completed, and recovering the initial data of the system;
and step S2, when a request for distributing the cloud machine is received from the user, the cloud machine is redistributed according to the user type, and cloud mobile phone redistribution processing is carried out according to the category of the user.
Preferably, step S1 further comprises:
step S100, judging whether the cloud mobile phone is in an idle state, if so, starting a cloud mobile phone release flow, and entering step S101;
step S101, customized data of a current user of the cloud mobile phone are analyzed, evaluation is carried out according to the type of the customized data of the user, the size of the data and the recovery speed, and the category of the current user of the cloud mobile phone is determined;
step S102, according to the determined category of the current user, carrying out data backup by adopting a corresponding method;
step S103, restarting the cloud mobile phone after the data backup is completed, and recovering the initial data of the system.
Preferably, in step S101, the current user 'S customized data is counted, the type of the user' S customized data, the size of the data and the recovery speed are analyzed and evaluated, the recovery time of the personalized data is calculated, and the user type is determined according to the recovery time of the personalized data.
Preferably, in step S101, the recovery time of the personalized data is: network transmission and recovery time of system pre-installed application user data + network download time, installation time and user data network transmission and recovery time of user application installation package.
Preferably, the method for determining the user type according to the time of personalized data recovery comprises the following steps:
when the time < = set value of the personalized data recovery is determined as a class A user;
and judging the user as the B-class user or the C-class user when the personalized data recovery time is set, and distinguishing the B-class user from the C-class user according to the I/O concurrent data applied in a period of time.
Preferably, in step S102, if the current user is a class a user, a network quick backup recovery method is adopted to perform data backup, personalized data of the user is extracted, compressed, packaged and uploaded to an external storage server, and a cloud mobile phone of the class a user is added into a release queue; if the current user is a B-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, and adding the cloud mobile phone of the user into a release queue so as to release and restart for standby when the cloud mobile phone is insufficient; if the current user is a C-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, and carrying out configuration release according to parameters such as I/O load and the like of the system.
Preferably, step S2 further comprises:
step S200, receiving a request of a user for requesting cloud machine allocation, and carrying out cloud machine allocation according to the category of the user;
step S201, adopting a corresponding method to quickly recover the data according to the classification of the user.
Preferably, in step S201, if the user is a class a user, a network fast backup recovery method is adopted to recover the data, and the user data is directly downloaded from the external storage server for recovery; if the user is a B-class user or a C-class user, the data recovery is carried out by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery.
Preferably, in step 201, for a class B user or a class C user, after the data fast recovery is completed by the network fast backup recovery method, the background scans the application installed in the network-mounted directory to perform installation recovery, without affecting the user operation.
In order to achieve the above object, the present invention further provides a system for implementing time sharing of a cloud mobile phone, including:
the cloud machine release processing unit is used for counting the customized data of the current user when the cloud mobile phone is judged to be in an idle state, determining the category of the current user according to the statistical result, carrying out corresponding backup processing on the customized data of the current user according to the determined category, restarting the cloud machine after the data backup is completed, and recovering the initial data of the system;
And the cloud machine reassignment unit is used for reassigning cloud machine assignment according to the user type and carrying out cloud mobile phone reassignment according to the user type when receiving a request of the user for assigning the cloud machine.
Compared with the prior art, the invention has the following beneficial effects:
1. the invention fully considers various use scenes of the cloud mobile phone, considers the situation of the user installing the application, also considers the situation of the system presetting application, carries out classified backup processing and quick recovery on the user data, and ensures the integrity of the user data;
2. according to the cloud machine sharing method and device, the user data is quickly restored, the cloud machine is not required to be restarted, time-consuming restoration is carried out in the background, a user client can be quickly connected with a new cloud machine, the user client can not feel difference completely, user experience is guaranteed, and the good effect of cloud machine sharing is achieved.
3. Aiming at the condition of storing in external storage, the invention fully considers the service condition of the system I/O, avoids the system from being blocked and enhances the user experience.
4. According to the cloud mobile phone operation method and device, the content of user data modification is analyzed, and the cloud mobile phone is released and redistributed selectively, so that different users can use the same cloud mobile phone in a time sharing mode, the utilization rate of the cloud mobile phone is greatly improved, the operation cost of the cloud mobile phone is reduced, and the operation mode of the cloud mobile phone is also flexible.
Drawings
FIG. 1 is a flow chart of steps of a method for realizing time sharing of a cloud mobile phone according to the present invention;
fig. 2 is a block diagram of a system for implementing time sharing of a cloud mobile phone according to the present invention;
FIG. 3 is a flowchart of cloud machine release in an embodiment of the present invention;
FIG. 4 is a flow chart of reassignment of a cloud machine in an embodiment of the present invention;
fig. 5 is a flowchart of a network fast backup recovery process according to an embodiment of the present invention.
Detailed Description
Other advantages and effects of the present invention will become readily apparent to those skilled in the art from the following disclosure, when considered in light of the accompanying drawings, by describing embodiments of the present invention with specific embodiments thereof. The invention may be practiced or carried out in other embodiments and details within the scope and range of equivalents of the various features and advantages of the invention.
Fig. 1 is a flow chart of steps of a method for realizing time sharing of a cloud mobile phone, as shown in fig. 1, the method for realizing time sharing of a cloud mobile phone is applied to a cloud terminal (comprising a cloud server and a background service), and comprises the following steps:
step S1, when the cloud mobile phone is in an idle state, the customized data of the current user is counted, the category of the current user is determined according to the counted result, corresponding backup processing is carried out on the customized data of the current user according to the determined category, and after the data backup is completed, the cloud mobile phone is restarted, and the initial data of the system is restored.
Specifically, step S1 further includes:
step S100, judging whether the cloud mobile phone is in an idle state, if so, starting a cloud mobile phone release flow, and entering step S101.
In the method, when the cloud mobile phone judges that the user is active or does not operate overtime and exits to use the cloud mobile phone and is not connected with the cloud mobile phone again within the preset time, the cloud mobile phone is judged to be in an idle state currently (for example, the cloud mobile phone is judged not to be used by the user for a period of time), a cloud mobile phone release flow is started, and step S101 is started.
Step S101, customized data of a current user of the cloud mobile phone are analyzed, evaluation is carried out according to the type of the customized data of the user, the size of the data and the recovery speed, and the category of the current user of the cloud mobile phone is determined.
In the invention, the classification method of the cloud mobile phone users is mainly divided into three types according to the customized data of the users, wherein the customized data of the users mainly comprises two types of modification of system preset applications (including system applications and common applications) and applications installed by the users, the cloud mobile phone evaluates the types of the customized data of the users, the sizes of the data and the recovery speed by analyzing the types of the customized data of the users, and the users are divided into three types of A/B/C, and the data backup and recovery are carried out by adopting the corresponding method, wherein:
The class A user belongs to an application preset by a system, personal applications are rarely installed, and personalized data are relatively few, so that the personalized data of the user can be extracted, compressed, packed and uploaded to an external storage server; in the embodiment of the invention, the personalized data comprises, but is not limited to, user modification data of a system pre-installed application, a user-installed application installation package and user data.
The B-class user not only uses the preset application of the system, but also installs a part of personal application for use, and personalized data is general, so that the modified part of the preset application of the system is extracted, compressed, packed and uploaded to an external storage server, and the cloud machine can be quickly restored when the cloud machine is restored; for the personalized installation of the application app part, a network disk mounting mode is adopted, the system recovers background data, the cloud mobile phone can be put into a queue for standby, and the cloud mobile phone is released when the cloud mobile phone is insufficient;
the class C user installs more personalized apps, has more personalized data and needs to be released according to parameters such as I/O load of the system.
Therefore, before the cloud machine is released, the customized data of the current user is counted, the type, the size and the recovery speed of the customized data of the user are analyzed and evaluated, the recovery time of the personalized data is calculated, and which of the three types A/B/C is determined according to the recovery time of the personalized data. Specifically, the recovery time of the personalized data is estimated according to the personalized data, and the estimation method is as follows: network transmission and recovery time of system pre-installed application user data + network download time, installation time and user data network transmission and recovery time of user application installation package. Class a/B/C users may specifically divide the user types as follows:
1. When the personalized data recovery time < = 5 seconds, the personalized data recovery time is a class A user;
2. when the personalized data recovery time is more than 5 seconds, the personalized data is B or C, and then the personalized data is distinguished according to the I/O concurrent data applied at ordinary times; if the recorded disk I/O ratio is high, determining that the user is the C-class user, otherwise, determining that the user is the B-class user.
Step S102, according to the determined category of the current user, carrying out data backup by adopting a corresponding method.
Specifically, if the current user is a class A user, a network quick backup recovery method is adopted to carry out data backup, namely, personalized data of the user is extracted, compressed, packed and uploaded to an external storage server, and cloud mobile phones of the class A user are added into a release queue which can be released, so that the cloud mobile phones are released and restarted for standby when the cloud mobile phones are insufficient; if the current user is a B-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, namely extracting a modified part of the application preset by the system, compressing, packing and uploading the modified part to an external storage server, and carrying out personalized installation of an application app part, adopting a mode of network disk mapping backup recovery, and adding cloud mobile phones of the users into a releasable queue so as to release and restart for standby when the cloud mobile phones are insufficient; if the current user is a C-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, and carrying out configuration release according to parameters such as I/O load of the system, namely determining whether to add a releasable release queue according to the configuration of the parameters such as the I/O load. It should be noted that, the distinction between B-class users and C-class users is that the I/O of the disk is low in normal times, and the disk mounting does not affect the use; the class C users occupy more disk I/O, and the same server should avoid distributing excessive class C user cloud mobile phone instances by considering the network I/O processing capacity of the whole cloud mobile phone server.
In a specific embodiment of the present invention, for performing data backup by using a network fast backup recovery method, the method specifically includes the following steps:
extracting user modification data, including modification content of a system preset application and an application installed by a user, specifically including:
the application installed by the user is analyzed through information such as modification time and the like by analyzing the data difference between the data/app catalog and the preset system application; or alternatively
The modification data of the system preset application and the data installed by the user are analyzed and analyzed under the data/data directory, and extraction is carried out according to the directory; an adb backup command fetch may also be employed for allowing an allowances backup application.
And compressing, packing and uploading the extracted user data to an external storage server for backup. Specifically, the modified content of the system preset application and the application installed by the user are respectively packaged, each application corresponds to the subdirectory of the user, is compressed into a file, is named with the user ID and the timestamp, and is uploaded to the designated network storage server.
For the backup mode of network disk mapping backup recovery, mainly aiming at the situation that the user installs more apps, the data content of the extracted data backup is considered to be more, and the backup speed is influenced, so that the method of network disk mounting is adopted to improve the recovery time, the independent catalogs of the user installation application are mapped, and the independent catalogs are stored separately from the system application, thereby being convenient for isolating the backup.
The method is realized by independently installing and running the user application APK through the network disk, and comprises the following steps:
1. application installation directory: can be mapped to install under/mnt/nfsistal directory, respectively, creating 3 directories:
copy apk file to this directory at installation time/mnt/NFSInstall/app
IndustIndustInstantal/data- -storage of application data
N/mnt/NFSInstall/dalvik-cache- -install the dex file in apk under the dalvik-cache directory
2. Application installation process
Downloading an APK installation package to a/mnt/NFSInstall/app directory, decompressing and scanning the installation package, storing a dex file (Dalvik byte code) to the/mnt/NFSInstall/Dalvik-cache directory, and creating a corresponding application data directory under the/mnt/NFSInstall/data directory.
3. Application offloading process
Files and directories created under the three directories/mnt/NFSInstall/app,/mnt/NFSInstall/data,/mnt/NFSInstall/dalvik-cache are deleted during installation.
4. User data usage backup
The application data installed by the user is stored in an independent/mnt/NFSINStal directory, and the user can install, uninstall and update the application data to the lower part of the directory in real time. When the user releases the cloud machine in an idle mode, only the disk mounted on the network is required to be unloaded.
And step S103, restarting the cloud mobile phone after the data backup is completed, and recovering the initial data of the system, namely releasing the cloud mobile phone and waiting for the connection and use of a new user.
Specifically, the cloud machine is released according to the release queue, and preferably, when the cloud machine is added to the release queue, the situation that the class a user releases preferentially can be considered.
And step S2, when a request for distributing the cloud machine is received, the cloud machine distribution is redistributed according to the user type, and the cloud mobile phone redistribution processing is carried out according to the category of the user.
Specifically, step S2 further includes:
step S200, receiving a request of a user for requesting cloud machine allocation, and carrying out cloud machine allocation according to the category of the user.
That is, after the cloud mobile phone before the user is released, when the user applies for connecting the cloud mobile phone again, the system needs to redistribute the cloud mobile phone, when the user applies for the cloud mobile phone, the system generally distributes uniformly, distributes from the idle cloud mobile phone, obtains first, and can only wait for the system to release the redistribution of other cloud mobile phones if the idle cloud mobile phone does not exist.
When a request for distributing the cloud machine is received, if the request is a new user, the request can be directly distributed; if the user is not a new user, the user type is determined, and the determination of the user type can be omitted herein according to the method, and the cloud machine can be directly allocated to the class a/B user, if the user is a class B user, the case that the instance of the cloud machine server is allocated is considered, and it is required to ensure that the proportion of the instance of the class C cloud mobile phone user allocated by the cloud machine server does not exceed a set value, for example, 10%.
Step S201, adopting a corresponding method to quickly recover the data according to the classification of the user.
Specifically, if the user is a class-A user, a network quick backup recovery method is adopted to recover the data, namely, personalized data of the class-A user is relatively less, the user data is directly downloaded from an external storage server to recover, and the cloud machine can be ensured to be quickly accessed and normally used; if the user is a B-class user, performing data recovery by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, namely, directly downloading user data from an external storage server by system preset application data of the B-class user to recover, ensuring that the cloud machine can be quickly accessed, and searching a corresponding catalog in the background to import the data into a memory by a mode of network disk mounting of personalized apps and data thereof installed by the user; if the user is a class C user, the recovery process of the class C user is similar to that of the class B user, that is, the data recovery is performed by combining the network fast backup recovery and the network disk mapping backup recovery, preferably, if the user apps are too many and the recovery time in the background is relatively long, the data recovery can be performed first for the common application.
In a specific embodiment of the present invention, for data recovery by using a network fast backup recovery method, the method specifically includes the following steps:
Downloading data of a corresponding user from a network data storage server to a cloud mobile phone, and decompressing the downloaded data, in the specific embodiment of the present invention, taking an object storage service (OBS data bucket for short) of which the cloud is the cloud as an example:
./obsutil cp obs://bucket/001/data/
and respectively restoring the decompressed data to the data/app and the data/data catalog, or restoring by using an adb restore.
In a word, the condition that the user has less modified data is processed by the quick recovery method, so that the recovery can be quickly performed, the waiting time is reduced, and the user experience is improved.
And for the network disk mapping backup recovery mode, namely, the user data is backed up in a network disk mounting mode, when a user is connected with the cloud machine, the user data network disk is mounted to the/mnt/NFSInstall directory, the system background scanning is started, and the mounting information is loaded into the memory. Because a certain time is needed for loading the scanning apk into the system memory after the network disk is mounted, the scanning apk needs to be executed in the background, and the influence on the use of a user is avoided.
In addition, for some applications where read-write disks are frequent, the access delay of the network may affect the performance (because the read-write delay of the network disk is larger than that of the local disk), and the manner of using network mounting has a certain requirement on the I/O performance, so that the I/O condition needs to be detected in real time for configuration and use. The cloud mobile phone time sharing method and the cloud mobile phone time sharing device consider the situations, fully ensure practical experience of cloud mobile phone time sharing, avoid waiting of users and improve user experience.
And after the data is quickly restored by the network quick backup restoration method, the background scanning network mounting catalog-mounted application is installed and restored for B-class and C-class users, so that the user operation is not influenced.
Specifically, after the quick recovery is completed, the user can operate the cloud machine quickly, and the background scans the application installed in the network-mounted catalog to perform installation recovery, so that the user operation is not influenced.
Fig. 2 is a block diagram of a system for implementing time sharing of a cloud mobile phone according to the present invention, as shown in fig. 2, the system for implementing time sharing of a cloud mobile phone according to the present invention is applied to a cloud terminal, and includes:
and the cloud machine release processing unit 20 is used for counting the customized data of the current user when the cloud mobile phone is judged to be in an idle state, determining the category of the current user according to the statistical result, carrying out corresponding backup processing on the customized data of the current user according to the determined category, restarting the cloud machine after the data backup is completed, and recovering the initial data of the system.
Specifically, the cloud machine release processing unit 20 further includes:
the idle state monitoring module 201 is configured to determine whether the cloud mobile phone is in an idle state, and if so, start a cloud mobile phone release process, and enter the user category evaluation module 202.
In the method, when the cloud mobile phone judges that the user is active or does not operate overtime and exits to use the cloud mobile phone and is not connected with the cloud mobile phone again within a preset time, the cloud mobile phone is judged to be in an idle state currently, a cloud mobile phone release process is started, and the user category evaluation module 202 is entered.
The user category evaluation module 202 is configured to analyze the customized data of the current user of the cloud mobile phone, evaluate the customized data according to the type of the customized data, the size of the customized data and the recovery speed, and determine the category of the current user of the cloud mobile phone.
In the invention, the classification method of the cloud mobile phone users is mainly divided into three types according to the customized data of the users, wherein the customized data of the users mainly comprises two types of modification of system preset applications (including system applications and common applications) and applications installed by the users, the cloud mobile phone evaluates the types of the customized data of the users, the sizes of the data and the recovery speed by analyzing the types of the customized data of the users, and the users are divided into three types of A/B/C, and the data backup and recovery are carried out by adopting the corresponding method, wherein:
the A-class user belongs to an application preset by a system only, personal applications are rarely installed, personalized data are fewer, so that personalized data of the user can be extracted, compressed, packed and uploaded to an external storage server, and in the embodiment of the invention, the personalized data comprise, but are not limited to, user modification data of the system pre-installed application, a user-installed application installation package and user data;
The B-class user not only uses the preset application of the system, but also installs a part of application for carrying out, and personalized data is general, so that the modified part of the preset application of the system is extracted, compressed, packed and uploaded to an external storage server, and the cloud machine can be quickly restored to be connected during restoration; for the personalized installation of the application app part, a network disk mounting mode is adopted, the system recovers background data, the cloud mobile phone can be put into a queue for standby, and the cloud mobile phone is released when the cloud mobile phone is insufficient;
the personalized apps installed by the class C users are rich, personalized data are rich, and the personalized apps are required to be released according to parameters such as I/O load of the system.
Therefore, before the cloud machine is released, the customized data of the current user is counted, the type, the size and the recovery speed of the customized data of the user are analyzed and evaluated, the recovery time of the personalized data is calculated, and which of the three types A/B/C is determined according to the recovery time of the personalized data. Specifically, the recovery time of the personalized data is estimated according to the personalized data, and the estimation method is as follows: network transmission and recovery time of system pre-installed application user data + network download time, installation time and user data network transmission and recovery time of user application installation package. Class a/B/C users may specifically divide the user types as follows:
1. When the personalized data recovery time < = 5 seconds, the personalized data recovery time is a class A user;
2. when the personalized data recovery time is more than 5 seconds, the personalized data is B or C, and then the personalized data is distinguished according to the I/O concurrent data applied at ordinary times; if the recorded disk I/O ratio is high, determining that the user is the C-class user, otherwise, determining that the user is the B-class user.
And the data backup module 203 is configured to perform data backup by adopting a corresponding method according to the determined category of the current user.
Specifically, if the current user is a class-A user, a network quick backup recovery method is adopted to carry out data backup, namely, personalized data of the user is extracted, compressed, packed and uploaded to an external storage server, and cloud mobile phones of the class-A user are added into a releasable release queue so as to be released and restarted for standby when the cloud mobile phones are insufficient; if the current user is a B-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, namely extracting a modified part of the application preset by the system, compressing, packing and uploading the modified part to an external storage server, and carrying out personalized installation of an application app part, adopting a mode of network disk mapping backup recovery, and adding cloud mobile phones of the users into a releasable queue so as to release and restart for standby when the cloud mobile phones are insufficient; if the current user is a C-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, and carrying out configuration release according to parameters such as I/O load of the system, namely determining whether to add a releasable release queue according to the configuration of the parameters such as the I/O load. It should be noted that, the distinction between B-class users and C-class users is that the I/O of the disk is low in normal times, and the disk mounting does not affect the use; the class C users occupy more disk I/O, and the same server should avoid distributing excessive class C user cloud mobile phone instances by considering the network I/O processing capacity of the whole cloud mobile phone server.
In a specific embodiment of the present invention, for performing data backup by using a network fast backup recovery method, the method specifically includes the following steps:
extracting user modification data, including modification content of a system preset application and an application installed by a user, specifically including:
the application installed by the user is analyzed through information such as modification time and the like by analyzing the data difference between the data/app catalog and the preset system application; or alternatively
The modification data of the system preset application and the data installed by the user are analyzed and analyzed under the data/data directory, and extraction is carried out according to the directory; an adb backup command fetch may also be employed for allowing an allowances backup application.
And compressing, packing and uploading the extracted user data to an external storage server for backup. Specifically, the modified content of the system preset application and the application installed by the user are respectively packaged, each application corresponds to the subdirectory of the user, is compressed into a file, is named with the user ID and the timestamp, and is uploaded to the designated network storage server.
For the backup mode of network disk mapping backup recovery, mainly aiming at the situation that the user installs more apps, the data content of the extracted data backup is considered to be more, and the backup speed is influenced, so that the method of network disk mounting is adopted to improve the recovery time, the independent catalogs of the user installation application are mapped, and the independent catalogs are stored separately from the system application, thereby being convenient for isolating the backup.
The method is realized by independently installing and running the user application APK through the network disk, and comprises the following steps:
1. application installation directory: can be mapped to install under/mnt/nfsistal directory, respectively, creating 3 directories:
copy apk file to this directory at installation time/mnt/NFSInstall/app
IndustIndustInstantal/data- -storage of application data
N/mnt/NFSInstall/dalvik-cache- -install the dex file in apk under the dalvik-cache directory
2. Application installation process
Downloading an APK installation package to a/mnt/NFSInstall/app directory, decompressing and scanning the installation package, storing a dex file (Dalvik byte code) to the/mnt/NFSInstall/Dalvik-cache directory, and creating a corresponding application data directory under the/mnt/NFSInstall/data directory.
3. Application offloading process
Files and directories created under the three directories/mnt/NFSInstall/app,/mnt/NFSInstall/data,/mnt/NFSInstall/dalvik-cache are deleted during installation.
4. User data usage backup
The application data installed by the user is stored in an independent/mnt/NFSINStal directory, and the user can install, uninstall and update the application data to the lower part of the directory in real time. When the user releases the cloud machine in an idle mode, only the disk mounted on the network is required to be unloaded.
And the cloud machine releasing module 204 is used for restarting the cloud mobile phone after the data backup is completed, recovering the initial data of the system and waiting for the connection and use of a new user.
Specifically, the cloud machine release module 204 may release the cloud machine according to the release queue, and preferably, when joining the release queue, the case that the class a user releases preferentially may also be considered.
And the cloud machine reassignment unit 21 is used for, when receiving a request of a user for distributing cloud machines, reclassifying the cloud mobile phones according to the user types and carrying out cloud mobile phone reassignment processing according to the user types.
Specifically, the cloud machine reassignment unit 21 further includes:
the request receiving module 210 is configured to receive a request from a user for requesting to allocate a cloud machine, and allocate the cloud machine according to a category of the user.
That is, when the user applies for connecting the cloud mobile phone again after the cloud mobile phone before the user is released, the system receives the request for distributing the cloud mobile phone, and needs to redistribute the cloud mobile phone. When a user applies for a cloud machine, the cloud machines are generally distributed uniformly by a system, are distributed from an idle cloud machine, are obtained first, and if the idle cloud machine is not available, the system can only release the redistribution of other cloud machines.
When a request for distributing the cloud machine is received, if the request is a new user, the request can be directly distributed; if the user is not a new user, the user type is determined, and the determination of the user type can be omitted herein according to the method, and the cloud machine can be directly allocated to the class a/B user, if the user is a class B user, the case that the instance of the cloud machine server is allocated is considered, and it is required to ensure that the proportion of the instance of the class C cloud mobile phone user allocated by the cloud machine server does not exceed a set value, for example, 10%.
The data recovery module 211 is configured to perform quick recovery of data by adopting a corresponding method according to the classification of the user.
Specifically, if the user is a class-A user, a network quick backup recovery method is adopted to recover the data, namely, personalized data of the class-A user is relatively less, the user data is directly downloaded from an external storage server to recover, and the cloud machine can be ensured to be quickly accessed and normally used; if the user is a B-class user, performing data recovery by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, namely, directly downloading user data from an external storage server by system preset application data of the B-class user to recover, ensuring that the cloud machine can be quickly accessed, and searching a corresponding catalog in the background to import the data into a memory by a mode of network disk mounting of personalized apps and data thereof installed by the user; if the user is a class C user, the recovery process of the class C user is similar to that of the class B user, that is, the data recovery is performed by combining the network fast backup recovery and the network disk mapping backup recovery, preferably, if the user apps are too many and the recovery time in the background is relatively long, the data recovery can be performed first for the common application.
In a specific embodiment of the present invention, for data recovery by using a network fast backup recovery method, the method specifically includes the following steps:
downloading data of a corresponding user from a network data storage server to a cloud mobile phone, and decompressing the downloaded data, in the specific embodiment of the present invention, taking an object storage service (OBS data bucket for short) of which the cloud is the cloud as an example:
./obsutil cp obs://bucket/001/data/
and respectively restoring the decompressed data to the data/app and the data/data catalog, or restoring by using an adb restore.
In a word, the condition that the user has less modified data is processed by the quick recovery method, so that the recovery can be quickly performed, the waiting time is reduced, and the user experience is improved.
And for the network disk mapping backup recovery mode, namely, the user data is backed up in a network disk mounting mode, when a user is connected with the cloud machine, the user data network disk is mounted to the/mnt/NFSInstall directory, the system background scanning is started, and the mounting information is loaded into the memory. Because a certain time is needed for loading the scanning apk into the system memory after the network disk is mounted, the scanning apk needs to be executed in the background, and the influence on the use of a user is avoided.
In addition, for some applications where read-write disks are frequent, the access delay of the network may affect the performance (because the read-write delay of the network disk is larger than that of the local disk), and the manner of using network mounting has a certain requirement on the I/O performance, so that the I/O condition needs to be detected in real time for configuration and use. The cloud mobile phone time sharing method and the cloud mobile phone time sharing device consider the situations, fully ensure practical experience of cloud mobile phone time sharing, avoid waiting of users and improve user experience.
And after the data is quickly restored by the network quick backup restoration method, the background scanning network mounting catalog-mounted application is installed and restored for B-class and C-class users, so that the user operation is not influenced.
And after the data is quickly restored by the network quick backup restoration method, the background scanning network mounting catalog-mounted application is installed and restored for B-class and C-class users, so that the user operation is not influenced.
Specifically, after the quick recovery is completed, a user can quickly operate the cloud machine, and the background scans the application installed in the network-mounted catalog to perform installation recovery, so that the user operation is not influenced.
Examples
In this embodiment, the method includes a cloud machine idle release process and a cloud machine reassignment process, and the backup recovery of data includes two modes of user data quick recovery and user application network disk mounting. As shown in fig. 3, the cloud machine release flow is as follows:
step one, when the cloud machine judges that the cloud machine is actively used or is not in operation overtime, and is not connected with the cloud machine again for a certain time, the cloud machine judges that the cloud machine is in an idle state, and a cloud machine release process is started.
And secondly, counting user modification data before releasing the cloud machine, dividing the user modification data into A/B/C types according to the modified data content, and respectively carrying out data backup and cloud machine releasing processing on each type. The cloud mobile phone user classification method is mainly based on three types of user customized data, wherein the user customized data mainly comprises two types of modification of system preset applications (including system applications and commonly used applications) and applications installed by users. The cloud system analyzes the type of customized data of the user, the size of the data and the progressive evaluation of the recovery speed, divides the user into the following three types of A/B/C, and adopts a corresponding method for data backup and recovery:
The A-class user belongs to an application preset by a system, personal applications are rarely installed, personalized data are fewer, personalized data of the user can be extracted, compressed, packed and uploaded to an external storage server;
the B-class user not only uses the preset application of the system, but also installs a part of applications for execution, and the personalized data is general. Extracting a modified part of the application preset by the system, compressing, packing and uploading to an external storage server, and quickly recovering to connect to the cloud machine when recovering; and for the personalized application app installation part, a network disk mounting mode can be adopted, and the system recovers in background data. The cloud mobile phone can be put into a queue to be used as a standby, and released when the cloud mobile phone is insufficient;
the personalized apps installed by the class C users are also rich, personalized data are rich, the backup and recovery data of the class C users are more, and the class C users are required to be released according to parameters such as the I/O load of the system.
And thirdly, restarting the cloud machine after the data backup is completed, recovering the initial data of the system, and waiting for connection and use of a new user.
As shown in fig. 4, in this embodiment, the cloud machine reassignment flow is as follows:
step one, when a cloud machine before a user is released, applying for connecting the cloud machine again, wherein the cloud machine needs to be redistributed by the system;
Step two, the cloud machine adopts a corresponding method to recover data according to the classification of the users:
the personalized data of the A-class user is less, and the user data is directly downloaded from an external storage server for recovery, so that the cloud machine can be fast accessed and normally used;
the system preset application data of the class B user directly downloads the user data from an external storage server for recovery, so that the cloud machine can be quickly accessed, and the user-installed personalized app and the data thereof are searched in the background to guide the data into the memory in a network disk mounting mode;
the recovery process for class C users is similar to B, and if the user app is much and the recovery time in the background is relatively long, the recovery can be performed first for the commonly used application.
And thirdly, after the quick recovery is completed, a user can quickly operate the cloud machine, and the background scans the application installed in the network-mounted catalog to perform installation recovery without affecting the operation of the user.
In this embodiment, the backup and recovery of data includes two modes of user data network fast backup and recovery and user application network disk mounting, in which:
1. the network fast backup recovery mainly comprises the following steps, as shown in fig. 5:
Step one, extracting user modification data, including modification content of a system preset application and an application to be installed:
1. the application installed by the user is analyzed through information such as modification time and the like by analyzing the data difference between the data/app catalog and the preset system application;
2. the modification data of the system preset application and the data installed by the user are analyzed and analyzed under the data/data directory, and extraction is carried out according to the directory; an adb backup command fetch may also be employed for allowing an allowances backup application.
Step two, user data compression, packing and uploading backup
And respectively packaging the modified content of the system preset application and the application installed by the user, compressing each application into a file corresponding to the subdirectory of the user, naming the file with the user ID and the timestamp, and uploading the file to a designated network storage server.
Taking an object storage service (OBS data bucket for short) as a cloud as an example, the data uploading backup is realized through the obsettil:
1. before using the obsettil tool, the terminal node information of the OBS needs to be acquired first, the terminal node of the area is designated, and the network transmission delay is reduced;
2. creating an OBS data bucket through an/obsutil mb OBS:// bucket-test command;
3. the user data compression packet is uploaded to the OBS bucket,/OBS bucket cp/data/20211208.Tar gzobs:// bucket-test/001
Step three, user data downloading and decompressing
Downloading data of a corresponding user from a network data storage server to a cloud machine, taking an object storage service (OBS data bucket for short) which is a cloud as an example:
./obsutil cp obs://bucket/001/data/
and decompressing the downloaded data.
Step four, user recovery
And respectively restoring the data to the data/app and the data/data catalog, or restoring by using an adb restore.
In a word, the condition of less modified data is processed by the quick recovery method, so that the recovery can be quickly performed, the waiting time is reduced, and the user experience is improved.
2. Network disk mapping backup recovery
Aiming at the situation that the user installs more apps, the method of network disk mounting can be adopted to improve the recovery time in consideration of the fact that the data content of the extracted data backup is more and the backup speed is influenced. The user installs the independent catalogue of application to map, separate and store with the system application, facilitate isolating the backup.
The method is realized by independently installing and running the user application APK through the network disk, and comprises the following steps:
1. application installation directory: can be mapped to install under/mnt/nfsistal directory, respectively, creating 3 directories:
copy apk file to this directory at installation time/mnt/NFSInstall/app
IndustIndustInstantal/data- -storage of application data
N/mnt/NFSInstall/dalvik-cache- -install the dex file in apk under the dalvik-cache directory
2. Application installation process
Downloading an APK installation package to a/mnt/NFSInstall/app directory, decompressing and scanning the installation package, storing a dex file (Dalvik byte code) to the/mnt/NFSInstall/Dalvik-cache directory, and creating a corresponding application data directory under the/mnt/NFSInstall/data directory.
3. Application offloading process
Files and directories created under the three directories/mnt/NFSInstall/app,/mnt/NFSInstall/data,/mnt/NFSInstall/dalvik-cache are deleted during installation.
4. User data usage backup
The application data installed by the user is stored in an independent/mnt/NFSINStal directory, and the user can install, uninstall and update the application data to the lower part of the directory in real time. When the user releases the cloud machine in an idle mode, only the disk mounted on the network is required to be unloaded.
5. User application resume process
When a user connects the cloud machine, the user data network disk is mounted to the/mnt/NFSInstall directory, the background scanning of the system is started, and the mounting information is loaded to the memory. Because a certain time is needed for loading the scanning apk into the system memory after the network disk is mounted, the scanning apk needs to be executed in the background, and the influence on the use of a user is avoided.
The above embodiments are merely illustrative of the principles of the present invention and its effectiveness, and are not intended to limit the invention. Modifications and variations may be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is to be indicated by the appended claims.

Claims (6)

1. A method for realizing cloud mobile phone time sharing comprises the following steps:
step S1, when the cloud mobile phone is judged to be in an idle state, the customized data of the current user is counted, the category of the current user is determined according to the counted result, corresponding backup processing is carried out on the customized data of the current user according to the determined category, and after the data backup is completed, the cloud mobile phone is restarted, and the initial data of the system is restored;
step S2, when a request of a user for distributing cloud mobile phones is received, the cloud mobile phones are redistributed according to the category of the user;
step S1 further comprises:
step S100, judging whether the cloud mobile phone is in an idle state, if so, starting a cloud mobile phone release flow, and entering step S101;
step S101, customized data of a current user of the cloud mobile phone are analyzed, evaluation is carried out according to the type of the customized data of the user, the size of the data and the recovery speed, and the category of the current user of the cloud mobile phone is determined;
Step S102, according to the determined category of the current user, carrying out data backup by adopting a corresponding method;
step S103, restarting the cloud mobile phone after the data backup is completed, and recovering the initial data of the system;
in step S101, the customized data of the current user is counted, the type, the size and the recovery speed of the customized data of the user are analyzed and evaluated, the recovery time of the personalized data is calculated, and the category of the user is determined according to the recovery time of the personalized data;
in step S101, the recovery time of the personalized data is: network transmission and recovery time of system pre-installed application user data + network download time, installation time and user data network transmission and recovery time of user application installation package;
the method for determining the category of the user according to the personalized data recovery time comprises the following steps:
when the time < = set value of the personalized data recovery is determined as a class A user;
and judging the user as the B-class user or the C-class user when the personalized data recovery time is set, and distinguishing the B-class user from the C-class user according to the I/O concurrent data applied in a period of time.
2. The method for realizing time sharing of cloud mobile phones as claimed in claim 1, wherein in step S102, if the current user is a class a user, a network fast backup recovery method is adopted to perform data backup, personalized data of the user is extracted, compressed and packed and uploaded to an external storage server, and the cloud mobile phones of the class a user are added into a release queue; if the current user is a B-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, and adding the cloud mobile phone of the user into a release queue so as to release and restart for standby when the cloud mobile phone is insufficient; if the current user is a C-class user, carrying out data backup by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery, and carrying out configuration release according to parameters such as I/O load and the like of the system.
3. The method for implementing time sharing of a cloud mobile phone according to claim 1, wherein step S2 further comprises:
step S200, receiving a request of a user for applying for distributing cloud mobile phones, and distributing the cloud mobile phones according to the category of the user;
step S201, adopting a corresponding method to quickly recover the data according to the category of the user.
4. The method for realizing time sharing of the cloud mobile phone as claimed in claim 3, wherein the method comprises the following steps: in step S201, if the user is a class a user, performing data recovery by using a network fast backup recovery method, and directly downloading user data from an external storage server for recovery; if the user is a B-class user or a C-class user, the data recovery is carried out by adopting a mode of combining network quick backup recovery and network disk mapping backup recovery.
5. The method for realizing time sharing of the cloud mobile phone as claimed in claim 4, wherein the method comprises the following steps: in step 201, for a class B user or a class C user, after the data fast recovery is completed by the network fast backup recovery method, the background scans the application installed in the network mount directory to perform the installation recovery, without affecting the user operation.
6. A system for implementing cloud handset time sharing, comprising:
The cloud mobile phone release processing unit is used for counting the customized data of the current user when the cloud mobile phone is judged to be in an idle state, determining the category of the current user according to the statistical result, carrying out corresponding backup processing on the customized data of the current user according to the determined category, restarting the cloud mobile phone after the data backup is completed, and recovering the initial data of the system;
the cloud mobile phone reassigning unit is used for reassigning the cloud mobile phone according to the category of the user when receiving the request of the user for applying for the cloud mobile phone assignment;
the cloud mobile phone release processing unit further comprises:
the idle state monitoring module is used for judging whether the cloud mobile phone is in an idle state, if so, starting a cloud mobile phone release process, and entering the user category evaluation module;
the user category evaluation module is used for analyzing the customized data of the current user of the cloud mobile phone, evaluating the customized data according to the type of the customized data of the user, the size of the customized data and the recovery speed, and determining the category of the current user of the cloud mobile phone;
the data backup module is used for carrying out data backup by adopting a corresponding method according to the determined category of the current user;
the cloud mobile phone release module is used for restarting the cloud mobile phone after the data backup is completed, recovering the initial data of the system and waiting for the connection and use of a new user;
In a user category evaluation module, the customized data of the current user are counted, the type, the size and the recovery speed of the customized data of the user are analyzed and evaluated, the recovery time of the personalized data is calculated, and the category of the user is determined according to the recovery time of the personalized data;
the recovery time of the personalized data is as follows: network transmission and recovery time of system pre-installed application user data + network download time, installation time and user data network transmission and recovery time of user application installation package;
the method for determining the category of the user according to the personalized data recovery time comprises the following steps:
when the time < = set value of the personalized data recovery is determined as a class A user;
and judging the user as the B-class user or the C-class user when the personalized data recovery time is set, and distinguishing the B-class user from the C-class user according to the I/O concurrent data applied in a period of time.
CN202210460151.XA 2022-04-24 2022-04-24 Method and system for realizing time sharing of cloud mobile phone Active CN114827147B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210460151.XA CN114827147B (en) 2022-04-24 2022-04-24 Method and system for realizing time sharing of cloud mobile phone

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210460151.XA CN114827147B (en) 2022-04-24 2022-04-24 Method and system for realizing time sharing of cloud mobile phone

Publications (2)

Publication Number Publication Date
CN114827147A CN114827147A (en) 2022-07-29
CN114827147B true CN114827147B (en) 2023-04-25

Family

ID=82510262

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210460151.XA Active CN114827147B (en) 2022-04-24 2022-04-24 Method and system for realizing time sharing of cloud mobile phone

Country Status (1)

Country Link
CN (1) CN114827147B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118488069A (en) * 2023-02-11 2024-08-13 华为云计算技术有限公司 Cloud mobile phone hot start method and cloud mobile phone management platform

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102497404B (en) * 2011-12-02 2014-05-21 曙光信息产业(北京)有限公司 Storage backup method based on cloud environment
CN106506484B (en) * 2016-10-25 2020-01-14 Oppo广东移动通信有限公司 Data backup method, device and system
US10664357B1 (en) * 2016-12-20 2020-05-26 EMC IP Holding Company LLC Single agent backup for cloud networks
CN109005245B (en) * 2018-09-07 2021-09-14 广州微算互联信息技术有限公司 Cloud mobile phone use management method and system
CN111988409B (en) * 2020-08-20 2023-06-13 深圳市臂云科技有限公司 Method and system for realizing cloud mobile phone mounted external storage starting

Also Published As

Publication number Publication date
CN114827147A (en) 2022-07-29

Similar Documents

Publication Publication Date Title
US11526434B1 (en) Network-level garbage collection in an on-demand code execution system
US8954487B2 (en) Management server and method for providing cloud computing service
US11231955B1 (en) Dynamically reallocating memory in an on-demand code execution system
CN106557384B (en) Data processing method, device and system based on Linux
CN111078318B (en) Processing method, device and system of configuration file and storage medium
CN102831173A (en) Memory expanding method, device and terminal based on Android system
CN111338854A (en) Kubernetes cluster-based method and system for quickly recovering data
CN110968331B (en) Method and device for running application program
CN102932408A (en) Management method and platform of server cluster
CN114827147B (en) Method and system for realizing time sharing of cloud mobile phone
JP2008305404A (en) System, method and program product for backing up data
US10824339B1 (en) Snapshot-based garbage collection in an on-demand code execution system
CN105786539B (en) File downloading method and device
CN109947450A (en) System file upgrade method, device, mobile terminal and readable storage medium storing program for executing
CN107577506B (en) Data preloading method and system
CN106790403A (en) Realize the method for mobile cloud computing halfpace and realize distributed method
CN113037851B (en) Method for cloud mobile phone system super-resolution based on storage implementation
CN111432019B (en) Cloud game device distribution method and system based on edge cloud cooperation mode
CN113110851A (en) Resource loading method and device, electronic equipment and medium
CN101510156A (en) Information system resource recovery method and device
CN117914675A (en) Method and device for constructing distributed cache system
CN111431951B (en) Data processing method, node equipment, system and storage medium
CN113934437B (en) Method and system for installing application on cloud mobile phone and client cloud mobile phone
CN115827035A (en) Equipment upgrading method and device, storage medium and electronic device
CN115390754A (en) Hard disk management method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
EE01 Entry into force of recordation of patent licensing contract

Application publication date: 20220729

Assignee: Bee Assistant Co.,Ltd.

Assignor: Guangdong yuewuji Network Technology Co.,Ltd.

Contract record no.: X2023980043650

Denomination of invention: A Method and System for Implementing Cloud Phone Time Sharing

Granted publication date: 20230425

License type: Common License

Record date: 20231017

EE01 Entry into force of recordation of patent licensing contract