Cloud mobile phone service system and method based on mother-child architecture

Abstract

The invention relates to the technical field of computers, and discloses a cloud mobile phone service system and method based on a mother-child architecture, and the method comprises the steps that a mother machine receives and responds to the application start-stop operation of a user on a first target child machine through a second client, and sends an application start-stop instruction to the first target child machine, the application start-stop instruction carries an application unique identifier of a target application to be started and stopped, and the first target sub-machine is an associated sub-machine of the mother machine; and if the first target sub-machine receives the application start-stop instruction, enabling or closing the indicated local target application. According to the application, the start-stop control can be performed on any application of any sub-machine through the master machine, switching from one sub-machine to another sub-machine to perform the application start-stop control is not needed, and the application start-stop of the sub-machine can be completed through the master machine, so that the tedious operation is avoided, the operation convenience is improved, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a cloud phone service system and method based on a parent-child architecture. Background Art

[0002] Currently, clients can manage multiple cloud phones, but they can only access one cloud phone at a time. Multiple cloud phones operate independently. If you need to start or pause an application on another cloud phone after accessing one, you must exit the cloud device where the current session is located and then switch to the next cloud phone to start or stop the application. This method is cumbersome and inconvenient for users. Summary of the Invention

[0003] The main purpose of this application is to provide a cloud phone service system and method based on a parent-child architecture, aiming to solve the technical problem of cumbersome operations when starting and stopping cloud machine applications in the existing technology.

[0004] In a first aspect, the present application provides a cloud phone service system based on a parent-child architecture, the system comprising: a first client, a second client, a first server, a parent machine deployed on the first server, and a child machine associated with the parent machine, wherein the parent machine and the associated child machine are both cloud phones;

[0005] A first client, running on the user terminal and displayable on the terminal interface, is configured to receive and respond to a user's motherboard entry operation, enter and display the motherboard interface;

[0006] The second client runs on the master machine and can be displayed on the master machine interface;

[0007] The master device is configured to receive, through the second client, and respond to a user's application start / stop operation on the first target sub-device, and send an application start / stop instruction to the first target sub-device, wherein the application start / stop instruction carries an application unique identifier of the target application to be started / stopped, and the first target sub-device is an associated sub-device of the master device;

[0008] The first target sub-machine is configured to enable or disable the indicated local target application upon receiving the application enable / disable instruction.

[0009] The present application also provides a cloud phone service method based on a parent-child architecture, which is applied to a parent machine, on which a second client runs. The method includes:

[0010] receiving, through the second client, and responding to a user's application start / stop operation on the first target sub-machine, an application start / stop instruction is sent to the first target sub-machine, causing the first target sub-machine to enable or disable the indicated local target application, wherein the application start / stop instruction carries an application unique identifier of the target application to be enabled or disabled, and the first target sub-machine is an associated sub-machine of the master machine;

[0011] Among them, the first target sub-machine is the associated sub-machine of the mother machine. The mother machine and its associated sub-machines are deployed on the first server. The mother machine interface can be displayed through the first client running on the user terminal. The mother machine interface displayed on the first client can be operated through the first client. The first client runs on the user terminal and can be displayed on the terminal interface of the user terminal. The second client can be displayed on the mother machine interface. The second client displayed on the mother machine interface can be operated through the mother machine interface. The sub-machine interface of the associated sub-machine can be displayed through the second client. The sub-machine interface displayed on the second client can be operated through the second client.

[0012] The third aspect of the present application provides a computer device, comprising: a memory and at least one processor, wherein instructions are stored in the memory; at least one processor calls the instructions in the memory so that the computer device executes the above-mentioned cloud phone service method based on the parent-child architecture.

[0013] The fourth aspect of the present application provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is run on a computer, it enables the computer to execute the above-mentioned cloud phone service method based on the parent-child architecture.

[0014] This application provides an application start-stop control solution based on a cloud phone master-submachine architecture. The master machine can receive and respond to the user's application start-stop operation through a second client to instruct the target submachine to start and stop the target application. This application can start and stop any application on any submachine through the master machine, eliminating the need to switch from one submachine to another to start and stop the application. The master machine can complete the start and stop of the submachine's application through the master machine, eliminating tedious operations, improving operational convenience, and enhancing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a functional module diagram of an embodiment of a cloud phone service system based on a parent-child architecture in an embodiment of the present application;

[0016] Figure 2 This is a schematic diagram of the display levels of each terminal interface in the embodiment of the present application;

[0017] Figure 3 This is a schematic diagram of a mother machine interface in one embodiment of the present application;

[0018] Figure 4 This is a schematic diagram of the interface of the second client in one embodiment of the present application;

[0019] Figure 5 This is a schematic diagram of the interaction structure of each module on the server side of Example 1 of the present application;

[0020] Figure 6This is a schematic diagram of the mother-child service logic of Example 1 of the present application;

[0021] Figure 7 This is a schematic diagram of the start-stop interaction process of the mother-child machine application in Example 1 of the present application;

[0022] Figure 8 This is a flow chart of an embodiment of a cloud phone service method based on a parent-child architecture in an embodiment of the present application. DETAILED DESCRIPTION

[0023] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" or "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0024] In the existing technology, cloud phones are all run independently. When you need to start or stop non-system applications on another cloud phone device, you need to exit the currently operating cloud phone and switch to another cloud phone to operate. This method is cumbersome to operate, and frequent switching of cloud phone devices leads to a poor user experience.

[0025] Based on this, the present application provides a cloud phone service based on a parent-child architecture, wherein the service includes an application start-stop control service based on the cloud phone parent-child architecture.

[0026] refer to Figure 1 In one embodiment of the present application, a cloud phone service system based on a parent-child architecture is provided, the system comprising: a first client, a second client, a first server 20, a parent machine 21 deployed on the first server 20, and a child machine 22 associated with the parent machine 21, wherein the parent machine 21 and the associated child machine 22 are both cloud phones;

[0027] The first client runs on the user terminal 10 and can be displayed on the terminal interface, and is used to receive and respond to the user's motherboard entry operation, enter and display the motherboard interface;

[0028] The second client runs on the master machine 21 and can be displayed on the master machine interface;

[0029] The master device 21 is configured to receive, through the second client, and respond to a user's application start / stop operation on the first target child device, and send an application start / stop instruction to the first target child device, wherein the application start / stop instruction carries the application unique identifier of the target application to be started / stopped. The first target child device is the associated child device 22 of the master device 21;

[0030] The first target sub-machine is configured to enable or disable the indicated local target application upon receiving the application enable / disable instruction.

[0031] Specifically, this application provides a cloud phone parent-child architecture, in which the parent-child combination of a cloud phone is a special cloud phone service combination, including a master parent machine 21 and at least one controlled associated child machine 22. The parent machine 21 has management and control rights over the associated child machines 22, enabling the issuance of a variety of operating instructions to meet the needs of different scenarios, such as batch account management and automated task execution.

[0032] The cloud phone service system based on the parent-child architecture includes an application layer, a business layer and a support layer, wherein the application layer includes a first client and a second client, the business layer includes a parent machine 21 and its associated child machine 22, and the support layer includes a service platform module of the first server 20.

[0033] The first server 20 may be a cloud server, and the master machine 21 and its associated slave machines 22 are deployed on the first server 20. Multiple master machines 21 and their associated slave machines 22 may be deployed on the first server 20, and this application does not impose any restrictions on this.

[0034] The first client runs on the user terminal 10 and can be displayed on the terminal interface. It is used to receive and respond to the user's motherboard entry operation, enter and display the motherboard interface. The first client provides an operation entry for the motherboard 21. In addition, the system may also include the user terminal 10.

[0035] In a specific embodiment, the mother machine interface displayed on the first client is specifically a screenshot of the video stream of the mother machine 21. After the mother machine 21 is assigned to the user, the mother machine 21 will push the stream to the user's first client, and the first client will capture the video frame in the push stream screen for display.

[0036] The first client is coupled to the second server; the server side of the first client is located on the second server. The system may include the second server.

[0037] The second client runs on the host machine 21 and can be displayed on the host machine interface. It is a cloud phone program running on the host machine 21.

[0038] The server side of the second client is located on the first server 20 .

[0039] The second client provides an operation portal for the slave.

[0040] The user terminal 10 may be a physical mobile phone or tablet, etc.

[0041] Both the master machine 21 and the slave machine are cloud machines or cloud phones.

[0042] Figure 2 This is a schematic diagram of the display levels of each terminal interface in the embodiment of this application, refer to Figure 2 A first client is installed on the user terminal 10. The user terminal 10 can access the first client, and the first client can be used to access the master interface of any master 21. A second client is installed on the master 21. Therefore, by operating the second client on the master interface, the user can access the slave interface of a related slave 22.

[0043] Since the second client is installed on the mother machine 21, the mother machine 21 can receive and respond to the user's application start and stop operations on the first target child machine through the second client, and respond to the application start and stop operations to achieve the purpose of enabling or disabling any application on any child machine.

[0044] The user can apply for at least one master phone 21 and at least one slave phone for each master phone 21 . That is, one master phone 21 can manage at least one slave phone, and the slave phones managed by the master phone 21 are all associated slave phones 22 of the master phone 21 .

[0045] The master machine 21 and the slave machine are both cloud phones (or cloud machines). The master machine 21 and the slave machine are both deployed on a server or cloud server or cloud machine server on the server side. The cloud machine server can be an ARM architecture blade server.

[0046] The first client is a first application terminal, which runs on the user terminal 10 or a local terminal and can be displayed on the terminal interface of the user terminal 10. The user terminal 10 is, for example, a physical mobile phone or tablet held by the user, and this application does not limit this.

[0047] The first client can be, for example, an application or APP, a PC interface or a web page, or a mini-program (for example, a small application or page or H5 mini-program developed based on HTML5 technology), etc. This application does not impose any restrictions on this.

[0048] The user can enter and display the master machine interface through the first client by operating the first client. Among them, the user can apply for at least one master machine 21, the user can manage at least one master machine 21 through the first client, and each master machine 21 can manage at least one slave machine.

[0049] The cloud phone can be displayed as a large picture on the first client, or displayed in a 4-grid on the first client, or displayed in a 9-grid on the first client, or displayed in a 16-grid on the first client, etc. This application does not impose any restrictions on this.

[0050] When the cloud phone is displayed in a large image on the device management page of the first client, different cloud phones can be switched and displayed on the first client by sliding the phone screen left and right.

[0051] When cloud phones are displayed in a 4-grid format, up to 4 cloud phones can be displayed on one interface. If the user has ordered more than 4 cloud phones, all cloud phones can be displayed through multiple interfaces, with up to 4 cloud phones displayed on each interface. You can switch to different display interfaces by turning pages.

[0052] When cloud phones are displayed in a 9-grid format, a maximum of 9 cloud phones can be displayed on one screen; when cloud phones are displayed in a 16-grid format, a maximum of 16 cloud phones can be displayed on one screen.

[0053] The user can determine the display effect of each cloud phone by selecting the option in "Display Mode" on the first client. Among them, the options in "Display Mode" include large picture, 4-grid, 9-grid, 16-grid and list, etc. This application does not limit this.

[0054] In a specific embodiment, only the respective master devices 21 may be displayed on the device management page of the first client. Then, by selecting and entering a master device 21, its associated slave devices 22 may be displayed in the master device 21.

[0055] In another specific embodiment, the device management page of the first client can display both the master device 21 and the slave devices. By selecting a master device 21, the slave devices can be displayed on the master device 21; alternatively, a slave device can be directly selected from the device management page, and the user can directly display and operate the slave device through the second client.

[0056] Regardless of the display effect of the cloud phone on the interface, the user can select one of the cloud phones from the display interface and operate the cloud phone after entering the cloud phone, realizing the function of displaying the cloud phone screen through the real user terminal 10 (such as a mobile phone).

[0057] In a specific embodiment, the bottom of the first client includes multiple options such as "Cloud Phone", "Discover" and "My". The user can enter the cloud phone display interface (i.e., the device management page) by clicking the "Cloud Phone" option. The cloud phone display interface includes three options: "Sort", "Display Mode" and "Filter". The "Sort" option can be used to select the display priority of all cloud phones on the display interface. For example, if you select "Sort by Application Date", the latest applied cloud phone can be displayed in the front row of the display interface, and the cloud phones applied for earlier can be displayed in the back row. Of course, the reverse sorting is also possible, and this application does not limit this.

[0058] The "Filter" option can be used to filter some cloud phones that need to be displayed, and hide some cloud phones that are not displayed temporarily. For example, by filtering, only the main phone 21 or only the sub-phones or only one main phone 21 and its associated sub-phones 22 can be displayed. This application does not limit this.

[0059] Figure 3 This is a schematic diagram of the mother machine interface in one embodiment of the present application; Figure 3 ,exist Figure 3 It shows that you can find a cloud machine (cloud phone) with the "master machine 21" logo on the device management page of the first client, click it and enter the master machine interface of master machine 21. Figure 3 Specifically, the desktop of a mother machine 21 is displayed. On the desktop, a second client is displayed: the "child console" APP. The second client runs on the mother machine 21. The mother machine 21 is equivalent to a virtual phone as a cloud phone and can install various applications or APPs or clients. For example, Figure 3 Non-system applications such as "** Input Method" APP, "** Browser" APP and "** File Browser" APP are also installed on the middle mother machine 21. In addition, some system applications are also installed on this mother machine 21.

[0060] It should be noted that the user can install any APP or application on the master machine 21 or the slave machine as needed, and this application does not impose any restrictions on this.

[0061] On the master machine 21, the second client: the "parent-child console" can also be opened through a small program or a web page, and this application does not impose any restrictions on this.

[0062] After entering the mother machine interface from the first client, the user can operate the mother machine 21 just like operating a physical mobile phone, for example, open the APP on the mother machine 21, log in to the APP, operate the APP on the mother machine 21, download and install the APP on the mother machine 21, uninstall the APP, etc. This application does not impose any restrictions on this.

[0063] The master machine 21 can manage and control its associated slave machine 22 through the installed second client.

[0064] More specifically, the master machine 21, through its installed second client, can receive user commands to start or stop applications on any associated slave machine 22. That is, the user can access the master machine interface through the first client, then click on the second client from the master machine interface to access the second client. On the second client, the user can select to start or stop applications on a slave machine.

[0065] Through the application start / stop operation, the user specifies which applications of which sub-machine need to be started or closed (paused). Therefore, after the master machine 21 receives the user's application start / stop operation on the first target sub-machine through the second client, it responds to the application start / stop operation and sends an application start / stop instruction to the first target sub-machine.

[0066] After receiving the application start / stop instruction, the first target sub-machine starts and / or shuts down the designated target application.

[0067] The master device 21 can control the new slave device through the second client.

[0068] In the existing technology, there is no way to start and stop the applications of other cloud machines (cloud phones) when operating a cloud phone. This embodiment is based on the advantages of the mother and child machines. By operating the mother machine 21, the applications of the child machine can be directly started and stopped. When operating the cloud machine, any application of any cloud machine can be enabled or disabled without exiting the cloud machine.

[0069] This embodiment leverages the advantages of the parent-child machine architecture to enable users to independently start and stop cloud machine applications, thereby improving user experience.

[0070] In this embodiment, the master device 21 receives and responds to the user's application start / stop operations through the second client, thereby instructing the target slave device to start / stop the target application. In this embodiment, the master device 21 can control the start / stop of any application on any slave device. This eliminates the need to switch from one slave device to another to start / stop applications. Application start / stop operations on the slave devices can be completed directly through the master device 21, eliminating tedious operations, improving operational convenience, and enhancing the user experience.

[0071] In one embodiment, the master machine 21 is specifically configured to receive, through the second client, and respond to a user's application start / stop selection operation on the first target slave machine, and send an application list and status query request to the first target slave machine;

[0072] The first target sub-machine is specifically configured to query local applications and application status upon receiving an application list and status query request, and send the application and status query results to the main machine 21;

[0073] The master machine 21 is specifically configured to display the application list and application status of the first target slave machine to the user through the second client based on the application and status query results of the first target slave machine;

[0074] The master machine 21 is specifically configured to receive, through the second client, and respond to a user's designated operation on a target application to be started or stopped in the application list, generate and send an application start or stop instruction to the first target slave machine.

[0075] Specifically, Figure 4 This is a schematic diagram of the interface of the second client in one embodiment of the present application; Figure 4 , take the second client as the parent-child console APP as an example, click on the parent machine interface to enter the second client and then enter Figure 4 The left image in the figure shows the main operation interface of the parent-child console app. This interface provides multiple operational options, such as "Open slave preview" and "Slave control" with "Application start / stop" sub-options, as well as "File transfer," "Change cloud machine," and "Backup / restore" sub-options. The sub-options under "Slave control" allow you to remotely control slaves to perform tasks.

[0076] The general operation interface may further include a "Help" option, and the "Help" option includes "Help" sub-options.

[0077] Each of the above sub-options can be displayed in the form of pictures (pic) or icons on the main operation interface. The user clicks the "application start / stop" sub-option on the main operation interface to execute the application start / stop selection operation.

[0078] The master machine 21 receives and responds to the user's application start / stop selection operation on the first target sub-machine through the second client, and sends an application list and status query request to the first target sub-machine to obtain the application list or application list of the first target sub-machine and the current application status of each application.

[0079] If the first target sub-machine receives the application list and status query request, it queries the local application and application status, and sends the application and status query result to the mother machine 21, wherein the application and status query result includes the local application list of the first target sub-machine and the current status of the application; the application list includes the application unique identifier of the local application of the first target sub-machine.

[0080] Based on the application and status query results of the first target sub-machine, the master machine 21 displays the application list of the first target sub-machine and the current application status of each application to the user through the application start and stop interface of the second client. The application list can list each application that can be started and stopped by the first target sub-machine in the form of icons.

[0081] The user can select one or more applications from the application list to start (enable) or close (temporarily disable).

[0082] The master machine 21 receives and responds to the user's designated operation (i.e., selection operation) of the target application to be started or stopped in the application list through the second client, generates an application start or stop instruction, and sends the application start or stop instruction to the first target slave machine. The application start or stop instruction carries the application unique identifier of the target application to be started or stopped.

[0083] In this embodiment, after the mother machine 21 receives the application start / stop selection operation through the second client, it requests the first target child machine to obtain the application list and application status. After obtaining the application list and application status, the mother machine 21 will display them to the user through the second client, so that the user can select any one or more target applications to be started or stopped, and determine whether each target application is started or closed, thereby realizing the convenience of starting and stopping applications.

[0084] In one embodiment, the application state is an enabled state or a disabled state;

[0085] The master machine 21 is specifically configured to display a list of enabled applications and a list of disabled applications of the first target slave machine to the user through the second client based on the application status;

[0086] The mother machine 21 is specifically used to receive through the second client and send an application closing instruction to the first target child machine in response to the user's selection operation for the target application to be closed in the list of enabled applications, and / or receive through the second client and send an application enabling instruction to the first target child machine in response to the user's selection operation for the target application to be enabled in the list of closed applications.

[0087] Specifically, the application start / stop interface may have two options: "Start Application" and "Close Application". If the user clicks the "Start Application" option, the "Start Application" interface will display a list of closed applications, which includes applications that can be started by the first target sub-machine, where the current application status of the startable applications is closed. If the user clicks the "Close Application" option, the "Close Application" interface will display a list of enabled applications, which includes applications that can be closed by the first target sub-machine, where the current application status of the closeable applications is started (or already started).

[0088] In the list of closed applications, the user can select one or more target applications to be enabled. In the list of enabled applications, the user can select one or more target applications to be disabled.

[0089] The application of this embodiment is specifically an application program or APP installed on the slave or master machine 21 .

[0090] This embodiment displays applications in different application states by category, and can systematically display different applications to the user, making it easier for the user to correctly select an application to be started or closed, and avoiding misselection.

[0091] In one embodiment, the first target sub-machine is specifically configured to, upon receiving an application list and status query request, filter local system applications, query the application status of local non-system applications, and send the application and status query results of the local non-system applications to the master machine 21;

[0092] The master machine 21 is specifically configured to display the non-system application list and application status of the first target slave machine to the user through the second client.

[0093] Specifically, both the master device 21 and the slave devices have system applications and non-system applications installed. Because system applications are crucial, erroneous activation or deactivation can cause malfunctions in the master device 21 or the slave devices. To protect the master device 21 and the slave devices, this embodiment only allows users to activate or deactivate non-system applications.

[0094] The first target child machine filters out local system applications, searches only for local non-system applications and the corresponding current application states, and then sends them to the master machine 21 .

[0095] The master machine 21 displays only the non-system applications and their application states of the first target slave machine to the user through the second client.

[0096] In one embodiment, the first target sub-machine is further configured to send application status update feedback to the master machine 21 after completing the start and stop of the target application;

[0097] The master machine 21 is further configured to display the application list and updated application status of the first target slave machine to the user through the second client upon receiving application status update feedback.

[0098] Specifically, after the first target slave starts or shuts down the target application, the application state of the target application will change. The first target slave will send application state update feedback to the master 21. This feedback can not only inform the master 21 whether the start / stop operation is completed, but also update the master 21 with the latest application state of the target application in a timely manner.

[0099] The master machine 21 may update the application status of the application of the first target slave machine displayed by the second client according to the application status update feedback, thereby timely feeding back the application start / stop effect to the user.

[0100] In one embodiment, the master machine 21 is specifically configured to display the application start / stop interface to the user through the second client upon receiving an application start / stop selection operation from the user through the main operation interface of the second client;

[0101] or,

[0102] The master device 21 is specifically configured to, upon receiving a user's selection operation to open a preview of a sub-device via the second client, access and display to the user a sub-device preview interface of the second target sub-device via the second client, wherein a control panel may be displayed on the sub-device preview interface, and the control panel may include sub-options for starting and stopping applications.

[0103] If the control panel receives an application start / stop selection operation from the user, the second client terminal displays an application start / stop interface to the user.

[0104] The master machine 21 is further configured to send an application start / stop instruction to the first target slave machine if an application start / stop confirmation operation of the user is received through the application start / stop interface of the second client.

[0105] Specifically, Figure 4 This is a schematic diagram of the interface of the second client in one embodiment of the present application; Figure 4 , take the second client as the parent-child console APP as an example, click on the parent machine interface to enter the second client and then enter Figure 4 The left image in the figure shows the main operation interface of the parent-child console app. This interface provides multiple operational options, such as the "Open slave preview" option, the "" sub-option within the "slave control" option, and the "File transfer" sub-option, the "Change cloud machine" sub-option, and the "Backup and restore" sub-option. The sub-options under the "slave control" option allow you to remotely control slaves to perform tasks.

[0106] The general operation interface may further include a "Help" option, and the "Help" option includes "Help" sub-options.

[0107] Each of the above sub-options can be displayed in the form of pictures (pic) or icons on the main operation interface. The user can enter the application start and stop interface by clicking the "application start and stop" sub-option on the main operation interface.

[0108] In addition, after the user clicks the "Open Sub-machine Preview" option, he can enter the preview interface of a related sub-machine 22 from the main operation interface, as shown in the following example. Figure 4 The preview interface can also include a control panel, which contains the operational options of the general operation interface: "File Transfer", "Application Start and Stop", "Change Cloud Machine", and "Backup and Restore".

[0109] Through this control panel, when previewing the sub-machine through the second client, the main machine 21 can still perform functions such as "file transfer", "application start and stop", "change cloud machine", "backup and recovery" without exiting the current sub-machine preview interface.

[0110] Therefore, the user can also enter the application start and stop interface by clicking the "Application Start and Stop" sub-option on this control panel.

[0111] In addition, the control panel can also be hidden in the sub-machine preview interface in a folded form, or the control panel can be closed on the sub-machine preview interface so that the control panel does not block the complete display effect of the sub-machine interface. More specifically, a "Close" button and a folding and expanding control are provided on the control panel. The user clicks the "Close" button to close the control panel so that the control panel is no longer displayed on the sub-machine interface. When the control panel is displayed on the sub-machine interface, the user clicks the folding and expanding control to fold the control panel. After the control panel is folded, click the folding and expanding control again to fully display the control panel again. The control panel can be displayed in a floating form at any position on the sub-machine interface, for example, below, above, etc.

[0112] In the application start / stop interface, the user can select any slave managed and associated by the master 21 as the first target slave. Alternatively, if the application start / stop interface is entered from the control panel, the first target slave defaults to the currently previewed slave.

[0113] On the application start / stop interface, the user's selected first target sub-phone ID, such as "012345678912345678," can be displayed. The application start / stop interface can also display the service expiration time of the first target sub-phone, such as the expiration time of the first target sub-phone after 802 days and 13 hours.

[0114] In addition, on the application start and stop interface, the second client can also display the "Start application" option and the "Close application" option to the user. Above these two options, a text description "Please select the operation type" can be set to instruct the user to select the application to be started or the application to be closed from the two options.

[0115] The application start / stop interface is also provided with a "Confirm" button. When the user clicks the button, the master machine 21 will send an application start / stop instruction to the first target slave machine.

[0116] The master machine 21 provides two application start and stop entrances through the second client, which facilitates users to start and stop applications under different usage conditions.

[0117] In this embodiment, the application start / stop interface can be accessed through the main operation interface or control panel of the second client, allowing the user to start / stop applications. In this embodiment, application start / stop operations can be performed while previewing a sub-machine without exiting the preview. In this embodiment, applications can also be started / stopped on any cloud machine through the main operation interface of the second client of the master machine 21, without having to exit one cloud machine and enter another to start / stop applications, thus realizing efficient and convenient application start / stop functions for cloud machines.

[0118] In one embodiment, the master device 21 is specifically configured to, upon receiving an application start / stop selection operation from a user via the main operation interface of the second client, display an application start / stop interface to the user via the second client; and upon receiving a selection operation for a first target slave device and a target application to be started / stopped, as well as a first confirmation operation from the user via the application start / stop interface of the second client, send an application start / stop instruction to the first target slave device;

[0119] or,

[0120] The mother machine 21 is specifically used to display the application start / stop interface to the user through the second client if the user's application start / stop selection operation is received through the main operation interface of the second client; if the user's selection operation for the first target sub-machine and the target application to be started / stopped and the first confirmation operation are received through the application start / stop interface of the second client, the application start / stop prompt is displayed to the user through the second client; if the user's second confirmation change operation start / stop re-confirmation feedback result (response) is received through the second client, the application start / stop instruction is sent to the first target sub-machine.

[0121] Specifically, the application start / stop interface includes a slave selection option and a "Confirm" button. The user can select a slave as the first target slave from the slave selection option. After selecting the target application to be started / stopped, if the user clicks the "Confirm" button, the master device 21 will send the application start / stop instruction to the first target slave.

[0122] Of course, in order to ensure that the user is fully aware of the application start and stop, to avoid user misoperation, which may cause the application to work incorrectly or be interrupted by mistake. In another embodiment, after the user clicks the "Confirm" button, an application start and stop prompt pop-up window or a start and stop re-confirmation interface will pop up, and the application start and stop prompt will be displayed in the application start and stop prompt pop-up window or start and stop re-confirmation interface. The application start and stop prompt is, for example: Confirm to start the selected application? Or, Confirm to close the selected application? There are also "Cancel" and "Confirm" buttons on the application start and stop prompt pop-up window or start and stop re-confirmation interface. When the user clicks the "Confirm" button, the second confirmation operation is performed. If the user clicks the "Cancel" button, the start and stop of the application is canceled.

[0123] This embodiment sets a confirmation option, and can send a start / stop instruction after the user confirms to start / stop the application, thereby preventing the application from being started or stopped by mistake.

[0124] In one embodiment, the mother machine 21 is also used to receive and respond to the user's sub-machine preview operation on the first target sub-machine through the second client, obtain the target video stream picture of the sub-machine local collected by the first target sub-machine, process the target video stream picture and then display it through the second client, wherein the second client is displayed on the mother machine interface.

[0125] Specifically, if Figure 4The center-left image shows the main interface of the parent-child console app, which features multiple options, including "Open Sub-device Preview." After the user selects a target sub-device on the secondary client, they enter the main interface and click "Open Sub-device Preview" to display a preview of the target sub-device on the secondary client. Alternatively, if a sub-device selection option is provided on the main interface, the user can select a target sub-device on the main interface and click "Open Sub-device Preview" to display a preview of the target sub-device on the secondary client.

[0126] The above operation is the sub-machine preview operation performed by the user on the target sub-machine.

[0127] The master machine 21 includes a picture acquisition module, and the slave machine includes a video stream acquisition module.

[0128] In response to the preview operation of the slave, the master 21 obtains the local target video stream image of the target slave from the target slave through the image acquisition module, wherein the target video stream image is acquired by the video stream acquisition module of the target slave.

[0129] In a specific embodiment, the video stream acquisition module of the slave machine will only acquire the local video stream image after receiving the video acquisition instruction or notification from the master machine 21. The video acquisition instruction or notification may be issued by the image acquisition module of the master machine 21.

[0130] In another specific embodiment, the video stream acquisition module of the slave machine can acquire local video stream images in real time and wait for the master machine 21 to call.

[0131] The image acquisition module of the master machine 21 also processes the acquired target video stream, such as denoising and rendering, and then displays it through the second client. Since the second client runs on the master machine 21 and is displayed on the master machine interface, the preview image of the slave machine is actually displayed on the second client interface on the master machine interface.

[0132] This embodiment uses the mother-child machine architecture to achieve the purpose of having the mother machine 21 pull the child machine video stream from the child machine and then display the child machine screen on the mother machine 21 screen.

[0133] In this embodiment, the slave machine performs local video capture, and the master machine 21 obtains the video stream from the slave machine, processes it, renders it, and displays it through the second client, thereby realizing a preview display of the slave machine interface based on the master-slave machine architecture.

[0134] In current cloud phone usage scenarios, users are often limited by the performance and functionality of a single cloud phone, making it difficult to efficiently perform multi-tasking operations or complex business processes. For example, for office users, a single cloud phone cannot easily achieve multi-device collaboration, such as the inability to flexibly manage files across different devices. For gamers, a single cloud phone cannot simultaneously meet the different performance requirements of running game scripts and the smooth running of the game itself, resulting in lag or account suspension due to device performance bottlenecks or platform security detection.

[0135] Before the concept of cloud phone parent-child phones was proposed, similar problems were mainly solved by operating multiple independent cloud phones separately. Although multiple independent cloud phones can share tasks to a certain extent, the following problems still exist:

[0136] 1. There's a lack of efficient coordination between devices, making it difficult to centrally control one device from another. For example, transferring files from one cloud phone to another requires cumbersome external storage or complex network sharing settings.

[0137] 2. The screen cannot be conveniently shared and displayed on different cloud phones, and users cannot intuitively monitor the operation of another cloud phone through one cloud phone.

[0138] This application provides a cloud phone service system based on a parent-child architecture to solve the problems of inconvenient operation and lack of centralized management and control of multiple independent cloud phones.

[0139] In one embodiment, the system further includes a user terminal, the user terminal being in communication with the first server.

[0140] The user terminal is used to obtain the control authority of the parent and child cloud phones of the first server, and the first server is used to allocate the control authority of the parent machine and at least one associated child machine to the user terminal, wherein the parent machine is used to interact with each associated child machine, and the configuration of the parent machine is higher than the configuration of the associated child machine.

[0141] In one embodiment, the first server includes a control module, a slave service module, and a service platform module that are communicatively connected, wherein the master machine includes the control module, the associated slave machine includes the slave service module, and the user terminal is communicatively connected to the control module;

[0142] The master machine is used to send a slave machine service driving instruction to the slave machine service module through the control module, and the slave machine service module is used to perform corresponding operations based on the received slave machine service driving instruction.

[0143] In one embodiment, the service platform module is used to match idle cloud phones to user terminals based on the available resource pool of the first server and the device attributes of the user terminal, wherein relatively high-configuration cloud phones serve as master phones and relatively low-configuration cloud phones serve as associated slave phones, and unique identifiers of the master phone and the slave phone are assigned to the user terminal.

[0144] In one embodiment, the slave machine service module includes a video stream acquisition submodule, and the slave machine service module is further configured to call the video stream acquisition submodule to obtain the slave machine's image and generate a video stream, and transmit the video stream to the control module in real time;

[0145] The control module includes a picture acquisition submodule, and the control module is further used to call the picture acquisition submodule, receive the video stream sent by the sub-machine service module, decode the video stream and render it to the second client.

[0146] Specifically, the mother machine renders and displays the sub-machine video stream screen to the user terminal through the control module, and specifically displays the sub-machine video stream screen through the second client of the mother machine. Among them, the mother machine interface is displayed on the user terminal, which is equivalent to the user terminal displaying the sub-machine video stream screen through the first client, the first client through the mother machine, and the mother machine displaying the sub-machine video stream screen through the second client.

[0147] In one embodiment, the sub-machine service module includes a data storage sub-module, and the sub-machine service module is further configured to call the data storage sub-module to classify and store data in the associated sub-machine according to preset rules;

[0148] The control module includes a file storage submodule, which is also used to call the file storage submodule, the data transmission function of the service platform module and the data storage submodule in the slave service module to back up the data stored in the slave to the master, or restore the backup data of the master to the slave.

[0149] In one embodiment, the service platform module includes a resource allocation sub-module. Before backing up the data stored in the sub-machine to the main machine, the service platform module is also used to call the resource allocation sub-module, read the storage space of the main machine, and determine whether the free storage space meets the storage requirements of the backup data; if so, the coordination control module performs the backup; if not, a prompt of insufficient space is fed back to the user terminal.

[0150] Specifically, the user terminal displays a first client, the first client displays a motherboard interface, the motherboard interface displays a second client, and the insufficient space prompt is fed back to the user through the second client.

[0151] In one embodiment, before restoring the backup data of the parent machine to the associated child machine, the service platform module is also used to call the resource allocation function, read the storage space of the child machine, and determine whether the free storage space is sufficient to restore the backup data; if so, the coordination control module performs the restoration; if not, a prompt of insufficient space is fed back to the user terminal.

[0152] Specifically, the user terminal displays a first client, the first client displays a motherboard interface, the motherboard interface displays a second client, and the insufficient space prompt is fed back to the user through the second client.

[0153] In one embodiment, the control module includes an application running submodule, and the control module is further configured to call the application running submodule and send an application control instruction to the slave service module;

[0154] The slave machine service module includes a control instruction parsing submodule,

[0155] The sub-machine service module is also used to call the control instruction parsing sub-module, receive the application control instructions sent by the control module, parse the application control instructions, and control the application running status of the associated sub-machine according to the parsing results; the control module is also used to call the application running sub-module, monitor the application running status in the associated sub-machine, and feed back the running status to the user terminal.

[0156] In one embodiment, the service platform module is also used to receive a request from a user terminal to replace a cloud machine, match an idle cloud phone as a new sub-machine to the user terminal based on the available resource pool of the first server and the device attributes of the old sub-machine, and assign the identity of the new sub-machine to the user terminal.

[0157] In one embodiment, the service platform module is further configured to delete the identity of the old sub-machine from the user terminal, clear the data in the old sub-machine, and recycle the data to the available resource pool of the first server.

[0158] In the embodiment of the present application, the parent-child architecture is innovatively applied to the cloud phone service, forming a cloud phone mother-child machine mode, wherein the mother-child architecture (Mother-Child Architecture) is a system design pattern, which is usually used in distributed systems or service management. This architecture consists of two parts: a mother node (Mother Node), which is responsible for overall coordination and management, monitoring the status and health of child nodes, assigning tasks to child nodes, and may have a fault recovery mechanism; a child node (Child Node), which performs specific tasks and reports status to the mother node. The cloud phone mother-child machine mode can be understood as treating the cloud phone responsible for control as the mother node in the mother-child architecture, that is, as the mother machine 21; and the controlled cloud phone as the child node in the mother-child architecture, that is, as the associated child machine 22.

[0159] In the embodiments of the present application, user terminal 10 refers to the end that initiates requests and receives services in a computer network, typically a device or software directly operated by a user. User terminal 10 can be in the form of hardware, specifically a mobile terminal (smartphone or tablet), a desktop terminal (PC or laptop), or an embedded device (smart TV or IoT sensor). User terminal 10 can also be in the form of software, specifically a native application (iOS / Android app or Windows software), a browser (Chrome or Safari), or a command line tool (such as curl or Postman).

[0160] Since the operation of the mother-child machine or cloud phone needs to rely on a user terminal 10 to be used. For example, if you use online payment operations, you need to rely on a client that provides payment functions. Similarly, the operation of the mother-child machine or cloud phone also requires a user terminal 10 to provide an operation entrance.

[0161] The first server 20 can be a physical first server, a cloud first server, or a virtual first server. If the first server 20 is a physical first server (for example, a physical server with an ARM architecture), it can be understood that the physical server includes multiple computing chips, which include multiple host machines. Each host machine includes multiple cloud phone instances, and the parent machine 21 and the associated child machines 22 can be determined from these cloud phone instances. In the embodiment of the present application, the first server 20 takes a cloud server (such as a cloud server with an ARM architecture) as an example to illustrate a cloud phone service system based on a parent-child architecture.

[0162] In an embodiment of the present application, the user terminal 10 is connected to the first server 20 for communication. The core of the communication is the protocol selection and the data exchange format. The real-time, security and performance can be weighed according to the scenario to select the appropriate communication protocol and data exchange format. A variety of methods can also be mixed, such as HTTP application program interface (API) + WebSocket protocol for communication.

[0163] In an embodiment of the present application, a user can purchase a mother-child phone package through the user terminal 10. After the purchase is completed, the first server 20 will allocate the mother-child cloud phones, and allocate the control authority of the allocated mother-child cloud phones to the user terminal 10, as well as allocate the control authority of the mother phone 21 and at least one associated child phone 22 to the user terminal 10.

[0164] It should be noted that the mother machine 21 is assigned to the user terminal 10 for operation, and the control authority of the mother-child cloud phone is assigned to the user terminal 10, that is, the user can control the mother machine 21 on the user terminal 10, and control the associated child machine 22 through the mother machine 21. The mother-child cloud phone is deployed on the first server 20. The performance of the mother-child cloud phone (including computing power, network performance, virtualization efficiency and software optimization) still depends on the hardware resources of the first server 20, rather than the hardware resources (device configuration) of the user terminal 10. Therefore, the performance of the cloud phone is not affected by the device configuration of the user terminal 10 used by the user. Even if the device configuration of the user terminal 10 is low, the user can obtain a high-configuration cloud phone for use according to the usage needs, which achieves a breakthrough in physical limitations and is suitable for high-performance, multi-tasking scenarios.

[0165] The configuration of the cloud phone mainly includes CPU configuration, GPU configuration and memory / storage. When the first server 20 allocates the cloud phone, it is necessary to allocate a mother machine 21 and at least one associated child machine 22 to the user terminal 10. Among them, the division of the mother machine 21 and the associated child machine 22 is based on the configuration level of the cloud phone. The cloud phone with a higher configuration among all the optional cloud phones is selected as the mother machine 21, and the cloud phone with a lower configuration is selected as the associated child machine 22, so that the mother machine 21 can control each associated child machine 22 through interaction.

[0166] On user terminal 10, a user can view the screen of at least one associated slave device 22 through a master device 21. The user can control each associated slave device 22 through the master device 21. The following describes the interaction between a master device 21 and associated slave devices 22, using an example of a master device 21 controlling one associated slave device 22.

[0167] This application discloses a cloud phone service system based on a parent-child architecture. The system includes a user terminal 10 and a first server 20. The user terminal 10 is in communication with the first server 20. The user terminal 10 obtains control authority for the parent-child cloud phone from the first server 20 through the user terminal 10. The first server 20 allocates control authority for a parent device 21 and at least one associated child device 22 to the user terminal 10. The parent device 21 runs on the user terminal 10 and is used to interact with each associated child device 22. The configuration of the parent device 21 is higher than that of the associated child devices 22. This enables comprehensive and convenient control of at least one other cloud phone through one cloud phone, achieving low-cost and high-efficiency centralized management and control of multiple cloud phones, eliminating the need for users to frequently switch between different device interfaces, reducing operational complexity and time costs.

[0168] In the present application, refer to Figure 5The first server 20 includes a control module 23, a sub-machine service module 24, and a service platform module 25, which are connected in communication with each other in sequence. The user terminal 10 is connected in communication with the control module 23.

[0169] The mother machine 21 running on the user terminal 10 is used to send interaction instructions to the control module 23. The control module 23 is used to send sub-machine service drive instructions to the sub-machine service module 24 based on the received interaction instructions. The sub-machine service module 24 is used to call the data transmission function of the service platform module 25 based on the received sub-machine service drive instructions to complete the control of the associated sub-machine 22.

[0170] The control module 23 is the core of the cloud phone service system based on the parent-child architecture. It communicates with the user terminal 10 upwards, receiving interaction instructions corresponding to various service requests from the user terminal 10. It communicates with the slave service module 24 downwards, converting interaction instructions received from the user terminal 10 into driver instructions that the slave service module 24 can parse and send these instructions to the slave service module. It also communicates with the service platform module 25 to invoke various functions within the service platform module 25. Service requests initiated by the user terminal 10 include file transfer, application startup and shutdown, backup / restore, cloud machine replacement, and one-click new machine creation.

[0171] The slave service module 24 communicates with the control module 23 to achieve two-way interaction, and communicates with the service platform module 25 to invoke various functions within the service platform module 25. Upon receiving a drive instruction from the control module 23, the slave service module 24 invokes the data transmission function within the service platform module 25 and, through data transmission coordination, executes the drive instruction, thereby achieving corresponding control of the associated slave 22 according to the drive instruction.

[0172] The service platform module 25 is communicatively connected with the control module 23 and the sub-machine service module 24, serving as the business support for the cloud phone service system based on the parent-child architecture, providing an operating environment, and coordinating data transmission to ensure smooth data exchange between the user terminal 10, the control module 23 and the sub-machine service module 24.

[0173] In a specific embodiment, referring to Figure 6As shown in the mother-child machine business logic diagram, after the user purchases the mother-child machine package through the user terminal 10 (Android client, H5 or PC client), the user obtains the mother machine 21 and the associated child machine 22 allocated by the first server 20. After the user opens the mother machine 21 on the user terminal 10, the screen preview of the mother machine 21 can be displayed on the user terminal 10. The mother machine 21 is pre-installed with a "Console APP". By clicking on the "Console APP", the screen preview of the associated child machine 22 can be opened. Among them, the "Console APP" is a pre-installed APP that integrates business functions including file transfer, application start and stop, backup / restore, replacement of cloud machines and one-click new machines. Therefore, the user can also issue task instructions through the function options provided by the "Console APP" to control the associated child machine 22 accordingly. Among them, the functions of each business function in the "Console APP" are as follows:

[0174] File transfer: Click to read the list of files and non-system applications on the master device 21, and transfer them to the associated slave device 22 after the user selects them;

[0175] Application start and stop: After clicking, a list of non-system applications associated with the slave device 22 will be displayed on the master device 21, and the user can select an application to start or stop it;

[0176] Replace cloud machine: Click to directly replace a new associated sub-machine 22 on the master machine 21;

[0177] Backup and recovery: Backup refers to backing up files and non-system application data on the associated slave machine 22 to the master machine 21; recovery refers to restoring data that has been backed up to the master machine 21 to the associated slave machine 22;

[0178] One-click new machine: Perform a one-click new machine operation on the master machine 21 for the associated slave machine 22. One-click new machine means changing the parameters of the associated slave machine 22.

[0179] The user terminal 10 sends an interactive instruction of a data transmission request to the control module 23. After receiving the interactive instruction of the data transmission request, the control module 23 converts the interactive instruction of the data transmission request into a sub-machine service drive instruction (including the data transmission request) that can be parsed by the sub-machine service module 24, and then forwards the sub-machine service drive instruction to the sub-machine service module 24. The sub-machine service module 24 calls the data transmission function of the service platform module 25 based on the received sub-machine service drive instruction. At this time, the service platform module 25 is used to monitor the network status during data transmission, plan the transmission protocol, and coordinate data transmission to realize the transmission of the master machine 21 data to the associated sub-machine 22. After the transmission is completed, the service platform module 25 sends a transmission completion notification to the sub-machine service module 24, which is then fed back by the sub-machine service module 24 to the control module 23 and finally fed back to the user terminal 10.

[0180] For example, when the user chooses to transfer a file to the associated sub-machine 22, in the cloud phone service system based on the parent-child architecture, the parent machine 21 running on the user terminal 10 sends an interactive instruction containing a file transfer business function to the control module 23. After receiving the interactive instruction, the control module 23 converts the interactive instruction into a sub-machine service driver instruction that can be parsed by the sub-machine service module 24, and then sends the sub-machine service driver instruction to the sub-machine service module 24. The sub-machine service module 24 calls the data transmission function of the service platform module 25 based on the received sub-machine service driver instruction, and executes the relevant business operations of the file transfer to realize the transfer of the parent machine 21 file to the associated sub-machine 22.

[0181] Different from the problem in the prior art that is limited by the performance and functions of a single cloud phone and cannot efficiently run multi-tasking operations or complex business processing, in the embodiment of the present application, a control module 23, a sub-machine service module 24 and a service platform module 25 that are sequentially communicated with each other are constructed on the first server 20, and the user terminal 10 is communicated with the control module 23 to realize the step-by-step transmission of interactive instructions, so that the user can control the associated sub-machine 22 through the mother machine 21 after initiating an operation on the user terminal 10, realize flexible interactive management of data between different cloud phones, and efficiently run multi-tasking operations and complex business processing.

[0182] In an embodiment of the present application, the service platform module 25 is also used to match idle cloud phones to the user terminal 10 based on the available resource pool of the first server 20 and the device attributes of the user terminal 10, where the relatively high-end cloud phone serves as the mother phone 21 and the relatively low-end cloud phone serves as the associated sub-phone 22, and the identity identifiers of the mother phone 21 and the associated sub-phone 22 are assigned to the user terminal 10.

[0183] In the embodiment of the present application, the service platform module 25 includes a sub-function module for cloud machine allocation. When a user purchases a parent-child phone package on the user terminal 10, the service platform module 25 will call the cloud machine allocation sub-function module to allocate the parent and child cloud phones. For example, if a user purchases a package of one parent phone 21 and one associated child phone 22 on the user terminal 10, the cloud machine allocation process after the purchase is completed is as follows:

[0184] The service platform module 25 obtains cloud phone resource information from the available resource pool based on the first server 20. The available resource pool stores a large number of idle cloud phones with different configurations suitable for different application scenarios. It matches all idle cloud phones according to the user device attributes, and matches a mother phone 21 and an associated child phone 22 according to the actual needs of the user to purchase a package. The cloud phone with the higher configuration of the two matched cloud phones is used as the mother phone 21, and the other cloud phone with the lower configuration is used as the associated child phone 22. Then, after determining the mother phone 21 and each child phone 21, a mother-child phone instance is created, and the identity identifiers (IDs) of the mother phone 21 and the associated child phone 22 are assigned to the user terminal 10, and the IDs of the mother phone 21 and the associated child phone 22 are bound to associate the mother-child relationship. Among them, the user device attributes here can be understood as the device configuration of the above-mentioned user terminal 10, including CPU configuration (number of CPU cores, CPU memory), GPU configuration and memory / storage.

[0185] Different from the problem in the prior art that there is a lack of efficient coordination mechanism between devices and it is not convenient to centrally control another device on one device (cloud phone), in the embodiment of the present application, by dividing the cloud phone into a mother machine 21 and each associated child machine 22 according to the configuration level, the mother-child relationship is associated to form a mother-child architecture, so that the mother machine 21 can be used to control each associated child machine 22 to complete the collaborative interaction, and at least one other device can be conveniently controlled on one device.

[0186] In an embodiment of the present application, the service platform module 25 is also used to receive a request from the user terminal 10 to replace the cloud machine, match an idle cloud phone to the user terminal 10 as a new associated sub-machine 22 based on the available resource pool of the first server 20 and the device attributes of the old associated sub-machine 22, and assign the identity of the new associated sub-machine 22 to the user terminal 10.

[0187] The associated sub-machine 22 may malfunction during operation. For example, the associated sub-machine 22 may display an error code such as maintenance, failure, or offline, or the associated sub-machine 22 may freeze or display a black screen during operation. In this case, a new associated sub-machine 22 may be required.

[0188] In the embodiment of the present application, the sub-function module for cloud machine allocation included in the service platform module 25 can also be used to realize the function of replacing the cloud machine. When the associated sub-machine 22 fails, the user can send a request to replace the cloud machine to the service platform module 25 through the user terminal 10. After receiving the request to replace the cloud machine, the service platform module 25 first reads the device attributes of the old associated sub-machine 22 (i.e., the faulty associated sub-machine to be replaced) (i.e., the above-mentioned device configuration, including CPU configuration, GPU configuration and memory / storage). Then, the service platform module 25 obtains the cloud phone resource information from the available resource pool based on the first server 20. Then, according to the device attributes of the old associated sub-machine 22, a cloud phone of the same specifications is re-matched as the new associated sub-machine 22. Finally, a new instance of the associated sub-machine 22 is created, the identity (ID) of the new associated sub-machine 22 is assigned to the user terminal 10, and the IDs of the mother machine 21 and the new associated sub-machine 22 are re-bound, that is, the parent-child relationship between the mother machine 21 and the new associated sub-machine 22 is re-associated.

[0189] Different from the existing technology in which the replacement of cloud machines requires switching the current cloud phone device, that is, the problem of needing to exit the current session and switch to other cloud phone devices, in the embodiment of the present application, through the parent-child architecture of the cloud phone, the cloud machine can be replaced by direct operation in the parent machine 21, thereby realizing the operation of replacing the cloud machine without switching devices.

[0190] In the embodiment of the present application, the service platform module 25 is further configured to delete the identity of the old associated sub-machine 22 from the user terminal 10 , clear the data in the old associated sub-machine 22 , and recycle the data to the available resource pool of the first server 20 .

[0191] During the cloud machine replacement process, the old associated child machine 22 must be released and recycled. First, the service platform module 25 deletes the identity identifier (ID) of the old associated child machine 22 from the user terminal 10 and unbinds the old associated child machine 22 from the parent machine 21 (the parent-child relationship). After the unbinding is complete, the service platform module 25 clears the data in the old associated child machine 22, restoring the old associated child machine 22 to factory settings, and then reclaims the old associated child machine 22 to the available resource pool of the first server 20.

[0192] In the embodiment of the present application, the process of replacing the cloud machine is explained again by taking the interaction between the mother machine 21 and the associated child machine 22 and the user terminal 10 and the first server 20 as an example. First, the user terminal 10 sends a request to replace the cloud machine to the mother machine 21. After receiving the request, the mother machine 21 requests the configuration information of the associated child machine 22 from the first server 20. After the first server 20 returns the configuration information of the associated child machine 22 to the mother machine 21, the mother machine 21 sends a request to replace the cloud machine to the first server 20. The first server 20 will allocate the cloud machine, bind the allocated new associated child machine 22 to the mother machine 21 as a mother-child machine relationship, and then recycle the old associated child machine 22 to the available resource pool, and send a replacement completion notification to the mother machine 21. The mother machine 21 then feedbacks the replacement completion to the user terminal 10.

[0193] Unlike the existing technology in which the cloud machine replacement process is cumbersome and cannot be directly replaced on the currently operating cloud phone, and some manufacturers do not support customers to replace the cloud machine by themselves, in the embodiment of the present application, the user can use the cloud machine replacement function pre-installed in the mother machine 21 to directly and conveniently and quickly replace the associated sub-machine 22, and during the replacement process, the old associated sub-machine 22 is directly cleared of data and recycled into the available resource pool of the first server 20, thereby quickly realizing the exchange of the old and new cloud machines.

[0194] In an embodiment of the present application, the sub-machine service module 24 includes a video stream acquisition sub-module, and the sub-machine service module 24 is also used to call the video stream acquisition sub-module to obtain the picture of the associated sub-machine 22 and generate a video stream, and transmit the video stream to the control module 23 in real time; the control module 23 includes a picture acquisition sub-module, and the control module 23 is also used to call the picture acquisition sub-module, receive the video stream sent by the sub-machine service module 24, decode the video stream and render it to the user terminal 10.

[0195] In the embodiment of the present application, the user can view the screen of the associated sub-machine 22 through the screen of the main machine 21 displayed by the user terminal 10. When the user clicks the "View Console" function in the "Console App" built into the main machine 21, and then clicks to open the sub-machine preview, the screen of the associated sub-machine 22 can be displayed on the screen of the main machine 21.

[0196] During this process, the slave service module 24 invokes the video stream acquisition submodule within the slave service module 24 to acquire the image of the associated slave 22 through video streaming. Video streaming refers to the technology of transmitting real-time or recorded video data from a source (such as a cloud phone, camera, or computer) to a receiving end (such as a mobile phone, TV, or live streaming platform) via a network. For example, during a live game broadcast, the cloud phone pushes the image to the live streaming platform. Video streaming is one of the core functions of the cloud phone, involving multiple steps such as video acquisition, encoding, transmission, decoding, and rendering.

[0197] After acquiring the screen from the associated slave 22, the video stream acquisition submodule encodes and decompresses the screen (which may be the H.264 video compression standard) to generate video stream data, which is then transmitted in real time to the control module 23. Because the screen from the associated slave 22 is dynamically and continuously displayed on the screen of the master 21, the video stream acquisition submodule continuously acquires the screen from the associated slave 22 and continuously transmits the video stream data generated by encoding and decompressing the screen to the control module 23 during the above process.

[0198] After the video stream data is transmitted to the control module 23, the control module 23 will call the picture acquisition submodule in the control module 23 to receive the video stream data, then decode the video stream data, and render the decoded video stream data to the user terminal 10, so that the user can view the real-time picture of the associated sub-machine 22 through the main machine 21 running on the user terminal 10.

[0199] Different from the problem in the prior art that users cannot view the screen of another cloud machine device through one cloud machine device, in the embodiment of the present application, through the interaction of the video stream acquisition submodule in the sub-machine service module 24 and the screen acquisition submodule in the control module 23, the screen of the associated sub-machine 22 is obtained and displayed in real time on the screen of the mother machine 21, allowing users to conveniently view the screen of at least one associated sub-machine 22 through the mother machine 21, so as to facilitate the control operation of the associated sub-machine 22.

[0200] In an embodiment of the present application, the sub-machine service module 24 includes a data storage sub-module, and the sub-machine service module 24 is also used to call the data storage sub-module to classify and store the data in the associated sub-machine 22 according to preset rules; the control module 23 includes a file storage sub-module, and the control module 23 is also used to call the file storage sub-module, the data transmission function of the service platform module 25 and the data storage sub-module in the sub-machine service module 24 to back up the data stored in the associated sub-machine 22 to the mother machine 21, or restore the backup data of the mother machine 21 to the associated sub-machine 22.

[0201] To ensure continued use of data from the previous cloud machine after a switch, the "Console App" provides a backup / restore function. Users can back up data from the associated slave machine 22 to the master machine 21 in advance. After switching cloud machines, the backed-up data from the master machine 21 can be restored to the new associated slave machine 22, making data more accessible. The backed-up / restored data includes files and non-system application data.

[0202] During operation, the associated sub-machine 22 receives files and generates other non-system application data. These data are called by the data storage sub-module in the sub-machine service module 24 through the sub-machine service module 24, and are classified and stored in the storage space in the associated sub-machine 22 or the local storage space according to preset rules.

[0203] When the user selects the backup operation, the control module 23 will call the file storage submodule in the control module 23, the data transmission function of the service platform module 25, and the data storage submodule in the slave service module 24 to perform the backup operation. The backup operation is as follows:

[0204] First, the control module 23 invokes the file storage submodule within the control module 23 and the data storage submodule within the slave service module 24 to read the file directory and non-system application list from the storage space of the associated slave 22. Next, the file directory and non-system application list are fed back to the user terminal 10, allowing the user to select the data to be backed up. Finally, after determining all the data to be backed up, the control module 23 invokes the data transfer function of the service platform module 25 to transfer the data to be backed up from the storage space of the associated slave 22 to the storage space of the master 21. The data to be backed up can be processed based on its data type. For example, file types can be compressed, and application types can be packaged into an installation package. The compressed file and installation package are then encrypted and transferred to the storage space of the master 21.

[0205] During the backup process, a backup record is generated on the master machine 21. The backup record includes the backed-up compressed file and installation package, file information, backup time and data size. The backup record is used as a basis for subsequent backup data recovery.

[0206] When the user selects the restore operation, the control module 23 will call the file storage submodule in the control module 23, the data transmission function of the service platform module 25, and the data storage submodule in the slave service module 24 to perform the restore operation. The specific restore operation method is as follows:

[0207] First, the control module 23 calls the file storage submodule in the control module 23 to read all backup records in the mother machine 21, and feeds back to the user terminal 10 for the user to select the backup record that needs to be restored. Then, after determining the backup record that needs to be restored, the backup data in the backup record is decompressed. Then, the control module 23 calls the data transmission function of the service platform module 25 and the data storage submodule in the sub-machine service module 24, encrypts the decompressed backup data and transmits it to the associated sub-machine 22, and restores it to the corresponding storage directory in the storage space of the associated sub-machine 22. As for the application type data, after the installation package is transmitted to the associated sub-machine 22, the corresponding application will be directly installed on the associated sub-machine 22.

[0208] During the backup or restore process, the interaction process between the master machine 21 and the associated slave machine 22 is as follows:

[0209] After the backup process begins, the user selects the associated child machine 22 to be backed up on the parent machine 21. The associated child machine 22 returns the non-system files and files and application data in the APP (application) storage directory to the parent machine 21. After receiving the files and application data, the parent machine 21 backs them up and backs them up to the storage space on the parent machine 21, completing the backup. After the backup is complete, if a restore is needed, the backed-up data is selected on the parent machine 21, decompressed, and restored, and then transferred to the associated child machine 22. The associated child machine 22 then restores the backed-up data to its storage space, completing the restore.

[0210] In addition to file transfers between the master machine 21 and the associated slave machine 22 during backup and restore, users can also select the file transfer function in the "Console App" of the master machine 21 to transfer files from the master machine 21 to the associated slave machine 22. The file transfer process between the master machine 21 and the associated slave machine 22 is as follows:

[0211] After the user enters the mother machine 21 through the user terminal 10, he starts the "Console APP" pre-installed in the mother machine 21 and selects the file transfer function option. At this time, the first server 20 will read the file / application list (non-system) of the mother machine 21 and feedback it to the user terminal 10. The user selects the file / application to be transferred and transmits it to the associated sub-machine 22. The file / application is transferred to the corresponding file / application storage directory in the storage space of the associated sub-machine 22, and the transfer is completed.

[0212] Different from the prior art that relies on cumbersome operations of third-party storage services when performing backup / restore operations on multiple cloud phone devices, and the problem of additional costs due to the expansion of storage services, in the embodiment of the present application, through the parent-child architecture of the cloud phone, users can directly back up and restore the file data and non-system application data of the associated child machine 22 on the parent machine 21, without relying on third-party storage, reducing storage costs, and improving the convenience of backup and restore operations of file data and non-system application data in the cloud phone.

[0213] In an embodiment of the present application, the service platform module 25 includes a resource allocation sub-module. Before backing up the data stored in the associated sub-machine 22 to the main machine 21, the service platform module 25 is also used to call the resource allocation sub-module, read the storage space of the main machine 21, and determine whether the free storage space meets the storage requirements of the backup data; if so, the coordination control module 23 performs the backup; if not, the insufficient space prompt is fed back to the user terminal 10.

[0214] During the backup process described above, after compressing and packaging the data to be backed up on the associated slave machine 22, the service platform module 25 invokes the resource allocation submodule within the service platform module 25 to read the storage space size of the master machine 21 and determine whether the available storage space on the master machine 21 meets the backup data storage requirements. If so, the control module 23 invokes the data transfer function within the service platform module 25 to transfer the backup data to the available storage space on the master machine 21. If not, meaning that the available storage space on the master machine 21 is insufficient to store all the backup data, the control module 23 sends a message to the user terminal 10 indicating insufficient storage space on the master machine 21, and the backup data is not transferred.

[0215] Different from the existing technology that requires reliance on third-party storage for backup operations when performing file data and non-system application data backup operations in cloud phones, in the embodiment of the present application, the service platform module 25 calls the resource allocation function to determine whether the size of the free storage space in the mother machine 21 meets the backup requirements, and coordinates the backup of data in the associated sub-machine 22 to the free storage space of the mother machine 21, making the operation more convenient and the data transmission faster.

[0216] In an embodiment of the present application, before restoring the backup data of the master machine 21 to the associated slave machine 22, the service platform module 25 is also used to call the resource allocation function, read the storage space of the associated slave machine 22, and determine whether the free storage space is sufficient to restore the backup data; if so, the coordination control module 23 performs the restoration; if not, a prompt of insufficient space is fed back to the user terminal 10.

[0217] During the above-mentioned recovery process, after decompressing the backup data in the backup record, the service platform module 25 invokes the resource allocation submodule within the service platform module 25 to read the storage space size of the associated slave 22 and determine whether the available storage space in the associated slave 22 meets the backup data storage requirements. If so, the control module 23 invokes the data transmission function within the service platform module 25 to transfer the backup data to the available storage space in the associated slave 22 for recovery. If not, meaning that the available storage space in the associated slave 22 is insufficient to store all the backup data, the control module 23 sends a feedback to the user terminal 10 indicating insufficient storage space in the associated slave 22, and the backup data is not transferred.

[0218] Different from the problem in the prior art that third-party storage software only supports single file or application download operations when the user needs to restore, and cannot restore the entire file with the backup record module, in the embodiment of the present application, the service platform module 25 calls the resource allocation function to determine whether the size of the free storage space in the associated sub-machine 22 meets the recovery requirements, and coordinates the restoration of the backed-up data in the parent machine 21 to the free storage space of the associated sub-machine 22, which makes the operation more convenient and the data transmission faster.

[0219] In an embodiment of the present application, the control module 23 includes an application running sub-module, and the control module 23 is also used to call the application running sub-module and send application control instructions to the sub-machine service module 24; the sub-machine service module 24 includes a control instruction parsing sub-module, and the sub-machine service module 24 is also used to call the control instruction parsing sub-module, receive the application control instructions sent by the control module 23, parse the application control instructions, and control the application running status of the associated sub-machine 22 according to the parsing results; the control module 23 is also used to call the application running sub-module, monitor the application running status in the associated sub-machine 22, and feed back the running status to the user terminal 10.

[0220] In an embodiment of the present application, a user can control the application running status (including application startup / shutdown) of an associated slave 22 via the master 21 running on the user terminal 10. The user clicks on "Application Start / Stop" in the function options within the "Console App" built into the master 21 and selects the application to be controlled. The control module 23 then calls the application running submodule within the control module 23 and sends an application control instruction to the slave service module 24. The application control instruction includes information about the application to be controlled and the application running status operation. Once the application control instruction is transmitted to the slave service module 24, the slave service module 24 calls the control instruction parsing submodule to receive the application control instruction, parse it, and convert it into a command executable by the associated slave 22. This command is then executed via channel hardware or software to control the application running status of the associated slave 22. The "execution via channel hardware or software" can be understood as pre-installed in the slave service module 24 with some execution modules that implement functions such as file transfer, application startup / shutdown, and one-click new machine creation, stored in the form of channel hardware or software.

[0221] In a specific embodiment, referring to Figure 7 The schematic diagram of the interaction process of starting and stopping the application of the parent and child machines shown takes the interaction between the parent machine 21 and the associated child machine 22 as an example to illustrate the process of implementing the start and stop of the application. The process is as follows:

[0222] When the user clicks on the application start and stop function option in the "Console APP" built into the mother machine 21, the mother machine 21 sends an application list request (including the ID of the associated child machine 22) to the associated child machine 22 through the communication gateway. The communication gateway sends the application list request to the corresponding associated child machine 22 according to the ID of the associated child machine 22; after receiving the application list request, the associated child machine 22 returns a non-system application list (including application status) to the mother machine 21 through the communication gateway; the mother machine 22 receives and displays the non-system application list to the user terminal 10, and the user selects the application whose running status needs to be controlled in the non-system application list. For example, if the user chooses to start a game application that is not running, the mother machine 21 sends an application start instruction to the associated child machine 22 through the communication gateway. After receiving the application start instruction, the associated child machine 22 performs the corresponding operation, that is, starts the corresponding game application. At this time, the application status is updated and the update result is fed back to the mother machine 21; for example, if the user chooses to close the running game application, the mother machine 21 sends an application close instruction to the associated child machine 22 through the communication gateway. After receiving the application close instruction, the associated child machine 22 performs the corresponding operation, that is, closes the corresponding game application. At this time, the application status is updated and the update result is fed back to the mother machine 21.

[0223] Different from the cumbersome steps in the prior art in which cloud phone applications need to be started and stopped by exiting the cloud machine and performing application start and stop operations on the client, in the embodiment of the present application, by allowing users to directly control the start and stop of non-system applications on the associated sub-machine 22 on the main machine 21, users do not need to exit the main machine 21 and open the associated sub-machine 22 to start and stop non-system applications, thereby improving the convenience of operation.

[0224] This application discloses a cloud phone service system based on a parent-child architecture. The system includes a user terminal 10 and a first server 20. The user terminal 10 is in communication with the first server 20. The user terminal 10 obtains control authority for the parent-child cloud phone from the first server 20 through the user terminal 10. The first server 20 allocates control authority for a parent device 21 and at least one associated child device 22 to the user terminal 10. The parent device 21 runs on the user terminal 10 and is used to interact with each associated child device 22. The configuration of the parent device 21 is higher than that of the associated child devices 22. This enables comprehensive and convenient control of at least one other cloud phone through one cloud phone, achieving low-cost and high-efficiency centralized management and control of multiple cloud phones, eliminating the need for users to frequently switch between different device interfaces, reducing operational complexity and time costs.

[0225] The beneficial effects of the present application are as follows: Different from the prior art, the present application discloses a cloud phone service system based on a parent-child architecture. The system includes a client and a server, wherein the client communicates with the server, obtains the control authority of the parent-child cloud phone from the server through the client, and allocates the control authority of the parent phone and at least one child phone to the client through the server. The parent phone runs on the client and is used to interact with each child phone. The configuration of the parent phone is higher than that of the child phone, realizing comprehensive and convenient control of at least one other cloud phone through one cloud phone, realizing low-cost and high-efficiency centralized management and control of multiple cloud phones, eliminating the need for users to frequently switch between different device interfaces, reducing operational complexity and time costs.

[0226] refer to Figure 8 In one embodiment of the present application, a cloud phone service method based on a parent-child architecture is provided, which is applied to a parent machine, on which a second client runs. The method includes:

[0227] S100: Receiving, via the second client, and responding to a user's application start / stop operation on the first target sub-machine, sending an application start / stop instruction to the first target sub-machine, causing the first target sub-machine to enable or disable the indicated local target application, wherein the application start / stop instruction carries an application unique identifier of the target application to be enabled or disabled, and the first target sub-machine is an associated sub-machine of the master machine;

[0228] Among them, the first target sub-machine is the associated sub-machine of the mother machine. The mother machine and its associated sub-machines are deployed on the first server. The mother machine interface can be displayed through the first client running on the user terminal. The mother machine interface displayed on the first client can be operated through the first client. The first client runs on the user terminal and can be displayed on the terminal interface of the user terminal. The second client can be displayed on the mother machine interface. The second client displayed on the mother machine interface can be operated through the mother machine interface. The sub-machine interface of the associated sub-machine can be displayed through the second client. The sub-machine interface displayed on the second client can be operated through the second client.

[0229] Specifically, the cloud phone service method based on the parent-child architecture of this embodiment is specifically described in the above-mentioned description of the cloud phone service system based on the parent-child architecture, which will not be repeated here.

[0230] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0231] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0232] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A cloud phone service system based on a parent-child architecture, characterized in that: The system includes: a first client, a second client, a first server, a master machine deployed on the first server, and a slave machine associated with the master machine, wherein the master machine and the associated slave machine are both cloud phones; The first client runs on the user terminal and can be displayed on the terminal interface, and is used to receive and respond to the user's motherboard entry operation, enter and display the motherboard interface; The second client runs on the master machine and can be displayed on the master machine interface; The master machine is configured to receive, through the second client, and in response to a user's application start / stop operation on the first target child machine, send an application start / stop instruction to the first target child machine, wherein the application start / stop instruction carries an application unique identifier of the target application to be started / stopped, and the first target child machine is an associated child machine of the master machine; The first target sub-machine is configured to enable or disable the indicated local target application upon receiving the application enable / disable instruction.

2. The cloud phone service system based on the parent-child architecture according to claim 1 is characterized in that: The master machine is specifically configured to receive, through the second client, and respond to a user's application start / stop selection operation on the first target slave machine, and send an application list and status query request to the first target slave machine; The first target sub-machine is specifically configured to query local applications and application status upon receiving the application list and status query request, and send the application and status query results to the master machine; The master machine is specifically configured to display the application list and application status of the first target sub-machine to the user through the second client based on the application and status query results of the first target sub-machine; The master machine is specifically configured to receive, through the second client, and respond to a user's designated operation on a target application to be started or stopped in the application list, and generate and send an application start or stop instruction to the first target slave machine.

3. The cloud phone service system based on parent-child architecture according to claim 2 is characterized in that: The application status is an enabled state or a disabled state; The master machine is specifically configured to display, based on the application status, a list of enabled applications and a list of disabled applications of the first target slave machine to the user through the second client in a classified manner; The mother machine is specifically used to receive through the second client and send an application closing instruction to the first target child machine in response to the user's selection operation of the target application to be closed in the enabled application list, and / or receive through the second client and send an application enabling instruction to the first target child machine in response to the user's selection operation of the target application to be enabled in the closed application list.

4. The cloud phone service system based on the parent-child architecture according to claim 2 or 3, characterized in that: The first target sub-machine is specifically configured to, upon receiving the application list and status query request, filter local system applications, query the application status of local non-system applications, and send the application and status query results of the local non-system applications to the master machine; The master machine is specifically configured to display the non-system application list and application status of the first target slave machine to the user through the second client.

5. The cloud phone service system based on the parent-child architecture according to claim 2 or 3, characterized in that: The first target sub-machine is further configured to send application status update feedback to the master machine after completing the start and stop of the target application; The master machine is further configured to display the application list and updated application status of the first target slave machine to the user through the second client upon receiving the application status update feedback.

6. The cloud phone service system based on the parent-child architecture according to any one of claims 1 to 3, characterized in that: The master device is specifically configured to display an application start / stop interface to the user via the second client upon receiving an application start / stop selection operation from the user via the main operation interface of the second client; or, The master device is specifically configured to, upon receiving a user's selection operation to open a preview of a sub-device via the second client, access and display to the user a sub-device preview interface of the second target sub-device via the second client, wherein a control panel may be displayed on the sub-device preview interface, the control panel including sub-options for starting and stopping applications, and upon receiving a user's selection operation to start and stop an application via the control panel, display the application start and stop interface to the user via the second client; The master machine is further configured to send an application start / stop instruction to the first target slave machine if an application start / stop confirmation operation of the user is received through the application start / stop interface of the second client.

7. The cloud phone service system based on parent-child architecture according to claim 6 is characterized in that: The master device is specifically configured to, upon receiving an application start / stop selection operation from the user via the main operation interface of the second client, display the application start / stop interface to the user via the second client; and upon receiving a selection operation for the first target slave device and the target application to be started / stopped, as well as a first confirmation operation from the user via the application start / stop interface of the second client, send an application start / stop instruction to the first target slave device; or, The master machine is specifically configured to display the application start / stop interface to the user through the second client if a user's application start / stop selection operation is received through the general operation interface of the second client; display the application start / stop prompt to the user through the second client if a user's selection operation for the first target sub-machine and the target application to be started / stopped and a first confirmation operation are received through the application start / stop interface of the second client; and send the application start / stop instruction to the first target sub-machine if a second confirmation change operation is received through the second client.

8. The cloud phone service system based on the parent-child architecture according to any one of claims 1 to 3, characterized in that: The mother machine is further configured to receive and respond to a user's sub-machine preview operation on the first target sub-machine through the second client, obtain a local target video stream image of the sub-machine captured by the first target sub-machine, process the target video stream image, and then display it through the second client, wherein the second client is displayed on the mother machine interface.

9. The cloud phone service system based on parent-child architecture according to claim 1 is characterized in that: The first server includes a control module, a slave service module, and a service platform module that are communicatively connected, wherein the master machine includes the control module, the associated slave machine includes the slave service module, and the user terminal is communicatively connected to the control module; The master machine is configured to send a slave machine service driving instruction to the slave machine service module through the control module. The sub-machine service module is configured to execute corresponding operations based on the received sub-machine service driving instruction.

10. A cloud phone service method based on a parent-child architecture, applied to a parent machine, wherein a second client runs on the parent machine, characterized in that: The method comprises: receiving, through the second client, and responding to a user's application start / stop operation on the first target child machine, an application start / stop instruction is sent to the first target child machine, causing the first target child machine to enable or disable the indicated local target application, wherein the application start / stop instruction carries an application unique identifier of the target application to be enabled or disabled, and the first target child machine is an associated child machine of the master machine; Among them, the first target sub-machine is the associated sub-machine of the mother machine, the mother machine and its associated sub-machines are deployed on the first server, the mother machine interface can be displayed through the first client running on the user terminal, and the mother machine interface displayed on the first client can be operated through the first client, the first client runs on the user terminal and can be displayed on the terminal interface of the user terminal, the second client can be displayed on the mother machine interface, and the second client displayed on the mother machine interface can be operated through the mother machine interface, the sub-machine interface of the associated sub-machine can be displayed through the second client, and the sub-machine interface displayed on the second client can be operated through the second client.

Images