A cloud computer switching method, device, computer program product and storage medium

Abstract

Embodiments of the present application provide a cloud computer switching method, device, computer program product and storage medium. A terminal device can access and log in to multiple cloud computer systems isolated by a network at the same time, and when a user performs a cloud computer selection operation, the terminal device can automatically establish a data transmission channel with a required cloud computer based on a pre-configured network connection, thereby automatically switching to use the required cloud computer. In this way, during the cloud computer switching process, the user no longer needs to frequently perform account login and logout operations, and the user no longer needs to manually switch the network connection for the terminal device. Only a simple cloud computer selection operation is required to flexibly switch to use the cloud computer, which can realize automation of the cloud computer switching process, reduce the complexity of user operations, and thus improve the switching convenience of the cloud computer.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a cloud computer switching method, device, computer program product and storage medium. Background Technology

[0002] Cloud computers are remote desktop services provided based on cloud computing technology, allowing users to access their personal computer environment configured in the cloud via the internet or a local area network.

[0003] With the increasing popularity of cloud computing, more and more users are starting to use it, and their needs are becoming more diverse. The number of cloud computers used by individual users is also constantly increasing, especially for enterprise users. Different tasks need to be performed on different cloud computers, leading to frequent manual logins and logouts of different accounts to use these cloud computers, which is cumbersome and negatively impacts the user experience. Summary of the Invention

[0004] This application provides a cloud computer switching method, device, computer program product, and storage medium in several aspects to improve the ease of switching cloud computers.

[0005] This application provides a cloud computer switching method applicable to terminal devices. The terminal devices are configured with network connections to multiple cloud computer systems and are logged into each of the multiple cloud computer systems. The multiple cloud computer systems are network isolated from each other. The method includes:

[0006] In response to the cloud computer selection operation, the target cloud computer to which to switch is determined from the cloud computers provided by the multiple cloud computer systems;

[0007] In the plurality of cloud computer systems, identify the target cloud computer system in which the target cloud computer is located;

[0008] Based on the network connection configured for the target cloud computer system, a data transmission channel is established between the terminal device and the target cloud computer to switch to using the target cloud computer.

[0009] This application embodiment also provides a cloud computer switching system, wherein the cloud computer switching system has been configured with network connections between the terminal device and multiple cloud computer systems respectively, and has been logged into the multiple cloud computer systems respectively. The multiple cloud computer systems are network isolated from each other. The cloud computer switching system includes a cloud computer client and a cloud computer switching device.

[0010] The cloud computer switching device is configured to respond to a cloud computer selection operation by determining the target cloud computer to which the device needs to switch from among the cloud computers provided by the plurality of cloud computer systems; identifying the target cloud computer system in which the target cloud computer is located among the plurality of cloud computer systems; and establishing a data transmission channel between the terminal device and the target cloud computer based on the network connection configured for the target cloud computer system, so as to switch to using the target cloud computer.

[0011] The cloud computer client is configured to display the target cloud computer.

[0012] This application also provides a terminal device, including a memory, a processor, and a communication component;

[0013] The memory is used to store one or more computer instructions;

[0014] The processor is coupled to the memory and the communication component to execute one or more computer instructions for performing the aforementioned cloud computer switching method.

[0015] This application also provides a computer-readable storage medium for storing a computer program, which, when executed by one or more processors, causes the one or more processors to perform the aforementioned cloud computer switching method.

[0016] This application also provides a computer program product, including a computer program that, when executed by one or more processors, causes the one or more processors to perform the aforementioned cloud computer switching method.

[0017] In this embodiment, a method is proposed to configure network connections between multiple isolated cloud computer systems on a single terminal device, allowing simultaneous login to these systems. Based on this, in response to a cloud computer selection operation, the target cloud computer to be switched to can be determined, and the target cloud computer system it resides in can be identified. Furthermore, based on the network connection configured for the target cloud computer system, a data transmission channel can be automatically established between the terminal device and the target cloud computer to switch to the desired cloud computer. Accordingly, a single terminal device can simultaneously access and log in to multiple cloud computer systems. When a user performs a cloud computer selection operation, the terminal device can automatically establish a data transmission channel with the desired cloud computer based on a pre-configured network connection, thereby automatically switching to the desired cloud computer. This eliminates the need for frequent account login and logout operations and manual network connection switching during cloud computer switching. Users can simply perform a cloud computer selection operation to flexibly switch between cloud computers, automating the switching process, reducing user complexity, and improving the convenience of cloud computer switching. Attached Figure Description

[0018] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0019] Figure 1 A flowchart illustrating a cloud computer switching method provided for an exemplary embodiment of this application;

[0020] Figure 2 A logical schematic diagram of a cloud computer switching method provided for an exemplary embodiment of this application;

[0021] Figure 3 A schematic diagram of an optional internal structure in a cloud computer switching system provided as an exemplary embodiment of this application;

[0022] Figure 4 and Figure 5 A schematic diagram illustrating the display effect during a cloud desktop switching process, provided as an exemplary embodiment of this application;

[0023] Figure 6 and Figure 7 A schematic diagram illustrating the effect of a network connection configured for a terminal device, provided as an exemplary embodiment of this application;

[0024] Figure 8 and 9 This application provides an exemplary embodiment of a display effect diagram during the login process;

[0025] Figure 10 A schematic diagram illustrating the effect of a transmission status display window provided in an exemplary embodiment of this application;

[0026] Figure 11 This is a schematic diagram of the structure of a terminal device provided as another exemplary embodiment of this application. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0028] Before proceeding with a detailed description of the technical solutions provided in the various embodiments of this application, the following is a brief explanation of several technical concepts involved in this application.

[0029] Cloud computing, also known as desktop virtualization or cloud desktop, is a virtualized desktop environment provided through cloud computing technology. Users can remotely access the full functionality of a personal computer via the internet.

[0030] A cloud computing system can be understood as a server cluster used to provide cloud computers. A cloud computing system may include a management device and multiple cloud computer servers; the management device is used to manage these multiple cloud computer servers. A cloud computer server can refer to a cloud server used to support the operation of cloud computers. It should be understood that a cloud computer server may include components such as CPU, memory, images, and cloud disks, and can be a type of cloud server that can be readily available and elastically scalable.

[0031] The terminal device can render the desktop content of the cloud computer to the front end through the cloud computer client, and redirect the input and output data such as mouse operations of the front end to the cloud computer server.

[0032] Public cloud can be understood as a cloud computing environment provided to the public by cloud providers via the Internet, which can be shared by multiple users.

[0033] A private cloud can be understood as a dedicated cloud computing environment provided by a cloud provider to a single user, who can exclusively use the cloud computing environment and not share it with other users.

[0034] During their research, the inventors discovered that multiple cloud computers used by a user might be distributed across different network environments. For example, a business user might typically deploy cloud computers used for financial tasks in a private cloud, while those used for general tasks would typically be deployed in a public cloud. However, due to the uniqueness of the hardware interface on a physical network card, a single physical network card can only be connected to one network environment at a time via a network cable or other physical medium—for example, connecting to a network access point in a public cloud or a network access point in a private cloud, much like a socket can only have one plug inserted at a time.

[0035] Therefore, currently, when users need to switch between cloud computers located in different network environments, they need to manually modify physical connection parameters such as IP address and subnet address on the physical network card of the terminal device. Furthermore, users also need to switch accounts and log in when using different cloud computers. It is clear that users need to perform complex manual operations to complete a single cloud computer switch, which negatively impacts the user experience.

[0036] Therefore, this application proposes a cloud computer switching method to improve the convenience of switching cloud computers.

[0037] The technical concept of the cloud computer switching method proposed in this application is that: users only need to perform a simple cloud computer selection operation on the terminal device, and the terminal device can automatically complete the cloud computer switching, thereby reducing the complexity of user operation and improving the convenience of cloud computer switching.

[0038] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0039] Figure 1 This is a flowchart illustrating a cloud computer switching method provided as an exemplary embodiment of this application. Figure 2 This is a logical schematic diagram of a cloud computer switching method provided as an exemplary embodiment of this application. The method can be executed by a cloud computer switching system, which can be implemented as software, hardware, or a combination of both, and can be integrated into a terminal device.

[0040] In this embodiment, the terminal device can be pre-configured with network connections between multiple cloud computer systems that are isolated from the network. Here, network isolation can be understood as the isolation between the network environments in which different cloud computer systems reside. For example, cloud computer system A is located in a public cloud, and cloud computer system B is located in a private cloud; cloud computer system A and cloud computer system B are network isolated from each other. As another example, cloud computer system A is located in one private cloud, and cloud computer system B is located in another private cloud; cloud computer system A and cloud computer system B are also network isolated from each other.

[0041] The network connection in this embodiment may include physical connection and / or logical connection.

[0042] Physical connection, as understood, refers to the method of network access achieved through network cables or other physical media. It involves hardware-level connections and has a tangible physical communication link. For example, as mentioned earlier, configuring physical connection parameters such as subnet addresses for physical network interface cards (NICs) in a terminal device to enable the terminal device to access a network constitutes a physical connection. In this embodiment, the physical connection between the terminal device and some cloud computer systems can be configured based on the physical NICs in the terminal device. One physical NIC in the terminal device can support a physical connection between the terminal device and one cloud computer system. Therefore, preferably, the number of cloud computer systems using physical connections can be the same as the number of physical NICs in the terminal device. If the terminal device has multiple physical NICs, different physical NICs can support physical connections between the terminal device and different cloud computer systems.

[0043] Logical connections, in this context, can be understood as virtual network connections created on the basis of existing physical connections through software configuration and network protocols. They do not rely on direct physical communication links but rather are logical communication links constructed using software configuration and network protocols. In this embodiment, the number of physical connections supported by the physical network interface card on the terminal device is limited. For the portion exceeding this limit, logical connections can be used in this embodiment to configure the network connection between the terminal device and the relevant cloud computer system.

[0044] Based on this, in this embodiment, the terminal device can be pre-configured with network connections between itself and the multiple cloud computer systems that need to be accessed. Moreover, the network connection type can be selected as needed when accessing different cloud computer systems. The network connection type includes the aforementioned physical connection and logical connection.

[0045] It is understood that this embodiment does not require the terminal device to maintain a long connection with multiple cloud computer systems. Rather, it is sufficient to configure the network connection between the terminal device and multiple cloud computer systems and keep this communication connection open.

[0046] In this embodiment, the terminal device can also pre-login to multiple cloud computer systems. Here, "login" can be understood as the identity information used in the terminal device having passed the login verification of the cloud computer systems. That is, the identity information used in the terminal device has the permission to log in to the cloud computer systems. In this embodiment, the cloud computer switching device can record the identity information used when logging into multiple cloud computer systems, or store login credentials issued by the cloud computer systems, to maintain the terminal device's logged-in status for multiple cloud computer systems.

[0047] refer to Figure 2 Based on this, in this embodiment, a single terminal device can simultaneously access and log in to multiple network-isolated cloud computer systems.

[0048] Based on this, refer to Figure 1 The cloud computer switching method provided in this embodiment may include:

[0049] Step 100: In response to the cloud computer selection operation, determine the target cloud computer to switch to from the cloud computers provided by the multiple cloud computer systems;

[0050] Step 101: Identify the target cloud computer system in which the target cloud computer is located among the multiple cloud computer systems;

[0051] Step 102: Based on the network connection configured for the target cloud computer system, establish a data transmission channel between the terminal device and the target cloud computer to switch to using the target cloud computer.

[0052] After establishing the network connection between the terminal device described above and multiple cloud computer systems, the terminal device can automatically switch between cloud computers based on the user's cloud computer selection operation.

[0053] Figure 3 This is a schematic diagram of an optional internal structure in a cloud computer switching system provided as an exemplary embodiment of this application. (Reference) Figure 3 This embodiment proposes that a self-designed cloud computer switching device can be deployed in the cloud computer switching system.

[0054] refer to Figure 1 In step 100, it is proposed that the cloud computer switching device can respond to the cloud computer selection operation and determine the target cloud computer to which it needs to switch from among the cloud computers provided by multiple cloud computer systems. The cloud computer selection operation is a manual operation by the user, which can be understood as the user manually selecting the cloud computer to which they wish to switch.

[0055] In this embodiment, the user can pre-select the desired cloud computer from multiple cloud computer systems connected to the terminal device. This selection process can be initiated by the user or completed automatically by the terminal device; no limitation is made here. Among the cloud computers provided by the multiple cloud computer systems, the selected cloud computer is the one available for the user to switch to. Thus, in step 100, the cloud computer switching device responds to the cloud computer selection operation and determines the target cloud computer to switch to from the available cloud computers. It is understood that the available cloud computers can be some of the cloud computers provided by the aforementioned multiple cloud computer systems. Therefore, in step 100, the terminal device can display a display window corresponding to each of the multiple available cloud computers, which can display thumbnails, icons, or desktop content. The cloud computer selection operation can be, for example, a user selection operation on a specific display window; no limitation is made here regarding the manual operation corresponding to the cloud computer selection operation.

[0056] In step 100, the cloud computer switching device can select the cloud computer in the cloud computer selection operation as the target cloud computer to which it needs to switch.

[0057] Continue to refer to Figure 1 In step 101, the cloud computer switching device can identify the target cloud computer system in which the target cloud computer is located. As introduced in the technical concept explanation section above, a cloud computer system can contain at least one cloud computer server, therefore, a cloud computer system can provide at least one cloud computer to the outside world.

[0058] In this embodiment, the terminal device can autonomously record the cloud computer system where the user can switch between available cloud computers. Alternatively, the terminal device can also query the cloud computer system where the user can switch between available cloud computers from external devices. That is, in this embodiment, the terminal device can ascertain the relationship between cloud computers and cloud computer systems. Based on this, in step 101, the terminal device can easily identify the target cloud computer system where the target cloud computer is located, based on this relationship.

[0059] According to the technical concept in this embodiment, identifying the target cloud computer system in step 101 is mainly to determine which cloud computer system's network connection should be used to access the target cloud computer. That is, the terminal device performs a traffic redirection function, promptly redirecting traffic after a cloud computer selection operation to the appropriate network connection so that this traffic can flow to the target cloud computer the user needs to switch to. Thus, in this embodiment, when a cloud computer selection operation occurs on the terminal device, the cloud computer switching device can automatically identify and configure the correct network context (user identity, device status, time, etc.), thereby ensuring accurate switching to the user's desired cloud computer.

[0060] Based on this, refer to Figure 1 In step 102, the cloud computer switching device can establish a data transmission channel between the terminal device and the target cloud computer based on the network connection configured for the target cloud computer system, so as to switch to using the target cloud computer.

[0061] In this embodiment, network connections with different cloud computer systems are already configured in the terminal device. Based on these network connections, the terminal device has the ability to communicate with different cloud computer systems at any time. For the cloud computers within the cloud computer system, this embodiment proposes a dynamic, on-demand connection establishment mechanism.

[0062] The dynamic on-demand connection mechanism here can be understood as automatically establishing a data transmission channel when access to the cloud computer is needed, and disconnecting the data transmission channel in a timely manner after the access is completed.

[0063] In this embodiment, the dynamic on-demand establishment mechanism establishes data transmission channels on demand, taking cloud computers as the unit. This allows a single data transmission channel established in step 102 to support a terminal device to access a single cloud computer in the cloud computer system, rather than all cloud computers in the cloud computer system. This ensures that the cloud computer system exposes only the necessary cloud computers to the terminal device, thereby minimizing the exposure surface and attack surface, and improving the security of the cloud computer system.

[0064] In this embodiment, the dynamic on-demand establishment mechanism connects different cloud computers, making the data transmission channels used independent of each other. This independence avoids the potential risks of lateral movement, and even if a data transmission channel is attacked, it will not affect the security of other cloud computer systems.

[0065] Preferably, in this embodiment, the data transmission channel established in step 102 can be an encrypted channel. During the data transmission process between the terminal device and the target cloud computer, the data can be encrypted using encryption protocols (such as TLS, IPsec, etc.) before transmission to ensure the security and integrity of data transmission, thereby further protecting the data security in the target cloud computer.

[0066] In one exemplary implementation, tunneling technology can be used in step 102 to establish the required data transmission channel. Tunneling technology is a network communication technology whose core is to create a virtual and secure channel (i.e., a tunnel) that allows data to be transmitted as if in a straight line, even if the actual path may pass through different network layers or cross different network environments.

[0067] After establishing a data transmission channel between the terminal device and the target cloud computer in step 102, the terminal device can use the target cloud computer without any obstacles through this data transmission channel. When another cloud computer selection operation occurs, the cloud computer switching device can automatically disconnect the data transmission channel between the terminal device and the aforementioned target cloud computer.

[0068] The process of using cloud computers will not be explained in detail here.

[0069] It is worth emphasizing that, in step 102, there is no need to modify the physical connection parameters such as the IP address and subnet address on the physical network card of the terminal device as in traditional solutions. Since the terminal device has network connections configured separately for different cloud computer systems, the required network connection can be used as needed in step 102, and the physical connection parameters on the physical network card of the terminal device do not need to be modified.

[0070] Furthermore, this embodiment also proposes that after identifying the target cloud computer, the cloud computer switching device can trigger a switch to the target security policy corresponding to the target cloud computer; and perform security control on the usage operations that occur during the use of the target cloud computer in accordance with the target security policy.

[0071] The security policies here may include, but are not limited to, data transfer permissions and clipboard access permissions. Different cloud computers may have different security policies. Additionally, the security policies can be directly used by the cloud computer switching device. In this case, the cloud computer switching device can switch the security policy in the terminal device to the target security policy corresponding to the target cloud computer. Based on the target security policy, the cloud computer switching device can implement security control over usage operations occurring during the use of the target cloud computer locally on the terminal device. The security policies can also be used on the cloud computer system side. In this case, the cloud computer switching device can promptly notify the management device in the cloud computer system to which the target cloud computer belongs to switch to the target security policy corresponding to the target cloud computer, thereby enabling security control over usage operations occurring during the use of the target cloud computer through the management device. This embodiment does not limit the user of the security policies.

[0072] Therefore, in this embodiment, the security policy can be switched in a timely manner while switching cloud computers, thereby enabling more accurate security control over the usage operations that occur during the use of the target cloud computer, ensuring the security of the target cloud computer, and preventing unauthorized usage operations.

[0073] Furthermore, this embodiment also proposes that the cloud computer switching device can perform risk assessment on the network traffic sent from the terminal device to the target cloud computer during the use of the target cloud computer; if abnormal network traffic is determined, the traffic control strategy corresponding to the target cloud computer is adjusted to intercept subsequent abnormal network traffic.

[0074] The risk assessment in this embodiment may include, but is not limited to, dimensions such as abnormal bandwidth usage and confidential data transfer. For example, if a terminal device continuously transfers extremely large files while using a cloud computer, resulting in abnormal bandwidth usage, the traffic control policy of the terminal device for that cloud computer can be adjusted, such as prohibiting the terminal device from initiating network traffic to that cloud computer. As another example, regarding network traffic on the terminal device that involves the transfer of confidential data between different cloud computers, the traffic control policy of the terminal device can be adjusted, such as prohibiting all subsequent network traffic from the terminal device.

[0075] Based on this, by introducing risk assessment, network traffic on terminal devices can be continuously monitored, and traffic control policies can be automatically adjusted to adjust access permissions and security policies, enabling rapid response to abnormal traffic. This effectively enhances the self-defense capabilities of terminal devices and allows them to effectively cope with emerging threats.

[0076] In summary, this embodiment proposes configuring network connections between multiple isolated cloud computer systems on a single terminal device, allowing simultaneous login to these systems. Based on this, in response to a cloud computer selection operation, the target cloud computer to be switched to can be determined, and the target cloud computer system it resides in can be identified. Furthermore, based on the network connection configured for the target cloud computer system, a data transmission channel can be automatically established between the terminal device and the target cloud computer to switch to the desired cloud computer. Accordingly, a single terminal device can simultaneously access and log in to multiple cloud computer systems. When the user performs a cloud computer selection operation, the terminal device can automatically establish a data transmission channel with the desired cloud computer based on a pre-configured network connection, thus automatically switching to the desired cloud computer. This eliminates the need for frequent account login and logout operations and manual network connection switching during cloud computer switching. Users can simply perform a cloud computer selection operation to flexibly switch between cloud computers, automating the switching process, reducing user complexity, and improving the convenience of cloud computer switching.

[0077] In the above or following embodiments, reference is made to Figure 3 Furthermore, a self-designed cloud computer client can be deployed in the cloud computer switching system. In this embodiment, the cloud computer client can be used for human-computer interaction with the user, as well as for dynamically loading and displaying display windows of cloud computers from multiple cloud computer systems.

[0078] refer to Figure 3 Unlike the traditional architecture where one cloud PC system corresponds to one cloud PC client, this embodiment proposes deploying a cloud PC client on a terminal device to dynamically load and display cloud PCs from multiple cloud PC systems accessed by the terminal device, forming a one-to-many architecture. This means that a single cloud PC system can provide multiple cloud PCs. In this embodiment, the cloud PC client can load and display the cloud PCs pre-selected by the user across multiple cloud PC systems; unselected cloud PCs may not be loaded or displayed. Within a single cloud PC system, a user can select one or more cloud PCs.

[0079] The cloud PC client in this embodiment provides a cloud PC client interface, and multiple display windows can be displayed simultaneously on the same screen. These multiple display windows correspond to the multiple cloud PCs pre-selected by the user mentioned earlier.

[0080] Based on multiple display windows displayed on the same screen in the cloud computer client interface, this embodiment can support users to perform cloud computer selection operations in the cloud computer client interface. The cloud computer switching device can monitor the display window selected in the cloud computer selection operation and determine the cloud computer corresponding to the selected display window as the target cloud computer to which the user needs to switch.

[0081] Figure 4 and Figure 5 This is a schematic diagram illustrating the display effect during a cloud desktop switching process, provided as an exemplary embodiment of this application. (Reference) Figure 4 The cloud PC client interface displays two windows simultaneously. The left window shows the cloud PC currently in use. Figure 4 The example shown is the desktop content corresponding to cloud computer M. The display window on the right shows the desktop content of another cloud computer (M). Figure 4 The example shown is a thumbnail of a cloud computer (N). Based on this, in this embodiment, users can perform a selection operation (i.e., a cloud computer selection operation) on the right-hand display window, and the terminal device can determine the cloud computer corresponding to the right-hand display window as the target cloud computer to switch to.

[0082] The cloud computer client designed in this embodiment can integrate a quick switching function. Users can intuitively see the cloud computers selected in multiple cloud computer systems on the same screen, and can instantly switch the focus between different cloud computers on the same screen by performing cloud computer selection operations such as clicking on the cloud computer thumbnail or using shortcut keys, reducing operation delay and improving work efficiency.

[0083] Accordingly, in this embodiment, a self-designed cloud PC client provides users with a unified and intuitive interactive interface, serving as a centralized interaction entry point for multiple cloud PC systems. This client can dynamically load and display cloud PCs from multiple systems. Furthermore, the client integrates a quick switching function, allowing users to seamlessly browse and select different cloud PCs within the client interface through simple operations, thereby effectively improving the ease of use for multiple cloud PCs.

[0084] Furthermore, the self-designed cloud PC client in this embodiment also integrates dynamic window management functionality, providing a flexible window layout mechanism that allows users to freely drag, scale, or stack display windows of cloud PCs from different cloud PC systems within the cloud PC client interface. In this regard, this embodiment proposes that: after determining the target cloud PC to switch to, the cloud PC switching device can trigger the cloud PC client to switch the display window corresponding to the target cloud PC from a non-focus window to a focus window according to the preset focus window display parameters in the selected layout style. Additionally, it can also trigger the cloud PC client to switch the display window corresponding to the previous cloud PC from a focus window to a non-focus window. Of course, in this embodiment, the processing method for the display window corresponding to the previous cloud PC is not limited to this. It is also possible that it does not need to be switched from a focus window to a non-focus window; for example, it can remain a focus window, waiting for further user operations, such as window minimization, before adjusting the display window corresponding to the previous cloud PC. No further examples of processing methods are provided here.

[0085] The parameters displayed in the focus window may include, but are not limited to, the size of the focus window and its positional relationship with non-focus windows, etc., which are not limited here. The layout style selected in the cloud PC client can be user-defined or a default setting, which are also not limited here. The focus window renders the desktop content of the cloud PC, while the non-focus windows may display the cloud PC icon or thumbnail. The focus window is usually larger than the non-focus windows, and the focus window is usually located at the top layer. The non-focus windows will not obscure the focus window, so as to more prominently and intuitively display the cloud PC that the user needs.

[0086] refer to Figure 4 In one exemplary layout style, the focused window and non-focused windows can be tiled without obscuring each other; the size of the focused window is larger than the size of the non-focused windows. (See reference) Figure 4 The large window on the left is the focus window, and the small window on the right is the non-focus window. The focus window renders the desktop content of the currently used cloud computer, while the non-focus window displays a thumbnail of another cloud computer. Of course, this is just an example; other layout styles can be provided in this embodiment, such as full-screen display of the focus window, or overlapping arrangements between the focus and non-focus windows. No limitation is made on the layout style here.

[0087] As mentioned above, users can click Figure 4 The display window on the right side triggers a switch to the cloud computer on the right. See also... Figure 5 When the user clicks Figure 4After the display window on the right appears, the cloud computer on the right will be identified as the target cloud computer. Following the layout format selected in the cloud computer client, the size of the display window on the right will increase, becoming the focus window. Figure 5 As shown, the small window on the right becomes a large window and renders the desktop content of the cloud computer on the right. The large window on the left becomes a small window, that is, it switches to a non-focus window and displays a thumbnail of the cloud computer on the left.

[0088] In this way, after the user selects a cloud computer, the cloud computer client determines the display position of the target cloud computer's display window within the client interface according to the selected layout style, thus displaying the target cloud computer's desktop content within the display window. The user can then begin using the target cloud computer normally.

[0089] Furthermore, the self-designed cloud PC client in this embodiment also supports users to adjust windows as needed. Therefore, this embodiment proposes that the cloud PC client can also respond to window adjustment operations occurring in the cloud PC client interface, adjusting the display state of the selected display window in the cloud PC client interface.

[0090] The window adjustment operations here may include, but are not limited to, full-screen operation, drag operation, and window size adjustment operation; the display status here may include, but is not limited to, display position, window size, and the stacking relationship with other display windows.

[0091] Furthermore, the self-designed cloud PC client in this embodiment also supports security level visualization. To this end, this embodiment proposes that: the cloud PC switching device can determine the security level for each cloud PC corresponding to multiple display windows simultaneously shown on the cloud PC client interface. The security level is used to characterize the data confidentiality level of the cloud PC; the corresponding security level is displayed in association on these multiple display windows. That is, the security level determined for the cloud PC corresponding to any one of the multiple display windows can be displayed in association. (Reference) Figure 4 The security level of the corresponding cloud computer is displayed in the right-hand window.

[0092] This embodiment does not limit the number of security levels or the evaluation criteria, and can be flexibly designed as needed. In one exemplary implementation, the evaluation criteria can be designed according to the network type of the network environment in which the cloud computer system is located. For example, two security levels can be designed: when the network type is a public cloud, the security level is determined to be low; when the network type is a private cloud, the security level is determined to be high. Based on this, the cloud computer switching device in this embodiment can determine the network type of the network environment in which the terminal device is connected to multiple cloud computer systems; for any cloud computer corresponding to any display window simultaneously displayed on the cloud computer client interface, the security level corresponding to that cloud computer can be determined according to the network type of the cloud computer system to which that cloud computer belongs.

[0093] This embodiment does not limit the visualization method for security levels, as long as it can be associated with the corresponding display window. For example, a security level identifier can be displayed in the display window to represent the security level. Alternatively, different window colors can be used to distinguish different security levels, so the window color of the display window can be used to represent the security level. No further examples of security level visualization methods will be provided here.

[0094] In this way, by displaying the security level of the cloud computer in the display window, users can easily perceive the level of data confidentiality of the cloud computer. This allows users to quickly identify which cloud computer to switch to when they need to change their work content, which can effectively enhance users' awareness and control over the attributes of the cloud computer.

[0095] Furthermore, the self-designed cloud PC client in this embodiment also supports visualization of network environment information. To this end, this embodiment proposes that: the cloud PC switching device can determine the network environment information for each cloud PC corresponding to multiple display windows simultaneously shown on the cloud PC client interface; and associate and display the corresponding network environment information on multiple display windows. The network environment information describes the attribute information of the network environment in which the cloud PC is located. This network environment information may include, but is not limited to, network type (e.g., public cloud, private cloud), network connection method (e.g., physical connection, logical connection), and supported bandwidth range, etc., without further examples here. (Reference) Figure 4 The network environment information corresponding to the cloud computer is displayed in the right-hand window.

[0096] In this way, by displaying the network environment information of the cloud computer in the display window, users can easily perceive the network environment in which the cloud computer is located. Users can intuitively perceive the network environment of the cloud computer they are currently using, as well as the network environment of the cloud computer they need to switch to. This can effectively enhance users' awareness and control over the network environment.

[0097] Furthermore, the self-designed cloud PC client in this embodiment can also support security prompts. To this end, this embodiment proposes that the cloud PC client can obtain network connection status information and login expiration reminders, as well as other security prompts, from the cloud PC switching device, and display these security prompts in the corresponding display window of the cloud PC.

[0098] In this way, by displaying security alerts in the presentation window, users can be promptly aware of the security status of the network environment in which different cloud computers are located during operation. For cloud computers involving sensitive operations, additional authentication procedures are added in a timely manner to ensure the security of the cloud computers.

[0099] Furthermore, the self-designed cloud PC client in this embodiment also supports users manually modifying the security level, network environment information, and network connections configured for different cloud PC systems. To this end, this embodiment proposes that the cloud PC client provide a parameter modification entry. In response to a user's parameter modification operation performed on any cloud PC based on this entry, the modified parameters for that cloud PC can be obtained and synchronized to the cloud PC switching device. The parameters supported for modification by the parameter modification entry in this embodiment may include the aforementioned security level, network environment information, and network connection-related parameters, which are not specifically exemplified here.

[0100] Thus, in this embodiment, the automated execution capability of the cloud computer switching device can automatically determine the parameters corresponding to the aforementioned security level and network environment information for the cloud computer. Simultaneously, a parameter modification entry is provided in the cloud computer client, allowing users to manually select or temporarily override the parameters related to the aforementioned security level, network environment information, and network connection. This effectively ensures the accuracy and flexibility of the relevant parameters when the cloud computer switching device misjudges or when users have special needs, enhancing the user's sense of participation and control.

[0101] In addition, in this embodiment, the cloud PC client also provides a policy configuration and management portal. This portal allows administrators to flexibly configure policies for various aspects, such as transmission rules, approval levels, and sensitive information processing, according to organizational security policies. Through the console, administrators can monitor transmission activities on terminal devices and cloud PCs in real time and dynamically adjust policies to adapt to constantly changing security needs. Further details are omitted here.

[0102] In summary, this embodiment describes the design concept of a cloud PC client in a terminal device. The cloud PC client proposed in this embodiment provides a unified and intuitive user interface, allowing users to intuitively perceive the security level and network environment information of the cloud PC. This enables users to more intuitively understand the attributes of different cloud PCs and more quickly identify which cloud PC they need to use. Furthermore, the cloud PC client can cooperate with the cloud PC switching device in this embodiment, supporting the simultaneous display of multiple cloud PCs from multiple cloud PC systems. This allows users to seamlessly switch between cloud PCs, enabling them to work on cloud PCs with different security levels as needed. Relying on the automated switching capability provided by the cloud PC switching device, users do not need complex network configurations or account login / logout operations when switching cloud PCs. From the user's perspective, users can flexibly switch to use cloud PCs with different security levels with a simple cloud PC selection operation, thus effectively improving user convenience.

[0103] In the above or following embodiments, in addition to the function of automatically switching cloud computers, an automatic login function is also proposed to be designed in the cloud computer switching system. That is, the terminal device in this embodiment can automatically log in to multiple cloud computer systems. The automatic login function in the cloud computer switching system is described below.

[0104] refer to Figure 3 This embodiment proposes that a self-designed identification device can also be deployed in the cloud computer switching system. The identification device in this embodiment can be used to help users automatically log in to multiple desired cloud computer systems on terminal devices.

[0105] Based on this, in this embodiment, the identification device can respond to a login operation by obtaining the target identity information entered in the login operation; identifying the cloud computer system associated with the target identity information; and sending a login request to the identified cloud computer system based on the target identity information to request login to the identified cloud computer system.

[0106] Here, the terminal device can provide a login page for users, where they can log in. In this embodiment, the user is guided to input identity information during the login process. This identity information may include, but is not limited to, various types of information such as username and password, user biometric information, and identity tokens. User biometric information may include, but is not limited to, fingerprints and iris scans. This embodiment supports various existing or future types of identity information; an exhaustive list is not provided here.

[0107] It is understandable that logging in is a user operation. In this embodiment, the user only needs to perform the login operation during the login process. However, in the cloud computer switching process mentioned earlier, the user does not need to repeatedly perform the login operation. That is to say, in the cloud computer switching process mentioned earlier, the user does not need to perform frequent account login and logout operations.

[0108] Furthermore, in this embodiment, based on the target identity information entered by the user during login, the identification device can automatically identify the cloud computer system associated with the target identity, eliminating the need for the user to manually configure the relevant information of the cloud computer system to be logged into. Therefore, in this embodiment, the association between identity information and cloud computer systems can be pre-defined, and the identification device can automatically identify the cloud computer system associated with the target identity information based on this association. This association can be established based on information such as the user's historical login records and cloud computer service purchase records. The method for establishing this association is not limited here, nor will it be described in detail.

[0109] Based on this, the identification device in this embodiment can automatically send a login request to the identified cloud computer system based on the target identity information input by the user, in order to request to log in to the identified cloud computer system.

[0110] The cloud computer system associated with the target identity information can be one or more. If there are multiple systems, the identification device in this embodiment can send login requests to all of the cloud computer systems associated with the target identity information, which can further reduce the number of login operations for the user and thus improve the automation level of the login process.

[0111] In this embodiment, the login request carries the target's identity information. The identification device can send the login request to the relevant cloud computer system based on the network connection between the terminal device and the cloud computer system. After the login request arrives at the cloud computer system, the control device in the cloud computer system can verify the login permissions of the target's identity information. If the target's identity information passes the verification, a login credential, such as a session ID or access token, can be issued to the terminal device. In subsequent cloud computer switching processes, the terminal device can use the cloud computer in the cloud computer system without any problems based on the login credential.

[0112] As mentioned earlier, in this embodiment, the pre-established communication connection between the terminal device and multiple cloud computer systems can be maintained continuously. Therefore, after the identification device automatically logs into the relevant cloud computer system based on the target identity information, the terminal device's login status for the relevant cloud computer system can also be maintained. Cloud computer switching events occurring during the cloud computer switching process do not affect the terminal device's login status in each cloud computer system. Thus, in this embodiment, after the identification device completes automatic login during the login phase, it does not need to repeat automatic login during the cloud computer switching phase unless an abnormal event such as network connection loss, cloud computer system update, or identity information update causes the login status to become invalid. Furthermore, users do not need to perform frequent account login and logout operations during the cloud computer switching phase.

[0113] This embodiment mentions that during the login process, the identification device needs to send a login request based on the network connection between the terminal device and the cloud computer system. This embodiment does not limit the configuration method of the network connection. A preferred technical concept proposes:

[0114] The network connection configuration process can be integrated into the login process of this embodiment, automatically configuring the network connection between the terminal device and multiple cloud computer systems, thereby automating the network connection.

[0115] Therefore, this embodiment proposes that: the identification device can search for network configuration information that matches the target identity information based on the preset mapping relationship between identity information and network configuration information, and the searched network configuration information includes destination address information; according to the searched network configuration information, the network connection between the terminal device and the cloud computer system pointed to by the destination address information is configured.

[0116] It is understood that this embodiment proposes a mapping mechanism between identity information and network environment. Specifically, this embodiment pre-constructs a mapping relationship between identity information and network configuration information. The network configuration information describes the network environment of the cloud computer system. The network configuration information may include destination address information, and of course, may also include other information such as network type. The destination address information in this embodiment may include, but is not limited to, the network address of an access point in the network environment. Here, the access point can be a management device within the cloud computer system in the network environment, or it can be a gateway or other physical medium in the network environment that can connect to the management device within the cloud computer system; this is not limited here.

[0117] In this way, after finding network configuration information that matches the target identity information, the identification device can, on the one hand, identify the cloud computer system pointed to by the destination address information as a cloud computer system associated with the target identity information; on the other hand, it can automatically configure the network connection between the terminal device and the cloud computer system pointed to by the destination address information according to the found network configuration information. It should be understood that the network configuration information in this embodiment already provides the information required for establishing a network connection, such as network type and destination address information. Therefore, the identification device can establish a network connection between the terminal device and the cloud computer system pointed to by the destination address information without any obstacles based on the found network configuration information.

[0118] In addition, during the automatic network connection configuration process, the identification device can also determine the network connection method—whether it's a physical connection or a logical connection—as needed for the cloud computer system pointed to by the destination address information. The number of cloud computer systems using physical connections should generally not exceed the number of physical network cards on the terminal devices.

[0119] Based on this, an exemplary configuration scheme proposes that if, based on the network type contained in the found network configuration information, it is detected that any cloud computer system associated with the target identity information is located in a private cloud and requires a logical connection, the identification device can send a network connection request for the cloud computer system to the zero trust controller based on the target identity information; after the network connection request passes the authorization verification of the zero trust controller, the network connection between the terminal device and the target cloud computer system is established using the zero trust controller as a relay.

[0120] In this exemplary configuration scheme, a zero-trust security mechanism is introduced to ensure secure access to cloud computer systems within the private cloud.

[0121] Zero Trust security is a network security architecture and strategy whose core principle is "never trust, always verify." This means that regardless of whether a user or device is located inside or outside the network environment, strict verification and authorization are required to access resources within the network environment. The Zero Trust controller is responsible for this verification and authorization process.

[0122] In this exemplary configuration scheme, the activation information of the zero-trust controller can be recorded in the aforementioned network configuration information. Thus, the identification device can automatically activate the zero-trust controller according to the activation information provided in the network configuration information. Alternatively, the user can be guided to input activation information through a cloud computer client interface, and then the identification device can activate the zero-trust controller. The method by which the identification device obtains the activation information is not limited here.

[0123] By introducing a zero-trust security mechanism, the terminal device in this embodiment becomes a "trust intermediary," automatically performing zero-trust verification on network connection requests sent from the terminal device to the cloud computer system in the private cloud. This ensures that the terminal device can only access the cloud computer system in the private cloud if the user's input identity information on the terminal device has the necessary permissions. In other words, during the automatic network connection configuration process, the terminal device can automatically filter out untrusted network connection requests, thereby improving the security of the computer system in the private cloud.

[0124] Based on the introduction of a zero-trust security mechanism, if it is detected that any cloud computer system associated with the target identity information is located in a private cloud and is logically connected, the identification device can send a login request to the zero-trust controller used in the network connection corresponding to the cloud computer system based on the target identity information; after the login request passes the authentication of the zero-trust controller and the authentication of the cloud computer system, it is determined that the login to the cloud computer system is successful.

[0125] As mentioned earlier, in this scenario, the zero-trust controller acts as an intermediary in the communication link between the terminal device and the cloud computer system. Therefore, the identification device can first send the login request to the zero-trust controller for authentication. Only after the zero-trust controller confirms successful authentication will it forward the login request to the cloud computer system. The terminal device can only successfully log in to the cloud computer system after the cloud computer system also confirms successful authentication. The authentication dimensions that the zero-trust controller and the cloud computer system focus on are usually different, and will not be specifically explained here.

[0126] It is understood that, in this embodiment, after introducing a zero-trust security mechanism to the cloud computer system in the private cloud, the identification device can use the zero-trust controller to achieve request-level trust verification. Only requests verified by the zero-trust controller can be forwarded to the cloud computer system in the private cloud. This allows the terminal device to act as a trust intermediary to achieve request-level access control, thereby effectively ensuring secure access and secure login to the cloud computer system in the private cloud.

[0127] For example, after a user inputs fingerprint information into a terminal device, the identification device can use the trust verification capability of the zero-trust controller to verify whether a network connection request initiated based on that fingerprint information to a cloud computer system A in the private cloud should be allowed, that is, to verify whether the fingerprint information has the permission to access the cloud computer system A in the private cloud. If the zero-trust controller determines that the fingerprint information has the permission to access the cloud computer system A, it can inform the identification device in the terminal device of the verification result, and the identification device can continue to establish a network connection between the terminal device and the cloud computer system A. If the verification by the zero-trust controller fails, the identification device will not establish a network connection between the terminal device and the cloud computer system A. Of course, even if the above-mentioned network connection request is allowed, it does not mean that the login request initiated based on the fingerprint information to the cloud computer system A is trustworthy. Therefore, the identification device can use the trust verification capability of the zero-trust controller to continue to verify the login request.

[0128] Figure 6 and Figure 7 This is a schematic diagram illustrating the effect of a network connection configured for a terminal device, provided as an exemplary embodiment of this application. Taking the terminal device needing to access two cloud computer systems as an example, cloud computer system B is located in a private cloud, and cloud computer system C is located in a public cloud.

[0129] refer to Figure 6 The terminal device is equipped with two physical network interface cards (NICs): NIC 1 and NIC 2. Network connections between the terminal device and cloud computer systems B and C can be established using physical connections. In this embodiment, the identification device can configure the physical connection parameters of NIC 1 based on information such as the IP address and subnet address of the control device in cloud computer system B, thereby configuring the network connection between the terminal device and cloud computer system B. Similarly, the identification device in this embodiment can configure the physical connection parameters of NIC 2 based on information such as the IP address and subnet address of the control device in cloud computer system C, thereby configuring the network connection between the terminal device and cloud computer system C.

[0130] refer to Figure 7 The terminal device is equipped with a physical network card, which can establish a network connection between the terminal device and the cloud computer system C using a physical connection method. In this embodiment, the identification device can configure the physical connection parameters of the physical network card based on information such as the IP address and subnet address of the control device in the cloud computer system C, thereby configuring the network connection between the terminal device and the cloud computer system C. For the cloud computer system B, a logical connection method is used.

[0131] refer to Figure 7In this embodiment, the identification device uses user-inputted identity information to send a network connection request for cloud computer system B to the Software-Defined Perimeter (SDP) controller (acting as a zero-trust controller). After passing the trust verification of the SDP controller, a logical communication link can be established: terminal device - SDP controller - cloud computer system B (specifically, the management and control device within cloud computer system B), that is, the network connection between the terminal device and cloud computer system B is configured. SDP is a security technology for accessing resources based on identity control. It establishes boundaries through software rather than hardware, forming a virtual boundary around network resources, which can hide an organization's infrastructure, reduce the attack surface, and mitigate internal and external network security attacks. Here, the SDP controller is selected as the zero-trust controller in this embodiment.

[0132] pass Figure 6 and Figure 7 As can be seen from the example network connection, in this embodiment, the network connection method can be determined as needed for the cloud computer system to be accessed, and a zero-trust security mechanism can be introduced for the cloud computer system in the private cloud as needed (e.g., when a physical connection is not possible).

[0133] In this way, during the login process, the introduced zero-trust security mechanism can verify the trust of various requests made to the cloud-within-a-cloud computer system. This allows the terminal device to promptly detect and block untrusted requests. Therefore, this effectively ensures the security of the cloud-within-a-cloud computer system during the login process.

[0134] Of course, with the introduction of the zero-trust security mechanism, the zero-trust controller can also be used in the cloud PC switching process mentioned earlier to perform trust verification on various requests, such as data transmission requests and desktop operation requests, that occur to the cloud PC system in the private cloud. Based on the zero-trust security mechanism, advanced authentication mechanisms (such as multi-factor authentication and identity recognition) and fine-grained access control policies can be integrated on the terminal device side. This allows for real-time evaluation and authorization of network requests occurring on the terminal device based on network context (user identity, device status, time, etc.), achieving true on-demand access. Therefore, the security of the cloud PC system in the private cloud can also be effectively guaranteed during the cloud PC switching process.

[0135] Figure 8 and 9This embodiment provides a schematic diagram illustrating the display effect during the login process, as shown in an exemplary embodiment of this application. After the identification device automatically logs into multiple cloud computer systems based on the user's input identity information, the cloud computer systems can return a list of available cloud computers to the cloud computer client. In this embodiment, it supports displaying the cloud computer lists returned by multiple cloud computer systems on the same screen. The user can select the desired cloud computer from the list as needed. The cloud computer selected by the user corresponds to the range of cloud computers for the cloud computer selection operation in this embodiment. Figure 8 The two cloud computers shown are the ones selected by the user. Figure 8 Examples in the text are cloud computers C and D). After selecting a cloud computer, the user can also choose its display position in the cloud computer client interface. It can be seen that when the user has not performed the cloud computer selection operation, the cloud computer's display window does not show any information. This is because the identification device has not yet established a data transmission channel between the terminal device and the cloud computer; therefore, the cloud computer's desktop content has not yet reached the terminal device. (Continue to refer to...) Figure 9 After the user selects a cloud computer, the identification device can establish a connection between the terminal device and that cloud computer. Figure 9 The data transmission channel between the cloud computers on the left and the cloud computers in the middle allows the desktop content of the cloud computers to be loaded into the corresponding display window in the cloud computer client interface. Figure 9 In the middle, the two cloud computers on the right are in a state of waiting to open. It should be understood that "opening" here refers to the first access. After the first access, refer to... Figure 4 and 5 As described above, the display window corresponding to the cloud computer can show a wealth of information.

[0136] In summary, this embodiment utilizes a self-designed identification device to automate the login process. During login, the device automatically identifies the cloud computer system requiring access and login based on the user's input identity information, effectively reducing the complexity of the login process for the user. Furthermore, the device can automatically configure network connections and issue login requests based on the user's input identity information. It can also ensure secure access and login for cloud computer systems in the private cloud by introducing a zero-trust security mechanism as needed.

[0137] It should be understood that the automatic network connection configuration and automatic login provided in this embodiment are optional or preferred. Other implementation methods can also be used in this embodiment to complete network connection configuration and login to the cloud computer system on the terminal device. For example, users can be guided to perform relevant user operations, establish a network connection based on user-input parameters, and issue login requests based on user triggers. These implementation methods can also support completing network connection configuration and login to the cloud computer system on the terminal device, although the degree of automation is slightly lower. Further examples and explanations of these implementation methods are not provided here.

[0138] As proposed in the above or following embodiments, a data transmission control function can also be set in the cloud computer switching system. The data transmission control function in the cloud computer switching system is described below.

[0139] refer to Figure 3 In this embodiment, a self-designed data transmission control device can be deployed in the cloud computer switching system. This data transmission control device is used to securely manage data transmission events occurring in the terminal devices.

[0140] Therefore, this embodiment proposes that: the data transmission control device can respond to the data transmission operation and determine the data sending end, the data receiving end, and the data to be transmitted; if it is determined that the data to be transmitted meets the preset security requirements, it controls the data sending end to transmit the data to the data receiving end.

[0141] The data sending end can be a cloud computer or a terminal device (when the data to be transmitted is located locally on the terminal device), and the data receiving end can be a cloud computer or a terminal device (when the data to be transmitted needs to be transmitted to the local terminal device).

[0142] In this embodiment, the cloud computer client interface on the terminal device supports users performing data transfer operations between different cloud computers or between the terminal device and a cloud computer. For example, a user can use the clipboard to cut data from cloud computer A and then paste it into cloud computer B. Alternatively, a user can copy data from either cloud computer and then paste it onto the terminal device. These data transfer operations can all result in data transfer events, and the data sender, data receiver, and data to be transferred may differ in different data transfer events.

[0143] Based on this, an exemplary implementation proposes that if the data sender and data receiver are different cloud computers, the data transmission control device in the terminal device can trigger the data sender to send a transmission approval request to the control device in its own cloud computer system, thereby driving the control device to evaluate whether the data to be transmitted meets the preset security requirements. Wherein, after determining that the data to be transmitted meets the preset security requirements, the control device can configure the data receiver's access permissions for the data to be transmitted.

[0144] In this exemplary implementation, if the data sender and receiver are different cloud computers, the data to be transmitted resides in the storage space of the cloud computer system. Therefore, during data transmission, the data does not need to pass through a terminal device. Instead, access permissions for the data to be transmitted can be configured on the cloud for the data receiver, enabling the data receiver to download the data to be transmitted from the cloud. In this case, which involves data download between two cloud computer systems, after the cloud computer system to which the data sender belongs has specifically granted access permissions for the data to be transmitted, download requests initiated by the cloud computer system to which the data receiver belongs for the data to be transmitted will be allowed, thus enabling the download of the data to be transmitted without obstacles. The specific process of data download between the two cloud computer systems will not be detailed here.

[0145] In this exemplary implementation, the preset security requirements are used by the management device in the cloud computer system to which the data sender belongs. In this embodiment, the data transmission management device is responsible for triggering the data sender to send a transmission approval request to the management device in its cloud computer system. This management device can assess whether the data to be transmitted can be transmitted, thereby ensuring the security of the data to be transmitted.

[0146] In another exemplary implementation, if the data to be transmitted is located locally on the terminal device, the data transmission control device can trigger the data receiving end to send a transmission approval request to the control device in its own cloud computer system, thereby driving the control device to evaluate whether the data to be transmitted meets the preset security requirements. The data transmission control device can also send the data to be transmitted to the storage space corresponding to the control device, so that after determining that the data to be transmitted meets the preset security requirements, the control device can configure the data receiving end's access permissions to the data to be transmitted, allowing the data receiving end to retrieve the data to be transmitted from the storage space.

[0147] In this scenario, data transmission between the terminal device and the cloud computer is involved; that is, the local data of the terminal device needs to be transferred to the cloud computer. In this exemplary implementation, the preset security requirements are used by the management device in the cloud computer system to which the data receiving end belongs. The data transmission management device in this embodiment is responsible for triggering the data receiving end to send a transmission approval request to the management device in its cloud computer system. This management device can assess whether the data to be transmitted can be transmitted to the cloud computer, thereby ensuring the security of the cloud computer.

[0148] In this embodiment, as mentioned earlier, the security levels of different cloud computer systems are not different. The security level characterizes the degree of data confidentiality within the cloud computer system. The data transmission control device in this embodiment can use the security level of the cloud computer involved in the data transmission process, or between different cloud computers, as a decision-making basis among preset security requirements when data is transmitted between the terminal device and the cloud computer, or between different cloud computers.

[0149] An exemplary security requirement could be: the security level of the data receiver must be higher than or equal to the security level of the data sender; data transmission to the terminal device is not allowed when the security level of the data sender is higher than a specified threshold; and / or, the terminal device is not allowed to receive local data when the security level of the data receiver is higher than a specified threshold, etc.

[0150] Of course, other decision-making criteria can also be introduced into the preset security requirements in this embodiment, including but not limited to file type and sensitivity labels, etc., which are not limited here and no further examples will be given.

[0151] Furthermore, in this embodiment, a manual approval process can be introduced, whereby the aforementioned control device can decide whether to allow data transmission based on the manual approval result. Moreover, the control device can record the approval result and all processing actions occurring during data transmission in an approval log, ensuring full traceability and reviewability.

[0152] Further preferably, this embodiment also proposes that the data transmission control device can trigger the aforementioned control equipment to perform content checks and virus scans on the data to be transmitted, to ensure the security of the data itself. Moreover, for data to be transmitted in a specific format, the data transmission control device can also trigger the aforementioned control equipment to perform format conversion or data anonymization processing on the data to be transmitted, so that the data to be transmitted meets the data format requirements of the cloud computer system to which the data receiving end belongs, further strengthening data protection.

[0153] This embodiment also proposes that the data transmission control device can provide a transmission status display window to show the transmission status of the data to be transmitted. Based on this, in this embodiment: the data transmission control device can monitor the transmission status of the data to be transmitted; and display the transmission status of the data to be transmitted in the transmission status display window provided in the cloud computer client interface. The transmission status includes one or more of the following: approval progress, transmission progress, identification information of the data to be transmitted, and identification information of the data sender and the data receiver.

[0154] Figure 10 This is a schematic diagram illustrating the effect of a transmission status display window provided for an exemplary embodiment of this application. (Reference) Figure 10 The transmission status display window can be set in units of data to be transmitted. Figure 10 The example shows two data sets to be transmitted: data E and data F, demonstrating the transmission status, including the approval progress, transmission progress, identification information of the data to be transmitted, identification information of the data sender, and identification information of the data receiver.

[0155] It is worth noting that the transmission status display window in this embodiment is provided and maintained by the data transmission control device. Therefore, the transmission status display window can display the transmission status of the data to be transmitted involving multiple cloud computers used in the terminal device. It can be understood as a global and unified transmission status display outlet, rather than being limited to a single cloud computer.

[0156] In summary, this embodiment utilizes a self-designed data transmission control device to achieve secure management of data transmission events occurring on the terminal device. When data transmission events occur between different cloud computers or between the terminal device and a cloud computer, the data transmission control device provides a secure and controllable data transmission mechanism, thereby ensuring the security of data transmission between different cloud computers or between the terminal device and a cloud computer. Especially when data transmission is involved between cloud computers with different security levels, it can reduce the risk of data leakage while meeting reasonable data sharing needs, thus achieving a secure and flexible data transmission solution.

[0157] Based on the descriptions of the foregoing embodiments, the cloud computer switching solution provided in this embodiment includes:

[0158] Multiple cloud computer systems with network isolation can be accessed: Through the cloud computer switching device, multiple physically isolated cloud computer systems in network environments can be dynamically accessed on a single terminal device according to authentication and authorization policies, without the need for repeated network connection configuration, thus improving flexibility and security.

[0159] It enables dynamic identity and permission management: integrating advanced authentication and fine-grained access control to ensure on-demand, real-time evaluation and authorization, and enhancing the accuracy of access control based on multiple factors such as user identity and device status.

[0160] Encryption and microtunneling technologies can be introduced: create a network session for each cloud computer and dynamically establish an independent encrypted channel to ensure end-to-end data security, limit the spread of potential threats, and improve the security of data transmission.

[0161] It can perform adaptive risk assessment: It can use technologies such as machine learning to monitor network behavior in terminal devices, automatically adjust the access permissions and security policies of terminal devices, respond quickly to anomalies, and enhance dynamic defense capabilities.

[0162] It enables intelligent network identification and automatic configuration: It designs a mapping mechanism between identity information and network configuration information to enable automatic matching and selection of network connections when users switch between different cloud computers, thereby improving user experience and operational efficiency.

[0163] It can integrate the UI interface with the free switching function: it provides a unified and intuitive interface, supports simultaneous display of multiple cloud computers, supports dynamic window management, supports security level visualization and one-click switching of cloud computers, and simplifies the operation complexity.

[0164] It enables data transmission control: achieving secure data transmission across security levels, including dynamic data isolation, multi-level approval and auditing, and intelligent document analysis and transformation, ensuring data isolation and compliant transmission, and strengthening data protection measures.

[0165] Accordingly, the cloud computer switching solution provided in this embodiment not only overcomes the shortcomings of traditional solutions such as cumbersome operation, high management costs, and numerous security risks, but also enables users to switch between different network-isolated cloud computer systems freely, efficiently, and securely through the above series of technological innovations. This greatly improves the user experience, increases work efficiency, and provides a more efficient and practical solution for information security management of enterprises and institutions.

[0166] Figure 11 This is a schematic diagram of the structure of a terminal device provided as another exemplary embodiment of this application. For example... Figure 11 As shown, the terminal device may include: a memory 10, a processor 11, and a communication component 12. The terminal device is configured with network connections to multiple cloud computer systems and is logged into each of the multiple cloud computer systems, with network isolation between the multiple cloud computer systems.

[0167] Processor 11, coupled to memory 10 and communication component 12, is used to execute computer programs in memory 10 for:

[0168] In response to the cloud computer selection operation, the target cloud computer to which to switch is determined from the cloud computers provided by the multiple cloud computer systems;

[0169] In the plurality of cloud computer systems, identify the target cloud computer system in which the target cloud computer is located;

[0170] Based on the network connection configured for the target cloud computer system, a data transmission channel is established between the terminal device and the target cloud computer to switch to using the target cloud computer.

[0171] In an optional embodiment, when the processor 11 determines the target cloud computer to which it needs to switch in response to a cloud computer selection operation, it can specifically be used to:

[0172] The cloud PC client interface is displayed, and the cloud PC client interface displays the display windows corresponding to the cloud PCs from the multiple cloud PC systems on the same screen.

[0173] In response to the cloud computer selection operation, the cloud computer corresponding to the selected display window is identified as the target cloud computer.

[0174] In an alternative embodiment, the processor 11 may also be used for:

[0175] For each cloud computer corresponding to the multiple display windows simultaneously displayed on the cloud computer client interface, a security level is determined, and the security level is used to characterize the data confidentiality level of the cloud computer.

[0176] On any of the multiple display windows, the associated display is the security level determined by the cloud computer corresponding to that display window.

[0177] In an alternative embodiment, the processor 11 may also be used for:

[0178] In response to a login operation, obtain the target identity information entered in the login operation;

[0179] Identify the cloud computer system associated with the target identity information;

[0180] Based on the target identity information, a login request is sent to the identified cloud computer system to request login to the identified cloud computer system.

[0181] In an optional embodiment, when identifying the cloud computer system associated with the target identity information, the processor 11 can specifically be used for:

[0182] Based on a preset mapping relationship between identity information and network configuration information, network configuration information that matches the target identity information is searched, and the searched network configuration information includes destination address information.

[0183] The cloud computer system pointed to by the destination address information is identified as a cloud computer system associated with the target identity information.

[0184] In an alternative embodiment, the processor 11 may also be used for:

[0185] Configure the network connection between the terminal device and the cloud computer system pointed to by the destination address information according to the found network configuration information;

[0186] The login request is issued based on the configured network connection.

[0187] In an optional embodiment, when the processor 11 configures the network connection between the terminal device and the cloud computer system pointed to by the destination address information according to the found network configuration information, it can specifically be used for:

[0188] If, based on the network type contained in the found network configuration information, it is detected that any cloud computer system associated with the target identity information is located in a private cloud and requires a logical connection, then a network connection request for the cloud computer system is sent to the zero trust controller based on the target identity information.

[0189] After the network connection request passes the authorization verification of the zero trust controller, a network connection is established between the terminal device and the target cloud computer system, with the zero trust controller acting as an intermediary.

[0190] In an optional embodiment, when the processor 11 sends a login request to the identified cloud computer system based on the target identity information, it can specifically be used for:

[0191] If it is detected that any cloud computer system associated with the target identity information is located in a private cloud and uses a logical connection, then based on the target identity information, the login request is sent to the zero-trust controller used in the network connection corresponding to the cloud computer system.

[0192] After the login request is authenticated by the zero-trust controller and the cloud computer system, it is determined that the login to the cloud computer system is successful.

[0193] In one alternative embodiment, the data transmission channel is an encrypted channel and is disconnected when another cloud computer selection operation occurs.

[0194] In an alternative embodiment, the processor 11 may also be used for:

[0195] In response to a data transmission operation, determine the data sender, the data receiver, and the data to be transmitted;

[0196] If it is determined that the data to be transmitted meets the preset security requirements, the data sending end is triggered to transmit the data to the data receiving end.

[0197] In an alternative embodiment, the processor 11 may also be used for:

[0198] If the data sending end and the data receiving end are different cloud computers, the data sending end is triggered to send a transmission approval request to the management and control device in its own cloud computer system, so as to drive the management and control device to evaluate whether the data to be transmitted meets the preset security requirements.

[0199] Wherein, when the control device determines that the data to be transmitted meets the preset requirements, it configures the data receiving end's access permissions to the data to be transmitted.

[0200] In an alternative embodiment, the processor 11 may also be used for:

[0201] If the data to be transmitted is located locally on the terminal device, the data receiving end is triggered to send a transmission approval request to the management and control device in its own cloud computer system, so as to drive the management and control device to evaluate whether the data to be transmitted meets the preset security requirements.

[0202] When the data sending end is triggered to transmit the data to be transmitted to the data receiving end, it can be specifically used for:

[0203] The data to be transmitted is sent to the storage space corresponding to the control device, so that after the control device determines that the data to be transmitted meets the preset security requirements, it can configure the data receiving end to access the data to be transmitted, so that the data receiving end can obtain the data to be transmitted from the storage space.

[0204] In an alternative embodiment, the processor 11 may also be used for:

[0205] Monitor the transmission status of the data to be transmitted;

[0206] The transmission status of the data to be transmitted is displayed in the transmission status display window provided in the cloud computer client interface;

[0207] The transmission status includes one or more of the following: approval progress, transmission progress, identification information of the data to be transmitted, identification information of the data sending end, and identification information of the data receiving end.

[0208] In an alternative embodiment, the processor 11 may also be used for:

[0209] After the target cloud computer is identified, a switch to the target security policy corresponding to the target cloud computer is triggered. Different cloud computers have different security policies.

[0210] In accordance with the target security policy, security control is exercised over the usage operations that occur during the use of the target cloud computer.

[0211] In an alternative embodiment, the processor 11 may also be used for:

[0212] During the use of the target cloud computer, a risk assessment is performed on the network traffic sent from the terminal device to the target cloud computer;

[0213] If abnormal network traffic is detected, the traffic control policy corresponding to the target cloud computer is adjusted to intercept subsequent abnormal network traffic.

[0214] In an alternative embodiment, the processor 11 may also be used for:

[0215] After identifying the target cloud computer to switch to, the display window corresponding to the target cloud computer is switched from a non-focus window to a focus window according to the preset focus window display parameters in the selected layout style; and / or,

[0216] Switch the display window corresponding to the cloud computer from the focus window to the non-focus window.

[0217] In an alternative embodiment, the processor 11 may also be used for:

[0218] In response to a window adjustment operation occurring in the cloud PC client interface, adjust the display state of the selected display window in the cloud PC client interface;

[0219] The window adjustment operation includes drag operation and / or window size adjustment operation; the display state includes one or more of the following: display position, window size, and stacking relationship with other display windows.

[0220] Furthermore, such as Figure 11 As shown, the terminal device also includes a display 13, a power supply component 14, an audio component 15, and other components. Figure 11 The diagram only shows some components and does not mean that the terminal device only includes... Figure 11 The components shown.

[0221] It is worth noting that the technical details of the various embodiments of the terminal device mentioned above can be found in the relevant descriptions in the foregoing method embodiments. To save space, they will not be repeated here, but this should not cause any loss to the scope of protection of this application.

[0222] The above Figure 11The memory in the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0223] The above Figure 11 The communication component is configured to facilitate wired or wireless communication between the device containing the communication component and other devices. The device containing the communication component can access wireless networks based on communication standards, such as 2G, 3G, 4G / LTE, 5G, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel.

[0224] The above Figure 11 The display in the document includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a Touch Panel, the screen can be implemented as a touchscreen to receive input signals from a user. The Touch Panel includes one or more touch sensors to sense touches, swipes, and gestures on the Touch Panel. The touch sensors can sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation.

[0225] The above Figure 11 The power supply component provides power to the various components of the device in which it resides. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which it resides.

[0226] The above Figure 11The audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0227] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the above-described method embodiments. The computer-readable storage medium includes volatile or non-volatile components, or a combination thereof, and can be removable or non-removable. Examples of computer-readable storage media include, but are not limited to, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), flash memory or other memory technologies, CD-ROM, Digital Video Disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium.

[0228] Accordingly, this application also provides a computer program product, which includes a computer program or instructions that, when executed by a processor, cause the processor to implement the steps in the above method embodiments. It should be understood that each step or combination of steps in the above method flow can be implemented by the computer program or instructions. Furthermore, these computer programs or instructions can be applied to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device, enabling the processor of the general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to function as an apparatus for implementing the corresponding functions in the above method embodiments.

[0229] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0230] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0231] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for switching between cloud computers, characterized in that, Applicable to terminal devices, wherein the terminal devices are configured with network connections to multiple cloud computer systems and are logged into the multiple cloud computer systems respectively, and the multiple cloud computer systems are network isolated from each other, the method includes: In response to the cloud computer selection operation, the target cloud computer to which to switch is determined from the cloud computers provided by the plurality of cloud computer systems; In the plurality of cloud computer systems, identify the target cloud computer system in which the target cloud computer is located; Based on the network connection configured for the target cloud computer system, a data transmission channel is established between the terminal device and the target cloud computer to switch to using the target cloud computer.

2. The method according to claim 1, characterized in that, In response to the cloud computer selection operation, determine the target cloud computer to switch to, including: The cloud PC client interface is displayed, and the cloud PC client interface displays the display windows corresponding to the cloud PCs from the multiple cloud PC systems on the same screen. In response to the cloud computer selection operation, the cloud computer corresponding to the selected display window is identified as the target cloud computer.

3. The method according to claim 2, characterized in that, Also includes: For each cloud computer corresponding to the multiple display windows simultaneously displayed on the cloud computer client interface, a security level is determined. The security level is used to characterize the data confidentiality level of the corresponding cloud computer. On any of the multiple display windows, the associated display is the security level determined by the cloud computer corresponding to that display window.

4. The method according to claim 1, characterized in that, Also includes: In response to a login operation, obtain the target identity information entered in the login operation; Identify the cloud computer system associated with the target identity information; Based on the target identity information, a login request is sent to the identified cloud computer system to request login to the identified cloud computer system.

5. The method according to claim 4, characterized in that, Identifying the cloud computer system associated with the target identity information includes: Based on the preset mapping relationship between identity information and network configuration information, network configuration information that matches the target identity information is found, and the found network configuration information includes destination address information; The cloud computer system pointed to by the destination address information is identified as a cloud computer system associated with the target identity information.

6. The method according to claim 5, characterized in that, Also includes: Configure the network connection between the terminal device and the cloud computer system pointed to by the destination address information according to the found network configuration information; The login request is issued based on the configured network connection.

7. The method according to claim 6, characterized in that, Based on the found network configuration information, configure the network connection between the terminal device and the cloud computer system pointed to by the destination address information, including: If, based on the network type contained in the found network configuration information, it is detected that any cloud computer system associated with the target identity information is located in a private cloud and requires a logical connection, then a network connection request for the cloud computer system is sent to the zero trust controller based on the target identity information. After the network connection request passes the authorization verification of the zero trust controller, a network connection is established between the terminal device and the target cloud computer system, with the zero trust controller acting as an intermediary.

8. The method according to claim 4 or 7, characterized in that, Based on the target identity information, a login request is sent to the identified cloud computer system, including: If it is detected that any cloud computer system associated with the target identity information is located in a private cloud and requires a logical connection, then based on the target identity information, the login request is sent to the zero-trust controller used in the network connection corresponding to the cloud computer system. After the login request is authenticated by the zero-trust controller and the cloud computer system, it is determined that the login to the cloud computer system is successful.

9. The method according to claim 1, characterized in that, The data transmission channel is encrypted and disconnected when responding to the cloud computer's selection operation again.

10. The method according to claim 1, characterized in that, Also includes: In response to a data transmission operation, determine the data sender, the data receiver, and the data to be transmitted; If it is determined that the data to be transmitted meets the preset security requirements, the data sending end is triggered to transmit the data to the data receiving end.

11. The method according to claim 10, characterized in that, Also includes: If the data sending end and the data receiving end are different cloud computers, the data sending end is triggered to send a transmission approval request to the management and control device in its own cloud computer system, so as to drive the management and control device to evaluate whether the data to be transmitted meets the preset security requirements. Wherein, when the control device determines that the data to be transmitted meets the preset requirements, it configures the data receiving end's access permissions to the data to be transmitted.

12. The method according to claim 10, characterized in that, Also includes: If the data to be transmitted is located locally on the terminal device, the data receiving end is triggered to send a transmission approval request to the management and control device in its own cloud computer system, so as to drive the management and control device to evaluate whether the data to be transmitted meets the preset security requirements. Triggering the data sending end to transmit the data to be transmitted to the data receiving end includes: The data to be transmitted is sent to the storage space corresponding to the control device, so that after the control device determines that the data to be transmitted meets the preset security requirements, it can configure the data receiving end to access the data to be transmitted, so that the data receiving end can obtain the data to be transmitted from the storage space.

13. The method according to any one of claims 10-12, characterized in that, Also includes: Monitor the transmission status of the data to be transmitted; The transmission status of the data to be transmitted is displayed in the transmission status display window provided in the cloud computer client interface; The transmission status includes one or more of the following: approval progress, transmission progress, identification information of the data to be transmitted, identification information of the data sending end, and identification information of the data receiving end.

14. The method according to claim 1, characterized in that, Also includes: After the target cloud computer is identified, a switch to the target security policy corresponding to the target cloud computer is triggered. Different cloud computers have different security policies. In accordance with the target security policy, security control is exercised over the usage operations that occur during the use of the target cloud computer.

15. The method according to claim 1, characterized in that, Also includes: During the use of the target cloud computer, a risk assessment is performed on the network traffic sent from the terminal device to the target cloud computer; If abnormal network traffic is detected, the traffic control policy corresponding to the target cloud computer is adjusted to intercept subsequent abnormal network traffic.

16. The method according to claim 1, characterized in that, Also includes: After identifying the target cloud computer to switch to, the display window corresponding to the target cloud computer is switched from a non-focus window to a focus window according to the preset focus window display parameters in the selected layout style; and / or, Switch the display window corresponding to the cloud computer from the focus window to the non-focus window.

17. The method according to claim 16, characterized in that, Also includes: In response to a window adjustment operation occurring in the cloud PC client interface, adjust the display state of the selected display window in the cloud PC client interface; The window adjustment operation includes drag operation and / or window size adjustment operation; the display state includes one or more of the following: display position, window size, and the stacking relationship between the selected display window and other display windows.

18. A cloud computer switching system, characterized in that, The cloud computer switching system has been configured with network connections to multiple cloud computer systems in the terminal device and has been logged into the multiple cloud computer systems respectively. The multiple cloud computer systems are network isolated from each other. The cloud computer switching system includes a cloud computer client and a cloud computer switching device. The cloud computer switching device is configured to respond to a cloud computer selection operation by determining the target cloud computer to which the device needs to switch from among the cloud computers provided by the plurality of cloud computer systems; identifying the target cloud computer system in which the target cloud computer is located among the plurality of cloud computer systems; and establishing a data transmission channel between the terminal device and the target cloud computer based on the network connection configured for the target cloud computer system, so as to switch to using the target cloud computer. The cloud computer client is configured to display the target cloud computer.

19. A terminal device, characterized in that, Includes memory, processor, and communication components; The memory is used to store one or more computer instructions; The processor is coupled to the memory and the communication component and is used to execute one or more computer instructions to perform the cloud computer switching method according to any one of claims 1-17.

20. A computer-readable storage medium for storing a computer program, characterized in that, When the computer program is executed by one or more processors, the one or more processors perform the cloud computer switching method according to any one of claims 1-17.

21. A computer program product, characterized in that, The method includes a computer program that, when executed by one or more processors, causes the one or more processors to perform the cloud computer switching method according to any one of claims 1-17.

Images