Processing method for user request, electronic device, electronic equipment, and medium

Abstract

The application discloses a user request processing method, an electronic device, an electronic equipment and a medium. In the application, an edge server receives a user request sent by a client in two different protocols, a QUIC protocol and an HTTP(S) protocol; detects whether the edge server supports the QUIC protocol, if yes, sends a response message to the client based on the QUIC protocol, and does not respond to the user request based on the HTTP(S) protocol.

Description

TECHNICAL FIELD

[0001] The present application relates to data processing technology, and in particular to a user request processing method, an electronic device, an electronic equipment and a medium. BACKGROUND

[0002] QUIC is a low-latency Internet transport protocol based on UDP protocol, which provides reliable, ordered, secure and faster transmission services on the basis of UDP. These advantages are particularly important for CDN networks facing a large number of users, so business platforms are increasingly using the QUIC protocol for business processing.

[0003] Among them, QUIC protocol can be widely used, one of the reasons is that it can achieve the purpose of higher business processing efficiency compared with HTTPS / HTTP transmission protocol. However, in the related art, there are often cases of business processing failure due to the non-uniformity of the transmission protocols supported by the client and the edge server during the process of business data interaction between the client and the edge server, or the need to reconnect based on other protocols, which also affects the efficiency of business processing. SUMMARY

[0004] The embodiments of the present application provide a user request processing method, an electronic device, an electronic equipment and a medium, and the technical solution of the present application can solve the problem of non-uniform transmission protocol supported by the edge server and the client in the related art.

[0005] Among them, according to an aspect of an embodiment of the present application, a user request processing method is provided, applied to an edge server, comprising:

[0006] Receiving a user request sent by a client in two different protocols of QUIC protocol and HTTP(S) protocol;

[0007] Detecting whether the QUIC protocol is supported by itself, if yes, sending a response message to the client based on the QUIC protocol, and not responding to the user request based on the HTTP(S) protocol.

[0008] Optionally, in another embodiment based on the above method of the present application, after detecting whether the QUIC protocol is supported by itself, further comprising:

[0009] If not, send the response message to the client based on the HTTP(S) protocol, and do not respond to the user request based on the QUIC protocol.

[0010] Optionally, in another embodiment based on the above method of the present application, before sending the response message to the client based on the QUIC protocol, further comprising:

[0011] If it is determined that the user request is a user request for obtaining resource data, it is detected whether the resource data is stored locally.

[0012] If not, a resource obtaining request is sent to an upper server based on a QUIC protocol and an HTTP(S) protocol respectively within a preset time interval, and resource data returned by the upper server is received.

[0013] Optionally, in another embodiment based on the method described above, before the response message is sent to the client based on the QUIC protocol, the method further comprises:

[0014] If it is determined that the user request is a user request for obtaining resource data, it is detected whether the resource data is stored locally.

[0015] If not, a resource obtaining request is sent to an upper server based on a QUIC protocol and an HTTP(S) protocol respectively within a preset time interval, and resource data returned by the upper server is received.

[0016] Optionally, in another embodiment based on the method described above, after the user request sent by the client in two different protocols of the QUIC protocol and the HTTP(S) protocol is received, the method further comprises:

[0017] It is detected that a time interval between the two times when the user request is received.

[0018] If the time interval is less than a first preset time threshold, it is detected whether the QUIC protocol is supported.

[0019] According to an aspect of an embodiment of the present application, a user request processing method is provided, which is applied to an upper server and comprises:

[0020] A resource obtaining request sent by an edge server in two different protocols of a QUIC protocol and an HTTP(S) protocol is received.

[0021] It is detected whether the QUIC protocol is supported, if yes, resource data corresponding to the resource obtaining request is sent to the edge server based on the QUIC protocol, and a resource obtaining request based on the HTTP(S) protocol is not responded.

[0022] If not, the resource data is sent to the edge server based on the HTTP(S) protocol, and a resource obtaining request based on the QUIC protocol is not responded.

[0023] Optionally, in another embodiment based on the method described above, after the resource obtaining request sent by the edge server in two different protocols of the QUIC protocol and the HTTP(S) protocol is received, the method further comprises:

[0024] detecting a time interval between receiving the two resource acquisition requests;

[0025] if the time interval is less than a second preset time threshold, detecting whether the electronic device supports the QUIC protocol.

[0026] According to another aspect of the embodiments of the present application, a user request processing electronic device is provided, which is applied to an edge server and includes:

[0027] a first receiving module configured to receive a user request sent by a client in two different protocols, i.e., a QUIC protocol and an HTTP(S) protocol;

[0028] a first sending module configured to detect whether the electronic device supports the QUIC protocol, and if yes, send a response message to the client based on the QUIC protocol, and not respond to a user request based on the HTTP(S) protocol.

[0029] According to another aspect of the embodiments of the present application, a user request processing electronic device is provided, which is applied to an upper layer server and includes:

[0030] a second receiving module configured to receive a resource acquisition request sent by an edge server in two different protocols, i.e., a QUIC protocol and an HTTP(S) protocol;

[0031] a second sending module configured to detect whether the electronic device supports the QUIC protocol, and if yes, send resource data corresponding to the resource acquisition request to the edge server based on the QUIC protocol, and not respond to a resource acquisition request based on the HTTP(S) protocol;

[0032] a third sending module configured to, if no, send the resource data to the edge server based on the HTTP(S) protocol, and not respond to a resource acquisition request based on the QUIC protocol.

[0033] According to another aspect of the embodiments of the present application, an electronic device is provided, which includes:

[0034] a memory configured to store executable instructions; and

[0035] a display configured to display the executable instructions stored in the memory to perform the operations of any of the above user request processing methods.

[0036] According to another aspect of the embodiments of the present application, a computer readable storage medium is provided, which is configured to store computer readable instructions, and the instructions are executed to perform the operations of any of the above user request processing methods.

[0037] In the present application, the edge server receives user requests sent by the client in two different protocols of QUIC protocol and HTTP(S) protocol; detects whether the edge server supports the QUIC protocol, if yes, sends a response message to the client based on the QUIC protocol, and does not respond to the user request based on the HTTP(S) protocol. By applying the technical solution of the present application, the client can initiate a user request to the edge server based on the QUIC protocol and the HTTP(S) protocol respectively, so that the edge server can respond to the user request of one of the protocols according to whether the edge server supports the QUIC protocol, and continue to transmit data through the corresponding protocol in the future, thereby solving the problem that the edge server and the client cannot transmit resource data when the edge server does not support the QUIC protocol.

[0038] The technical solutions of the present application will be described in detail below with reference to the accompanying drawings and embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0039] The accompanying drawings, which form a part of the specification, illustrate embodiments of the present application and, together with the description, serve to explain the principles of the present application.

[0040] The present application can be more clearly understood with reference to the following detailed description in conjunction with the accompanying drawings, in which:

[0041] Figure 1 A user request processing method according to the present application is shown in the schematic diagram;

[0042] Figure 2 Another user request processing method according to the present application is shown in the schematic diagram;

[0043] Figure 3 A flowchart of a user request processing method according to the present application is shown in the schematic diagram;

[0044] Figures 4-5 An electronic device for user request processing according to the present application is shown in the schematic diagram;

[0045] Figure 6 An electronic device for user request processing according to the present application is shown in the schematic diagram. DETAILED DESCRIPTION

[0046] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. Note that the relative arrangement, numerical expressions, and numerical values of the components and steps set forth in these embodiments are not limiting to the scope of the present application unless otherwise specifically stated.

[0047] It should be understood, however, that the sizes of the components illustrated in the drawings are not intended to be limiting, and are being depicted schematically only.

[0048] The following description of at least one exemplary embodiment is merely exemplary in nature and is not intended to limit the application or the application and uses of it in any way.

[0049] Techniques, methods, and apparatus known to those of ordinary skill in the relevant art can not be discussed in any detail since they can be readily understood from the disclosure and descriptions

[0050] It should be noted that like reference numerals and letters refer to like items throughout the attached drawings, and thus, once certain items are defined in one drawing, they should not require further discussion in a subsequent drawing.

[0051] In addition, the technical solutions among the various embodiments of the present application can be combined with each other, but it must be based on the fact that the technical solutions can be realized by those of ordinary skill in the art, and when the combination of technical solutions contradicts each other or cannot be realized, it should be considered that the combination of technical solutions does not exist and is not within the protection scope of the present application.

[0052] It should be noted that other embodiments of the present application will readily occur to those skilled in the art upon consideration of the specification and practice of the application disclosed herein. The present application is intended to include all such variations as fall within the general scope of the application, and the general principles and features defined herein. The specification and examples are, accordingly, to be regarded in an illustrative rather than a restrictive sense, and all such variations as constitute equivalents of the specific application are intended to be within the scope of the present application.

[0053] It should be understood that the present application is not limited to the precise construction and methods described herein and as shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the present application. The scope of the present application is limited only by the claims appended hereto.

[0054] The processing method for a user request according to the exemplary embodiments of the present application will be described below in conjunction with Figures 1-3 The application scenarios described below are merely shown for the purpose of facilitating the understanding of the spirit and principles of the present application, and the embodiments of the present application are not limited in this respect. On the contrary, the embodiments of the present application can be applied to any applicable scenario.

[0055] In one embodiment, the present application further provides a processing method for a user request. Figure 1 A flowchart schematically showing a processing method for a user request according to an embodiment of the present application is shown in FIG. 1. As shown in FIG. 1, the method is applied to an edge server and includes the following steps. Figure 1

[0056] ​S101, receiving a user request sent by a client in two different protocols, a QUIC protocol and an HTTP(S) protocol.

[0057] In one way, the HTTP(S) protocol can be the HTTPS or HTTP protocol commonly supported by the edge server.

[0058] In addition, QUIC is a low-latency Internet transport protocol based on the UDP protocol, which mainly appears to solve some problems existing in the existing TCP network transmission protocol, including TCP head blocking, handshake delay and TCP protocol ossification. QUIC provides reliable, ordered, secure and faster transmission services on the basis of UDP, which is particularly important for distributed cloud networks facing massive users, so individual manufacturers have begun to provide QUIC protocol support.

[0059] Among them, the QUIC protocol can be widely used, one of the reasons is that it can achieve the purpose of higher business processing efficiency compared with the HTTPS or HTTP transmission protocol. However, in the related technology, there are often problems that the edge server cannot send the resource data requested by the client to the client due to the fact that the edge server does not support the QUIC protocol, or needs to be reconnected based on other protocols, thereby affecting the user business processing efficiency, in the process of resource data transmission between the edge server and the client supporting the QUIC protocol.

[0060] In view of the above problems, the application adopts a scheme that the client sends a user request to the edge server in the HTTPS or HTTP protocol (i.e. HTTP(S)) commonly supported by the edge server, and sends a user request to the edge server in the QUIC protocol with higher transmission efficiency. The edge server selects one of the user requests based on the QUIC protocol or the user request based on the HTTP(S) protocol to respond according to a preset rule.

[0061] It should be noted that the application does not limit the time interval between the user requests sent by the client in two different protocols. In one way, the time interval between the two user requests can be 0, or any shorter time value.

[0062] It can be understood that when the preset time interval is 0, it represents that the client sends the user request based on two different protocols at the same time. When the time interval is 1s, it represents that the client sends the user request based on two different protocols with 1s interval.

[0063] In one mode, when the preset time interval is not 0, the client represents that the user request is sent based on two different protocols in a time interval. For this case, the application does not limit the sending order of the two user requests. For example, the client can first send the user request based on the QUIC protocol, or first send the user request based on HTTPS or HTTP (i.e. HTTP(S)).

[0064] In one mode, the user request can be a user request for obtaining resource data, or a request for deleting, adding or modifying specified data, etc. The application does not make specific limitations.

[0065] S102, detecting whether the edge server supports the QUIC protocol, if yes, sending a response message based on the QUIC protocol to the client, and not responding to the user request based on the HTTP(S) protocol.

[0066] In one mode, since the QUIC protocol can make the business processing more efficient. Therefore, in order to achieve the purpose of preferentially transmitting data based on the QUIC protocol, the application proposes that the edge server actively sends a response message based on the QUIC protocol to the client when detecting that the edge server supports the QUIC protocol, and does not respond to the user request sent by the client based on the HTTP(S) protocol.

[0067] Similarly, if the edge server detects that it does not support the QUIC protocol, in order to ensure the normal transmission of business data, the edge server sends a response message based on the HTTP(S) protocol to the client (the response message can carry feedback of the processing result), and does not respond to the user request sent by the client based on the QUIC protocol.

[0068] Further, for the same user request sent by the client based on two different protocols, the edge server can respond according to the protocol supported by the edge server. For the user request that does not need to be responded, in one mode, it can not be responded, but operations such as discarding, deleting or transferring to a specified storage area can be performed.

[0069] In another mode, an additional response message can be sent to the client, which does not process the user request based on the other protocol.

[0070] It can be understood that after the edge server detects that it supports the QUIC protocol and sends a response message based on the QUIC protocol to the client, the client can always send a user request based on the QUIC protocol to the edge server in the subsequent, so as to realize that the client and the edge server supporting the QUIC protocol can transmit data based on the QUIC protocol with higher data transmission efficiency.

[0071] In one way, the response message returned by the edge server to the client can carry the feedback result of processing the user request. For example, when the user request is a user access request, the resource data corresponding to the user access request can be carried in the response message. For another example, when the user request is a request to delete specified data, the information that the deletion of the specified data is successful (or failed) can be carried in the response message.

[0072] In the present application, the edge server receives user requests sent by the client in two different protocols, QUIC protocol and HTTP(S) protocol; detects whether the edge server supports the QUIC protocol, if yes, sends a response message to the client based on the QUIC protocol, and does not respond to the user request based on the HTTP(S) protocol. By applying the technical solution of the present application, the client can initiate a user request to the edge server based on the HTTP(S) protocol and the QUIC protocol respectively, so that the edge server responds to the user request of one of the protocols according to whether the edge server supports the QUIC protocol, and continues to transmit data through the corresponding protocol in the subsequent process, thereby solving the problem that the edge server cannot transmit resource data or needs to re-connect based on other protocols when the edge server does not support the QUIC protocol, which affects the business processing efficiency.

[0073] Optionally, in another embodiment based on the above method of the present application, after S102 (detecting whether the edge server supports the QUIC protocol), the following steps can be implemented:

[0074] If not, send a response message to the client based on the HTTP(S) protocol, and do not respond to the user request based on the QUIC protocol.

[0075] Further, if the edge server detects that it does not support the QUIC protocol, data transmission is performed between the edge server and the client based on the HTTP(S) protocol. Specifically, after processing the user request, the edge server needs to send a response message to the client based on the HTTP(S) protocol (the response message can carry the feedback of the processing result), so as to ensure that the client can receive the response message in time to avoid affecting the business processing progress.

[0076] Further, the edge server no longer responds to the user request sent by the client based on the QUIC protocol. In one way, it can not be responded to, but be executed, for example, discarded, deleted or moved to a specified storage area, or an additional response message is returned to the client that the user request sent based on the QUIC protocol will not be processed.

[0077] Optionally, in another embodiment based on the above method of the present application, before S102 (sending a response message to the client based on the QUIC protocol), the following steps can be implemented:

[0078] If it is determined that the user request is a user request for obtaining resource data, it is detected whether the local has stored resource data.

[0079] If not, the edge server sends a resource acquisition request to the upper server based on the QUIC protocol and the HTTP(S) protocol respectively within a preset time interval, and receives the resource data returned by the upper server.

[0080] In one way, if it is determined that the user request is a user request for obtaining resource data, the step of whether the local has stored resource data can be started. Further, if the edge server does not store the resource data corresponding to the user request, it is necessary to send a resource acquisition request to the upper server, which is not specifically limited in the present application, for example, it can be any one of other edge servers, parent servers, intermediate source servers and source station servers. The edge server sends a resource acquisition request to any one of the servers where the edge server stores the resource data, such as the source station server, other edge servers, parent servers, and intermediate source servers, and after obtaining the corresponding resource data, the edge server sends the resource data to the client.

[0081] Optionally, for the process of the edge server requesting resource data from the upper server, there can be a problem that the edge server and the upper server cannot transmit data due to the non-uniformity of the protocols supported by the two.

[0082] For example, when the edge server supporting the QUIC protocol and the upper server not supporting the QUIC protocol transmit resource data, the upper server cannot respond to the resource acquisition request sent by the edge server based on the QUIC protocol due to the upper server not supporting the QUIC protocol, and thus the edge server and the upper server cannot transmit data.

[0083] Therefore, in order to solve the above problem, the edge server in the embodiment of the present application needs to send a resource acquisition request to the upper server based on the HTTPS or HTTP protocol (i.e. HTTP(S)) commonly supported by the upper server, and to send a resource acquisition request to the upper server based on the QUIC protocol with higher transmission efficiency, so that the upper server selects one of the resource acquisition requests sent by the edge server based on the two different protocols to respond according to a preset rule.

[0084] It should be noted that the application also does not limit the time interval between the resource acquisition requests sent by the edge server to the upper server based on the two different protocols. In one way, the time interval between the two resource acquisition requests can be 0, or any shorter time value.

[0085] It can be understood that when the preset time interval is 0, it means that the edge server sends the resource acquisition request based on the two different protocols at the same time. When the time interval is 1s, it means that the edge server sends the resource acquisition request based on the two different protocols in turn with an interval of 1s. In one way, when the preset time interval is not 0, it means that the edge server sends the resource acquisition request based on the two different protocols in turn with a certain time interval. For this case, the application does not limit the sending order of the two resource acquisition requests. For example, the resource acquisition request can be sent based on the QUIC protocol first, or the resource acquisition request can be sent based on the HTTPS or HTTP (i.e. HTTP(S)) first.

[0086] Further, for the same resource acquisition request sent by the edge server based on the two different protocols, the upper server can send a response of the resource data according to the protocol it supports. For the resource acquisition request that does not need to be responded, in one way, it can not be responded, but operations such as discarding, deleting or moving to a specified storage area can be performed.

[0087] Further, after the edge server receives the resource data returned by the upper server based on the QUIC protocol or the HTTP(S) protocol, the edge server sends the resource data to the client. It can be understood that if the upper server supports the QUIC protocol, the upper server sends the resource data requested by the edge server based on the QUIC protocol. If the upper server does not support the QUIC protocol, the upper server sends the resource data requested by the edge server based on the HTTP(S) protocol.

[0088] In the above way, in the process of requesting the resource data by the edge server based on the QUIC protocol and the HTTP(S) protocol to the upper server, the upper server can return different response messages to the client according to whether it supports the QUIC protocol, so as to solve the problem that the upper server cannot send the resource data requested by the edge server due to the upper server not supporting the QUIC protocol, and then affect the user business processing efficiency.

[0089] Optionally, in another embodiment based on the above method of the application, before sending the response message to the client based on the HTTP(S) protocol, the following steps can be implemented:

[0090] If it is determined that the user request is a user request for obtaining resource data, it is detected whether the resource data is stored locally;

[0091] If not, a resource obtaining request is sent to an upper server based on an HTTP(S) protocol, and resource data returned by the upper server is received.

[0092] In one way, if it is determined that the user request is a user request for obtaining resource data, it can be started whether the resource data exists locally. Further, if the edge server does not store the resource data corresponding to the user request, in order to solve the problem that the edge server and the upper server may not be able to transmit data to each other due to the non-uniformity of the protocols supported by the two. In the embodiment of the application, the edge server can send a resource obtaining request to the upper server based on the HTTPS or HTTP protocol (i.e. HTTP(S) protocol) commonly supported by the upper server, and thus ensure that the edge server can receive the resource data in time and thus avoid affecting the experience effect of user browsing.

[0093] Optionally, in another embodiment based on the above-mentioned method of the application, after S101 (receiving the user request sent by the client in two different protocols of QUIC protocol and HTTP(S) protocol), the following steps can be implemented:

[0094] Detecting the time interval between receiving the two user requests;

[0095] If the time interval is less than a first preset time threshold, detecting whether the edge server supports the QUIC protocol.

[0096] It should be noted that due to the delay and other situations in the process of data transmission, even for the case that the client sends two user requests in different protocols at the same time, the receiving time of the two access requests may still have a certain difference for the edge server as the receiving end.

[0097] In one way, the application can detect the time interval between the user requests received by the edge server based on different protocols, and when it is detected that the time interval is less than a certain preset time threshold (i.e. the first preset time threshold), it is considered that the two user requests in different protocols sent by the client are generated based on the same data access, and then it is detected whether the edge server supports the QUIC protocol.

[0098] Among them, the first preset time threshold is not limited in the application, for example, it can be 0 seconds, or 1s or tens of milliseconds, etc.

[0099] It should be noted that the purpose of the embodiment of the application for detecting the time interval between two user requests is that if the receiving interval of the two requests is too long, the user requests of two different protocols sent by the client may not be generated based on the same data request. In turn, the edge server does not need to perform the judgment operation of detecting whether it supports the QUIC protocol, but directly responds to each user request separately, thereby saving unnecessary running resources of the edge server.

[0100] By applying the technical solution of the application, the client can initiate a user request to the edge server based on the HTTP(S) protocol and the QUIC protocol respectively, so that the edge server responds to the user request of one protocol according to whether it supports the QUIC protocol. And continue to transmit data through the corresponding protocol, thereby solving the problem that in the case that the transmission protocols of the edge server and the client are not unified, they cannot transmit data to each other, or need to be connected based on other protocols, thereby affecting the user business processing efficiency.

[0101] In another embodiment, the application further provides a user request processing method. Figure 2 The flowchart of a user request processing method according to an embodiment of the application is schematically shown. As shown in Figure 2 The method is applied to an upper server, which includes:

[0102] S201, receiving a resource acquisition request sent by an edge server in two different protocols of QUIC and HTTP(S).

[0103] In the application, the upper server is not limited, for example, it can be any one of other edge servers, parent servers, central servers.

[0104] For the process of the edge server requesting resource data from the upper server, there may also be a problem that the edge server and the upper server cannot transmit data due to the non-uniformity of the protocols supported by the two.

[0105] In order to solve the above-mentioned problem that the edge server and the upper server cannot transmit data due to the non-uniformity of the protocols supported by the two, in the embodiment of the application, the edge server needs to send a resource acquisition request to the upper server in the HTTPS or HTTP protocol (i.e. HTTP(S)) commonly supported by the upper server, and send a resource acquisition request to the upper server in the QUIC protocol with higher transmission efficiency. The upper server selects one of the resource acquisition request based on the QUIC protocol or the resource acquisition request based on the HTTP(S) protocol to respond according to a preset rule.

[0106] It should be noted that the application also does not limit the time interval between the reception of the resource acquisition request of the two different protocols by the upper server. In one way, the time interval between the two resource acquisition requests can be 0, or any shorter time value.

[0107] It can be understood that when the preset time interval is 0, it means that the upper server receives the resource acquisition request of the two different protocols at the same time. When the preset time interval is 1s, it means that the upper server receives the resource acquisition request of the two different protocols at an interval of 1s.

[0108] S202, detecting whether the self supports the QUIC protocol, if yes, sending the resource data corresponding to the resource acquisition request to the edge server based on the QUIC protocol, and not responding to the resource acquisition request based on the HTTP(S) protocol.

[0109] Further, for the edge server sending the same resource acquisition request based on the two different protocols, the upper server can respond to the sending of the resource data according to the protocol supported by the self, and for the resource acquisition request that does not need to be responded, in one way, it can not be responded, but be executed, for example, discarded, deleted or moved to the specified storage area and the like.

[0110] It can be understood that if the upper server supports the QUIC protocol, the resource data requested by the edge server is sent based on the QUIC protocol. If the upper server does not support the QUIC protocol, the resource data requested by the edge server is sent based on the HTTP(S) protocol.

[0111] S203, if not, sending the resource data to the edge server based on the HTTP(S) protocol, and not responding to the resource acquisition request based on the QUIC protocol.

[0112] Further, if the upper server detects that the self does not support the QUIC protocol, the data transmission with the edge server is based on the HTTP(S) protocol. Specifically, after obtaining the corresponding resource data, the upper server needs to send a response message (the response message carries the resource data) to the edge server based on the HTTP(S) protocol, so as to ensure that the edge server can timely receive the resource data to avoid affecting the progress of business processing.

[0113] Similarly, the upper server also does not respond to the resource acquisition request based on the QUIC protocol sent by the edge server. In one way, it can be discarded, or an additional response message is sent to the edge server, which no longer processes the resource acquisition request based on the QUIC protocol.

[0114] In the present application, the upper-layer server receives the resource acquisition requests sent by the edge server in two different protocols, i.e., the QUIC protocol and the HTTP(S) protocol; detects whether the upper-layer server supports the QUIC protocol, if yes, sends the resource data corresponding to the resource acquisition request to the edge server based on the QUIC protocol, and does not respond to the resource acquisition request based on the HTTP(S) protocol; if not, sends the resource data to the edge server based on the HTTP(S) protocol, and does not respond to the resource acquisition request based on the QUIC protocol. By applying the technical solution of the present application, in the process that the edge server requests the resource data from the upper-layer server based on the QUIC protocol and the HTTP(S) protocol, the upper-layer server can return different response messages to the edge server according to whether the upper-layer server supports the QUIC protocol, thereby solving the problem that the upper-layer server cannot send the requested resource data to the edge server due to the fact that the upper-layer server does not support the QUIC protocol, and further affecting the user service processing efficiency.

[0115] Optionally, in another embodiment based on the above-mentioned method of the present application, after S201 (receiving the resource acquisition requests sent by the edge server in two different protocols, i.e., the QUIC protocol and the HTTP(S) protocol), the following steps can be implemented:

[0116] detecting the time interval between the two received resource acquisition requests;

[0117] if the time interval is less than a second preset time threshold, detecting whether the upper-layer server supports the QUIC protocol.

[0118] It should be noted that due to the delay and other situations in the process of data transmission, even for the case that the edge server sends two different protocol resource acquisition requests at the same time, the receiving time of the two resource acquisition requests may still have a certain difference for the upper-layer server of the receiving end.

[0119] In one way, the present application can detect the time interval between the received resource acquisition requests based on different protocols by the upper-layer server, when it is detected that the time interval is less than a certain preset time threshold (i.e., the second preset time threshold), it is considered that the resource acquisition requests sent by the edge server based on two different protocols are generated based on the same resource data request, and then it is detected whether the upper-layer server supports the QUIC protocol.

[0120] Among them, the present application does not specifically limit the second preset time threshold, which can be 0 seconds, 1 second, etc.

[0121] It should be noted that the purpose of the upper server detecting the time interval between the two resource acquisition requests in the embodiments of the present application is that if the receiving interval of the two resource acquisition requests is too long, it means that the two resource acquisition requests of different protocols sent by the edge server may not be generated based on acquiring the same resource data. Then the upper server does not need to perform the judgment operation of detecting whether it supports the QUIC protocol, but directly responds to each resource acquisition request separately, thereby saving unnecessary running resources of the upper server.

[0122] By applying the technical solutions of the present application, the edge server can initiate resource acquisition requests to the upper server based on the HTTP(S) protocol and the QUIC protocol respectively, so that the upper server responds to the resource acquisition request of one protocol according to whether it supports the QUIC protocol. And continue to transmit data through the corresponding protocol, thereby solving the problem that in the case that the transmission protocols of the upper server and the edge server are not unified, data transmission cannot be performed between each other, or it is necessary to connect based on other protocols, thereby affecting the user business processing efficiency.

[0123] In one way, as shown in Figure 3 a flow chart of a user request processing method is provided in the present application, which includes:

[0124] First, the client sends a user request to the edge server based on the QUIC protocol and the HTTP(S) protocol.

[0125] Further, after the edge server receives the user request sent by the client based on the QUIC protocol and the HTTP(S) protocol, if it is determined that the user request is a user request for acquiring resource data, it is detected whether the local has stored resource data. If not, resource acquisition requests are sent to the upper server based on the QUIC protocol and the HTTP(S) protocol within a preset time interval.

[0126] Among them, after the upper server receives the resource acquisition requests sent by the edge server based on the QUIC protocol and the HTTP(S) protocol, it needs to detect whether it supports the QUIC protocol. If yes, the resource data corresponding to the resource acquisition request is sent to the edge server based on the QUIC protocol, and the resource acquisition request based on the HTTP(S) protocol is not responded; if not, the resource data corresponding to the resource acquisition request is sent to the edge server based on the HTTP(S) protocol, and the resource acquisition request based on the QUIC protocol is not responded.

[0127] In addition, after receiving the resource data sent by the upper server, the edge server also needs to detect whether it supports the QUIC protocol. If it supports, the response message containing the resource data corresponding to the user request is sent to the client based on the QUIC protocol, and the user request based on the HTTP(S) protocol is not responded.

[0128] If it does not support, the response message containing the resource data corresponding to the user request is sent to the client based on the HTTP(S) protocol, and the user request based on the QUIC protocol is not responded.

[0129] By applying the technical solution of the present application, the edge server can be initiated by the client based on the HTTP(S) protocol and the QUIC protocol to make the edge server respond to the access request of one of the protocols according to whether it supports the QUIC protocol. And continue to transmit data through the corresponding protocol, thereby solving the problem that the edge server cannot transmit resource data with the client when the edge server does not support the QUIC protocol.

[0130] In addition, in the process of the edge server obtaining resource data from the upper server, the edge server can initiate a resource acquisition request to the upper server based on the HTTP(S) protocol and the QUIC protocol, so that the upper server responds to the resource acquisition request of one of the protocols according to whether it supports the QUIC protocol. And continue to transmit data through the corresponding protocol, thereby further solving the problem that the upper server and the edge server cannot transmit data with each other when the transmission protocols of the two are not unified, or need to be connected based on other protocols, thereby affecting the efficiency of user business processing.

[0131] In another embodiment of the present application, as shown in Figure 4 The present application also provides an electronic device for processing user requests. The electronic device is applied to an edge server and includes,

[0132] The first receiving module 301 is configured to receive user requests sent by a client in two different protocols, QUIC protocol and HTTP(S) protocol.

[0133] The first sending module 302 is configured to detect whether it supports the QUIC protocol. If it does, the response message is sent to the client based on the QUIC protocol, and the user request based on the HTTP(S) protocol is not responded.

[0134] In the present application, the edge server receives user requests sent by the client in two different protocols, i.e., the QUIC protocol and the HTTP(S) protocol; detects whether the edge server supports the QUIC protocol, if yes, sends a response message to the client based on the QUIC protocol, and does not respond to the user request based on the HTTP(S) protocol. By applying the technical solution of the present application, the client can initiate a user request to the edge server based on the HTTP(S) protocol and the QUIC protocol respectively, so that the edge server responds to the user request of one of the protocols according to whether the edge server supports the QUIC protocol, and continues to transmit data through the corresponding protocol in the subsequent process, thereby solving the problem that the edge server cannot transmit resource data or needs to connect based on other protocols again when the edge server does not support the QUIC protocol, and thus affecting the efficiency of user business processing.

[0135] In another embodiment of the present application, the first sending module 302 is configured to:

[0136] If not, the response message is sent to the client based on the HTTP(S) protocol, and the user request based on the QUIC protocol is not responded.

[0137] In another embodiment of the present application, the first sending module 302 is configured to:

[0138] If it is determined that the user request is a user request for obtaining resource data, it is detected whether the resource data is stored locally;

[0139] If not, a resource obtaining request is sent to the upper server based on the QUIC protocol and the HTTP(S) protocol within a preset time interval, and resource data returned by the upper server is received.

[0140] In another embodiment of the present application, the first sending module 302 is configured to:

[0141] If it is determined that the user request is a user request for obtaining resource data, it is detected whether the resource data is stored locally;

[0142] If not, a resource obtaining request is sent to the upper server based on the HTTP(S) protocol, and resource data returned by the upper server is received.

[0143] In another embodiment of the present application, the first receiving module 301 is configured to:

[0144] The time interval between the reception of the two user requests is detected;

[0145] If the time interval is less than a first preset time threshold, it is detected whether the edge server supports the QUIC protocol.

[0146] In another embodiment of the present application, as shown in Figure 5 The present application also provides a user request processing electronic device. Wherein, the application is applied to the upper layer server, including:

[0147] The second receiving module 303 is configured to receive the resource acquisition request sent by the edge server in two different protocols of QUIC protocol and HTTP(S) protocol;

[0148] The second sending module 304 is configured to detect whether the self supports the QUIC protocol, if yes, send the resource data corresponding to the resource acquisition request to the edge server based on the QUIC protocol, and do not respond to the resource acquisition request based on the HTTP(S) protocol;

[0149] The third sending module 302 is configured to if no, send the resource data to the edge server based on the HTTP(S) protocol, and do not respond to the resource acquisition request based on the QUIC protocol.

[0150] In the present application, the upper layer server receives the resource acquisition request sent by the edge server in two different protocols of QUIC protocol and HTTP(S) protocol; detects whether the self supports the QUIC protocol, if yes, sends the resource data corresponding to the resource acquisition request to the edge server based on the QUIC protocol, and do not respond to the resource acquisition request based on the HTTP(S) protocol; if no, sends the resource data to the edge server based on the HTTP(S) protocol, and do not respond to the resource acquisition request based on the QUIC protocol. Through the application of the technical solution of the present application, in the process of the edge server requesting the resource data to the upper layer server based on the QUIC protocol and the HTTP(S) protocol, the upper layer server can return different response messages to the edge server according to whether the self supports the QUIC protocol, so as to solve the problem that the upper layer server cannot send the resource data requested by the edge server to the edge server due to the upper layer server not supporting the QUIC protocol, or needs to be connected based on other protocols again, thereby affecting the user business processing efficiency.

[0151] In another embodiment of the present application, the second receiving module 303 is configured to:

[0152] Detect the time interval between receiving the two resource acquisition requests;

[0153] If the time interval is less than the second preset time threshold, detect whether the self supports the QUIC protocol.

[0154] The present application provides an electronic device, as shown in Figure 6As shown, it comprises a computer readable storage medium 401 storing a computer program and a processor 402, which, when read and run by the processor, implements the method as described above.

[0155] The electronic device provided by the above embodiments of the present application has the same beneficial effects as the method adopted, run or implemented by the application program stored therein.

[0156] The computer readable storage medium provided by the embodiments of the present application stores a computer program, which, when read and run by the processor, implements the method as described above.

[0157] The technical solutions of the embodiments of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for making an electronic device (which can be an air conditioner, a refrigeration device, a personal computer, a server or a network device) or a processor execute all or part of the steps of the method described in the embodiments of the present application. The storage medium mentioned above includes a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk and various program code storage media.

[0158] The computer readable storage medium provided by the above embodiments of the present application has the same beneficial effects as the method adopted, run or implemented by the application program stored therein.

[0159] The computer program product provided by the embodiments of the present application includes a computer program, which, when executed by the processor, implements the method as described above.

[0160] The computer program product provided by the above embodiments of the present application has the same beneficial effects as the method adopted, run or implemented by the application program stored therein.

[0161] It should be noted that, in the present application, the terms such as first and second, etc. are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0162] Each of the embodiments in the present application is described in a related manner, and the same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the difference from other embodiments. In particular, for the user request processing method, electronic device, electronic equipment, and readable storage medium embodiments, since they are basically similar to the above-mentioned user request processing method embodiments, the description is relatively simple, and the relevant parts can be referred to the above-mentioned user request processing method embodiments.

[0163] Although the present application is disclosed as above, the present application is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present application, and therefore the protection scope of the present application should be subject to the scope defined by the claims.

Claims

1. A method for processing user requests, characterized in that, Applications to edge servers include: Receive user requests sent by clients using both QUIC and HTTP(S) protocols; It checks whether it supports the QUIC protocol. If so, it sends a response message to the client based on the QUIC protocol and does not respond to user requests based on the HTTP(S) protocol. Before sending the response message to the client based on the QUIC protocol, the method further includes: If it is determined that the user request is a user request for obtaining resource data, check whether the resource data is stored locally; If not, the system will send resource acquisition requests to the upper-layer server based on the QUIC protocol and the HTTP(S) protocol respectively within a preset time interval, and receive the resource data returned by the upper-layer server.

2. The method as described in claim 1, characterized in that, After detecting whether it supports the QUIC protocol, the following is also included: If not, the response message is sent to the client based on the HTTP(S) protocol, and no response is given to user requests based on the QUIC protocol.

3. The method as described in claim 2, characterized in that, Before sending the response message to the client based on the HTTP(S) protocol, the method further includes: If it is determined that the user request is a user request for obtaining resource data, check whether the resource data is stored locally; If not, a resource acquisition request is sent to the upper-layer server based on the HTTP(S) protocol, and the resource data returned by the upper-layer server is received.

4. The method as described in claim 1, characterized in that, After receiving user requests sent by the client using both QUIC and HTTP(S) protocols, the method further includes: Detect the time interval between two received user requests; If the time interval is less than a first preset time threshold, then it checks whether it supports the QUIC protocol.

5. A method for processing user requests, characterized in that, Applied to upper-layer servers, including: The system receives resource acquisition requests from an edge server using both QUIC and HTTP(S) protocols. The edge server receives user requests from clients using both protocols; it checks if it supports QUIC; if so, it sends a response message to the client using QUIC and does not respond to HTTP(S) user requests. The edge server also checks if the user request is for acquiring resource data; if not, it sends the resource acquisition request to an upper-layer server using both QUIC and HTTP(S) protocols within a preset time interval and receives the resource data returned by the upper-layer server. If it supports the QUIC protocol, it sends the resource data corresponding to the resource acquisition request to the edge server based on the QUIC protocol, and does not respond to resource acquisition requests based on the HTTP(S) protocol. If not, the resource data is sent to the edge server via the HTTP(S) protocol, and no response is given to resource acquisition requests based on the QUIC protocol.

6. The method as described in claim 5, characterized in that, After receiving resource acquisition requests sent by the edge server using both QUIC and HTTP(S) protocols, the process further includes: Detect the time interval between receiving two resource acquisition requests; If the time interval is less than the second preset time threshold, then it checks whether it supports the QUIC protocol.

7. An electronic device for processing user requests, characterized in that, Applications to edge servers include: The first receiving module is configured to receive user requests sent by the client using two different protocols: QUIC and HTTP(S). The first sending module is configured to detect whether it supports the QUIC protocol. If so, it sends a response message to the client based on the QUIC protocol and does not respond to user requests based on the HTTP(S) protocol. The first sending module is configured to: if it is determined that the user request is a user request for obtaining resource data, detect whether the resource data is stored locally; If not, the system will send resource acquisition requests to the upper-layer server based on the QUIC protocol and the HTTP(S) protocol respectively within a preset time interval, and receive the resource data returned by the upper-layer server.

8. An electronic device for processing user requests, characterized in that, Applied to upper-layer servers, including: The second receiving module is configured to receive resource acquisition requests sent by the edge server using both QUIC and HTTP(S) protocols. The edge server receives user requests from clients using both QUIC and HTTP(S) protocols; detects whether it supports the QUIC protocol; if so, it sends a response message to the client using the QUIC protocol and does not respond to user requests using the HTTP(S) protocol. The edge server is also configured to, if it determines that the user request is for acquiring resource data, detect whether the resource data is stored locally; if not, it sends the resource acquisition request to the upper-layer server using both the QUIC and HTTP(S) protocols within a preset time interval and receives the resource data returned by the upper-layer server. The second sending module is configured to detect whether it supports the QUIC protocol. If it does, it sends the resource data corresponding to the resource acquisition request to the edge server based on the QUIC protocol, and does not respond to the resource acquisition request based on the HTTP(S) protocol. The third sending module is configured to send the resource data to the edge server based on the HTTP(S) protocol if no, and not to respond to resource acquisition requests based on the QUIC protocol.

9. An electronic device, characterized in that, include: Memory, used to store executable instructions; as well as, A processor, configured to execute the executable instructions with the memory to perform the operation of the user request processing method according to any one of claims 1-4 or 5-6.

10. A computer-readable storage medium for storing computer-readable instructions, characterized in that, When the instruction is executed, it performs the operation of the user request processing method described in any one of claims 1-4 or 5-6.

11. A computer program product, comprising a computer program, characterized in that, The computer program is executed by a processor to implement the operation of the user request processing method as described in any one of claims 1-4 or 5-6.

Images