CN106603728B - HTTPS acceleration method and system, data center and node service cloud - Google Patents
HTTPS acceleration method and system, data center and node service cloud Download PDFInfo
- Publication number
- CN106603728B CN106603728B CN201710074638.3A CN201710074638A CN106603728B CN 106603728 B CN106603728 B CN 106603728B CN 201710074638 A CN201710074638 A CN 201710074638A CN 106603728 B CN106603728 B CN 106603728B
- Authority
- CN
- China
- Prior art keywords
- domain name
- client
- virtual domain
- request
- convergence
- 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.)
- Active
Links
- 230000001133 acceleration Effects 0.000 title claims abstract description 82
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000006854 communication Effects 0.000 claims abstract description 17
- 238000004891 communication Methods 0.000 claims abstract description 16
- 238000012545 processing Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses an HTTPS acceleration method and system, a data center and a node service cloud, and belongs to the technical field of information. The method comprises the following steps: the client converges the destination domain name according to a convergence rule to generate a virtual domain name and sends the virtual domain name to the acceleration server; the acceleration server restores the virtual domain name into a destination domain name according to the convergence rule, and establishes communication connection with the source server according to the destination domain name. Therefore, the invention can reduce the SSL/TLS connection time for a plurality of times to 1 time in one access, thereby achieving the effect of reducing the number of SSL/TLS connections, effectively improving the access speed of HTTPS and reducing the consumption of computing performance.
Description
Technical Field
The invention relates to the technical field of communication, in particular to an HTTPS acceleration method and system, a data center and a node service cloud.
Background
HTTPS (HyperText Transfer Protocol over Secure Socket Layer) is an HTTP (HyperText Transfer Protocol) channel targeted for security, and simply a Secure version of HTTP. Namely, SSL (Secure Sockets Layer protocol)/TLS (Transport Layer protocol) layers are added under HTTP, the Security basis of HTTPS is SSL/TLS, and therefore SSL/TLS is needed for the detailed content of encryption. It is a URI scheme (abstract identifier system) that is syntactically similar to the http system. For secure HTTP data transfer.
At present, in a network environment, various tampering and hijacking are in endless, and in addition to the requirement of data privacy protection, great companies complete the transformation of the HTTPS in sequence, so that the HTTPS becomes a future development trend. However, HTTPs has 2 distinct disadvantages over HTTP:
1. the calculation performance consumption is large: because the SSL/TLS handshake adopts an asymmetric encryption algorithm and is very power-consuming to the server, the data actually transmitted uses a symmetric encryption algorithm, which is less power-consuming but is power-consuming compared with the asymmetric encryption algorithm.
2. The access speed is slow: compared with HTTP, HTTPs has a slow access speed, mainly slow SSL/TLS handshake, and generally 2 to 3 more RTTs (Round-Trip Time).
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention provide an HTTPS acceleration method and system, a data center, and a node service cloud. The technical scheme is as follows:
in a first aspect, an HTTPS acceleration method provided in an embodiment of the present invention includes:
the client converges the destination domain name according to a convergence rule to generate a virtual domain name and sends the virtual domain name to the acceleration server;
the acceleration server restores the virtual domain name into a destination domain name according to the convergence rule, and establishes communication connection with the source server according to the destination domain name.
Optionally, the method further comprises:
the data center establishes a convergence rule for the destination domain name according to the first request data request, and sends a second request data request for determining convergence to the client according to the convergence rule.
Optionally, the method further comprises:
and the client converges the destination domain name according to the second request data request to generate the virtual domain name.
Optionally, the method further comprises:
the client adds an identification field into the generated virtual domain name, and the acceleration server determines to restore the virtual domain name according to the identification field.
In a second aspect, an HTTPS acceleration system provided by an embodiment of the present invention includes:
the client is used for converging the target domain name according to the convergence rule to generate a virtual domain name and sending the virtual domain name;
and the acceleration server is used for receiving the virtual domain name, reducing the virtual domain name into a destination domain name according to a convergence rule, and establishing communication connection with the source server through the destination domain name.
Optionally, the system further comprises:
and the data center is used for receiving the first request data request, establishing a convergence rule for the destination domain name according to the first request data request, and sending a second request data request for determining convergence to the client according to the convergence rule.
Optionally, the client is further configured to converge the destination domain name according to the second request data request to generate the virtual domain name.
Optionally, the client is further configured to add an identification field in the generated virtual domain name;
and the acceleration server is also used for determining to restore the virtual domain name according to the identification field.
Optionally, the client comprises:
and the virtual domain name generation module is used for converging the target domain name to generate a virtual domain name.
In a third aspect, an embodiment of the present invention provides a data center, including:
a receiving module, configured to receive a first request data request;
the processing module is used for establishing a convergence rule for the destination domain name according to the first request data request;
and the sending module is used for sending the convergence rule and determining a converged second request data request to the client.
In a fourth aspect, an embodiment of the present invention provides a node service cloud, including:
the data center is used for establishing a convergence rule for the destination domain name according to a first request data request sent by the client and feeding back the convergence rule to the client;
and the acceleration server is used for receiving the virtual domain name sent by the client, restoring the virtual domain name into a destination domain name according to a convergence rule, and establishing communication connection with the source server through the destination domain name.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
according to the HTTPS acceleration method provided by the embodiment of the invention, a target domain name is converged by a client according to a convergence rule to generate a virtual domain name and the virtual domain name is sent to an acceleration server; the acceleration server restores the virtual domain name into a destination domain name according to the convergence rule, and establishes communication connection with the source server according to the destination domain name. Therefore, the invention can reduce the SSL/TLS connection time for a plurality of times to 1 time in one access, thereby achieving the effect of reducing the number of SSL/TLS connections, effectively improving the access speed of HTTPS and reducing the consumption of computing performance.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for a user of ordinary skill in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of an HTTPS acceleration method according to an embodiment of the present invention;
fig. 2 is a flowchart of another HTTPS acceleration method according to an embodiment of the present invention;
fig. 3 is a flowchart of another HTTPS acceleration method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an HTTPS acceleration system according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of another HTTPS acceleration system according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another HTTPS acceleration system according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a data center according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a node service cloud according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
The embodiment of the invention provides an HTTPS acceleration method, which can be applied to a CDN (content delivery Network), and the method needs to proxy an application client to request flow, change a request method of the method and embed SDK assistance in the application client, so that the execution of the method needs to embed SDK (Software Development Kit) in the application client in the CDN, the SDK proxies an in-application request through the application client, reads domain name convergence configuration taken from a data center of the CDN, converges a target domain name to be processed into a negotiated virtual domain name, and reads the virtual domain name and restores the original domain name to be returned to the source normally after the application client transmits the request to an acceleration server of the CDN. The method is applied to the communication process of the acceleration server of the CDN, and the purpose of reducing a plurality of original HTTPS connections to one HTTPS connection is achieved.
The process flow shown in fig. 1-3 will be described in detail below with reference to the following embodiments, which may be as follows:
In this embodiment, the client 1 may converge a plurality of destination domain names into one virtual domain name according to a preset convergence rule, and send the virtual domain name to the acceleration server 2, so that, during this access, the SSL/TLS handshake connection between the client 1 and the acceleration server 2 only needs to be established once. Therefore, in the access, the time loss of (N-1) SSL/TLS handshake is theoretically saved between the client 1 and the acceleration server 2, wherein N is the number of destination domain names in the access. For example, the client 1 needs to access a page in the kyoto, where the page includes N different domain names (assumed to be a.jd.com, b.jd.com, etc.), converge the N different domain names included in the page according to the convergence rule to generate a virtual domain name (assumed to be a.juanpi.com), and the client 1 sends the virtual domain name to the acceleration server 2.
The establishment of the convergence rule requires the client 1 to negotiate with the data center 3 served by the CDN node. Referring to fig. 2, optionally, before step 100, the method further comprises:
In this embodiment, the data center 3 may configure the destination domain name according to the first request data request, complete the negotiation between the client 1 and the data center 3 for the destination domain name, and after the negotiation, when the client 1 needs to access the destination domain name, the client 1 may converge the destination domain name to generate the virtual domain name. In this step, a convergence rule should be set in the client 1 and the acceleration server 2 in advance.
In this embodiment, the convergence rule may also be established when the client 1 needs to access the destination domain name; referring to fig. 3, optionally, step 100 specifically includes:
The data center 3 establishes a convergence rule for the destination domain name according to the first request data request, because the data center 3 and the acceleration server 2 are both included in the CDN node server, the data center 3 can provide the convergence rule for the acceleration server 2, so that the acceleration server 2 can identify and restore the virtual domain name sent by the client 1.
Step 030, the client 1 converges the destination domain name according to the second request data request to generate a virtual domain name.
The client 1 determines a convergence rule for the destination domain name according to the second request data, and converges the destination domain name to generate the virtual domain name.
In this embodiment, the convergence of the client 1 on the destination domain name can be completed by SDK.
The acceleration server 2 may restore the virtual domain name to the destination domain name according to a preset convergence rule, or restore the virtual domain name to the destination domain name according to a convergence rule established by the data center 3. After the acceleration server 2 restores the virtual domain name to the destination domain name, the acceleration server 2 returns to the source normally through the destination domain name, establishes communication connection with the source server, and completes the access.
In this embodiment, in order to facilitate the server 2 to quickly identify the virtual domain name, the method further includes:
the client 1 adds identification information into the generated virtual domain name, and the acceleration server 2 restores the virtual domain name according to the identification information. Specifically, the client 1 adds an identification field (for example, X-App-Host, X is a virtual domain name, and App-Host is an identification field) to the generated virtual domain name, and the acceleration server 2 determines to restore the virtual domain name according to the identification field.
According to the HTTPS acceleration method provided by the embodiment of the invention, a target domain name is converged by a client 1 according to a convergence rule to generate a virtual domain name and the virtual domain name is sent to an acceleration server 2; the acceleration server 2 restores the virtual domain name to a destination domain name according to the convergence rule, and establishes communication connection with the source server according to the destination domain name. Therefore, the method can reduce the SSL/TLS connection time for multiple times to 1 time in one access, thereby achieving the effect of reducing the number of SSL/TLS connections, effectively improving the HTTPS access speed and reducing the consumption of computing performance.
Based on the same technical concept, referring to fig. 4, an embodiment of the present invention further provides an HTTPS acceleration system, including:
the client 1 is used for converging the destination domain name according to a convergence rule to generate a virtual domain name and sending the virtual domain name;
and the acceleration server 2 is used for receiving the virtual domain name, reducing the virtual domain name into a destination domain name according to a convergence rule, and establishing communication connection with the source server through the destination domain name.
In this embodiment, the client 1 may converge a plurality of destination domain names into one virtual domain name according to a preset convergence rule, and send the virtual domain name to the acceleration server 2, so that, during this access, the SSL/TLS handshake connection between the client 1 and the acceleration server 2 only needs to be established once. Therefore, in the access, the time loss of (N-1) SSL/TLS handshake is theoretically saved between the client 1 and the acceleration server 2, wherein N is the number of destination domain names in the access. For example, the client 1 needs to access a page in the kyoto, where the page includes N different domain names (assumed to be a.jd.com, b.jd.com, etc.), converge the N different domain names included in the page according to the convergence rule to generate a virtual domain name (assumed to be a.juanpi.com), and the client 1 sends the virtual domain name to the acceleration server 2.
The establishment of the convergence rule requires the client 1 to negotiate with the data center 3 performing the CND node service. Optionally, the client 1 is further configured to send a first request data request for configuring the destination domain name.
In this embodiment, the data center 3 may configure the destination domain name according to the first request data request, complete the negotiation between the client 1 and the data center 3 for the destination domain name, and after the negotiation, when the client 1 needs to access the destination domain name, the client 1 may converge the destination domain name to generate the virtual domain name. In this step, a convergence rule should be set in the client 1 and the acceleration server 2 in advance.
Referring to fig. 5, optionally, the system further comprises:
the data center 3 is configured to receive the first request data request, establish a convergence rule for the destination domain name according to the first request data request, and send a second request data request for determining convergence to the client 1 according to the convergence rule.
The data center 3 establishes a convergence rule for the destination domain name according to the first request data request, because the data center 3 and the acceleration server 2 are both included in the CDN node server, the data center 3 can provide the convergence rule for the acceleration server 2, so that the acceleration server 2 can identify and restore the virtual domain name sent by the client 1.
Optionally, the client 1 is further configured to converge the destination domain name according to the second request data request to generate a virtual domain name.
Referring to fig. 6, optionally, the client 1 includes:
the virtual domain name generating module 11 is configured to converge the destination domain name to generate a virtual domain name.
In this embodiment, the virtual domain name generation module 11 may be implemented by embedding an SDK in the client 1, and the convergence of the destination domain name is implemented by the SDK.
Optionally, in order to facilitate the acceleration of the server 2 to quickly identify the virtual domain name, the client 1 is further configured to add an identification field in the generation of the virtual domain name;
and the acceleration server 2 is further configured to determine to restore the virtual domain name according to the identification field.
According to the HTTPS acceleration system provided by the embodiment of the invention, a target domain name is converged by a client 1 according to a convergence rule to generate a virtual domain name, and the virtual domain name is sent to an acceleration server 2; the acceleration server 2 restores the virtual domain name to a destination domain name according to the convergence rule, and establishes communication connection with the source server according to the destination domain name. Therefore, the system can reduce the SSL/TLS connection time for multiple times to 1 time in one access, thereby achieving the effect of reducing the number of the SSL/TLS connections, effectively improving the access speed of the HTTPS and reducing the consumption of the computing performance.
Based on the same technical concept, referring to fig. 7, an embodiment of the present invention provides a data center 3, including:
a receiving module 31, configured to receive a first request data request;
a processing module 32, configured to establish a convergence rule for the destination domain name according to the first request data request;
a sending module 33, configured to send the convergence rule and the second request data request for determining convergence to the client.
In this embodiment, the data center 3 may configure the destination domain name according to the first request data request, complete the negotiation between the client 1 and the data center 3 for the destination domain name, and after the negotiation, when the client 1 needs to access the destination domain name, the client 1 may converge the destination domain name to generate the virtual domain name.
The data center 3 establishes a convergence rule for the destination domain name according to the first request data request, because the data center 3 and the acceleration server 2 are both included in the CDN node server, the data center 3 can provide the convergence rule for the acceleration server 2, so that the acceleration server 2 can identify and restore the virtual domain name sent by the client 1.
In the data center provided by the embodiment of the invention, the first request data request is received through the receiving module 31; the processing module 32 is used for establishing a convergence rule for the destination domain name according to the first request data request; a sending module 33, sending the convergence rule and the second request data request determined to be converged to the client. In this way, the data center can perform convergence configuration on the destination domain name according to the request of the client.
Based on the same technical concept, referring to fig. 8, an embodiment of the present invention provides a node service cloud, including:
the data center 3 is used for establishing a convergence rule for the destination domain name according to a first request data request sent by the client 1 and feeding back the convergence rule to the client 1;
and the acceleration server 2 is used for receiving the virtual domain name sent by the client 1, restoring the virtual domain name into a destination domain name according to a convergence rule, and establishing communication connection with the source server through the destination domain name.
The node service cloud end is used for node service of the CDN,
according to the node service cloud provided by the embodiment of the invention, a convergence rule is established for a destination domain name through the data center 3 according to a first request data request sent by the client 1 and the convergence rule is fed back to the client 1; the acceleration server 2 receives the virtual domain name sent by the client 1, restores the virtual domain name into a destination domain name according to a convergence rule, and establishes communication connection with the source server through the destination domain name. Therefore, the cloud service node can reduce the SSL/TLS connection time for multiple times to 1 time in one access, so that the effect of reducing the number of the SSL/TLS connections is achieved, the HTTPS access speed can be effectively improved, and meanwhile, the calculation performance consumption is reduced.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
It is also noted that the term "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion, such that a good or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such good or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a commodity or system that includes the element.
The foregoing description shows and describes several preferred embodiments of the invention, but as aforementioned, it is to be understood that the invention is not limited to the forms disclosed herein, but is not to be construed as excluding other embodiments and is capable of use in various other combinations, modifications, and environments and is capable of changes within the scope of the inventive concept as expressed herein, commensurate with the above teachings, or the skill or knowledge of the relevant art. And that modifications and variations may be effected by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (11)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710074638.3A CN106603728B (en) | 2017-02-11 | 2017-02-11 | HTTPS acceleration method and system, data center and node service cloud |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710074638.3A CN106603728B (en) | 2017-02-11 | 2017-02-11 | HTTPS acceleration method and system, data center and node service cloud |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106603728A CN106603728A (en) | 2017-04-26 |
| CN106603728B true CN106603728B (en) | 2020-03-31 |
Family
ID=58585593
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710074638.3A Active CN106603728B (en) | 2017-02-11 | 2017-02-11 | HTTPS acceleration method and system, data center and node service cloud |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106603728B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242336A (en) * | 2008-03-13 | 2008-08-13 | 杭州华三通信技术有限公司 | Method of Remotely Accessing Intranet Web Server and Web Proxy Server |
| WO2012163055A1 (en) * | 2011-11-18 | 2012-12-06 | 华为技术有限公司 | Method and related apparatus for transmitting media content |
| CN103139258A (en) * | 2011-11-30 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | A method, device and system for processing page access requests of mobile terminals |
| CN104584011A (en) * | 2012-06-28 | 2015-04-29 | 茨特里克斯系统公司 | Methods and systems for secure in-network insertion of WEB content and WEB services |
| CN105556501A (en) * | 2013-05-30 | 2016-05-04 | 电子湾有限公司 | Systems and methods of token piggybacking |
| CN106100963A (en) * | 2016-08-16 | 2016-11-09 | 重庆邮电大学 | A kind of software VPN realization method based on meaning conversion in full |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9027086B2 (en) * | 2013-02-01 | 2015-05-05 | Vidder, Inc. | Securing organizational computing assets over a network using virtual domains |
-
2017
- 2017-02-11 CN CN201710074638.3A patent/CN106603728B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242336A (en) * | 2008-03-13 | 2008-08-13 | 杭州华三通信技术有限公司 | Method of Remotely Accessing Intranet Web Server and Web Proxy Server |
| WO2012163055A1 (en) * | 2011-11-18 | 2012-12-06 | 华为技术有限公司 | Method and related apparatus for transmitting media content |
| CN103139258A (en) * | 2011-11-30 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | A method, device and system for processing page access requests of mobile terminals |
| CN104584011A (en) * | 2012-06-28 | 2015-04-29 | 茨特里克斯系统公司 | Methods and systems for secure in-network insertion of WEB content and WEB services |
| CN105556501A (en) * | 2013-05-30 | 2016-05-04 | 电子湾有限公司 | Systems and methods of token piggybacking |
| CN106100963A (en) * | 2016-08-16 | 2016-11-09 | 重庆邮电大学 | A kind of software VPN realization method based on meaning conversion in full |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106603728A (en) | 2017-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111213128B (en) | Implement blockchain-based web services | |
| US10411956B2 (en) | Enabling planned upgrade/downgrade of network devices without impacting network sessions | |
| TWI378700B (en) | Reliable messaging using redundant message streams in a high speed, low latency data communications environment | |
| CN112751898B (en) | Load balancing method, device, medium and equipment | |
| CN108401011A (en) | The accelerated method of handshake request, equipment and fringe node in content distributing network | |
| EP3142306B1 (en) | Openflow communication method, system, controller, and service gateway | |
| CN104580253A (en) | Method and device for processing user data | |
| CN105103522A (en) | Law latency server-side redirection of UDP-based transport protocols traversing client-side NAT firewall | |
| US10476992B1 (en) | Methods for providing MPTCP proxy options and devices thereof | |
| US11005732B1 (en) | Methods for improved service chain classification and management and devices thereof | |
| EP3128713B1 (en) | Page push method and system | |
| US7949704B2 (en) | Administration of a broker-based publish/subscribe messaging system | |
| US11030661B2 (en) | Opt-out enforcement for systems using non-cookie browser identification | |
| CN112751897A (en) | Load balancing method, device, medium and equipment | |
| US9882957B1 (en) | Client-side endpoint specification in a network service request | |
| CN110166577A (en) | Distributed Application cluster conversation processing system and method | |
| CN115361143A (en) | Cross-domain data transmission method and device, electronic device, computer readable medium | |
| CN114584603A (en) | Method and device for connecting desktop client software and server and readable storage medium | |
| CN102170456A (en) | Method, device and system for acquiring content in PPN (peer-to-peer network) | |
| CN102065143B (en) | Communication method and system based on HTTP (hyper Text Transfer Protocol), HTTP server and HTTP client | |
| CN107547352A (en) | Document sending method, apparatus and system | |
| CN106603728B (en) | HTTPS acceleration method and system, data center and node service cloud | |
| EP4531345A1 (en) | Methods for generating client-executable actions through tls parameters and devices thereof | |
| WO2016155266A1 (en) | Data sharing method and device for virtual desktop | |
| EP2800330A1 (en) | Secret key management method for multi-network platform |
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 |