WO2023109913A1 - 握手连接的方法、电子装置、电子设备以及介质 - Google Patents

握手连接的方法、电子装置、电子设备以及介质 Download PDF

Info

Publication number
WO2023109913A1
WO2023109913A1 PCT/CN2022/139361 CN2022139361W WO2023109913A1 WO 2023109913 A1 WO2023109913 A1 WO 2023109913A1 CN 2022139361 W CN2022139361 W CN 2022139361W WO 2023109913 A1 WO2023109913 A1 WO 2023109913A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration information
edge server
client
handshake
server
Prior art date
Application number
PCT/CN2022/139361
Other languages
English (en)
French (fr)
Inventor
卢江滨
Original Assignee
贵州白山云科技股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 贵州白山云科技股份有限公司 filed Critical 贵州白山云科技股份有限公司
Publication of WO2023109913A1 publication Critical patent/WO2023109913A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/026—Details of "hello" or keep-alive messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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
    • 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

Definitions

  • Embodiments of the present disclosure relate to, but are not limited to, a handshake connection method, an electronic device, an electronic device, and a medium.
  • QUIC is a low-latency Internet transmission protocol based on the UDP protocol. On the basis of UDP, it provides reliable, orderly, secure and faster transmission services. These advantages are especially important for CDN networks facing a large number of users. Therefore, business platforms use the QUIC protocol more and more frequently for business processing.
  • the QUIC protocol can transmit faster, one of the reasons is that it can solve the handshake delay problem existing in the existing TCP network transmission protocol. Specifically, through the transmission of the QUIC protocol, the client and the server can achieve the purpose of business data transmission between the two parties through a handshake interaction.
  • the disclosure provides a handshake connection method, an electronic device, an electronic device and a medium.
  • a method for handshaking connections which is applied to a target edge server, including:
  • the configuration information includes server parameters required to complete the handshake connection with the client;
  • the acquisition of configuration information includes:
  • the method further includes:
  • the sending the configuration information to at least one other edge server associated with the target edge server includes:
  • the sending the configuration information to at least one other edge server associated with the target edge server includes:
  • the sending the configuration information to at least one other edge server associated with the target edge server includes:
  • an electronic device for handshake connection which is applied to an edge server, including:
  • the configuration information includes server parameters required to complete the QUIC handshake connection with the client;
  • the configuration information in a local preset storage area after storing the configuration information in a local preset storage area, it further includes:
  • a service processing device in a cloud computing network which is characterized in that it is applied to a target edge server, including:
  • the first receiving module is configured to receive the first handshake request sent by the client based on the QUIC protocol;
  • the first obtaining module is configured to obtain configuration information, and the configuration information includes server parameters required to complete the QUIC handshake connection with the client;
  • a sending module configured to send the configuration information to the client to complete the handshake connection; and send the configuration information to at least one other edge server associated with the target edge server, so that the When other edge servers receive the handshake request sent by the client based on the QUIC protocol, they complete the QUIC handshake connection with the client according to the configuration information.
  • a service processing device in a cloud computing network which is characterized in that it is applied to an edge server, including:
  • the second obtaining module is configured to obtain the configuration information sent by the target edge server, the configuration information includes server parameters required to complete the QUIC handshake connection with the client;
  • a storage module configured to store the configuration information in a local preset storage area
  • the second receiving module is configured to complete the handshake connection with the client according to the configuration information when receiving the first handshake request sent by the client based on the QUIC protocol.
  • an electronic device comprising:
  • the display is used for displaying with the memory to execute the executable instruction to complete the operation of any one of the methods for the handshake connection described above.
  • a computer-readable storage medium for storing computer-readable instructions, and when the instructions are executed, operations of any one of the above-mentioned handshake connection methods are performed.
  • a computer program product including a computer program, and the computer program is used to be executed by a processor to implement the method for handshaking connection described in any one of the above.
  • the edge server after the edge server receives the initial handshake request sent by the client for the first time based on the QUIC protocol, it can obtain configuration information including server parameters required to complete the QUIC handshake connection with the client, and send the configuration information to the client for Complete the handshake connection; and, send the configuration information to at least one other edge server associated with the target edge server, so that when other edge servers receive the handshake request sent by the client based on the QUIC protocol, communicate with the client according to the configuration information Complete the QUIC handshake connection.
  • the configuration information can also be sent to at least one other edge server associated with it, so as to reach other edges
  • the server can realize the purpose of exchanging business data without performing an initial handshake request with the client, thereby improving the business processing efficiency under the QUIC protocol.
  • Fig. 1 is a schematic diagram of an exemplary process architecture of a working principle of a handshake connection in the related art according to an exemplary embodiment
  • Fig. 2 is a schematic diagram of a handshake connection method according to an exemplary embodiment
  • Fig. 3 is a schematic diagram of a system architecture of a handshake connection according to an exemplary embodiment
  • Fig. 4 is a schematic diagram showing another handshake connection method according to an exemplary embodiment
  • 5-6 are schematic diagrams of an electronic device connected by handshake according to an exemplary embodiment
  • Fig. 7 is a schematic diagram of another electronic device for handshake connection according to an exemplary embodiment.
  • All directional indications (such as up, down, left, right, front, back%) in the embodiments of the present disclosure are only used to explain the relative positional relationship between the various components in a certain posture (as shown in the drawings) , sports conditions, etc., if the specific posture changes, the directional indication also changes accordingly.
  • the technical solution of the present disclosure can avoid the problem that every time a client connects to a server that has never interacted with it, it needs to complete an initial handshake process with it and obtain corresponding configuration information before performing data interaction, thereby affecting business processing efficiency.
  • FIGS. 1-5 A method for performing a handshake connection according to an exemplary embodiment of the present disclosure is described below with reference to FIGS. 1-5 .
  • the following application scenarios are only shown for easy understanding of the spirit and principle of the present disclosure, and the implementation manners of the present disclosure are not limited in this respect. On the contrary, the embodiments of the present disclosure can be applied to any applicable scene.
  • FIG. 1 shows a schematic diagram of an exemplary method in which the working principle of completing a complete handshake connection between a client and an edge server according to an embodiment of the present disclosure can be applied.
  • FIG. 1 it includes the process of completing an initial handshake request (ie 1RTT) between the client and the edge server and the subsequent process of a complete handshake request (ie 0RTT) between the two, including:
  • Step 1 The client first determines whether the configuration information of the edge server is stored locally (the configuration information includes the server parameters required to complete the QUIC handshake connection with the two), if not, it can send an initial handshake request (ie Inchoate Client Hello packet) to request to obtain configuration information from the edge server so as to obtain the server parameters required to complete the QUIC handshake connection with the edge server.
  • an initial handshake request ie Inchoate Client Hello packet
  • Step 2 After the edge server receives the initial handshake request (that is, the Inchoate Client Hello packet), it can generate a prime number p and an integer g. And further calculate the public key A according to p, g and the randomly generated private key a, and put ⁇ A, p, g ⁇ in the configuration information (ie Server Config), and pass the Rejection (REJ) message to the configuration information sent to the client.
  • the initial handshake request that is, the Inchoate Client Hello packet
  • Step 3 After receiving the REJ message, the client extracts the server parameters, and randomly generates a public number b as the private key, then calculates the public key B according to p, g, and b in the configuration information, and then calculates the public key B according to p, A and
  • the initial key K is calculated from the three parameters of b, and the public key B and the business data encrypted with the initial key K are sent to the edge server through a complete handshake request (that is, a Full Client Hello message), thereby completing a handshake process.
  • Step 4 Enter the 0RTT process, that is, after the edge server receives the complete handshake request, it can calculate the initial key according to the public number sent by the client, and decrypt the business data sent by the client through the initial key K.
  • the edge server will regenerate a new private key c, and then generate a new public key C through the parameters p, g, and c; and the edge server can calculate a new key K2 according to the three parameters p, B, and c, and use K2 Encrypt the business data that needs to be returned, and bring the newly generated public key C of the edge server, and return it to the client through the Server Hello message.
  • Step 5 After receiving the Server Hello message sent by the edge server, the client can calculate the new key K2 according to p, C, and b, and decrypt the corresponding business data.
  • Step 6 After that, the two parties encrypt and decrypt the transmitted data through K2 until the connection ends.
  • the client can directly calculate the initial key K and encrypt the transmission data to achieve 0RTT handshake, eliminating the transmission delay of re-acquiring configuration information.
  • the handshake method based on the QUIC protocol can realize the purpose of business data transmission between the client and the server through one handshake interaction. Compared with the TCP protocol, which requires three-way handshake interaction to realize data transmission, it can greatly avoid the problem of handshake delay, and then quickly realize the processing of user services.
  • Fig. 2 schematically shows a schematic flowchart of a method for handshaking connection according to an embodiment of the present disclosure. As shown in Figure 2, the method is applied to the target edge server, including:
  • QUIC is a low-latency Internet transmission protocol based on the UDP protocol. Its emergence is mainly to solve some problems in the existing TCP network transmission protocol, including TCP queue head blocking, handshake delay, and TCP protocol rigidity. Based on UDP, QUIC provides reliable, orderly, secure, and faster transmission services. These advantages are especially important for CDN networks facing a large number of users. Therefore, many CDN manufacturers have begun to provide processing capabilities for QUIC protocol requests.
  • the data transmission of the QUIC protocol needs to be encrypted. Therefore, during the establishment of the QUIC connection, the edge server and the client need to negotiate an encryption private key through an RTT and exchange the key. After completing the complete connection process of the handshake.
  • the handshake process of the QUIC protocol requires the client to complete an initial handshake connection process every time it establishes a connection with an edge server that has not interacted before to achieve subsequent 0RTT transmission.
  • an initial handshake request is also required with each of them, which affects business processing efficiency.
  • the target edge server for the first time that the target edge server receives the handshake request sent by the client based on the QUIC protocol, the target edge server detects whether there is configuration information stored in the local storage area, if not, generates server parameters, and based on the server parameters Configuration information is generated, and in addition, the target edge server synchronizes the configuration information to other edge servers associated with it.
  • the edge servers in the server cluster share a piece of configuration information, when the client establishes a connection to any server in the server cluster, 0RTT handshake can be realized, thereby improving business processing efficiency.
  • the handshake request can be an Inchoate Client Hello packet sent by the client.
  • the client may also first detect whether configuration information of the target edge server is stored in itself before this. It can be understood that when the client does not detect the configuration information itself or does not detect the existence of complete configuration information, it can send an initial handshake request to the target edge server, obtain configuration information from the target edge server, and then complete the handshake with the target edge server The server parameters required for connection to achieve the purpose of completing the handshake connection.
  • the configuration information may be Server Config information.
  • configuration information including server parameters may be generated for the client.
  • the server parameters may include a prime number generated by the edge server and an integer.
  • public keys calculated from prime numbers, integers, and randomly generated private keys, etc.
  • the target edge server After generating the configuration information, the target edge server sends the configuration information to the client through a Rejection (REJ) message.
  • the client can extract the server parameters, and randomly generate a public number as the private key, and then calculate the public key according to the prime number and integer in the configuration information, pass the public key and the business data encrypted with the initial key through the complete
  • the handshake request (ie Full Client Hello message) is sent to the target edge server to complete the handshake connection.
  • the target edge server in order to solve the problem that the client needs to complete a complete handshake connection process for each edge server that has not interacted before or has interacted but the configuration information has expired before data transmission can be performed.
  • the target edge server after the target edge server generates the configuration information, it can also send the configuration information to other edge servers associated with it, and share a piece of configuration information with at least one other edge server associated with the target edge server,
  • an ORTT handshake can be implemented, thereby improving service processing efficiency.
  • the present disclosure does not specifically limit the association relationship between the target edge server and other edge servers. For example, when the target edge server and other edge servers are deployed in the same service area, there is an association relationship between them. Or, when the target edge server and other edge servers are servers processing the same service type, there is an association relationship between the two, and so on.
  • the present disclosure does not specifically limit the number of other edge servers associated with the target edge server, for example, there may be one or more.
  • the target edge server may forward the configuration information to one of the multiple other edge servers, or forward the configuration information to multiple or all of the multiple other edge servers.
  • the configuration information may be propagated through broadcasting or other sending manners, which is not limited in the present disclosure.
  • the client After the client receives the configuration information, in subsequent new connections, it can use the configuration information to directly calculate the initial key K and encrypt the transmitted data to realize the 0RTT handshake with the target edge server.
  • the client when the client connects to other edge servers associated with the target edge server, the ORTT handshake with other edge servers can also be implemented through the configuration information.
  • the target edge server after the target edge server receives the handshake request sent by the client for the first time based on the QUIC protocol, it can obtain configuration information including server parameters required to complete the QUIC handshake connection with the client, and send the configuration information to the client. Complete the handshake connection; and, send the configuration information to at least one other edge server associated with the target edge server, so that when other edge servers receive the handshake request sent by the client based on the QUIC protocol, they complete the QUIC with the client according to the configuration information Handshake connection.
  • the target edge server after the target edge server generates the configuration information required to complete the QUIC handshake connection for the client, it can also send the configuration information to at least one other edge server associated with it, so as to achieve other The edge server can use the configuration information to realize the purpose of exchanging business data without performing an initial handshake request with the client, thereby improving the business processing efficiency under the QUIC protocol.
  • the configuration information includes server parameters required to complete the QUIC handshake connection with the client
  • the server parameter can be a prime number and an integer generated when the edge server completes the QUIC handshake connection with the client, and a public key calculated based on the prime number, the integer, and a randomly generated private key.
  • the prime number the integer and the public key can be combined as server parameters, configuration information is generated accordingly, and the configuration information is subsequently sent to the client through a REJ message.
  • the target edge server before the target edge server generates server parameters, it can also detect whether there is configuration information stored locally, and check whether the configuration information is expired. call in the area.
  • the historical configuration information stored in the storage area can be directly called to complete the handshake connection with the client. , otherwise the target edge server needs to continue to generate server parameters, and generate configuration information based on the server parameters, and then complete the QUIC handshake connection with the client.
  • the target edge server can only send data to other edge servers in the server cluster where it is located. Send configuration information.
  • the client can directly use the configuration information to directly calculate the initial key K and encrypt the transmitted data.
  • this configuration information it can directly use this configuration information to decrypt the encrypted data transmitted by the client and perform subsequent data interaction, thereby realizing the 0RTT handshake between the client and other edge servers.
  • edge server A as the target edge server
  • edge server B and edge server C as other edge servers
  • the edge server A After receiving the initial handshake request sent by the client for the first time based on the QUIC protocol, the edge server A can obtain the configuration information of the server parameters required to complete the QUIC handshake connection with the client, and send the configuration information to the client to complete While shaking the connection, the configuration information can also be broadcast to any one or more of the other edge servers (eg, edge server B and edge server C) in the cluster. In the subsequent process of establishing a connection with the edge server B and/or the edge server C, the client can directly use the configuration information to implement ORTT handshake.
  • edge server B and edge server C the client can directly use the configuration information to implement ORTT handshake.
  • the present disclosure can also choose that the target edge server strategically send configuration information to other specified edge servers.
  • Send configuration information may only send configuration information to other edge servers located in the same geographical area, or only send configuration information to other edge servers that process the same type of business.
  • the other edge servers mentioned in the embodiments of the present disclosure in the same region or with the same service type as the target edge server may be in the same server cluster range as the target edge server, or may not be in the same server cluster range.
  • the configuration information is sent directly or indirectly to at least one other edge server.
  • the target edge server since the number of other edge servers associated with the target edge server may be large, if the target edge server needs to send configuration information to each of the other edge servers one by one, the target edge server may be more expensive. Big sending resource issue. Therefore, in a manner, the present disclosure may also choose that the target edge server generate a forwarding instruction for informing other edge servers to help forward the configuration information, so as to directly or indirectly send the configuration information to other edge servers associated with it. .
  • the forwarding instruction may be to inform other edge servers to forward configuration information to edge servers adjacent to itself, and the instruction may be an instruction carried at the same time as sending the configuration information.
  • the target edge server only needs to send the configuration information to other edge servers, and the subsequent propagation method can be propagated layer by layer by other edge servers to other edge servers adjacent to itself. It can be understood that this method can share the pressure of the target edge server to send configuration information, thereby saving the data sending and receiving resources of the target edge server.
  • the forwarding instruction may also be to instruct other edge servers to transmit configuration information to the specified edge server.
  • the target edge server A may send a forwarding instruction to the other edge server C, so as to instruct the edge server C to transmit the configuration information to the edge server B through other link channels.
  • the edge server C may be a server adjacent to the edge server B.
  • Fig. 4 schematically shows a schematic flowchart of a method for handshaking connection according to an embodiment of the present disclosure. As shown in Figure 4, the method is applied to edge servers, including:
  • the edge server first receives the configuration information sent by the target edge server to complete a complete handshake connection with the client, so that the edge server can implement 0RTT handshake with client.
  • the configuration information may be configuration information including server parameters generated for the client during the process of establishing a connection between the target edge server and the client based on the QUIC protocol for the first time. It is understandable that the handshake process of the QUIC protocol requires the client to complete an initial handshake connection process and obtain the corresponding configuration information every time it establishes a connection with an edge server that has not interacted before. After the edge server receives the configuration information sent by the target edge server, the subsequent client can directly transmit encrypted business data according to the configuration information possessed by both the client and the edge server. The purpose of business data interaction can be carried out, thereby improving the business processing efficiency of the two under the QUIC protocol.
  • the edge server in this disclosure may be an edge server associated with the target edge server.
  • the two are associated.
  • the target edge server and other edge servers handle the same service type, the two are associated and so on.
  • the present disclosure does not specifically limit the number of edge servers, for example, there may be one or more.
  • the target edge server may forward the configuration information to one of the multiple edge servers, or forward the configuration information to multiple or all of the multiple edge servers.
  • the edge server in the way that the edge server receives the configuration information sent by the target edge server, the edge server in the same cluster as the target edge server receives and saves the configuration information broadcast by the target edge server, or in a way other than broadcasting, This disclosure does not limit it.
  • the edge server may store the configuration information in a local preset storage area. So that when the subsequent client sends encrypted service data to the edge server according to the configuration information, the edge server can decrypt the encrypted data according to the configuration information, and then complete the ORTT service data interaction.
  • the edge server when it receives the handshake request sent by the client based on the QUIC protocol, it can calculate the initial key according to the public number sent by the client, and decrypt the business data sent by the client through the initial key K.
  • the edge server will regenerate a new private key c, and then generate a new public key C through the parameters p, g, and c; and the edge server can calculate a new key K2 according to the three parameters p, B, and c, and use K2 Encrypt the business data that needs to be returned, and bring the newly generated public key C of the edge server, and return it to the client through the Server Hello message.
  • the edge server can receive the configuration information generated by the target edge server for the client to complete the QUIC handshake connection, and then store the configuration information, so that the subsequent implementation can be achieved through the configuration information.
  • the purpose of business data interaction can be performed without an initial handshake request with the client, thereby improving the business processing efficiency under the QUIC protocol.
  • the configuration information is forwarded to at least one edge server associated with the target edge server, and the configuration information is used to complete the handshake connection between the edge server and the client.
  • the present disclosure may also choose that the edge server receives the forwarding instruction sent by the target edge server, wherein, The forwarding instruction is used to instruct the edge server to forward the configuration information to at least one edge server associated with the target edge server, so that the edge server shares the configuration information forwarding task for the target edge server.
  • the purpose of the forwarding instruction is to strategically instruct the target edge server to send the configuration information to other designated edge servers.
  • the target edge server may only send the configuration information to the edge servers located in the same geographical area, or only send the configuration information to the edge servers that handle the same type of business as the target edge server.
  • the forwarding instruction may be to tell the edge server to forward the configuration information to the edge server adjacent to itself, and the instruction may be an instruction carried at the same time as sending the configuration information.
  • the configuration information can be sent to one or more edge servers adjacent to itself.
  • the forwarding instruction may also be to instruct other edge servers to transmit configuration information to the specified edge server.
  • the target edge server A may send a forwarding instruction to the other edge server C, so as to instruct the edge server C to transmit the configuration information to the edge server B through other link channels.
  • the edge server C may be a server adjacent to the edge server B.
  • the target edge server only needs to send the configuration information to other edge servers adjacent to itself, and the subsequent propagation method can be propagated layer by layer by other edge servers to other edge servers adjacent to itself . It can be understood that this method can share the pressure of the target edge server to send configuration information, thereby saving data sending and receiving resources of the target edge server.
  • the technical solution of the present disclosure is to use the edge server to send the configuration information required for the QUIC handshake connection with the client to other edge servers associated with itself, so as to realize the ORTT data exchange between other edge servers and the client. purpose of the interaction. In this way, not only can the operating resources of the client be saved to achieve the purpose of quickly providing business services to users, but also the processing resources of the edge server can be reduced, thereby achieving the purpose of optimizing the overall business processing system.
  • the present disclosure also provides an electronic device for handshake connection, which is applied to a target edge server, including:
  • the first receiving module 301 is configured to receive the first handshake request sent by the client based on the QUIC protocol;
  • the first obtaining module 302 is configured to obtain configuration information, the configuration information includes server parameters required to complete the QUIC handshake connection with the client;
  • the sending module 303 is configured to complete a handshake connection with the client according to the configuration information; and send the configuration information to at least one other edge server associated with the target edge server, so that other edge servers
  • the server receives the handshake request sent by the client based on the QUIC protocol, it completes the QUIC handshake connection with the client according to the configuration information.
  • the target edge server after receiving the initial handshake request sent by the client for the first time based on the QUIC protocol, can obtain configuration information including server parameters required to complete the QUIC handshake connection with the client, and send the configuration information to the client for Complete the handshake connection; and, send the configuration information to at least one other edge server associated with the target edge server, so that when other edge servers receive the handshake request sent by the client based on the QUIC protocol, they complete the QUIC with the client according to the configuration information Handshake connection, so that other edge servers can use this configuration information to realize the purpose of exchanging business data without making an initial handshake request with the client, thereby improving the business processing efficiency under the QUIC protocol.
  • the first acquisition module 302 is configured to:
  • the sending module 303 is configured to:
  • the sending module 303 is configured to:
  • the sending module 303 is configured to:
  • the present disclosure further provides an electronic device for handshake connection.
  • the edge server including:
  • the second obtaining module 304 is configured to obtain the configuration information sent by the target edge server, which includes the server parameters needed to complete the QUIC handshake connection with the client;
  • the storage module 305 is configured to store the configuration information in a local preset storage area
  • the second receiving module 306 is configured to complete the handshake connection with the client according to the configuration information when receiving the first handshake request sent by the client based on the QUIC protocol.
  • the edge server after the edge server receives the first handshake request sent by the client based on the QUIC protocol, it can obtain configuration information including server parameters required to complete the QUIC handshake connection with the client, and send the configuration information to the client to complete handshake connection; and, sending the configuration information to at least one other edge server associated with the target edge server, so that when other edge servers receive the handshake request sent by the client based on the QUIC protocol, they complete the QUIC handshake with the client according to the configuration information Connection, so that other edge servers can use this configuration information to realize the purpose of exchanging business data without going through a complete handshake process with the client. In turn, the business processing efficiency under the QUIC protocol is improved.
  • the storage module 305 is configured as:
  • the second receiving module 306 is configured to:
  • Fig. 7 is a logical structural block diagram of an electronic device according to an exemplary embodiment.
  • the electronic device 400 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • an electronic device 400 may include one or more of the following components: a processor 401 and a memory 402 .
  • the processor 401 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like.
  • Processor 401 can adopt at least one hardware form in DSP (Digital Signal Processing, digital signal processing), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array, programmable logic array) accomplish.
  • Processor 401 may also include a main processor and a coprocessor, and the main processor is a processor for processing data in a wake-up state, also known as a CPU (Central Processing Unit, central processing unit); the coprocessor is Low-power processor for processing data in standby state.
  • CPU Central Processing Unit, central processing unit
  • the coprocessor is Low-power processor for processing data in standby state.
  • the processor 401 may be integrated with a GPU (Graphics Processing Unit, image processor), and the GPU is used for rendering and drawing the content that needs to be displayed on the display screen.
  • the processor 401 may also include an AI (Artificial Intelligence, artificial intelligence) processor, where the AI processor is used to process computing operations related to machine learning.
  • AI Artificial Intelligence, artificial intelligence
  • Memory 402 may include one or more computer-readable storage media, which may be non-transitory.
  • the memory 402 may also include high-speed random access memory and non-volatile memory, such as one or more magnetic disk storage devices and flash memory storage devices.
  • the non-transitory computer-readable storage medium in the memory 402 is used to store at least one instruction, and the at least one instruction is used to be executed by the processor 401 to realize the interactive effects provided by the method embodiments of the present disclosure. calibration method.
  • the electronic device 400 may further include: a peripheral device interface 403 and at least one peripheral device.
  • the processor 401, the memory 402, and the peripheral device interface 403 may be connected through buses or signal lines.
  • Each peripheral device can be connected to the peripheral device interface 403 through a bus, a signal line or a circuit board.
  • the peripheral device includes: at least one of a radio frequency circuit 404 , a touch screen 405 , a camera 406 , an audio circuit 407 , a positioning component 408 and a power supply 409 .
  • the peripheral device interface 403 may be used to connect at least one peripheral device related to I/O (Input/Output, input/output) to the processor 401 and the memory 402 .
  • the processor 401, memory 402 and peripheral device interface 403 are integrated on the same chip or circuit board; in some other embodiments, any one of the processor 401, memory 402 and peripheral device interface 403 or The two can be implemented on a separate chip or circuit board, which is not limited in this embodiment.
  • the radio frequency circuit 404 is used to receive and transmit RF (Radio Frequency, radio frequency) signals, also called electromagnetic signals.
  • the radio frequency circuit 404 communicates with the communication network and other communication devices through electromagnetic signals.
  • the radio frequency circuit 404 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals into electrical signals.
  • the radio frequency circuit 404 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and the like.
  • the radio frequency circuit 404 can communicate with other terminals through at least one wireless communication protocol.
  • the wireless communication protocol includes but is not limited to: metropolitan area network, mobile communication networks of various generations (2G, 3G, 4G and 5G), wireless local area network and/or WiFi (Wireless Fidelity, wireless fidelity) network.
  • the radio frequency circuit 404 may also include circuits related to NFC (Near Field Communication, short-range wireless communication), which is not limited in the present disclosure.
  • the display screen 405 is used to display a UI (User Interface, user interface).
  • the UI can include graphics, text, icons, video, and any combination thereof.
  • the display screen 405 also has the ability to collect touch signals on or above the surface of the display screen 405 .
  • the touch signal can be input to the processor 401 as a control signal for processing.
  • the display screen 405 can also be used to provide virtual buttons and/or virtual keyboards, also called soft buttons and/or soft keyboards.
  • the display screen 405 may be a flexible display screen, which is arranged on the curved surface or the folding surface of the electronic device 400 . Even, the display screen 405 can also be set as a non-rectangular irregular figure, that is, a special-shaped screen.
  • the display screen 405 can be made of LCD (Liquid Crystal Display, liquid crystal display), OLED (Organic Light-Emitting Diode, organic light-emitting diode) and other materials.
  • the camera assembly 406 is used to capture images or videos.
  • the camera component 406 includes a front camera and a rear camera.
  • the front camera is set on the front panel of the terminal, and the rear camera is set on the back of the terminal.
  • there are at least two rear cameras which are any one of the main camera, depth-of-field camera, wide-angle camera, and telephoto camera, so as to realize the fusion of the main camera and the depth-of-field camera to realize the background blur function.
  • camera assembly 406 may also include a flash.
  • the flash can be a single-color temperature flash or a dual-color temperature flash. Dual color temperature flash refers to the combination of warm light flash and cold light flash, which can be used for light compensation under different color temperatures.
  • Audio circuitry 407 may include a microphone and speakers.
  • the microphone is used to collect sound waves of the user and the environment, and convert the sound waves into electrical signals and input them to the processor 401 for processing, or input them to the radio frequency circuit 404 to realize voice communication.
  • the microphone can also be an array microphone or an omnidirectional collection microphone.
  • the speaker is used to convert the electrical signal from the processor 401 or the radio frequency circuit 404 into sound waves.
  • the loudspeaker can be a conventional membrane loudspeaker or a piezoelectric ceramic loudspeaker.
  • audio circuitry 407 may also include a headphone jack.
  • the positioning component 408 is used to locate the current geographic location of the electronic device 400, so as to realize navigation or LBS (Location Based Service, location-based service).
  • the positioning component 408 may be a positioning component based on the GPS (Global Positioning System) of the United States, the Beidou system of China, the Grenax system of Russia or the Galileo system of the European Union.
  • the power supply 409 is used to supply power to various components in the electronic device 400 .
  • Power source 409 may be AC, DC, disposable or rechargeable batteries.
  • the rechargeable battery can support wired charging or wireless charging.
  • the rechargeable battery can also be used to support fast charging technology.
  • the electronic device 400 further includes one or more sensors 410 .
  • the one or more sensors 410 include, but are not limited to: an acceleration sensor 411 , a gyro sensor 412 , a pressure sensor 413 , a fingerprint sensor 414 , an optical sensor 415 and a proximity sensor 416 .
  • the acceleration sensor 411 can detect the acceleration on the three coordinate axes of the coordinate system established by the electronic device 400 .
  • the acceleration sensor 411 can be used to detect the components of the gravitational acceleration on the three coordinate axes.
  • the processor 401 may control the touch display screen 405 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 411 .
  • the acceleration sensor 411 can also be used for collecting game or user's motion data.
  • the gyro sensor 412 can detect the body direction and rotation angle of the electronic device 400 , and the gyro sensor 412 can cooperate with the acceleration sensor 411 to collect 3D actions of the user on the electronic device 400 .
  • the processor 401 can realize the following functions: motion sensing (such as changing the UI according to the user's tilt operation), image stabilization during shooting, game control and inertial navigation.
  • the pressure sensor 413 may be disposed on the side frame of the electronic device 400 and/or the lower layer of the touch screen 405 .
  • the pressure sensor 413 can detect the user's grip signal on the electronic device 400 , and the processor 401 performs left and right hand recognition or shortcut operation according to the grip signal collected by the pressure sensor 413 .
  • the processor 401 controls the operable controls on the UI interface according to the user's pressure operation on the touch screen 405.
  • the operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.
  • the fingerprint sensor 414 is used to collect the user's fingerprint, and the processor 401 identifies the user's identity according to the fingerprint collected by the fingerprint sensor 414, or, the fingerprint sensor 414 identifies the user's identity according to the collected fingerprint.
  • the processor 401 authorizes the user to perform related sensitive operations, such sensitive operations include unlocking the screen, viewing encrypted information, downloading software, making payment, and changing settings.
  • the fingerprint sensor 414 may be disposed on the front, back or side of the electronic device 400 . When the electronic device 400 is provided with a physical button or a manufacturer's logo, the fingerprint sensor 414 may be integrated with the physical button or the manufacturer's Logo.
  • the optical sensor 415 is used to collect ambient light intensity.
  • the processor 401 can control the display brightness of the touch screen 405 according to the ambient light intensity collected by the optical sensor 415 . Specifically, when the ambient light intensity is high, the display brightness of the touch screen 405 is increased; when the ambient light intensity is low, the display brightness of the touch screen 405 is decreased.
  • the processor 401 may also dynamically adjust shooting parameters of the camera assembly 406 according to the ambient light intensity collected by the optical sensor 415 .
  • the proximity sensor 416 also called a distance sensor, is usually arranged on the front panel of the electronic device 400 .
  • the proximity sensor 416 is used to collect the distance between the user and the front of the electronic device 400 .
  • the processor 401 controls the touch display screen 405 to switch from the bright screen state to the off screen state; when the proximity sensor 416 When it is detected that the distance between the user and the front of the electronic device 400 gradually increases, the processor 401 controls the touch display screen 405 to switch from the off-screen state to the on-screen state.
  • FIG. 4 does not constitute a limitation to the electronic device 400, and may include more or less components than shown in the figure, or combine some components, or adopt a different component arrangement.
  • a non-transitory computer-readable storage medium including instructions, such as a memory 404 including instructions, the above instructions can be executed by the processor 420 of the electronic device 400 to complete the above method based on handshake connection , the method includes: receiving the first handshake request sent by the client based on the QUIC protocol; obtaining configuration information, which includes server parameters required to complete the QUIC handshake connection with the client; sending the configuration information to The client completes the QUIC handshake connection; and, sends the configuration information to at least one other edge server associated with the target edge server, so that the other edge server receives the client-based QUIC protocol When sending the handshake request, complete the QUIC handshake connection with the client according to the configuration information.
  • the above instructions may also be executed by the processor 420 of the electronic device 400 to complete other steps involved in the above exemplary embodiments.
  • the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • an application program/computer program product including one or more instructions, which can be executed by the processor 420 of the electronic device 400, so as to complete the above-mentioned handshake-based connection
  • the method includes: receiving the handshake request sent by the client for the first time based on the QUIC protocol; obtaining configuration information, the configuration information includes server parameters required to complete the QUIC handshake connection with the client; sending the configuration information to the client to complete the QUIC handshake connection; and, sending the configuration information to at least one other edge server associated with the target edge server, so that the other edge server receives the QUIC-based
  • the above instructions may also be executed by the processor 420 of the electronic device 400 to complete other steps involved in the above exemplary embodiments.
  • the edge server after the edge server receives the initial handshake request sent by the client for the first time based on the QUIC protocol, it can obtain configuration information including server parameters required to complete the QUIC handshake connection with the client, and send the configuration information to the client for Complete the handshake connection; and, send the configuration information to at least one other edge server associated with the target edge server, so that when other edge servers receive the handshake request sent by the client based on the QUIC protocol, communicate with the client according to the configuration information Complete the QUIC handshake connection.
  • the configuration information can also be sent to at least one other edge server associated with it, so as to reach other edges
  • the server can realize the purpose of exchanging business data without performing an initial handshake request with the client, thereby improving the business processing efficiency under the QUIC protocol.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)

Abstract

本公开是关于一种握手连接的方法、电子装置、电子设备以及介质。本公开中，在边缘服务器接收客户端首次基于QUIC协议发送的初始握手请求后，可以获取包括有与客户端完成QUIC握手连接所需的服务器参数的配置信息，并将配置信息发送给客户端以完成握手连接；以及，将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据配置信息与所述客户端完成QUIC握手连接。

Description

握手连接的方法、电子装置、电子设备以及介质
本公开基于2021年12月17日提交中国专利局、申请号为202111554091.X，发明名称为“握手连接的方法、电子装置、电子设备以及介质”的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本公开作为参考。
技术领域
本公开实施例涉及但不限于一种握手连接的方法、电子装置、电子设备以及介质。
背景技术
QUIC是一种基于UDP协议的低时延互联网传输协议，其在UDP的基础上，提供了可靠、有序、安全以及更快速的传输服务等，这些优点对于面向海量用户的CDN网络尤为重要，因此业务平台越来越频繁的使用QUIC协议进行业务处理。
其中，QUIC协议能够更快速的传输，其中一个原因即为其可以解决现有的TCP网络传输协议中存在的握手延迟的问题。具体来说，通过QUIC协议的传输，可以达到客户端与服务器通过一次握手交互即可实现双方进行业务数据传输的目的。
然而，QUIC协议的握手过程也存在一个问题，即当客户端每连接一个未曾交互过的服务器时，均需要与其完成一次初始握手过程并获取对应的配置信息后，才可以进行数据交互，但这样也会影响业务处理的效率。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本公开提供一种握手连接的方法、电子装置、电子设备以及介质。
根据本公开的一个方面，提供一种握手连接的方法，应用于目标边缘服务器，包括：
接收客户端首次基于QUIC协议发送的握手请求；
获取配置信息，所述配置信息中包括有与所述客户端完成握手连接所需的服务器参数；
将所述配置信息发送给所述客户端以完成QUIC握手连接；以及，
将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接。
在一些示例性的实施例中，所述获取配置信息，包括：
检测本地存储区域中是否存储有所述配置信息；
若无，生成所述服务器参数；
并基于所述服务器参数生成所述配置信息。
在一些示例性的实施例中，在所述检测本地存储区域中是否存储有所述配置信息之后，还包括：
若有，检测所述配置信息是否过期；
若未过期，从所述存储区域中调取所述配置信息。
在一些示例性的实施例中，所述将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，包括：
确定所述目标边缘服务器所在的服务器集群，并将所述配置信息发送给在所述服务器集群中的至少一个其他边缘服务器。
在一些示例性的实施例中，所述将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，包括：
将所述配置信息发送给同区域或同业务类型的至少一个其他边缘服务器。
在一些示例性的实施例中，所述将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，包括：
将所述配置信息直接或间接发送给所述至少一个其他边缘服务器。
根据本公开的又一个方面，提供一种握手连接的电子装置，应用于边缘服务器，包括：
获取目标边缘服务器发送的配置信息，所述配置信息中包括有与客户端完成QUIC握手连接所需的服务器参数；
将所述配置信息存储到本地的预设存储区域中；
当接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息，完成与所述客户端的握手连接。
在一些示例性的实施例中，在所述将所述配置信息存储到本地的预设存储区域中之后，还包括：
检测所述配置信息是否过期；
若未过期，从所述存储区域中调取所述配置信息；
若过期，则从目标边缘服务器获取最新的配置信息。
根据本公开的又一个方面，提供一种云计算网络中的业务处理装置，其特征在于，应用于目标边缘服务器，包括：
第一接收模块，被配置为接收客户端首次基于QUIC协议发送的握手请求；
第一获取模块，被配置为获取配置信息，所述配置信息中包括有与所述客户端完成QUIC握手连接所需的服务器参数；
发送模块，被配置为将所述配置信息发送给所述客户端以完成握手连接；以及，将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接。
根据本公开的又一个方面，提供一种云计算网络中的业务处理装置，其特征在于，应用于边缘服务器，包括：
第二获取模块，被配置为获取目标边缘服务器发送的配置信息，所述配置信息中包括有与客户端完成QUIC握手连接所需的服务器参数；
存储模块，被配置为将所述配置信息存储到本地的预设存储区域中；
第二接收模块，被配置为当接收到所述客户端首次基于QUIC协议发送的握手请求时，根据所述配置信息，完成与所述客户端的握手连接。
根据本公开的另一个方面，提供一种电子设备，包括：
存储器，用于存储可执行指令；以及
显示器，用于与所述存储器显示以执行所述可执行指令从而完成上述任一所述握手连接的方法的操作。
根据本公开的另一个方面，提供一种计算机可读存储介质，用于存储计算机可读取的指令，所述指令被执行时执行上述任一所述握手连接的方法的操作。
根据本公开的另一个方面，提供一种计算机程序产品，包括计算机程序，计算机程序用于被处理器执行实现上述任一项所述握手连接的方法。
本公开中，在边缘服务器接收客户端首次基于QUIC协议发送的初始握手请求后，可以获取包括有与客户端完成QUIC握手连接所需的服务器参数的配置信息，并将配置信息发送给客户端以完成握手连接；以及，将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据 配置信息与所述客户端完成QUIC握手连接。通过应用本公开的技术方案，在边缘服务器为客户端生成用于完成QUIC握手连接所需的配置信息后，还可以将该配置信息发送给与其关联的至少一个其他边缘服务器上，以达到其他边缘服务器可以通过该配置信息实现无需与该客户端再进行一次初始握手请求即可以进行业务数据交互的目的，进而提高了QUIC协议下的业务处理效率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
构成说明书的一部分的附图描述了本公开的实施例，并且连同描述一起用于解释本公开的原理，并不构成对本公开的不当限定。
参照附图，根据下面的详细描述，可以更加清楚地理解本公开，其中：
图1为根据一示例性实施例示出的相关技术中一种握手连接的工作原理的示例性流程架构的示意图；
图2为根据一示例性实施例示出的一种握手连接的方法示意图；
图3为根据一示例性实施例示出的一种握手连接的系统架构示意图；
图4为根据一示例性实施例示出的另一种握手连接的方法示意图；
图5-6为根据一示例性实施例示出的一种握手连接的电子装置示意图；
图7为根据一示例性实施例示出的另一种握手连接的电子设备示意图。
具体实施方式
现在将参照附图来详细描述本公开的各种示例性实施例。应注意到：除非另外具体说明，否则在这些实施例中阐述的部件和步骤的相对布置、数字表达式和数值不限制本公开的范围。
同时，应当明白，为了便于描述，附图中所示出的各个部分的尺寸并不是按照实际的比例关系绘制的。
以下对至少一个示例性实施例的描述实际上仅仅是说明性的，不作为对本公开及其应用或使用的任何限制。
对于相关领域普通技术人员已知的技术、方法和设备可能不作详细讨论，但在适当情况下，所述技术、方法和设备应当被视为说明书的一部分。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步讨论。
另外，本公开各个实施例之间的技术方案可以相互结合，但是必须是以本领域普通技术人员能够实现为基础，当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在，也不在本公开要求的保护范围之内。
本公开实施例中所有方向性指示(诸如上、下、左、右、前、后……)仅用于解释在某一特定姿态(如附图所示)下各部件之间的相对位置关系、运动情况等，如果该特定姿态发生改变时，则该方向性指示也相应地随之改变。
本公开的技术方案可以避免每当客户端连接一个未曾交互过的服务器时，均需要与其完成一次初始握手过程并获取对应的配置信息后才可以进行数据交互，进而影响业务处理效率的问题。
下面结合图1-图5来描述根据本公开示例性实施方式的用于进行握手连接的方法。下述应用场景仅是为了便于理解本公开的精神和原理而示出，本公开的实施方式在此方面不受任何限制。相反，本公开的实施方式可以应用于适用的任何场景。
其中，图1示出了可以应用本公开实施例的客户端与边缘服务器完成一次完整握手连接的工作原理的示例性方法的示意图。
由图1可以看出，包括客户端与边缘服务器完成一次初始握手请求的(即1RTT)过程以及后续二者进行完整握手请求的(即0RTT)过程，其中包括：
步骤一：客户端首先判断本地是否存储有该边缘服务器的配置信息(该配置信息中包括有与二者完成QUIC握手连接所需的服务器参数)，如无，则可以发送一个初始握手请求(即Inchoate Client Hello数据包)以请求向该边缘服务器获取配置信息从而获得与边缘服务器完成QUIC握手连接所需的服务器参数。
步骤二：边缘服务器收到初始握手请求(即Inchoate Client Hello数据包)后，可以生成一个质数p和一个整数g。并进一步的根据p、g和随机生成的私钥a计算出公钥A，并将{A，p，g}放在配置信息(即Server Config)中，并通过Rejection(REJ)消息将配置信息发送给该客户端。
步骤三：客户端接收到REJ消息后，提取其中的服务器参数，并随机生成一个公开数b作为私钥，再根据配置信息中的p，g，b算出公钥B，然后根据p、A和b三个参数算出初始密钥K，并将公钥B和利用初始密钥K加密的业务数据通过完整握手请求(即Full Client Hello消息)发送给边缘服务器，进而完成一次握手过程。
步骤四：进入到0RTT过程，即边缘服务器接收到完整握手请求后，可以根据客户端发来的公开数计算出初始密钥，并通过初始密钥K解密客户端发来的业务数据。其中边缘服务器会重新生成新的私钥c，然后通过p，g，c参数生成新的公钥C；且边缘服务器可以根据p、B和c三个参数算出新的密钥K2，并利用K2加密需要返回的业务数据，以及带上边缘服务器新生成的公钥C，在通过Server Hello消息返回给客户端。
步骤五：客户端收到边缘服务器发送的Server Hello消息后，即可以根据p，C，b计算出新的密钥K2，并解密出相应的业务数据。
步骤六：之后双方通过K2加解密传输的数据，直到连接结束。
其中，对于后续的连接，如果客户端本地的配置信息没过期，客户端可以直接计算出初始秘钥K并加密传输数据，实现0RTT握手，省去了重新获取配置信息的传输延迟。
可以理解的，基于QUIC协议的握手方式可以实现客户端与服务器通过一次握手交互即可实现双方进行业务数据传输的目的。相对于TCP协议中需要进行三次握手交互才可以实现数据传输的方式来说，可以极大的避免握手延迟的问题，进而快速实现用户业务的处理。
一种实施方式中，本公开还提出一种握手连接的方法。图2示意性地示出了根据本公开实施方式的一种握手连接的方法的流程示意图。如图2所示，该方法应用于目标边缘服务器，包括：
S101，接收客户端首次基于QUIC协议发送的握手请求。
其中，QUIC是一种基于UDP协议的低时延互联网传输协议，其出现主要是为了解决现有的TCP网络传输协议中存在的一些问题，包括TCP队头阻塞、握手延迟以及TCP协议僵化等。QUIC在UDP的基础上，提供了可靠、有序、安全以及更快速的传输服务等，这些优点对于面向海量用户的CDN网络尤为重要，因此很多CDN厂商开始提供了QUIC协议请求的处理能力。
一种方式中，为了保证数据传输的安全，QUIC协议的数据传输是需要加密实现的，因此在QUIC的建连过程中需要边缘服务器与客户端通过一次RTT协商出加密私钥并在密钥交换后完成握手的完整连接过程。
由上可以看出，QUIC协议的握手过程是需要客户端每与一个之前未曾交互的边缘服务器进行建连时，均需要完成一次初始的握手连接过程才可以实现后续的0RTT传输。当服务器集群内的边缘服务器数量为多个且客户端与服务器集群内的不同边缘服务器建立连接时，也需要分别与其进行一次初始握手请求，从而影响业务处理效率。
一种方式中，本公开对于目标边缘服务器首次接收客户端基于QUIC协议发送的握手请求而言，目标边缘服务器检测本地存储区域中是否存储有配置信息，若无，生成服务器参数，并基于服务器参数生成配置信息，此外，目标边缘服务器将该配置信息同步给与其相关联的其他边缘服务器。通过让服务器集群内的边缘服务器共享一份配置信息，当客户端向服务器集群内的任意一台服务器建立连接时，可以实现0RTT握手，从而提高业务处理效率。
一种方式中，握手请求可以为客户端发送的Inchoate Client Hello数据包。在一些示例性的实施例中，客户端还可以在此之前首先检测自身中是否存储有该目标边缘服务器的配置信息。可以理解的，当客户端未在自身检测到配置信息或未检测存在完整的配置信息后，可以向目标边缘服务器发送初始握手请求，从该目标边缘服务器获取配置信息进而获得与目标边缘服务器完成握手连接所需的服务器参数，以实现完成握手连接的目的。其中，该配置信息可以为Server Config信息。
S102、获取配置信息，配置信息中包括有与客户端完成QUIC握手连接所需的服务器参数。
在目标边缘服务器接收到初始握手请求之后，为了完成与客户端的握手连接，可以为该客户端生成有包含服务器参数的配置信息。例如服务器参数可以包括边缘服务器所生成的质数和一个整数。以及根据质数、整数和随机生成的私钥所计算得出的公钥等等。
S103、将配置信息发送给客户端以完成QUIC握手连接，以及将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据配置信息与客户端完成QUIC握手连接。
目标边缘服务器在生成配置信息后，将该配置信息通过Rejection(REJ)消息发送给客户端。以使客户端提取其中的服务器参数，并随机生成一个公开数作为私钥，再根据配置信息中的质数和整数计算得出公钥后，将公钥和利用初始密钥加密的业务数据通过完整握手请求(即Full Client Hello消息)发送给目标边缘服务器以完成握手连接。
其中，为了解决客户端需要为每一个之前未曾交互或交互过但配置信息已经过期的边缘服务器完成一次完整的握手连接过程后才能进行数据传输所导致的处理业务效率下降的问题。本公开实施例中在目标边缘服务器生成配置信息后，还可以将该配置信息发送给与其相关联的其他边缘服务器处，通过与目标边缘服务器相关联的至少一个其他边缘服务器共享一份配置信息，当客户端向与目标边缘服务器相关联的至少一个其他边缘服务器建立连接时，可以实现0RTT握手，从而提高业务处理效率。
一种方式中，本公开不对目标边缘服务器与其他边缘服务器的关联关系进行具体限定，例如，当目标边缘服务器与其他边缘服务器部署在同一业务区域内时，二者存在关联关系。或者，当目标边缘服务器与其他边缘服务器为处理同一种业务类型的服务器时，二者存在关联关系等等。
另外，本公开也不对与目标边缘服务器相关联的其他边缘服务器的数量进行具体限定，例如可以为一个也可以为多个。其中在其他边缘服务器为多个时，目标边缘服务器可以向该多个其他边缘服务器中的一个转发该配置信息，也可以向该多个其他边缘服务器中的多个或全部转发该配置信息。
一种方式中，在目标边缘服务器向其他边缘服务器发送配置信息的方式中，可以通过广播的方式将配置信息进行传播，也可以通过其他发送方式，本公开对此不作限定。
客户端收到配置信息后，在后续的新连接中，便可以使用该配置信息直接计算出初始密钥K并加密传输数据，实现与目标边缘服务器的0RTT握手。另外，当客户端连接到与目标边缘服务器相关联的其他边缘服务器时，也可以通过该配置信息实现跟其他边缘服务器进行0RTT握手。
本公开中，在目标边缘服务器接收客户端首次基于QUIC协议发送的握手请求后，可以获取包括有与客户端完成QUIC握手连接所需的服务器参数的配置信息，并将配置信息发送给客户端以完成握手连接；以及，将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据配置信息与客户端完成QUIC握手连接。通过应用本公开的技术方案，在目标边缘服务器为客户端生成有用于完成QUIC握手连接所需的配置信息后，还可以将该配置信息发送给与其关联的至少一个其他边缘服务器上，以达到其他边缘服务器可以通过该配置信息实现无需与该客户端再进行一次初始握手请求即可以进行业务数据交互的目的，进而提高了QUIC协议 下的业务处理效率。
在一些示例性的实施例中，在基于本公开上述方法的另一个实施例中，在S102(获取配置信息，配置信息中包括有与客户端完成QUIC握手连接所需的服务器参数)中，可以实施下述步骤：
检测本地存储区域中是否存储有配置信息，若无，生成服务器参数，并基于服务器参数生成配置信息。
一种方式中，该服务器参数可以为边缘服务器与客户端完成QUIC握手连接时所生成的质数和一个整数，以及根据质数、整数和随机生成的私钥计算出的公钥。以使后续可以将该质数、整数以及公钥合并作为服务器参数后，据此生成配置信息，并在后续通过REJ消息将配置信息发送给该客户端。
另一种方式中，目标边缘服务器在生成服务器参数之前，还可以先检测本地中是否存储有配置信息，并检测该配置信息是否过期，若检测到存储有未过期的配置信息，则直接从存储区域中进行调取。
可以理解的，如果存储有未过期的配置信息，为了节省目标边缘服务器的计算资源，本公开实施例中可以直接调取存储区域中存储的历史配置信息用于与客户端完成本次的握手连接，否则目标边缘服务器需要继续生成服务器参数，并基于服务器参数生成配置信息，进而与客户端完成本次QUIC握手连接。
在一些示例性的实施例中，在基于本公开上述方法的另一个实施例中，在S103(将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接)中，可以实施下述步骤：
确定目标边缘服务器所在的服务器集群，并将配置信息发送给在服务器集群中的至少一个其他边缘服务器。
一种方式中，为了避免边缘服务器之间跨域传输配置信息所引起的不信任和耗费收发资源的问题，本公开实施例中可以由目标边缘服务器仅向其所在的服务器集群内的其他边缘服务器发送配置信息。
可以理解的，同一服务器集群内的其他边缘服务器在后续与客户端的握手连接时，可以由客户端直接使用该配置信息直接计算出初始密钥K并加密传输数据，而其他边缘服务器由于本地也存储有该配置信息，因此其可以直接利用该配置信息对客户端传输的加密数据进行解密并在后续进行数据交互，从而实现了客户端与其他边缘服务器的0RTT握手。
举例来说，如图3所示，例如当目标边缘服务器所在的服务器集群共有3个边缘服务器，以边缘服务器A为目标边缘服务器，边缘服务器B和边缘服务器C为其他边缘服务器为例：
边缘服务器A在接收到客户端首次基于QUIC协议发送的初始握手请求之后，可以获取与该客户端完成QUIC握手连接所需的服务器参数的配置信息，并在将该配置信息发送给客户端以完成握手连接的同时，还可以将配置信息广播给集群内其他边缘服务器(例如边缘服务器B和边缘服务器C)的其中任意一个或多个。以使后续客户端再与边缘服务器B和/或边缘服务器C进行建连的过程中，可以直接用该配置信息实现0RTT握手。
在一些示例性的实施例中，在基于本公开上述方法的另一个实施例中，在S103(将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接)中，可以实施下述步骤：
将配置信息发送给同区域或同业务类型的至少一个其他边缘服务器。
在一些示例性的实施例中，为了避免边缘服务器向海量边缘服务器发送配置信息所导致的耗费较大发送资源的问题，本公开还可以选择由目标边缘服务器策略性的向指定的其他边缘服务器处发送配置信息。例如目标边缘服务器可以只向与其同处一个地理区域的其他边缘服务器发送配置信息，又或只向与其处理的业务类型相同的其他边缘服务器发送配置信息。
本公开实施例中提及的与目标边缘服务器同区域或同业务类型的其他边缘服务器可以为与目标边缘服务器所在同一个服务器集群范围，也可以不在同一个服务器集群范围。
在一些示例性的实施例中，在基于本公开上述方法的另一个实施例中，在S103(将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接)中，可以实施下述步骤：
将配置信息直接或间接发送给至少一个其他边缘服务器。
在一些示例性的实施例中，由于与目标边缘服务器相关联的其他边缘服务器的数量可能众多，因此如果目标边缘服务器需要向每个其他边缘服务器逐个发送配置信息，可能会导致耗费目标边缘服务器较大发送资源的问题。因此一种方式中，本公开还可以选择由目标边缘服务器生成一个用于告知其他边缘服务器帮助转发配置信息的转发指令，从而实现将配置信息直接或间接的发送给与其相关联的其他边缘服务器处。
一种方式中，转发指令可以为告知其他边缘服务器将配置信息转发给与自身相邻的边缘服务器，该指令可以是与发送配置信息时同时携带的指令。在此情况下，目标边缘服务器将配置信息发送给其他边缘服务器即可，后续的传播方式可以由其他边缘服务器再通过向与自身相邻的其他边缘服务器向外部进行逐层传播。可以理解的，这种方式可以分担目标边缘服务器发送配置信息的压力，进而节省了目标边缘服务器的数据收发资源。
另一种方式中，转发指令也可以为指示其他边缘服务器向指定的边缘服务器传输配置信息。可以理解的，例如当目标边缘服务器A与其他边缘服务器B之间的链路通道因为故障等原因发生阻塞时，会导致目标边缘服务器A无法向边缘服务器B传输配置信息。为了解决这一问题，本公开实施例中可以由目标边缘服务器A向其他边缘服务器C发送一个转发指令，以指示边缘服务器C通过其他的链路通道向边缘服务器B传输配置信息。优选的方式中，边缘服务器C可以为与边缘服务器B相邻的服务器。
一种实施方式中，本公开还提出一种握手连接的方法。图4示意性地示出了根据本公开实施方式的一种握手连接的方法的流程示意图。如图4所示，该方法应用于边缘服务器，包括：
S201，获取目标边缘服务器发送的配置信息，配置信息中包括有与客户端完成QUIC握手连接所需的服务器参数。
其中对于边缘服务器来说，首先接收目标边缘服务器发送的用于与客户端完成完整握手连接所需的配置信息，以使该边缘服务器在后续与客户端建立连接的过程中，通过该配置信息实现与客户端的0RTT握手。
具体来说，该配置信息可以为该目标边缘服务器首次与客户端基于QUIC协议建连的过程中，为客户端生成的包含有服务器参数的配置信息。可以理解的，由于QUIC协议的握手过程是需要客户端每与一个之前未曾交互的边缘服务器进行建连时，均需要完成一次初始握手连接过程并获取对应的配置信息后才可以进行数据交互。而边缘服务器在接收到目标边缘服务器发送的配置信息后，后续客户端可以直接根据客户端和边缘服务器均具备的配置信息传输加密业务数据，进而实现无需与该客户端再进行一次初始握手请求即可以进行业务数据交互的目的，从而提高了QUIC协议下二者的业务处理效率。
一种方式中，本公开中的边缘服务器可以为与目标边缘服务器相关联的边缘服务器。例如，当目标边缘服务器与其他边缘服务器部署在同一业务区域内时，二者相关联。或者，当目标边缘服务器与其他边缘服务器为处理同一种业务类型的服务器时，二者相关联等等。
另外，本公开不对边缘服务器的数量进行具体限定，例如可以为一个也可以为多个。其中在边缘服务器为多个时，目标边缘服务器可以向该多个边缘服务器中的一个转发该配置信息，也可以向该多个边缘服务器中的多个或全部转发该配置信息。
一种方式中，在边缘服务器接收目标边缘服务器发送的配置信息的方式中，和目标边缘 服务器处于同一集群的边缘服务器对目标边缘服务器广播的配置信息进行接收保存，也可以通过广播以外的方式，本公开对此不作限定。
S202，将配置信息存储到本地的预设存储区域中。
在边缘服务器接收到配置信息后，可以将该配置信息存储到本地的预设存储区域中。以使后续客户端在根据该配置信息向边缘服务器发送加密后的业务数据时，边缘服务器可以根据该配置信息对加密数据进行解密，进而完成0RTT的业务数据交互。
S203，当接收到客户端基于QUIC协议发送的握手请求时，根据配置信息，完成与客户端的握手连接。
其中，边缘服务器接收到客户端基于QUIC协议发送的握手请求时，可以根据客户端发来的公开数计算出初始密钥，并通过初始密钥K解密客户端发来的业务数据。其中边缘服务器会重新生成新的私钥c，然后通过p，g，c参数生成新的公钥C；且边缘服务器可以根据p、B和c三个参数算出新的密钥K2，并利用K2加密需要返回的业务数据，以及带上边缘服务器新生成的公钥C，在通过Server Hello消息返回给客户端。
通过应用本公开的技术方案，可以由边缘服务器接收目标边缘服务器为客户端生成的用于完成QUIC握手连接所需的配置信息后，将该配置信息进行存储，以达到后续可以通过该配置信息实现无需与该客户端再进行一次初始握手请求即可以进行业务数据交互的目的，进而提高了QUIC协议下的业务处理效率。
在一些示例性的实施例中，在基于本公开上述方法的另一个实施例中，在S201(获取目标边缘服务器发送的配置信息)，可以实施下述步骤：
若接收到目标边缘服务器发送的转发指令；
将配置信息转发给与目标边缘服务器相关联的至少一个边缘服务器处，配置信息用于实现边缘服务器与客户端完成握手连接。
在一些示例性的实施例中，为了避免目标边缘服务器向海量边缘服务器发送配置信息所导致耗费较大发送资源的问题，本公开还可以选择由边缘服务器接收目标边缘服务器发送的转发指令，其中，该转发指令用于指示边缘服务器将配置信息转发给与目标边缘服务器相关联的至少一个边缘服务器处，从而实现由边缘服务器为目标边缘服务器分担配置信息转发任务的目的。
其中，该转发指令的目的是由目标边缘服务器策略性的指示边缘服务器向指定的其他边缘服务器处发送配置信息。例如目标边缘服务器可以只向与其同处一个地理区域的边缘服务器发送配置信息，又或只向与其处理的业务类型相同的边缘服务器发送配置信息。
举例来说，转发指令可以为告知边缘服务器将配置信息转发给与自身相邻的边缘服务器，该指令可以是与发送配置信息时同时携带的指令，在这种情况下，边缘服务器在接收到转发指令后，可以将配置信息发送给自身相邻的一个或多个边缘服务器处。
在进行举例来说，转发指令也可以为指示其他边缘服务器向指定的边缘服务器传输配置信息。可以理解的，例如当目标边缘服务器A与其他边缘服务器B之间的链路通道因为故障等原因发生阻塞时，会导致目标边缘服务器A无法向边缘服务器B传输配置信息。为了解决这一问题，本公开实施例中可以由目标边缘服务器A向其他边缘服务器C发送一个转发指令，以指示边缘服务器C通过其他的链路通道向边缘服务器B传输配置信息。优选的方式中，边缘服务器C可以为与边缘服务器B相邻的服务器。
可以理解的，目标边缘服务器只需要将配置信息发送给与自身相邻的其他边缘服务器即可，后续的传播方式可以由其他边缘服务器再通过向自身相邻的其他边缘服务器向外部进行逐层传播。可以理解的，这种方式可以分担目标边缘服务器发送配置信息的压力，进而节省了目标边缘服务器的数据收发资源。
在一些示例性的实施例中，在基于本公开上述方法的另一个实施例中，在S202(将所述配置信息存储到本地的预设存储区域中)之后，可以实施下述步骤：
检测所述配置信息是否过期；
若未过期，从所述存储区域中调取所述配置信息；
若过期，则从目标边缘服务器获取最新的配置信息。
可以理解的，为了保证在后续无需与客户端再进行一次初始握手流程即可以进行业务数据交互的目的，需要保证边缘服务器处存储的配置信息与客户端处存储的配置信息一致。因此，为了避免事先缓存的配置信息已过期而导致边缘服务器无法与客户端实现0RTT功能的弊端，本公开需要确认所存储的配置信息是最新的配置信息，进而保证本地所存储的配置信息为与客户端处存储的配置信息为相同的配置信息，从而实现二者后续根据该相同的配置信息进行业务数据传输的目的。
一种方式中，本公开的技术方案为通过边缘服务器将与客户端进行QUIC握手连接所需的配置信息发送给与自身关联的其他边缘服务器的方式，来实现其他边缘服务器与客户端进行0RTT数据交互的目的。这样不仅可以节省客户端的运行资源以达到快速为用户提供业务服务的目的，还可以减轻边缘服务器的处理资源，进而达到优化整体业务处理系统的目的。
在本公开的另外一种实施方式中，如图5所示，本公开还提供一种握手连接的电子装置，其中，应用于目标边缘服务器，包括：
第一接收模块301，被配置为接收客户端首次基于QUIC协议发送的握手请求；
第一获取模块302，被配置为获取配置信息，所述配置信息中包括有与所述客户端完成QUIC握手连接所需的服务器参数；
发送模块303，被配置为根据所述配置信息，完成与所述客户端的握手连接；以及，将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据配置信息与客户端完成QUIC握手连接。
本公开中，目标边缘服务器接收客户端首次基于QUIC协议发送的初始握手请求后，可以获取包括有与客户端完成QUIC握手连接所需的服务器参数的配置信息，并将配置信息发送给客户端以完成握手连接；以及，将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据配置信息与客户端完成QUIC握手连接，以达到其他边缘服务器可以通过该配置信息实现无需与该客户端再进行一次初始握手请求即可以进行业务数据交互的目的，进而提高了QUIC协议下的业务处理效率。
在本公开的另外一种实施方式中，第一获取模块302，被配置为：
检测本地存储区域中是否存储有所述配置信息；
若无，生成所述服务器参数；
并基于所述服务器参数生成所述配置信息；
若有，检测所述配置信息是否过期；
若未过期，从所述存储区域中调取所述配置信息。
本公开的另外一种实施方式中，发送模块303，被配置为：
确定所述目标边缘服务器所在的服务器集群，并将所述配置信息发送给在所述服务器集群中的至少一个其他边缘服务器。
本公开的另外一种实施方式中，发送模块303，被配置为：
将所述配置信息发送给同区域或同业务类型的至少一个其他边缘服务器。
本公开的另外一种实施方式中，发送模块303，被配置为：
将所述配置信息直接或间接发送给所述至少一个其他边缘服务器。
在本公开的另外一种实施方式中，如图6所示，本公开还提供一种握手连接的电子装置。其中，应用于边缘服务器，包括：
第二获取模块304，被配置为获取目标边缘服务器发送的配置信息，所述配置信息中包 括有与客户端完成QUIC握手连接所需的服务器参数；
存储模块305，被配置为将所述配置信息存储到本地的预设存储区域中；
第二接收模块306，被配置为当接收到所述客户端首次基于QUIC协议发送的握手请求时，根据所述配置信息，完成与所述客户端的握手连接。
本公开中，在边缘服务器接收客户端首次基于QUIC协议发送的握手请求后，可以获取包括有与客户端完成QUIC握手连接所需的服务器参数的配置信息，并将配置信息发送给客户端以完成握手连接；以及，将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据配置信息与客户端完成QUIC握手连接，以达到其他边缘服务器可以通过该配置信息实现无需与该客户端再进行一次完整的握手流程即可以进行业务数据交互的目的。进而提高了QUIC协议下的业务处理效率。
本公开的另外一种实施方式中，存储模块305，被配置为：
检测所述配置信息是否过期；
若未过期，从所述存储区域中调取所述配置信息；
若过期，则从目标边缘服务器获取最新的配置信息。
本公开的另外一种实施方式中，第二接收模块306，被配置为：
若接收到所述目标边缘服务器发送的转发指令；
将所述配置信息转发给与所述目标边缘服务器相关联的至少一个边缘服务器处，所述配置信息用于实现边缘服务器与所述客户端完成握手连接。
图7是根据一示例性实施例示出的一种电子设备的逻辑结构框图。例如，电子设备400可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图7，电子设备400可以包括以下一个或多个组件：处理器401和存储器402。
处理器401可以包括一个或多个处理核心，比如4核心处理器、8核心处理器等。处理器401可以采用DSP(Digital Signal Processing，数字信号处理)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)、PLA(Programmable Logic Array，可编程逻辑阵列)中的至少一种硬件形式来实现。处理器401也可以包括主处理器和协处理器，主处理器是用于对在唤醒状态下的数据进行处理的处理器，也称CPU(Central Processing Unit，中央处理器)；协处理器是用于对在待机状态下的数据进行处理的低功耗处理器。在一些实施例中，处理器401可以在集成有GPU(Graphics Processing Unit，图像处理器)，GPU用于负责显示屏所需要显示的内容的渲染和绘制。一些实施例中，处理器401还可以包括AI(Artificial Intelligence，人工智能)处理器，该AI处理器用于处理有关机器学习的计算操作。
存储器402可以包括一个或多个计算机可读存储介质，该计算机可读存储介质可以是非暂态的。存储器402还可包括高速随机存取存储器，以及非易失性存储器，比如一个或多个磁盘存储设备、闪存存储设备。在一些实施例中，存储器402中的非暂态的计算机可读存储介质用于存储至少一个指令，该至少一个指令用于被处理器401所执行以实现本公开中方法实施例提供的互动特效标定方法。
在一些实施例中，电子设备400还可以包括有：外围设备接口403和至少一个外围设备。处理器401、存储器402和外围设备接口403之间可以通过总线或信号线相连。各个外围设备可以通过总线、信号线或电路板与外围设备接口403相连。具体地，外围设备包括：射频电路404、触摸显示屏405、摄像头406、音频电路407、定位组件408和电源409中的至少一种。
外围设备接口403可被用于将I/O(Input/Output，输入/输出)相关的至少一个外围设备连接到处理器401和存储器402。在一些实施例中，处理器401、存储器402和外围设备接口403被集成在同一芯片或电路板上；在一些其他实施例中，处理器401、存储器402和外围设 备接口403中的任意一个或两个可以在单独的芯片或电路板上实现，本实施例对此不加以限定。
射频电路404用于接收和发射RF(Radio Frequency，射频)信号，也称电磁信号。射频电路404通过电磁信号与通信网络以及其他通信设备进行通信。射频电路404将电信号转换为电磁信号进行发送，或者，将接收到的电磁信号转换为电信号。在一些示例性的实施例中，射频电路404包括：天线系统、RF收发器、一个或多个放大器、调谐器、振荡器、数字信号处理器、编解码芯片组、用户身份模块卡等等。射频电路404可以通过至少一种无线通信协议来与其它终端进行通信。该无线通信协议包括但不限于：城域网、各代移动通信网络(2G、3G、4G及5G)、无线局域网和/或WiFi(Wireless Fidelity，无线保真)网络。在一些实施例中，射频电路404还可以包括NFC(Near Field Communication，近距离无线通信)有关的电路，本公开对此不加以限定。
显示屏405用于显示UI(User Interface，用户界面)。该UI可以包括图形、文本、图标、视频及其它们的任意组合。当显示屏405是触摸显示屏时，显示屏405还具有采集在显示屏405的表面或表面上方的触摸信号的能力。该触摸信号可以作为控制信号输入至处理器401进行处理。此时，显示屏405还可以用于提供虚拟按钮和/或虚拟键盘，也称软按钮和/或软键盘。在一些实施例中，显示屏405可以为一个，设置电子设备400的前面板；在另一些实施例中，显示屏405可以为至少两个，分别设置在电子设备400的不同表面或呈折叠设计；在再一些实施例中，显示屏405可以是柔性显示屏，设置在电子设备400的弯曲表面上或折叠面上。甚至，显示屏405还可以设置成非矩形的不规则图形，也即异形屏。显示屏405可以采用LCD(Liquid Crystal Display，液晶显示屏)、OLED(Organic Light-Emitting Diode，有机发光二极管)等材质制备。
摄像头组件406用于采集图像或视频。在一些示例性的实施例中，摄像头组件406包括前置摄像头和后置摄像头。通常，前置摄像头设置在终端的前面板，后置摄像头设置在终端的背面。在一些实施例中，后置摄像头为至少两个，分别为主摄像头、景深摄像头、广角摄像头、长焦摄像头中的任意一种，以实现主摄像头和景深摄像头融合实现背景虚化功能、主摄像头和广角摄像头融合实现全景拍摄以及VR(Virtual Reality，虚拟现实)拍摄功能或者其它融合拍摄功能。在一些实施例中，摄像头组件406还可以包括闪光灯。闪光灯可以是单色温闪光灯，也可以是双色温闪光灯。双色温闪光灯是指暖光闪光灯和冷光闪光灯的组合，可以用于不同色温下的光线补偿。
音频电路407可以包括麦克风和扬声器。麦克风用于采集用户及环境的声波，并将声波转换为电信号输入至处理器401进行处理，或者输入至射频电路404以实现语音通信。出于立体声采集或降噪的目的，麦克风可以为多个，分别设置在电子设备400的不同部位。麦克风还可以是阵列麦克风或全向采集型麦克风。扬声器则用于将来自处理器401或射频电路404的电信号转换为声波。扬声器可以是传统的薄膜扬声器，也可以是压电陶瓷扬声器。当扬声器是压电陶瓷扬声器时，不仅可以将电信号转换为人类可听见的声波，也可以将电信号转换为人类听不见的声波以进行测距等用途。在一些实施例中，音频电路407还可以包括耳机插孔。
定位组件408用于定位电子设备400的当前地理位置，以实现导航或LBS(Location Based Service，基于位置的服务)。定位组件408可以是基于美国的GPS(Global Positioning System，全球定位系统)、中国的北斗系统、俄罗斯的格雷纳斯系统或欧盟的伽利略系统的定位组件。
电源409用于为电子设备400中的各个组件进行供电。电源409可以是交流电、直流电、一次性电池或可充电电池。当电源409包括可充电电池时，该可充电电池可以支持有线充电或无线充电。该可充电电池还可以用于支持快充技术。
在一些实施例中，电子设备400还包括有一个或多个传感器410。该一个或多个传感器410包括但不限于：加速度传感器411、陀螺仪传感器412、压力传感器413、指纹传感器414、光学传感器415以及接近传感器416。
加速度传感器411可以检测以电子设备400建立的坐标系的三个坐标轴上的加速度大小。比如，加速度传感器411可以用于检测重力加速度在三个坐标轴上的分量。处理器401可以根据加速度传感器411采集的重力加速度信号，控制触摸显示屏405以横向视图或纵向视图进行用户界面的显示。加速度传感器411还可以用于游戏或者用户的运动数据的采集。
陀螺仪传感器412可以检测电子设备400的机体方向及转动角度，陀螺仪传感器412可以与加速度传感器411协同采集用户对电子设备400的3D动作。处理器401根据陀螺仪传感器412采集的数据，可以实现如下功能：动作感应(比如根据用户的倾斜操作来改变UI)、拍摄时的图像稳定、游戏控制以及惯性导航。
压力传感器413可以设置在电子设备400的侧边框和/或触摸显示屏405的下层。当压力传感器413设置在电子设备400的侧边框时，可以检测用户对电子设备400的握持信号，由处理器401根据压力传感器413采集的握持信号进行左右手识别或快捷操作。当压力传感器413设置在触摸显示屏405的下层时，由处理器401根据用户对触摸显示屏405的压力操作，实现对UI界面上的可操作性控件进行控制。可操作性控件包括按钮控件、滚动条控件、图标控件、菜单控件中的至少一种。
指纹传感器414用于采集用户的指纹，由处理器401根据指纹传感器414采集到的指纹识别用户的身份，或者，由指纹传感器414根据采集到的指纹识别用户的身份。在识别出用户的身份为可信身份时，由处理器401授权该用户执行相关的敏感操作，该敏感操作包括解锁屏幕、查看加密信息、下载软件、支付及更改设置等。指纹传感器414可以被设置电子设备400的正面、背面或侧面。当电子设备400上设置有物理按键或厂商Logo时，指纹传感器414可以与物理按键或厂商Logo集成在一起。
光学传感器415用于采集环境光强度。在一个实施例中，处理器401可以根据光学传感器415采集的环境光强度，控制触摸显示屏405的显示亮度。具体地，当环境光强度较高时，调高触摸显示屏405的显示亮度；当环境光强度较低时，调低触摸显示屏405的显示亮度。在另一个实施例中，处理器401还可以根据光学传感器415采集的环境光强度，动态调整摄像头组件406的拍摄参数。
接近传感器416，也称距离传感器，通常设置在电子设备400的前面板。接近传感器416用于采集用户与电子设备400的正面之间的距离。在一个实施例中，当接近传感器416检测到用户与电子设备400的正面之间的距离逐渐变小时，由处理器401控制触摸显示屏405从亮屏状态切换为息屏状态；当接近传感器416检测到用户与电子设备400的正面之间的距离逐渐变大时，由处理器401控制触摸显示屏405从息屏状态切换为亮屏状态。
本领域技术人员可以理解，图4中示出的结构并不构成对电子设备400的限定，可以包括比图示更多或更少的组件，或者组合某些组件，或者采用不同的组件布置。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器404，上述指令可由电子设备400的处理器420执行以完成上述基于握手连接的方法，该方法包括：接收客户端首次基于QUIC协议发送的握手请求；获取配置信息，所述配置信息中包括有与所述客户端完成QUIC握手连接所需的服务器参数；将所述配置信息发送给所述客户端以完成QUIC握手连接；以及，将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接。在一些示例性的实施例中，上述指令还可以由电子设备400的处理器420执行以完成上述示例性实施例中所涉及的其他步骤。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
在示例性实施例中，还提供了一种应用程序/计算机程序产品，包括一条或多条指令，该一条或多条指令可以由电子设备400的处理器420执行，以完成上述基于握手连接的方法，该方法包括：接收客户端首次基于QUIC协议发送的握手请求；获取配置信息，所述配置信息中包括有与所述客户端完成QUIC握手连接所需的服务器参数；将所述配置信息发送给所 述客户端以完成QUIC握手连接；以及，将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接。在一些示例性的实施例中，上述指令还可以由电子设备400的处理器420执行以完成上述示例性实施例中所涉及的其他步骤。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
工业实用性
本公开中，在边缘服务器接收客户端首次基于QUIC协议发送的初始握手请求后，可以获取包括有与客户端完成QUIC握手连接所需的服务器参数的配置信息，并将配置信息发送给客户端以完成握手连接；以及，将配置信息发送给与目标边缘服务器相关联的至少一个其他边缘服务器，以使其他边缘服务器接收到客户端基于QUIC协议发送的握手请求时，根据配置信息与所述客户端完成QUIC握手连接。通过应用本公开的技术方案，在边缘服务器为客户端生成用于完成QUIC握手连接所需的配置信息后，还可以将该配置信息发送给与其关联的至少一个其他边缘服务器上，以达到其他边缘服务器可以通过该配置信息实现无需与该客户端再进行一次初始握手请求即可以进行业务数据交互的目的，进而提高了QUIC协议下的业务处理效率。

Claims (13)

  1. 一种握手连接的方法，应用于目标边缘服务器，包括：
    接收客户端首次基于QUIC协议发送的握手请求；
    获取配置信息，所述配置信息中包括有与所述客户端完成QUIC握手连接所需的服务器参数；
    将所述配置信息发送给所述客户端以完成QUIC握手连接；以及，
    将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接。
  2. 如权利要求1所述的方法，其中，所述获取配置信息，包括：
    检测本地存储区域中是否存储有所述配置信息；
    若无，生成所述服务器参数；
    并基于所述服务器参数生成所述配置信息。
  3. 如权利要求2所述的方法，在所述检测本地存储区域中是否存储有所述配置信息之后，还包括：
    若有，检测所述配置信息是否过期；
    若未过期，从所述存储区域中调取所述配置信息。
  4. 如权利要求1所述的方法，其中，所述将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，包括：
    确定所述目标边缘服务器所在的服务器集群，并将所述配置信息发送给在所述服务器集群中的至少一个其他边缘服务器。
  5. 如权利要求1所述的方法，其中，所述将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，包括：
    将所述配置信息发送给同区域或同业务类型的至少一个其他边缘服务器。
  6. 如权利要求1所述的方法，其中，所述将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，包括：
    将所述配置信息直接或间接发送给所述至少一个其他边缘服务器。
  7. 一种握手连接的方法，应用于边缘服务器，包括：
    获取目标边缘服务器发送的配置信息，所述配置信息中包括有与客户端完成QUIC握手连接所需的服务器参数；
    将所述配置信息存储到本地的预设存储区域中；
    当接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息，完成与所述客户端的握手连接。
  8. 如权利要求7所述的方法，在所述将所述配置信息存储到本地的预设存储区域中之后，还包括：
    检测所述配置信息是否过期；
    若未过期，从所述存储区域中调取所述配置信息；
    若过期，则从目标边缘服务器获取最新的配置信息。
  9. 一种握手连接的电子装置，应用于目标边缘服务器，包括：
    第一接收模块，被配置为接收客户端首次基于QUIC协议发送的握手请求；
    第一获取模块，被配置为获取配置信息，所述配置信息中包括有与所述客户端完成QUIC握手连接所需的服务器参数；
    发送模块，被配置为根据所述配置信息，完成与所述客户端的握手连接；以及，将所述配置信息发送给与所述目标边缘服务器相关联的至少一个其他边缘服务器，以使所述其他边缘服务器接收到所述客户端基于QUIC协议发送的握手请求时，根据所述配置信息与所述客户端完成QUIC握手连接。
  10. 一种握手连接的电子装置，应用于边缘服务器，包括：
    第二获取模块，被配置为获取目标边缘服务器发送的配置信息，所述配置信息中包括有与客户端完成QUIC握手连接所需的服务器参数；
    存储模块，被配置为将所述配置信息存储到本地的预设存储区域中；
    第二接收模块，被配置为当接收到所述客户端首次基于QUIC协议发送的握手请求时，根据所述配置信息，完成与所述客户端的握手连接。
  11. 一种电子设备，包括：
    存储器，用于存储可执行指令；以及，
    处理器，用于与所述存储器显示以执行所述可执行指令从而完成权利要求1-6或7-8中任一所述握手连接的方法的操作。
  12. 一种计算机可读存储介质，用于存储计算机可读取的指令，其中，所述指令被执行时执行权利要求1-6或7-8中任一所述握手连接的方法的操作。
  13. 一种计算机程序产品，包括计算机程序，其中，所述计算机程序被处理器执行实现若权利要求1-6或7-8中任一项所述的方法。
PCT/CN2022/139361 2021-12-17 2022-12-15 握手连接的方法、电子装置、电子设备以及介质 WO2023109913A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111554091.XA CN116266835A (zh) 2021-12-17 2021-12-17 握手连接的方法、电子装置、电子设备以及介质
CN202111554091.X 2021-12-17

Publications (1)

Publication Number Publication Date
WO2023109913A1 true WO2023109913A1 (zh) 2023-06-22

Family

ID=86743819

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/139361 WO2023109913A1 (zh) 2021-12-17 2022-12-15 握手连接的方法、电子装置、电子设备以及介质

Country Status (2)

Country Link
CN (1) CN116266835A (zh)
WO (1) WO2023109913A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106059986A (zh) * 2015-04-22 2016-10-26 阿里巴巴集团控股有限公司 Ssl会话重用的方法和服务器
CN111756674A (zh) * 2019-03-28 2020-10-09 上海哔哩哔哩科技有限公司 网络通信方法、系统、设备及计算机可读存储介质
CN112637348A (zh) * 2020-12-23 2021-04-09 北京金山云网络技术有限公司 一种连接建立方法、装置、系统及电子设备
CN112839108A (zh) * 2021-03-02 2021-05-25 北京金山云网络技术有限公司 连接建立方法、装置、设备、数据网络及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106059986A (zh) * 2015-04-22 2016-10-26 阿里巴巴集团控股有限公司 Ssl会话重用的方法和服务器
CN111756674A (zh) * 2019-03-28 2020-10-09 上海哔哩哔哩科技有限公司 网络通信方法、系统、设备及计算机可读存储介质
CN112637348A (zh) * 2020-12-23 2021-04-09 北京金山云网络技术有限公司 一种连接建立方法、装置、系统及电子设备
CN112839108A (zh) * 2021-03-02 2021-05-25 北京金山云网络技术有限公司 连接建立方法、装置、设备、数据网络及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHEN SHAN; JERO SAMUEL; JAGIELSKI MATTHEW; BOLDYREVA ALEXANDRA; NITA-ROTARU CRISTINA: "Secure Communication Channel Establishment: TLS 1.3 (over TCP Fast Open) versus QUIC", JOURNAL OF CRYPTOLOGY, SPRINGER US, NEW YORK, vol. 34, no. 3, 24 May 2021 (2021-05-24), New York, XP037463050, ISSN: 0933-2790, DOI: 10.1007/s00145-021-09389-w *

Also Published As

Publication number Publication date
CN116266835A (zh) 2023-06-20

Similar Documents

Publication Publication Date Title
WO2019091289A1 (zh) 生成签名的方法、电子设备及存储介质
CN111225042B (zh) 数据传输的方法、装置、计算机设备以及存储介质
CN108833607B (zh) 物理地址获取方法、装置及可读介质
WO2020001564A1 (zh) 一种处理任务的方法、装置及系统
CN111092809B (zh) 实时推送信息的方法、装置、计算机设备及存储介质
CN112312226B (zh) 连麦方法、系统、装置、电子设备及存储介质
CN111866140B (zh) 融合管理设备、管理系统、服务调用方法及介质
CN111355774B (zh) 一种基于p2p的服务通信方法、装置及系统
WO2019129092A1 (zh) 一种降帧率拍照方法、移动终端及存储介质
WO2021238564A1 (zh) 显示设备及其畸变参数确定方法、装置、系统及存储介质
CN111106902B (zh) 数据报文传输方法、装置、设备及计算机可读存储介质
WO2023125946A1 (zh) 用户访问请求处理方法、装置、设备、介质及产品
CN113225688B (zh) 数据传输方法及显示装置
CN113726521A (zh) 通信方法、装置、电子设备及可读存储介质
CN110290191B (zh) 资源转移结果处理方法、装置、服务器、终端及存储介质
CN111770556A (zh) 网络连接的方法、装置、电子设备及介质
CN111131392A (zh) 处理消息的方法、装置、电子设备及介质
CN113852459A (zh) 密钥协商方法、设备及计算机可读存储介质
CN109688064B (zh) 数据传输方法、装置、电子设备和存储介质
CN110597840A (zh) 基于区块链的伴侣关系建立方法、装置、设备及存储介质
WO2023109913A1 (zh) 握手连接的方法、电子装置、电子设备以及介质
WO2022247750A1 (zh) 访问请求的处理方法、电子装置、电子设备以及介质
CN111447132B (zh) 数据传输方法、装置、系统以及计算机存储介质
CN110708582B (zh) 同步播放的方法、装置、电子设备及介质
CN113518383B (zh) 网络管理方法、装置、系统、设备及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22906658

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE