Method and device for enhancing cloud-edge communication

By introducing QUIC transmission protocols on the cloud and edge, the problem of cloud-edge communication interruption and connection establishment time in weak network environments is solved, and more efficient communication is achieved.

CN115883629BActive Publication Date: 2025-03-07SHENZHEN COMTOP INFORMATION TECH
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211560825.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-12-07
Publication Date
2025-03-07
Estimated Expiration
2042-12-07

AI Technical Summary

Technical Problem

In a weak network environment, communication between the cloud and the edge is prone to interruption, and frequently establishing connections takes a long time when using the TCP+TLS protocol, resulting in low communication efficiency.

Method used

To support the WebSocket Transport Protocol, QUIC Transport Protocol is introduced to the cloud and edge side, and by editing and loading configuration files on the cloud and edge side, listening and parsing connection requests, switching between the QUIC client and the WebSocket client is achieved to optimize communication.

Benefits of technology

This reduces the occurrence of communication interruptions and shortens the time spent establishing a connection, thereby improving the efficiency of cloud-edge communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115883629B_ABST
    Figure CN115883629B_ABST
Patent Text Reader

Abstract

The present invention discloses a method and device for enhancing cloud-edge communication. The method and device can be applied to a cloud and an edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud edits a configuration file of the cloud. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. Based on the loading result, the cloud monitors the connection request of the edge. When the connection request of the edge is monitored, the cloud parses the connection request to obtain a parsing result. Based on the parsing result, the cloud connects to the edge for communication. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of Internet communication technology, and in particular to a method and device for enhancing cloud-edge communication. Background Art

[0002] With the rapid development of Internet technology, the application scenarios of edge computing technology are increasing, such as industrial Internet, public security and surveillance. Edge computing technology is to deploy the computing tasks required by users at the edge of the network close to the data source, and use edge resources to provide services to users, thereby reducing the amount of data uploaded to the cloud data center and alleviating network bandwidth pressure. The edge computing architecture consists of two parts, namely the cloud and the edge. The cloud is responsible for the distribution of applications and configurations, and the edge is responsible for running edge applications and managing access devices.

[0003] However, in a weak network environment, due to the instability of network connections, communication between the cloud and the edge is prone to interruption. When using the TCP+TLS protocol for communication, it takes a long time to frequently establish connections, resulting in low communication efficiency.

[0004] Therefore, it is particularly important to propose a technical solution on how to enhance cloud-edge communication and thus improve communication efficiency. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a method and device for enhancing cloud-edge communication, which can introduce the QUIC transmission protocol to the cloud and edge that support the WebSocket transmission protocol, reduce the occurrence of communication interruptions, and reduce the time spent on establishing connections, thereby improving communication efficiency.

[0006] In order to solve the above technical problems, the first aspect of the present invention discloses a method for enhancing cloud-edge communication, which is applied to the cloud. The method includes:

[0007] The cloud edits the configuration file of the cloud;

[0008] After the configuration file on the cloud is edited, the cloud loads the configuration file on the cloud to obtain a first loading result;

[0009] The cloud terminal monitors the connection request of the edge terminal based on the first loading result;

[0010] After monitoring the connection request of the edge terminal, the cloud terminal analyzes the connection request and obtains the analysis result;

[0011] The cloud end is connected to the edge end for communication based on the analysis result.

[0012] As an optional implementation manner, in the first aspect of the present invention, before the cloud loads the configuration file of the cloud, it includes:

[0013] The cloud registration message processing function obtains a registration result, wherein the registration result includes a working state of a communication channel between the cloud and the edge;

[0014] The message processing function includes at least one of a heartbeat function, a message loop write function and a channel detection function;

[0015] The heartbeat function is used to periodically detect the heartbeat between the communication channels; the message loop write function is used to instruct the cloud to send messages cyclically; the channel detection function is used to detect abnormal parameters of the communication channel, and the abnormal parameters include at least one of the delay duration of the communication channel and the packet loss rate of the communication channel;

[0016] The cloud loading the configuration file on the cloud to obtain a first loading result includes:

[0017] The cloud loads the configuration file of the cloud based on the registration result to obtain a first loading result.

[0018] As an optional implementation manner, in the first aspect of the present invention, the cloud-side editing of the cloud-side configuration file includes:

[0019] The cloud edits the first startup file of the QUIC client and / or the second startup file of the WebSocket client as the configuration file of the cloud, the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working;

[0020] The first startup file of the QUIC client includes the QUIC client configuration parameters, where the QUIC client configuration parameters include at least one of a first listening port, a first listening address, a first enabled state, and a maximum concurrent write message, where the maximum concurrent write message is used to indicate the maximum number of messages that the QUIC client can process;

[0021] The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second listening port, a second listening address, and a second enabled state;

[0022] Wherein, the cloud connects to the edge end for communication based on the analysis result, including:

[0023] When the state of the QUIC client is the first enabled state, the cloud closes the WebSocket client, and communicates with the edge through the QUIC client based on the parsing result;

[0024] When the state of the WebSocket client is the second enabled state, the cloud closes the QUIC client and communicates with the edge through the WebSocket client based on the parsing result.

[0025] A second aspect of the present invention discloses another method for enhancing cloud-edge communication, which is applied to an edge terminal, and the method includes:

[0026] The edge end loads the configuration file of the edge end to obtain a second loading result;

[0027] The edge end initializes a channel client based on the second loading result, where the channel client includes a QUIC client and / or a WebSocket client, and the channel client is used to perform bidirectional communication with the cloud to form a bidirectional communication channel;

[0028] The edge terminal reads the configuration file of the channel client and sets the node identifier of the edge terminal;

[0029] The edge sends a connection logic request to the cloud based on the node identifier of the edge that has been set, and establishes a connection with the cloud after receiving feedback from the cloud for allowing the establishment of the connection.

[0030] As an optional implementation, in the second aspect of the present invention, the configuration file of the edge terminal is used to instruct the edge terminal to select the QUIC client and / or the WebSocket client to perform two-way communication with the cloud;

[0031] The edge end loads the configuration file of the edge end, including:

[0032] The edge end loads the first startup file of the QUIC client and / or the second startup file of the WebSocket client, where the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working;

[0033] The first startup file of the QUIC client includes the QUIC client configuration parameters, and the QUIC client configuration parameters include at least one of a first formal configuration state, a first port address, and a first enabled state;

[0034] The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second formal configuration state, a second port address, and a second enabled state.

[0035] As an optional implementation manner, in the second aspect of the present invention, after the edge terminal establishes a connection with the cloud, the method further includes:

[0036] The edge end analyzes the communication working state of the currently selected channel client to obtain an analysis result, wherein the analysis result is used to instruct the edge end to perform one of retaining the currently selected channel client and switching to a standby channel client;

[0037] The edge end performs an operation matching the analysis result according to the analysis result;

[0038] The edge end performs an operation matching the analysis result according to the analysis result, including:

[0039] When the analysis result shows that the communication working state of the currently selected channel client meets the preset condition, the edge terminal retains the currently selected channel client;

[0040] When the analysis result shows that the communication working state of the currently selected channel client does not meet the preset condition, the edge end closes the currently selected channel client and switches to the backup channel client, where the backup channel client is one of the QUIC client and the WebSocket client;

[0041] The preset condition includes at least one of a transmission rate and a bit error rate of the channel client currently selected.

[0042] As an optional implementation, in the second aspect of the present invention, the method further includes:

[0043] The edge end encrypts the certificate of the channel client to obtain an encrypted channel client;

[0044] The edge end reads the configuration file of the channel client, including:

[0045] The edge terminal reads the encrypted configuration file of the channel client.

[0046] A third aspect of the present invention discloses a device for enhancing cloud-edge communication, which is applied to a cloud. The device includes:

[0047] An editing module, used to edit the configuration file in the cloud;

[0048] A first loading module, configured to load the configuration file on the cloud after editing the configuration file on the cloud to obtain a first loading result;

[0049] A monitoring module, configured to monitor a connection request from an edge terminal based on the first loading result;

[0050] A parsing module, configured to parse the connection request after monitoring the connection request of the edge end, and obtain a parsing result;

[0051] The first communication module is used to connect to the edge end for communication based on the analysis result.

[0052] As an optional implementation, in the third aspect of the present invention, the device further includes:

[0053] A registration module, used to register a message processing function and obtain a registration result, wherein the registration result includes a working state of a communication channel between the cloud and the edge;

[0054] The message processing function includes at least one of a heartbeat function, a message loop write function and a channel detection function;

[0055] The heartbeat function is used to periodically detect the heartbeat between the communication channels; the message loop write function is used to instruct the cloud to send messages cyclically; the channel detection function is used to detect abnormal parameters of the communication channel, and the abnormal parameters include at least one of the delay duration of the communication channel and the packet loss rate of the communication channel;

[0056] The first loading module loads the configuration file on the cloud, and the specific method of obtaining the first loading result includes:

[0057] The first loading module loads the configuration file in the cloud based on the registration result to obtain a first loading result.

[0058] As an optional implementation, in the third aspect of the present invention, the specific manner in which the editing module edits the configuration file on the cloud includes:

[0059] Editing a first startup file of a QUIC client and / or a second startup file of a WebSocket client as configuration files of the cloud, wherein the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working;

[0060] The first startup file of the QUIC client includes the QUIC client configuration parameters, where the QUIC client configuration parameters include at least one of a first listening port, a first listening address, a first enabled state, and a maximum concurrent write message, where the maximum concurrent write message is used to indicate the maximum number of messages that the QUIC client can process;

[0061] The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second listening port, a second listening address, and a second enabled state;

[0062] The specific manner in which the first communication module connects to the edge end for communication based on the analysis result includes:

[0063] When the state of the QUIC client is the first enabled state, the first communication module closes the WebSocket client, and communicates with the edge end through the QUIC client based on the parsing result;

[0064] When the state of the WebSocket client is the second enabled state, the first communication module closes the QUIC client and communicates with the edge end through the WebSocket client based on the parsing result.

[0065] A fourth aspect of the present invention discloses a device for enhancing cloud-edge communication, which is applied to an edge terminal, and the device includes:

[0066] A second loading module, used to load the configuration file of the edge end to obtain a second loading result;

[0067] An initialization module, configured to initialize a channel client based on the second loading result, wherein the channel client includes a QUIC client and / or a WebSocket client, and the channel client is configured to perform bidirectional communication with the cloud to form a bidirectional communication channel;

[0068] A reading module, used to read the configuration file of the channel client and set the node identifier of the edge end;

[0069] A sending module, used to send a connection logic request to the cloud based on the node identifier of the edge terminal that has been set;

[0070] The second communication module is used to establish a connection with the cloud after receiving feedback sent by the cloud for allowing the connection to be established.

[0071] As an optional implementation, in the fourth aspect of the present invention, the configuration file of the edge terminal is used to instruct the edge terminal to select the QUIC client and / or the WebSocket client to perform two-way communication with the cloud;

[0072] The specific manner in which the second loading module loads the configuration file of the edge terminal includes:

[0073] The second loading module loads the first startup file of the QUIC client and / or the second startup file of the WebSocket client, wherein the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working;

[0074] The first startup file of the QUIC client includes the QUIC client configuration parameters, and the QUIC client configuration parameters include at least one of a first formal configuration state, a first port address, and a first enabled state;

[0075] The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second formal configuration state, a second port address, and a second enabled state.

[0076] As an optional implementation, in the fourth aspect of the present invention, the device further includes:

[0077] An analysis module, configured to analyze the communication working state of the currently selected channel client after the edge terminal establishes a connection with the cloud terminal, and obtain an analysis result, wherein the analysis result is used to instruct the edge terminal to perform one of retaining the currently selected channel client and switching to a standby channel client;

[0078] An execution module, used for executing an operation matching the analysis result according to the analysis result;

[0079] The specific manner in which the execution module executes the operation matching the analysis result according to the analysis result includes:

[0080] When the analysis result shows that the communication working state of the currently selected channel client meets the preset condition, the execution module retains the currently selected channel client;

[0081] When the analysis result shows that the communication working state of the currently selected channel client does not meet the preset condition, the execution module closes the currently selected channel client and switches to the backup channel client, where the backup channel client is one of the QUIC client and the WebSocket client;

[0082] The preset condition includes at least one of a transmission rate and a bit error rate of the channel client currently selected.

[0083] As an optional implementation, in the fourth aspect of the present invention, the device further includes:

[0084] An encryption module, used for encrypting the certificate of the channel client to obtain an encrypted channel client;

[0085] The specific manner in which the reading module reads the configuration file of the channel client includes:

[0086] The reading module reads the encrypted configuration file of the channel client.

[0087] A fifth aspect of the present invention discloses another device for enhancing cloud-edge communication, the device comprising:

[0088] A memory storing executable program code;

[0089] a processor coupled to the memory;

[0090] The processor calls the executable program code stored in the memory to execute the method for enhancing cloud-edge communication disclosed in the first and second aspects of the present invention.

[0091] The sixth aspect of the present invention discloses a computer-storable medium, which stores computer instructions. When the computer instructions are called, they are used to execute the method for enhancing cloud-edge communication disclosed in the first and second aspects of the present invention.

[0092] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0093] In an embodiment of the present invention, a method and device for enhancing cloud-edge communication can be applied to a cloud and an edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud edits a configuration file of the cloud. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. Based on the loading result, the cloud monitors the connection request of the edge. When the connection request of the edge is monitored, the cloud parses the connection request to obtain a parsing result. Based on the parsing result, the cloud connects to the edge for communication. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0095] Figure 1 It is a flowchart of a method for enhancing cloud-edge communication disclosed in an embodiment of the present invention;

[0096] Figure 2 It is a flowchart of another method for enhancing cloud-edge communication disclosed in an embodiment of the present invention;

[0097] Figure 3 It is a flowchart of another method for enhancing cloud-edge communication disclosed in an embodiment of the present invention;

[0098] Figure 4 It is a flowchart of another method for enhancing cloud-edge communication disclosed in an embodiment of the present invention;

[0099] Figure 5 It is a structural schematic diagram of a device for enhancing cloud-edge communication disclosed in an embodiment of the present invention;

[0100] Figure 6 It is a structural schematic diagram of another device for enhancing cloud-edge communication disclosed in an embodiment of the present invention;

[0101] Figure 7 It is a structural schematic diagram of another device for enhancing cloud-edge communication disclosed in an embodiment of the present invention;

[0102] Figure 8 It is a structural diagram of another device for enhancing cloud-edge communication disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0103] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0104] The terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, device, product or end including a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units inherent to these processes, methods, products or ends.

[0105] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0106] The present invention discloses a method and device for enhancing cloud-edge communication, which can be applied to a cloud and an edge end. The cloud can establish a message communication connection with the edge end. On this basis, the cloud edits the configuration file of the cloud. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. Based on the loading result, the cloud monitors the connection request of the edge end. When the connection request of the edge end is monitored, the cloud parses the connection request to obtain a parsing result. Based on the parsing result, the cloud connects to the edge end for communication, which can shorten the time for establishing the communication connection and improve the communication efficiency. The following are detailed descriptions.

[0107] Embodiment 1

[0108] See also Figure 1 , Figure 1 1 is a flow chart of a method for enhancing cloud-edge communication disclosed in an embodiment of the present invention. Figure 1 The method for enhancing cloud-edge communication described above can be applied to the cloud, wherein the cloud message center can be understood as a local server or a cloud server, which is not limited in the embodiments of the present invention. Figure 1 As shown, the method for enhancing cloud-edge communication may include the following operations:

[0109] 101. Edit the cloud configuration files.

[0110] In an embodiment of the present invention, optionally, the configuration file of the cloud can be used to instruct the cloud to select a communication client to establish communication with the edge, wherein the communication client may include a QUIC client or a WebSocket client, which is not limited in the embodiment of the present invention.

[0111] 102. After the configuration file in the cloud is edited, the cloud loads the configuration file in the cloud to obtain a first loading result.

[0112] In the embodiment of the present invention, optionally, the cloud can verify the edited cloud configuration file, and after the verification is correct, it can be loaded according to the corresponding configuration file to obtain a first loading result, which is not limited in the embodiment of the present invention.

[0113] 103. The cloud monitors the connection request from the edge based on the first loading result.

[0114] In an embodiment of the present invention, optionally, monitoring of connection requests from the edge can be achieved by installing a proxy middleware. When the cloud has loaded the cloud configuration file, it can enter a state of monitoring connection requests from the edge. When the cloud receives a connection request from the edge, the cloud can enter a working state. When the cloud does not receive a connection request from the edge, the cloud can be in a waiting state, which is not limited in the embodiment of the present invention.

[0115] 104. After monitoring the connection request from the edge, the cloud parses the connection request and obtains the parsing result.

[0116] In an embodiment of the present invention, optionally, when the proxy middleware listens to a connection request from the edge, it can parse the connection request sent by the edge to obtain a parsing result. Further optionally, the parsing result can include obtaining the type of connection request by parsing an identification bit, and selecting a corresponding communication method based on the type, which is not limited in the embodiment of the present invention.

[0117] 105. Based on the analysis results, the cloud connects to the edge for communication.

[0118] It can be seen that the method for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud edits the cloud configuration file. After editing the cloud configuration file, the cloud loads the cloud configuration file to obtain a loading result. Based on the loading result, the cloud listens for the connection request from the edge. When the connection request from the edge is listened, the cloud parses the connection request to obtain a parsing result. Based on the parsing result, the cloud connects to the edge for communication. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency.

[0119] Embodiment 2

[0120] See also Figure 2 , Figure 2 is a flow chart of another method for enhancing cloud-edge communication disclosed in an embodiment of the present invention. Figure 2 The method for enhancing cloud-edge communication described above can be applied to a cloud message center, where the cloud message center can be understood as a local server or a cloud server, which is not limited in the embodiments of the present invention. Figure 2 As shown, the method for enhancing cloud-edge communication may include the following operations:

[0121] 201. Edit the cloud configuration files in the cloud.

[0122] 202. The cloud registration message processing function obtains the registration result.

[0123] In an embodiment of the present invention, optionally, the registration result may include the working status of the communication channel between the cloud and the edge. Further optionally, the message processing function may include at least one of a heartbeat function, a message loop write function and a channel detection function, which is not limited in the embodiment of the present invention.

[0124] As an optional implementation, the heartbeat function can be used to periodically detect the heartbeat between communication channels; the message loop write function can be used to instruct the cloud to send messages in a loop; the channel detection function can be used to detect abnormal parameters of the communication channel, and the abnormal parameters may include at least one of the delay duration of the communication channel and the packet loss rate of the communication channel, which is not limited in the embodiments of the present invention.

[0125] 203. The cloud loads the configuration file of the cloud based on the registration result to obtain a first loading result.

[0126] 204. The cloud monitors the connection request from the edge based on the first loading result.

[0127] 205. After monitoring the connection request from the edge, the cloud parses the connection request and obtains the parsing result.

[0128] 206. The cloud connects to the edge for communication based on the analysis results.

[0129] In the embodiment of the present invention, the specific technical details and technical terminology of step 201 and step 203 to step 206 can refer to the description of step 101 to step 105 in the first embodiment, and will not be repeated here.

[0130] It can be seen that the method for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud edits the configuration file of the cloud. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. Based on the loading result, the cloud monitors the connection request of the edge. When the connection request of the edge is monitored, the cloud parses the connection request to obtain a parsing result. Based on the parsing result, the cloud connects to the edge to communicate. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and reduce the time spent on establishing a connection, thereby improving communication efficiency. In addition, the management of the working status of the communication channel between the cloud and the edge can be achieved by registering a message processing function, thereby improving communication efficiency.

[0131] In an optional embodiment, in the above step 201, editing the cloud configuration file in the cloud may include:

[0132] The first startup file of the QUIC client and / or the second startup file of the WebSocket client are edited in the cloud. As configuration files in the cloud, the first startup file of the QUIC client and / or the second startup file of the WebSocket client can be used to instruct the QUIC client and / or the WebSocket client to enter a working state. The QUIC client and the WebSocket client are independent of each other when working.

[0133] In this optional embodiment, optionally, the first startup file of the QUIC client may include a QUIC client configuration parameter, and the QUIC client configuration parameter may include at least one of a first listening port, a first listening address, a first enabled state, and a maximum concurrent write message, which is not limited in this embodiment of the present invention. Further optionally, the maximum concurrent write message may be used to indicate the maximum number of messages that the QUIC client can process, which is not limited in this embodiment of the present invention;

[0134] Optionally, the second startup file of the WebSocket client may include WebSocket client configuration parameters, and the WebSocket client configuration parameters may include at least one of a second listening port, a second listening address, and a second enabled state, which is not limited in the embodiment of the present invention;

[0135] Among them, the cloud connects to the edge end for communication based on the analysis results, which may include:

[0136] When the state of the QUIC client is the first enabled state, the WebSocket client can be closed. At this time, the cloud can communicate with the edge through the QUIC client based on the parsing result, which is not limited in the embodiment of the present invention;

[0137] When the state of the WebSocket client is the second enabled state, the QUIC client can be closed. At this time, the cloud can communicate with the edge through the WebSocket client based on the parsing result, which is not limited in the embodiment of the present invention.

[0138] It can be seen that this optional embodiment can introduce the QUIC communication protocol for the cloud and edge that support the WebSocket communication protocol. The cloud and edge can choose to use either the WebSocket communication protocol or the QUIC communication protocol for communication, which increases the choice of communication protocols and reduces congestion during the communication process, thereby being more conducive to completing communication tasks.

[0139] Embodiment 3

[0140] See also Figure 3 , Figure 3 It is a flowchart of another method for enhancing cloud-edge communication disclosed in an embodiment of the present invention. Figure 3 The method for enhancing cloud-edge communication described above can be applied to an edge message center, which can be integrated into a computer device or exist independently, and the embodiments of the present invention do not limit this. Figure 3 As shown, the method for enhancing cloud-edge communication may include the following operations:

[0141] 301. The edge end loads the configuration file of the edge end to obtain a second loading result.

[0142] In an embodiment of the present invention, optionally, the configuration file of the edge terminal can be used to instruct the edge terminal to select a communication client to establish communication with the cloud. Further optionally, the communication client can include one of a QUIC client or a WebSocket client, which is not limited in the embodiment of the present invention.

[0143] 302. The edge terminal initializes the channel client based on the second loading result.

[0144] In an embodiment of the present invention, optionally, the channel client may include at least one of a QUIC client and a WebSocket client. The channel client may be used to perform bidirectional communication with the cloud to form a bidirectional communication channel, which is not limited in the embodiment of the present invention.

[0145] 303. The edge end reads the configuration file of the channel client and sets the node identifier of the edge end.

[0146] In the embodiment of the present invention, optionally, the node identifier may be the IP address of the edge terminal, which is not limited in the embodiment of the present invention.

[0147] 304. The edge sends a connection logic request to the cloud based on the node identifier of the edge that has been set, and establishes a connection with the cloud after receiving feedback sent by the cloud for allowing the connection to be established.

[0148] It can be seen that the method for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the edge loads the configuration file of the edge to obtain a loading result. The edge initializes the channel client based on the loading result. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. The edge reads the configuration file of the channel client and sets the node identifier of the edge. Based on the node identifier of the edge that has been set, the edge sends a connection logic request to the cloud, and after receiving feedback sent by the cloud to allow the connection to be established, the edge establishes a connection with the cloud. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency.

[0149] Embodiment 4

[0150] See also Figure 4 , Figure 4 : is a flow chart of a method for enhancing cloud-edge communication disclosed in an embodiment of the present invention. Figure 4 The method for enhancing cloud-edge communication described above can be applied to the edge message center, which can be integrated into a computer device or exist independently, and the embodiment of the present invention does not limit this. Figure 4 As shown, the method for enhancing cloud-edge communication may include the following operations:

[0151] 401. The edge end loads the configuration file of the edge end and obtains a second loading result.

[0152] 402. The edge terminal initializes the channel client based on the second loading result.

[0153] 403. The edge end encrypts the certificate of the channel client to obtain the encrypted channel client.

[0154] In the embodiment of the present invention, optionally, the edge end reading the configuration file of the channel client may include: the edge end reading the encrypted configuration file of the channel client, which is not limited in the embodiment of the present invention.

[0155] 404. The edge end reads the configuration file of the channel client and sets the node identifier of the edge end.

[0156] 405. The edge sends a connection logic request to the cloud based on the node identifier of the edge that has been set, and establishes a connection with the cloud after receiving feedback from the cloud for allowing the connection to be established.

[0157] 406. The edge end analyzes the communication working status of the currently selected channel client and obtains the analysis result.

[0158] In the embodiment of the present invention, optionally, the analysis result may be used to instruct the edge end to perform one of retaining the currently selected channel client and switching to a backup channel client, which is not limited in the embodiment of the present invention.

[0159] 407. The edge end performs an operation matching the analysis result according to the analysis result.

[0160] In the embodiment of the present invention, optionally, the edge end performs an operation matching the analysis result according to the analysis result, which may include:

[0161] When the analysis result shows that the communication working status of the currently selected channel client meets the preset conditions, the edge end retains the currently selected channel client;

[0162] When the analysis result shows that the communication working status of the currently selected channel client does not meet the preset conditions, the edge end closes the currently selected channel client and switches to the backup channel client. Optionally, the backup channel client can be one of a QUIC client and a WebSocket client, which is not limited in the embodiment of the present invention.

[0163] Further optionally, the preset condition may include at least one of a transmission rate and a bit error rate of a currently selected channel client, which is not limited in the embodiment of the present invention.

[0164] In the embodiment of the present invention, the specific technical details and technical terminology of step 201, step 202, step 404 and step 405 can refer to the description of step 301 to step 304 in implementation three, and will not be repeated here.

[0165] It can be seen that the method for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud can establish a message communication connection with the edge. On this basis, the edge loads the configuration file of the edge to obtain a loading result. The edge initializes the channel client based on the loading result. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. The edge reads the configuration file of the channel client and sets the node identifier of the edge. Based on the node identifier of the edge that has been set, the edge sends a connection logic request to the cloud, and after receiving feedback sent by the cloud to allow the connection to be established, the edge establishes a connection with the cloud. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency. In addition, encrypting the certificate of the channel client can improve the channel security of cloud-edge message transmission. According to the communication working status of the currently selected channel client, the edge end is instructed to retain the currently selected channel client or switch to one of the backup channel clients. This can realize automatic migration of connections and error correction during communication, greatly improving the efficiency of cloud-edge communication.

[0166] In an optional embodiment, in the above step 401, the configuration file of the edge end may be used to instruct the edge end to use a QUIC client and / or a WebSocket client to perform two-way communication with the cloud, which is not limited in the embodiment of the present invention;

[0167] In step 401, the edge end loads the configuration file of the edge end, which may include:

[0168] The edge end loads the first startup file of the QUIC client and / or the second startup file of the WebSocket client. The first startup file of the QUIC client and / or the second startup file of the WebSocket client can be used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client can work independently of each other, which is not limited in this embodiment of the present invention;

[0169] As an optional implementation manner, the first startup file of the QUIC client may include a QUIC client configuration parameter, and the QUIC client configuration parameter may include at least one of a first formal configuration state, a first port address, and a first enabled state, which is not limited in this embodiment of the present invention;

[0170] As another optional implementation, the second startup file of the WebSocket client may include WebSocket client configuration parameters, and the WebSocket client configuration parameters may include at least one of a second formal configuration state, a second port address, and a second enabled state, which is not limited in this embodiment of the present invention.

[0171] It can be seen that this optional embodiment can introduce the QUIC communication protocol for the cloud and edge that support the WebSocket communication protocol. The cloud and edge can choose to use either the WebSocket communication protocol or the QUIC communication protocol for communication, which increases the choice of communication protocols and reduces congestion during the communication process, thereby being more conducive to completing communication tasks.

[0172] Embodiment 5

[0173] See also Figure 5 , Figure 5 : is a schematic diagram of a structure of a device for enhancing cloud-edge communication disclosed in an embodiment of the present invention. Figure 5 The device for enhancing cloud-edge communication described above can be applied to the cloud, wherein the cloud message center can be understood as a local server or a cloud server, which is not limited in the embodiments of the present invention. Figure 5 As shown, the device for enhancing cloud-edge communication may include the following modules:

[0174] The editing module 501 is used to edit the configuration file in the cloud.

[0175] In an embodiment of the present invention, optionally, the configuration file of the cloud can be used to instruct the cloud to select a communication client to establish communication with the edge, wherein the communication client may include a QUIC client or a WebSocket client, which is not limited in the embodiment of the present invention.

[0176] The first loading module 502 is used to load the configuration file in the cloud after editing the configuration file in the cloud to obtain a first loading result.

[0177] In the embodiment of the present invention, optionally, the first loading module 502 can check and verify the edited cloud configuration file. After the check is correct, it can be loaded according to the corresponding configuration file to obtain a first loading result, which is not limited in the embodiment of the present invention.

[0178] The monitoring module 503 is used to monitor the connection request of the edge terminal based on the first loading result.

[0179] In an embodiment of the present invention, optionally, when the cloud has completed loading the cloud configuration file, the monitoring module 503 can enter a state of monitoring the connection request of the edge end. When the connection request of the edge end is monitored, the cloud can enter a working state. When the connection request of the edge end is not monitored, the cloud can be in a waiting state. The embodiment of the present invention does not limit this.

[0180] The parsing module 504 is used to parse the connection request after monitoring the connection request from the edge end to obtain the parsing result.

[0181] In an embodiment of the present invention, optionally, when the monitoring module 503 monitors a connection request from the edge end, the parsing module 504 may parse the connection request sent by the edge end to obtain a parsing result. Further optionally, the parsing result may include obtaining the type of the connection request by parsing the identification bit, and selecting a corresponding communication method according to the type, which is not limited in the embodiment of the present invention.

[0182] The first communication module 505 is used to connect to the edge end for communication based on the analysis result.

[0183] It can be seen that the device for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud edits the cloud configuration file. After editing the cloud configuration file, the cloud loads the cloud configuration file to obtain a loading result. Based on the loading result, the cloud listens for the connection request from the edge. When the connection request from the edge is listened, the cloud parses the connection request to obtain a parsing result. Based on the parsing result, the cloud connects to the edge for communication. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency.

[0184] In an optional embodiment, if Figure 5 As shown, the device for enhancing cloud-edge communication may also include the following modules:

[0185] The registration module 506 is used to register the message processing function and obtain the registration result.

[0186] In an embodiment of the present invention, optionally, the registration result may include the working status of the communication channel between the cloud and the edge. Further optionally, the message processing function may include at least one of a heartbeat function, a message loop write function and a channel detection function, which is not limited in the embodiment of the present invention.

[0187] As an optional implementation, the heartbeat function can be used to periodically detect the heartbeat between communication channels; the message loop write function can be used to instruct the cloud to send messages in a loop; the channel detection function can be used to detect abnormal parameters of the communication channel, and the abnormal parameters may include at least one of the delay duration of the communication channel and the packet loss rate of the communication channel, which is not limited in the embodiments of the present invention.

[0188] The first loading module loads the configuration file in the cloud, and the specific method of obtaining the first loading result may include:

[0189] The first loading module loads the configuration file in the cloud based on the registration result to obtain a first loading result.

[0190] It can be seen that the device for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud edits the configuration file of the cloud. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain the loading result. Based on the loading result, the cloud monitors the connection request of the edge. After monitoring the connection request of the edge, the cloud parses the connection request to obtain the parsing result. Based on the parsing result, the cloud connects to the edge to communicate. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency. In addition, the management of the working status of the communication channel between the cloud and the edge can be achieved by registering a message processing function, thereby improving communication efficiency.

[0191] In another optional embodiment, the specific manner in which the editing module 501 edits the configuration file in the cloud may include:

[0192] The first startup file of the QUIC client and / or the second startup file of the WebSocket client are edited in the cloud. As configuration files in the cloud, the first startup file of the QUIC client and / or the second startup file of the WebSocket client can be used to instruct the QUIC client and / or the WebSocket client to enter a working state. The QUIC client and the WebSocket client are independent of each other when working.

[0193] In this optional embodiment, optionally, the first startup file of the QUIC client may include a QUIC client configuration parameter, and the QUIC client configuration parameter may include at least one of a first listening port, a first listening address, a first enabled state, and a maximum concurrent write message, which is not limited in this embodiment of the present invention. Further optionally, the maximum concurrent write message may be used to indicate the maximum number of messages that the QUIC client can process, which is not limited in this embodiment of the present invention;

[0194] Optionally, the second startup file of the WebSocket client may include WebSocket client configuration parameters, and the WebSocket client configuration parameters may include at least one of a second listening port, a second listening address, and a second enabled state, which is not limited in the embodiment of the present invention;

[0195] The specific manner in which the first communication module 505 connects to the edge end for communication based on the analysis result may include:

[0196] When the state of the QUIC client is the first enabled state, the WebSocket client can be closed. At this time, the cloud can communicate with the edge through the QUIC client based on the parsing result, which is not limited in the embodiment of the present invention;

[0197] When the state of the WebSocket client is the second enabled state, the QUIC client can be closed. At this time, the cloud can communicate with the edge through the WebSocket client based on the parsing result, which is not limited in the embodiment of the present invention.

[0198] It can be seen that this optional embodiment can introduce the QUIC communication protocol for the cloud and edge that support the WebSocket communication protocol. The cloud and edge can choose to use either the WebSocket communication protocol or the QUIC communication protocol for communication, which increases the choice of communication protocols and reduces congestion during the communication process, thereby being more conducive to completing communication tasks.

[0199] Embodiment 6

[0200] See also Figure 6 , Figure 6 is a schematic diagram of the structure of another device for enhancing cloud-edge communication disclosed in an embodiment of the present invention. Figure 6 The method for enhancing cloud-edge communication described above can be applied to an edge message center, which can be integrated into a computer device or exist independently, and the embodiments of the present invention do not limit this. Figure 6 As shown, the device for enhancing cloud-edge communication may include the following modules:

[0201] The second loading module 601 is used to load the configuration file of the edge end and obtain a second loading result.

[0202] In an embodiment of the present invention, optionally, the configuration file of the edge terminal can be used to instruct the edge terminal to select a communication client to establish communication with the cloud. Further optionally, the communication client can include a QUIC client or a WebSocket client, which is not limited in the embodiment of the present invention.

[0203] The initialization module 602 is used to initialize the channel client based on the second loading result.

[0204] In an embodiment of the present invention, optionally, the channel client may include at least one of a QUIC client and a WebSocket client. The channel client may be used to perform bidirectional communication with the cloud to form a bidirectional communication channel, which is not limited in the embodiment of the present invention.

[0205] The reading module 603 is used to read the configuration file of the channel client and set the node identification of the edge end.

[0206] In the embodiment of the present invention, optionally, the node identifier may be the IP address of the edge terminal, which is not limited in the embodiment of the present invention.

[0207] The sending module 604 is used to send a connection logic request to the cloud based on the node identifier of the edge end that has been set;

[0208] The second communication module 605 is used to establish a connection with the cloud after receiving feedback from the cloud for allowing the connection to be established.

[0209] It can be seen that the device for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the edge loads the configuration file of the edge to obtain a loading result. The edge initializes the channel client based on the loading result. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. The edge reads the configuration file of the channel client and sets the node identifier of the edge. Based on the node identifier of the edge that has been set, the edge sends a connection logic request to the cloud, and after receiving feedback sent by the cloud to allow the connection to be established, the edge establishes a connection with the cloud. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency.

[0210] In an optional embodiment, if Figure 7 As shown, the device for enhancing cloud-edge communication may also include the following modules:

[0211] The analysis module 606 is used to analyze the communication working status of the currently selected channel client after the edge terminal establishes a connection with the cloud to obtain an analysis result.

[0212] The analysis result is used to instruct the edge end to perform one of retaining the currently selected channel client and switching to a standby channel client;

[0213] The execution module 607 is used to execute an operation matching the analysis result according to the analysis result.

[0214] In the embodiment of the present invention, optionally, the specific manner in which the execution module 607 executes the operation matching the analysis result according to the analysis result may include:

[0215] When the analysis result shows that the communication working state of the currently selected channel client meets the preset condition, the execution module 607 retains the currently selected channel client;

[0216] When the analysis result shows that the communication working state of the currently selected channel client does not meet the preset condition, the execution module 607 closes the currently selected channel client and switches to the backup channel client. Optionally, the backup channel client can be one of a QUIC client and a WebSocket client, which is not limited in the embodiment of the present invention.

[0217] Further optionally, the preset condition may include at least one of a transmission rate and a bit error rate of a currently selected channel client, which is not limited in the embodiment of the present invention.

[0218] The encryption module 608 is used to encrypt the certificate of the channel client to obtain the encrypted channel client.

[0219] In the embodiment of the present invention, optionally, the specific manner in which the reading module 603 reads the configuration file of the channel client may include: the reading module 603 reads the encrypted configuration file of the channel client, which is not limited in the embodiment of the present invention.

[0220] It can be seen that the device for enhancing cloud-edge communication described in the embodiment of the present invention can be applied to the cloud and the edge. The cloud can establish a message communication connection with the edge. On this basis, the cloud can establish a message communication connection with the edge. On this basis, the edge loads the configuration file of the edge to obtain a loading result. The edge initializes the channel client based on the loading result. After editing the configuration file of the cloud, the cloud loads the configuration file of the cloud to obtain a loading result. The edge reads the configuration file of the channel client and sets the node identifier of the edge. Based on the node identifier of the edge that has been set, the edge sends a connection logic request to the cloud, and after receiving feedback sent by the cloud to allow the connection to be established, the edge establishes a connection with the cloud. The QUIC transmission protocol can be introduced for the cloud and edge that support the WebSocket transmission protocol, which can reduce the occurrence of communication interruptions and the time spent on establishing a connection, thereby improving communication efficiency. In addition, encrypting the certificate of the channel client can improve the channel security of cloud-edge message transmission. According to the communication working status of the currently selected channel client, the edge end is instructed to retain the currently selected channel client or switch to one of the backup channel clients. This can realize automatic migration of connections and error correction during communication, greatly improving the efficiency of cloud-edge communication.

[0221] In another optional embodiment, the configuration file of the edge end may be used to instruct the edge end to use a QUIC client and / or a WebSocket client to perform bidirectional communication with the cloud, which is not limited in the embodiment of the present invention;

[0222] The specific manner in which the second loading module 601 loads the configuration file of the edge terminal may include:

[0223] The second loading module 601 loads the first startup file of the QUIC client and / or the second startup file of the WebSocket client. The first startup file of the QUIC client and / or the second startup file of the WebSocket client can be used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client can work independently of each other, which is not limited in this embodiment of the present invention;

[0224] As an optional implementation manner, the first startup file of the QUIC client may include a QUIC client configuration parameter, and the QUIC client configuration parameter may include at least one of a first formal configuration state, a first port address, and a first enabled state, which is not limited in this embodiment of the present invention;

[0225] As another optional implementation, the second startup file of the WebSocket client may include WebSocket client configuration parameters, and the WebSocket client configuration parameters may include at least one of a second formal configuration state, a second port address, and a second enabled state, which is not limited in this embodiment of the present invention.

[0226] It can be seen that this optional embodiment can introduce the QUIC communication protocol for the cloud and edge that support the WebSocket communication protocol. The cloud and edge can choose to use either the WebSocket communication protocol or the QUIC communication protocol for communication, which increases the choice of communication protocols and reduces congestion during the communication process, thereby being more conducive to completing communication tasks.

[0227] Embodiment 7

[0228] See also Figure 8 , Figure 8 FIG. 1 is a schematic diagram of the structure of another device for enhancing cloud-edge communication disclosed in an embodiment of the present invention. Figure 8 As shown, the device for enhancing cloud-edge communication may include:

[0229] A memory 701 storing executable program codes;

[0230] a processor 702 coupled to the memory 701;

[0231] The processor 702 calls the executable program code stored in the memory 701 to execute the steps in the method for enhancing cloud-edge communication described in any of the above embodiments.

[0232] Embodiment 8

[0233] An embodiment of the present invention discloses a computer-storable medium, which stores computer instructions. When the computer instructions are called, they are used to execute the steps in the method for enhancing cloud-edge communication described in any of the above embodiments.

[0234] Embodiment 9

[0235] An embodiment of the present invention discloses a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable a computer to execute the steps in the method for enhancing cloud-edge communication described in any of the above embodiments.

[0236] The device embodiments described above are only illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, i.e., they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art may understand and implement it without creative work.

[0237] Through the specific description of the above embodiments, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the above technical solution can be essentially or partly contributed to the prior art in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, and the storage medium includes a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electronically erasable rewritable read-only memory (EEPROM), a compact disc (CD-ROM) or other optical disc storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0238] Finally, it should be noted that the data synchronization method and device applied to the power system disclosed in the embodiment of the present invention discloses only the preferred embodiment of the present invention, which is only used to illustrate the technical solution of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, ordinary technicians in this field should understand that it is still possible to modify the technical solutions recorded in the aforementioned embodiments, or to replace some of the technical features therein by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A method for enhancing cloud-edge communication, characterized in that: Applied to the cloud, the method includes: The cloud edits the configuration file of the cloud; After the configuration file on the cloud is edited, the cloud loads the configuration file on the cloud to obtain a first loading result; The cloud terminal monitors the connection request of the edge terminal based on the first loading result; After monitoring the connection request of the edge terminal, the cloud terminal analyzes the connection request and obtains the analysis result; The cloud terminal connects to the edge terminal for communication based on the analysis result; Before loading the configuration file on the cloud, the following steps are included: The cloud registration message processing function obtains a registration result, wherein the registration result includes a working status of a communication channel between the cloud and the edge; The message processing function includes at least one of a heartbeat function, a message loop write function, and a channel detection function, the parsing result includes the type of connection request obtained by parsing the identification bit, and the cloud selects a corresponding communication method according to the type to connect to the edge end for communication; The heartbeat function is used to periodically detect the heartbeat between the communication channels; the message loop write function is used to instruct the cloud to send messages cyclically; the channel detection function is used to detect abnormal parameters of the communication channel, and the abnormal parameters include at least one of the delay duration of the communication channel and the packet loss rate of the communication channel; The specific method of monitoring the connection request of the edge terminal is: When the cloud has finished loading the configuration file of the cloud, the cloud enters a state of listening to the connection request of the edge end, and when the cloud receives the connection request of the edge end, the cloud enters a working state; When the cloud does not receive a connection request from the edge, the cloud is in a waiting state; The cloud loads the configuration file of the cloud to obtain a first loading result, including: The cloud loads the configuration file of the cloud based on the registration result to obtain a first loading result; The cloud-side editing of the cloud-side configuration file includes: The cloud edits the first startup file of the QUIC client and / or the second startup file of the WebSocket client as the configuration file of the cloud, the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working; The first startup file of the QUIC client includes the QUIC client configuration parameters, where the QUIC client configuration parameters include at least one of a first listening port, a first listening address, a first enabled state, and a maximum concurrent write message, where the maximum concurrent write message is used to indicate the maximum number of messages that the QUIC client can process; The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second listening port, a second listening address, and a second enabled state; Wherein, the cloud connects to the edge end for communication based on the analysis result, including: When the state of the QUIC client is the first enabled state, the cloud closes the WebSocket client, and communicates with the edge through the QUIC client based on the parsing result; When the state of the WebSocket client is the second enabled state, the cloud closes the QUIC client and communicates with the edge through the WebSocket client based on the parsing result.

2. A method for enhancing cloud-edge communication, characterized in that: Applied to the edge end, the method includes: The edge end loads the configuration file of the edge end to obtain a second loading result; The edge end initializes a channel client based on the second loading result, where the channel client includes a QUIC client and / or a WebSocket client, and the channel client is used to perform bidirectional communication with the cloud to form a bidirectional communication channel; The edge terminal reads the configuration file of the channel client and sets the node identifier of the edge terminal; The edge sends a connection logic request to the cloud based on the node identifier of the edge that has been set, and establishes a connection with the cloud after receiving a feedback from the cloud for allowing the connection to be established; The configuration file of the edge end is used to instruct the edge end to select the QUIC client and / or the WebSocket client to perform two-way communication with the cloud end; The edge end loads the configuration file of the edge end, including: The edge end loads the first startup file of the QUIC client and / or the second startup file of the WebSocket client, where the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working; The first startup file of the QUIC client includes the QUIC client configuration parameters, and the QUIC client configuration parameters include at least one of a first formal configuration state, a first port address, and a first enabled state; The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second formal configuration state, a second port address, and a second enabled state; After the edge terminal establishes a connection with the cloud, the method further includes: The edge end analyzes the communication working state of the currently selected channel client to obtain an analysis result, wherein the analysis result is used to instruct the edge end to perform one of retaining the currently selected channel client and switching to a standby channel client; The edge end performs an operation matching the analysis result according to the analysis result; The edge end performs an operation matching the analysis result according to the analysis result, including: When the analysis result shows that the communication working state of the currently selected channel client meets the preset condition, the edge terminal retains the currently selected channel client; When the analysis result shows that the communication working state of the currently selected channel client does not meet the preset condition, the edge end closes the currently selected channel client and switches to the backup channel client, where the backup channel client is one of the QUIC client and the WebSocket client; The preset condition includes at least one of a transmission rate and a bit error rate of the currently selected channel client; And, the method further comprises: The edge end encrypts the certificate of the channel client to obtain an encrypted channel client; The edge end reads the configuration file of the channel client, including: The edge terminal reads the encrypted configuration file of the channel client.

3. A device for enhancing cloud-edge communication, characterized in that: Applied to the cloud, the device comprises: An editing module, used to edit the configuration file in the cloud; A first loading module, configured to load the configuration file on the cloud after editing the configuration file on the cloud to obtain a first loading result; A monitoring module, configured to monitor a connection request from an edge terminal based on the first loading result; A parsing module, configured to parse the connection request after monitoring the connection request of the edge end, and obtain a parsing result; A first communication module, used to connect to the edge end for communication based on the analysis result; The device also includes: A registration module, used to register a message processing function and obtain a registration result, wherein the registration result includes a working state of a communication channel between the cloud and the edge; The message processing function includes at least one of a heartbeat function, a message loop write function, and a channel detection function, the parsing result includes the type of connection request obtained by parsing the identification bit, and the cloud selects a corresponding communication method according to the type to connect to the edge end for communication; The heartbeat function is used to periodically detect the heartbeat between the communication channels; the message loop write function is used to instruct the cloud to send messages cyclically; the channel detection function is used to detect abnormal parameters of the communication channel, and the abnormal parameters include at least one of the delay duration of the communication channel and the packet loss rate of the communication channel; The specific method of monitoring the connection request of the edge terminal is: When the cloud has finished loading the configuration file of the cloud, the cloud enters a state of listening to the connection request of the edge end, and when the cloud receives the connection request of the edge end, the cloud enters a working state; When the cloud does not receive a connection request from the edge, the cloud is in a waiting state; The first loading module loads the configuration file on the cloud, and a specific method of obtaining the first loading result includes: The first loading module loads the configuration file in the cloud based on the registration result to obtain a first loading result; The specific manner in which the editing module edits the configuration file on the cloud includes: Editing a first startup file of a QUIC client and / or a second startup file of a WebSocket client as configuration files of the cloud, wherein the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working; The first startup file of the QUIC client includes the QUIC client configuration parameters, where the QUIC client configuration parameters include at least one of a first listening port, a first listening address, a first enabled state, and a maximum concurrent write message, where the maximum concurrent write message is used to indicate the maximum number of messages that the QUIC client can process; The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second listening port, a second listening address, and a second enabled state; The specific manner in which the first communication module connects to the edge end for communication based on the analysis result includes: When the state of the QUIC client is the first enabled state, the first communication module closes the WebSocket client, and communicates with the edge end through the QUIC client based on the parsing result; When the state of the WebSocket client is the second enabled state, the first communication module closes the QUIC client and communicates with the edge end through the WebSocket client based on the parsing result.

4. A device for enhancing cloud-edge communication, characterized in that: Applied to the edge end, the device includes: A second loading module, used to load the configuration file of the edge end to obtain a second loading result; An initialization module, configured to initialize a channel client based on the second loading result, wherein the channel client includes a QUIC client and / or a WebSocket client, and the channel client is configured to perform bidirectional communication with the cloud to form a bidirectional communication channel; A reading module, used to read the configuration file of the channel client and set the node identifier of the edge end; A sending module, used to send a connection logic request to the cloud based on the node identifier of the edge terminal that has been set; A second communication module, configured to establish a connection with the cloud after receiving feedback from the cloud for allowing the connection to be established; The configuration file of the edge end is used to instruct the edge end to select the QUIC client and / or the WebSocket client to perform two-way communication with the cloud end; The specific manner in which the second loading module loads the configuration file of the edge terminal includes: The second loading module loads the first startup file of the QUIC client and / or the second startup file of the WebSocket client, wherein the first startup file of the QUIC client and / or the second startup file of the WebSocket client are used to instruct the QUIC client and / or the WebSocket client to enter a working state, and the QUIC client and the WebSocket client are independent of each other when working; The first startup file of the QUIC client includes the QUIC client configuration parameters, and the QUIC client configuration parameters include at least one of a first formal configuration state, a first port address, and a first enabled state; The second startup file of the WebSocket client includes the WebSocket client configuration parameters, and the WebSocket client configuration parameters include at least one of a second formal configuration state, a second port address, and a second enabled state; The device also includes: An analysis module, configured to analyze the communication working state of the currently selected channel client after the edge terminal establishes a connection with the cloud terminal, and obtain an analysis result, wherein the analysis result is used to instruct the edge terminal to perform one of retaining the currently selected channel client and switching to a standby channel client; An execution module, used for executing an operation matching the analysis result according to the analysis result; The specific manner in which the execution module executes the operation matching the analysis result according to the analysis result includes: When the analysis result shows that the communication working state of the currently selected channel client meets the preset condition, the execution module retains the currently selected channel client; When the analysis result shows that the communication working state of the currently selected channel client does not meet the preset condition, the execution module closes the currently selected channel client and switches to the backup channel client, where the backup channel client is one of the QUIC client and the WebSocket client; The preset condition includes at least one of a transmission rate and a bit error rate of the currently selected channel client; And, the device further comprises: An encryption module, used for encrypting the certificate of the channel client to obtain an encrypted channel client; The specific manner in which the reading module reads the configuration file of the channel client includes: The reading module reads the encrypted configuration file of the channel client.

5. A device for enhancing cloud-edge communication, characterized in that: The device comprises: A memory storing executable program code; a processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the method for enhancing cloud-edge communication as described in any one of claims 1-2.

Citation Information

Patent Citations

  • QUIC protocol-based cloud edge service access method and system

    CN112887433A

  • Cloud desktop connection method, device and equipment

    CN115277806A