Cloud machine initialization method and device and electronic equipment

Abstract

The invention discloses a cloud machine initialization method and device and electronic equipment, and belongs to the technical field of cloud mobile phones. The method comprises the steps that a cloud machine initialization instruction sent by a cloud mobile phone scheduling platform is received, and the cloud machine initialization instruction is used for indicating initialization of a target cloud machine; a first storage path is mounted on a path of application data of a target cloud machine, the target cloud machine is initialized, a storage space corresponding to the first storage path is a cloud machine sharing space, and application data shared by a plurality of cloud machines on a server is stored in the cloud machine sharing space. In this way, time can be saved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of cloud phone technology, and in particular to a cloud machine initialization method, device and electronic device. Background Art

[0002] A cloud machine is a container instance running in the cloud. There is no connection between the cloud machines, and their data is completely isolated from each other. The cloud machine server needs to store complete data for each cloud machine separately.

[0003] Therefore, in the related art, when a user registers a new cloud machine, the newly registered cloud machine system needs to initialize brand new data, which consumes a long time and seriously affects the user experience. Summary of the invention

[0004] The embodiments of the present application provide a cloud machine initialization method, device and electronic device, which can at least solve the problem of long cloud machine initialization time.

[0005] In order to solve the above technical problems, this application is implemented as follows: In a first aspect, an embodiment of the present application provides a cloud machine initialization method, the method comprising: receiving a cloud machine initialization instruction sent by a cloud phone scheduling platform, wherein the cloud machine initialization instruction is used to instruct the initialization of a target cloud machine; initializing the target cloud machine by mounting the path of the application data of the target cloud machine to a first storage path, wherein the storage space corresponding to the first storage path is a cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server.

[0006] In a second aspect, a cloud machine initialization device is provided, which includes: a receiving module for receiving a cloud machine initialization instruction sent by a cloud phone scheduling platform, wherein the cloud machine initialization instruction is used to instruct the initialization of a target cloud machine; an initialization module for initializing the target cloud machine by mounting the path of the application data of the target cloud machine to a first storage path, wherein the storage space corresponding to the first storage path is a cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server.

[0007] In a third aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method described in the first aspect above are implemented.

[0008] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect above are implemented.

[0009] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer executes the steps of the method described in the first aspect above.

[0010] The technical solution provided by this application may have the following beneficial effects: In the embodiment of the present application, a cloud machine initialization instruction sent by a cloud phone scheduling platform can be received, wherein the cloud machine initialization instruction is used to instruct the target cloud machine to be initialized; the target cloud machine is initialized by mounting the path of the target cloud machine's application data to the first storage path, wherein the storage space corresponding to the first storage path is the cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server. In the above manner, the time for cloud machine initialization can be reduced, the waiting time for users to register cloud machines can be shortened, and the user experience can be improved.

[0011] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0013] Figure 1 A schematic diagram of cloud machine backup and restoration in the related art is shown; Figure 2 A schematic diagram of a process flow of a cloud machine initialization method provided in an embodiment of the present application is shown; Figure 3 A schematic diagram of a cloud machine storage structure provided by an embodiment of the present application is shown; Figure 4 A timing diagram showing initialization of shared data by an operations administrator provided in an embodiment of the present application is shown; Figure 5 A schematic diagram showing the overall process of initializing shared data provided by an embodiment of the present application is shown; Figure 6 The timing diagram of user registration and activation of cloud machine provided by the embodiment of the present application is shown Figure 7 A schematic diagram of user registration and activation of a cloud machine provided in an embodiment of the present application is shown; Figure 8 A timing diagram of backing up a cloud machine by an operations administrator provided in an embodiment of the present application is shown; Fig. 9 A timing diagram of a user backup cloud machine provided in an embodiment of the present application is shown; Fig.10 A schematic diagram of a backup cloud machine provided in an embodiment of the present application is shown; Fig.11 A timing diagram of an operation administrator restoring a cloud machine provided in an embodiment of the present application is shown; Fig.12 A timing diagram of a user restoring a cloud machine provided in an embodiment of the present application is shown; Fig.13 A schematic diagram of cloud machine restoration provided in an embodiment of the present application is shown; Fig.14 A schematic diagram of a cloud machine storage global architecture provided by an embodiment of the present application is shown; Fig.15 A schematic diagram of the structure of a cloud machine initialization device provided in an embodiment of the present application is shown; Fig.16 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown; Fig.17 A schematic structural diagram of another electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0014] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0015] Usually, a cloud machine is a container instance running in the cloud. There is no connection between the cloud machines, and the data of each cloud machine is completely isolated. In this case, the applications between the cloud machines are also completely isolated, resulting in some identical resources being stored in each cloud machine. On the one hand, it wastes storage space, and on the other hand, it causes duplicate installation of applications, especially for large applications. For example, most game applications are large, and data initialization will take a long time. Secondly, if Figure 1 As shown, when backing up and restoring a cloud machine, the data of the entire cloud machine needs to be backed up and restored. If there are many applications installed or they are large, it will take a considerable amount of time to back up and restore the data, causing a very bad user experience.

[0016] In the related technology, firstly, for newly registered users, each cloud machine system has to initialize a brand new data, which consumes a long time in the process and seriously affects the user experience. Secondly, when backing up user data, each cloud machine must be fully backed up, which not only wastes storage space, but also requires a lot of network transmission time, especially for larger applications, such as game applications. Thirdly, when restoring data, there are also problems of wasted space and long transmission time. For pre-installed applications, the application installation data is the same, and each user has installed the same pre-installed application, resulting in a large amount of duplicate application installation data in the entire server.

[0017] Figure 2 A schematic diagram of a process flow of a cloud machine initialization method provided by an exemplary embodiment of the present application is shown. The method can be applied to a server, which can be an ARM server. Figure 2 As shown, the method mainly includes the following steps: S201: Receive the cloud machine initialization instruction sent by the cloud phone scheduling platform.

[0018] The initialization cloud machine instruction is used to instruct the initialization of the target cloud machine.

[0019] In the embodiments of the present application, Figure 3 As shown, the server may include a cloud machine instance, a cloud machine shared space, and a cloud machine user space. Among them, the cloud machine instance is an important component of the cloud machine, a container in the ARM server, and the core part of the entire cloud machine. It ensures that the cloud machine can run independently, isolated from other containers, and ensures that applications do not interfere with each other. In the cloud machine initialization method of an embodiment of the present application, the server can receive an initialization cloud machine instruction sent by a cloud phone scheduling platform, and the initialization cloud machine instruction can be used to instruct the target cloud machine to be initialized. In actual applications, the initialization cloud machine instruction can carry the identification of the target cloud machine. For example, if it is an initialization of the cloud machine, the server can receive an initialization instruction sent by a cloud phone scheduling platform. The initialization cloud machine instruction can be used to instruct the initialization of the target cloud machine. In actual applications, the initialization cloud machine instruction can carry the identification of the target cloud machine. For example, if it is an initialization of the cloud machine, the server can receive an initialization instruction Figure 3 To initialize cloud machine A in the , you can carry the identifier of cloud machine A to avoid errors.

[0020] In an optional implementation, the cloud machine server may pre-store application data shared by each cloud machine. Therefore, before receiving the initialization cloud machine instruction sent by the cloud phone scheduling platform, the method may further include the following steps: Receiving the application data sent by the cloud phone scheduling platform; The application data is stored in the cloud machine shared space.

[0021] In an embodiment of the present application, the server can receive application data sent by the cloud phone scheduling platform, and then store the application data in the cloud machine shared space.

[0022] In the embodiments of the present application, Figure 4 The timing diagram showing the administrator initializing shared data may include the following steps: Step 401: Request to initialize application data; first, the operation administrator can request to initialize application data on the cloud phone scheduling platform.

[0023] Step 402: Initialize system application data + non-system application data; after receiving the request, the cloud phone scheduling platform can initialize the application data that needs to be shared. The initialized application data includes two parts, one part is system application data; the other part is non-system application data.

[0024] Step 403: Store application data in the cloud machine shared space; after initialization, the cloud phone scheduling platform can send application data to the host ARM server of each cloud phone for storage.

[0025] Step 404: store the system application data in the system application space; in actual applications, the server may store the system application data in the application data in the / phonespace / share / system / app / directory of the system application space.

[0026] Step 405: Store non-system application data in the non-system application space; in actual applications, the server can store non-system application data in the / phonespace / share / user / data / app / directory of the non-system application space. Through steps 405 and 406, in the cloud machine shared space of each ARM server, there will be exactly the same system application data and non-system application data, and any cloud machine on this ARM server can use these shared data.

[0027] Step 406: Storage completion response; after the server completes the storage, it can respond to the cloud phone scheduling platform so that the cloud phone scheduling platform is informed of the server's completion of storage.

[0028] Step 407: Initialization completion response; the cloud phone scheduling platform can respond to the operation administrator that initialization is complete to avoid the operation administrator from repeating initialization.

[0029] Its overall business process is as follows Figure 5 shown.

[0030] In an optional implementation, the cloud machine initialization instruction also carries identification information corresponding to the registered object; then after receiving the cloud machine initialization instruction sent by the cloud phone scheduling platform, the method also includes: associating the identification information with the target cloud machine.

[0031] In an embodiment of the present application, the instruction to initialize the cloud machine may carry identification information, and the identification information includes a user identifier userID and a cloud machine identifier phoneID. The identification information corresponds one-to-one to the target cloud machine, and the identification information can be associated with the target cloud machine to facilitate more convenient identification and search for the target cloud machine. In actual applications, the cloud phone scheduling platform can assign a user identifier userID and a cloud machine identifier phoneID to the user based on the registration information (such as a mobile phone number). The two unique identifiers are 19-bit Long type IDs generated according to the snowflake algorithm to ensure global uniqueness. For example, the generated format is: 1666288245916319746. In actual applications, other algorithms can also be used to generate identification information, which is not specifically limited in the embodiments of the present application.

[0032] S202: Initialize the target cloud machine by mounting the path of the application data of the target cloud machine to the first storage path.

[0033] Among them, the storage space corresponding to the first storage path is a cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server.

[0034] In an embodiment of the present application, the server can initialize the target cloud machine by mounting the path of the target cloud machine's application data to the first storage path. The server can initialize the target cloud machine by mounting the path of the target cloud machine's application data to the first storage path. The storage space corresponding to the first storage path is the cloud machine shared space. The cloud machine shared space stores application data shared by multiple cloud machines on the server.

[0035] In an optional implementation, the above application data may include system application data and non-system application data. In an embodiment of the present application, the application data includes system application data and non-system application data. The system application data may be the system application data of the cloud machine system itself, and the non-system application data may be the data shared by the application program.

[0036] In an optional implementation, initializing the target cloud machine includes: According to the identification information, the path of the user data of the target cloud machine is mounted to the second storage path, wherein the storage space corresponding to the second storage path is the user space of the server, and the user space is used to store the user data of the target cloud machine, and different cloud machines on the server correspond to different user spaces.

[0037] In an embodiment of the present application, based on identification information, the path of user data of the target cloud machine is mounted to the second storage path, wherein the storage space corresponding to the second storage path is the user space of the server.

[0038] In the embodiment of the present application, the timing diagram of user registration and activation of cloud machine is as follows: Figure 6 As shown, the following steps are included: Step 601: User registers a cloud machine; Step 602: Request to register the cloud machine; when the user registers and activates the cloud machine, the cloud machine client requests the cloud phone scheduling platform.

[0039] Step 603: Generate user ID and cloud machine ID phoneID + allocate cloud machine; the cloud phone scheduling platform can assign a user ID and cloud machine ID phoneID to the user according to the registration information (such as mobile phone number). The two unique identifiers are 19-bit Long type IDs generated according to the snowflake algorithm to ensure global uniqueness. For example, the generated format is: 1666288245916319746. Then allocate cloud machines according to resource conditions. In actual applications, other algorithms can also be used to generate identification information, which is not specifically limited in the embodiments of this application.

[0040] Step 604: Initialize the cloud machine according to userID and phoneID; the cloud phone scheduling platform can send a cloud machine initialization instruction to the server. In the embodiment of the present application, the cloud machine initialization instruction can carry the identification information, which includes the user identification userID and the cloud machine identification phoneID.

[0041] Step 605: Mount the cloud machine shared space; the server can mount the cloud machine shared space.

[0042] Step 606: Mount shared system applications + shared non-system applications; the server can mount the path of the system application data of the target cloud machine to the corresponding path of the system application space, and mount the path of the non-system application data to the corresponding path of the non-system application space.

[0043] Step 607: Mounting completion response; Step 608: Start the cloud machine; after the mounting is completed, the server can start the cloud machine.

[0044] Step 609: Initialize the startup response; the server can send a response message to the cloud phone scheduling platform to facilitate the cloud phone scheduling platform to learn that the target cloud machine has completed initialization.

[0045] Step 610: Respond to the client; the cloud phone scheduling platform can respond to the cloud phone client to facilitate the cloud phone client to learn that the target cloud machine has completed initialization.

[0046] Step 611: Respond to the user. The cloud phone client can respond to the user, which can improve the user's experience of registering the cloud machine.

[0047] like Figure 7 As shown, when a user registers a cloud machine and logs in, the server mounts the cloud machine's system application data to the shared system application space, mounts the cloud machine's non-system application data to the shared non-system application space, and mounts the cloud machine's user data to the user space corresponding to the registered object. For example, for a new user, the personal user data is empty, and the path of the data generated by the user in the target cloud machine can be / data / data / , / sdcard / Android / data / , and the mount path in the server's user space can be set to / phonespace / user / user1 / data / data / , / phonespace / user / user1 / sdcard / Android / data / , where user1 is a specific user ID.

[0048] Optionally, the cloud machine's mounting configuration may be as shown in Table 1.

[0049] Table 1

[0050] In an optional implementation, after completing the initialization of the target cloud machine by mounting the path of the application data of the target cloud machine to the first storage path, the method may further include: An initialization cloud machine response message is sent to the cloud phone scheduling platform, wherein the initialization cloud machine response message is used to indicate that the target cloud machine has completed initialization.

[0051] In an embodiment of the present application, an initialization cloud machine response message can be sent to the cloud phone scheduling platform. The initialization cloud machine response message indicates that the target cloud machine has completed initialization, which makes it easier for the cloud phone scheduling platform to learn that the target cloud machine has completed initialization and is being activated, thereby improving the user experience of registering a cloud machine.

[0052] In the embodiment of the present application, the server can complete the mounting of system application data and non-system application data, thereby achieving the effect of registering and activating the cloud machine in seconds, which can improve the efficiency of activating the cloud machine and the user experience.

[0053] In an optional implementation, after initializing the target cloud machine, the method may further include the following steps: Step 1, receiving a backup instruction sent by the cloud phone scheduling platform, wherein the backup instruction is used to instruct to back up the data of the target cloud machine; Step 2: Backing up the user data of the target cloud machine to obtain and store the backup user data of the target cloud machine.

[0054] In the embodiment of the present application, the server can receive a backup instruction sent by the cloud phone scheduling platform, wherein the backup instruction is used to instruct to back up the data of the target cloud machine; then, by backing up the user data of the target cloud machine, the backup user data of the target cloud machine is obtained and stored. In actual application, there are two scenarios for backup, one scenario is that the administrator backs up the target cloud machine, and the other scenario is that the user backs up the target cloud machine himself.

[0055] In the embodiment of the present application, the timing diagram of the administrator backing up the cloud machine is as follows: Figure 8 As shown, the following steps may be included: Step 801: Administrator backup parameters: userID+phoneID; in actual applications, the operation administrator can select the target cloud machine on the cloud phone scheduling platform, and then initiate a backup request, which can carry the user ID userID and the cloud machine ID phoneID.

[0056] Step 802: Determine the target cloud machine according to the userID and phoneID; the cloud phone scheduling platform can determine the target cloud machine according to the userID and phoneID.

[0057] Step 803: Initiate a backup request; the cloud phone scheduling platform initiates a backup request to the target cloud machine in the server; Step 804: Back up user data; the target cloud machine may instruct the cloud machine space to back up user data; Step 805: Back up user data; the cloud machine space backs up user data; Step 806: backup response; the cloud machine space performs a backup response to the target cloud machine; Step 807: userID:phoneID is combined into a file KEY, and user data is stored in OBS; Step 808: Backup response; the target cloud machine makes a backup response to the cloud phone scheduling platform, and can notify the cloud phone scheduling platform that the backup has been completed.

[0058] Step 809: Backup response; the cloud phone scheduling platform can respond to the administrator and notify the target cloud machine to complete the backup.

[0059] The administrator first selects the target cloud machine on the cloud phone scheduling platform, and then initiates a backup request. The request will carry the user ID userID and the cloud machine ID phoneID. After receiving the backup request, the cloud phone scheduling platform will find the corresponding target cloud machine based on the userID and phoneID, and forward the backup instruction to the corresponding server. Then, the corresponding user data can be backed up, and the backup user data of the target cloud machine can be obtained and stored. As for system application and non-system application data, these two parts of data are shared data and do not need to be backed up. You only need to back up user data to achieve the effect of backing up the cloud machine in seconds.

[0060] In the embodiment of the present application, the timing diagram of the user backing up the cloud machine is as follows: Fig. 9 As shown, the following steps may be included: Step 901: User initiates backup; the user can initiate backup of the target cloud machine on the cloud phone client.

[0061] Step 902: User backup parameters: userID+phoneID; Step 903: Determine the target cloud machine according to the userID and phoneID; Step 904: initiate a backup request; Step 905: Back up user data; Step 906: Back up user data; Step 907: backup response; Step 908: userID:phoneID is combined into a file KEY, and the user data is stored in OBS; Step 909: backup response; Step 910: backup response; Step 911: Respond to user backup The user initiates a backup request through the cloud phone client. After receiving the backup request, the cloud phone client forwards the request with the user ID and cloud machine phone ID to the cloud phone scheduling platform. The subsequent process is the same as the backup process of the operation administrator.

[0062] In actual applications, the user data in the user space can also be compressed and backed up, the backup user data can be obtained, and then the backup user data can be zip compressed. Therefore, in an optional implementation, storing the backup user data of the target cloud machine can include: storing the backup user data in the object storage OBS.

[0063] In the embodiment of the present application, the backup user data can be stored in the object base storage (OBS). OBS has higher flexibility and scalability. Using OBS can not only ensure that data will not be lost, but also ensure the persistence and stable access of data, and the cost is low. In practical applications, other forms of storage can also be used, which are not specifically limited in the embodiment of the present application.

[0064] In an optional implementation, the backup user data may be identified by identification information corresponding to the target cloud machine.

[0065] For example, you can name the backup user data with userID:phoneID, such as: 1666288245916319746:1666276758711709697, and then store the data properly. Identifying the backup user data with the identification information corresponding to the target cloud machine is helpful for querying.

[0066] In an optional implementation, after acquiring and storing the backup user data of the target cloud machine, the method may further include: sending a backup instruction response message to the cloud phone scheduling platform, wherein the backup instruction response message is used to indicate the completion of the backup of the target cloud machine.

[0067] In an embodiment of the present application, after obtaining and storing the backup user data of the target cloud machine, a backup instruction response message can also be sent to the cloud phone scheduling platform. The backup instruction response message indicates that the backup of the target cloud machine has been completed, which helps the cloud phone scheduling platform to learn of the completion of the backup of the target cloud machine, facilitating recording and the next step of restoration.

[0068] In the embodiment of the present application, the backup data of the entire cloud machine includes three types of data backup, namely, cloud machine system application data backup, cloud machine application data backup, and user data backup generated by users when using applications. Among them, cloud machine system application data and non-system application data are shared data. For this type of data, the administrator has maintained the data on the cloud phone scheduling platform and distributed it to the shared space of each ARM server. For this part of the data, there is no need for additional backup. As for user data, each user can store a separate copy. In order to save resources, in the embodiment of the present application, the backup user data can be compressed. For example, the zip compression algorithm can be used for compression. The zip compression algorithm is a sliding window-based LZ77 compression algorithm that highly compresses the data, which not only ensures the integrity of the data, but also saves storage resources. Finally, the compressed file is named as a recognizable file in the format of userID:phoneID and stored in the OBS storage service. The overall process is as follows: Fig.10 shown.

[0069] In an optional implementation, after acquiring and storing the backup user data of the target cloud machine, the method may further include the following steps: Step 1, receiving a restore instruction sent by the cloud phone scheduling platform, wherein the restore instruction is used to instruct to restore the data of the target cloud machine; Step 2, restoring the stored backup user data to the user space corresponding to the target cloud machine in the server; Step 3: mount the path of the user data of the target cloud machine to the second storage path, and mount the path of the application data of the target cloud machine to the first storage path, wherein the storage space corresponding to the second storage path is the user space.

[0070] Through the above implementation method, after the cloud machine is backed up, the backed up cloud machine can be restored. For example, the user or administrator can send a restore instruction to the server through the cloud phone scheduling platform. The restore instruction is used to instruct the restoration of the data of the target cloud machine. After receiving the restore instruction, the server restores the stored backup user data to the user space corresponding to the target cloud machine in the server, and then mounts the path of the user data of the target cloud machine to the second storage path corresponding to the user space, and mounts the path of the application data of the target cloud machine to the first storage path corresponding to the cloud machine shared space. There is no need to restore the application data of the target cloud machine, thereby shortening the restoration time of the target cloud machine.

[0071] In an optional implementation, after mounting the path of the user data of the target cloud machine to the second storage path, and mounting the path of the application data of the target cloud machine to the first storage path, the method further includes: sending a restore instruction response message to the cloud phone scheduling platform, wherein the restore instruction response message is used to indicate the completion of the restoration of the target cloud machine.

[0072] In the embodiment of the present application, the server can send a restore command response message to the cloud phone scheduling platform, and indicate the completion of the restoration of the target cloud machine through the restore command response message. In this way, the cloud phone scheduling platform can learn that the target cloud machine has been restored, which helps the cloud phone scheduling platform to provide progress feedback to the user terminal.

[0073] In actual applications, there are two scenarios for restoration: one is the administrator restoring the cloud machine, and the other is the user restoring it himself. For cloud machine restoration, system applications and non-system applications are shared data and do not need to be restored. Just point the path of the target cloud machine's application data to its shared space. The server only needs to obtain user data from OBS and restore it to the cloud machine user space.

[0074] In the embodiments of the present application, Fig.11 To restore the cloud machine timing diagram for the operations administrator, you can include the following steps: Step 1101: Restore the target cloud machine parameters: userID+phoneID; the restore request initiated by the operation administrator to the cloud phone client carries the identification information corresponding to the target cloud machine, namely the user ID userID and the cloud machine ID phoneID.

[0075] Step 1102: Obtain user backup and shared data information according to userID and phoneID; the cloud phone client can determine the target cloud machine according to the user identifier userID and the cloud machine identifier phoneID, and then obtain the corresponding user backup and shared data information.

[0076] Step 1103: Restore the cloud machine; the cloud phone client can send a restore instruction to the target cloud machine.

[0077] Step 1104: Pull the backup user data according to the KEY userID:phoneID; in actual applications, the target cloud machine can pull the backup user data from the OBS storage according to the name of the corresponding backup user data (userID:phoneID).

[0078] Step 1105: Acquire the backup user data; the target cloud machine can obtain the backup user data by pulling.

[0079] Step 1106: Restore the backup; the target cloud machine can restore the backed-up user data.

[0080] Step 1107: Restore user data + mount cloud machine shared space; the backed-up user data can be restored to the user space and the application data can be mounted.

[0081] Step 1108: Restoration and mounting are completed; Step 1109: Restore response; the target cloud machine can notify the cloud phone scheduling platform that the restoration has been completed.

[0082] Step 11010: Restore response. The cloud phone scheduling platform can notify the operation administrator that the restoration of the target cloud machine has been completed. The administrator can directly select the cloud phone that needs to be restored on the cloud phone scheduling platform and initiate a restore request. The request carries the user ID userID and the cloud machine ID phoneID. The cloud phone scheduling platform obtains the backup information and shared resource information of the corresponding cloud machine based on the userID and phoneID, and notifies the corresponding cloud machine to prepare for restoration. Then the target cloud machine pulls the backup of the user data from the OBS object storage, finds the corresponding backup file through the file identifier userID:phoneID, and decompresses the backup and restores it to the user space. Then mount the cloud machine shared space, and the cloud machine restoration is completed.

[0083] In the embodiment of the present application, the user restores the cloud machine timing diagram as shown in Fig.12 As shown, the following steps may be included: Step 1201: Manually restore and change the cloud machine login; the user can manually log in to the cloud phone client. In actual application, other cloud machine accounts can be used to log in to the cloud phone client, and then restore the target cloud machine on the cloud phone client.

[0084] Step 1202: Restore the target cloud machine parameters: userID+phoneID; Step 1203: Obtain user backup and shared data information according to userID and phoneID; Step 1204: Restore the target cloud machine; Step 1205: Pull backup user data according to KEY userID:phoneID; Step 1206: Acquire backup user data; Step 1207: restore the backup; Step 1208: Restore user data + mount cloud machine shared space; Step 1209: Restoration and mounting are completed; Step 12010: restore response; Step 12011: restore response; Step 12012: Respond to the user.

[0085] In actual applications, users restore cloud machines through the cloud phone client. When the user initiates the restoration on the cloud phone client, the cloud phone client will forward the request with the user ID userID and the cloud machine ID phoneID to the cloud phone scheduling platform. The subsequent process is the same as the process for the administrator to restore the cloud phone.

[0086] In the embodiment of the present application, the restored data of the entire cloud machine includes three parts of data: system application data, non-system application data, and user data. Among them, system application data and non-system application data are shared data, which do not need to be pulled from the backup, but only need to be mounted to the shared space. As for user data, it is necessary to pull it from OBS and decompress it to the user space, and then mount the user data path to the user space, and finally realize the cloud machine restoration in seconds. The overall flow chart of restoring the cloud machine is as follows: Fig.13 shown.

[0087] In the embodiment of the present application, a cloud machine initialization instruction sent by a cloud phone scheduling platform can be received, wherein the cloud machine initialization instruction is used to instruct the target cloud machine to be initialized; the target cloud machine is initialized by mounting the path of the target cloud machine's application data to the first storage path, wherein the storage space corresponding to the first storage path is the cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server. In the above manner, the storage space overhead of the server can be reduced, the time for cloud machine initialization can be shortened, and the user experience can be improved.

[0088] In the embodiment of the present application, the real machine to the cloud machine, combined with the cloud phone scheduling platform and OBS storage, completes the entire shared storage business process, and its global architecture diagram is as follows Fig.14 As shown. Not only can storage space be saved, but the application installation data of each cloud machine is shared. The efficiency of opening cloud machines is improved. For new cloud machines, just point its mount path to the shared space to achieve the effect of quickly opening the cloud machine. Improve the efficiency of cloud machine backup and restore. The entire backup and restore only needs to target user personal data. There is no need to back up and restore application installation data. It only needs to be mounted to the shared space. For some large applications, it can save a lot of data transmission time.

[0089] The cloud machine initialization method provided in the embodiment of the present application can be executed by a cloud machine initialization device. In the embodiment of the present application, the cloud machine initialization device executing the cloud machine initialization method is taken as an example to illustrate the cloud machine initialization device provided in the embodiment of the present application.

[0090] Fig.15 The schematic diagram of the structure of the cloud machine initialization device provided by an exemplary embodiment of the present application is shown. The cloud machine initialization device can be implemented as follows Figure 2 All or part of the content in the illustrated embodiment, the cloud machine initialization device includes: a receiving module 1501 and an initialization module 1502.

[0091] In an embodiment of the present application, the receiving module 1501 is used to receive an initialization cloud machine instruction sent by a cloud phone scheduling platform, wherein the initialization cloud machine instruction is used to instruct the initialization of the target cloud machine; the initialization module 1502 is used to initialize the target cloud machine by mounting the path of the application data of the target cloud machine to a first storage path, wherein the storage space corresponding to the first storage path is a cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server.

[0092] In an optional implementation, the application data includes system application data and non-system application data.

[0093] In an optional implementation, the device also includes: a sending module, used to send an initialization cloud machine response message to the cloud phone scheduling platform, wherein the initialization cloud machine response message is used to indicate that the target cloud machine has completed initialization.

[0094] In an optional implementation, the cloud machine initialization instruction also carries identification information corresponding to the registration object; The receiving module 1502 is also used to: associate the identification information with the target cloud machine.

[0095] In an optional implementation, when the initialization module 1502 is used to initialize the target cloud machine, it is specifically used to: According to the identification information, the path of the user data of the target cloud machine is mounted to the second storage path, wherein the storage space corresponding to the second storage path is the user space of the server, and the user space is used to store the user data of the target cloud machine, and different cloud machines on the server correspond to different user spaces.

[0096] In an optional implementation, the receiving module is further used to receive application data sent by the cloud phone scheduling platform; The initialization module is also used to store the application data in the cloud machine shared space.

[0097] In an optional implementation, the receiving module is further used to receive a backup instruction sent by the cloud phone scheduling platform, wherein the backup instruction is used to instruct to back up the data of the target cloud machine; The device also includes: a backup module, which is used to obtain and store the backup user data of the target cloud machine by backing up the user data of the target cloud machine.

[0098] In an optional implementation, when the backup module is used to store the backup user data of the target cloud machine, it is specifically used to: The backup user data is stored in the object storage OBS.

[0099] In an optional implementation, the backup user data is identified by identification information corresponding to the target cloud machine.

[0100] In an optional implementation, the sending module is further configured to: A backup instruction response message is sent to the cloud phone scheduling platform, wherein the backup instruction response message is used to indicate that the backup of the target cloud machine is completed.

[0101] In an optional implementation, the receiving module 1501 is further used to: receive a restore instruction sent by the cloud phone scheduling platform, wherein the restore instruction is used to instruct to restore the data of the target cloud machine; The device further comprises: a restoration module, configured to restore the stored backup user data to a user space in the server corresponding to the target cloud machine; The restoration module is also used to mount the path of the user data of the target cloud machine to the second storage path, and to mount the path of the application data of the target cloud machine to the first storage path, wherein the storage space corresponding to the second storage path is the user space.

[0102] In an optional implementation, the sending module is further used to: send a restore instruction response message to the cloud phone scheduling platform, wherein the restore instruction response message is used to indicate the completion of the restoration of the target cloud machine.

[0103] The cloud machine initialization device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0104] The cloud machine initialization device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0105] The cloud machine initialization device provided in the embodiment of the present application can achieve Figure 1 To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0106] Alternatively, if Fig.16 As shown, an embodiment of the present application also provides an electronic device 1600, including a processor 1601 and a memory 1602, and the memory 1602 stores a program or instruction that can be executed on the processor 1601. When the program or instruction is executed by the processor 1601, the various steps of the above-mentioned cloud machine initialization method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0107] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0108] Fig.17 FIG. 1 is a block diagram of another electronic device 1700 according to an exemplary embodiment of the present application. The electronic device 1700 may be implemented as a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart watch, a TV, etc. The electronic device 1700 may also be called a user device, a portable terminal, a laptop terminal, a desktop terminal, etc.

[0109] Typically, the electronic device 1700 includes a processor 1701 and a memory 1702 .

[0110] The processor 1701 may include one or more processing cores, such as a 4-core processor, a 10-core processor, etc. The processor 1701 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 1701 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1701 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1701 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0111] The memory 1702 may include one or more computer-readable storage media, which may be non-transitory. The memory 1702 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 1702 is used to store at least one instruction, which is used to be executed by the processor 1701 to implement all or part of the steps in the cloud machine initialization method shown in the method embodiment of the present application.

[0112] In some embodiments, the electronic device 1700 may further optionally include: a peripheral device interface 1703 and at least one peripheral device. The processor 1701, the memory 1702 and the peripheral device interface 1703 may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface 1703 via a bus, a signal line or a circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1704, a display screen 1705, a camera assembly 1706, an audio circuit 1707 and a power supply 1708.

[0113] In some embodiments, the electronic device 1700 further includes one or more sensors 1709 , including but not limited to: an acceleration sensor 1710 , a gyroscope sensor 1711 , a pressure sensor 1712 , an optical sensor 1713 , and a proximity sensor 1714 .

[0114] Those skilled in the art will understand that Fig.17 The structure shown in the figure does not constitute a limitation on the electronic device 1700, and may include more or less components than those shown in the figure, or combine certain components, or adopt a different component arrangement.

[0115] An embodiment of the present application also provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned cloud machine initialization method are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0116] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0117] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned cloud machine initialization method, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0118] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0119] An embodiment of the present application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the steps of the above-mentioned cloud machine initialization method are implemented and the same technical effect can be achieved. To avoid repetition, they will not be repeated here.

[0120] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the claims.

[0121] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A cloud machine initialization method, characterized in that: include: Receive a cloud machine initialization instruction sent by a cloud phone scheduling platform, wherein the cloud machine initialization instruction is used to instruct to initialize a target cloud machine; The target cloud machine is initialized by mounting the path of the application data of the target cloud machine to the first storage path, wherein the storage space corresponding to the first storage path is the cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server.

2. The method according to claim 1, characterized in that The application data includes system application data and non-system application data.

3. The method according to claim 1, characterized in that After completing the initialization of the target cloud machine by mounting the path of the application data of the target cloud machine to the first storage path, the method further includes: An initialization cloud machine response message is sent to the cloud phone scheduling platform, wherein the initialization cloud machine response message is used to indicate that the target cloud machine has completed initialization.

4. The method according to claim 1, characterized in that The initialization cloud machine instruction also carries identification information corresponding to the registration object; After receiving the cloud machine initialization instruction sent by the cloud phone scheduling platform, the method further includes: Associate the identification information with the target cloud machine.

5. The method according to claim 4, characterized in that Initializing the target cloud machine includes: According to the identification information, the path of the user data of the target cloud machine is mounted to the second storage path, wherein the storage space corresponding to the second storage path is the user space of the server, and the user space is used to store the user data of the target cloud machine, and different cloud machines on the server correspond to different user spaces.

6. The method according to any one of claims 1 to 5, characterized in that: Before receiving the cloud machine initialization instruction sent by the cloud phone scheduling platform, the method further includes: Receiving the application data sent by the cloud phone scheduling platform; The application data is stored in the cloud machine shared space.

7. The method according to any one of claims 1 to 5, characterized in that: After initializing the target cloud machine, the method further includes: Receiving a backup instruction sent by the cloud phone scheduling platform, wherein the backup instruction is used to instruct to back up the data of the target cloud machine; By backing up the user data of the target cloud machine, the backup user data of the target cloud machine is obtained and stored.

8. The method according to claim 7, characterized in that The storing of the backup user data of the target cloud machine includes: The backup user data is stored in the object storage OBS.

9. The method according to claim 8, characterized in that The backup user data is identified by the identification information corresponding to the target cloud machine.

10. The method according to claim 8, characterized in that After acquiring and storing the backup user data of the target cloud machine, the method further includes: sending a backup instruction response message to the cloud phone scheduling platform, wherein the backup instruction response message is used to indicate that the backup of the target cloud machine is completed.

11. The method according to claim 8, characterized in that After acquiring and storing the backup user data of the target cloud machine, the method further includes: Receiving a restore instruction sent by the cloud phone scheduling platform, wherein the restore instruction is used to instruct to restore the data of the target cloud machine; Restoring the stored backup user data to the user space corresponding to the target cloud machine in the server; The path of the user data of the target cloud machine is mounted on the second storage path, and the path of the application data of the target cloud machine is mounted on the first storage path, wherein the storage space corresponding to the second storage path is the user space.

12. The method according to claim 11, characterized in that After mounting the path of the user data of the target cloud machine to the second storage path, and mounting the path of the application data of the target cloud machine to the first storage path, the method further includes: A restore instruction response message is sent to the cloud phone scheduling platform, wherein the restore instruction response message is used to indicate the completion of the restoration of the target cloud machine.

13. A cloud machine initialization device, characterized in that: include: A receiving module, used to receive a cloud machine initialization instruction sent by a cloud phone scheduling platform, wherein the cloud machine initialization instruction is used to instruct to initialize a target cloud machine; An initialization module is used to initialize the target cloud machine by mounting the path of the application data of the target cloud machine to a first storage path, wherein the storage space corresponding to the first storage path is a cloud machine shared space, and the cloud machine shared space stores application data shared by multiple cloud machines on the server.

14. The device according to claim 13, characterized in that The receiving module is further used to receive the application data sent by the cloud phone scheduling platform; The initialization module is also used to store the application data in the cloud machine shared space.

15. The device according to claim 13, characterized in that The receiving module is further used to receive a backup instruction sent by the cloud phone scheduling platform, wherein the backup instruction is used to instruct to back up the data of the target cloud machine; The device also includes: a backup module, which is used to obtain and store the backup user data of the target cloud machine by backing up the user data of the target cloud machine.

16. An electronic device, characterized in that: The electronic device includes a processor and a memory, the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the cloud machine initialization method as described in any one of claims 1 to 12 are implemented.

17. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, the steps of the cloud machine initialization method as described in any one of claims 1 to 12 are implemented.

18. A computer program product, characterized in that The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer executes the steps of the cloud machine initialization method as described in any one of claims 1 to 12.

Images