CN116346814A - Application control method, device, storage medium and chip based on cloud desktop - Google Patents

Abstract

An application control method, device, storage medium and chip based on a cloud desktop, used for synchronizing the state of the application on the cloud desktop based on the state of the application on the first desktop, thereby reducing the user's operation steps and improving the user's convenience. The first device of the present application receives the first information, the first information includes application identification information and information indicating that the application in the first desktop is in the first state, and the first device controls the application of the cloud desktop to be in the first state based on the first information . Since the first device can synchronize the state of the application on the cloud desktop based on the state of the application on the first desktop, the user's operation steps are reduced and the user's convenience is improved.

Description

Application control method, device, storage medium and chip based on cloud desktop

technical field

The present application relates to the field of cloud desktop technology, and in particular to a cloud desktop-based application control method, device, storage medium, and chip.

Background technique

In order to facilitate users' access to and management of desktops, desktop virtualization technology is proposed. Through desktop virtualization technology, users can use clients to access their cloud desktops anytime and anywhere through the network. Currently, users usually use a mouse or a keyboard to operate the desktop. Specifically, when the user operates the desktop on the client side through the mouse or keyboard, the input information of the mouse or keyboard is sent to the server through the set window message hook, and the server responds to the user's operation according to the input information of the mouse or keyboard. The corresponding response is presented on the client side.

In practical applications, the user may perform some operations on the same application on multiple desktops, but the same application on multiple desktops is not related, and the user needs to operate the application on each desktop independently.

For example, the user opens application #1 on desktop #1 (such as a local desktop of an electronic device installed with a cloud desktop client), and performs some transactions through application #1, such as work, chat, leisure and entertainment. Afterwards, after the user logs in to the cloud desktop through the client, if he wants to continue using application #1, he needs to double-click the application #1 installed on the cloud desktop on the cloud desktop again to start and log in to application #1. These operations are relatively complicated and bring great inconvenience to users.

Contents of the invention

The present application provides a cloud desktop-based application control method, device, storage medium, and chip, which are used to synchronize the state of the application on the cloud desktop based on the state of the application on the first desktop, thereby reducing the user's operation steps and improving the user's convenience sex.

In a first aspect, an embodiment of the present application provides a method for controlling an application based on a cloud desktop, and the method may be applicable to a first device. The first device may be, for example, a server or a unit, module or chip (system) inside the server.

In this application, the first device receives the first information. The first information includes identification information of the application and information indicating that the application in the first desktop is in the first state. The first state is a state in the target state. The target state includes one or more of a startup state, a login state, a display state, a logout state, or an application exit state. Based on the first information, the first device controls the application of the cloud desktop to be in the first state.

Since the first device can synchronize the state of the application on the cloud desktop based on the state of the application on the first desktop, the user's operation steps are reduced and the user's convenience is improved.

In a possible implementation manner, the display state includes a front display state, or a non-front display state. In this way, the first device can also control the synchronization of the display state of the application on the first desktop and the cloud desktop, thereby providing greater convenience for the user.

In a possible implementation manner, the first desktop has an association relationship with the cloud desktop. This application can preset the association relationship between the first desktop and the cloud desktop, so that the state of the application of the first desktop and the cloud desktop is synchronized, and for other desktops that are not associated with the cloud desktop, the applications of the other desktops will not be connected with the cloud desktop. Application state synchronization on the Internet, which can improve security.

In a possible implementation manner, when the first state includes startup state, login state or display state, the first device receives the connection request before the application controlling the cloud desktop is in the first state based on the first information message, the connection request message requests the client to establish a connection with the cloud desktop, and the first information is carried in the connection request message. The first device starts the cloud desktop based on the connection request, and the started cloud desktop controls the application to be in the first state based on the first information.

In this way, when the cloud desktop is started, the applications on the cloud desktop are also automatically started, and the state is synchronized with the application on the first desktop, so that the user's operation steps can be reduced, and more convenience can be provided for the user.

In a possible implementation manner, the first device determines that the application on the cloud desktop is switched to the second state in the target state, and the first device sends the second information. The second information includes the identification of the application and indicates that the application is in the second state in the cloud desktop. Information about the second state. In this way, the states of the first desktop and the cloud desktop can be kept in sync, thereby providing more convenience for the user.

In a possible implementation manner, the second information is used by the second device to control the application of the first desktop to switch to the second state, and the second device is a client-side device.

In a possible implementation manner, the first device receives third information, where the third information includes an application identifier and information indicating that the application on the first desktop is in a third state in the target state, and the first device receives the third information based on the third information The application controlling the cloud desktop is switched to the third state. In this way, the states of the first desktop and the cloud desktop can be kept in sync, thereby providing more convenience for the user.

In a possible implementation manner, the first device receives the second authorization information of the application, the second authorization information includes information indicating the state of allowing the application to be synchronized on the first interface and the cloud desktop, and the first device receives the application from the second device. For the first authorization information, the second device is a device on the client side. When the first device determines that the first authorization information matches the second authorization information, based on the first information, the application of the cloud desktop is controlled to be in the first state. This increases security.

In a possible implementation manner, the first authorization information includes an application authorization code, and/or, identification information of the first interface.

In a possible implementation manner, the first desktop satisfies one of the following contents: the interface of the application started on the first desktop integrates the entry of the client; the process of the application started on the first desktop and the process corresponding to the client have Association relationship; the electronic device displaying the first desktop is the same electronic device as the electronic device where the client is located; the electronic device displaying the first desktop is two electronic devices of the same type as the electronic device where the client is located; or, The electronic device displaying the first desktop and the electronic device where the client is located are two different types of electronic devices. In this way, the user can flexibly set desktops requiring application synchronization according to actual conditions, which can improve the flexibility of the solution.

In a second aspect, the embodiment of the present application provides a method for controlling an application based on a cloud desktop, and the method may be applicable to a second device. The second device may be, for example, the client or a unit, module, or chip (system) inside the client.

In this application, the second device acquires first information, and the first information includes application identification information and information indicating that the application on the first desktop is in the first state. The first state is a state in the target state. The target state includes one or more of a startup state, a login state, a display state, a logout state, or an application exit state. The second device sends the first information, the first information is used by the first device to control the application of the cloud desktop to be in the first state based on the first information, and the first device is a device on the server side.

Since the first device can synchronize the state of the application on the cloud desktop based on the state of the application on the first desktop, the user's operation steps are reduced and the user's convenience is improved.

In a possible implementation manner, the display state includes a front display state, or a non-front display state. For related introductions and beneficial effects, refer to the relevant description of the first aspect above, and no more details are given here.

In a possible implementation manner, the first desktop has an association relationship with the cloud desktop. For related introductions and beneficial effects, refer to the relevant description of the first aspect above, and no more details are given here.

In a possible implementation manner, when the first state includes the startup state, the login state, or the first display state, the second device sends a connection request message, the connection request message requests the client to establish a connection with the cloud desktop, and the first information Carried in a connection request message.

In this way, when the cloud desktop is started, the applications on the cloud desktop are also automatically started, and the state is synchronized with the application on the first desktop, so that the user's operation steps can be reduced, and more convenience can be provided for the user.

In a possible implementation manner, the second device receives the second information, the second information includes an application identifier and information indicating that the application in the cloud desktop is in the second state of the target state, and the second device controls the The application on the first desktop is switched to the second state.

In a possible implementation manner, the second information is sent when the first device determines that the application on the cloud desktop is switched to the second state, and the first device is a device on the server side. In this way, when the cloud desktop is started, the applications on the cloud desktop are also automatically started, and the state is synchronized with the application on the first desktop, so that the user's operation steps can be reduced, and more convenience can be provided for the user.

In a possible implementation manner, the second device determines that the application on the first desktop is switched to the third state in the target state, and the second device sends third information, where the third information includes the identification of the application and indicates that the application on the first desktop The application transitions to the information of the third state in the target state.

In a possible implementation manner, the third information is used by the first device to control the cloud desktop application to switch to the third state based on the third information, and the first device is a device on the server side. In this way, when the cloud desktop is started, the applications on the cloud desktop are also automatically started, and the state is synchronized with the application on the first desktop, so that the user's operation steps can be reduced, and more convenience can be provided for the user.

In a possible implementation manner, the second device receives the third authorization information of the application, the third authorization information includes information indicating the state of allowing the synchronization of the application on the first interface and the cloud desktop, and the first authorization information is the third authorization information information in . The second device sends first authorization information. This increases security.

In a possible implementation manner, the first authorization information includes an application authorization code, and/or, identification information of the first interface.

In a possible implementation manner, the first desktop satisfies one of the following contents: the interface of the application started on the first desktop integrates the entry of the client; the process of the application started on the first desktop and the process corresponding to the client have Association relationship; the electronic device displaying the first desktop is the same electronic device as the electronic device where the client is located; the electronic device displaying the first desktop is two electronic devices of the same type as the electronic device where the client is located; or, The electronic device displaying the first desktop and the electronic device where the client is located are two different types of electronic devices. Users can flexibly set the desktops that require application synchronization according to the actual situation, which can improve the flexibility of the solution.

In a third aspect, a communication device is provided, and the communication device may be the aforementioned first device or the second device. The communication device may include a communication unit and a processing unit, so as to implement any one of the above first aspect to the second aspect, or to implement any possible implementation manner of the first aspect to the second aspect. The communication unit is used to perform functions related to transmission and reception. Optionally, the communication unit includes a receiving unit and a sending unit. In one design, the communication device is a communication chip, the processing unit may be one or more processors or processor cores, and the communication unit may be an input/output circuit or port of the communication chip.

In another design, the communication unit may be a transmitter and a receiver, or the communication unit may be a transmitter and a receiver.

Optionally, the communication device further includes various modules that can be used to implement any one of the above first aspect to the second aspect, or to implement any possible implementation manner of the first aspect to the second aspect.

In a fourth aspect, a communication device is provided, and the communication device may be the aforementioned first device or the second device. The communication device may include a processor and a memory, so as to implement any one of the above first aspect to the second aspect, or to implement any possible implementation manner of the first aspect to the second aspect. Optionally, a transceiver is also included, the memory is used to store computer programs or instructions, the processor is used to call and run the computer programs or instructions from the memory, and when the processor executes the computer programs or instructions in the memory, the The communication device implements any one of the above first aspect to the second aspect, or implements any possible implementation manner of the first aspect to the second aspect.

Optionally, there are one or more processors, and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

Optionally, the transceiver may include a transmitter (transmitter) and a receiver (receiver).

In a fifth aspect, a communication device is provided, and the communication device may be the aforementioned first device or the second device. The communications device may include a processor to implement any one of the above first aspect to the second aspect, or to implement any possible implementation manner of the first aspect to the second aspect. The processor is coupled with memory. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

In an implementation manner, when the communication device is the first device or the second device, the communication interface may be a transceiver, or an input/output interface. Optionally, the transceiver may be a transceiver circuit. Optionally, the input/output interface may be an input/output circuit.

In yet another implementation, when the communication device is a chip or a chip system, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system, etc. . A processor may also be embodied as processing circuitry or logic circuitry.

In a sixth aspect, a system is provided, and the system includes the above-mentioned first device.

In a possible implementation manner, the system may further include one or more second devices.

In a seventh aspect, a computer program product is provided, and the computer program product includes: a computer program (also referred to as code, or an instruction), which, when the computer program is executed, causes the computer to execute the above-mentioned first aspect to the second aspect. Any aspect, or any possible implementation manner of implementing the first aspect to the second aspect.

In an eighth aspect, a computer-readable storage medium is provided, and the computer-readable medium stores a computer program (also referred to as code, or an instruction) which, when run on a computer, causes the computer to perform the above-mentioned first to second aspects. Any one of the aspects, or any possible implementation manner of implementing the first aspect to the second aspect.

In a ninth aspect, a chip system is provided, and the chip system may include a processor. The processor is coupled with the memory, and may be used to execute any one of the above first aspect to the second aspect, or to execute any possible implementation manner of the first aspect to the second aspect. Optionally, the chip system further includes a memory. Memory, used to store computer programs (also called code, or instructions). A processor, configured to call and run a computer program from the memory, so that the device installed with the system-on-a-chip executes any one of the above-mentioned first to second aspects, or executes any possible one of the first to second aspects implementation.

In a tenth aspect, a processing device is provided, including: an interface circuit and a processing circuit. Interface circuitry may include input circuitry and output circuitry. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, so that any one of the above-mentioned first aspect to the second aspect, or any possible implementation manner of implementing the first aspect to the second aspect is accomplish.

In a specific implementation process, the above-mentioned processing device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example but not limited to, the receiver, the output signal of the output circuit may be, for example but not limited to, output to the transmitter and transmitted by the transmitter, and the input circuit and the output The circuit may be the same circuit, which is used as an input circuit and an output circuit respectively at different times. The present application does not limit the specific implementation manners of the processor and various circuits.

In an implementation manner, when the communication device is the first device or the second device. The interface circuit may be a radio frequency processing chip in the first device or the second device, and the processing circuit may be a baseband processing chip in the first device or the second device.

In yet another implementation manner, the communication device may be a part of the first device or the second device, such as an integrated circuit product such as a system chip or a communication chip. The interface circuit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system. The processing circuitry may be logic circuitry on the chip.

Description of drawings

FIG. 1 is a schematic diagram of a possible network architecture provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of another possible network architecture provided by the embodiment of the present application;

FIG. 3 is a schematic flow diagram of a cloud desktop-based application control method provided in an embodiment of the present application;

FIG. 4A is a schematic diagram of a client interface provided by an embodiment of the present application;

FIG. 4B is a schematic diagram of another client interface provided by the embodiment of the present application;

FIG. 5A is a schematic structural diagram of a virtual desktop data processing system provided by an embodiment of the present application;

FIG. 5B is a schematic flowchart of a cloud desktop-based application control method provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a device provided in an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a device provided in an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a device provided by an embodiment of the present application.

Detailed ways

Some of the terms involved in the embodiments of the present application are firstly explained below, so as to be easily understood by those skilled in the art.

(1) Virtual desktop is a kind of software or service, which may refer to the operating system desktop obtained by the user during the remote access process. Users' access to virtual desktops is not limited by factors such as devices, regions, and time, providing users with flexibility in accessing virtual desktops.

(2) Virtual machine refers to a complete computer system that is simulated by software and has complete hardware system functions and runs in a completely isolated environment. Everything that can be done on a physical machine can be done on a virtual machine. When creating a virtual machine in a computer, part of the hard disk and memory capacity of the physical machine needs to be used as the hard disk and memory capacity of the virtual machine. Each virtual machine has an independent CMOS, hard disk and operating system, and the virtual machine can be operated like a physical machine. In practical applications, a physical server can virtualize multiple virtual machines through virtualization technology.

Figure 1 is a schematic diagram of a cloud desktop system architecture scenario provided by the embodiment of the present application. The system is only an exemplary description, and only shows the components related to the embodiment of the present invention, but Figure 1 is not applicable to the present invention specific limitations.

As shown in Figure 1, the system includes a cloud desktop client. The clients involved in the embodiments of this application can be replaced by cloud desktop clients, cloud desktop clients, etc. For the convenience of introduction, some of the The location is called a client.

The client can be installed on an electronic device, and the electronic device on which the client is installed can be called a thin client. The network uses the remote desktop protocol to access the cloud desktop (the cloud desktop can also be a virtual machine, a remote desktop or a virtual desktop (Virtual Desktop), etc.).

The system may also include a server (such as the servers 104a...104n shown in FIG. 1), the server is the carrier of the cloud desktop, and the cloud desktop may exist on the server in the form of a virtual machine. A server can provide one or more cloud desktops.

The system may also include a cloud desktop management system. The cloud desktop management system is used to provide functions such as mapping between the user's client and the cloud desktop. The client first connects to the cloud desktop management system, obtains the user's virtual machine address, and then connects to the cloud desktop. The cloud desktop management system can be a server or an ordinary personal computer, which is not specifically limited in the present invention. The user accesses the cloud desktop assigned to the user on the server through the client, and the cloud desktop transmits the content accessed by the user to the user's client for display.

The above-mentioned cloud desktop exists in the form of a virtual machine on the server as an example only, the server can also create a container, and the cloud desktop can also run in the container, which is not limited in this embodiment of the present application.

Based on the system shown in FIG. 1 , FIG. 2 exemplarily shows a schematic diagram of a cloud desktop system architecture scenario provided by an embodiment of the present application.

As shown in FIG. 2 , the system includes an electronic device 10 , a cloud desktop management system 30 , a server 20 and a server 40 for application #1.

Wherein, the cloud desktop management system 30 may be the above-mentioned cloud desktop management system in FIG. 1 , and the cloud desktop management system may be used to provide functions such as mapping between the user's client and the cloud desktop.

The electronic device 10 may be installed with a client 11 and an application #1, and may also include a registry 13 . The electronic device 10 may also be called a local device. The electronic device 10 may be the above-mentioned ordinary computer 101a, a tablet computer 101b, a smart phone 101c, and the like. The server 20 can provide a cloud desktop 21, and the cloud desktop 21 includes a cloud desktop agent 22 and application #1, and can also include a registry 23.

The user can access the cloud desktop 21 through the client 11 of the electronic device 10 . The desktop of the electronic device 10 and the cloud desktop can also install one or more applications respectively. In the embodiment of this application, the application #1 is installed on the local desktop of the electronic device 10, and the application #1 is installed on the cloud desktop 21. . In actual applications, the local desktop and the cloud desktop of the electronic device 10 can also install more applications respectively, which is not limited in this embodiment of the present application. The application #1 installed on the local desktop of the electronic device 10 and the application #1 installed on the cloud desktop 21 can provide the user with one or more functions based on the service server 40 of the application #1. For example, the user can provide the user with one or more functions based on the application #1 (electronic The application #1 installed on the device 10, or the application #1 installed on the cloud desktop 21) performs social chatting video, etc. Another example is that the user uses the application #1 to shop, and another example is the user uses the application #1 to work (such as the welink application) etc.

In the embodiment of the present application, a client entry can be set in the electronic device 10, and the client entry and the entry of application #1 can be independent or related. In FIG. 2 , the client portal is embedded in the application #1 on the local desktop of the electronic device 10 as an example. In actual applications, the application #1 on the local desktop of the electronic device 10 may not be embedded in the client portal. In practical applications, the local desktop of the electronic device 10 may also have multiple entries for the client 11. For example, the interface of the application #1 on the local desktop of the electronic device 10 is provided with an entry for the client 11, and the interface of the electronic device 10 is also provided with The local desktop of 10 is provided with the entrance of client 11.

Based on the embodiments shown in FIG. 1 and FIG. 2 and other contents above, FIG. 3 exemplarily shows a cloud desktop-based application control method provided by an embodiment of the present application. For ease of presentation, the method is written from the perspective of interaction between the first device and the second device.

The first device in the embodiment of the present application may be a server-side device, and the first device may be a server, or a unit, module, or chip (system) in the server. In a possible implementation manner, the first device may be, for example, the cloud desktop proxy 22 in FIG. 2 . The second device in this solution can be a client or a device in the client, for example, the second device can be an electronic device (such as the ordinary computer 101a, tablet computer 101b, smart phone 101c, etc. in the aforementioned Figure 1) with the client installed. The unit, module or chip (system), for another example, the second device may be the aforementioned client 11 in FIG. 2 .

In this embodiment of the present application, an application is used as an example for introduction, and the following application may be the application #1 mentioned in FIG. 2 above. In the embodiment of the present application, the state of the same application on the cloud desktop and the first desktop can be the same, thereby reducing the user's operation steps and providing convenience for the user. A further introduction will be made below in conjunction with FIG. 3 .

As shown in Figure 3, the method includes:

In step 301, the second device acquires first information.

The first information includes identification information of the application and information indicating that the application in the first desktop is in the first state.

The identification information of the application in this embodiment of the present application may include information capable of indicating the application, such as at least one of an application identification or an application name.

In the embodiment of this application, the application can have multiple states. In order to distinguish the various states of the application, they are collectively referred to as the target state, and the target state includes one of the startup state, login state, display state, logout state, or exit application state or more. The first state in the embodiment of the present application, as well as the second state and the third state involved in the follow-up all belong to the state in the target state, wherein any two states in the first state, the second state and the third state are different .

When the application is in the activated state, it means that the application has been activated. When the application is in the login state, it means that the application has been started and the user has successfully logged in.

When the application is in the display state, it means that the application has been started and the user has successfully logged in, and there is a specific display method. The display state in this embodiment of the present application may include multiple types, such as a front display state, a front operation state, a non-front display state, or a non-front operation state.

For example, the display state of the application includes the front display state, which means that the application has been started and is currently displayed at the forefront of the current desktop, or that the application is placed in front of the desktop.

Another example is that the display state of the application includes the pre-operation state, which means that the application has been started and placed on the desktop, and the application is currently in operation (that is, the user is performing some operations on the application).

Another example is that the display state of the application includes a non-front display state, which means that the application has been started but is not displayed at the forefront of the current desktop, or that the application is not placed in front of the desktop.

Another example is that the display state of the application includes a non-pre-operation state, which means that the application has been started and is not placed on the desktop, and the application is not currently in operation (that is, the user is not currently performing an operation on the application).

When the application is in the logout state, it means that the application has logged out of the logged-in user account.

When the application is in the state of exiting the application, it means that the application has been completely exited, or that the application has been closed.

The first desktop in the embodiment of the present application is a desktop different from the cloud desktop, and the application is installed on the first desktop (for example, the application may be application #1 shown in FIG. 2 ).

In a possible implementation manner, the electronic device displaying the first desktop and the electronic device where the client is located (or the electronic device on which the client is installed) may be the same electronic device. The second device may acquire the first state of the application through communication between processes of the same electronic device.

For example, the entrance of the client and the entrance of the application on the first desktop can be two independent entrances. In this case, the client and the application on the first desktop can be two separate processes, and the second device can The state information (information of the first state) of the application on the first desktop is acquired through the communication between the two processes. For example, two processes are under the same operating system, and system functions provided by the operating system can be called to perform local inter-process communication.

For another example, the process of the application started on the first desktop has an association relationship with the process corresponding to the client (client of the cloud desktop). As shown), when the user enters the client through the interface of the application started on the first desktop, an association relationship may be established between the process of the client and the process of the application. In this case, since there is an association between the process of the client and the process of the application, the second device (such as the client) can access the process of the application in order to obtain the state information of the application on the first desktop ( first state information).

The following schematic diagrams of possible local desktops of several electronic devices 10 are exemplarily shown in FIG. 4A and FIG. 4B . In Fig. 4A and Fig. 4B, the electronic device displaying the first desktop and the electronic device where the client is located are the same electronic device, the electronic device is the electronic device 10 in Fig. 2 above, the electronic device 10 is a notebook computer, and application #1 Take WeLink as an example to illustrate. In the embodiment of this application, "WeLink" is introduced as an example of an application. The solution provided in the embodiment of this application is not limited to the application of "WeLink", and may also be applicable to other applications.

As shown in FIG. 4A, the interface currently displayed by the electronic device 10 is the local desktop of the electronic device 10. It can be seen that the local desktop of the electronic device 10 includes icons of multiple applications, such as the icon of this computer, the icon of WeLink, and Cloud desktop icon. Wherein, the WeLink icon can be regarded as the icon of the application #1, and also can be regarded as the entrance of the application #1 on the local desktop of the electronic device 10 . The icon of the cloud desktop can be regarded as the icon of the client 11 , and also can be regarded as the entrance of the client 11 on the local desktop of the electronic device 10 . As shown in FIG. 4A , the entry of the client 11 and the entry of the application #1 included in the local desktop of the electronic device 10 in the embodiment of the present application may be two independent entries. After the application #1 is started, it is a process, and after the client 11 is started, it is another process, and the two processes are independent of each other.

As shown in FIG. 4B , the client portal can be embedded in the application #1 installed on the local desktop of the electronic device 10 . Open the application #1 on the local desktop of the electronic device 10 (for example, by double-clicking the WeLink icon on the local desktop of the electronic device 10 to open "WeLink"), the interface of the application #1 can include a variety of functional options, such as messaging, meeting, communication record, business and knowledge. The icon of the cloud desktop can be set on the interface of the application #1, and the icon of the cloud desktop on the interface of the application #1 can be regarded as the entrance of the embedded client 11 on the application #1. The user can pass a certain operation (such as double-clicking or clicking) the cloud desktop icon on the WeLink interface, and then open the cloud desktop. When the user logs in to the cloud desktop through the client portal embedded in the application #1 of the local desktop of the electronic device 10, WeLink and The processes between the cloud desktops can be two processes with an association relationship (for example, the association relationship between WeLink and the cloud desktop can be established through the authorization of the user), so that the client 11 can more easily determine the local location of the electronic device 10. The state of application #1 on the desktop (such as whether it is in the login state). The form of embedding the client portal in the interface of application #1 in the embodiment of the present application in Fig. Other interfaces or other locations embed client portals.

In yet another possible implementation manner, the electronic device displaying the first desktop and the electronic device where the client is located may be two different electronic devices, and the types of the two electronic devices may be the same or different. Types of electronic devices may include, for example, computers, tablets, or smartphones. For example, the electronic device displaying the first desktop is computer #1, the electronic device installed with the client is computer #2, and computer #1 and computer #2 are of the same type. For another example, the electronic device displaying the first desktop is a tablet computer, the electronic device installed with the client is computer #2, and the tablet computer and computer #2 are of different types. For another example, the electronic device displaying the first desktop is computer #1, the electronic device installed with the client is a mobile phone, and the computer #1 and the mobile phone are of different types.

In the case that the electronic device displaying the first desktop and the electronic device where the client is located are two different electronic devices, the second device may obtain the status information of the application on the first desktop through the connection between the electronic devices (i.e. information in the first state), for example, the electronic device displaying the first desktop is computer #1, the electronic device installed with the client is a smart phone, and computer #1 and the smart phone are connected to the same WLAN at the same time, and computer #1 and A channel is established between the smart phones through bluetooth or wireless local area network, and the second device can obtain the state information (information of the first state) of the application on the first desktop through the channel.

In step 302, the second device sends first information, the first information is used by the first device to control the cloud desktop application to be in the first state based on the first information, and the first device is a device in the server.

Correspondingly, the first device receives the first information.

Step 303, the first device controls the application of the cloud desktop to be in the first state based on the first information.

For example, if the user logs in to the application #1 on the first desktop, the application #1 on the cloud desktop will also be in the login state. Another example is that application #1 on the cloud desktop logs out, and then application #1 on the first desktop also automatically logs out. For another example, application #1 on the first desktop is set to the front display state. When the user switches to the cloud desktop, application #1 on the cloud desktop is also in the front display state. It can be seen that even if the user is on the first desktop and When switching between cloud desktops, application #1 is always displayed at the forefront. It can be seen that, in the embodiment of the present application, the state of the application on the first desktop can be synchronized with the state of the application on the cloud desktop, thereby reducing the user's operation steps and improving the user's convenience.

In a possible implementation manner, if the first state includes a startup state, a login state or a display state. Before step 303, the second device may also send a connection request message to the first device. Correspondingly, the first device receives the connection request message. The connection request message requests the client to establish a connection with the cloud desktop. The second device may carry the first information in a connection request message and send it to the first device, or the second device may separately send the first information to the first device through a channel established with the first device. The first device starts the cloud desktop based on the connection request, and the started cloud desktop controls the application to be in the first state based on the first information.

For example, the first state includes a login state. If the user has logged in the application on the first desktop, when the user starts the cloud desktop through the client, the cloud desktop will automatically log in to the application after the cloud desktop is successfully started (the login account of the application on the first desktop is the same as the account on the cloud desktop. The login account is the same). It can be seen that the user does not need to double-click the application icon on the cloud desktop to open the application again, thereby reducing the user's operation steps and providing greater convenience to the user.

In another possible implementation manner, after step 303, the states of the first desktop and the cloud desktop may also continue to be synchronized.

For example, the first device determines that the application on the cloud desktop is switched to the second state in the target state (the application on the cloud desktop switches from a state different from the second state (such as the first state or other states) to the second state), The first device sends second information. The corresponding second device receives the second information. The second information includes an application identifier and information indicating that the application is in the second state on the cloud desktop. The second device controls the application on the first desktop to switch to the second state based on the second information.

Since the second information is sent when the first device determines that the application on the cloud desktop is switched to the second state, the second information is used by the second device to control the application on the first desktop to switch to the second state. It can be seen that the first The state of the application on the desktop and the cloud desktop can be kept in sync, thereby saving the operation steps of the user and providing convenience to the user.

For another example, the second device determines that the application on the first desktop is switched to the third state in the target state (the application on the first desktop is from a state different from the third state (such as the first state, the second state or other states) switch to the third state), the second device sends third information. The corresponding first device receives the third information. The third information includes an application identifier and information indicating that the application on the first desktop is switched to the third state in the target state. The first device controls the application of the cloud desktop to switch to the third state based on the third information.

Since the third information is sent when the second device determines that the application on the first desktop is switched to the third state, the third information is used by the first device to control the application on the cloud desktop to switch to the third state based on the third information. It can be seen that the states of the applications on the first desktop and the cloud desktop can be kept synchronized, thereby saving the user's operation steps and providing convenience to the user.

In yet another possible implementation, the first desktop may have an association relationship with the cloud desktop. For example, the user may set the association relationship between the first desktop and the cloud desktop through authorization in advance, so that the state of the application on the first desktop can be Allows synchronization with the state of the application on the cloud desktop.

In a possible implementation manner, before step 302, the first device and the second device may respectively receive authorization information, and the authorization information received by the first device may be different from the authorization information received by the second device, or may be the same. The authorization information includes, for example, the authorization code of the application, and/or, the identification information of the first interface. The identification information of the first interface in the embodiment of the present application may refer to information capable of identifying the first interface, such as the device identifier of the electronic device to which the first interface belongs, the device type information of the electronic device to which the first interface belongs, and the like.

For example, the first device receives the second authorization information of the application, and the second authorization information includes information indicating the state of allowing the application to be synchronized on the first interface and the cloud desktop. The second device receives third authorization information of the application, where the third authorization information includes information indicating a state of allowing the application to be synchronized on the first interface and the cloud desktop. The second authorization information and the third authorization information may be the same or different.

Before the above step 302, the second device may send first authorization information to the first device, where the first authorization information is part or all of the third authorization information. In the above step 303, the first device controls the cloud desktop application to be in the first state based on the first information when it is determined that the first authorization information matches the second authorization information. In yet another possible implementation manner, when the first device determines that the first authorization information does not match the second authorization information, it does not perform the above step 303, that is, it does not automatically set the status of the application to the first status .

For example, if the second device sends an authorization code #1 to the first device, the first device compares the authorization code #1 from the second device with the authorization code received in advance, and if the two authorization codes are the same, then It means that the first authorization information matches the second authorization information, and the first device then controls the application of the cloud desktop to be in the first state based on the first information. In this way, security can be improved. If the two authorization codes are different, it means that the first authorization information does not match the second authorization information, and the first device no longer controls the application state of the cloud desktop based on the first information.

Based on the embodiments shown in Fig. 1, Fig. 2, Fig. 3, Fig. 4A and Fig. 4B and the above-mentioned other contents, Fig. 5A exemplarily shows a schematic diagram of another communication system architecture provided by the embodiment of the present application, and Fig. 5B exemplarily shows A cloud desktop-based application control method provided in an embodiment of the present application is provided. The scheme shown in Fig. 5B is schematically based on Fig. 5A. The solution shown in FIG. 5B is based on the system architecture shown in FIG. 2. In FIG. 5B, in order to further introduce the solution of the embodiment of the present application, the cloud desktop management system 30 is divided into multiple modules, such as Access service, authentication center, desktop control service and desktop management service, etc. The server 40 of application #1 may include a business service of application #1 and a management service of application #1. The system architecture applicable to the embodiment of the present application may also include other devices, such as a third party and an authentication center, etc., which are not shown in the figure.

As shown in Figure 5A and Figure 5B, the method includes:

Step 501, the management service of application #1 registers application #1 with the desktop management service and authorizes it.

In step 501, the management service of application #1 may register with the desktop management service, and authorize the state synchronization between the cloud desktop and application #1 on the first desktop. For example, the management service of application #1 may send some authorization information to the desktop management service, such as an authorization code and/or identification information of the first desktop that allows the application to synchronize.

The desktop management service can be used to manage users who log in to cloud desktops or cloud applications, and the matching relationship between users and cloud desktops.

In step 502, the desktop management service delivers an application registration service to the desktop control service.

The application registration service is used to register application #1. In step 502, the desktop management service also delivers the registration information of the application #1 and the authorization information of the application #1 to the desktop control service.

Step 503 , the desktop control service delivers the registration information of the application #1 and the authorization information of the application #1 to the client 11 and the cloud desktop agent 22 respectively.

The desktop control service is connected to the client 11 and the cloud desktop agent 22 respectively. The authorization information of application #1 issued by the desktop control service to the client 11 (equivalent to the third authorization information of the foregoing content) and the authorization information of application #1 issued by the cloud desktop proxy 22 (equivalent to the second authorization information of the foregoing content). authorization information) may be different or the same, for example, may include an authorization code. These authorization information may indicate that the application #1 on the cloud desktop is allowed to synchronize with the state on other desktops (such as the first desktop or other desktops).

In yet another possible implementation manner, the authorization information may also include the identification information of the first desktop, so that the authorization information may indicate a specified desktop (such as the first desktop) that is allowed to synchronize with the state of application #1 on the cloud desktop. In this embodiment, the application #1 on the desktop other than the designated desktop cannot be synchronized with the state of the application #1 on the cloud desktop. This solution can provide users with more personalized settings, thereby improving the flexibility of user settings.

The desktop control service can be used to send control instructions to the client 11 (or the process of the client) or the cloud desktop proxy 22 (or the proxy process of the cloud desktop), and the desktop control service can be used between the electronic device 10 and the cloud desktop Pre-connection verification is performed when building a data connection channel, and connection status control can also be performed.

Step 504 , the client 11 writes the authorization information of the application #1 into the registry 13 , and the cloud desktop agent 22 writes the authorization information of the application #1 into the registry 23 .

In the embodiment of this application, the client 11 and the cloud desktop agent 22 will store the received authorization information of application #1, and the storage location can be flexibly set. In FIG. 5A, the authorization information is stored in the registry as an example. In practice, In the application, it can also be stored in other locations.

In addition to the authorization information (such as authorization code, or associated authorization code), the client 11 writes the application #1 information in the registry 13, and may also include some application #1 information, such as the information required by the cloud desktop to start the application. Some, such as the identification and name of the application #1, the startup path on the first desktop, the startup path on the cloud desktop, or one or more of whether the application #1 is associated with the remote cloud desktop or not. The authorization code may be assigned by the system after the user agrees to authorize the application #1 of the cloud desktop to establish an association relationship with the application #1 of the first desktop.

In addition to the authorization information (such as the authorization code), the information of the application #1 written by the cloud desktop agent 22 in the registry 23 may also include some information of the application #1, such as some required by the cloud desktop to start the application, such as application# One or more of the identification, name of 1, the startup path on the first desktop, the startup path on the cloud desktop, or whether application #1 is associated with the remote cloud desktop.

The application #1 information written by the client 11 in the registry 13 and the application #1 information written by the cloud desktop agent 22 in the registry 23 may be the same or different.

In addition, if the applications are different, for example, application #1 is replaced by application #2, the above-mentioned information about application #1 written by the client 11 in the registry 13 will also be replaced by the application written by the client 11 in the registry 13 The information of #2, with different applications, the two information will also be different. The information of application #1 written in the registry 23 by the cloud desktop agent 22 will also be replaced by the information of application #2 written by the cloud desktop agent 22 in the registry 23, and the two information will be different depending on the application .

Step 505 , the user logs into the application #1 on the electronic device 10 .

In Figure 5B, the user has already started and logged into application #1 before starting the cloud desktop as an example. In actual applications, the user may only start application #1 but not log in before starting the cloud desktop, or may also log in to application #1 And set the display mode of always displaying at the forefront of the desktop.

Step 506, the user clicks to set the client entry set on the interface of application #1.

Through the solution provided in step 506, the user can pull up the client through the client portal integrated in application #1 (this portal can also be called the lightweight cloud desktop client portal). During the pull-up process, application #1 can Send the information of the application #1 to the client 11, such as the identification information of the application #1, the information of the current status of the application #1, and the like.

Step 507, the user inputs the user information of the cloud desktop on the opened interface of the client 11.

Step 508, the client 11 sends the user information of the cloud desktop to the authentication center through the access service.

Through step 508, the authentication center can check whether the user information matches the preset user information. If they match, the authentication succeeds; if they do not match, the authentication fails.

In step 509, the client 11 requests the access service for a pre-connection, and the desktop control service requests the authentication center to authenticate the pre-connection.

For example, when a user logs in to application #1 on the first desktop through the cloud desktop client, the backend cloud desktop server may be turned on, off, or in the process of starting.

The process of the client 11 requesting the pre-connection may also be referred to as the process of the cloud desktop client requesting the pre-start. The pre-connection process may include cloud server status judgment and/or server login authentication judgment and other processing (server login may be connected to the enterprise's active directory (active directory, AD), or may be connected to the enterprise's third-party authentication center, etc.). Wherein, judging the status of the cloud service may include: judging whether the server in the cloud has been turned on (or said to be in the turned-on state). If the cloud server is closed or is in the process of starting (begins to start but has not started successfully), you can enable the cloud server to start or wait for the cloud server to start. The authentication judgment of server login can be to judge whether the user has the right to log in to the cloud desktop, for example, it can be judged whether the user information of the user is associated with the cloud desktop, if it is determined that the user has the right to log in to the cloud desktop (such as determining the The user's user information is associated with the cloud desktop), that is, the authentication is successful, if the user does not have the right to log in to the cloud desktop (for example, it is determined that the user's user information does not have an associated relationship with the cloud desktop), then the authentication fails. If the cloud server is turned on, and the server login authentication determines that the user has the right to log in to the cloud desktop (that is, the authentication is successful), it can be said that the pre-connection is successful, and then the client and the cloud can establish a communication channel.

Wherein, the access service can be used for the client 11 to log in to the cloud desktop, and the cloud desktop service access gateway.

The authentication center can also authenticate other content, for example, the authentication center authenticates cloud desktop login. For example, after the authentication center receives a message for requesting a pre-connection (or also called a pre-connection request), the cloud desktop can control the server to check the status of the cloud service, and notify the started cloud server (operating system, OS) for authentication .

In order to further improve security, other authentication centers (such as a third-party authentication center) may further perform authentication, for example, authentication may be performed on cloud desktop system login. For authentication content, refer to the foregoing description, and details are not repeated here.

Step 510 , the client 11 reads the authorization information of the application #1 stored in the registry 13 .

Step 511 , the client 11 sends a connection request message to the cloud desktop agent 22 .

The connection establishment request message is used to establish a channel between the client 11 and the cloud desktop proxy 22 . In a possible implementation manner, the connection request message may carry the authorization information of the application #1 and the status information of the application #1 on the electronic device 10 .

In step 512, the cloud desktop agent 22 reads the authorization information of the application #1 and the startup information (such as the startup path) of the application #1 from the registry 23 .

In step 512, the cloud desktop agent 22 compares the authorization information of the application #1 read from the registry 23 with the authorization information received from the client 11, and if the content is consistent, it is considered that the two match, and then the step 513. On the contrary, if the two do not match, only the cloud desktop is started, but step 513 is not executed.

Step 513 , the cloud desktop agent 22 starts and logs in the application #1 on the cloud desktop 21 according to the startup information of the application #1 (such as the startup path).

In step 513, the cloud desktop agent 22 controls the application #1 on the cloud desktop to keep the same state as the application #1 on the electronic device 10. In the embodiment of the present application, the application #1 is in the login state as an example for illustration.

After the user logs in to the cloud desktop through the client 11, the cloud desktop agent 22 establishes a channel with the client 11 for data transmission, and the cloud desktop can deliver the remote operation data to the user's local terminal (such as the electronic device 10) for rendering. The cloud desktop can also receive keyboard and mouse events (such as operation events input through the keyboard and mouse) and control signaling from the local terminal (such as the electronic device 10).

It can be seen from the above content that the user has logged in the application #1 on the local desktop of the electronic device 10, then when the user starts the cloud desktop 21 through the client 11, the cloud desktop 21 will automatically log in to the application #1 after the startup is successful. There is no need to double-click the icon of the application #1 on the cloud desktop to open the application #1 again, thereby reducing the user's operation steps and providing greater convenience to the user. And when the user is working on the cloud desktop shared by multiple people, for the application #1 on the remote cloud desktop, the user can exit the application on the cloud desktop by exiting the application #1 on the local terminal (such as the first desktop) #1, thereby reducing the risk of personal data leakage.

In the embodiment of this application, after the first desktop and cloud desktop log in to application #1 at the same time, the message content of application #1 logged in on the first desktop and cloud desktop can also be synchronized, and the data of application #1 on the first desktop and cloud desktop (such as message content) can be synchronized by the business service of application #1, without the need to synchronize through the channel between the client 11 and the cloud desktop agent 22, the channel between the client 11 and the cloud desktop agent 22 can be used for synchronization The status of application #1 on the first desktop and cloud desktop, such as startup, login, display status, logout or application exit, etc. For example, after the first desktop and the cloud desktop log in to application #1 at the same time, the user sends a message #1 in the application #1 of the cloud desktop, and the business service of the application #1 will synchronize the content to the application on the first desktop #1, that is, the application #1 that the user sees on the first desktop will also display that the message #1 has been sent.

The names of the above-mentioned messages are only examples. With the evolution of communication technology, any of the above-mentioned messages may change their names, but no matter how their names change, as long as their meanings are the same as those of the above-mentioned messages in this application, they all fall into the Within the protection scope of this application.

In the embodiment of the present application, sending information to a terminal device may be understood as that the destination of the information is the terminal device. For example, sending information from module A to the terminal includes: module A sends the information to the terminal through the air interface, optionally, module A can perform baseband and/or mid-radio frequency operations on the information; or, module A submits the information to module B , and module B sends this information to the terminal. Wherein, when the module B sends the information to the terminal, it may transmit the information transparently, segment the information and send the information, or multiplex the information with other information and send the information. Optionally, module B may perform baseband and/or mid-radio frequency operations on the information and send the information, etc. Optionally, module B may encapsulate the information in a data packet. Optionally, module B may also add a header and/or padding bits to the data packet.

In this embodiment of the present application, receiving information from a terminal device may be understood as that the source of the information is the terminal device. For example, module A receiving information from the terminal device includes: module A receiving the information from the terminal through the air interface, optionally, module A can perform baseband and/or mid-radio frequency operations on the information; or, module B receiving the information from the terminal through the air interface information, and submit this information to module A. Wherein, module B submits the information to module A, including: transparently submitting the received information to module A, combining multiple received segments into the information and submitting it to module A, or multiplexing information After extracting the information, submit it to module A. Optionally, the module B may perform baseband and/or intermediate radio frequency operations on the received information and then send the information and the like. Optionally, the information received by module B is encapsulated in a data packet. Optionally, the data packet may include a packet header and/or padding bits and the like.

The above-mentioned module B may be one module, or a plurality of modules coupled in sequence, without limitation. For example, module A is a DU module, and module B is an RU module; for another example, module A is a CU-CP module, and module B is a DU module and an RU module.

The foregoing mainly introduces the solution provided by the present application from the perspective of interaction between various network elements. It can be understood that, in order to implement the above functions, each network element includes a corresponding hardware structure and/or software module for performing each function. Those skilled in the art should easily realize that the present invention can be realized in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

According to the foregoing method, FIG. 6 is a schematic structural diagram of a device provided in an embodiment of the present application.

Referring to Figure 6, a simplified schematic diagram of an apparatus 1301 is provided. The apparatus 1301 is used to realize the functions of the network element in the embodiment of the present application, for example, the network element may be a base station, a terminal, a DU, a CU, a CU-CP, a CU-UP or a RU. The device 1301 may be the network element, or a device that can be installed in the network element, or a device that can be matched and used with the network element, without limitation, for example, the device may be a chip or a chip system. The device 1301 includes an interface 1303 and a processor 1302 . Optionally, the processor 1302 is configured to execute a program 1305 . The processor 1302 may store the program 1305, or obtain the program 1305 from other devices or other devices (for example, from the memory 1304 or downloaded from a third-party website, etc.). Optionally, the device 1301 includes a memory 1304 . The memory 1304 is used to store programs 1306 . The program 1306 can be stored in advance or loaded later. Optionally, the memory 1304 can also be used to store necessary data. These components work together to provide various functions described in the embodiments of this application.

Processor 1302 may include one or more processors as a combination of computing devices. The processor 1302 may respectively include one or more of the following: a microprocessor, a microcontroller, a digital signal processor (Digital Signal Processor, DSP), a digital signal processing device (Digital Signal Processor device, DSPD), an application specific integrated circuit ( Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA), programmable logic device (programmable logic device. PLD), gating logic, transistor logic, discrete hardware circuit, processing circuit or other suitable Hardware, firmware, and/or a combination of hardware and software configured to execute various functions described in the embodiments of the present application. Processor 1302 may be a general purpose processor or a special purpose processor. For example, processor 1302 may be a baseband processor or a central processing unit. A baseband processor can be used to process communication protocols and communication data. The central processing unit can be used to execute software programs and process data in the software programs.

The interface 1303 may include any suitable hardware or software for enabling communication with one or more computer devices (such as the network element of the embodiment of the present application). For example, in some embodiments, interface 1303 may include terminals and/or pins for coupling wires for wired connections or wireless interfaces for wireless connections. In some embodiments, interface 1303 may include a transmitter, a receiver, an interface and/or an antenna. The interface may be configured to use any available protocol (eg, 3GPP standard protocol) to enable communication between computer devices (eg, the network element in the embodiment of the present application).

The programs in the embodiments of this application refer to software in a broad sense. Software may be a program code, program, subroutine, instruction set, code, code segment, software module, application, software application, or the like. The program can run on a processor and/or a computer to execute various functions and/or processes described in the embodiments of the present application.

The memory 1304 may store necessary data required when the processor 1302 executes software. Memory 1304 may be implemented using any suitable storage technology. For example, memory 1304 can be any available storage medium that can be accessed by a processor and/or computer. Non-limiting examples of storage media are: random access memory (random access memory, RAM), read-only memory (read-only memory, ROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM ), compact disc read-only memory (CD-ROM), removable media, optical disc storage, magnetic disk storage media, magnetic storage devices, flash memory, registers, state memory, remotely mounted memory, local or remote memory components, or Any other medium that can carry or store software, data or information and be accessed by a processor/computer.

The memory 1304 and the processor 1302 can be set separately or integrated together. Processor 1302 may read information from memory 1304 and store and/or write information in memory. The memory 1304 may be integrated in the processor 1302 . The processor 1302 and the memory 1304 may be arranged in an integrated circuit (such as an application-specific integrated circuit (ASIC)). The integrated circuit may be set in the network element or other network nodes in the embodiment of the present application. The dotted line in the memory 1304 in the figure further indicates that the memory is optional.

Furthermore, the communication device 1301 may further include a bus system, wherein the processor 1302, the memory 1304, and the interface 1303 may be connected through the bus system.

As shown in Figure 6, the device 1301 can be a first device or a second device, and can also be a chip or a circuit, such as a chip or a circuit that can be set in the first device, or a chip that can be set in the second device or circuit.

In the case where the device 1301 is used to realize the function of the first device: the processor 1302 is used to: receive first information through the interface 1303, and based on the first information, an application controlling the cloud desktop is in a first state.

In the case where the device 1301 is used to implement the functions of the first device, in a possible implementation manner, when the first state includes a startup state, a login state, or a display state, the processor 1302 is further configured to: receive through the interface 1303 The connection request message starts the cloud desktop based on the connection request, and the started cloud desktop controls the application to be in the first state based on the first information.

In the case where the device 1301 is used to implement the functions of the first device, in a possible implementation manner, the processor 1302 is also used to: determine that the application on the cloud desktop is switched to the second state in the target state, and send the message through the interface 1303 The second information includes an application identifier and information indicating that the application is in a second state on the cloud desktop.

In the case where the device 1301 is used to implement the functions of the first device, in a possible implementation manner, the processor 1302 is further configured to: receive third information through the interface 1303, where the third information includes the identification of the application and indicates the first desktop The application in the target state is in the third state information, and the application of the cloud desktop is controlled to switch to the third state based on the third information.

In the case where the device 1301 is used to implement the functions of the first device, in a possible implementation manner, the processor 1302 is further configured to: receive the second authorization information of the application through the interface 1303, the second authorization information includes the An interface and cloud desktop synchronization application state information, through the interface 1303 to receive the first authorization information from the second device, the second device is a device on the client side, when it is determined that the first authorization information matches the second authorization information Next, the application that controls the cloud desktop based on the first information is in the first state.

In the case where the device 1301 is used to realize the function of the second device: the processor 1302 is used to obtain the first information, and send the first information through the interface 1303 .

In the case where the device 1301 is used to implement the functions of the second device, in a possible implementation manner, when the first state includes a startup state, a login state, or a first display state, the processor 1302 is further configured to: 1303 Send a connection request message, the connection request message requests the client to establish a connection with the cloud desktop, and the first information is carried in the connection request message.

In the case where the device 1301 is used to implement the functions of the first device, in a possible implementation manner, the processor 1302 is further configured to: receive second information through the interface 1303, the second information includes the application identification and indicates that the cloud desktop The application is in the second state information in the target state, and the application on the first desktop is controlled to switch to the second state based on the second information.

In the case where the device 1301 is used to implement the functions of the first device, in a possible implementation manner, the processor 1302 is further configured to: determine that the application on the first desktop is switched to the third state in the target state, and through the interface 1303 Send third information, where the third information includes an application identifier and information indicating that the application on the first desktop is switched to a third state in the target state.

In the case where the device 1301 is used to implement the functions of the first device, in a possible implementation manner, the processor 1302 is further configured to: receive third authorization information of the application through the interface 1303, where the third authorization information includes the The first authorization information is the information in the third authorization information. Send the first authorization information through the interface 1303 .

For the concepts, explanations, detailed descriptions and other steps involved in the communication device related to the technical solutions provided by the embodiments of the present application, please refer to the foregoing methods or descriptions of these contents in other embodiments, and details are not repeated here.

According to the foregoing method, FIG. 7 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG. 7 , a device 1401 may include a transceiver 1403 and a processor 1402 . Further, the device 1401 may include a memory 1404 . The dotted line in the memory 1404 in the figure further indicates that the memory is optional. The transceiver 1403 is used to input and/or output information; the processor 1402 is used to execute computer programs or instructions, so that the device 1401 implements the method of the first device or the second device in the above-mentioned related solutions of FIG. 3 or FIG. 5B . In the embodiment of the present application, the transceiver 1403 can implement the solution implemented by the interface 1303 in FIG. 6 above, the processor 1402 can implement the solution implemented by the processor 1302 in FIG. The realized scheme will not be repeated here.

Based on the above embodiments and the same idea, FIG. 8 is a schematic diagram of a communication device provided by an embodiment of the present application. As shown in FIG. 8, the device 1501 can be a first device or a second device, or a chip or a circuit, such as A chip or circuit disposed on the first device or the second device.

The apparatus 1501 includes a processing unit 1502 and a communication unit 1503 . Further, the device 1501 may include the storage unit 1504 or may not include the storage unit 1504 . The dotted line in the storage unit 1504 in the figure further indicates that the storage is optional.

In the case where the device 1501 is used to realize the function of the first device: the processing unit 1502 is used to receive the first information through the communication unit 1503, and the processing unit 1502 is used to control the application of the cloud desktop to be in the first state based on the first information.

In a case where the device 1501 is used to realize the function of the second device: the processing unit 1502 is used to acquire the first information. The processing unit 1502 is configured to send the first information through the communication unit 1503 .

For the concepts, explanations, detailed descriptions and other steps involved in the communication device related to the technical solutions provided by the embodiments of the present application, please refer to the foregoing methods or descriptions of these contents in other embodiments, and details are not repeated here.

It can be understood that, the function of each unit in the above apparatus 1501 can refer to the implementation of the corresponding method embodiment, and details are not repeated here.

It should be understood that the above division of units of the communication device is only a division of logical functions, which may be fully or partially integrated into one physical entity or physically separated during actual implementation. In the embodiment of the present application, the communication unit 1503 may be realized by the interface 1303 in FIG. 6 above, and the processing unit 1502 may be realized by the processor 1302 in FIG. 6 above.

According to the method provided in the embodiment of the present application, the present application also provides a computer program product, the computer program product including: computer program code or instruction, when the computer program code or instruction is run on the computer, the computer is made to execute the Or the method of any one of the embodiments shown in FIG. 5B.

According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, the computer-readable medium stores program code, and when the program code is run on the computer, the computer is made to execute the method shown in Figure 3 or Figure 5B. The method of any of the illustrated embodiments.

According to the method provided in the embodiment of the present application, the present application further provides a chip system, where the chip system may include a processor. The processor is coupled with the memory, and may be used to execute the method in any one of the embodiments shown in FIG. 3 or FIG. 5B . Optionally, the chip system further includes a memory. Memory, used to store computer programs (also called code, or instructions). The processor is configured to call and run a computer program from the memory, so that the device installed with the system-on-a-chip executes the method in any one of the embodiments shown in FIG. 3 or FIG. 5B .

According to the method provided in the embodiments of the present application, the present application further provides a system, which includes the foregoing one or more first devices.

In yet another possible implementation manner, the system may further include one or more second devices.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. A computer can be a general purpose computer, special purpose computer, computer network, or other programmable device. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g. Coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server, a data center, etc. integrated with one or more available media. Available media may be magnetic media (e.g., floppy disk, hard disk, magnetic tape), optical media (e.g., high-density digital video disc (digital video disc, DVD)), or semiconductor media (e.g., solid state disk (solid state disc, SSD) )wait.

It should be pointed out that a part of the patent application documents contains content protected by copyright. Copyright is reserved by the copyright owner other than to make copies of the contents of the patent file or records of the Patent Office.

The network equipment in each of the above device embodiments corresponds to the terminal equipment and the network equipment or terminal equipment in the method embodiments, and the corresponding modules or units perform corresponding steps, for example, the communication unit (transceiver) executes receiving or sending in the method embodiments Steps, other steps except sending and receiving can be executed by a processing unit (processor). For the functions of the specific units, reference may be made to the corresponding method embodiments. Wherein, there may be one or more processors.

The terms "component", "module", "system" and the like are used in this specification to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be components. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more packets of data (e.g., data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet via a signal interacting with other systems). Communicate through local and/or remote processes.

Those of ordinary skill in the art can realize that various illustrative logical blocks (illustrative logical blocks) and steps (steps) described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. accomplish. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

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

A unit described as a separate component may or may not be physically separated, and a component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. If the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.

The above is only the specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the application, and should cover Within the protection scope of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

In this application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. In the text description of this application, the character "/" generally indicates that the contextual objects are an "or" relationship; in the formulas of this application, the character "/" indicates that the contextual objects are a "division" Relationship. "Including at least one of A, B and C" may mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

It can be understood that the various numbers involved in the embodiments of the present application are only for convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial numbers of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic.

Claims (29)

1. The application control method based on the cloud desktop is characterized by being applied to a first device, wherein the first device is a server-side device, and the method comprises the following steps:

Receiving first information, wherein the first information comprises identification information of an application and information indicating that the application in a first desktop is in a first state, the first state is a state in a target state, and the target state comprises one or more of a starting state, a login state, a display state, a login exit state or an application exit state;

and controlling the application of the cloud desktop to be in the first state based on the first information.

2. The method of claim 1, wherein the first state comprises a start state, a login state, or a display state:

the receiving the first information includes:

receiving a connection request message, wherein the connection request message requests a client to establish connection with a cloud desktop, and the first information is carried in the connection request message;

the controlling, based on the first information, the application of the cloud desktop to be in the first state includes:

and starting the cloud desktop based on the connection request, and controlling the application on the cloud desktop after starting to be in the first state based on the first information.

3. The method of claim 1 or 2, wherein the controlling the application of the cloud desktop in the first state based on the first information further comprises:

Determining that the application on the cloud desktop is switched to a second state in the target states;

and sending second information, wherein the second information comprises an identification of the application and information indicating that the application is in the second state on the cloud desktop.

4. The method of any of claims 1-3, wherein the controlling the application of the cloud desktop to be in the first state based on the first information further comprises:

receiving third information, wherein the third information comprises an identification of the application and information indicating a third state of the application in the first desktop in the target state;

and controlling the application of the cloud desktop to be switched to the third state based on the third information.

5. The method of any of claims 1-4, wherein the controlling the application of a cloud desktop to be in the first state based on the first information further comprises:

receiving second authorization information of the application, wherein the second authorization information comprises information indicating that the state of the application is allowed to be synchronized between the first desktop and the cloud desktop;

receiving first authorization information from a second device, wherein the second device is a device at a client side;

The controlling, based on the first information, the application of the cloud desktop to be in the first state includes:

and controlling the application of the cloud desktop to be in the first state based on the first information under the condition that the first authorization information is matched with the second authorization information.

6. The method of any of claims 1-5, wherein the first desktop meets one of:

integrating an inlet of the client by an interface of the application started on the first desktop;

the process of the application started on the first desktop has an association relationship with the process corresponding to the client;

displaying the electronic equipment of the first desktop and the electronic equipment where the client is located as the same electronic equipment;

displaying the electronic equipment of the first desktop and the electronic equipment of the client as two electronic equipment of the same type; or alternatively, the first and second heat exchangers may be,

and displaying the electronic equipment of the first desktop and the electronic equipment of the client as two different types of electronic equipment.

7. An application control method based on a cloud desktop is characterized in that the method is applied to a second device, and the second device is a device at a client side, and the method comprises the following steps:

Acquiring first information, wherein the first information comprises identification information of an application and information indicating that the application in a first desktop is in a first state, the first state is a state in a target state, and the target state comprises one or more of a starting state, a login state, a display state, a login exit state and an application exit state;

and sending the first information, wherein the first information is used for a first device to control the application of the cloud desktop to be in the first state based on the first information, and the first device is a device at a server side.

8. The method of claim 7, wherein the first state comprises a start state, a login state, or a first display state:

the sending the first information includes:

and sending a connection request message, wherein the connection request message requests the client to establish connection with a cloud desktop, and the first information is carried in the connection request message.

9. The method of claim 7 or 8, wherein after the transmitting the first information, further comprising:

receiving second information, wherein the second information comprises an identification of the application and information indicating a second state of the application in the cloud desktop in the target state;

And controlling the application of the first desktop to be switched to the second state based on the second information.

10. The method of any of claims 7-9, wherein after the sending the first information, further comprising:

determining that the application on the first desktop switches to a third state of the target states;

and sending third information, wherein the third information comprises an identification of the application and information indicating that the application on the first desktop is switched to a third state in the target states.

11. The method of any of claims 7-10, wherein prior to the sending the first information, further comprising:

receiving third authorization information of the application, wherein the third authorization information comprises information indicating that the state of the application is allowed to be synchronized between the first desktop and the cloud desktop;

and sending first authorization information, wherein the first authorization information is information in the third authorization information.

12. The method of any of claims 7-11, wherein the first desktop meets one of:

integrating an inlet of the client by an interface of the application started on the first desktop;

The process of the application started on the first desktop has an association relationship with the process corresponding to the client;

displaying the electronic equipment of the first desktop and the electronic equipment where the client is located as the same electronic equipment;

displaying the electronic equipment of the first desktop and the electronic equipment of the client as two electronic equipment of the same type; or alternatively, the first and second heat exchangers may be,

and displaying the electronic equipment of the first desktop and the electronic equipment of the client as two different types of electronic equipment.

13. The utility model provides an application control device based on cloud desktop, its characterized in that, the device is first device, first device is the device of server side, the device includes processor and interface:

the processor is configured to:

receiving first information through the interface, wherein the first information comprises identification information of an application and information indicating that the application in a first desktop is in a first state, the first state is a state in a target state, and the target state comprises one or more of a start state, a login state, a display state, an exit login state and an exit application state;

and controlling the application of the cloud desktop to be in the first state based on the first information.

14. The apparatus of claim 13, wherein the first state comprises a start state, a login state, or a display state:

the processor is configured to:

receiving a connection request message through the interface, wherein the connection request message requests the client to establish connection with the cloud desktop, and the first information is carried in the connection request message;

and starting the cloud desktop based on the connection request, and controlling the application to be in the first state based on the first information by the cloud desktop after starting.

15. The apparatus of claim 13 or 14, wherein the processor is further configured to:

determining that the application on the cloud desktop is switched to a second state in the target states;

and sending second information through the interface, wherein the second information comprises an identification of the application and information indicating that the application is in the second state on the cloud desktop.

16. The apparatus of any of claims 13-15, wherein the processor is further configured to:

receiving third information through the interface, wherein the third information comprises an identification of the application and information indicating a third state of the application in the first desktop in the target state;

And controlling the application of the cloud desktop to be switched to the third state based on the third information.

17. The apparatus of any of claims 13-16, wherein the processor is further configured to:

receiving, by the interface, second authorization information for the application, the second authorization information including information indicating a state that allows synchronization of the application at the first desktop and the cloud desktop;

receiving first authorization information from a second device through the interface, wherein the second device is a device at a client side;

and controlling the application of the cloud desktop to be in the first state based on the first information under the condition that the first authorization information is matched with the second authorization information.

18. The apparatus of any of claims 13-17, wherein the first desktop satisfies one of:

integrating an inlet of the client by an interface of the application started on the first desktop;

the process of the application started on the first desktop has an association relationship with the process corresponding to the client;

displaying the electronic equipment of the first desktop and the electronic equipment where the client is located as the same electronic equipment;

Displaying the electronic equipment of the first desktop and the electronic equipment of the client as two electronic equipment of the same type; or alternatively, the first and second heat exchangers may be,

and displaying the electronic equipment of the first desktop and the electronic equipment of the client as two different types of electronic equipment.

19. An application control device based on a cloud desktop is characterized in that the device is a second device, the second device is a device at a client side, and the device comprises a processor and an interface:

the processor is configured to:

acquiring first information, wherein the first information comprises identification information of an application and information indicating that the application in a first desktop is in a first state, the first state is a state in a target state, and the target state comprises one or more of a starting state, a login state, a display state, a login exit state and an application exit state;

and sending the first information through the interface, wherein the first information is used for controlling the application of the cloud desktop to be in the first state by a first device based on the first information, and the first device is a device at a server side.

20. The apparatus of claim 19, wherein the first state comprises an activated state, a logged in state, or a first display state:

The processor is configured to:

and sending a connection request message through the interface, wherein the connection request message requests the client to establish connection with a cloud desktop, and the first information is carried in the connection request message.

21. The apparatus of claim 19 or 20, wherein the processor is further configured to:

receiving second information through the interface, wherein the second information comprises an identification of the application and information indicating a second state of the application in the cloud desktop in the target state;

and controlling the application of the first desktop to be switched to the second state based on the second information.

22. The apparatus of any of claims 19-21, wherein the processor is further configured to:

determining that the application on the first desktop switches to a third state of the target states;

and sending third information through the interface, wherein the third information comprises an identification of the application and information indicating that the application on the first desktop is switched to a third state in the target states.

23. The apparatus of any of claims 19-22, wherein the processor is further configured to:

Receiving third authorization information of the application through the interface, wherein the third authorization information comprises information indicating that the state of the application is allowed to be synchronized at the first desktop and the cloud desktop;

and sending first authorization information through the interface, wherein the first authorization information is information in the third authorization information.

24. The apparatus of any of claims 19-23, wherein the first desktop satisfies one of:

integrating an inlet of the client by an interface of the application started on the first desktop;

the process of the application started on the first desktop has an association relationship with the process corresponding to the client;

displaying the electronic equipment of the first desktop and the electronic equipment where the client is located as the same electronic equipment;

displaying the electronic equipment of the first desktop and the electronic equipment of the client as two electronic equipment of the same type; or alternatively, the first and second heat exchangers may be,

and displaying the electronic equipment of the first desktop and the electronic equipment of the client as two different types of electronic equipment.

25. A communication device is characterized by comprising a processor and a memory,

The memory is used for storing a computer program or instructions;

the processor being configured to execute a computer program or instructions in a memory to cause the method of any of claims 1-12 to be performed.

26. A communication device comprising a processing unit and a communication unit, the processing unit being adapted to perform the method according to any of claims 1-12 by means of the communication unit.

27. A computer readable storage medium storing computer executable instructions which, when invoked by a computer, cause the method of any one of claims 1-12 to be performed.

28. A chip system comprising at least one processor, and interface circuitry, the interface circuitry and the at least one processor being interconnected by a line, the processor executing instructions to perform the method of any of claims 1-12.

29. A computer program product, characterized in that the computer program product stores a computer program comprising program instructions which, when executed by a computer, cause the computer to perform the method according to any of claims 1-12.

Images