Transmission protocol switching method, device, and storage medium

Abstract

Embodiments of the present invention provide a transmission protocol switching method, a device, and a storage medium. During establishment of the connection between a cloud computer server and a cloud computer client, the two parties can simultaneously enable a plurality of transmission protocols to be selected, instead of specifying a single fixed transmission protocol. Once the connection between the two parties has been established, the cloud computer server can monitor scenario state parameters corresponding to the cloud computer client, so as to sense the transmission demand change condition of the cloud computer client; and the association relationship between the scenario state parameters and the transmission protocols is further preset in the cloud computer server and is used as a decision-making basis for protocol switching. On this basis, when detecting that the scenario state parameters corresponding to the cloud computer client have changed, the cloud computer server can automatically perform transmission protocol switching, so as to dynamically switch the transmission protocols along with the dynamically-changing transmission demands of the cloud computer client, thereby fully exploiting respective advantages of different transmission protocols, ensuring continuous and stable transmission performance of a cloud computer, and improving user experience.

Description

[0001] TECHNICAL FIELD The present disclosure relates to the field of cloud computing technology, and more particularly to a method, device, and storage medium for switching transmission protocols. Background: Cloud computing is a cloud-based desktop service that uses a DaaS (Desktop as a Service) architecture to provide an easy-to-use, secure, and efficient cloud desktop office system. Users can access a cloud computing server through a cloud computing client to interactively operate the cloud computing server, achieving the same experience as using a local computer. Currently, when a cloud computing client and cloud computing server first establish a connection, they must determine which transmission protocol to use for data transmission. After the connection is established, the transmission protocol between the two parties remains unchanged. This rigid transmission protocol selection method results in unstable transmission performance of cloud computing, affecting user experience. SUMMARY OF THE INVENTION Various aspects of the present disclosure provide a method, device, and storage medium for switching transmission protocols to optimize the transmission performance of cloud computing. Embodiments of the present disclosure provide a transmission protocol switching method applicable to a cloud computing server. The method comprises: enabling multiple transmission protocols to be selected during the process of establishing a connection with a cloud computing client; after establishing a connection with the cloud computing client, monitoring a scene state parameter corresponding to the cloud computing client; and, if the scene state parameter corresponding to the cloud computing client changes, controlling transmission protocol switching based on an association between the scene state parameter and the transmission protocol. Furthermore, enabling multiple transmission protocols to be selected during the process of establishing a connection with the cloud computing client comprises: establishing various transmission channels required for data transmission with the cloud computing client; and, based on the transmission channel used for processing the connection, performing identity mutualization with the cloud computing client under each of the multiple transmission protocols to enable the multiple transmission protocols to be selected. Furthermore, based on the transmission channel used for processing the connection, mutual identity authentication is performed with the cloud computer client under the multiple selected transmission protocols, including: creating different protocol ports for different selected transmission protocols; carrying the corresponding protocol ports in identity authentication messages; exchanging identity authentication messages with the cloud computer client under the multiple selected transmission protocols based on the transmission channel used for processing the connection, and performing mutual identity authentication and protocol port agreement with the cloud computer client under the multiple selected transmission protocols. Furthermore, monitoring scenario status parameters corresponding to the cloud computer client includes: monitoring the scenario type corresponding to the cloud computer client; and monitoring user preferences corresponding to the cloud computer client.Furthermore, the scene type includes an audio and video scene. Monitoring the scene type corresponding to the cloud PC client includes: monitoring applications using a microphone device in the cloud PC instance corresponding to the cloud PC client; if an audio and video call application is included among the monitored applications, determining that the scene type corresponding to the cloud PC client is an audio and video scene. Furthermore, the method further includes: monitoring attribute information of data sent to the cloud PC client; if the sent data includes audio data, the data frame rate exceeds a specified frame rate threshold, and / or the number of frames in which the coverage of the changed area in the screenshot exceeds a specified coverage threshold and meets a preset standard, determining that the scene type corresponding to the cloud PC client is an audio and video scene. Furthermore, the user preferences include prioritizing image quality and prioritizing smoothness. Monitoring the user preferences corresponding to the cloud PC client includes: after receiving a preference configuration message sent by the cloud PC client, parsing the user preferences from the preference configuration message and using them as the monitored user preferences corresponding to the cloud PC client. Furthermore, when the scene state parameters corresponding to the cloud computer client change, based on the association between the scene state parameters and the transmission protocol, controlling the transmission protocol switch includes: if the cloud computer client is in a first scene type and the user preference of the cloud computer client is detected to have switched to the first preference, switching to the first transmission protocol associated with the first scene type and the first preference; or if the cloud computer client is in the first preference and the scene type corresponding to the cloud computer client is detected to have switched to the first scene type, switching to the first transmission protocol. Furthermore, if the first scene type is an audio or video scene and the first preference is to prioritize smoothness, the first transmission protocol uses RTC. The method further includes: after switching to the first transmission protocol, if the cloud computer client is detected to have switched from the audio or video scene type to another scene type, or if the user preference of the cloud computer client is detected to have switched from the priority to smoothness to another preference, switching from the first transmission protocol to a second transmission protocol associated with the scene type and preference type currently corresponding to the cloud computer client.Furthermore, switching from the first transmission protocol to a second transmission protocol associated with the scene type and preference type to which the cloud computer client has switched includes: if the scene type of the cloud computer client is switched to a non-audio / video scene or the user preference of the cloud computer client is switched to prioritizing image quality, then using QUICo as the second transmission protocol. Furthermore, controlling the transmission protocol switching includes: controlling the transmission protocol switching in a transmission channel used to transmit audio and video data; wherein the transmission protocols used in other transmission channels remain unchanged. Furthermore, after switching the transmission protocol, the method further includes: if audio data needs to be sent to the cloud computer client, sending a protocol switching notification to the cloud computer client via the transmission channel used to transmit audio data, thereby triggering the cloud computer client to restart its local audio playback device and switch the transmission protocol in the transmission channel used to transmit audio data; and if recording data provided by the cloud computer client needs to be received, sending a protocol switching notification to the cloud computer client via the transmission channel used to transmit recording data, thereby triggering the cloud computer client to restart its local recording device and switch the transmission protocol in the transmission channel used to transmit recording data. Furthermore, the method further includes: if image frames need to be sent to the cloud computer client, sending a protocol switching notification to the cloud computer client via the transmission channel used for transmitting image data, thereby triggering the cloud computer client to switch the transmission protocol of the transmission channel used for transmitting image data; and sending image frames carrying frame numbers to the cloud computer client according to the switched transmission protocol, wherein the first frame sent after the transmission protocol switch also carries key frame data, thereby triggering the cloud computer client to discard unplayed image frames with frame numbers less than the first frame and decode the first frame based on the key frame data. The present disclosure also provides a cloud computer server comprising a memory, a processor, and a communication component; the memory is configured to store one or more computer instructions; and the processor is coupled to the memory and the communication component and configured to execute the one or more computer instructions to perform the aforementioned transmission protocol switching method. The present disclosure also provides a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, causes the one or more processors to perform the aforementioned transmission protocol switching method. In the embodiment of the present disclosure, during the process of establishing a connection between the cloud computer server and the cloud computer client, multiple transmission protocols to be selected can be enabled simultaneously between the two parties, instead of specifying a fixed one.Based on this, after a connection is established between the two parties, the cloud computing server can monitor the scene state parameters corresponding to the cloud computing client to detect changes in the cloud computing client's transmission requirements. Furthermore, the cloud computing server also presets the relationship between the scene state parameters and the transmission protocol, which serves as the basis for protocol switching decisions. Based on this, the cloud computing server can automatically switch the transmission protocol when it detects changes in the scene state parameters corresponding to the cloud computing client. This allows the cloud computing server to dynamically switch the transmission protocol in response to the cloud computing client's dynamically changing transmission requirements, thereby fully leveraging the respective advantages of different transmission protocols, continuously and stably ensuring the cloud computing client's transmission performance, and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS The drawings described herein are provided to provide a further understanding of the present disclosure and constitute a part of this disclosure. The illustrative embodiments of this disclosure and their descriptions are provided to explain this disclosure and are not intended to unduly limit it. In the accompanying drawings: Figure 1 is a flow chart of a transmission protocol switching method provided by an exemplary embodiment of the present disclosure; Figure 2 is a logical diagram of a transmission protocol switching method provided by an exemplary embodiment of the present disclosure; Figure 3 is a schematic diagram of an optional communication architecture between a cloud computing client and a cloud computing server provided by an exemplary embodiment of the present disclosure; Figure 4 is a schematic diagram of an optional implementation of a transmission protocol switching method provided by an exemplary embodiment of the present disclosure; Figure 5 is a logical diagram of the transmission protocol switching validation process in a transmission channel for transmitting image data provided by an exemplary embodiment of the present disclosure; Figure 6 is a logical diagram of the transmission protocol switching validation process in a transmission channel for transmitting audio data provided by an exemplary embodiment of the present disclosure; Figure 7 is a logical diagram of the transmission protocol switching validation process in a transmission channel for transmitting recorded data provided by an exemplary embodiment of the present disclosure; Figure 8 is a schematic diagram of the structure of a cloud computing server provided by another exemplary embodiment of the present disclosure. DETAILED DESCRIPTION To further clarify the objectives, technical solutions, and advantages of the present disclosure, the technical solutions of the present disclosure will be clearly and completely described below in conjunction with specific embodiments of the present disclosure and the corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present disclosure, and are not intended to be exhaustive. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure. Before providing a detailed description of the technical solutions of the various embodiments of this disclosure, a brief explanation of several technical concepts involved in this disclosure is provided below. Cloud PC is a computing-based desktop service on the cloud that utilizes a DaaS (Desktop as a Service) architecture to provide an easy-to-use, secure, and efficient cloud-based desktop office system.In cloud computing technology, a cloud computing client serves as a user terminal. It can connect to a cloud computing server and render and display the cloud desktop. It also redirects user input and output data, such as mouse and keyboard operations, to the cloud computing server, serving as the basis for cloud computing within the cloud computing server. A cloud computing server serves as a server within cloud computing technology. Data computation in cloud computing technology is centralized within the cloud computing server. The cloud computing server can provide the cloud desktop image to the cloud computing client for rendering and display, using methods such as screenshots. A transmission protocol refers to a communication protocol within the transport layer, which primarily handles data transmission across the network. Data transmission between a cloud computing client and a cloud computing server must be performed in accordance with the transmission protocol. Typical transmission protocols include the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP). The following details the technical solutions provided by various embodiments of the present disclosure, in conjunction with the accompanying figures. Figure 1 is a flow chart illustrating a transmission protocol switching method according to an exemplary embodiment of the present disclosure. This method can be performed by a protocol decision device, which can be implemented as software, hardware, or a combination of software and hardware. The protocol decision device can be integrated into a cloud computing server. Referring to Figure 1 , the method may include: Step 100: Activate multiple candidate transmission protocols during the process of establishing a connection with a cloud computing client; Step 101: After establishing a connection with the cloud computing client, monitor the scene state parameters corresponding to the cloud computing client; Step 102: When the scene state parameters corresponding to the cloud computing client change, control transmission protocol switching based on the association between the scene state parameters and the transmission protocol. In this embodiment, the protocol decision device can be deployed in the cloud computing server to execute the transmission protocol switching method provided in this embodiment. Figure 2 is a logical diagram of a transmission protocol switching method provided in an exemplary embodiment of the present disclosure. As shown in Figure 2 , the cloud computing server can communicate with the cloud computing client via a network. To better illustrate the interaction logic between the cloud computing client and the cloud computing server in this embodiment, Figure 2 only shows the cloud computing client and the cloud computing server. However, it should be understood that this embodiment does not modify the communication architecture between the cloud computing client and the cloud computing server. In actual applications, other participants are often used to support communication between the cloud computing client and the cloud computing server, and this embodiment does not limit this. Figure 3 is a schematic diagram of an optional communication architecture between a cloud computing client and a cloud computing server, provided in an exemplary embodiment of the present disclosure.Referring to Figure 3 , the cloud computing client and cloud computing server can communicate via a security gateway. The security gateway can act as a relay server between the cloud computing client and the cloud computing server, routing (mapping) traffic between the two. Further explanation of the security gateway is omitted here. Furthermore, referring to Figure 3 , the cloud computing system can also include a management and control node. The management and control node can provide a management and control platform for cloud computing administrators, allowing them to configure cloud computing management and control. The management and control node can enforce these management and control configurations between the cloud computing client and the cloud computing server. Further explanation of the management and control node is omitted here. Referring to Figures 1 and 2 , in this embodiment, during the process of establishing a connection between the cloud computing client and the cloud computing server, multiple transmission protocols are enabled. Enabling multiple transmission protocols can be understood as establishing connections between the cloud computing client and the cloud computing server based on multiple transmission protocols. Furthermore, after enabling multiple transmission protocols, the cloud computing client and the cloud computing server will maintain the connections established under these transmission protocols. In actual applications, various potential transmission protocols that may be used by the cloud computing client and cloud computing server can be enabled. Of course, considering the cost of connection maintenance, the selected transmission protocols to be enabled on the cloud computing client and cloud computing server can be determined based on actual needs. In this embodiment, the selected transmission protocols may include, but are not limited to, UDP protocols such as QUIC (Quick UDP Internet Connections) and RTC (Real-Time Communications). It should be understood that these are merely exemplary, and the selected transmission protocols in this embodiment are not limited to these. As mentioned above, enabling multiple selected transmission protocols means establishing connections between the cloud computing client and cloud computing server based on various transmission protocols. This embodiment is not limited to the implementation method of establishing connections based on various transmission protocols. In a preferred implementation, various transmission channels required for data transmission can be first established between the cloud computing client and cloud computing server. In this step, the TCP protocol can be used to establish these transmission channels through a handshake. It is worth noting that in this step, the selected transmission protocols in this embodiment have not yet been enabled. Among them, these transmission channels may include but are not limited to:

[0002] Main Channel: handles connections and disconnections with the cloud computer client;

[0003] Inputs Channel: Processes data from input devices such as mouse, keyboard, and touchpad;

[0004] Display Channel: Processes desktop image data;

[0005] Cursor Channel: handles data related to mouse pointer display;

[0006] Playback Channel: Processes the sound data generated by the cloud computer server side;

[0007] Record channel: Processes recording data from the cloud computing client. It should be understood that the aforementioned naming of transmission channels is illustrative and not limiting in this embodiment. The aforementioned Main Channel can be used for connection processing. Based on this, in this preferred implementation, the cloud computing server can establish mutual identity with the cloud computing client under various selected transmission protocols using the transmission channel used for connection processing, thereby enabling the use of these multiple transmission protocols. Thus, in this preferred implementation, mutual identity authentication can be established between the cloud computing client and the cloud computing server under various transmission protocols, relying on the established transmission channel used for connection processing. The mutual identity authentication process under these multiple transmission protocols can be carried out according to their respective protocols, and this embodiment does not interfere with this process. The essence of connection is mutual identity authentication. In this embodiment, after completing mutual identity authentication, the cloud computing client and the cloud computing server have activated the corresponding transmission protocol. In subsequent communication, the two parties no longer need to repeatedly establish connections under various transmission protocols. Furthermore, this preferred implementation proposes modifying the network structure of the cloud computing client and cloud computing server. Referring to Figure 3 , different protocol ports can be created for different candidate transmission protocols on both the cloud computing client and the cloud computing server. These different protocol ports are used to identify different candidate transmission protocols, allowing port numbers to be used to distinguish between different candidate transmission protocols. This can prevent network preemption issues between different candidate transmission protocols within the same protocol, especially when multiple candidate transmission protocols belong to the same protocol. Furthermore, the security gateway between the cloud computing client and the cloud computing server can also simultaneously create more protocol ports to perform port adaptation with the cloud computing client and the cloud computing server, respectively. In actual applications, the cloud computing client and the cloud computing server can each register their created protocol ports with the control node in Figure 3 , which can then distribute these protocol ports to the cloud computing client, the cloud computing server, and the security gateway.Protocol port 5912 will be used, while RTC will use protocol port 5913. Similarly, on the cloud computing client, QUIC will use protocol port 6001, while RTC will use protocol port 6002. Based on this, in this preferred implementation, the cloud computing server and cloud computing client can carry the corresponding protocol port in the authentication message. Based on the aforementioned transmission channel for processing the connection, the cloud computing server and cloud computing client can exchange authentication messages under various selected transmission protocols, thereby achieving mutual identity recognition and protocol port agreement based on the authentication messages. This allows independent connections to be established between the cloud computing server and cloud computing client under various selected transmission protocols. An independent connection here can be understood as not sharing protocol ports with other selected transmission protocols. Continuing with the example port numbers of each protocol port in Figure 3 , when the cloud computer client and cloud computer server perform identity authentication under RTC, the cloud computer client can carry port number 6002 in the identity authentication message, while the cloud computer server can carry port number 5913 in the identity authentication message. In this way, after mutual identity authentication, both parties will carry the port number provided by the other party in data messages during subsequent communication to ensure correct data packet routing. As can be understood from Figure 3 , the connections established under the two selected transport protocols, QUIC and RTC, are independent of each other and will not cause any network preemption issues. It is also worth noting that the above-mentioned scheme of creating different protocol ports for different selected transport protocols is merely a preferred option, which can effectively avoid network preemption issues that may occur between the selected transport protocols. However, it should be understood that in this preferred implementation, different selected transport protocols can also share protocol ports, and this does not affect the implementation of the inventive concept of this embodiment. In this embodiment, other implementations can be used to enable multiple candidate transmission protocols between the cloud computing client and the cloud computing server, and are not limited to the preferred implementation described above. For example, the cloud computing client and the cloud computing server can each perform connection operations according to the standard connection procedures for the multiple candidate transmission protocols to establish standard connections under each of the multiple candidate transmission protocols, rather than relying on the Main Channel in the preferred implementation described above. It should be understood that in step 100, the concept of this embodiment is to simultaneously enable multiple candidate transmission protocols during the establishment process of the cloud computing client and the cloud computing server, and to maintain connections under these candidate transmission protocols. This embodiment supports various implementations for enabling these protocols, and these implementations are not limited, so further examples will not be provided herein. At this point, the connection establishment process between the cloud computing client and the cloud computing server is complete.Afterward, referring to FIG. 1 , in step 101, this embodiment proposes that the cloud computer server monitor the scenario state parameters corresponding to the cloud computer client. The scenario state parameters can be used to describe the usage scenario corresponding to the cloud computer client from a specified state dimension. The usage scenario can be understood as the type of work the user expects to complete using the cloud computer. In this embodiment, an exemplary state dimension included in the scenario state parameters can be the scene type. Optionally, the scene type in this embodiment can include audio and video scenes and non-audio and video scenes. Audio and video scenes can include audio and video call scenes and audio and video playback scenes, while non-audio and video scenes can include office scenes, visual design scenes, and artificial intelligence scenes, among others. Further examples are not provided here. However, it should be understood that the scene type is only one exemplary state dimension included in the aforementioned scene state parameters. In this embodiment, the scene state parameters can also include more state dimensions, such as user preferences. Of course, other state dimensions that can describe the usage scenario corresponding to the cloud computer client can also be included, but further examples are not provided here. Based on the definition of the scene state parameters, it can be seen that in this embodiment, the scene state parameters can reflect the transmission requirements of the cloud computer client. The transmission requirements here can be understood as the types of data that the cloud computing client needs to transmit to the cloud computing server, as well as the preferred transmission performance. Different candidate transmission protocols have different transmission advantages. Based on this, the cloud computing server can fully perceive the transmission requirements of the cloud computing client through the scene state parameters and then determine an appropriate transmission protocol for the cloud computing client. The advantages of the determined transmission protocol will be adapted to the transmission requirements of the cloud computing client. To this end, referring to Figure 1, in this embodiment, the cloud computing server can pre-configure the association between the scene state parameters and the transmission protocol. Based on this association, in step 102, the cloud computing server can control the switching of transmission protocols based on this association when the scene state parameters corresponding to the cloud computing client change. It should be understood that, as mentioned above, the scene state parameters in this embodiment include parameters under multiple state dimensions. Therefore, the scene state parameters are generally a parameter group. In this embodiment, the cloud computing server can associate adapted transmission protocols with different parameter groups. During the process of establishing this association, the aforementioned principles can be followed to associate the scene state parameters with appropriate transmission protocols based on the transmission requirements reflected by them. Furthermore, in this embodiment, the association between scene state parameters and transmission protocols can be configured as needed, and operations such as adding, deleting, and modifying the association can be supported based on actual needs to accommodate flexible and changing transmission requirements.This embodiment does not limit which scene state parameters are associated with which transmission protocols. In this embodiment, the operation of controlling the transmission protocol switch in step 102 may include at least two processing steps: the first step can be described as determining whether a transmission protocol switch is necessary; the second step can be described as implementing the switched transmission protocol after determining the need to switch the transmission protocol. Regarding the first step, in this embodiment, the cloud computing server can promptly detect whether the scene state parameters have changed. Furthermore, if a change is detected, the cloud computing server can determine whether a transmission protocol switch is necessary based on the pre-configured association between the scene state parameters and transmission protocols. This embodiment supports multiple scene state parameters being associated with the same transmission protocol. Therefore, even if the scene state parameters have changed, the associated transmission protocol may not have changed. In this case, there is no need to switch the transmission protocol. Specifically, the cloud computing server can query the transmission protocol associated with the changed scene state parameters based on the pre-configured association. If the queried transmission protocol differs from the currently used transmission protocol, it confirms the need to switch the transmission protocol. Regarding the second step, after determining the need to switch the transmission protocol, since various candidate transmission protocols have already been activated in step 100 in this embodiment, the cloud computing server and the cloud computing client can seamlessly switch to the new transmission protocol, eliminating the need to reestablish a connection between the two parties. This can be understood as follows: while the connection between the cloud computing server and the cloud computing client remains, both parties switch to using the transmission protocol for subsequent data transmission. In summary, in this embodiment, during the process of establishing a connection between the cloud computing server and the cloud computing client, multiple candidate transmission protocols can be activated simultaneously, rather than specifying a fixed one. Based on this, after a connection is established, the cloud computing server can monitor the scene state parameters corresponding to the cloud computing client to detect changes in the cloud computing client's transmission requirements. Furthermore, the cloud computing server also presets the relationship between scene state parameters and transmission protocols, which serves as the basis for protocol switching decisions. Based on this, the cloud computing server can automatically switch transmission protocols upon detecting changes in the scene state parameters corresponding to the cloud computing client. This allows the server to dynamically switch transmission protocols in response to the cloud computing client's dynamically changing transmission requirements, thereby fully leveraging the respective advantages of different transmission protocols, continuously and stably ensuring the cloud computing client's transmission performance, and improving the user experience. Figure 4 is a schematic diagram of an optional implementation of a transmission protocol switching method provided in an exemplary embodiment of the present disclosure. Referring to Figure 4, this embodiment provides several exemplary scene state parameters: scene type and user preference.Based on this, referring to Figure 4 , after establishing a connection with a cloud computer client, the cloud computer server can monitor the scene type corresponding to the cloud computer client and monitor the user preferences corresponding to the cloud computer client. The following describes in detail the two exemplary scene state parameter monitoring schemes described above. Regarding scene types, as mentioned above, scene types in this embodiment may include at least audio and video scenes. It should be understood that in actual applications, neither the cloud computer server nor the cloud computer client directly annotates the scene type. Therefore, the cloud computer server cannot directly obtain the scene type corresponding to the cloud computer client. Therefore, this embodiment proposes that the cloud computer server can indirectly detect the scene type corresponding to the cloud computer client by monitoring other parameters or states. To this end, in this embodiment, referring to Figure 4 , a scene detection component can be deployed in the aforementioned protocol decision device to detect the scene type corresponding to the cloud computer client. Based on this, the protocol decision device can obtain the scene type corresponding to the cloud computer client from the scene detection component as a scene state parameter. Following the previous description, the audio and video scenarios in this embodiment can include subtypes such as audio and video call scenarios and audio and video playback scenarios. Therefore, this embodiment proposes using a scene detection module to detect various subtypes from multiple perspectives. Several exemplary detection schemes are provided below: In one exemplary aspect, applications using a microphone device can be monitored in a cloud computing instance corresponding to a cloud computing client. If an audio and video call application is detected among the detected applications, the scenario type corresponding to the cloud computing client is determined to be an audio and video scenario. A cloud computing instance refers to a service instance on a cloud computing server that provides cloud computing services to a cloud computing client, also known as a guest client. In actual applications, the usage of the microphone device in the guest OS of the cloud computing instance corresponding to the cloud computing client can be monitored to identify applications using the microphone device. Applications here can be understood as applications running on the cloud computing server, such as players, browsers, instant messaging applications, and so on. In this embodiment, information such as the names of audio and video call applications can be pre-collected. This allows for quick and accurate detection of audio call applications among applications using a microphone device. Examples of audio call applications include various instant messaging applications, and specific application names are not provided here.In another exemplary aspect, the attribute information of data sent to a cloud computer client can be monitored, and the following indicators can be used to determine whether the scene is an audio or video playback scenario: the presence of audio data; the data frame rate exceeding a specified frame rate threshold; the number of frames in the screenshot where the coverage of the changed area exceeds a specified coverage threshold and meets a preset standard. If the attribute information of the data sent by the cloud computer client meets one or more of these indicators, the cloud computer client can be determined to be in an audio or video playback scenario, and further, the scene type corresponding to the cloud computer client can be determined to be an audio or video scenario. The specified frame rate threshold, specified coverage threshold, and preset standard involved can all be set according to actual needs. For example, the specified frame rate threshold can be set to 25 FPS, the specified coverage threshold can be set to 90%, and the preset standard can be set to a frame count exceeding 5-20 frames, although this embodiment is not limited to these. In this embodiment, other aspects can also be used to detect whether the cloud computer client is in other subtypes of the audio or video scenario, not limited to the exemplary aspects provided above, and further examples are not provided here. Furthermore, it should be understood that the scene types in this embodiment may include not only the aforementioned audio and video scenes, but also other types. In this embodiment, the number of scene types required and the names of the various types can be determined based on the granularity of scene type segmentation required in the aforementioned association relationship. Optionally, in this embodiment, scene types can be divided into audio and video scenes and non-audio and video scenes. Of course, scene types can also be divided into audio and video scenes, office scenes, and artificial intelligence scenes, etc. Again, as mentioned above, the scene types categorized in this embodiment are not limited and can be divided according to actual needs. Regarding user preferences, as mentioned above, user preferences in this embodiment may include at least image quality priority and smoothness priority. Image quality priority can be understood as prioritizing image quality with lower requirements for smoothness; smoothness priority can be understood as prioritizing smoothness with lower requirements for image / audio quality. During research, the inventors discovered that user preferences are typically configured by the user or administrator of the cloud computing client through configuration operations. This configuration operation typically triggers the cloud computing client to send a preference configuration message to the cloud computing server. Based on this, referring to Figure 4 , in this embodiment, upon receiving a preference configuration message from a cloud computing client, the cloud computing server can parse the preference configuration message to extract the user preferences, which are then used as the user preferences corresponding to the monitored cloud computing client. It should be understood that the aforementioned preference types are merely exemplary, and the user preferences in this embodiment may also include other preference types, and are not limited to these. Further examples are not provided here.Furthermore, referring to FIG4 , in addition to monitoring the scenario status parameters corresponding to the cloud computer client, the cloud computer server can also monitor the connection status between the cloud computer client and the cloud computer client under various selected transmission protocols. In practical applications, heartbeat detection can be used to detect whether the connections under various selected transmission protocols are active. If some connections are detected to be disconnected, the aforementioned identity verification process can be re-executed to re-establish the connections under the relevant selected transmission protocols. This ensures seamless switching of transmission protocols and avoids the problem of discovering that the corresponding connection has been disconnected after the transmission protocol switch is determined, resulting in the need to re-establish the connection. In addition, if the protocol decision device detects that the connection under the transmission protocol to be switched to is disconnected after determining that the transmission protocol switch is necessary, the transmission protocol switch can be stopped, that is, the existing transmission protocol can be maintained to avoid transmission lag caused by poor connection under the transmission protocol. Furthermore, referring to FIG4 , the cloud computer server can also monitor the protocol control mode corresponding to the cloud computer client. This embodiment proposes that multiple protocol control modes can be supported, such as TCP mode, QUIC mode, RTC mode, and automatic mode. The transmission protocol switching solution provided in this embodiment is supported in automatic mode. Furthermore, in this embodiment, the control platform provided by the control node in Figure 3 supports configuration of the protocol control mode by administrators and other staff members of the cloud computer client. The cloud computer server can obtain the corresponding protocol control mode of the cloud computer client from the control node. Based on this, in this embodiment, if the cloud computer server detects that the protocol control mode corresponding to the cloud computer client is automatic, it can execute the transmission protocol switching method provided in this embodiment. In other modes, it can execute a traditional solution instead of the transmission protocol switching solution provided in this embodiment. In other words, the protocol control mode has the highest priority in this embodiment and determines whether to initiate the transmission protocol switching method provided in this embodiment. In summary, in this embodiment, various implementation methods can be used to monitor the scene state parameters corresponding to the cloud computer client. Changes in the scene state parameters corresponding to the cloud computer client can also be detected in a timely manner. During research, the inventors discovered that because the scene state parameters include parameters under multiple state dimensions, changes in parameters under any state dimension will result in the scene state parameters being determined to have changed. However, in this embodiment, the association between the scene state parameters and the transmission protocols is static. Therefore, no matter which state dimension of the scene state parameters changes and causes the scene state parameters to change, in this embodiment, whether the transmission protocol needs to be switched is determined based on the overall state of the parameter group corresponding to the scene state parameters.Following the two exemplary state dimensions included in the scene state parameters provided in this embodiment: scene type and user preference, in one exemplary scenario: if the cloud computer client is in the first scene type and detects that the cloud computer client's user preference has switched to the first preference, the first transmission protocol associated with the first scene type and the first preference is switched to. Alternatively, if the cloud computer client is in the first preference and detects that the scene type corresponding to the cloud computer client has switched to the first scene type, the first transmission protocol is switched to. That is, in this embodiment, whether the scene type changes or the user preference changes, if the parameter group formed by the scene type and user preference is associated with a new transmission protocol, a transmission protocol switch will be triggered. Optionally, the first scene type can be an audio or video scene, the first preference can prioritize smoothness, and the first transmission protocol can be RTC. That is, in the aforementioned association, the transmission protocol associated with the scene state parameter [Audio or video scene, smoothness prioritized] is RTC. Whether a user preference switch event occurs in an audio / video scenario, or a scene type switch event occurs in a scenario where the user preference prioritizes smoothness, if the resulting scene state parameter changes to [Audio / Video Scenario, Smoothness Prioritized], a switch to the RTC transport protocol will be triggered. In this embodiment, after switching to the first transport protocol, the cloud computing server continues to execute the aforementioned monitoring logic. If it detects that the cloud computing client has switched from an audio / video scenario to another scenario type, or if it detects that the user preference of the cloud computing client has switched from smoothness priority to another preference, it switches from the first transport protocol to the second transport protocol associated with the scene type and preference type currently associated with the cloud computing client. The second transport protocol to be selected is determined based on a pre-configured association in the cloud computing server. In one optional design, the selected transport protocols may be RTC or QUIC. In the association, the scene state parameter [Audio / Video Scenario, Smoothness Prioritized] may be associated with RTC (the first transport protocol); all other scene state parameters may be associated with QUIC (the second transport protocol).On this basis, after switching to RTC, if the cloud PC client's scene type switches to a non-audio / video scene, or the cloud PC client's user preference switches to prioritizing image quality, then the switch from RTC to QUIC can be made. It should be understood that if the cloud PC client's scene type switches to a non-audio / video scene, regardless of whether the cloud PC client's user preference switches to prioritizing image quality, a switch to the second transmission protocol, QUIC, will be triggered. Similarly, if the cloud PC client's scene type switches to a non-audio / video scene, regardless of whether the cloud PC client's scene type switches to a non-audio / video scene, a switch to the second transmission protocol, QUIC, will be triggered. It is worth noting that the above-described association design scheme is merely illustrative and this embodiment is not limited thereto. More detailed and complex associations can be designed, and further examples are not provided here. Regardless of the association, in this embodiment, the cloud PC server uses the changed scene state parameters as the basis for decision-making. When a switching event occurs in any state dimension of the scene state parameters, resulting in a change in the transmission protocol associated with the scene state parameter, the cloud PC server can be triggered to switch the transmission protocol. Furthermore, during research, the inventors discovered that, as mentioned above, multiple transmission channels are typically used between the cloud computing client and the cloud computing server to facilitate transmission tasks of varying dimensions. For example, the Main_channel in the previous example is primarily used for connection processing, while the Playback channel is primarily used to transmit audio data generated by the cloud computing server. Based on this, this embodiment proposes that the cloud computing server can control transmission protocol switching only within designated transmission channels. In other words, the cloud computing server can dynamically switch transmission protocols only within certain transmission channels, while ignoring the transmission protocols within other transmission channels. Optionally, the designated transmission channels can be those used to transmit audio and video data. For example, the transmission channels used to transmit desktop image data, audio data generated by the cloud computing server, and audio recording data from the cloud computing client, as described above, can remain unchanged according to the transmission protocols used in traditional solutions and remain unaffected by the transmission protocol switching solution provided in this embodiment. The following describes the transmission protocol switching validation process under several specified exemplary transmission channels.Regarding the transmission channel for image data transmission: If a cloud computer server needs to send image frames to a cloud computer client, it can send a protocol switching notification to the cloud computer client via the transmission channel for image data transmission, triggering the cloud computer client to switch the transmission protocol for the transmission channel used for image data transmission. Subsequently, image frames carrying frame numbers can be sent to the cloud computer client according to the switched transmission protocol. The first frame sent after the transmission protocol switch also carries key frame data, triggering the cloud computer client to discard unplayed image frames with frame numbers less than the first frame and decode the first frame based on the key frame data. Figure 5 is a logical diagram of the transmission protocol switching process for a transmission channel used for image data transmission, provided by an exemplary embodiment of the present disclosure. Referring to Figure 5, the transmission channel used to transmit image data is described as a Display Channel. The cloud computing server (shown as the server in Figure 5) can send image frames (shown as Video Frames in Figure 5) to the cloud computing client (shown as the Client in Figure 5) via this transmission channel. It should be understood that in cloud computing technology, the cloud computing server generates image frames by taking screenshots, transmitting the audio and video playback screens on the cloud computing server to the cloud computing client for rendering and display. Referring to Figure 5, before switching transmission protocols, the transmission protocol used between the cloud computing client and the cloud computing server under the Display Channel was QUIC. The cloud computing server sent a Video Frame with frame number N-1 to the cloud computing client. When frame number N was generated but not yet sent to the cloud computing client, a transmission protocol switch occurred, and the switched transmission protocol became RTCo. Referring to Figure 5, the cloud computing server sent a protocol switch notification to the cloud computing client, and the cloud computing client switched to using RTC to decode subsequently received image frames. After switching the transmission protocol, the first frame sent by the cloud PC server to the cloud PC client is frame number N+1, which carries key frame data for decoding. Therefore, the cloud PC client receives frame number N+1 according to the RTC and successfully completes decoding. However, frame number N arrives at the cloud PC client only after the transmission protocol switch is complete. Therefore, the cloud PC client discards frame number N. As can be seen, in this embodiment, when a transmission protocol switch occurs in the transmission channel used to transmit image data, the cloud PC client is allowed to drop frames to avoid decoding errors or reception errors. However, the order of the image frames is ensured to ensure correct rendering.Regarding the transmission channel for audio data transmission: If a cloud computing server needs to send audio data to a cloud computing client, it sends a protocol switch notification to the cloud computing client via the transmission channel used for audio data transmission. This triggers the cloud computing client to restart its local audio playback device and switch the transmission protocol for the transmission channel used for audio data transmission. The audio data here can be understood as audio data generated by the cloud computing server. After receiving the audio data, the cloud computing client must use its local audio playback device to play it. Figure 6 is a logical diagram of the transmission protocol switch validation process for a transmission channel used for audio data transmission, provided by an exemplary embodiment of the present disclosure. Referring to Figure 6, before switching the transmission protocol, the cloud computing server (shown as "server" in Figure 6) can send audio data (shown as "PLAYBACK DATA" in Figure 6) to the cloud computing client (shown as "Client" in Figure 6) via the transmission channel. oAfterwards, the cloud computer server detects that the user preference corresponding to the cloud computer client has switched from image quality priority to smoothness priority, and thus determines that the transmission protocol needs to be switched. Referring to Figure 6, the cloud computer server sends a protocol switching notification to the cloud computer client (shown as MODE CHANGE, PLAYBACK STOP, and PLAYBACK START in Figure 6). Under this trigger, the cloud computer client switches the transmission protocol and restarts its local audio playback device (the example in Figure 6 is MediaPlayer). The cloud computer server will send subsequent audio data according to the switched transmission protocol (shown as PushAudioFrame in Figure 6). The cloud computer client will receive and decode the audio data according to the switched transmission protocol and play it using its local audio playback device. It should be understood that triggering the cloud PC client to restart its audio playback device is intended to prevent the cloud PC client from continuing to play audio data received but not yet played under the transmission protocol before the switch. By restarting, this unplayed audio data is discarded, allowing the cloud PC client to quickly switch to playing audio data received under the transmission protocol after the switch, thereby improving playback quality. Furthermore, referring to Figure 6, if audio data sent by the cloud PC server after the transmission protocol switch arrives at the cloud PC client before the protocol switch notification, the cloud PC client can cache this earlier-arrived audio data in a designated location (NetEQ in the example of Figure 6). After the cloud PC client completes the audio playback device restart, it can proactively retrieve and play this earlier-arrived audio data. This effectively prevents audio data frame loss in the transmission protocol after the switch. Regarding the transmission channel for transmitting recorded data: If the cloud computing server needs to receive recorded data provided by the cloud computing client, it will send a protocol switching notification to the cloud computing client via the transmission channel used for transmitting recorded data, triggering the cloud computing client to restart its local recording device and switch the transmission protocol for the transmission channel used for transmitting recorded data. Figure 7 is a logical diagram of the transmission protocol switching process for a transmission channel used for transmitting recorded data, provided in an exemplary embodiment of the present disclosure.Referring to FIG7 , before switching the transmission protocol, the cloud computer client (shown as Client in FIG7 ) can send recording data (shown as RECORD_DATA in FIG7 ) to the cloud computer server (shown as server in FIG7 ) based on the transmission channel. Afterwards, the cloud computer server detects that the user preference corresponding to the cloud computer client has switched from image quality priority to smoothness priority, thereby determining that the transmission protocol needs to be switched; Referring to FIG7 , the cloud computer server sends a protocol switching notification to the cloud computer client (shown as MODE CHANGE, RECORD STOP, and REC ORD START in FIG7 ). Under this trigger, the cloud computer client switches the transmission protocol and restarts its local recording device (the example in FIG7 is MediaRecorder). The cloud computer client will send subsequent recording data (shown as PushAudioFrame in FIG7 ) according to the switched transmission protocol, and the cloud computer server will receive and decode the recording data according to the switched transmission protocol. Moreover, as shown in FIG7 , after switching the transmission protocol, The cloud computing server will reject recorded data sent using the pre-switched transmission protocol. In summary, in this embodiment, the cloud computing server can intelligently identify the scenario type corresponding to the cloud computing client and scenario state parameters such as user preferences to determine whether a transmission protocol switch is necessary. Furthermore, the transmission protocol switch can be performed within a designated transmission channel without interfering with other transmission channels. Furthermore, within different designated transmission channels, protocol switch notifications can be used to trigger the cloud computing client to synchronously switch transmission protocols and perform other necessary preparatory work, ensuring that the user is unaware of the transmission protocol switch process. This makes transmission protocol switching more timely and efficient, thereby effectively improving transmission performance. It should be noted that while some of the processes described in the above embodiments and accompanying figures include multiple operations that appear in a specific order, it should be understood that these operations may be executed in a different order than those presented herein or in parallel. Operation sequence numbers, such as 101 and 102, are merely used to distinguish between different operations and do not represent any specific execution order. Furthermore, these processes may include more or fewer operations, and these operations may be performed sequentially or in parallel. It should be noted that terms such as "first" and "second" are used herein to distinguish between different scenario types and user preferences, and do not represent a sequential order. Figure 8 is a schematic diagram of the structure of a cloud computing server provided in another exemplary embodiment of the present disclosure. As shown in Figure 8, the cloud computing server may include a memory 80, a processor 81, and a communication component 82.The processor 81 is coupled to the memory 80 and the communication component 82 and is configured to execute a computer program in the memory 80 to: enable multiple transmission protocols to be selected during the process of establishing a connection with a cloud computer client; monitor scene state parameters corresponding to the cloud computer client after the connection is established; and control transmission protocol switching based on the association between the scene state parameters and the transmission protocol when the scene state parameters corresponding to the cloud computer client change. In an optional embodiment, when enabling multiple transmission protocols to be selected during the process of establishing a connection with a cloud computer client, the processor 81 may specifically be configured to: establish various transmission channels required for data transmission with the cloud computer client; and, based on the transmission channel used for processing the connection, perform identity mutual recognition with the cloud computer client under each of the multiple transmission protocols to enable the multiple transmission protocols to be selected. In an optional embodiment, when the processor 81 completes identity mutualization with the cloud computer client under the multiple selected transmission protocols based on the transmission channel used for processing the connection, the processor 81 may specifically be configured to: create different protocol ports for different selected transmission protocols; carry the corresponding protocol ports in identity authentication messages; exchange identity authentication messages with the cloud computer client under the multiple selected transmission protocols based on the transmission channel used for processing the connection, and complete identity mutualization and protocol port agreement with the cloud computer client under the multiple selected transmission protocols. In an optional embodiment, when the processor 81 monitors the scene status parameters corresponding to the cloud computer client, the processor may specifically be configured to: monitor the scene type corresponding to the cloud computer client; and monitor the user preferences corresponding to the cloud computer client. In an optional embodiment, the scene type includes an audio and video scene. When monitoring the scene type corresponding to the cloud computer client, the processor 81 may specifically be configured to: monitor applications in the cloud computer instance corresponding to the cloud computer client that are using a microphone device; and if the monitored applications include audio and video call applications, determine that the scene type corresponding to the cloud computer client is an audio and video scene. In an optional embodiment, the processor 81 may also be used to: monitor attribute information of data sent to the cloud computer client; if the sent data contains audio data, the data frame rate exceeds a specified frame rate threshold, and / or the number of frames in which the coverage of the changed area in the screenshot exceeds a specified coverage threshold and reaches a preset standard, then determine that the scene type corresponding to the cloud computer client is an audio and video scene.In an optional embodiment, the user preferences include prioritizing image quality and smoothness. When monitoring the user preferences corresponding to the cloud computer client, the processor 81 may specifically be configured to: upon receiving a preference configuration message sent by the cloud computer client, parse the user preferences from the preference configuration message and use them as the monitored user preferences corresponding to the cloud computer client. In an optional embodiment, when the scene state parameters corresponding to the cloud computer client change, the processor 81 may control the switching of transmission protocols based on the association between the scene state parameters and the transmission protocols. Specifically, the processor 81 may be configured to: if the cloud computer client is in a first scene type and the user preference of the cloud computer client is detected to have switched to the first preference, switch to using a first transmission protocol associated with the first scene type and the first preference; or if the cloud computer client is in the first preference and the scene type corresponding to the cloud computer client is detected to have switched to the first scene type, switch to using the first transmission protocol. In an optional embodiment, if the first scene type is an audio / video scene and the first preference prioritizes smoothness, then the first transmission protocol uses RTC. The processor 81 may further be configured to: after switching to the first transmission protocol, if it is detected that the cloud computer client switches from the audio / video scene type to another scene type, or if it is detected that the user preference of the cloud computer client switches from the smoothness priority to another preference, then switch from the first transmission protocol to a second transmission protocol associated with the scene type and preference type currently corresponding to the cloud computer client. In an optional embodiment, when switching from the first transmission protocol to the second transmission protocol associated with the scene type and preference type to which the cloud computer client has switched, the processor 81 may be configured to: if the scene type of the cloud computer client switches to a non-audio / video scene or the user preference of the cloud computer client switches to image quality priority, then use QUICo as the second transmission protocol. In an optional embodiment, when controlling the transmission protocol switching, the processor 81 may be configured to: control the transmission protocol switching in a transmission channel used to transmit audio / video data, wherein the transmission protocols used in other transmission channels remain unchanged.In an optional embodiment, after switching the transmission protocol, the processor 81 can also be used to: if it is necessary to send audio data to the cloud computer client, then send a protocol switching notification to the cloud computer client through the transmission channel used to transmit audio data, so as to trigger the cloud computer client to restart its local audio playback device and switch the transmission protocol under the transmission channel used to transmit audio data; if it is necessary to receive recording data provided by the cloud computer client, then send a protocol switching notification to the cloud computer client through the transmission channel used to transmit recording data, so as to trigger the cloud computer client to restart its local recording device and switch the transmission protocol under the transmission channel used to transmit recording data. In an optional embodiment, the processor 81 may also be configured to: if image frames need to be sent to the cloud computer client, send a protocol switch notification to the cloud computer client via the transmission channel used to transmit image data, thereby triggering the cloud computer client to switch the transmission protocol of the transmission channel used to transmit image data; and send image frames carrying frame numbers to the cloud computer client according to the switched transmission protocol. The first frame sent after the transmission protocol switch also carries key frame data, thereby triggering the cloud computer client to discard unplayed image frames with frame numbers less than the first frame and decode the first frame based on the key frame data. Furthermore, as shown in FIG8 , the cloud computer server also includes other components, such as a power supply component 83. FIG8 only schematically illustrates some components and does not mean that the cloud computer server only includes the components shown in FIG8 . It is worth noting that the technical details of the above-mentioned cloud computer server embodiments can be found in the relevant descriptions of the aforementioned method embodiments. To save space, they will not be repeated here, but this should not affect the scope of protection of the present disclosure. Accordingly, embodiments of the present disclosure also provide a computer-readable storage medium storing a computer program. When executed, the computer program can implement the steps performed in the above-described method embodiments. The memory in FIG. 8 is used to store the computer program and can be configured to store various other data to support operations on the computing platform. Examples of such data include instructions for any application or method operating on the computing platform, contact data, phone book data, messages, images, videos, etc. 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 memory, flash memory, magnetic disk, or optical disk.The communication component in FIG8 is configured to facilitate wired or wireless communication between the device in which the communication component resides and other devices. The device in which the communication component resides can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G, or other mobile communication networks, or a combination 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. In one exemplary embodiment, the communication component also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID), infrared data association (IrDA), ultra-wideband (UWB), Bluetooth (BT), or other technologies. The power supply component in FIG8 provides power to various components of the device in which the power supply component 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 the power supply component resides. Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, such that the instructions, executed by the processor of the computer or other programmable data processing device, produce means for implementing the functions specified in one or more processes in the flowcharts and / or one or more blocks in the block diagrams. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in one or more processes in the flowchart and / or one or more blocks in the block diagram.These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing the computer or other programmable device to execute a series of operational steps to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device with steps for implementing the functions specified in one or more flow charts and / or one or more blocks in a block diagram. It should also be noted that the terms "comprise," "include," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a..." does not preclude the presence of additional identical elements in the process, method, commodity, or apparatus comprising the element. 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, storage, and display) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. The collection, use, and processing of 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 reject. The above description is merely an embodiment of this disclosure and is not intended to limit it. Those skilled in the art will appreciate that various modifications and variations of this disclosure are possible. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this disclosure are intended to be included within the scope of protection of this disclosure. Industrial Applicability: When establishing a connection between a cloud computing server and a cloud computing client, multiple transmission protocols can be enabled simultaneously between the two parties, rather than specifying a fixed one. Based on this, after the two parties establish a connection, the cloud computer server can monitor the scene status parameters corresponding to the cloud computer client to perceive changes in the cloud computer client's transmission requirements. In addition, the cloud computer server also presets the relationship between scene status parameters and transmission protocols as the decision basis for protocol switching. On this basis, the cloud computer server can automatically switch the transmission protocol when it detects changes in the scene status parameters corresponding to the cloud computer client. The transmission protocol is dynamically switched according to the dynamic transmission requirements of the cloud computer client, thereby fully leveraging the respective advantages of different transmission protocols, continuously and stably ensuring the transmission performance of the cloud computer, and improving the user experience.

Claims

Claims 1. A transmission protocol switching method, applicable to a cloud computer server, the method comprising: During the process of establishing a connection with the cloud computer client, enable multiple candidate transport protocols; After establishing a connection with the cloud computer client, monitor the scene status parameters corresponding to the cloud computer client; in the case where the scene status parameters corresponding to the cloud computer client change, based on the association relationship between the scene status parameters and the transport protocol, control the transport protocol to switch.

2. The method according to claim 1, wherein During the process of establishing a connection with the cloud computer client, enable multiple candidate transport protocols, including: establishing various transport channels required for data transmission between the cloud computer client; based on the transport channel used to process the connection, complete identity mutual authentication with the cloud computer client under the multiple candidate transport protocols to enable the multiple candidate transport protocols.

3. The method according to claim 2, wherein Based on the transport channel used to process the connection, complete identity mutual authentication with the cloud computer client under the multiple candidate transport protocols, including: creating different protocol ports for different candidate transport protocols; carrying the corresponding protocol ports in the identity authentication message; based on the transport channel used to process the connection, interact with the cloud computer client with the identity authentication message under the multiple candidate transport protocols, and complete identity mutual authentication and protocol port agreement with the cloud computer client under the multiple candidate transport protocols.

4. The method according to claim 1, wherein Monitor the scene status parameters corresponding to the cloud computer client, including: monitoring the scene type corresponding to the cloud computer client; monitoring the user preference corresponding to the cloud computer client.

5. The method according to claim 4, wherein The scene type includes an audio-video scene. Monitoring the scene type corresponding to the cloud computer client includes: monitoring the application that is using the microphone device in the cloud computer instance corresponding to the cloud computer client; if there is an audio-video call application among the monitored applications, determine that the scene type corresponding to the cloud computer client is an audio-video scene.

6. The method according to claim 5, wherein, It also includes: Monitoring the attribute information of the data sent to the cloud computer client; If there is audio data in the sent data, the data frame rate exceeds the specified frame rate threshold and / or the number of frames with the change area coverage rate in the screenshot exceeding the specified coverage rate threshold reaches the preset standard, then determine that the scene type corresponding to the cloud computer client is an audio-video scene.

7. The method according to claim 4, wherein The user preference includes picture quality priority and smoothness priority. Monitoring the user preference corresponding to the cloud computer client includes: After receiving the preference configuration message sent by the cloud computer client, parse the user preference from the preference configuration message as the monitored user preference corresponding to the cloud computer client.

8. The method according to claim 4, wherein When the scenario state parameter corresponding to the cloud computer client changes, based on the association relationship between the scenario state parameter and the transmission protocol, control the switching of the transmission protocol, including: if the cloud computer client is in the first scenario type and it is detected that the user preference of the cloud computer client switches to the first preference, then switch to using the first transmission protocol associated with the first scenario type and the first preference; or, if the cloud computer client is in the first preference and it is detected that the scenario type corresponding to the cloud computer client switches to the first scenario type, then switch to using the first transmission protocol.

9. The method according to claim 8, wherein If the first scenario type is an audio / video scenario and the first preference is smoothness first, then the first transmission protocol uses RTC. The method further includes: after switching to the first transmission protocol, if it is detected that the cloud computer client switches from the audio / video type scenario to other scenario types, or it is detected that the user preference of the cloud computer client switches from smoothness first to other preferences, then switch from the first transmission protocol to the second transmission protocol associated with the scenario type and preference type currently corresponding to the cloud computer client.

10. The method according to claim 9, wherein Switching from the first transmission protocol to the second transmission protocol associated with the scenario type and preference type to which the cloud computer client switches includes: if the scenario type of the cloud computer client switches to a non-audio / video scenario or the user preference of the cloud computer client switches to picture quality first, then the second transmission protocol uses QUIC.

11. The method according to claim 2, wherein, Controlling the switching of the transmission protocol includes: controlling the switching of the transmission protocol under the transmission channel for transmitting audio / video related data; where the transmission protocols used under other transmission channels remain unchanged.

12. The method according to claim 1, wherein After switching the transmission protocol, the method further includes: if it is necessary to send audio data to the cloud computer client, then send a protocol switching notification to the cloud computer client through the transmission channel for transmitting audio data, so as to trigger the cloud computer client to restart its local audio playback device and switch the transmission protocol under the transmission channel for transmitting audio data; if it is necessary to receive the recording data provided by the cloud computer client, then send a protocol switching notification to the cloud computer client through the transmission channel for transmitting recording data, so as to trigger the cloud computer client to restart its local recording device and switch the transmission protocol under the transmission channel for transmitting recording data.

13. The method according to claim 12, wherein The method further includes: if it is necessary to send an image frame to the cloud computer client, sending a protocol switching notification to the cloud computer client through a transmission channel for transmitting image data, so as to trigger the cloud computer client to switch the transmission protocol under the transmission channel for transmitting image data; sending an image frame with a frame number to the cloud computer client according to the switched transmission protocol, wherein the first frame sent after switching the transmission protocol also carries key frame data, so as to trigger the cloud computer client to discard the unplayed image frames with frame numbers smaller than the first frame and decode the first frame based on the key frame data.

14. A cloud computer server, comprising a memory, a processor and a communication component; the memory is used for storing one or more computer instructions; the processor is coupled with the memory and the communication component and is used for executing the one or more computer instructions to execute the transmission protocol switching method according to any one of claims 1-13.

15. A computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to execute the transmission protocol switching method according to any one of claims 1-13.

Images