Data transmission method and electronic device

Abstract

Embodiments of the present application provide a data transmission method and an electronic device. The method comprises: a server receives a first message sent by a client, the first message comprising indication information, and the indication information being used for indicating the connection type of the first message; on the basis of the indication information, the server sends, by means of a transmission link, data carried in the first message to logic modules matching the connection type, wherein a plurality of different logic modules use the same transmission link.

Description

Data transmission methods and electronic devices

[0001] Cross-references

[0002] This application claims priority to Chinese Patent Application No. 202410779716X, filed on June 17, 2024, entitled "Data Transmission Method and Electronic Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a data transmission method and an electronic device. Background Technology

[0004] Desktop protocols mainly include virtual machine desktop protocols and host desktop protocols. The desktop protocol channels in related technologies are multi-channel, with each channel responsible for an independent logical module. These channels include, for example, the main channel, display channel, disk redirection channel, and file transfer channel. Because multiple different channels operate independently, it is not conducive to unified management of data transmission. Summary of the Invention

[0005] The purpose of this application is to provide a data transmission method and electronic device that can at least solve the problem in related technologies where different channels are independent of each other, which is not conducive to unified management of data transmission.

[0006] In a first aspect, embodiments of this application provide a data transmission method, comprising: a server receiving a first message sent by a client, the first message including indication information, the indication information being used to indicate the connection type of the first message; the server, based on the indication information, sending data carried in the first message to a logical module matching the connection type via a transmission link; wherein multiple different logical modules use the same transmission link.

[0007] In a second aspect, embodiments of this application provide an electronic device, including at least one processor; and a memory storing computer-executable instructions, which, when executed, use the at least one processor to perform the steps of the method described in the first aspect.

[0008] Thirdly, embodiments of this application provide a computer-readable storage medium storing at least one computer program that, when executed by a processor, implements the steps of the method described in the first aspect. Attached Figure Description

[0009] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0010] Figure 1 shows a flowchart of a data transmission method provided in an embodiment of this application;

[0011] Figure 2 shows a schematic diagram of the application architecture of the data transmission method provided in an embodiment of this application;

[0012] Figure 3 shows a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0013] Figure 4 is a schematic diagram of the hardware structure of an electronic device that performs the data transmission method provided in the embodiments of this application. Detailed Implementation

[0014] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0015] In the field of cloud desktop technology, related technologies are divided into multiple channels, such as protocol channels (e.g., main channel, display channel, keyboard and mouse channel, etc.) and data channels (e.g., out-of-band video channel, USB redirection channel, disk redirection channel, file transfer channel, etc.). Each channel is responsible for a specific function. Because multiple different channels are independent of each other, it is not conducive to unified management of data transmission. The embodiments of this application mainly combine the data from multiple channels into a single transmission link for transmission. By encapsulating connection type information in the messages transmitted between the client and the server, and adding tag information, different connection types of data can be distinguished, and messages can be forwarded to different logical modules. By adopting the technical means of unifying the transmission link, it is beneficial to manage the transmission of data of different connection types, such as priority management and bandwidth management; at the same time, unifying the transmission links between the server and the client can save the link resources of intermediate gateway network elements.

[0016] Figure 1 illustrates a flowchart of a data transmission method provided in an embodiment of this application. This method can be executed by a server; in other words, it can be executed by software or hardware installed on the server. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster. As shown in Figure 1, the method may include the following steps.

[0017] S102: The server receives a first message sent by the client. The first message includes indication information, which is used to indicate the connection type of the first message.

[0018] In one embodiment, both the client and server include proxy modules, as shown in Figure 2. The client's proxy module may include, for example, a proxy module, and the server's (virtual machine, VM, or host) proxy module may include, for example, a tunnel module. The server can receive the first message sent by the client's proxy through the tunnel.

[0019] In one embodiment, a transport link exists between the client and the server, such as a Transport Control Protocol (TCP) link or a User Datagram Protocol (UDP) link. Messages between the client and the server (such as the first message and the second message mentioned later) can be transmitted through this transport link. Before S102, the client can also send a request message to the server to establish the aforementioned transport link between the client and the server. By unifying the transport link between the server and the client, link resources of intermediate gateway network elements can be saved.

[0020] In one embodiment, the aforementioned indication information can be encapsulated within the header of the first message. This indication information helps the network-side device determine the connection type of the first message, thereby enabling fine-grained management of data for different connection types. The connection type may include, for example, desktop protocol data, USB redirection data, disk redirection data, video redirection data, display data, keyboard and mouse data, out-of-band video data, and so on. It is understood that different first messages can carry data of different connection types. For example, the first message received by the server at the first moment may carry desktop protocol data; the first message received by the server at the second moment may carry USB redirection data, and so on.

[0021] S104: Based on the indication information, the server sends the data carried in the first message to the logical module that matches the connection type via the transmission link; wherein, multiple different logical modules use the same transmission link.

[0022] It is understood that the aforementioned logic modules can be located either inside or outside the server. The logic module shown in Figure 2 is located inside the server. Typically, corresponding logic modules also exist in the client.

[0023] In one embodiment, multiple different logical modules can have a one-to-one correspondence with data of multiple different connection types. These logical modules are, for example, the desktop protocol (S) module (matched with desktop protocol data), USB redirect (U) module (matched with USB redirect data), disk redirect (D) module (matched with disk redirect data), and video redirect (V) module (matched with video redirect data) shown in Figure 2.

[0024] It is understood that Figure 2 only schematically shows four types of logic modules. In reality, there can be more logic modules of various types, and it is not limited to the four logic modules shown in Figure 2.

[0025] In one embodiment, multiple different logic modules use the same transmission link, or data of multiple connection types are transmitted using the same transmission link, that is, data from multiple channels are merged into the same transmission link for transmission, thereby achieving link merging.

[0026] The data transmission method provided in this application embodiment transmits data of multiple different connection types using the same transmission link and distinguishes them using connection type information. This is beneficial for managing the transmission of data of different connection types, such as priority management and bandwidth management. At the same time, the unified transmission link between the server and the client can save the link resources of intermediate gateway network elements.

[0027] In one embodiment, the first message received by the server may further include transmission policy information; thus, sending the data carried by the first message to the logic module matching the connection type via the transmission link includes: sending the data carried by the first message to the logic module matching the connection type via the transmission link based on the transmission policy information.

[0028] In this embodiment, the transmission strategy information may be located in the message body of the first message. This transmission strategy information is used to indicate the transmission strategy used when transmitting the first message (or the data carried by the first message).

[0029] In one embodiment, the transmission strategy information includes at least one of the following:

[0030] 1) Priority information, such as the priority level of data compared to other connection types. This priority information helps the server determine the transmission priority of the data carried in the first message, enabling transmission management of data from different connection types and improving transmission efficiency.

[0031] 2) Bandwidth information. This bandwidth information allows for the allocation of appropriate transmission bandwidth for the data carried in the first message, which helps improve transmission efficiency and avoids bandwidth waste.

[0032] In one embodiment, the method further includes: the server adding tag information to the first message based on the indication information; wherein the tag information is used to indicate the connection type of the first message, for example, the tag information can be used to determine the identifier (ID) of the virtual channel in the transmission link and determine the connection type (or data type) of the first message; the tag information is also used to determine the transmission strategy of the first message, the transmission strategy including, for example, priority size, bandwidth size, etc.

[0033] In this embodiment, a transmission link exists between the server-side tunnel and the logical module. This transmission link can contain multiple different virtual channels (or logical channels) for transmitting data of different connection types. The data carried by the first message includes protocol data or application data. In this embodiment, separate transmission links can be established for protocol data and application data. For example, protocol data of multiple connection types can be transmitted through one transmission link, while application data of multiple connection types can be transmitted through another transmission link.

[0034] In this embodiment, after receiving the first message, the server can determine the connection type of the first message based on the indication information carried in the first message. The server can add tag information to the first message based on the indication information; for example, it can also add tag information to the corresponding virtual channel used to transmit the data of the first message.

[0035] This embodiment can unify the cloud desktop protocol channel and data channel, and tag the data on the server side. This allows for convenient and effective fine-grained management of different virtual channels, including but not limited to determining the virtual link ID, connection type, priority information, bandwidth information, etc. of the virtual channel. This solution is universal and can save link resources.

[0036] In one embodiment, the data carried by the first message includes protocol data or application data; sending the data carried by the first message to a logic module matching the connection type via a transmission link includes one of the following:

[0037] 1) The protocol data carried in the first message and the tag information are transmitted transparently to the logic module that matches the connection type through the transmission link.

[0038] In this embodiment, for the logical module corresponding to the protocol data, such as the protocol module, the protocol module can usually directly process the message header and tag information. Therefore, after the tunnel and the protocol module establish a transmission link, the message can be transmitted transparently.

[0039] 2) Remove the tag information and the message header of the first message, and send the application data carried in the first message to the logic module that matches the connection type via the transmission link.

[0040] In this embodiment, for other application modules besides the logic module, such as the data module, the data module cannot process message headers and tag information. Therefore, after the tunnel establishes a transmission link with the data module, it strips the message headers and tag information to transmit data.

[0041] This application embodiment can achieve link unification based on cloud desktop protocol and data channels, including a method for unifying the protocol channel and data channel of cloud desktop connection. The client encapsulates the connection type (linktype) in the message header and passes it to the server tunnel. After the server tunnel decapsulates, it identifies the connection type in the message header and tags different virtual channels (or logical channels) to achieve fine-grained management of different logical channels. In particular, it involves link unification of protocol channels and data channels, including virtual machine desktop protocol and host desktop protocol.

[0042] This application's embodiments are based on the current product's separation of protocol channels and data channels, and the fact that the server-side proxy module tunnel and client-side proxy are only responsible for link aggregation and message forwarding, making it impossible to achieve fine-grained control of different logical channels. It proposes to unify the protocol and data channels into a single link, with all data transmitted through a single transmission link. Then, the server and client distribute the data to different logical modules by tagging different logical channels, thereby achieving fine-grained policy settings from logic to channel. For example, the virtual link ID, data type, priority information, and bandwidth information of the virtual channel can be specified.

[0043] This application's embodiments are applicable to all desktop protocols, regardless of the type of cloud desktop protocol. The main approach involves client-side and server-side desktop protocol channels and data channels, where all channels are aggregated into a unified channel. Different logical channels are tagged and categorized through proxy modules on both the client and server sides, distributing data to different logical modules. This allows for fine-grained control of strategies across different logical modules; for example, virtual link IDs, data types, priority information, and bandwidth information can be specified for virtual channels.

[0044] The above embodiments mainly describe the transmission process of the first uplink message. The following will describe the transmission process of the second downlink message.

[0045] In one embodiment, the method further includes: the server receiving a second message from the logic module through the transmission link; and sending the second message to the client.

[0046] In one embodiment, sending the second message to the client includes: sending the second message to the client based on the transmission policy information of the second message.

[0047] In this embodiment, the transmission strategy information may include at least one of the following: priority information; bandwidth size information, as described in the previous embodiment.

[0048] In this embodiment, the transmission strategy information can be carried by the second message, for example, carried in the message body of the second message; of course, the transmission strategy information can also be locally configured information, for example, the server configures different transmission strategy information locally for downlink messages of different connection types.

[0049] In one embodiment, the method further includes: adding tag information to the second message, the tag information being used to indicate the connection type of the second message, and the tag information being used to determine the transmission strategy of the second message, as described in the preceding embodiments.

[0050] In this embodiment, after the data from the protocol module or the application module is returned to the tunnel, the tunnel can re-encapsulate the message header and mark it with tags, and then return the message carrying the message header and tag information to the client; at the same time, it manages different connection types, such as priority size and bandwidth size control, to complete the desktop connection and data transmission.

[0051] To illustrate the data transmission method provided in the embodiments of this application in detail, several embodiments will be described below.

[0052] This application embodiment is mainly applied to the unification of protocol channel and data channel links during cloud desktop connection usage, as shown in Figure 3. The upper part of Figure 3 shows the protocol data transmission process, and the lower part shows the application data transmission process, which may include the following steps:

[0053] The client sends a connection establishment message (corresponding to the first message in the previous embodiment). The message header encapsulates different connection type information, and the message header includes transmission policy information, which may be logical channel management policy information.

[0054] The client can send a connection establishment message through the created protocol virtual channel 1.

[0055] Before the client sends a connection establishment message, the client and server can also create a TCP / UDP link.

[0056] The server-side tunnel can also establish TCP links with logical modules.

[0057] The server-side tunnel parses the message header to identify the connection type and tags it. It then parses the message body and executes transmission policy control.

[0058] For the upstream data, the server removes the tag and message header, and then forwards it to the corresponding logical module through the created virtual channel. This logical module includes, for example, iceserver, spiceserver, and other applications as shown in Figure 3; where iceserver and spiceserver are protocol modules, and other applications are data modules.

[0059] For downlink data, a corresponding tag is added based on which logical channel the data belongs to. At the same time, the level and proportion of data transmission for different logical channels are controlled according to channel priority. Finally, all data sent to the client is tagged, thereby realizing fine-grained management of different logical channels.

[0060] For virtual machine desktop protocol scenarios that implement desktop connection and data transmission via tunnels within the desktop, network connectivity between the terminal (client) and the server (host or virtual desktop machine) is required. The client establishes a unified virtual channel through a proxy and the server's proxy tunnel. The client sends a connection establishment message containing a header with the connection type (protocol type or data type). The message body carries the priority and bandwidth of different connection types. The service proxy module tunnel within the host and virtual machine parses the message header, identifies different message types, and tags them. Simultaneously, based on the connection type priority and bandwidth, it sends the data to the different logical channels.

[0061] For the protocol module, message headers and tags can be processed directly. Therefore, after the tunnel and the protocol module establish a chain, messages are passed through. For other application modules (data modules), message headers and tags cannot be processed. After the tunnel and the application module establish a chain, message headers and tags are stripped to transmit data.

[0062] Protocol data and application module data are returned to the tunnel. The tunnel re-encapsulates the message headers and tags them, and then returns the message headers and tags to the client. At the same time, it manages different connection types and controls bandwidth priority and size to complete the desktop connection and data transmission.

[0063] This application's embodiments involve, but are not limited to, host desktop protocols and virtual machine desktop protocols. Host desktop protocols require communication between the terminal and the host, establishing a connection between the terminal and the host. The host then communicates with the virtual machine through a host proxy tunnel, spiceserver, or VirtIo. Virtual machine desktop protocols only require direct communication between the terminal and the virtual machine. The terminal directly establishes a connection with the proxy tunnel within the virtual machine, and the tunnel then establishes connections and communications with protocol modules within the virtual machine (establishing main channels, display channels, keyboard and mouse channels, etc.) and other application modules (out-of-band video, USB redirection, disk redirection, file transfer, etc.).

[0064] Example 1: Virtual Desktop Protocol Link Unification

[0065] The client terminal and the desktop virtual machine are connected to the network and can connect to the desktop via the virtual machine desktop protocol. The client creates a virtual channel (including protocol channel and data channel) through a proxy and a desktop virtual machine proxy tunnel. The client proxy encapsulates the connection type in the message header and contains the logical channel management policy in the message body. The service proxy tunnel parses the connection data type, tags it, and then forwards the data to the corresponding protocol module or data module according to the logical channel management policy such as bandwidth priority. The protocol module or data module returns the data to the tunnel, which then encapsulates the message header, tags it, processes the logical channel priority, and returns the data to the client. This achieves desktop connection and data transmission while distinguishing between different channels, facilitating fine-grained management of each logical channel. For example, the virtual link ID, connection type, priority information, and bandwidth size of the virtual channel can be specified.

[0066] Example 2: Unifying Host Desktop Protocol Links

[0067] The host desktop protocol requires the client terminal and the host to be connected to the network. The client establishes a connection with the host proxy tunnel through a proxy. The client message header encapsulates the connection type, and the message body contains the logical channel management policy. The tunnel parses the connection type in the message header, tags each logical channel, and establishes a connection with the Spiceserver. Based on the tags and logical channel management policy, data is sent to the protocol module or application module according to priority and bandwidth. The returned message goes to the tunnel module, where the message header is encapsulated again and tagged. Based on the logical channel management policy, data is sent to the client according to priority and bandwidth.

[0068] Figure 4 illustrates a schematic diagram of the hardware structure of the electronic device implementing the embodiments of this application. Referring to the figure, at the hardware level, the electronic device includes a processor, and may also include an internal bus, a network interface, and a memory. The memory may include RAM, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk storage device. Of course, the electronic device may also include other hardware required for other services.

[0069] The processor, network interface, and memory can be interconnected via an internal bus, which can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only a single bidirectional arrow is used in this diagram, but this does not imply that there is only one bus or one type of bus.

[0070] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0071] The processor reads the corresponding computer program from non-volatile memory into memory and then runs it, forming a device for locating the target user at the logical level. The processor executes the program stored in memory and specifically performs the method disclosed in the embodiments shown in Figures 1-3, and implements the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0072] The methods disclosed in the embodiments shown in Figures 1-3 of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0073] The electronic device can also execute any of the embodiments described in the foregoing method embodiments and achieve the functions and beneficial effects of any of the embodiments described in the foregoing method embodiments, which will not be repeated here.

[0074] Of course, in addition to software implementation, the electronic device of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0075] This application also proposes a computer-readable storage medium that stores at least one computer program. When executed by a processor, the computer program implements the methods disclosed in the embodiments shown in Figures 1-3 and achieves the functions and beneficial effects of the methods described in the foregoing embodiments, which will not be repeated here.

[0076] The computer-readable storage medium may include, but is not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, or key drives, etc.).

[0077] This application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, which, when executed by a computer, implement the following process: the method disclosed in the embodiments shown in Figures 1-3 and achieve the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0078] In summary, the above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0079] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0080] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change 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), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

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

[0082] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

Claims

1. A data transmission method, comprising: The server receives a first message sent by the client. The first message includes indication information, which is used to indicate the connection type of the first message. Based on the indication information, the server sends the data carried in the first message to the logical module that matches the connection type via the transmission link; wherein multiple different logical modules use the same transmission link.

2. The method according to claim 1, wherein, The first message also includes transmission strategy information; The step of sending the data carried in the first message to a logic module matching the connection type via a transmission link includes: Based on the transmission strategy information, the data carried in the first message is sent to the logic module that matches the connection type via the transmission link.

3. The method according to claim 1 or 2, wherein, The method further includes: Based on the indication information, the server adds tag information to the first message; The tag information is used to indicate the connection type of the first message, and the tag information is also used to determine the transmission strategy of the first message.

4. The method according to claim 3, wherein, The data carried in the first message includes protocol data or application data; sending the data carried in the first message to the logic module matching the connection type via the transmission link includes: The protocol data carried in the first message and the tag information are transparently transmitted to the logic module matching the connection type via the transmission link; or, Remove the tag information and the message header of the first message, and send the application data carried in the first message to the logic module that matches the connection type via the transmission link.

5. The method according to any one of claims 1 to 4, wherein, The method further includes: The server receives a second message from the logic module through the transmission link; The second message is sent to the client.

6. The method according to claim 5, wherein, Sending the second message to the client includes: Based on the transmission strategy information of the second message, the second message is sent to the client.

7. The method according to claim 6, wherein, The method further includes: Add tag information to the second message. The tag information is used to indicate the connection type of the second message and to determine the transmission strategy of the second message.

8. The method according to claim 2 or 6, wherein, The transmission strategy information includes at least one of the following: Priority information; Bandwidth information.

9. An electronic device, comprising: At least one processor; as well as A memory storing computer-executable instructions, which, when executed, use the at least one processor to perform the data transfer method according to any one of claims 1-8.

10. A computer-readable medium storing at least one computer program that, when executed by a processor, implements the data transmission method as described in any one of claims 1-8.

Images