Interaction method and apparatus for cloud mobile phone

Abstract

Disclosed in the embodiments of the present application are an interaction method and apparatus for a cloud mobile phone, which are used for improving the proportion of a visual area of a user interface of a cloud mobile phone. The method in the embodiments of the present application comprises: a terminal device sending a first event instruction to a cloud server in response to a first input event of a user, wherein the first event instruction is used for requesting the cloud server to generate update content of a cloud mobile phone service; the terminal device receiving an event response message sent by the cloud server, wherein the event response message comprises the update content generated by the cloud server on the basis of the event instruction; and the terminal device displaying the update content on the terminal device on the basis of the event response message, wherein the update content comprises one or more of the following: a navigation bar, a previous interface and a next interface.

Description

A cloud phone interaction method and device

[0001] This application claims priority to the Chinese patent applications filed with the State Intellectual Property Office of China on December 26, 2023, with application number 202311813704.6, and invention name “A method and device for interface navigation”, and filed with the State Intellectual Property Office of China on April 29, 2024, with application number 202410547322.1, and invention name “A method and device for interaction with a cloud phone”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of cloud computing, and in particular to a method and device for interacting with a cloud phone. Background Art

[0003] With the development of cloud computing technology, cloud phones, a virtual mobile phone service based on cloud computing, are becoming increasingly popular. In cloud phone applications, cloud phones do not require actual hardware devices for communication and computing. Instead, the phone's operating system and applications run on remote cloud servers. Users can access cloud phones using a variety of terminal devices, without being restricted by specific hardware devices.

[0004] Currently, when users interact with cloud phones through terminal devices, they often control the cloud phone's display interface through the navigation bar on the cloud phone interface or rely on the floating ball in the cloud phone interface to ensure that users can switch pages and navigate the interface while using the cloud phone. However, the permanent navigation bar on the cloud phone's display interface, or the method of displaying the system navigation bar through the floating ball during use, occupies the user's visible and operable area on the terminal device for the cloud phone, reducing the screen-to-body ratio of the user's visible and operable area when using the cloud phone, resulting in poor interaction between the user and the cloud phone. Summary of the Invention

[0005] The present application provides a method for exchanging cloud phones. In this embodiment, while a user is using a cloud phone, the cloud server can update the display content of the cloud phone's user interface based on the user's input events, thereby displaying a navigation bar when the user performs a specified operation, thereby increasing the screen-to-body ratio of the user's visible area when using the cloud phone. The present application also provides a cloud phone interaction device, computing device, computing device cluster, computer-readable storage medium, and computer program product corresponding to the cloud phone interaction method.

[0006] In the first aspect, an embodiment of the present application provides an interactive method for a cloud phone, which can be executed by a terminal device or a cloud server, or by a component of the terminal device or cloud server, such as a processor, chip or chip system of the terminal device or cloud server, or by a logic module or software that can realize all or part of the functions of the terminal device or cloud server. The method provided in the first aspect includes: the terminal device sends a first event instruction to the cloud server in response to a first input event of the user, and the first event instruction is used to request the cloud server to generate updated content for the cloud phone service. The terminal device receives an event response message sent by the cloud server, and the event response message includes the updated content generated by the cloud server based on the event instruction. The terminal device displays the updated content on the terminal device based on the event response message, and the updated content includes one or more of the following: a navigation bar, a previous interface, and a next interface.

[0007] In the embodiment of the present application, the terminal device of the cloud phone system can send event instructions to the cloud server based on the user's input events, so that the cloud server updates the content of the cloud phone user interface based on the event instructions. Therefore, in the embodiment of the present application, the user can control the cloud phone to display the display content that the user wants to obtain based on the specified action event. Compared with the current solution in which the navigation bar and other content in the cloud phone interface are fixedly occupied by the cloud phone user interface, the cloud phone interaction solution in the embodiment of the present application improves the screen ratio of the visible area and the display flexibility of the cloud phone user interface.

[0008] In one possible implementation, the first input event includes one or more of the following: clicking or sliding the screen, shaking the device, custom gestures, and voice control. For example, the user controls the display of a navigation bar on the user interface of the cloud phone by clicking the screen, controls the return of the user interface of the cloud phone to the previous interface by sliding the screen to the right, controls the forward movement of the user interface of the cloud phone to the next interface by sliding the screen to the left, controls the forward movement of the user interface of the cloud phone to the homepage interface by shaking the terminal device, and controls the screenshot of the current user interface of the cloud phone by custom gestures.

[0009] In the embodiment of the present application, the user can control the display content of the cloud phone user interface based on multiple input events, thereby improving the flexibility of controlling the cloud phone user interface.

[0010] In one possible implementation, the updated content is a navigation bar, which includes one or more of the following virtual buttons: a back button, a home button, and a menu button. The navigation bar is displayed at the bottom of the cloud phone interface, or the navigation bar is displayed in a local area of ​​the cloud phone interface. When the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar can be a virtual navigation button.

[0011] In an embodiment of the present application, the user can control the cloud phone to display a navigation bar at the bottom or in a local area of ​​the user interface based on a specified input event, so that the cloud phone displays the navigation bar only when the user needs to operate the navigation bar, thereby improving the screen ratio of the visible area and the display flexibility of the navigation bar in the cloud phone user interface.

[0012] In one possible implementation, while the terminal device is sending a first event instruction to the cloud server in response to the user's first input event, the terminal device is sending a right-swipe event instruction to the cloud server in response to the user's screen sliding action to the right. The right-swipe event instruction is used to request the cloud server to return to the previous user interface of the current user interface.

[0013] In the embodiment of the present application, the user can control the user interface of the cloud phone by sliding the screen to the right to return to the previous interface, thereby improving the flexibility and operating efficiency of the user in controlling the user interface of the cloud phone.

[0014] In one possible implementation, while the terminal device is sending a first event instruction to the cloud server in response to the user's first input event, the terminal device is sending a left-swipe event instruction to the cloud server in response to the user's left-swiping screen action. The left-swipe event instruction is used to request the cloud server to go to the next user interface of the current user interface.

[0015] In the embodiment of the present application, the user can control the user interface of the cloud phone to go to the next interface by sliding the screen to the left, thereby improving the flexibility and operating efficiency of the user in controlling the user interface of the cloud phone.

[0016] In one possible implementation, in the process of the terminal device sending a first event instruction to the cloud server in response to the user's first input event, the terminal device sends a click event instruction to the cloud server in response to the user's action of clicking the screen, and the click event instruction is used to request the cloud server to display a navigation bar in the current user interface.

[0017] In the embodiment of the present application, the user can control the display navigation bar of the user interface of the cloud phone by clicking the screen, thereby improving the flexibility and operating efficiency of the user in controlling the user interface of the cloud phone.

[0018] In one possible implementation, the terminal device sends a second event instruction to the cloud server in response to the user's second input event on the virtual key in the navigation bar. The second event instruction is used to request the cloud server to generate a cloud phone interface corresponding to the virtual key. The second input event is one or more of the following: clicking the screen, custom gestures, and voice control. For example, when the user wants to return to the previous interface of the current user interface of the cloud phone, the user clicks the return button in the navigation bar, and the terminal device sends a return button click event instruction to the cloud server. The return button click event instruction is used to request the cloud server to generate the previous interface of the current cloud phone user interface. For another example, when the user wants to return to the home page interface of the cloud phone user interface, the user clicks the home button in the navigation bar, and the terminal device sends a home button click event instruction to the cloud server. The home button click event instruction is used to request the cloud server to generate the home page interface of the cloud phone user interface.

[0019] In the embodiment of the present application, the user can further operate the virtual buttons in the navigation bar in the cloud phone user interface, so that the cloud phone interface corresponding to the virtual buttons is displayed in the cloud phone user interface, thereby improving the display flexibility of the cloud phone user interface.

[0020] In one possible implementation, after the terminal device displays updated content on the terminal device based on an event response message, when the terminal device does not receive a user input event within a preset time, the terminal device receives an event message sent by the cloud server, and the event message is used to instruct the terminal device to hide the navigation bar on the cloud phone interface.

[0021] In an embodiment of the present application, when the user does not operate the virtual buttons of the navigation bar in the cloud phone user interface within a predetermined time, the cloud server will hide the navigation bar, thereby increasing the screen ratio of the visible area of ​​the cloud phone user interface.

[0022] In one possible implementation, when the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar is a virtual navigation button. In response to a user's short press of the virtual navigation button, the terminal device sends a short press event instruction to the cloud server. The short press event instruction is used to request the cloud server to generate the cloud phone's homepage interface. The short press duration is less than a first threshold, for example, 200 milliseconds.

[0023] In the embodiment of the present application, when the navigation bar is a virtual navigation button, when the user wants the cloud phone user interface to display the home page interface, the user can control the cloud server to generate the cloud phone home page interface by short pressing the virtual navigation button in the cloud phone user interface, that is, the user can operate the virtual navigation button in the cloud phone user interface through different key press durations, thereby realizing different operation intentions, thereby improving the user's flexibility in controlling the cloud phone user interface.

[0024] In one possible implementation, when the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar is a virtual navigation button. The terminal device responds to the user's long press action on the virtual navigation button and sends a long press event instruction to the cloud server. The long press event instruction is used to request the cloud server to generate a menu interface for the cloud phone. The button duration of the long press action is greater than or equal to the first threshold.

[0025] In the embodiment of the present application, when the navigation bar is a virtual navigation button, when the user wants the cloud phone user interface to display the menu interface, the user can long press the virtual navigation button in the cloud phone user interface to control the cloud server to generate the cloud phone menu interface. In the embodiment of the present application, the user can operate the virtual navigation button in the cloud phone user interface by different press durations, thereby realizing different user operation intentions and improving the user's flexibility in controlling the cloud phone user interface.

[0026] On the second aspect, the present application example provides an interactive device for a cloud phone, which includes a transceiver unit and a processing unit. The transceiver unit is used to send a first event instruction to the cloud server in response to a first input event of the user, and the first event instruction is used to request the cloud server to generate updated content for the cloud phone service. The transceiver unit is also used to receive an event response message sent by the cloud server, and the event response message includes the updated content generated by the cloud server based on the event instruction. The processing unit is used to display the updated content on the terminal device based on the event response message, and the updated content includes one or more of the following: a navigation bar, a previous interface, and a next interface.

[0027] In one possible implementation, the first input event includes one or more of the following: clicking or sliding the screen, shaking the device, a custom gesture, and voice control.

[0028] In one possible implementation, the updated content is a navigation bar, which includes one or more of the following virtual buttons: a return button, a home button, and a menu button. The navigation bar is displayed at the bottom of the cloud phone interface, or the navigation bar is displayed in a local area of ​​the cloud phone interface.

[0029] In one possible implementation, the transceiver unit is also used to send a second event instruction to the cloud server in response to a second input event of the user on the virtual key in the navigation bar. The second event instruction is used to request the cloud server to generate a cloud phone interface corresponding to the virtual key. The second input event is one or more of the following: clicking the screen, custom gestures, and voice control.

[0030] In a possible implementation, the transceiver unit is further used to receive an event message sent by the cloud server when the terminal device does not receive a user input event within a preset time, and the event message is used to instruct the terminal device to hide the navigation bar in the cloud phone interface.

[0031] In one possible implementation, when the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar is a virtual navigation button, and the transceiver unit is also used to respond to the user's short press action on the virtual navigation button, and send a short press event instruction to the cloud server. The short press event instruction is used to request the cloud server to generate a home page interface of the cloud phone, and the key duration of the short press action is less than a first threshold.

[0032] In one possible implementation, when the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar is a virtual navigation button, and the transceiver unit is also used to respond to the user's long press action on the virtual navigation button, and send a long press event instruction to the cloud server. The long press event instruction is used to request the cloud server to generate a menu interface for the cloud phone, and the button duration of the long press action is greater than or equal to the first threshold.

[0033] In a third aspect, an embodiment of the present application provides a computing device, comprising a processor coupled to a memory, the processor being used to store instructions. When the instructions are executed by the processor, the computing device executes the method described in the first aspect or any possible implementation of the first aspect.

[0034] In a fourth aspect, an embodiment of the present application provides a computing device cluster, which includes one or more computing devices, each of which includes a processor coupled to a memory, and the processor is used to store instructions. When the instructions are executed by the processor, the computing device cluster executes the method described in the first aspect or any possible implementation method of the first aspect.

[0035] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium having instructions stored thereon. When the instructions are executed, the computer executes the method described in the first aspect or any possible implementation method of the first aspect.

[0036] In a sixth aspect, an embodiment of the present application provides a computer program product, which includes instructions. When the instructions are executed, the computer implements the method described in the first aspect or any possible implementation method of the first aspect.

[0037] It can be understood that the beneficial effects that can be achieved by any of the above-mentioned cloud phone interactive devices, computing devices, computing device clusters, computer-readable media or computer program products can refer to the beneficial effects in the corresponding methods and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] FIG1 is a schematic diagram of the system architecture of a cloud phone system provided in an embodiment of the present application;

[0039] FIG2 is a flow chart of a cloud phone interaction method provided in an embodiment of the present application;

[0040] FIG3 is a schematic diagram of a cloud phone user interface provided in an embodiment of the present application;

[0041] FIG4 is a schematic diagram of another cloud phone user interface provided in an embodiment of the present application;

[0042] FIG5 is a schematic diagram of another cloud phone user interface provided in an embodiment of the present application;

[0043] FIG6 is a schematic diagram of another cloud phone user interface provided in an embodiment of the present application;

[0044] FIG7 is a schematic diagram of another cloud phone user interface provided in an embodiment of the present application;

[0045] FIG8 is a schematic diagram of a cloud phone interaction device provided in an embodiment of the present application;

[0046] FIG9 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0047] FIG10 is a schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0048] FIG11 is a schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The embodiments of the present application provide a cloud phone interaction method and device for improving the screen ratio of the visible area and the interaction flexibility during the interaction process of the cloud phone.

[0050] 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 sequential sequence. 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" and "having," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., 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.

[0051] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0052] First, some terms involved in the embodiments of the present application are introduced to facilitate those skilled in the art to understand the technical solutions.

[0053] The navigation bar refers to the button display window used for interactive page switching in the terminal display device, such as the view window at the bottom of the Android phone that carries the return, home page, and multi-tasking page.

[0054] Interface navigation refers to the interactive switching operations of pages in the terminal device, such as returning to the previous page, returning to the home page, displaying the multitasking page, etc.

[0055] A floating ball is an interactive small view in the user interface that carries extended functions. It is usually a movable and clickable small ball button icon that floats at the top of the view. Clicking the floating ball will open the page view that carries the function and can be moved within the page.

[0056] The screen-to-body ratio refers to the ratio of the visible and operable area of ​​the screen to the front area of ​​the entire device. The larger the screen-to-body ratio, the larger the visible and operable area, and vice versa.

[0057] In order to make the technical solution of the present application clearer and easier to understand, the system architecture of the present application is introduced below with reference to the accompanying drawings.

[0058] Please refer to Figure 1, which is a schematic diagram of the system architecture of a cloud phone interactive system provided as an example in this application. In the example shown in Figure 1, cloud phone system 10 includes a terminal device 101 and a cloud server 102. Terminal device 101 includes a client application 1011 and a user interface component 1012, and cloud server 102 includes a cloud-side processing module 1021 and an input event module 1022. The following describes the specific functions of each component of cloud phone system 10.

[0059] Terminal device 101 is the device through which users interact with the cloud phone's cloud server 102. Cloud phones support a variety of terminal devices. For example, terminal device 101 includes, but is not limited to, mobile phones, tablet computers, and laptop computers. Terminal device 101 can connect to the cloud phone's cloud server 102 via a network, allowing users to remotely access and control applications and functions on the cloud phone through terminal device 101.

[0060] The terminal device 101 includes a client application 1011 and a user interface component 1012, wherein the client application 1011 includes one or more applications installed in the terminal device 101, the client application 1011 is used to establish a connection with the cloud server 102 and provide a user interface for the cloud phone. Users can access the cloud phone system provided by the cloud server 102 through the client application 1011.

[0061] The user interface component 1012 is used to display the user interface of the cloud phone. The user interface component 1012 is also used to obtain user input events and transmit the user input events to the cloud server 102. The user input events include various types of device input events, such as user operations such as screen clicks and slides, user input operations on the keyboard, and user voice control operations on the microphone.

[0062] Cloud server 102 is a server that provides cloud phones. Using virtualization technology, cloud server 102 can create multiple cloud phone instances on the server, each with its own independent operating system and application environment. Cloud server 102 is also used to receive cloud phone operation instructions from users of terminal device 101, provide computing and storage resources for the cloud phone based on the user's instructions, and manage applications and data on the cloud phone based on the instructions.

[0063] Cloud server 102 includes a cloud-side processing module 1021 and an input event module 1022. Cloud-side processing module 1021 is used to implement the core functions of the mobile phone system, including managing user login sessions, verifying user identities, and allocating and managing cloud phone instances. Cloud-side processing module 1021 is also used to respond to operation instructions sent by terminal device 101, generate a response message to the operation instruction, and send a response message corresponding to the operation instruction to terminal device 101. The response message to the operation instruction includes the cloud phone user interface generated by cloud server 102.

[0064] The input event module 1022 records user input events from the terminal device 101. The cloud-side processing module 1021 can obtain user input events to the cloud phone from the input event module 1022 and respond accordingly. The input events recorded by the input event module 1022 include user input events based on the various hardware components of the terminal device 101, such as the keyboard, mouse, microphone, and touch screen.

[0065] Based on the cloud phone system 10 shown in Figure 1, the present application also provides a cloud phone interaction method. The following describes the cloud phone interaction method provided in the present application embodiment in conjunction with the embodiments.

[0066] Please refer to Figure 2, which is a flow chart of a cloud phone interaction method provided by an embodiment of the present application. In the example shown in Figure 2, the method includes the following steps:

[0067] 201. The terminal device 101 sends a first event instruction to the cloud server 102, where the first event instruction is used to request the cloud server to generate updated content for the cloud phone service.

[0068] In response to the user's first input event, the terminal device 101 sends a first event instruction to the cloud server 102. The first event instruction is used to request the cloud server 102 to generate updated content for the cloud phone service. The updated content of the cloud phone service is the cloud phone interface generated by the cloud server 102 based on the first event instruction.

[0069] In the embodiment of the present application, the user's first input event includes one or more of the following: clicking or sliding the screen, shaking the device, a custom gesture, and voice control. The update content of the cloud phone service includes one or more of the following: displaying a navigation bar in the cloud phone user interface, displaying the previous interface of the cloud phone user interface, and displaying the next interface of the cloud phone user interface.

[0070] For example, in an example of step 201, when a user is using a cloud phone through a terminal device 101, when the user wants to display a navigation bar on the cloud phone user interface, the user clicks on the cloud phone user interface displayed on the screen of the terminal device 101. The terminal device 101 responds to the user's screen click action and sends a screen click event instruction to the cloud server 102. The screen click event instruction is used to request the cloud server 102 to generate a cloud phone user interface containing a navigation bar.

[0071] In one possible implementation, in response to the user sliding the screen to the right, the terminal device 101 sends a right-swipe event instruction to the cloud server 102, where the right-swipe event instruction is used to request the cloud server 102 to return to the previous user interface of the current user interface.

[0072] Specifically, when the user wants the cloud phone user interface to return to the previous interface, after the user slides the screen to the right, the user interface component 1012 of the terminal device 101 will obtain the right-swipe input event and send the key code (key code) corresponding to the right-swipe input event to the cloud server 102. The cloud server 102 records the right-swipe input event corresponding to the key code to the input event module 1022, and requests the cloud-side processing module 1021 to generate the previous interface of the current user interface.

[0073] Please refer to Figure 3, which is a schematic diagram of a cloud phone interaction provided in an embodiment of the present application. In the example shown in Figure 3, when a user uses the cloud phone service on a terminal device 101, the terminal device 101 first establishes a network connection between the terminal device 101 and the cloud server 102 based on the client application 1011 corresponding to the cloud phone. After that, the terminal device 101 receives the user interface sent by the cloud server 102 and displays the cloud phone user interface sent by the cloud server 102 based on the user interface component 1012.

[0074] In Figure a of the example shown in Figure 3, when the user uses the cloud phone service based on the terminal device 101, when the user wants to return to the previous user interface from the current user interface of the cloud phone, the user can slide the screen of the terminal device 101 to the right. The terminal device 101 responds to the user's action of sliding the screen to the right, and the terminal device 101 sends a right-swipe event instruction to the cloud server 102.

[0075] In one possible implementation, in response to the user's left-swiping screen action, the terminal device 101 sends a left-swiping event instruction to the cloud server 102, where the left-swiping event instruction is used to request the cloud server 102 to go to the next user interface of the current user interface.

[0076] Specifically, when the user wants to go to the next interface of the cloud phone user interface, the user slides the screen to the left, and the user interface component 1012 of the terminal device 101 obtains the left-swipe input event and sends the key code corresponding to the left-swipe input event to the cloud server 102. The cloud server 102 records the left-swipe input event corresponding to the key code to the input event module 1022, and requests the cloud-side processing module 1021 to generate the next interface of the current user interface.

[0077] Please continue to refer to Figure 3. In the example figure b shown in Figure 3, when the user uses the cloud phone service based on the terminal device 101, when the user wants to go from the current user interface of the cloud phone to the next user interface, the user can slide the screen of the terminal device 101 to the left. The terminal device 101 responds to the user's left sliding action, and the terminal device 101 sends a left sliding event instruction to the cloud server 102.

[0078] In one possible implementation, in response to a user's screen-clicking action, the terminal device 101 sends a click event instruction to the cloud server 102 , where the click event instruction is used to request the cloud server 102 to display a navigation bar in the current user interface.

[0079] Specifically, when the user wants the cloud phone user interface to display a navigation bar, the user clicks the screen, and the user interface component 1012 of the terminal device 101 obtains the click input event and sends the key code corresponding to the click input event to the cloud server 102. The cloud server 102 records the click event corresponding to the key code to the input event module 1022, and requests the cloud side processing module 1021 of the cloud server 102 to generate a cloud phone user interface that displays the navigation bar.

[0080] Please refer to Figure 4, which is a schematic diagram of another cloud phone interaction provided by an embodiment of the present application. In the example shown in Figure 4, after the terminal device 101 establishes a network connection with the cloud server 102, the terminal device 101 displays the cloud phone user interface. In step a of the example shown in Figure 4, when the user uses the cloud phone through the terminal device 101, when the user wants to display the navigation bar in the current cloud phone user interface of the cloud phone, the user can click on the screen of the terminal device 101, and the terminal device 101 responds to the user's screen click action and sends a click event instruction to the cloud server 102.

[0081] It should be noted that in addition to controlling the cloud server 102 to display the navigation bar in the cloud phone user interface by clicking the screen, the user can control the cloud server 102 to display the navigation bar in the cloud phone user interface through other specified input events, such as shaking the terminal device, voice control, custom gestures on the screen, etc., without specific limitations.

[0082] 202. The terminal device receives an event response message sent by the cloud server, where the event response message includes update content generated by the cloud server based on the event instruction.

[0083] After receiving the first event instruction sent by the terminal device 101, the cloud server 102 generates an event response message based on the first event instruction sent by the terminal device 101, and sends the event response message to the terminal device 101. The event response message includes the updated content generated by the cloud server 102 based on the event instruction.

[0084] For example, in an example of step 202, the terminal device 101 responds to the user's screen click action and sends a screen click event instruction to the cloud server 102. The cloud server 102 generates a response message corresponding to the screen click event instruction based on the screen click event instruction. The response message includes a cloud phone user interface that displays a navigation bar. The cloud server 102 sends a response message corresponding to the screen click event instruction to the terminal device 101.

[0085] In one possible implementation, when the first event instruction is a right-swipe event instruction, the cloud server 102 generates an event response message based on the right-swipe event instruction, and the event response message instructs the cloud phone user interface to return to the previous user interface of the current user interface.

[0086] In a possible implementation, when the first event instruction is a left-swipe event instruction, the cloud server 102 generates an event response message based on the left-swipe event instruction, and the event response message instructs the cloud phone to go to the next user interface of the current user interface.

[0087] Please continue to refer to Figure 3. In Figure a of the example shown in Figure 3, after the cloud server 102 receives the right-swipe event instruction sent by the terminal device 101, the cloud server 102 generates a response message of the right-swipe event instruction based on the right-swipe event instruction. The response message of the right-swipe event instruction includes the previous interface of the current user interface of the cloud phone.

[0088] In Figure b of the example shown in Figure 3, after the cloud server 102 receives the left-swipe event instruction sent by the terminal device 101, the cloud server 102 generates a response message of the left-swipe event instruction based on the left-swipe event instruction, and the response message of the left-swipe event instruction includes the next interface of the current user interface of the cloud phone.

[0089] In a possible implementation, when the first event instruction is a click event instruction, the cloud server 102 generates an event response message based on the click event instruction, and the event response message instructs the cloud phone to display a navigation bar in the current user interface.

[0090] Please continue to refer to Figure 4. In step b of the example shown in Figure 4, after the cloud server 102 receives the click event instruction sent by the terminal device 101, the cloud server 102 generates a response message of the click event instruction based on the click event instruction. The response message of the click event instruction includes a cloud phone user interface that displays a navigation bar. The cloud server 102 sends a response message of the click event instruction to the terminal device 101, so that the cloud phone user interface in the terminal device 101 displays a navigation bar.

[0091] 203. The terminal device displays updated content on the terminal device based on the event response message, where the updated content includes one or more of the following: a navigation bar, a previous interface, and a next interface.

[0092] After the terminal device 101 receives the event response message sent by the cloud server 102, the updated content is displayed on the terminal device 101 based on the event response message. The updated content includes one or more of the following: the navigation bar of the cloud phone, the previous interface of the cloud phone user interface, and the next interface of the cloud phone user interface.

[0093] For example, in one example of step 202, when a user wants to display a navigation bar on the cloud phone user interface, the user clicks the screen, and the terminal device 101 sends a screen click event instruction to the cloud server 102, and the cloud server 102 sends a response message corresponding to the screen click event instruction to the terminal device 101. After receiving the response message corresponding to the screen click event instruction, the terminal device 101 displays the cloud phone user interface including the navigation bar based on the response message.

[0094] In one possible implementation, when the event response message is an event response message corresponding to a right-swipe event instruction, the terminal device 101 displays the previous user interface of the cloud phone on the terminal device 101 based on the event response message corresponding to the right-swipe event instruction.

[0095] In one possible implementation, when the event response message is an event response message corresponding to a left-swipe event instruction, the terminal device 101 displays the next user interface of the cloud phone on the terminal device 101 based on the event response message corresponding to the left-swipe event instruction.

[0096] Please continue to refer to Figure 3. In the example figure a shown in Figure 3, when the event response message received by the terminal device 101 is the event response message corresponding to the right-swipe event instruction sent by the cloud server 102, the terminal device 101 parses the user interface corresponding to the event response message and displays the previous interface of the current user interface of the cloud phone on the terminal device 101.

[0097] In the example figure b shown in Figure 3, when the event response message received by the terminal device 101 is the event response message corresponding to the left-swipe event instruction sent by the cloud server 102, the terminal device 101 parses the user interface corresponding to the event response message and displays the next interface of the current user interface of the cloud phone on the terminal device 101.

[0098] In one possible implementation, when the event response message is an event response message corresponding to a click event instruction, the terminal device 101 displays a navigation bar of the user display interface of the cloud phone on the terminal device 101 based on the event response message corresponding to the click event instruction.

[0099] Please continue to refer to Figure 4. In the example shown in Figure 4, when the event response message received by the terminal device 101 is an event response message corresponding to the click event instruction sent by the cloud server 102, the terminal device 101 parses the user interface corresponding to the event response message and displays the navigation bar in the cloud phone user interface of the terminal device 101.

[0100] In one possible implementation, when the updated content is a navigation bar, the navigation bar is displayed at the bottom of the cloud phone interface, or the navigation bar is displayed in a local area of ​​the cloud phone interface, and the navigation bar includes one or more of the following virtual buttons: a back button, a home button, and a menu button. When the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar can be a virtual navigation button. The navigation bar can be displayed semi-transparently in the cloud phone user interface.

[0101] Please refer to Figure 5, which is a schematic diagram of a cloud phone user interface provided by an embodiment of the present application. In the example shown in Figure 5, Figure a is a schematic diagram of the navigation bar displayed at the bottom of the cloud phone interface, and Figure b is a schematic diagram of the navigation bar displayed locally on the cloud phone interface. In the example shown in Figure a, the navigation bar at the bottom of the cloud phone interface includes virtual buttons such as the return button, home button, and menu button. In the example shown in Figure b, the navigation bar displayed in a local area of ​​the cloud phone interface is a virtual navigation button, and the virtual navigation button can also be a floating ball, which is not specifically limited.

[0102] It can be understood that in the embodiment of the present application, in addition to being located at the bottom display value of the cloud phone user interface, the navigation bar can also be located in other positions of the cloud phone user interface, such as the top area, left edge area or right edge area of ​​the cloud phone user interface, without specific limitation.

[0103] In one possible implementation, after the terminal device 101 displays updated content on the terminal device based on an event response message, when the updated content is a navigation bar, the terminal device 101 responds to the user's second input event on a virtual key in the navigation bar, and the terminal device 101 sends a second event instruction to the cloud server 102. The second event instruction is used to request the cloud server 102 to generate a cloud phone interface corresponding to the virtual key. The second input event is one or more of the following: clicking the screen, a custom gesture, and voice control.

[0104] Please continue to refer to Figure 5. In Figure a of the example shown in Figure 5, after the terminal device 101 displays the navigation bar at the bottom of the cloud phone user interface based on the event response message sent by the cloud server 102, the navigation bar at the bottom of the cloud phone interface includes virtual buttons such as the return button, home button and menu button, and the user can further operate the virtual buttons in the navigation bar.

[0105] For example, when a user wants to return to the previous interface of the current user interface of the cloud phone, the user can click the back button in the navigation bar of the cloud phone interface. The terminal device 101 responds to the user's back button click action event, and the terminal device 101 sends a back button click event instruction to the cloud server 102. The return button click event instruction is used to request the cloud server 102 to generate the previous interface of the current cloud phone user interface. After the cloud server 102 generates the previous interface of the current cloud phone user interface based on the return button click event instruction, it sends an event response message corresponding to the return button click event instruction to the terminal device 101. The terminal device 101 displays the previous user interface of the cloud phone user interface based on the event response message.

[0106] In Figure b of the example shown in Figure 5, the navigation bar is a navigation key in the local area of ​​the mobile phone user interface. After the terminal device 101 displays the navigation button in the local area of ​​the cloud phone's user interface based on the event response message sent by the cloud server 102, the user can further operate the navigation button.

[0107] For example, a user can click on a virtual navigation button on the cloud phone user interface. The terminal device 101 responds to the user's virtual navigation button click action and sends a virtual navigation button click event instruction to the cloud server 102. The cloud server 102 generates updated content for the cloud phone user interface based on the virtual navigation button click event instruction. The updated content includes the navigation bar content that is expanded and displayed in the current cloud phone user interface. The navigation bar content includes a return button, a home button, and a menu button. The cloud server 102 sends an event response message corresponding to the virtual navigation button click event instruction to the terminal device 101. The terminal device 101 displays the expanded navigation bar of the cloud phone on the terminal device 101 based on the event response message.

[0108] In one possible implementation, when the updated content is a navigation bar, when the terminal device 101 does not receive a user input event within a preset time, the input event includes the user's operation on the navigation bar of the cloud phone user interface, that is, the user does not operate the navigation bar of the cloud phone user interface within the time, then the terminal device 101 receives an event message sent by the cloud server 102, and the event message is used to instruct the terminal device 101 to hide the navigation bar in the cloud phone interface, and the preset time is, for example, 3 to 8 seconds.

[0109] Please refer to Figure 6, which is a schematic diagram of a cloud phone user interface hiding a navigation bar provided in an embodiment of the present application. In the example shown in Figure 6, the cloud phone user interface displayed by terminal device 101 includes a navigation bar. If terminal device 101 does not receive a user input event within a preset time, that is, the user does not operate the navigation bar of the cloud phone user interface within the predetermined time, cloud server 102 sends an event message to terminal device 101, and the event message is used to instruct terminal device 101 to hide the navigation bar in the cloud phone interface.

[0110] In the example shown in Figure 6, when the navigation bar is a virtual navigation button for a local area, if the terminal device 101 does not receive the user's input event within the preset time, that is, the user does not operate the virtual navigation button of the cloud phone user interface within the predetermined time, then the cloud server 102 sends an event message to the terminal device 101, and the event message is used to instruct the terminal device 101 to hide the virtual navigation button in the cloud phone interface.

[0111] In one possible implementation, when the navigation bar is a virtual navigation button for a local area, the terminal device 101 sends a short press event instruction to the cloud server 102 in response to the user's short press action on the virtual navigation button. The short press event instruction is used to request the cloud server 102 to generate a homepage interface of the cloud phone. The key duration of the short press action is less than a first threshold, for example, 200 to 500 milliseconds.

[0112] Please refer to Figure 7, which is an interactive diagram of a virtual navigation button of a cloud phone interface provided by an embodiment of the present application. In the example shown in Figure 7, the terminal device 101 sends an event response message based on the cloud server 102. After the terminal device 101 displays the virtual navigation button of the cloud phone user interface, when the user wants the terminal device 101 to display the home page interface of the cloud phone, the user can short press the virtual navigation button. For example, the user short presses the virtual navigation button for 200 milliseconds. The terminal device 101 responds to the user's short press action and sends a short press event instruction to the cloud server 102. The cloud server 102 generates the home page interface of the cloud phone based on the short press event instruction, and sends an event response message corresponding to the short press event instruction to the terminal device 101. The terminal device 101 displays the home page interface of the cloud phone user interface on the terminal device 101 based on the event response message.

[0113] In one possible implementation, when the navigation bar is a virtual navigation key, the terminal device 101 sends a long press event instruction to the cloud server 102 in response to the user's long press action on the virtual navigation key. The long press event instruction is used to request the cloud server 102 to generate a menu interface for the cloud phone, and the key duration of the long press action is greater than or equal to the first threshold.

[0114] Please continue to refer to Figure 7. In the example shown in Figure 7, the navigation bar of the cloud phone user interface is used as a virtual navigation key for a local area. When the user wants the terminal device 101 to display the menu interface of the cloud phone, the user can long press the virtual navigation button. For example, the user long presses the virtual navigation button for 500 milliseconds. The terminal device 101 responds to the user's long press action and sends a long press event instruction to the cloud server 102. After receiving the long press event instruction, the cloud server 102 generates the menu interface of the cloud phone user interface based on the long press event instruction, and sends an event response message corresponding to the long press event instruction to the terminal device 101. The event response message corresponding to the long press event instruction contains the menu interface of the cloud phone user interface. The terminal device 101 displays the menu interface of the cloud phone user interface on the terminal device 101 based on the event response message.

[0115] It can be seen from the above embodiments that the terminal device 101 of the cloud phone system in the embodiment of the present application can send event instructions to the cloud server 102 based on the user's input events, so that the cloud server 102 can control the cloud phone user interface based on the user's specified input events, thereby improving the display flexibility of the cloud phone user interface.

[0116] Based on the above method embodiment, the embodiment of the present application also provides an interactive device for a cloud phone. The interactive device for the cloud phone provided by the embodiment of the present application is described in detail below.

[0117] Please refer to Figure 8, which is a schematic diagram of the structure of a cloud phone interaction device provided in an embodiment of the present application. In the example shown in Figure 8, the cloud phone interaction device 800 is used to implement the various steps performed by the cloud phone system 10 in the above embodiments. The cloud phone interaction device 800 includes a transceiver unit 801 and a processing unit 802.

[0118] The transceiver unit 801 is configured to send a first event instruction to the cloud server in response to a first input event from the user. The first event instruction is configured to request the cloud server to generate updated content for the cloud phone service. The transceiver unit 801 is further configured to receive an event response message from the cloud server. The event response message includes updated content generated by the cloud server based on the event instruction. The processing unit 802 is configured to display the updated content on the terminal device based on the event response message. The updated content includes one or more of the following: a navigation bar, a previous interface, and a next interface.

[0119] In one possible implementation, the first input event includes one or more of the following: clicking or sliding the screen, shaking the device, a custom gesture, and voice control.

[0120] In one possible implementation, the updated content is a navigation bar, which includes one or more of the following virtual buttons: a return button, a home button, and a menu button. The navigation bar is displayed at the bottom of the cloud phone interface, or the navigation bar is displayed in a local area of ​​the cloud phone interface.

[0121] In one possible implementation, the transceiver unit 801 is also used to send a second event instruction to the cloud server in response to a second input event of the user on the virtual key in the navigation bar. The second event instruction is used to request the cloud server to generate a cloud phone interface corresponding to the virtual key. The second input event is one or more of the following: clicking the screen, custom gestures, and voice control.

[0122] In a possible implementation, the transceiver unit 801 is also used to receive an event message sent by the cloud server when the terminal device does not receive a user input event within a preset time. The event message is used to instruct the terminal device to hide the navigation bar in the cloud phone interface.

[0123] In one possible implementation, when the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar is a virtual navigation button, and the transceiver unit 801 is also used to respond to the user's short press action on the virtual navigation button, and send a short press event instruction to the cloud server. The short press event instruction is used to request the cloud server to generate a home page interface of the cloud phone, and the key duration of the short press action is less than the first threshold.

[0124] In one possible implementation, when the navigation bar is displayed in a local area of ​​the cloud phone interface, the navigation bar is a virtual navigation button, and the transceiver unit 801 is also used to respond to the user's long press action on the virtual navigation button, and send a long press event instruction to the cloud server. The long press event instruction is used to request the cloud server to generate a menu interface for the cloud phone, and the key duration of the long press action is greater than or equal to the first threshold.

[0125] It is understandable that the transceiver unit 801 and the processing unit 802 in the cloud phone interaction device 800 can be mapped as functional modules to the various modules in the cloud phone system 10 in Figure 1, thereby realizing the functions of each module in the cloud phone system 10.

[0126] It should be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or they can all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the memory in the form of a program, called by a certain processing element of the device and perform the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or in the form of software called through the processing element.

[0127] It is worth noting that, for the sake of simplicity of description, the above method embodiments are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited to the order of the actions described. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required for this application.

[0128] Other reasonable step combinations that can be thought of by those skilled in the art based on the above description also fall within the scope of protection of this application. Secondly, those skilled in the art should also be familiar with that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by this application.

[0129] Please refer to Figure 9, which is a schematic diagram of the structure of a computing device provided in an embodiment of the present application. As shown in Figure 9, the computing device 900 includes: a processor 901, a memory 902, a communication interface 903, and a bus 904. The processor 901, the memory 902, and the communication interface 903 are coupled via a bus (not labeled in the figure). The memory 902 stores instructions. When the execution instructions in the memory 902 are executed, the computing device 900 executes the method executed by the terminal device or cloud server in the above method embodiment.

[0130] The computing device 900 may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For example, when a unit in the apparatus can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0131] The processor 901 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0132] The memory 902 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0133] The memory 902 stores executable program code, and the processor 901 executes the executable program code to respectively implement the functions of the aforementioned units or modules, thereby implementing the above-mentioned cloud phone interaction method. That is, the memory 902 stores instructions for executing the above-mentioned cloud phone interaction method.

[0134] The communication interface 903 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 900 and other devices or a communication network.

[0135] In addition to the data bus, bus 904 may also include a power bus, a control bus, and a status signal bus. The bus may be a Peripheral Component Interconnect Express (PCIe) bus, an Extended Industry Standard Architecture (EISA) bus, a unified bus (Ubus or UB), a Compute Express Link (CXL), or a Cache Coherent Interconnect for Accelerators (CCIX). Buses can be categorized as address buses, data buses, and control buses.

[0136] Please refer to Figure 10 , which is a schematic diagram of a computing device cluster provided in an embodiment of the present application. As shown in Figure 10 , the computing device cluster 1000 includes at least one computing device 900 .

[0137] As shown in Figure 10, the computing device cluster 1000 includes at least one computing device 900. The memory 902 in one or more computing devices 900 in the computing device cluster 1000 may store the same instructions for executing the above-mentioned cloud phone interaction method.

[0138] In some possible implementations, the memory 902 of one or more computing devices 900 in the computing device cluster 1000 may also store partial instructions for executing the above-mentioned cloud phone interaction method. In other words, the combination of one or more computing devices 900 can jointly execute the instructions for executing the above-mentioned cloud phone interaction method.

[0139] It should be noted that the memory 902 in different computing devices 900 in the computing device cluster 1000 can store different instructions, each for executing part of the functions of the above-mentioned cloud phone interaction device. In other words, the instructions stored in the memory 902 in different computing devices 900 can implement the functions of one or more modules in the processing unit and the transceiver unit.

[0140] In some possible implementations, one or more computing devices 900 in the computing device cluster 1000 may be connected via a network, which may be a wide area network or a local area network.

[0141] Please refer to Figure 11, which is a schematic diagram of computer devices in a computer cluster provided by an embodiment of the present application connected via a network. As shown in Figure 11, two computing devices 900A and 900B are connected via a network. Specifically, the connection to the network is through a communication interface in each computing device.

[0142] In one possible implementation, the memory of the computing device 900A stores instructions for executing the functions of the transceiver unit, while the memory of the computing device 900B stores instructions for executing the functions of the processing unit.

[0143] It should be understood that the functions of the computing device 900A shown in Figure 11 may also be completed by multiple computing devices. Similarly, the functions of the computing device 900B may also be completed by multiple computing devices.

[0144] In another embodiment of the present application, a computer-readable storage medium is provided, in which computer-executable instructions are stored. When the processor of the device executes the computer-executable instructions, the device executes the method executed by the cloud phone system in the above method embodiment.

[0145] In another embodiment of the present application, a computer program product is provided, the computer program product including computer-executable instructions stored in a computer-readable storage medium. When a processor of a device executes the computer-executable instructions, the device executes the method executed by the cloud phone system in the above method embodiment.

[0146] 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.

[0147] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0148] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0149] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0150] 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 is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment 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.

Claims

1. An interaction method for a cloud mobile phone, characterized in that, Applied to a cloud mobile phone system, the cloud mobile phone system includes a terminal device and a cloud server, and the cloud server is used to provide cloud mobile phone services to the terminal device. The method includes: The terminal device responds to a first input event of the user and sends a first event instruction to the cloud server. The first event instruction is used to request the cloud server to generate update content of the cloud mobile phone service; The terminal device receives an event response message sent by the cloud server. The event response message includes the update content generated by the cloud server based on the event instruction; The terminal device displays the update content on the terminal device based on the event response message. The update content includes one or more of the following: a navigation bar, a previous interface, and a next interface.

2. The method according to claim 1, characterized in that, The first input event includes one or more of the following: clicking or swiping the screen, shaking the device, a custom gesture, and voice control.

3. The method according to claim 1 or 2, characterized in that, The update content is a navigation bar. The navigation bar includes one or more of the following virtual keys: a back key, a home key, and a menu key. The navigation bar is displayed at the bottom of the cloud mobile phone interface, or the navigation bar is displayed in a partial area of the cloud mobile phone interface.

4. The method according to claim 3, characterized in that The method further includes: The terminal device responds to a second input event of the user on the virtual key in the navigation bar and sends a second event instruction to the cloud server. The second event instruction is used to request the cloud server to generate a cloud mobile phone interface corresponding to the virtual key. The second input event includes one or more of the following: clicking the screen, a custom gesture, and voice control.

5. The method according to claim 3 or 4, characterized in that, After the terminal device displays the update content on the terminal device based on the event response message, the method further includes: When the terminal device does not receive an input event from the user within a preset time, the terminal device receives an event message sent by the cloud server. The event message is used to instruct the terminal device to hide the navigation bar on the cloud mobile phone interface.

6. The method according to any one of claims 3 to 5, characterized in that, When the navigation bar is displayed in a partial area of the cloud mobile phone interface, the navigation bar is a virtual navigation key. The method further includes: The terminal device responds to a short press action of the user on the virtual navigation key and sends a short press event instruction to the cloud server. The short press event instruction is used to request the cloud server to generate the home page interface of the cloud mobile phone. The key press duration of the short press action is less than a first threshold.

7. The method according to any one of claims 3 to 5, characterized in that, When the navigation bar is displayed in a partial area of the cloud mobile phone interface, the navigation bar is a virtual navigation key. The method further includes: The terminal device responds to a long press action of the user on the virtual navigation key and sends a long press event instruction to the cloud server. The long press event instruction is used to request the cloud server to generate the menu interface of the cloud mobile phone. The key press duration of the long press action is greater than or equal to the first threshold.

8. An interaction device for a cloud mobile phone, characterized in that, Applied to a cloud mobile phone system, the device includes: A transceiver unit, configured to respond to a first input event of the user and send a first event instruction to the cloud server. The first event instruction is used to request the cloud server to generate update content of the cloud mobile phone service; The transceiver unit is further configured to receive an event response message sent by the cloud server, where the event response message includes the update content generated by the cloud server based on the event instruction; The processing unit is configured to display the update content on the terminal device based on the event response message, where the update content includes one or more of the following: a navigation bar, a previous interface, and a next interface.

9. The device according to claim 8, characterized in that, The first input event includes one or more of the following: clicking or swiping the screen, shaking the device, a custom gesture, and voice control.

10. The device according to claim 8 or 9, characterized in that, The update content is a navigation bar, and the navigation bar includes one or more of the following virtual keys: a back key, a home key, and a menu key. The navigation bar is displayed at the bottom of the cloud phone interface, or the navigation bar is displayed in a partial area of the cloud phone interface.

11. The device according to claim 10, characterized in that, The transceiver unit is further configured to: In response to a second input event of the user on the virtual key in the navigation bar, send a second event instruction to the cloud server, where the second event instruction is used to request the cloud server to generate a cloud phone interface corresponding to the virtual key. The second input event includes one or more of the following: clicking the screen, a custom gesture, and voice control.

12. The device according to claim 10 or 11, characterized in that, The transceiver unit is further configured to: When the terminal device does not receive an input event of the user within a preset time, receive an event message sent by the cloud server, where the event message is used to instruct the terminal device to hide the navigation bar on the cloud phone interface.

13. The device according to any one of claims 10 to 12, characterized in that, When the navigation bar is displayed in a partial area of the cloud phone interface, the navigation bar is a virtual navigation key, and the transceiver unit is further configured to: In response to a short press action of the user on the virtual navigation key, send a short press event instruction to the cloud server, where the short press event instruction is used to request the cloud server to generate a home interface of the cloud phone. The key duration of the short press action is less than a first threshold.

14. The device according to any one of claims 10 to 13, characterized in that, When the navigation bar is displayed in a partial area of the cloud phone interface, the navigation bar is a virtual navigation key, and the transceiver unit is further configured to: In response to a long press action of the user on the virtual navigation key, send a long press event instruction to the cloud server, where the long press event instruction is used to request the cloud server to generate a menu interface of the cloud phone. The key duration of the long press action is greater than or equal to the first threshold.

15. A computing device, characterized in that, It includes a processor, and the processor is coupled to a memory. The processor is configured to store instructions, and when the instructions are executed by the processor, the computing device is caused to execute the method according to any one of claims 1 to 7.

16. A cluster of computing devices, characterized in that, It includes at least one computing device, and the computing device includes a processor, and the processor is coupled to a memory. The processor is configured to store instructions, and when the instructions are executed by the processor, the computing device cluster is caused to execute the method according to any one of claims 1 to 7.

17. A computer-readable storage medium having instructions stored thereon, characterized in that, When the instructions are executed, the computer is caused to execute the method according to any one of claims 1 to 7.

18. A computer program product, comprising instructions therein, characterized in that, When the instructions are executed, the computer is caused to implement the method according to any one of claims 1 to 7.

Images