WO2023125946A1 - 用户访问请求处理方法、装置、设备、介质及产品 - Google Patents

用户访问请求处理方法、装置、设备、介质及产品 Download PDF

Info

Publication number
WO2023125946A1
WO2023125946A1 PCT/CN2022/143988 CN2022143988W WO2023125946A1 WO 2023125946 A1 WO2023125946 A1 WO 2023125946A1 CN 2022143988 W CN2022143988 W CN 2022143988W WO 2023125946 A1 WO2023125946 A1 WO 2023125946A1
Authority
WO
WIPO (PCT)
Prior art keywords
user access
access request
response message
protocol
edge server
Prior art date
Application number
PCT/CN2022/143988
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 WO2023125946A1 publication Critical patent/WO2023125946A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/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
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • 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
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • H04L67/1078—Resource delivery mechanisms
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • Embodiments of the present disclosure relate to but are not limited to a user access request processing method, device, device, medium and product.
  • 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 be widely used, one of the reasons is that it can achieve the purpose of making business processing more efficient than HTTPS or HTTP transmission protocols, but in related technologies, it often occurs when the client and the edge server conduct business In the process of data interaction, since the transmission protocols of the two are not unified, if the routing is completely followed by the client's protocol, business processing will fail, which will also affect the efficiency of business processing.
  • the present disclosure provides a user access request processing method, electronic device, electronic equipment, and media.
  • the technical solution of the present disclosure can solve the problem of inability to transmit resource data caused by the inconsistency of the transmission protocols between the edge server and the client in the related art. .
  • a method for processing a user access request is provided, which is applied to an edge server, including:
  • a first response message is sent to the client based on the HTTPS or HTTP protocol, and the first response message is used to instruct the client to send a user access message based on the QUIC protocol next time. ask;
  • the user access request after detecting whether the user access request contains identification information corresponding to the QUIC protocol, it further includes:
  • the user access request after detecting whether the user access request contains identification information corresponding to the QUIC protocol, it further includes:
  • the resource acquisition request after the resource acquisition request is sent to the upper-layer server based on the QUIC protocol, it further includes:
  • the third response message includes resource data corresponding to the resource acquisition request
  • the resource acquisition request after the resource acquisition request is sent to the upper-layer server based on the QUIC protocol, it further includes:
  • the fourth response message returned by the upper-layer server is obtained, the fourth response message is used to instruct the edge server to send the resource acquisition request to the upper-layer server based on the HTTPS or HTTP protocol next time;
  • the edge server obtains the resource data from the upper layer server based on HTTPS or HTTP protocol, it sends the resource data to the client based on QUIC protocol.
  • the method further includes:
  • a method for processing user access requests is provided, which is applied to a client, including:
  • the method after receiving the second response message sent by the edge server, the method further includes:
  • an electronic device for processing user access requests which is applied to an edge server, including:
  • the first receiving module is configured to receive a user access request sent by the client based on the HTTPS or HTTP protocol;
  • a detection module configured to detect whether the user access request contains identification information corresponding to the QUIC protocol
  • the first sending module is configured to, if any, send a first response message to the client based on the HTTPS or HTTP protocol when it is determined that it supports the QUIC protocol, and the first response message is used to indicate the client The next time a user access request is sent based on the QUIC protocol;
  • the second receiving module is configured to receive the user access request sent by the client based on the QUIC protocol
  • the second sending module is configured to send a second response message to the client based on the QUIC protocol, where the second response message includes resource data corresponding to the user access request.
  • an electronic device for processing a user access request which is applied to a client, including:
  • the third sending module is configured to send a user access request to the edge server based on the HTTPS or HTTP protocol, and the user access request includes identification information corresponding to the QUIC protocol;
  • the third receiving module is configured to receive a first response message sent by the edge server, where the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time;
  • a fourth sending module configured to send the user access request to the edge server based on the QUIC protocol
  • a fourth receiving module configured to receive a second response message sent by the edge server, where the second response message includes resource data corresponding to the user access request.
  • an electronic device comprising:
  • a display configured to display with the memory to execute the executable instructions so as to complete any one of the above-mentioned operations of the user access request processing method.
  • a computer-readable storage medium for storing computer-readable instructions, and when the instructions are executed, operations of any one of the above-mentioned user access request processing methods are performed.
  • the edge server receives the user access request sent by the client based on the HTTPS or HTTP protocol; detects whether the user access request contains identification information corresponding to the QUIC protocol; if so, determines that it supports the QUIC protocol based on The HTTPS or HTTP protocol sends the first response message to the client, and the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time; receive the user access request sent by the client based on the QUIC protocol; send a message to the client based on the QUIC protocol Sending a second response message, where the second response message includes resource data corresponding to the user access request.
  • the user access request initiated by the client to the edge server based on the HTTPS or HTTP protocol can carry an identification information used to inform the edge server that the client supports the QUIC protocol, so that the edge server can Support the QUIC protocol to return different response messages to the client in a targeted manner, and then perform data transmission through the corresponding protocol, thus avoiding the problem that the two cannot perform resource data transmission when the edge server does not support the QUIC protocol .
  • FIG. 1 is a schematic diagram of a method for processing a user access request proposed by the present disclosure
  • FIG. 2 is a schematic diagram of another method for processing user access requests proposed in the present disclosure
  • 3-4 are schematic diagrams of an electronic device for processing user access requests proposed by the present disclosure.
  • FIG. 5 is a schematic diagram of an electronic device for processing user access requests proposed by the present disclosure.
  • FIGS. 1-3 A processing method for user access requests according to an exemplary embodiment of the present disclosure will be described below with reference to FIGS. 1-3 . It should be noted that the following application scenarios are only shown to facilitate understanding of the spirit and principles 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 schematically shows a schematic flowchart of a method for processing a user access request according to an embodiment of the present disclosure. As shown in Figure 1, the method is applied to edge servers, including:
  • S101 Receive a user access request sent by a client based on an HTTPS or HTTP protocol.
  • 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, individual CDN vendors have begun to provide processing capabilities for QUIC protocol requests.
  • the QUIC protocol can be widely used, one of the reasons is that it can achieve higher business processing efficiency than HTTPS or HTTP transmission protocols.
  • HTTPS or HTTP transmission protocols it often occurs that during the resource data transmission process between the edge server and the client supporting the QUIC protocol, the edge server cannot send the requested resource data to the client because the edge server does not support the QUIC protocol. This further affects the user's business processing efficiency.
  • the client sends the user access request to the edge server through the HTTPS or HTTP protocol generally supported by the edge server.
  • the edge server when the edge server receives the user access request sent by the client, it detects whether the user access request contains identification information corresponding to the QUIC protocol, and if so, the edge server determines that the client It is a client that supports the QUIC protocol.
  • the identification information can be a set character string, including but not limited to 001, a, A, understandably, as long as It may be agreed in advance on the edge server side that the fields such as numbers or letters correspond to the meaning that the client supports the QUIC protocol, and the present disclosure does not limit the identification information.
  • this disclosure proposes a method that is detected by the edge server If it supports the QUIC protocol itself, it actively initiates a first response message to the client to instruct the client to send a user access request to the edge server based on a higher version protocol (that is, switching from HTTPS or HTTP protocol to QUIC protocol), so that Next time, the client sends a user access request to the edge server based on the QUIC protocol, so that the client and the edge server that support the QUIC protocol can transmit resource data based on the QUIC protocol with faster data transmission efficiency.
  • a higher version protocol that is, switching from HTTPS or HTTP protocol to QUIC protocol
  • S105 Send a second response message to the client based on the QUIC protocol, where the second response message includes resource data corresponding to the user access request.
  • the edge server receives the user access request sent by the client based on the QUIC protocol, it first detects whether the resource data corresponding to the user access request is stored in its own storage area, and if so, reads the resource data , and send the resource data to the client based on the QUIC protocol.
  • the user access request sent by the client based on the HTTPS or HTTP protocol is received; whether the user access request contains identification information corresponding to the QUIC protocol is detected;
  • the HTTP protocol sends a first response message to the client, and the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time; receive the user access request sent by the client based on the QUIC protocol; send a request to the client based on the QUIC protocol A second response message, where the second response message includes resource data corresponding to the user access request.
  • the user access request initiated by the client to the edge server based on the HTTPS or HTTP protocol can carry an identification information used to inform the edge server that the client supports the QUIC protocol, so that the edge server can Support the QUIC protocol to return different response messages to the client in a targeted manner, and then perform data transmission through the corresponding protocol, thus avoiding the problem that the two cannot perform resource data transmission when the edge server does not support the QUIC protocol .
  • the edge server when the edge server receives the user access request sent by the client and detects that the user access request does not contain the identification information corresponding to the QUIC protocol, the edge server can determine that the client is Clients that do not support the QUIC protocol, so the edge server sends the resource data corresponding to the user's access request to the client based on the HTTPS or HTTP protocol, thereby ensuring that the client can receive the resource data in a timely manner to avoid problems that affect the progress of business processing .
  • the edge server does not store the resource data corresponding to the user's access request, it sends a resource acquisition request to the upper-layer server.
  • This disclosure does not specifically limit the upper-layer server, for example, it can be other edge servers, parent servers, central servers and any one of the origin server.
  • the edge server sends a resource acquisition request to the source station or any of the other edge servers, parent servers, and central servers that store the resource data, and after obtaining the corresponding resource data, sends it to the client based on the QUIC protocol.
  • the resource data is not specifically limit the upper-layer server, for example, it can be other edge servers, parent servers, central servers and any one of the origin server.
  • the edge server sends a resource acquisition request to the source station or any of the other edge servers, parent servers, and central servers that store the resource data, and after obtaining the corresponding resource data, sends it to the client based on the QUIC protocol.
  • the resource data is not specifically limit the upper-layer server, for example, it can be other edge
  • the third response message includes resource data corresponding to the resource acquisition request
  • the resource data is sent to the client based on the QUIC protocol.
  • the upper-layer server will send the requested resource data to the edge server based on the QUIC protocol. Send the resource data requested by the client to ensure that the client can receive the resource data in time to avoid problems that affect the progress of business processing.
  • the fourth response message returned by the upper-layer server is obtained, the fourth response message is used to instruct the edge server to send a resource acquisition request to the upper-layer server based on the HTTPS or HTTP protocol next time;
  • the edge server obtains the resource data from the upper-layer server based on the HTTPS or HTTP protocol, it sends the resource data to the client based on the QUIC protocol.
  • the upper-layer server can first detect whether it supports the QUIC protocol. When the upper-layer server detects that it does not support the QUIC protocol , you can no longer try to parse the request, but actively send a response message to the edge server that sends the resource acquisition request based on the QUIC protocol to instruct it to send the resource acquisition request based on the lower version protocol.
  • the edge server after receiving the response message, the edge server resends the resource acquisition request to the upper-layer server based on protocol downgrade (switching from QUIC protocol to HTTPS or HTTP protocol), so that the upper-layer server that does not support the QUIC protocol can Send resource data to the edge through HTTPS or HTTP protocol.
  • protocol downgrade switching from QUIC protocol to HTTPS or HTTP protocol
  • the fourth response message sent by the upper-layer server corresponds to a response message containing an error identifier or a response message indicating protocol downgrade, wherein the response error identifier can be an ECONNREFUSED error code or a 5XX status code, that is, when the upper-layer server is in After detecting that it does not support the QUIC protocol, it generates an ECONNREFUSED error code or 5XX status code and sends it to the edge server.
  • the response error identifier can be an ECONNREFUSED error code or a 5XX status code
  • the edge server parses the response message and gets the ECONNREFUSED error code or 5XX status code, it can use the error code Or the 5XX status code directly determines that the upper-layer server does not support the QUIC protocol, and then sends the resource acquisition request again based on the HTTPS or HTTP protocol.
  • the fourth response message received by the edge server corresponds to a timeout response message or the fourth response message is empty, it can send a resource acquisition request to the upper-layer server based on the QUIC protocol again, so as to further confirm whether the upper-layer server supports QUIC protocol.
  • the fourth response message sent by the upper-layer server still corresponds to a timeout response message (such as a response message with a status code of 504) or the upper-layer server does not send a response message, that is, when the fourth response message is empty, then determine that the upper-layer The server does not support the QUIC protocol, and then sends the resource acquisition request again based on the HTTPS or HTTP protocol.
  • the upper-layer server can return different response messages to the client according to whether it supports the QUIC protocol, thereby avoiding Supporting the QUIC protocol results in the failure of the upper-layer server to send the requested resource data to the edge server, thereby affecting the efficiency of user business processing.
  • the edge server receives the user access request sent by the client based on the QUIC protocol, it first detects whether the resource data corresponding to the user access request is stored in its own storage area, and if so, reads the resource data , and send the resource data to the client based on the QUIC protocol.
  • the user access request initiated by the client to the edge server based on the HTTPS or HTTP protocol can carry an identification information used to inform the edge server that the client supports the QUIC protocol, so that the edge server can Support the QUIC protocol to return different response messages to the client in a targeted manner, and then use the corresponding protocol for data transmission, thereby avoiding the problem that the two cannot perform resource data transmission when the edge server does not support the QUIC protocol .
  • Fig. 2 schematically shows a schematic flowchart of a method for processing a user access request according to an embodiment of the present disclosure. As shown in Figure 2, this method is applied to the client, 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, individual CDN vendors have begun to provide processing capabilities for QUIC protocol requests.
  • the QUIC protocol can be widely used, one of the reasons is that it can achieve higher business processing efficiency than HTTPS or HTTP transmission protocols.
  • HTTPS or HTTP transmission protocols it often occurs that during the process of resource data transmission between the edge server and the client supporting the QUIC protocol, the edge server cannot send the requested information to the client because the edge server does not support the QUIC protocol.
  • Resource data which in turn affects the efficiency of user business processing.
  • the client since the client does not know whether the edge server it is communicating with supports the QUIC protocol, and if the edge server does not support the QUIC protocol, sending a request to it directly based on the QUIC protocol may cause the edge server to fail to respond question. Therefore, in this disclosure, the client can firstly send a user access request to the edge server with the HTTPS or HTTP protocol that must be supported by the edge server, and in order to achieve the purpose of prioritizing resource data transmission based on the QUIC protocol, the client needs to add a user in the request.
  • the edge server To inform the edge server that the client supports the identification information of the QUIC protocol, so that the edge server actively initiates a request to the client when it detects the user access request with the identification information and also supports the QUIC protocol. Instruct the client to send the first response message of the user access request to the edge server based on the protocol upgrade method (that is, switch from HTTPS or HTTP protocol to the QUIC protocol), so as to achieve the purpose of the client sending the user access request based on the QUIC protocol next time, thereby Realize that both the client and the edge server that support the QUIC protocol can transmit resource data based on the QUIC protocol with faster data transmission efficiency.
  • the protocol upgrade method that is, switch from HTTPS or HTTP protocol to the QUIC protocol
  • S202 Receive a first response message sent by the edge server, where the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time.
  • the client that sends user access requests based on the HTTPS or HTTP protocol resends resources to the edge server after receiving the message from the edge server indicating that it is based on a protocol upgrade (switching from HTTPS or HTTP protocol to QUIC protocol)
  • a protocol upgrade switching from HTTPS or HTTP protocol to QUIC protocol
  • the user access request is resent to the edge server based on the QUIC protocol, so that the client and the edge server that both support the QUIC protocol can transmit resource data through the QUIC protocol with faster transmission efficiency.
  • the edge server when the edge server receives the user access request sent by the client based on the QUIC protocol, the edge server also sends the user access request to the edge server based on the QUIC protocol, so that the client and the edge server that both support the QUIC protocol can communicate.
  • the QUIC protocol with faster transmission efficiency is used to transmit resource data.
  • S204 Receive a second response message sent by the edge server, where the second response message includes resource data corresponding to the user access request.
  • the edge server after the edge server receives the user access request sent by the client based on the QUIC protocol, it can retrieve the resource data from its own storage area or the server that stores the resource data (for example, it can be an upper layer server or other edge server, parent Any one of the server and the central server) retrieves the corresponding resource data, and after obtaining the resource data, sends a second response message containing the resource data to the client based on the QUIC protocol.
  • the user access request is sent to the edge server based on the HTTPS or HTTP protocol, and the user access request contains identification information corresponding to the QUIC protocol; the first response message sent by the edge server is received, and the first response message is used to instruct the client Next time, the user access request is sent based on the QUIC protocol; the user access request is sent to the edge server based on the QUIC protocol; and the second response message sent by the edge server is received, and the second response message includes resource data corresponding to the user access request.
  • the edge server can return different response messages to the client according to whether it supports the QUIC protocol, thereby Realize the data transmission between the client and the edge server that both support the QUIC protocol based on the QUIC protocol, and it can also avoid the situation that the edge server cannot parse the user request sent by the client when the transmission protocol between the edge server and the client is not uniform. The problem that the two cannot perform resource data transmission.
  • the user access request is sent to the edge server based on the QUIC protocol.
  • the client determines the protocol supported by the edge server, it can record the association relationship between the edge server and the QUIC protocol in the local storage area (for example, it can be stored in historical access data).
  • the client can directly send resource acquisition requests to the edge server based on the QUIC protocol.
  • the client when it subsequently sends a resource acquisition request to the edge server, it can first obtain the historical access data pre-stored in the local storage area, and traverse the historical access data to see if there is a historical access record of the edge server. exists, then read the relationship between the transmission protocol associated with the edge server stored in the historical access record, that is, the client can determine whether the edge server supports the QUIC protocol through the historical access record, and if it is confirmed that it supports it, it can be directly based on The QUIC protocol sends a resource acquisition request to the edge server. Understandably, if the QUIC protocol is not supported, the resource acquisition request can also be directly sent to the edge server based on the HTTPS or HTTP protocol.
  • the above-mentioned embodiments of the present disclosure can avoid that when subsequent clients request resource data from the edge server again, they do not need to send resource acquisition requests to the edge server based on HTTPS or HTTP protocol and QUIC protocol to obtain the corresponding resource data, thereby saving The transmission time of business data is shortened, and the data sending and receiving resources of the server are also reduced.
  • the present disclosure further provides an electronic device for processing user access requests.
  • applied to the edge server including,
  • the first receiving module 301 is configured to receive a user access request sent by the client based on the HTTPS or HTTP protocol;
  • the detection module 302 is configured to detect whether the user access request contains identification information corresponding to the QUIC protocol;
  • the first sending module 303 is configured to send a first response message to the client based on the HTTPS or HTTP protocol if it is determined that it supports the QUIC protocol, and the first response message is used to indicate that the client The next time the terminal sends a user access request based on the QUIC protocol;
  • the second receiving module 304 is configured to receive the user access request sent by the client based on the QUIC protocol
  • the second sending module 305 is configured to send a second response message to the client based on the QUIC protocol, where the second response message includes resource data corresponding to the user access request.
  • the user access request sent by the client based on the HTTPS or HTTP protocol is received; whether the user access request contains identification information corresponding to the QUIC protocol is detected;
  • the HTTP protocol sends a first response message to the client, and the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time; receive the user access request sent by the client based on the QUIC protocol; send a request to the client based on the QUIC protocol A second response message, where the second response message includes resource data corresponding to the user access request.
  • the user access request initiated by the client to the edge server based on the HTTPS or HTTP protocol can carry an identification information used to inform the edge server that the client supports the QUIC protocol, so that the edge server can Support the QUIC protocol to return different response messages to the client in a targeted manner, and then perform data transmission through the corresponding protocol, thus avoiding the problem that the two cannot perform resource data transmission when the edge server does not support the QUIC protocol .
  • the detection module 302 is configured to:
  • the detection module 302 is configured to:
  • the first sending module 303 is configured to:
  • the third response message includes resource data corresponding to the resource acquisition request
  • the second sending module 305 is configured to:
  • the fourth response message returned by the upper-layer server is obtained, the fourth response message is used to instruct the edge server to send the resource acquisition request to the upper-layer server based on the HTTPS or HTTP protocol next time;
  • the edge server obtains the resource data from the upper layer server based on HTTPS or HTTP protocol, it sends the resource data to the client based on QUIC protocol.
  • the second sending module 305 is configured to:
  • the present disclosure further provides an electronic device for processing user access requests.
  • applied to the client including:
  • the third sending module 306 is configured to send a user access request to the edge server based on the HTTPS or HTTP protocol, and the user access request includes identification information corresponding to the QUIC protocol;
  • the third receiving module 307 is configured to receive a first response message sent by the edge server, where the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time;
  • the fourth sending module 308 is configured to send the user access request to the edge server based on the QUIC protocol
  • the fourth receiving module 309 is configured to receive a second response message sent by the edge server, where the second response message includes resource data corresponding to the user access request.
  • the user access request is sent to the edge server based on the HTTPS or HTTP protocol, and the user access request contains identification information corresponding to the QUIC protocol; the first response message sent by the edge server is received, and the first response message is used to instruct the client Next time, the user access request is sent based on the QUIC protocol; the user access request is sent to the edge server based on the QUIC protocol; and the second response message sent by the edge server is received, and the second response message includes resource data corresponding to the user access request.
  • the edge server can return different response messages to the client according to whether it supports the QUIC protocol, thereby Realize the data transmission between the client and the edge server that both support the QUIC protocol based on the QUIC protocol, and it can also avoid the situation that the edge server cannot parse the user request sent by the client when the transmission protocol between the edge server and the client is not uniform. The problem that the two cannot perform resource data transmission.
  • the fourth receiving module 309 is configured to:
  • Fig. 5 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 optionally 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.
  • FIG. 6 does not constitute a limitation to the electronic device 400, and may include more or less components than shown in the figure, or combine certain components, or adopt different component arrangements.
  • 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 audio-video stream-based push
  • the method includes: receiving a user access request sent by a client based on HTTPS or HTTP protocol; detecting whether the user access request contains identification information corresponding to the QUIC protocol; if so, determining that the user supports the QUIC protocol In this case, send a first response message to the client based on the HTTPS or HTTP protocol, and the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time; the user access request; sending a second response message to the client based on the QUIC protocol, where the second response message includes resource data corresponding to the user access request.
  • 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 audio-video stream-based
  • the push method comprising: receiving a user access request sent by the client based on HTTPS or HTTP protocol; detecting whether identification information corresponding to the QUIC protocol is included in the user access request; if so, determining that the user supports the QUIC protocol In the case where the client sends a first response message based on HTTPS or HTTP protocol, the first response message is used to instruct the client to send a user access request based on the QUIC protocol next time; A user access request sent; sending a second response message to the client based on the QUIC protocol, where the second response message includes resource data corresponding to the user access request.
  • 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 user access request initiated by the client to the edge server based on the HTTPS or HTTP protocol carries an identification information used to inform the edge server that the client supports the QUIC protocol, so that the edge server can determine whether it supports the QUIC protocol.
  • the edge server can determine whether it supports the QUIC protocol.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本公开公开了一种用户访问请求处理方法、装置、设备、介质及产品。本公开中，接收客户端基于HTTPS或HTTP协议发送的用户访问请求；检测用户访问请求中是否包含有对应于QUIC协议的标识信息；若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向客户端发送第一响应消息，第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求；接收客户端基于QUIC协议发送的用户访问请求；基于QUIC协议向客户端发送第二响应消息，第二响应消息包括用户访问请求对应的资源数据。

Description

用户访问请求处理方法、装置、设备、介质及产品
本公开基于2021年12月31日提交中国专利局、申请号为202111678311.X，发明名称为“用户访问请求的处理方法、电子装置、电子设备以及介质”的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本公开作为参考。
技术领域
本公开实施例涉及但不限于一种用户访问请求处理方法、装置、设备、介质及产品。
背景技术
QUIC是一种基于UDP协议的低时延互联网传输协议，其在UDP的基础上，提供了可靠、有序、安全以及更快速的传输服务等，这些优点对于面向海量用户的CDN网络尤为重要，因此业务平台越来越频繁的使用QUIC协议进行业务处理。
QUIC协议能够被广泛使用，其中一个原因是其相对于HTTPS或HTTP传输协议来说，可以达到让业务处理效率更高的目的，但是在相关技术中，经常会出现在客户端与边缘服务器进行业务数据交互的过程中，由于二者的传输协议不统一，如果完全遵循客户端的协议来进行路由会导致业务处理失败的情况，这样也会影响业务处理的效率。
发明内容
以下是对本公开详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本公开提供一种用户访问请求的处理方法、电子装置、电子设备以及介质，本公开的技术方案可以相关技术中存在的由于边缘服务器与客户端的传输协议不统一所导致的无法传输资源数据的问题。
根据本公开的第一方面，提供一种用户访问请求的处理方法，应用于边缘服务器，包括：
接收客户端基于HTTPS或HTTP协议发送的用户访问请求；
检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息；
若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向所述客户端发送第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
接收所述客户端基于QUIC协议发送的用户访问请求；
基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
在本公开一些示例性的实施例中，在所述检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息之后，还包括：
若无，则基于HTTPS或HTTP协议向所述客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
在本公开一些示例性的实施例中，在所述检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息之后，还包括：
检测所述边缘服务器是否存储有所述资源数据；
若无，基于QUIC协议向上层服务器发送资源获取请求。
在本公开一些示例性的实施例中，在所述基于QUIC协议向上层服务器发送资源获取请求之后，还包括：
若接收到所述上层服务器返回的第三响应消息，所述第三响应消息包括所述资源获取请求对应的资源数据；
则基于QUIC协议将所述资源数据发送给所述客户端。
在本公开一些示例性的实施例中，在所述基于QUIC协议向上层服务器发送资源获取请求之后，还包括：
若获取到所述上层服务器返回的第四响应消息，所述第四响应消息用于指示所述边缘服务器下次基于HTTPS或HTTP协议向所述上层服务器发送所述资源获取请求；
则在所述边缘服务器基于HTTPS或HTTP协议从所述上层服务器获取所述资源数据后，基于QUIC协议将所述资源数据发送给所述客户端。
在本公开一些示例性的实施例中，在所述检测所述边缘服务器是否存储有所述资源数据之后，还包括：
若有，基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
根据本公开的第二方面，提供一种用户访问请求的处理方法，应用于客户端，包括：
基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，所述用户访问请求包含有对应于QUIC协议的标识信息；
接收所述边缘服务器发送的第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
基于QUIC协议向所述边缘服务器发送所述用户访问请求；
接收所述边缘服务器发送的第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
在本公开一些示例性的实施例中在所述接收所述边缘服务器发送的第二响应消息之后，还包括：
记录所述边缘服务器与QUIC协议的关联关系；
当再次向所述边缘服务器发送用户访问请求时，基于QUIC协议向所述边缘 服务器发送所述用户访问请求。
根据本公开的第三方面，提供一种用户访问请求的处理电子装置，应用于边缘服务器，包括：
第一接收模块，被配置为接收客户端基于HTTPS或HTTP协议发送的用户访问请求；
检测模块，被配置为检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息；
第一发送模块，被配置为若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向所述客户端发送第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
第二接收模块，被配置为接收所述客户端基于QUIC协议发送的用户访问请求；
第二发送模块，被配置为基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
根据本公开的第四方面，提供一种用户访问请求的处理电子装置，应用于客户端，包括：
第三发送模块，被配置为基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，所述用户访问请求包含有对应于QUIC协议的标识信息；
第三接收模块，被配置为接收所述边缘服务器发送的第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
第四发送模块，被配置为基于QUIC协议向所述边缘服务器发送所述用户访问请求；
第四接收模块，被配置为接收所述边缘服务器发送的第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
根据本公开的第五方面，提供一种电子设备，包括：
存储器，用于存储可执行指令；以及
显示器，用于与所述存储器显示以执行所述可执行指令从而完成上述任一所述用户访问请求的处理方法的操作。
根据本公开的第六方面，提供一种计算机可读存储介质，用于存储计算机可读取的指令，所述指令被执行时执行上述任一所述用户访问请求的处理方法的操作。
本公开中，边缘服务器接收客户端基于HTTPS或HTTP协议发送的用户访问请求；检测用户访问请求中是否包含有对应于QUIC协议的标识信息；若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向客户端发送第一响应消息，第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求；接收客户端基于QUIC协议发送的用户访问请求；基于QUIC协议向客户端发送第 二响应消息，第二响应消息包括用户访问请求对应的资源数据。通过应用本公开的技术方案，可以由客户端基于HTTPS或HTTP协议向边缘服务器发起的用户访问请求中携带一个用于告知边缘服务器该客户端支持QUIC协议的标识信息，以使边缘服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，并在后续通过对应的协议进行数据传输，从而避免了在边缘服务器不支持QUIC协议的情况下，二者无法进行资源数据传输的问题。
下面通过附图和实施例，对本公开的技术方案做进一步的详细描述。在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
构成说明书的一部分的附图描述了本公开的实施例，并且连同描述一起用于解释本公开的原理。
参照附图，根据下面的详细描述，可以更加清楚地理解本公开，其中：
图1为本公开提出的一种用户访问请求的处理方法示意图；
图2为本公开提出的另一种用户访问请求的处理方法示意图；
图3-图4为本公开提出的一种用户访问请求的处理电子装置示意图；
图5为本公开提出的一种用户访问请求的处理电子设备示意图。
具体实施方式
现在将参照附图来详细描述本公开的各种示例性实施例。应注意到：除非另外具体说明，否则在这些实施例中阐述的部件和步骤的相对布置、数字表达式和数值不限制本公开的范围。
同时，应当明白，为了便于描述，附图中所示出的各个部分的尺寸并不是按照实际的比例关系绘制的。
以下对至少一个示例性实施例的描述实际上仅仅是说明性的，不作为对本公开及其应用或使用的任何限制。
对于相关领域普通技术人员已知的技术、方法和设备可能不作详细讨论，但在适当情况下，所述技术、方法和设备应当被视为说明书的一部分。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步讨论。
另外，本公开各个实施例之间的技术方案可以相互结合，但是必须是以本领域普通技术人员能够实现为基础，当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在，也不在本公开要求的保护范围之内。
需要说明的是，本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施 例仅被视为示例性的，本公开的真正范围和精神由权利要求部分指出。
应当理解的是，本公开并不局限于下面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
下面结合图1-图3来描述根据本公开示例性实施方式的用于进行用户访问请求的处理方法。需要注意的是，下述应用场景仅是为了便于理解本公开的精神和原理而示出，本公开的实施方式在此方面不受任何限制。相反，本公开的实施方式可以应用于适用的任何场景。
一种实施方式中，本公开还提出一种用户访问请求的处理方法。图1示意性地示出了根据本公开实施方式的一种用户访问请求的处理方法的流程示意图。如图1所示，该方法应用于边缘服务器，包括：
S101，接收客户端基于HTTPS或HTTP协议发送的用户访问请求。
S102，检测用户访问请求中是否包含有对应于QUIC协议的标识信息。
其中，QUIC是一种基于UDP协议的低时延互联网传输协议，其出现主要是为了解决现有的TCP网络传输协议中存在的一些问题，包括TCP队头阻塞、握手延迟以及TCP协议僵化等。QUIC在UDP的基础上，提供了可靠、有序、安全以及更快速的传输服务等，这些优点对于面向海量用户的CDN网络尤为重要，因此个别CDN厂商开始提供了QUIC协议请求的处理能力。
其中，QUIC协议能够被广泛使用，其中一个原因为其相对于HTTPS或HTTP传输协议来说，可以实现业务处理效率更高的目的。但是在相关技术中，经常会出现在边缘服务器与支持QUIC协议的客户端进行资源数据传输的过程中，由于边缘服务器不支持QUIC协议从而导致边缘服务器无法向客户端发送其所请求的资源数据，进而影响用户业务处理效率的问题。
针对上述问题，本公开由客户端以边缘服务器普遍支持的HTTPS或HTTP协议向其发送用户访问请求。在一些示例性的实施例中，在边缘服务器接收到客户端发送的用户访问请求时，检测该用户访问请求中是否包含有对应于QUIC协议的标识信息，若有，则边缘服务器确定该客户端为支持QUIC协议的客户端。
一种方式中，本公开不对标识信息进行具体限定，只要其对应于QUIC协议即可，该标识信息可以为设定好的字符串，包括但不限于001、a、A，可以理解的，只要预先在边缘服务器侧约定该数字或字母等字段为对应于客户端支持QUIC协议的含义即可，本公开不对标识信息进行限定。
S103，若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向客户端发送第一响应消息，第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求。
一种方式中，若边缘服务器检测到自身支持QUIC协议时，由于QUIC协议可以使业务处理效率更高，为了实现优先基于QUIC协议进行数据传输的目的，本公开提出一种由边缘服务器在检测到自身支持QUIC协议的情况下，主动向客户端发起一个用于指示客户端基于高版本协议(即由HTTPS或HTTP协议切换为 QUIC协议)向边缘服务器发送用户访问请求的第一响应消息，以使客户端下次基于QUIC协议向边缘服务器发送用户访问请求，从而实现将支持QUIC协议的客户端与边缘服务器可以基于数据传输效率更快的QUIC协议进行资源数据的传输。
S104、接收客户端基于QUIC协议发送的用户访问请求。
S105、基于QUIC协议向客户端发送第二响应消息，第二响应消息包括用户访问请求对应的资源数据。
一种方式中，若边缘服务器接收到客户端基于QUIC协议发送的用户访问请求后，先检测自身的存储区域中是否存储有该用户访问请求对应的资源数据，若有，则读取该资源数据，并将该资源数据基于QUIC协议向客户端发送。
本公开中，接收客户端基于HTTPS或HTTP协议发送的用户访问请求；检测用户访问请求中是否包含有对应于QUIC协议的标识信息；若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向客户端发送第一响应消息，该第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求；接收客户端基于QUIC协议发送的用户访问请求；基于QUIC协议向客户端发送第二响应消息，第二响应消息包括用户访问请求对应的资源数据。通过应用本公开的技术方案，可以由客户端基于HTTPS或HTTP协议向边缘服务器发起的用户访问请求中携带一个用于告知边缘服务器该客户端支持QUIC协议的标识信息，以使边缘服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，并在后续通过对应的协议进行数据传输，从而避免了在边缘服务器不支持QUIC协议的情况下，二者无法进行资源数据传输的问题。
在基于本公开上述方法的另一个实施例中，在S102(检测用户访问请求中是否包含有对应于QUIC协议的标识信息)之后，可以实施下述步骤：
若无，则基于HTTPS或HTTP协议向客户端发送第二响应消息，第二响应消息包括用户访问请求对应的资源数据。
在一些示例性的实施例中，在边缘服务器接收到客户端发送的用户访问请求并检测到该用户访问请求中未包含有对应于QUIC协议的标识信息时，则边缘服务器可以确定该客户端为不支持QUIC协议的客户端，因此边缘服务器则基于HTTPS或HTTP协议向客户端发送该用户访问请求对应的资源数据，进而确保客户端可以及时的接收到资源数据以避免出现影响业务处理进度的问题。
在基于本公开上述方法的另一个实施例中，在S102(检测用户访问请求中是否包含有对应于QUIC协议的标识信息)之后，可以实施下述步骤：
检测边缘服务器是否存储有资源数据；
若无，基于QUIC协议向上层服务器发送资源获取请求。
一种方式中，若边缘服务器未存储有该用户访问请求对应的资源数据，则向上层服务器发送资源获取请求，本公开不对上层服务器进行具体限定，例如可以为其他边缘服务器、父服务器、中心服务器和源站服务器的其中任意一种。 边缘服务器通过向源站或其他边缘服务器、父服务器、中心服务器的其中任意一种存储有该资源数据的服务器中发送资源获取请求，并获取到对应的资源数据后，基于QUIC协议向客户端发送该资源数据。
在基于本公开上述方法的另一个实施例中，基于QUIC协议向上层服务器发送资源获取请求之后，可以实施下述步骤：
若接收到上层服务器返回的第三响应消息，第三响应消息包括资源获取请求对应的资源数据；
则基于QUIC协议将资源数据发送给客户端。
一种方式中，若上层服务器支持QUIC协议，则上层服务器将基于QUIC协议向边缘服务器发送其所请求的资源数据，当边缘服务器接收到上层服务器返回的资源数据之后，则基于QUIC协议向客户端发送客户端所请求的资源数据，进而确保客户端可以及时的接收到资源数据以避免出现影响业务处理进度的问题。
在基于本公开上述方法的另一个实施例中，基于QUIC协议向上层服务器发送资源获取请求之后，可以实施下述步骤：
若获取到上层服务器返回的第四响应消息，第四响应消息用于指示边缘服务器下次基于HTTPS或HTTP协议向上层服务器发送资源获取请求；
则在边缘服务器基于HTTPS或HTTP协议从上层服务器获取资源数据后，基于QUIC协议将资源数据发送给客户端。
一种方式中，若上层服务器在接收到边缘服务器基于QUIC协议发送的资源获取请求之后，可以由上层服务器首先检测其自身是否支持QUIC协议，当上层服务器在检测到自身不支持QUIC协议的情况下，可以不再尝试对该请求进行解析，而是主动向基于QUIC协议发送资源获取请求的边缘服务器发送一个用于指示其基于低版本协议发送资源获取请求的响应消息。可以理解的，边缘服务器在接收到该响应消息后，则基于协议降级的方式(由QUIC协议切换为HTTPS或HTTP协议)重新向上层服务器发送资源获取请求，以使不支持QUIC协议的上层服务器可以通过HTTPS或HTTP协议向边缘发送资源数据。
一种方式中，上层服务器所发送的第四响应消息对应于包含错误标识的响应消息或者指示协议降级的响应消息，其中，响应错误标识可以为ECONNREFUSED错误码或5XX状态码，即当上层服务器在检测到自身不支持QUIC协议之后，生成一个ECONNREFUSED错误码或5XX状态码并将其发送给边缘服务器，而边缘服务器在解析响应消息并得到ECONNREFUSED错误码或5XX状态码之后，即可根据该错误码或5XX状态码直接确定该上层服务器不支持QUIC协议，进而在后续基于HTTPS或HTTP协议再次发送资源获取请求。
另一种方式中，若边缘服务器接收到的第四响应消息对应于超时响应消息或者第四响应消息为空时，可以再次基于QUIC协议向上层服务器发送资源获取请求，从而进一步确认上层服务器是否支持QUIC协议。其中，当获取到上层服务器发送的第四响应消息仍对应于超时响应消息(如状态码为504的响应消息) 或者上层服务器不发送响应消息，即第四响应消息为空时，则确定该上层服务器不支持QUIC协议，进而在后续基于HTTPS或HTTP协议再次发送资源获取请求。
通过上述方式，可以在客户端基于QUIC协议向上层服务器请求资源数据的过程中，由上层服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，从而避免了由于上层服务器不支持QUIC协议从而导致上层服务器无法向边缘服务器发送其所请求的资源数据，进而影响用户业务处理效率的问题。
在基于本公开上述方法的另一个实施例中，在检测边缘服务器是否存储有资源数据之后，可以实施下述步骤：
若有，基于QUIC协议向客户端发送第二响应消息，第二响应消息包括用户访问请求对应的资源数据。
一种方式中，若边缘服务器接收到客户端基于QUIC协议发送的用户访问请求后，先检测自身的存储区域中是否存储有该用户访问请求对应的资源数据，若有，则读取该资源数据，并将该资源数据基于QUIC协议向客户端发送。
通过应用本公开的技术方案，可以由客户端基于HTTPS或HTTP协议向边缘服务器发起的用户访问请求中携带一个用于告知边缘服务器该客户端支持QUIC协议的标识信息，以使边缘服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，并在后续采用对应的协议进行数据传输，从而避免了在边缘服务器不支持QUIC协议的情况下，二者无法进行资源数据传输的问题。
另外一种实施方式中，本公开还提出一种用户访问请求的处理方法。图2示意性地示出了根据本公开实施方式的一种用户访问请求的处理方法的流程示意图。如图2所示，该方法应用于客户端，包括：
S201，基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，用户访问请求包含有对应于QUIC协议的标识信息。
其中，QUIC是一种基于UDP协议的低时延互联网传输协议，其出现主要是为了解决现有的TCP网络传输协议中存在的一些问题，包括TCP队头阻塞、握手延迟以及TCP协议僵化等。QUIC在UDP的基础上，提供了可靠、有序、安全以及更快速的传输服务等，这些优点对于面向海量用户的CDN网络尤为重要，因此个别CDN厂商开始提供了QUIC协议请求的处理能力。
其中，QUIC协议能够被广泛使用，其中一个原因为其相对于HTTPS或HTTP传输协议来说，可以实现业务处理效率更高的目的。但是在相关技术中，经常会出现在边缘服务器与支持QUIC协议的客户端进行资源数据传输的过程中，由于边缘服务器不支持QUIC协议从而导致边缘服务器无法向客户端发送该客户端向其请求的资源数据，进而影响用户业务处理效率的问题。
为了解决上述问题，由于客户端并不知道本次与其通信的边缘服务器是否支持QUIC协议，且在边缘服务器不支持QUIC协议的情况下，直接基于QUIC协 议向其发送请求可能会导致边缘无法响应的问题。因此，本公开可以首先由客户端以边缘服务器一定支持的HTTPS或HTTP协议向其发送用户访问请求，并且为了实现优先基于QUIC协议进行资源数据传输的目的，客户端需要在该请求中添加一个用于告知边缘服务器该客户端支持QUIC协议的标识信息，以使边缘服务器在检测到该带有标识信息的用户访问请求且检测到自身同样支持QUIC协议的情况下，主动向客户端发起一个用于指示客户端基于协议升级的方式(即由HTTPS或HTTP协议切换为QUIC协议)向边缘服务器发送用户访问请求的第一响应消息，进而达到客户端下次基于QUIC协议发送用户访问请求的目的，从而实现将均支持QUIC协议的客户端与边缘服务器可以基于数据传输效率更快的QUIC协议进行资源数据的传输。
S202，接收边缘服务器发送的第一响应消息，第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求。
一种方式中，基于HTTPS或HTTP协议发送用户访问请求的客户端在接收到边缘服务器发送的用于指示其基于协议升级的方式(由HTTPS或HTTP协议切换为QUIC协议)重新向边缘服务器发送资源获取请求的第一响应消息时，则基于QUIC协议重新向边缘服务器发送用户访问请求，以使均支持QUIC协议的客户端与边缘服务器可以通传输效率更快的QUIC协议来进行资源数据的传输。
S203，基于QUIC协议向边缘服务器发送用户访问请求。
一种方式中，当边缘服务器接收到客户端基于QUIC协议发送的用户访问请求时，边缘服务器也基于QUIC协议向边缘服务器发送用户访问请求，以使均支持QUIC协议的客户端与边缘服务器可以通传输效率更快的QUIC协议来进行资源数据的传输。
S204，接收边缘服务器发送的第二响应消息，第二响应消息包括用户访问请求对应的资源数据。
一种方式中，边缘服务器在接收到客户端基于QUIC协议发送的用户访问请求后，其可以从自身的存储区域，或存储有该资源数据的服务器(例如可以为上层服务器或其他边缘服务器、父服务器、中心服务器的其中任意一种)中调取对应的资源数据，并在获取到资源数据后，基于QUIC协议向客户端发送包含有该资源数据的第二响应消息。
本公开中，在基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，用户访问请求包含有对应于QUIC协议的标识信息；接收边缘服务器发送的第一响应消息，第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求；基于QUIC协议向边缘服务器发送用户访问请求；接收边缘服务器发送的第二响应消息，第二响应消息包括用户访问请求对应的资源数据。通过应用本公开的技术方案，可以在客户端基于HTTPS或HTTP协议向边缘服务器请求资源数据的过程中，由边缘服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，从而实现将均支持QUIC协议的客户端与边缘服务器基于QUIC协议进行数据的传输，还能够避免在边缘服务器与客户端的传输协议不统一的 情况下，由于边缘服务器无法解析客户端发送的用户请求而导致的二者无法进行资源数据传输的问题。
在基于本公开上述方法的另一个实施例中，在S204(接收边缘服务器发送的第二响应消息)之后，可以实施下述步骤：
记录边缘服务器与QUIC协议的关联关系；
当再次向边缘服务器发送用户访问请求时，基于QUIC协议向边缘服务器发送用户访问请求。
一种方式中，为了避免后续客户端向该边缘服务器请求资源数据时同样还需要发送两次资源获取请求才可以获取资源数据所导致的耗费业务处理时间的问题。本公开可以在客户端确定边缘服务器所支持协议的情况下，将边缘服务器与QUIC协议的关联关系记录在本地的存储区域中(例如可以存储在历史访问数据中)，当再次需要向边缘服务器发送资源获取请求时，客户端可以直接基于QUIC协议向边缘服务器发送资源获取请求。
举例来说，在客户端后续向该边缘服务器发送资源获取请求时，可以首先获取预存在本地存储区域的历史访问数据，并遍历该历史访问数据中是否存在有该边缘服务器的历史访问记录，若存在，则读取历史访问记录中存储的与该边缘服务器所关联的传输协议的关系，即客户端可以通过该历史访问记录，确定边缘服务器是否支持QUIC协议，若确定其支持，则可以直接基于QUIC协议向边缘服务器发送资源获取请求，可以理解的，若不支持QUIC协议，那么也可以直接基于HTTPS或HTTP协议向边缘服务器发送资源获取请求。
本公开的上述实施方式可以避免后续客户端再次向该边缘服务器请求资源数据时，无需再次先后基于HTTPS或HTTP协议和QUIC协议向边缘服务器发送资源获取请求才可以获取到对应的资源数据，进而节省了业务数据的传输时间，也减少了服务器的数据收发资源。
在本公开的另外一种实施方式中，如图3所示，本公开还提供一种用户访问请求的处理电子装置。其中，应用于边缘服务器，包括，
第一接收模块301，被配置为接收客户端基于HTTPS或HTTP协议发送的用户访问请求；
检测模块302，被配置为检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息；
第一发送模块303，被配置为若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向所述客户端发送第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
第二接收模块304，被配置为接收所述客户端基于QUIC协议发送的用户访问请求；
第二发送模块305，被配置为基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
本公开中，接收客户端基于HTTPS或HTTP协议发送的用户访问请求；检测用户访问请求中是否包含有对应于QUIC协议的标识信息；若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向客户端发送第一响应消息，该第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求；接收客户端基于QUIC协议发送的用户访问请求；基于QUIC协议向客户端发送第二响应消息，第二响应消息包括用户访问请求对应的资源数据。通过应用本公开的技术方案，可以由客户端基于HTTPS或HTTP协议向边缘服务器发起的用户访问请求中携带一个用于告知边缘服务器该客户端支持QUIC协议的标识信息，以使边缘服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，并在后续通过对应的协议进行数据传输，从而避免了在边缘服务器不支持QUIC协议的情况下，二者无法进行资源数据传输的问题。
在本公开的另外一种实施方式中，检测模块302，被配置为：
若无，则基于HTTPS或HTTP协议向所述客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
在本公开的另外一种实施方式中，检测模块302，被配置为：
检测所述边缘服务器是否存储有所述资源数据；
若无，基于QUIC协议向上层服务器发送资源获取请求。
在本公开的另外一种实施方式中，第一发送模块303，被配置为：
若接收到所述上层服务器返回的第三响应消息，所述第三响应消息包括所述资源获取请求对应的资源数据；
则基于QUIC协议将所述资源数据发送给所述客户端。
在本公开的另外一种实施方式中，第二发送模块305，被配置为：
若获取到所述上层服务器返回的第四响应消息，所述第四响应消息用于指示所述边缘服务器下次基于HTTPS或HTTP协议向所述上层服务器发送所述资源获取请求；
则在所述边缘服务器基于HTTPS或HTTP协议从所述上层服务器获取所述资源数据后，基于QUIC协议将所述资源数据发送给所述客户端。
在本公开的另外一种实施方式中，第二发送模块305，被配置为：
若有，基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
在本公开的另外一种实施方式中，如图4所示，本公开还提供一种用户访问请求的处理电子装置。其中，应用于客户端，包括：
第三发送模块306，被配置为基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，所述用户访问请求包含有对应于QUIC协议的标识信息；
第三接收模块307，被配置为接收所述边缘服务器发送的第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
第四发送模块308，被配置为基于QUIC协议向所述边缘服务器发送所述用 户访问请求；
第四接收模块309，被配置为接收所述边缘服务器发送的第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
本公开中，在基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，用户访问请求包含有对应于QUIC协议的标识信息；接收边缘服务器发送的第一响应消息，第一响应消息用于指示客户端下次基于QUIC协议发送用户访问请求；基于QUIC协议向边缘服务器发送用户访问请求；接收边缘服务器发送的第二响应消息，第二响应消息包括用户访问请求对应的资源数据。通过应用本公开的技术方案，可以在客户端基于HTTPS或HTTP协议向边缘服务器请求资源数据的过程中，由边缘服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，从而实现将均支持QUIC协议的客户端与边缘服务器基于QUIC协议进行数据的传输，还能够避免在边缘服务器与客户端的传输协议不统一的情况下，由于边缘服务器无法解析客户端发送的用户请求而导致的二者无法进行资源数据传输的问题。
在本公开的另外一种实施方式中，第四接收模块309，被配置为：
记录所述边缘服务器与QUIC协议的关联关系；
当再次向所述边缘服务器发送用户访问请求时，基于QUIC协议向所述边缘服务器发送所述用户访问请求。
图5是根据一示例性实施例示出的一种电子设备的逻辑结构框图。例如，电子设备400可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图5，电子设备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包括可充电电池时，该可充电电池可以支持有线充电或无线充电。该可充电电池还可以用于支持快充技术。
本领域技术人员可以理解，图6中示出的结构并不构成对电子设备400的限定，可以包括比图示更多或更少的组件，或者组合某些组件，或者采用不同的组件布置。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器404，上述指令可由电子设备400的处理器420执行以完成上述基于音视频流推送的方法，该方法包括：接收客户端基于HTTPS或HTTP协议发送的用户访问请求；检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息；若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向所述客户端发送第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；接收所述客户端基于QUIC协议发送的用户访问请求；基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。上述指令还可以由电子设备400的处理器420执行以完成上述示例性实施例中所涉及的其他步骤。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
在示例性实施例中，还提供了一种应用程序/计算机程序产品，包括一条或 多条指令，该一条或多条指令可以由电子设备400的处理器420执行，以完成上述基于音视频流推送的方法，该方法包括：接收客户端基于HTTPS或HTTP协议发送的用户访问请求；检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息；若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向所述客户端发送第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；接收所述客户端基于QUIC协议发送的用户访问请求；基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。上述指令还可以由电子设备400的处理器420执行以完成上述示例性实施例中所涉及的其他步骤。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
工业实用性
在本公开中，通过由客户端基于HTTPS或HTTP协议向边缘服务器发起的用户访问请求中携带一个用于告知边缘服务器该客户端支持QUIC协议的标识信息，以使边缘服务器根据自身是否支持QUIC协议来针对性的向客户端返回不同的响应消息，并在后续通过对应的协议进行数据传输，从而避免了在边缘服务器不支持QUIC协议的情况下，二者无法进行资源数据传输的问题。

Claims (13)

  1. 一种用户访问请求的处理方法，应用于边缘服务器，包括：
    接收客户端基于HTTPS或HTTP协议发送的用户访问请求；
    检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息；
    若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向所述客户端发送第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
    接收所述客户端基于QUIC协议发送的用户访问请求；
    基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
  2. 如权利要求1所述的方法，其中，在所述检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息之后，还包括：
    若无，则基于HTTPS或HTTP协议向所述客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
  3. 如权利要求1所述的方法，其中，在所述检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息之后，还包括：
    检测所述边缘服务器是否存储有所述资源数据；
    若无，基于QUIC协议向上层服务器发送资源获取请求。
  4. 如权利要求3所述的方法，其中，在所述基于QUIC协议向上层服务器发送资源获取请求之后，还包括：
    若接收到所述上层服务器返回的第三响应消息，所述第三响应消息包括所述资源获取请求对应的资源数据；
    则基于QUIC协议将所述资源数据发送给所述客户端。
  5. 如权利要求3所述的方法，其中，在所述基于QUIC协议向上层服务器发送资源获取请求之后，还包括：
    若获取到所述上层服务器返回的第四响应消息，所述第四响应消息用于指示所述边缘服务器下次基于HTTPS或HTTP协议向所述上层服务器发送所述资源获取请求；
    则在所述边缘服务器基于HTTPS或HTTP协议从所述上层服务器获取所述资源数据后，基于QUIC协议将所述资源数据发送给所述客户端。
  6. 如权利要求3所述的方法，其中，在所述检测所述边缘服务器是否存储有所述资源数据之后，还包括：
    若有，基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
  7. 一种用户访问请求的处理方法，应用于客户端，包括：
    基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，所述用户访问请求包含有对应于QUIC协议的标识信息；
    接收所述边缘服务器发送的第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
    基于QUIC协议向所述边缘服务器发送所述用户访问请求；
    接收所述边缘服务器发送的第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
  8. 如权利要求7所述的方法，其中，在所述接收所述边缘服务器发送的第二响应消息之后，还包括：
    记录所述边缘服务器与QUIC协议的关联关系；
    当再次向所述边缘服务器发送用户访问请求时，基于QUIC协议向所述边缘服务器发送所述用户访问请求。
  9. 一种用户访问请求的处理电子装置，应用于边缘服务器，包括：
    第一接收模块，被配置为接收客户端基于HTTPS或HTTP协议发送的用户访问请求；
    检测模块，被配置为检测所述用户访问请求中是否包含有对应于QUIC协议的标识信息；
    第一发送模块，被配置为若有，则在确定自身支持QUIC协议的情况下基于HTTPS或HTTP协议向所述客户端发送第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
    第二接收模块，被配置为接收所述客户端基于QUIC协议发送的用户访问请求；
    第二发送模块，被配置为基于QUIC协议向客户端发送第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
  10. 一种用户访问请求的处理电子装置，应用于客户端，包括：
    第三发送模块，被配置为基于HTTPS或HTTP协议向边缘服务器发送用户访问请求，所述用户访问请求包含有对应于QUIC协议的标识信息；
    第三接收模块，被配置为接收所述边缘服务器发送的第一响应消息，所述第一响应消息用于指示所述客户端下次基于QUIC协议发送用户访问请求；
    第四发送模块，被配置为基于QUIC协议向所述边缘服务器发送所述用户访问请求；
    第四接收模块，被配置为接收所述边缘服务器发送的第二响应消息，所述第二响应消息包括所述用户访问请求对应的资源数据。
  11. 一种电子设备，包括：
    存储器，用于存储可执行指令；以及，
    处理器，用于与所述存储器执行所述可执行指令从而完成权利要求1-6或7-8中任一所述用户访问请求的处理方法的操作。
  12. 一种计算机可读存储介质，用于存储计算机可读取的指令，其中，所述指令被执行时执行权利要求1-6或7-8中任一所述用户访问请求的处理方法的操作。
  13. 一种计算机程序产品，包括计算机程序，其中，所述计算机程序被处理器执行实现如权利要求1-6或7-8中任一项所述的方法。
PCT/CN2022/143988 2021-12-31 2022-12-30 用户访问请求处理方法、装置、设备、介质及产品 WO2023125946A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111678311.XA CN116418795A (zh) 2021-12-31 2021-12-31 用户访问请求的处理方法、电子装置、电子设备以及介质
CN202111678311.X 2021-12-31

Publications (1)

Publication Number Publication Date
WO2023125946A1 true WO2023125946A1 (zh) 2023-07-06

Family

ID=86998142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/143988 WO2023125946A1 (zh) 2021-12-31 2022-12-30 用户访问请求处理方法、装置、设备、介质及产品

Country Status (2)

Country Link
CN (1) CN116418795A (zh)
WO (1) WO2023125946A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116962509A (zh) * 2023-09-20 2023-10-27 联通在线信息科技有限公司 基于quic协议的网络代理方法以及网络代理系统
CN117033088A (zh) * 2023-08-17 2023-11-10 广东保伦电子股份有限公司 适用于双机热备的资源调度方法、装置以及服务器系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110149388A (zh) * 2019-05-16 2019-08-20 北京字节跳动网络技术有限公司 Httpdns服务器的连接方法、装置及设备
CN112187801A (zh) * 2020-09-29 2021-01-05 杭州迪普科技股份有限公司 网站访问方法、装置及系统
CN113347269A (zh) * 2021-06-24 2021-09-03 江苏创源电子有限公司 一种工业系统的数据更新方法、电子设备和存储介质
CN113382062A (zh) * 2021-06-08 2021-09-10 北京天空卫士网络安全技术有限公司 一种数据传输方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110149388A (zh) * 2019-05-16 2019-08-20 北京字节跳动网络技术有限公司 Httpdns服务器的连接方法、装置及设备
CN112187801A (zh) * 2020-09-29 2021-01-05 杭州迪普科技股份有限公司 网站访问方法、装置及系统
CN113382062A (zh) * 2021-06-08 2021-09-10 北京天空卫士网络安全技术有限公司 一种数据传输方法、装置和系统
CN113347269A (zh) * 2021-06-24 2021-09-03 江苏创源电子有限公司 一种工业系统的数据更新方法、电子设备和存储介质

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117033088A (zh) * 2023-08-17 2023-11-10 广东保伦电子股份有限公司 适用于双机热备的资源调度方法、装置以及服务器系统
CN117033088B (zh) * 2023-08-17 2024-05-03 广东保伦电子股份有限公司 适用于双机热备的资源调度方法、装置以及服务器系统
CN116962509A (zh) * 2023-09-20 2023-10-27 联通在线信息科技有限公司 基于quic协议的网络代理方法以及网络代理系统
CN116962509B (zh) * 2023-09-20 2024-02-27 联通在线信息科技有限公司 基于quic协议的网络代理方法以及网络代理系统

Also Published As

Publication number Publication date
CN116418795A (zh) 2023-07-11

Similar Documents

Publication Publication Date Title
CN111225042B (zh) 数据传输的方法、装置、计算机设备以及存储介质
WO2023125946A1 (zh) 用户访问请求处理方法、装置、设备、介质及产品
US20200183525A1 (en) Display method and apparatus
CN111614549B (zh) 交互处理方法、装置、计算机设备及存储介质
WO2020001564A1 (zh) 一种处理任务的方法、装置及系统
CN109246123B (zh) 媒体流获取方法及装置
WO2021018297A1 (zh) 一种基于p2p的服务通信方法、装置及系统
CN111092809B (zh) 实时推送信息的方法、装置、计算机设备及存储介质
CN111596885B (zh) 音频数据处理方法、服务器及存储介质
AU2019208662B2 (en) Service processing method and mobile communication terminal
CN111106902B (zh) 数据报文传输方法、装置、设备及计算机可读存储介质
CN111159604A (zh) 图片资源加载方法及装置
WO2021077898A1 (zh) 网络注册方法及电子设备
CN111131392A (zh) 处理消息的方法、装置、电子设备及介质
US12061662B2 (en) Methods, apparatuses and systems for displaying alarm file
WO2020041988A1 (zh) 一种服务器节点的选择方法和终端设备
CN110597840A (zh) 基于区块链的伴侣关系建立方法、装置、设备及存储介质
WO2022247750A1 (zh) 访问请求的处理方法、电子装置、电子设备以及介质
CN107800720B (zh) 劫持上报方法、装置、存储介质及设备
CN111130985A (zh) 关联关系建立方法、装置、终端、服务器及存储介质
CN114785766A (zh) 智能设备的控制方法、终端及服务器
WO2022032458A1 (zh) 多模态数据发送方法和装置、多模态数据处理方法和装置
CN110708582B (zh) 同步播放的方法、装置、电子设备及介质
CN111193600B (zh) 一种接管服务的方法、装置及系统
WO2020001450A1 (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: 22915194

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE