CN112887433A - Cloud access edge service method and system based on QUIC protocol - Google Patents
Cloud access edge service method and system based on QUIC protocol Download PDFInfo
- Publication number
- CN112887433A CN112887433A CN202110385933.7A CN202110385933A CN112887433A CN 112887433 A CN112887433 A CN 112887433A CN 202110385933 A CN202110385933 A CN 202110385933A CN 112887433 A CN112887433 A CN 112887433A
- Authority
- CN
- China
- Prior art keywords
- quic
- connection
- edge
- cloud
- edge node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/164—Adaptation or special uses of UDP protocol
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention belongs to the field of cloud computing and edge computing, and discloses a cloud end edge service access method and a cloud end edge service access system based on a QUIC protocol. The invention realizes the function of accessing the edge service by the cloud, and the user in the public network can access the edge service in the internal network through the cloud, and still has good performance in the weak network environment at the edge side, thereby effectively improving the performance of the loading service and improving the stability of the network.
Description
Technical Field
The invention belongs to the field of cloud computing and edge computing, and particularly relates to a cloud-based edge service access method and system based on a QUIC protocol.
Background
With the development of technologies such as containers, kubernets, internet of things and the like, data generated at the edge of a network rapidly increases, but mass data are transmitted to a cloud center, the bandwidth and the time delay of the network are examined, the privacy of user data cannot be guaranteed, and edge computing is developed for solving the problems. Most deployment and application scenes of edge computing require cooperation of an edge side and a central cloud, and cloud-edge cooperation, which includes resource cooperation, application cooperation, data cooperation, intelligent cooperation and the like.
With the development of cloud computing and micro services, the expandability, the upgradability, the easy maintainability and the like of the micro services bring obvious benefits to the development, the test and the operation. However, the service of the cloud edge is necessarily sunk to the edge side, and because the CNI plug-in the native cloud cannot (hardly) operate on the edge side, the scheme for solving the service discovery by Kubernetes cannot be migrated to the edge side of the cloud edge side cooperation for use, so that the service accessing the edge through the cloud end becomes a very important research subject in the cloud edge side cooperation, and has an important practical significance on how to get through the channel from the cloud end to the service access of the edge. Currently, in edge-side network schemes in current cloud edge coordination architectures such as kubbeedge and OpenYurt, only edge-to-edge data stream communication and cloud and edge control stream communication are implemented. Because the cloud and the edge are not on the same network plane, a request of a user for initiating service access at the cloud end fails. In addition, at present, the communication between the cloud edge and the cloud end is realized only by a websocket protocol.
In the current cloud edge end system, if an edge gateway is in an intranet environment and can only access a public network in a one-way mode, a user cannot access a service deployed on an edge side at a cloud end in the scene.
Disclosure of Invention
The technical purpose is as follows: aiming at the defects, the invention discloses a cloud access edge service method and system based on a QUIC protocol, which realize the function of the cloud access edge service based on the QUIC protocol.
The technical scheme is as follows: in order to achieve the technical purpose, the invention adopts the following technical scheme:
a cloud access edge service method based on a QUIC protocol is used for system communication, the system comprises a cloud, an edge side and more than one user side, the edge side comprises more than one edge node, each edge node manages a plurality of pods in the form of a kubernets cluster, and the method is characterized in that: each edge node is provided with a service stream component service stream, and an edge gateway EdgeGateway and a tunnel server are arranged at the cloud end;
QUIC connection is established between the cloud and each edge node, and the steps are as follows:
the cloud end starts an EdgeGateway and a tunnel server and monitors requests from the edge node and the user end;
when each edge node is started, starting a corresponding service stream, and creating a QUIC connection, wherein the QUIC connection is used for establishing a data transmission channel between a cloud end and the edge node;
and monitoring the QUIC connection by a cloud tunnel server, and saving the QUIC connection by using the host IP and the hostname of the edge node as a key.
Preferably, the step of accessing the edge service by the cloud comprises:
s1, QUIC connection is established between the cloud and each edge node of the edge side;
s2, the Edgegateway receives a connection request initiated by a user terminal, wherein the connection request comprises service information to be accessed by the user terminal;
s3, the Edgegateway executes a reverse proxy process to generate a session Id for the current connection request; executing a load balancing strategy to obtain a real host IP of the edge node corresponding to the connection request and a port corresponding to the pod;
s4, the Edgegateway inquires the corresponding QUIC connection at the tunnel server according to the host IP, and writes the connection request connection initiated by the user side into the QUIC connection;
s5, continuously monitoring the QUIC connection by the service stream at the edge side; after receiving a connection request initiated by a user side through QUIC connection, a service stream is forwarded to a pod corresponding to the request;
s6, the service stream of the edge side writes the access pod request result back to the corresponding QUIC connection and sends the access pod request result to the cloud;
s7, the cloud tunnel server sends a response message to the EdgeGateway, where the response message includes a result of responding to the connection request in step S3.
Preferably, the service stream is configured to create a QUIC connection when an edge node is started, where the QUIC connection is used as a data channel for accessing an edge service of the edge node through a cloud; the service stream receives a connection request sent by a user side and forwarded by the cloud through QUIC connection, forwards the connection request to a pod corresponding to the connection request, receives a response message of the pod and returns the response message to the cloud tunnel server through the QUIC connection;
the tunnel server is used for storing the QUIC connection established by the edge node and sending a response message of the pod returned by the edge node to the Edgegateway;
and the Edgegateway supports a user to define a load balancing strategy and a QUIC protocol, receives and analyzes the connection request sent by the user side, inquires the corresponding QUIC connection at the tunnel server according to the analyzed information, writes the connection request sent by the user side into the QUIC connection and then sends the connection request to the corresponding edge node.
Preferably, the QUIC connection has a header, the header carries a host name hostname and a host IP of the corresponding edge node, and the tunnel server uses the host IP and hostname of the edge node as a key to store the corresponding QUIC connection.
Preferably, in step S3, the connection request initiated by the user side is an http request.
Preferably, in step S4, the EdgeGateway queries kubernets by parsing the uniform resource locator url corresponding to the http connection request, and parses the specific host IP.
Preferably, only one QUIC connection is established between the same edge node and the cloud, and the QUIC connection is used as a reusable data channel for the cloud to access the edge service of the edge node.
The utility model provides a system, includes high in the clouds, edge side and more than one user side, its characterized in that: the cloud end is provided with an edge gateway (Edgegateway) and a tunnel server (tunnel server), the edge side comprises more than one edge node, each edge node is provided with a service stream component service stream, and each edge node manages a plurality of pods in a kubernets cluster mode; wherein the content of the first and second substances,
the service stream is used for creating a QUIC connection when the edge node is started, and the QUIC connection is used as a data channel for accessing the edge service of the edge node by a cloud; the service stream receives a connection request sent by a user side and forwarded by the cloud through QUIC connection, forwards the connection request to a pod corresponding to the connection request, receives a response message of the pod and returns the response message to the cloud tunnel server through the QUIC connection;
the tunnel server is used for storing the QUIC connection established by the edge node and sending a response message of the pod returned by the edge node to the Edgegateway;
and the Edgegateway supports a user to define a load balancing strategy and a QUIC protocol, receives and analyzes the connection request sent by the user side, inquires the corresponding QUIC connection at the tunnel server according to the analyzed information, writes the connection request sent by the user side into the QUIC connection and then sends the connection request to the corresponding edge node.
Preferably, the QUIC connection is provided with a data header, and the header carries a host name hostname and a host IP of a corresponding edge node;
and the Edgegateway executes reverse proxy and load balancing on the received connection request sent by the user side, analyzes a specific host IP, and inquires corresponding QUIC connection at the tunnel server according to the host IP.
A cloud service center for an edge node in a communication connection system, comprising: the method comprises the steps that an edge gateway Edgegateway and a tunnel server are included, all QUIC connections established by edge nodes are stored in the tunnel server, and response messages returned by the edge nodes are sent to the Edgegateway;
the Edgegateway supports a user to define a load balancing strategy and a QUIC protocol, monitors a connection request from the edge node and the user side, and can search a corresponding QUIC connection from the tunnel server according to the analyzed request information of the user side and write the connection request sent by the user side into the QUIC connection.
Has the advantages that: due to the adoption of the technical scheme, the invention has the following technical effects:
according to the invention, under the cloud edge terminal environment, a user under a public network can access the edge service in the internal network through the cloud end, so that the functional defects of the cloud edge terminal are compensated, and the user experience of the cloud edge terminal integrated system is improved; the service is designed based on a QUIC protocol, still has good performance in the weak network environment at the edge side, and can effectively improve the performance of loading the service and improve the stability.
Drawings
FIG. 1 is a schematic diagram of a deployment topology of components in a cloud-based access edge service system based on a QUIC protocol according to the present invention;
FIG. 2 is a flowchart of a method for accessing edge services based on the cloud of the QUIC protocol according to the present invention;
FIG. 3 is a schematic diagram of the location of the cloud-based access edge service system based on the QUIC protocol in the current Internet environment.
Detailed Description
The following describes embodiments of the present invention with reference to the drawings.
The invention relates to a design for realizing cloud access edge service based on a QUIC protocol, wherein the network environment of an edge node is often not very stable, and the QUIC protocol has better performance in a weak network environment compared with a websocket and has higher speed in multiplexing for avoiding the blocking of a queue head compared with the websocket. The structural composition in the design of the invention comprises:
tunnel server: there is maintained a QUIC connection entity that communicates with the IP and hostname of the edge node and the edge node corresponding to the IP and hostname.
EdgeGateway: and receiving a data request sent by a user, generating a Session ID, executing a reverse proxy, performing load balancing, analyzing a specific host IP (intranet IP) from the Endpoints in the Ready state, and forwarding the request to the QUIC connection of a corresponding node.
service stream: the forwarding cloud tunnel server is responsible for sending the request sent by the forwarding cloud tunnel server and forwarding the request to a specific pod on the end side, and sending a result returned by the pod back to the cloud tunnel server, and the tunnel server can find a return body of the original request according to the sessionID in the message body.
As shown in fig. 1, in the present invention, a cloud node, i.e., a cloud node, needs to be managed by kubernets, has a service discovery capability of kubernets, and an edge node needs to be managed by an edge computing framework (kuberedge). When the system component is actually deployed, the system component is divided into two parts, the first component comprises an Edgegateway and a Tunnel Server, and the system component is deployed at the cloud end in a multi-active mode, so that an exposed interface of a public network is increased. The second component comprises a ServiceStream, deployed on each edge node. The starting sequence of the two components also has requirements, and the components of the cloud end are started before the components of the edge nodes.
As shown in fig. 2, the specific process of cloud access edge service based on the QUIC protocol of the present invention is as follows:
1. the cloud end starts the EdgeGateway and the tunnel server, and monitors requests, wherein the requests comprise a node registration QUIC client request of the edge side and a user request from the cloud end.
2. When each edge node is started, a service stream component is started, a QUIC connection is created, a tunnel server at the cloud monitors the QUIC connection, and the hostIP and the hostname are stored as keys. The service stream will keep listening to the connection and forward the connection according to the received message.
3. The EdgeGateway receives an http request initiated by a user.
4. The Edgegateway executes a reverse proxy process, generates an id for the current request, analyzes url, queries kubernets, executes a load balancing strategy, and takes the actual hostIP and the port.
5. EdgeGateway queries the QUIC connection at the tunnel server according to hostpip and writes this message connection to the QUIC connection. The http connection request is converted, extracted and the like, converted into a serializable message object and written into the QUIC connection.
6. After receiving the request, the service stream at the edge side forwards the request to the pod corresponding to the request.
7. And writing the result of the access pod request back to the corresponding QUIC connection, and sending the result to the cloud.
8. the tunnel server writes the result of the request back to the http connected response. The QUIC connection is a tunnel, and only one connection exists between an edge node and a cloud. After the QUIC connection is established, all user http connection requests are multiplexed into the channel.
The connection establishing request of the QUIC of the invention is provided with a header, and the header needs to carry the host name and the host IP of the edge node and is used for uniquely marking the edge node to distinguish the edge node from other edge nodes.
The service of the invention is designed based on the QUIC protocol, the QUIC protocol is based on the UDP protocol, stable TCP connection and repeated handshake are not needed, and the invention can still have good performance in the weak network environment at the edge side.
Fig. 3 is a schematic diagram of an application of the cloud-based edge service access system based on the QUIC protocol in the current internet environment, where a QUIC connection is established between a core cloud and an automobile data transmission device, that is, a QUIC tunnel for accessing the edge service from the cloud is provided, so that the problem of data stream communication from the cloud to the edge service is solved, and the data access performance is improved through the QUIC protocol.
The characters referred to in part in the present invention have the following meanings:
QUIC: quick UDP Internet Connection, UDP-based low latency Internet transport layer protocol.
EdgeGateway: an edge gateway. tunnel server: and a tunnel server. service stream: a service flow component.
http: hyper Text Transfer Protocol HyperFile Transfer Protocol. A header: and a data head. Key: a keyword.
SessionID: the session ID. url: a uniform resource locator.
CNI: container Network Interface, Container Network Interface.
kubernets: abbreviated as K8s, is a Google open source container cluster management system.
Pod: the resource object is a basic unit of the kubernets system and is a resource object for running containerized applications on the kubernets system.
And (3) LB strategy: the Loadbalance strategy is a load balancing strategy.
The above description is only of the preferred embodiments of the present invention, and it should be noted that: it will be apparent to those skilled in the art that various modifications and adaptations can be made without departing from the principles of the invention and these are intended to be within the scope of the invention.
Claims (10)
1. A cloud access edge service method based on a QUIC protocol is used for system communication, the system comprises a cloud, an edge side and more than one user side, the edge side comprises more than one edge node, each edge node manages a plurality of pods in the form of a kubernets cluster, and the method is characterized in that: each edge node is provided with a service stream component service stream, and an edge gateway EdgeGateway and a tunnel server are arranged at the cloud end;
QUIC connection is established between the cloud and each edge node, and the steps are as follows:
the cloud end starts an EdgeGateway and a tunnel server and monitors requests from the edge node and the user end;
when each edge node is started, starting a corresponding service stream, and creating a QUIC connection, wherein the QUIC connection is used for establishing a data transmission channel between a cloud end and the edge node;
and monitoring the QUIC connection by a cloud tunnel server, and saving the QUIC connection by using the host IP and the hostname of the edge node as a key.
2. The cloud access edge service method based on QUIC protocol as claimed in claim 1, wherein: the cloud end access edge service step comprises:
s1, QUIC connection is established between the cloud and each edge node of the edge side;
s2, the Edgegateway receives a connection request initiated by a user terminal, wherein the connection request comprises service information to be accessed by the user terminal;
s3, the Edgegateway executes a reverse proxy process to generate a session Id for the current connection request; executing a load balancing strategy to obtain a real host IP of the edge node corresponding to the connection request and a port corresponding to the pod;
s4, the Edgegateway inquires the corresponding QUIC connection at the tunnel server according to the host IP, and writes the connection request connection initiated by the user side into the QUIC connection;
s5, continuously monitoring QUIC connection between the cloud and the edge node by the service stream of the edge side; after receiving a connection request initiated by a user side through QUIC connection, a service stream is forwarded to a pod corresponding to the request;
s6, the service stream of the edge side writes the access pod request result back to the corresponding QUIC connection and sends the access pod request result to the cloud;
s7, the cloud tunnel server sends a response message to the EdgeGateway, where the response message includes a result of responding to the connection request in step S3.
3. The cloud access edge service method based on QUIC protocol as claimed in claim 1, wherein: the service stream is used for creating a QUIC connection when an edge node is started, and the QUIC connection is used as a data channel for accessing edge services of the edge node by a cloud; the service stream receives a connection request sent by a user side and forwarded by the cloud through QUIC connection, forwards the connection request to a pod corresponding to the connection request, receives a response message of the pod and returns the response message to the cloud tunnel server through the QUIC connection;
the tunnel server is used for storing the QUIC connection established by the edge node and sending a response message of the pod returned by the edge node to the Edgegateway;
and the Edgegateway supports a user to define a load balancing strategy and a QUIC protocol, receives and analyzes the connection request sent by the user side, inquires the corresponding QUIC connection at the tunnel server according to the analyzed information, writes the connection request sent by the user side into the QUIC connection and then sends the connection request to the corresponding edge node.
4. The cloud access edge service method based on QUIC protocol as claimed in claim 1, wherein: the QUIC connection is provided with a data header, the header carries a host name hostname and a host IP of a corresponding edge node, and the tunnel server uses the host IP and the hostname of the edge node as keys to store the corresponding QUIC connection.
5. The cloud access edge service method based on QUIC protocol as claimed in claim 1, wherein: in step S3, the connection request initiated by the user side is an http request.
6. Method of cloud access edge service based on QUIC protocol according to claim 4, characterized in that: in step S4, the EdgeGateway queries kubernets by parsing the uniform resource locator url corresponding to the http connection request, and parses a specific host IP.
7. The cloud access edge service method based on QUIC protocol as claimed in claim 1, wherein: only one QUIC connection is established between the same edge node and the cloud, and the QUIC connection is used as a reusable data channel for the cloud to access the edge service of the edge node.
8. The utility model provides a system, includes high in the clouds, edge side and more than one user side, its characterized in that: the cloud end is provided with an edge gateway (Edgegateway) and a tunnel server (tunnel server), the edge side comprises more than one edge node, each edge node is provided with a service stream component service stream, and each edge node manages a plurality of pods in a kubernets cluster mode; wherein the content of the first and second substances,
the service stream is used for creating a QUIC connection when the edge node is started, and the QUIC connection is used as a data channel for accessing the edge service of the edge node by a cloud; the service stream receives a connection request sent by a user side and forwarded by the cloud through QUIC connection, forwards the connection request to a pod corresponding to the connection request, receives a response message of the pod and returns the response message to the cloud tunnel server through the QUIC connection;
the tunnel server is used for storing the QUIC connection established by the edge node and sending a response message of the pod returned by the edge node to the Edgegateway;
and the Edgegateway supports a user to define a load balancing strategy and a QUIC protocol, receives and analyzes the connection request sent by the user side, inquires the corresponding QUIC connection at the tunnel server according to the analyzed information, writes the connection request sent by the user side into the QUIC connection and then sends the connection request to the corresponding edge node.
9. The system of claim 7, wherein: the QUIC connection is provided with a data header, and the header carries a host name hostname and a host IP of a corresponding edge node;
and the Edgegateway executes reverse proxy and load balancing on the received connection request sent by the user side, analyzes a specific host IP, and inquires corresponding QUIC connection at the tunnel server according to the host IP.
10. A cloud service center for an edge node in a communication connection system, comprising: the method comprises the steps that an edge gateway Edgegateway and a tunnel server are included, all QUIC connections established by edge nodes are stored in the tunnel server, and response messages returned by the edge nodes are sent to the Edgegateway;
the Edgegateway supports a user to define a load balancing strategy and a QUIC protocol, monitors a connection request from the edge node and the user side, and can search a corresponding QUIC connection from the tunnel server according to the analyzed request information of the user side and write the connection request sent by the user side into the QUIC connection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110385933.7A CN112887433B (en) | 2021-04-12 | 2021-04-12 | Cloud access edge service method and system based on QUIC protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110385933.7A CN112887433B (en) | 2021-04-12 | 2021-04-12 | Cloud access edge service method and system based on QUIC protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112887433A true CN112887433A (en) | 2021-06-01 |
| CN112887433B CN112887433B (en) | 2021-07-27 |
Family
ID=76039936
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110385933.7A Active CN112887433B (en) | 2021-04-12 | 2021-04-12 | Cloud access edge service method and system based on QUIC protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112887433B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113259479A (en) * | 2021-06-18 | 2021-08-13 | 腾讯科技（深圳）有限公司 | Data processing method and equipment |
| CN113612675A (en) * | 2021-06-25 | 2021-11-05 | 北京劲群科技有限公司 | Distributed intranet transparent implementation architecture and method |
| CN114143315A (en) * | 2021-11-30 | 2022-03-04 | 阿里巴巴（中国）有限公司 | Edge cloud system, host access method and device |
| CN114363077A (en) * | 2022-01-10 | 2022-04-15 | 河南能睿科技有限公司 | Management system based on safety access service edge |
| CN114584558A (en) * | 2022-01-17 | 2022-06-03 | 深圳渊联技术有限公司 | Cloud edge cooperative distributed API gateway system and API calling method |
| CN114827197A (en) * | 2022-03-31 | 2022-07-29 | 远景智能国际私人投资有限公司 | Service communication method, device, equipment and medium based on Internet of things |
| CN115225644A (en) * | 2022-07-27 | 2022-10-21 | 天翼云科技有限公司 | Load balancing system and data packet distribution method |
| CN115473898A (en) * | 2022-11-14 | 2022-12-13 | 杭州欧若数网科技有限公司 | Graph database management method and system in edge computing scene |
| WO2023274146A1 (en) * | 2021-07-01 | 2023-01-05 | 华为技术有限公司 | Remote access method, electronic device, and storage medium |
| CN116436671A (en) * | 2023-04-14 | 2023-07-14 | 北京志凌海纳科技有限公司 | Method, system, device and medium for Kubernetes cluster access in private network |
| WO2024016593A1 (en) * | 2022-07-19 | 2024-01-25 | 天翼云科技有限公司 | Edge node access method and apparatus |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160119196A1 (en) * | 2014-10-27 | 2016-04-28 | Cisco Technology, Inc. | Multipath Provisioning of L4-L7 Traffic in a Network |
| CN108449633A (en) * | 2018-03-22 | 2018-08-24 | 烽火通信科技股份有限公司 | Set-top box cloud frame based on NFV and service implementation method |
| CN110149388A (en) * | 2019-05-16 | 2019-08-20 | 北京字节跳动网络技术有限公司 | Connection method, device and the equipment of HTTPDNS server |
| CN111567011A (en) * | 2018-01-29 | 2020-08-21 | 华为技术有限公司 | Method for improving QoE of video service and WEB service by using cross-layer information |
| WO2020171957A1 (en) * | 2019-02-22 | 2020-08-27 | Vmware, Inc. | Virtual service networks |
| WO2020232404A1 (en) * | 2019-05-16 | 2020-11-19 | Intel Corporation | Technologies for control and management of multiple traffic steering services |
| US20200366619A1 (en) * | 2017-12-27 | 2020-11-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatus and method for controlling communication between an edge cloud server and a plurality of clients via a radio access network |
| CN112115090A (en) * | 2019-06-20 | 2020-12-22 | 英特尔公司 | Multi-protocol support for transactions |
| CN112383416A (en) * | 2020-11-02 | 2021-02-19 | 之江实验室 | Kubeedge and EdgeX fountain based intelligent edge device control platform |
| CN112532729A (en) * | 2020-11-30 | 2021-03-19 | 北京百度网讯科技有限公司 | Data synchronization method and device for edge device and cloud end |
| US20210099482A1 (en) * | 2019-09-26 | 2021-04-01 | Radware, Ltd. | DETECTION AND MITIGATION DDoS ATTACKS PERFORMED OVER QUIC COMMUNICATION PROTOCOL |
| CN112637177A (en) * | 2020-12-17 | 2021-04-09 | 下一代互联网重大应用技术（北京）工程研究中心有限公司 | Data encryption transmission method, device, equipment and medium |
-
2021
- 2021-04-12 CN CN202110385933.7A patent/CN112887433B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160119196A1 (en) * | 2014-10-27 | 2016-04-28 | Cisco Technology, Inc. | Multipath Provisioning of L4-L7 Traffic in a Network |
| US20200366619A1 (en) * | 2017-12-27 | 2020-11-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatus and method for controlling communication between an edge cloud server and a plurality of clients via a radio access network |
| CN111567011A (en) * | 2018-01-29 | 2020-08-21 | 华为技术有限公司 | Method for improving QoE of video service and WEB service by using cross-layer information |
| CN108449633A (en) * | 2018-03-22 | 2018-08-24 | 烽火通信科技股份有限公司 | Set-top box cloud frame based on NFV and service implementation method |
| WO2020171957A1 (en) * | 2019-02-22 | 2020-08-27 | Vmware, Inc. | Virtual service networks |
| CN110149388A (en) * | 2019-05-16 | 2019-08-20 | 北京字节跳动网络技术有限公司 | Connection method, device and the equipment of HTTPDNS server |
| WO2020232404A1 (en) * | 2019-05-16 | 2020-11-19 | Intel Corporation | Technologies for control and management of multiple traffic steering services |
| CN112115090A (en) * | 2019-06-20 | 2020-12-22 | 英特尔公司 | Multi-protocol support for transactions |
| US20210099482A1 (en) * | 2019-09-26 | 2021-04-01 | Radware, Ltd. | DETECTION AND MITIGATION DDoS ATTACKS PERFORMED OVER QUIC COMMUNICATION PROTOCOL |
| CN112383416A (en) * | 2020-11-02 | 2021-02-19 | 之江实验室 | Kubeedge and EdgeX fountain based intelligent edge device control platform |
| CN112532729A (en) * | 2020-11-30 | 2021-03-19 | 北京百度网讯科技有限公司 | Data synchronization method and device for edge device and cloud end |
| CN112637177A (en) * | 2020-12-17 | 2021-04-09 | 下一代互联网重大应用技术（北京）工程研究中心有限公司 | Data encryption transmission method, device, equipment and medium |
Non-Patent Citations (1)
| Title |
|---|
| 杨鑫等: "MEC的云边协同分析", 《中兴通讯技术》 * |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113259479A (en) * | 2021-06-18 | 2021-08-13 | 腾讯科技（深圳）有限公司 | Data processing method and equipment |
| CN113259479B (en) * | 2021-06-18 | 2022-12-20 | 腾讯科技（深圳）有限公司 | Data processing method and equipment |
| CN113612675A (en) * | 2021-06-25 | 2021-11-05 | 北京劲群科技有限公司 | Distributed intranet transparent implementation architecture and method |
| CN113612675B (en) * | 2021-06-25 | 2022-07-12 | 北京劲群科技有限公司 | Distributed intranet transparent implementation architecture and method |
| WO2023274146A1 (en) * | 2021-07-01 | 2023-01-05 | 华为技术有限公司 | Remote access method, electronic device, and storage medium |
| CN114143315A (en) * | 2021-11-30 | 2022-03-04 | 阿里巴巴（中国）有限公司 | Edge cloud system, host access method and device |
| CN114363077A (en) * | 2022-01-10 | 2022-04-15 | 河南能睿科技有限公司 | Management system based on safety access service edge |
| CN114363077B (en) * | 2022-01-10 | 2022-09-23 | 河南能睿科技有限公司 | Management system based on safety access service edge |
| CN114584558B (en) * | 2022-01-17 | 2024-03-15 | 深圳渊联技术有限公司 | Cloud edge cooperative distributed API gateway system and API calling method |
| CN114584558A (en) * | 2022-01-17 | 2022-06-03 | 深圳渊联技术有限公司 | Cloud edge cooperative distributed API gateway system and API calling method |
| CN114827197B (en) * | 2022-03-31 | 2023-09-12 | 远景智能国际私人投资有限公司 | Service communication method, device, equipment and medium based on Internet of things |
| CN114827197A (en) * | 2022-03-31 | 2022-07-29 | 远景智能国际私人投资有限公司 | Service communication method, device, equipment and medium based on Internet of things |
| WO2024016593A1 (en) * | 2022-07-19 | 2024-01-25 | 天翼云科技有限公司 | Edge node access method and apparatus |
| CN115225644A (en) * | 2022-07-27 | 2022-10-21 | 天翼云科技有限公司 | Load balancing system and data packet distribution method |
| CN115225644B (en) * | 2022-07-27 | 2023-11-03 | 天翼云科技有限公司 | Load balancing system and data packet distribution method |
| CN115473898A (en) * | 2022-11-14 | 2022-12-13 | 杭州欧若数网科技有限公司 | Graph database management method and system in edge computing scene |
| CN116436671B (en) * | 2023-04-14 | 2023-11-17 | 北京志凌海纳科技有限公司 | Method, system, device and medium for Kubernetes cluster access in private network |
| CN116436671A (en) * | 2023-04-14 | 2023-07-14 | 北京志凌海纳科技有限公司 | Method, system, device and medium for Kubernetes cluster access in private network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112887433B (en) | 2021-07-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112887433B (en) | Cloud access edge service method and system based on QUIC protocol | |
| WO2020228505A1 (en) | Method, device, and system for selecting mobile edge computing node | |
| US9923786B2 (en) | System and method for performing a service discovery for virtual networks | |
| US20200228433A1 (en) | Computer-readable recording medium including monitoring program, programmable device, and monitoring method | |
| KR101987784B1 (en) | Software-defined network-based method and system for implementing content distribution network | |
| WO2020135575A1 (en) | System and method for obtaining network topology, and server | |
| CN102238226B (en) | Conversation shift on the network centered by content | |
| US9401885B2 (en) | Data push service method and system using data pull model | |
| US20100088427A1 (en) | Selective Routing of Data Transmission Between Clients | |
| WO2008141538A1 (en) | Method, device and system for distributing file data | |
| WO2022148363A1 (en) | Data transmission method and data transmission server | |
| Chanda et al. | Contentflow: Mapping content to flows in software defined networks | |
| CN106131138B (en) | A kind of real-time supplying system of display data and method based on non-obstruction queue | |
| CN109451014B (en) | WebService agent system and transparent agent method thereof | |
| CN104468704B (en) | Support the Web server system and processing method of content center network | |
| WO2021135950A1 (en) | Data management method and system, associated subsystem and computer readable medium | |
| WO2017219813A1 (en) | Traffic processing method and transparent buffer system | |
| CN105450703A (en) | Data caching method and data caching device | |
| US20230107093A1 (en) | Data download method and apparatus, computer device, and storage medium | |
| CN115379010B (en) | Container network construction method, device, equipment and storage medium | |
| CN114501593B (en) | Network slice access method, device, system and storage medium | |
| JP2017500679A (en) | Media resource feedback method, apparatus, program, and recording medium | |
| WO2024021405A1 (en) | Data transmission system and method | |
| CN113259423A (en) | Method and device for client networking access in P2P system | |
| WO2013120325A1 (en) | Browser-to-browser direct communication method, device and communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |