CN112055083A - Request processing method and device, electronic equipment and medium - Google Patents

Request processing method and device, electronic equipment and medium Download PDF

Info

Publication number
CN112055083A
CN112055083A CN202010937692.8A CN202010937692A CN112055083A CN 112055083 A CN112055083 A CN 112055083A CN 202010937692 A CN202010937692 A CN 202010937692A CN 112055083 A CN112055083 A CN 112055083A
Authority
CN
China
Prior art keywords
request
terminal
frame skipping
request frame
global
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202010937692.8A
Other languages
Chinese (zh)
Other versions
CN112055083B (en
Inventor
杨毅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
ICBC Technology Co Ltd
Original Assignee
ICBC Technology Co Ltd
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 ICBC Technology Co Ltd filed Critical ICBC Technology Co Ltd
Priority to CN202010937692.8A priority Critical patent/CN112055083B/en
Publication of CN112055083A publication Critical patent/CN112055083A/en
Application granted granted Critical
Publication of CN112055083B publication Critical patent/CN112055083B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • 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

Abstract

The present disclosure provides a request processing method, including: in response to sending a request to a designated terminal, determining a global request frame hopping number, which is the sum of the request frame hopping number allowed by the designated terminal and the request frame hopping number allowed by a proxy terminal addressed to the designated terminal; sending a request and the global request frame skipping times to a specified terminal; determining whether a re-addressing condition is satisfied; if so, determining the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times; and repeatedly executing the sending step and the determining step by taking the new request frame skipping times as the global request frame skipping times until the re-addressing condition is not met, so that the appointed terminal sends the request and the global request frame skipping times to the proxy terminal to obtain a response result. The disclosure also provides a request processing device, an electronic device and a computer readable storage medium. The method and the device provided by the disclosure can be applied to the financial field or other fields.

Description

Request processing method and device, electronic equipment and medium
Technical Field
The present disclosure relates to the field of network technologies, and in particular, to a request processing method, apparatus, electronic device, and medium.
Background
The client initiates a request to the terminal (or server) 1 to expect to obtain a corresponding response result. But the terminal 1 may or may not be able to handle part of the request, i.e. it may not be possible to handle the entire request of the request just by means of the terminal 1. Therefore, based on the request sent by the client and a part of the requests that can be processed by the terminal 1 itself, one or more other terminals (taking the terminal 2 as an example) need to be called to process other requests that cannot be processed by the terminal 1 itself in an agent manner, after the terminal 2 completes processing of the requests that cannot be processed by the terminal 1 itself, a response result is returned to the terminal 1, and the terminal 1 processes the received response result and returns a final response result to the client. Since the request is inevitably abnormal due to the uncontrollable condition in the whole process of initiating the request and waiting for the response, in order to prevent the request from failing due to the uncontrollable condition in the request process, the client and the terminal 1 usually set a maximum waiting time for processing the request, i.e. the request is overtime.
The related art also provides some termination strategies for request timeouts. For example, the time length of the timeout request of the client can be set, and the time length of the timeout request of the terminal can be set at the same time. However, excessive request timeout generated by the backend directly results in uncontrollable response speed of the front end, and the more the number of the terminals of the backend is, the longer the waiting time of the front end is, and even the situation that the request is processed and completed while the request is timeout occurs in the front end, which seriously affects user experience.
Disclosure of Invention
In view of the above, the above technical problem of the related art is at least partially overcome in order to realize that the request timeout generated at the back end makes the response speed of the front end controllable. The disclosure provides a request processing method, a request processing device, an electronic device and a medium.
To achieve the above object, one aspect of the present disclosure provides a request processing method applied to a client, including: and responding to a request sent to a designated terminal, and determining the global request frame skipping times, wherein the global request frame skipping times are the sum of the request frame skipping times allowed by the designated terminal and the request frame skipping times allowed by a proxy terminal addressed to the designated terminal. And sending the request and the global request frame skipping times to the specified terminal. It is determined whether a re-addressing condition is satisfied. And if the readdressing condition is met, determining the number of the global request frame skipping minus the actually consumed number of the request frame skipping as the new number of the request frame skipping. And repeatedly executing the sending step and the determining step by taking the new request frame skipping times as global request frame skipping times until the re-addressing condition is not met, so that the designated terminal sends the request and the global request frame skipping times to the proxy terminal to obtain a response result.
According to an embodiment of the present disclosure, the determining the global request frame skipping number includes at least one of: and determining the frame skipping times of the global request based on the request attribute of the request, wherein the request attribute comprises at least one attribute of a request mode, request content and request timeliness. And determining the global frame skipping request number based on the terminal attribute of the specified terminal. And determining the frame skipping times of the global request based on the terminal attribute of the proxy terminal, wherein the terminal attribute comprises at least one attribute of equipment parameters, operation states and available quantity.
According to an embodiment of the present disclosure, the determining whether the re-addressing condition is satisfied includes: and determining that the re-addressing condition is met under the condition that the request and the global request frame skipping times are failed to send and the global request frame skipping times are not exhausted.
According to an embodiment of the present disclosure, the determining whether the re-addressing condition is satisfied includes: and under the condition that the request and the global request frame skipping times are successfully sent, determining that the re-addressing condition is not met. And/or determining that the re-addressing condition is not satisfied in the case that the global request frame skipping number has been exhausted.
According to an embodiment of the present disclosure, the method further includes: and terminating the transmission of the request to the designated terminal when the global request frame skipping frequency is exhausted.
In order to achieve the above object, another aspect of the present disclosure provides a request processing method applied to a specific terminal, including: and receiving the request sent by the client and the frame skipping times of the global request. And determining a proxy terminal for processing the request based on the request. And sending a processing request and the global request frame skipping times to the proxy terminal. It is determined whether a re-addressing condition is satisfied. And if the readdressing condition is met, determining the number of the global request frame skipping minus the actually consumed number of the request frame skipping as the new number of the request frame skipping. And repeatedly executing the sending step and the determining step by taking the new request frame skipping times as global request frame skipping times until the re-addressing condition is not met, so as to receive the processing result of the proxy terminal and return a response result to the client based on the processing result.
According to an embodiment of the present disclosure, the determining whether the re-addressing condition is satisfied includes: and determining that the re-addressing condition is met under the condition that the processing request and the global request frame skipping times are failed to send and the global request frame skipping times are not exhausted.
According to an embodiment of the present disclosure, the determining whether the re-addressing condition is satisfied includes: and under the condition that the processing request and the global request frame skipping times are successfully transmitted, determining that the re-addressing condition is not met. And/or determining that the re-addressing condition is not satisfied in the case that the global request frame skipping number has been exhausted.
According to an embodiment of the present disclosure, the method further includes: and terminating the transmission of the processing request to the proxy terminal when the global request frame skipping frequency is exhausted.
According to an embodiment of the present disclosure, the proxy terminal includes a first proxy terminal for processing a first sub-request and a second proxy terminal for processing a second sub-request, the second proxy terminal is a lower terminal of the first proxy terminal, and the sending the processing request and the global request frame skipping number to the proxy terminal includes: and transmitting the first sub-request and the global request frame skipping number to the first proxy terminal, and causing the first proxy terminal to transmit the second sub-request and the global request frame skipping number to the second proxy terminal when the first sub-request and the global request frame skipping number are successfully transmitted.
According to an embodiment of the present disclosure, the method further includes: and terminating the transmission of the second sub-request to the second proxy terminal when the first sub-request and the global request frame skipping number are failed to be transmitted and the global request frame skipping number is exhausted.
In order to achieve the above object, another aspect of the present disclosure provides a request processing method applied to a first proxy terminal, including: and receiving a processing request and the global request frame skipping times sent by a specified terminal. And determining whether a second proxy terminal exists based on the processing request, wherein the first proxy terminal is used for processing a first sub-request, the second proxy terminal is used for processing a second sub-request, and the second proxy terminal is a lower terminal of the first proxy terminal. And if the second agent terminal exists, sending the second sub-request and the global request frame skipping times to the second agent terminal. It is determined whether a re-addressing condition is satisfied. And if the readdressing condition is met, determining the number of the global request frame skipping minus the actually consumed number of the request frame skipping as the new number of the request frame skipping. And repeatedly executing the transmitting step and the determining step by taking the new request frame skipping times as global request frame skipping times until the re-addressing condition is not met, so as to return the processing result of the first proxy terminal and the processing result of the second proxy terminal to the designated terminal.
According to an embodiment of the present disclosure, the determining whether the re-addressing condition is satisfied includes: and determining that the re-addressing condition is satisfied when the second sub-request and the global request frame skipping times are failed to be transmitted and the global request frame skipping times are not exhausted.
According to an embodiment of the present disclosure, the determining whether the re-addressing condition is satisfied includes: and under the condition that the second sub-request and the global request frame skipping times are successfully transmitted, determining that the re-addressing condition is not met. And/or determining that the re-addressing condition is not satisfied in the case that the global request frame skipping number has been exhausted.
According to an embodiment of the present disclosure, the method further includes: and if the second agent terminal does not exist, returning the processing result of the first agent terminal to the specified terminal.
To achieve the above object, another aspect of the present disclosure provides a request processing apparatus applied to a client, including: the device comprises a first determining module and a second determining module, wherein the first determining module is used for responding to a request sent to a designated terminal and determining the global request frame skipping times, and the global request frame skipping times are the sum of the request frame skipping times allowed by the designated terminal and the request frame skipping times allowed by an agent terminal addressed to the designated terminal. And the first sending module is used for sending the request and the global request frame skipping times to the specified terminal. A second determining module for determining whether a re-addressing condition is satisfied. And a third determining module, configured to determine, if the readdressing condition is satisfied, the new request frame skipping times by subtracting the actually consumed request frame skipping times from the global request frame skipping times. A first executing module, configured to repeatedly execute the sending step and the determining step using the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, so that the designated terminal sends the request and the global request frame skipping number to the proxy terminal, so as to obtain a response result.
According to an embodiment of the present disclosure, the first determining module includes at least one of: and the first determining submodule is used for determining the frame skipping times of the global request based on the request attribute of the request, wherein the request attribute comprises at least one attribute of a request mode, request content and request time effectiveness. And the second determining submodule is used for determining the frame skipping times of the global request based on the terminal attribute of the specified terminal. And the third determining submodule is used for determining the frame skipping times of the global request based on the terminal attribute of the proxy terminal. The terminal attribute includes at least one attribute of a device parameter, an operation state, and an available number.
According to an embodiment of the present disclosure, the second determining module is configured to determine that the re-addressing condition is satisfied when the request and the global request frame skipping number are failed to be sent and the global request frame skipping number is not exhausted.
According to an embodiment of the present disclosure, the second determining module is configured to determine that the re-addressing condition is not satisfied when the request and the global request frame skipping number are successfully transmitted. And/or determining that the re-addressing condition is not satisfied in the case that the global request frame skipping number has been exhausted.
According to an embodiment of the present disclosure, the second determining module is further configured to terminate sending the request to the designated terminal when the global request frame skipping number is exhausted.
To achieve the above object, another aspect of the present disclosure provides a request processing apparatus applied to a specific terminal, including: and the first receiving module is used for receiving the request sent by the client and the frame skipping times of the global request. And a fourth determining module, configured to determine, based on the request, a proxy terminal for processing the request. And the second sending module is used for sending the processing request and the global request frame skipping times to the proxy terminal. A fifth determining module for determining whether the re-addressing condition is satisfied. And a sixth determining module, configured to determine, if the readdressing condition is satisfied, the new request frame skipping times by subtracting the actually consumed request frame skipping times from the global request frame skipping times. And a second execution module, configured to repeatedly execute the sending step and the determining step using the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, to receive a processing result of the proxy terminal, and return a response result to the client based on the processing result.
According to an embodiment of the present disclosure, the fifth determining module is configured to determine that the re-addressing condition is satisfied when the processing request and the global request frame skipping number are failed to be sent and the global request frame skipping number is not exhausted.
According to an embodiment of the present disclosure, the fifth determining module is configured to determine that the re-addressing condition is not satisfied when the processing request and the global request frame skipping number are successfully transmitted. And/or determining that the re-addressing condition is not satisfied in the case that the global request frame skipping number has been exhausted.
According to an embodiment of the present disclosure, the fifth determining module is further configured to terminate sending the processing request to the proxy terminal when the global request frame hopping number is exhausted.
According to an embodiment of the present disclosure, the proxy terminal includes a first proxy terminal for processing a first sub-request and a second proxy terminal for processing a second sub-request, the second proxy terminal is a lower terminal of the first proxy terminal, the second sending module is configured to send the first sub-request and the global request frame skipping number to the first proxy terminal, and when the first sub-request and the global request frame skipping number are successfully sent, the first proxy terminal is enabled to send the second sub-request and the global request frame skipping number to the second proxy terminal.
According to an embodiment of the present disclosure, the second sending module is further configured to terminate sending the second sub-request to the second proxy terminal when the sending of the first sub-request and the global request frame skipping number fails and the global request frame skipping number is exhausted.
To achieve the above object, another aspect of the present disclosure provides a request processing apparatus applied to a first agent terminal, including: and the second receiving module is used for receiving the processing request and the global request frame skipping times sent by the appointed terminal. A seventh determining module, configured to determine whether a second proxy terminal exists based on the processing request, where the first proxy terminal is configured to process a first sub-request, the second proxy terminal is configured to process a second sub-request, and the second proxy terminal is a lower terminal of the first proxy terminal. And a third sending module, configured to send the second sub-request and the global request frame skipping number to the second proxy terminal if the second proxy terminal exists. An eighth determining module for determining whether the re-addressing condition is satisfied. And a ninth determining module, configured to determine, if the readdressing condition is satisfied, the new request frame skipping times by subtracting the actually consumed request frame skipping times from the global request frame skipping times. A third executing module, configured to repeatedly execute the sending step and the determining step using the new frame skipping request number as a global frame skipping request number until the re-addressing condition is not satisfied, so as to return the processing result of the first proxy terminal and the processing result of the second proxy terminal to the designated terminal.
According to an embodiment of the present disclosure, the eighth determining module is configured to determine that the re-addressing condition is satisfied when the second sub-request and the global request frame skipping number are failed to be transmitted and the global request frame skipping number is not exhausted.
According to an embodiment of the present disclosure, the eighth determining module is configured to determine that the re-addressing condition is not satisfied when the second sub-request and the global request frame skipping number are successfully transmitted. And/or determining that the re-addressing condition is not satisfied in the case that the global request frame skipping number has been exhausted.
According to an embodiment of the present disclosure, the eighth determining module is further configured to, if the second proxy terminal does not exist, return a processing result of the first proxy terminal to the designated terminal.
To achieve the above object, another aspect of the present disclosure provides an electronic device including: one or more processors, a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the apparatus as described above.
To achieve the above object, another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
To achieve the above object, another aspect of the present disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
Compared with the request processing method provided by the related art, the request processing method provided by the disclosure overcomes the technical problems that excessive request overtime generated at the back end in the related art directly causes uncontrollable response speed of the front end, the waiting time consumption of the front end is longer as the number of terminals at the back end is larger, and even the request overtime occurs at the front end, the request is processed and completed, when the request is sent to a specified terminal, the global request frame skipping frequency is determined, wherein the global request frame skipping frequency is the sum of the request frame skipping frequency allowed by the specified terminal and the request frame skipping frequency allowed by the agent terminal addressed to the specified terminal, the global request frame skipping frequency is sent while the request is sent, so that the global request frame skipping frequency is transmitted among the client, the specified terminal and the agent terminal, and when the global request frame skipping frequency is exhausted, the sending of the request is stopped in time, so that the response time of the front-end client becomes controllable, the waiting time of the front end can be effectively reduced, timely and correct response feedback is provided for a user, and the user experience is improved.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
FIG. 1 schematically illustrates a system architecture to which the request processing method and apparatus may be applied, which is suitable for use in embodiments of the present disclosure;
FIG. 2 schematically illustrates a network topology diagram to which the request processing method and apparatus may be applied, suitable for use with embodiments of the present disclosure;
FIG. 3 schematically illustrates an application scenario in which the method and apparatus for processing a request may be applied, which is suitable for embodiments of the present disclosure;
FIG. 4 schematically illustrates a flow chart of a request processing method applied to a client according to an embodiment of the present disclosure;
fig. 5 schematically shows a flowchart of a request processing method applied to a specified terminal according to an embodiment of the present disclosure;
fig. 6 schematically shows a flowchart of a request processing method applied to a proxy terminal according to an embodiment of the present disclosure;
FIG. 7 schematically shows a general flow diagram one of a request processing method according to an embodiment of the disclosure;
FIG. 8 schematically illustrates a general flow diagram two of a request processing method according to an embodiment of the disclosure;
FIG. 9 schematically shows a block diagram of a request processing device applied to a client in accordance with an embodiment of the present disclosure;
fig. 10 schematically shows a block diagram of a request processing apparatus applied to a specified terminal according to an embodiment of the present disclosure;
fig. 11 schematically shows a block diagram of a request processing apparatus applied to a proxy terminal according to an embodiment of the present disclosure;
FIG. 12 schematically illustrates a schematic diagram of a computer-readable storage medium product suitable for implementing the request processing method described above, according to an embodiment of the present disclosure; and
fig. 13 schematically shows a block diagram of an electronic device adapted to implement the request processing method described above according to an embodiment of the present disclosure.
In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable request processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.
Aiming at the field of multi-level network application, the embodiment of the disclosure provides a request processing method, a request processing device, electronic equipment and a medium. The request processing method is applied to a client and comprises a frame skipping number determining stage and a request sending stage. In the frame skipping number determining stage, in response to a request sent to a designated terminal, a global request frame skipping number is determined, wherein the global request frame skipping number is the sum of the request frame skipping number allowed by the designated terminal and the request frame skipping number allowed by an agent terminal addressed to the designated terminal. In the request sending stage, sending a request and the global request frame skipping times to a specified terminal; determining whether a re-addressing condition is satisfied; if the readdressing condition is met, determining the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times; and repeatedly executing the sending step and the determining step by taking the new request frame skipping times as the global request frame skipping times until the re-addressing condition is not met, so that the appointed terminal sends the request and the global request frame skipping times to the proxy terminal to obtain a response result.
By the request processing method, the overall request frame skipping frequency is transmitted among the client, the designated terminal and the proxy terminal, and the sending of the request is stopped in time under the condition that the request frame skipping frequency is exhausted, so that the response time of the front-end client becomes controllable, the waiting time of the front end can be effectively reduced, timely and correct response feedback is provided for a user, and the user experience is improved.
It should be noted that the request processing method and apparatus provided by the present disclosure can be used in the financial field, and can also be used in any field other than the financial field. Therefore, the application field of the request processing method and device provided by the present disclosure is not limited.
Fig. 1 schematically illustrates a system architecture 100 to which the request processing method and apparatus may be applied, which is suitable for use in embodiments of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the system architecture 100 according to this embodiment may include clients 101, 102, 103, a network 104, a designated terminal 105, and a proxy terminal 106. The network 104 is used to provide a medium for communication links between the clients 101, 102, 103 and the designated terminal 105, the designated terminal 105 and the proxy terminal 106. The network 104 may include various types of connections, such as a network (shown in FIG. 2) that may be provided by an ISP (Internet Service Provider). ISP is similar to China telecom, China Mobile and China Unicom, and is a famous ISP in China. An ISP can apply for a plurality of IP addresses from an internet administration authority, and then the authority and the individual obtain the right to use an IP address from an ISP and can connect to the internet through the ISP.
The user can use the clients 101, 102, 103 to send a request through the network 104, and can interact with the designated terminal 105, and when the designated terminal 105 cannot respond to all or part of the request, the proxy terminal 106 is required to perform proxy processing, and the processing result returned by the proxy terminal 106 is processed and then returned to the clients 101, 102, 103. Various messaging client applications, such as payment-type applications, shopping-type applications, web browser applications, search-type applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the clients 101, 102, 103.
Clients 101, 102, 103 may be a variety of electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablets, laptop and desktop computers, and the like.
The designated terminal 105 and the proxy terminal 106 may be server-side terminals that provide various services, such as web servers (for example only) that provide support for websites browsed by users using the clients 101, 102, 103. The web server may analyze and/or otherwise process the received message, such as the user request, and feed back the processing result (e.g., a web page, information, or data obtained or generated according to the user request) to the client 101, 102, 103.
It should be noted that the request processing method provided by the embodiments of the present disclosure may be generally executed by the clients 101, 102, 103. Accordingly, the request processing device provided by the embodiment of the present disclosure can be generally disposed in the clients 101, 102, 103. The request processing method provided by the embodiments of the present disclosure may also be performed by a designated terminal 105 or a proxy terminal 106 that is different from the clients 101, 102, 103 and capable of communicating with the clients 101, 102, 103. Accordingly, the request processing apparatus provided by the embodiment of the present disclosure may also be provided in a designated terminal 105 or a proxy terminal 106 that is different from the clients 101, 102, 103 and capable of communicating with the clients 101, 102, 103.
It should be understood that the number of clients, networks, designated terminals and proxy terminals in fig. 1 is merely illustrative. There may be any number of clients, networks, designated terminals, and proxy terminals, as desired for implementation.
Fig. 2 schematically illustrates a network topology diagram to which the request processing method and apparatus may be applied, which is applicable to the embodiments of the present disclosure.
As shown in fig. 2, ISP network topology 200 may include a backbone ISP network, regional ISP network, and local ISP network. Wherein the backbone ISP networks may include, but are not limited to, backbone ISP network 211, backbone ISP network 212, backbone ISP network 213, and backbone ISP network 214. Regional ISP networks may include, but are not limited to, regional ISP network 221, regional ISP network 222, regional ISP network 223, and regional ISP network 224. The local ISP network is typically the very end of the network and may include, but is not limited to, a corporate network 231, a school network 232, or a home network 233.
It should be noted that when a request is sent from a local client and first reaches the local ISP network, i.e. an IP frame skip occurs, the local ISP network is addressed by the routing address mapping table, and may be addressed to the local ISP network or may be addressed directly to the local ISP network of another local terminal. When the addressing reaches the regional ISP, an IP frame hop occurs, the regional ISP will continue addressing, and an IP frame hop will occur for each addressing. The total times of IP frame skipping are determined by TTL value set by the client.
The TTL (Time to live) field specifies the maximum number of segments that an IP packet can pass through before being dropped by a router. TTL is an 8-bit field in the IPv4 header, and refers to the number of times ICMP packets are forwarded, i.e., the number of hops or frame hops, and is located in the 9 th byte of IPv4 packets. The function of TTL is to limit the time that an IP packet can exist in a computer network, with a maximum value of 255 and a recommended value of 64. TTL is actually the maximum number of hops an IP packet can forward in a computer network. The TTL field is set by the sender of the IP packet, and the router modifies the TTL field value every time the IP packet passes through a router on the entire forwarding path from the source IP to the destination IP, specifically, the TTL field is decremented by 1, and then the IP packet is forwarded. If the TTL is reduced to 0 before the IP packet reaches the destination IP, the router discards the received IP packet with TTL of 0 and sends an ICMP time exceeded message to the sender of the IP packet. The TTL mainly has the functions of avoiding infinite circulation and receiving and transmitting of the IP packet in the network, saving network resources and enabling a sender of the IP packet to receive alarm information. The maximum value of TTL cannot be greater than 255 decimal and the recommended value is 64.
It should be understood that the number of backbone ISP networks, regional ISP networks, and local ISP networks shown in fig. 2 is merely illustrative. There may be any number of backbone ISP networks, regional ISP networks, and local ISP networks, as desired for implementation.
Fig. 3 schematically illustrates an application scenario in which the method and apparatus for processing a request may be applied, which is suitable for the embodiment of the present disclosure.
As shown in fig. 3, in the application scenario 300, a client, an ISP network 1, a terminal 1, an ISP network 2 and a terminal 2 are included, the terminal 1 and the terminal 2 form a complete request link, the ISP network 1 is used to provide a medium for a communication link between the client and the terminal 1, and the ISP network 2 is used to provide a medium for a communication link between the terminal 1 and the terminal 2. In operation S311, the client initiates a request to the terminal 1 to pass through the ISP network 1. In operation S312, terminal 1 is addressed by frame hopping 1 time in ISP network 1. In operation S313, the terminal 1 initiates a request to the terminal 2 to pass through the ISP network 2. In operation S314, terminal 2 is addressed by frame hopping 1 time in the ISP network 2. In operation S315, the terminal 2 processes the request. In operation S216, the terminal 2 returns the processing result to the client via the layer of the original path.
In order to prevent the request from failing due to uncontrollable situations encountered in the request process, the related art also provides a termination strategy for request timeout. For example, the time T0 when the client requests timeout may be set to 10s, and the time T1 when the terminal 1 requests timeout may be set to 5 s. When the client initiates a request to the terminal 1, if the request is abnormal, a return is sent to the client for 10 seconds at most according to the expectation of the client. However, such setting may cause the client to receive the timeout request, and the request transaction initiated by the client has actually been successfully executed, which may specifically include the following two cases.
In the first case: the client initiates a request to the terminal 1, the time of the request process is 9s, the terminal 1 subsequently requests the terminal 2 to process the request of the client in an agent mode, the time of the processing process of the terminal 2 is 1.5s, at the moment, the client directly returns a response result of processing overtime to the client after not receiving the request response of the terminal 2, and the request processing is completed after the terminal 2 returns the result of 0.5 s.
In the second case: the client initiates a request to the terminal 1, the time of the request process is 9s, the terminal 1 then requests the terminal 2 to process the request of the client in an agent mode, the process needs 6s, the terminal 1 requests timeout to perform timeout feedback on the client, the request timeout time of the client is 10s, 9s is consumed in the process that the client requests the terminal 1, no response feedback is given by the terminal 1, and the client returns request timeout to the client.
In both cases, the request policy expected by the client is inconsistent with the actually generated request policy. The reason is that excessive requests generated in other terminals are overtime, which directly causes the response result of the front-end client to become uncontrollable, and the more the number of the terminals at the back end is, the longer the waiting time of the front end is, and even the situation that the request is processed and completed while the request is overtime occurs at the front end.
It should be noted that if a special condition is encountered during the request, that is, a server abnormality occurs in the subsequent terminal, but an error that the terminal is not reachable is encountered, as in 404, the request failure may be directly returned according to the actual condition, or the attempt is continued until the time for the request timeout expires.
It should be understood that terminal 1 in fig. 3 is a terminal for receiving a client request, terminal 2 is a terminal for which terminal 1 requests proxy processing, and the number of proxy terminals is merely illustrative. There may be any number of proxy terminals depending on the specific implementation requirements of the client initiating the request to the terminal 1.
The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments of the invention. Moreover, any number of elements in the drawings are by way of example and not by way of limitation, and any nomenclature is used solely for differentiation and not by way of limitation.
Fig. 4 schematically shows a flowchart of a request processing method applied to a client according to an embodiment of the present disclosure. As shown in fig. 4, the method 400 includes operations S410 to S450.
In operation S410, a global request frame skip number is determined in response to transmitting a request to a designated terminal.
In this disclosure, the designated terminal may be a terminal directly connected to the client, and configured to receive a request sent by the client. The request message sent by the client to the specified terminal may be an HTTP (Hyper Text Transfer Protocol) request, including: in the message head line, the request method for the resource, the identifier of the resource and the protocol used. An HTTP request message consists of 4 parts, a request line (request line), request headers (headers), a blank line (blank line), and request data (request body). The request line is divided into three parts: a request method, a request address URL (Uniform Resource Locator) and an HTTP protocol version. Html HTTP/1.1, for example GET/index. A URL is an abstract unique identification method of a resource location. The format of the protocol version is: minor version numbers, commonly used are HTTP/1.0 and HTTP/1.1.
Taking HTTP request as an example, the request retry means that request exception is captured by ICMP (Internet Control Message Protocol) in the current request, which is generally caused by unreachable end point, transmission timeout, IP (Internet Protocol) header error and lack of other necessary parameters, and at this time, the request needs to be retransmitted to try to obtain the desired value.
In the present disclosure, the global request frame hopping number determined in response to the transmission of the request to the specified terminal is the maximum value of the global request frame hopping numbers in the entire request process, which is the sum of the request frame hopping numbers allowed to be addressed to the specified terminal and the request frame hopping numbers allowed to be addressed to the proxy terminal of the specified terminal. That is, the total of the frame skipping times of the ISP network allowed to address the designated terminal when the designated terminal is requested and the frame skipping times of the ISP network allowed to address the proxy terminal when the proxy terminal is requested is the global request frame skipping times.
In operation S420, a request and a global request frame skip number are transmitted to a designated terminal.
According to the embodiment of the disclosure, when a request is sent to a specified terminal, the number of frame skipping times of a global request is additionally sent. According to the components of the HTTP request, the global frame hopping number may be transmitted to the specified terminal as a request parameter, and may be stored in a request header (headers), for example. The present disclosure is not limited to the specific attached embodiments.
In operation S430, it is determined whether a re-addressing condition is satisfied. In operation S440, if the re-addressing condition is satisfied, the global request frame skip number minus the actually consumed request frame skip number is determined as a new request frame skip number.
In the disclosure, under the condition that the re-addressing condition is met, the global request frame skipping times are updated in real time, and a basis is provided for judging whether the re-addressing condition is met.
In operation S450, the transmitting step and the determining step are repeatedly performed with the new request frame skipping number as the global request frame skipping number until the re-addressing condition is not satisfied, so that the designated terminal transmits the request and the global request frame skipping number to the proxy terminal to obtain a response result.
In the present disclosure, the HTTP response packet is composed of 4 parts of a status line (status line), headers (headers), a blank line (blank line), and response data (response body), corresponding to the HTTP request packet. The status row consists of 3 parts, respectively: protocol version, status code scan. The protocol version is consistent with the request message, and the state code description is a simple description of the state code.
Through the embodiment of the disclosure, the global request frame skipping frequency is determined according to the request sent by the client to the designated terminal, and is also sent while the request is sent to the designated terminal, so that the global request frame skipping frequency can be transmitted among the client, the designated terminal and the proxy terminal along with the circulation of the request, and the request frame skipping frequency is consumed once per addressing, therefore, the global request frame skipping frequency is reduced by one time, before the designated terminal is successfully addressed, the actually consumed request frame skipping frequency is reduced from the global request frame skipping frequency, the global request frame skipping frequency can be dynamically updated, so that the addressing can be executed again under the condition that the global request frame skipping frequency is not exhausted, and under the condition that the global request frame skipping frequency is exhausted, the sending of the request is timely terminated, so that the response of the front-end client becomes controllable, the waiting time of the front end is reduced, the user can respond and feed back timely, and the user experience is improved.
It should be noted that, in response to sending a request to a specific terminal, the determined global request frame skipping number is changed in a floating manner according to the actual situation, and is not fixed or unchanged. The determination method can be determined according to practical situations and experience of a person skilled in the art, and the disclosure does not limit the determination method.
As an alternative embodiment, the aforementioned determining the global request frame skipping number includes at least one of: and determining the frame skipping times of the global request based on the request attribute of the request, wherein the request attribute comprises at least one attribute of a request mode, request content and request timeliness. And determining the global frame skipping request number based on the terminal attribute of the specified terminal. And determining the global frame skipping request times based on the terminal attribute of the proxy terminal, wherein the terminal attribute comprises at least one attribute of equipment parameters, an operation state and an available number.
Alternatively, the global request frame hopping number may be determined based on only the request attribute, may be determined based on only the terminal attribute of the specified terminal, and may be determined based on only the terminal attribute of the proxy terminal.
Alternatively, the global request frame skipping number may be determined based on the request attribute and the terminal attribute of the designated terminal, may be determined based on the request attribute and the terminal attribute of the proxy terminal, or may be determined based on the terminal attributes of the designated terminal and the proxy terminal.
Alternatively, the global request frame hopping number may be determined based on the request attribute, the terminal attribute of the specified terminal, and the terminal attribute of the proxy terminal.
In the present disclosure, the data interaction manner between the client and the terminal, and between the terminal and the terminal includes, but is not limited to, HTTP and RPC (remote procedure call) request manners. Taking HTTP request approach as an example, HTTP1.0 defines three request methods: GET, POST and HEAD methods. The request method defined by HTTP/1.1 has 8 types: GET (requests a resource in its entirety), POST (submits a form), PUT (uploads a file), DELETE (DELETEs), PATCH, HEAD (requests only a response header), OPTIONS (returns the methods supported by the requested resource), TRACE (the agent passed in the middle of pursuing a resource request). The higher the requirement on the request aging, the smaller the determined global request frame skipping times. The more complex the content of the request, the greater the determined global request frame skipping number.
In the present disclosure, the device parameters are used to characterize the maximum processing capability desired by the terminal, such as processor, memory configuration parameters. The operation state is used for representing the current actual processing capacity of the terminal, such as processor occupancy rate and memory occupancy rate. The available number is used to characterize the number of terminals used to process the request. The device parameters, the running state and the available number intuitively reflect the request processing capacity of the terminal to a certain extent, and provide reference basis for determining the global request frame skipping times.
For example, if the number of terminals is 5, the global request frame skipping number may be determined to be 64, and if the number of terminals is 10, the global request frame skipping number may be determined to be 128. For another example, if the request method is post, the global request frame skipping number may be determined to be 128, and if the request method is get, the global request frame skipping number may be determined to be 64. For another example, if the request is an immediate response request, the global request frame skipping number may be determined to be 64, and if the request is a non-immediate response request, the global request frame skipping number may be determined to be a larger request frame skipping number, such as 128.
As an alternative embodiment, the aforementioned operation S430 (determining whether the re-addressing condition is satisfied) includes: and determining that the re-addressing condition is met under the condition that the request and the global request frame skipping times are failed to send and the global request frame skipping times are not exhausted.
As an alternative embodiment, the aforementioned operation S430 (determining whether the re-addressing condition is satisfied) may include: and under the condition that the request and the global request frame skipping times are successfully transmitted, determining that the re-addressing condition is not met. And/or determining that the aforementioned re-addressing condition is not satisfied in the case that the aforementioned global request frame skipping number has been exhausted.
As an alternative embodiment, the foregoing method may further include: and terminating the transmission of the request to the designated terminal when the global request frame skipping number is exhausted.
Fig. 5 schematically shows a flowchart of a request processing method applied to a specified terminal according to an embodiment of the present disclosure. As shown in fig. 5, the method 500 includes operations S510 to S560.
In operation S510, a request sent by a client and a global request frame skipping number are received.
According to the embodiment of the disclosure, the global request frame skipping number received by the designated terminal is the global request frame skipping number obtained by subtracting the request frame skipping number actually consumed by addressing the designated terminal from the determined global request frame skipping number in response to the request sent to the designated terminal by the client. And if the request frame skipping times actually consumed by addressing the specified terminal are 10, the global request frame skipping times sent by the client and received by the specified terminal are smaller than the global request frame skipping times determined by the client in response to the request sent to the specified terminal.
In operation S520, based on the request, a proxy terminal for processing the request is determined.
In operation S530, a processing request and a global request frame skip number are transmitted to the proxy terminal.
In the present disclosure, after the designated terminal receives the request transmitted from the client, it is necessary to proxy the terminal to process part of the request. Therefore, the designated terminal can send a processing request to the proxy terminal in anticipation of acquiring a partially requested processing result from the proxy terminal. And when the processing request is sent, sending the global request frame skipping times.
In operation S540, it is determined whether a re-addressing condition is satisfied. In operation S550, if the re-addressing condition is satisfied, the global request frame skip number minus the actually consumed request frame skip number is determined as a new request frame skip number.
In operation S560, the transmitting step and the determining step are repeatedly performed with the new request frame hopping number as the global request frame hopping number until the re-addressing condition is not satisfied to receive the processing result of the proxy terminal and return a response result to the client based on the processing result.
By the embodiment of the disclosure, the global request frame skipping times are sent to the proxy terminal, so that the global request frame skipping times can be transmitted between the designated terminal and the proxy terminal along with the circulation of the processing request, and the request frame skipping times are consumed once per addressing, so that the global request frame skipping times are reduced once, before the proxy terminal is successfully addressed, the actually consumed request frame skipping times are reduced from the global request frame skipping times, the global request frame skipping times can be dynamically updated, so that the addressing can be executed again under the condition that the global request frame skipping times are not exhausted, and the sending of the request is timely terminated under the condition that the global request frame skipping times are exhausted, so that the response of the front-end client becomes controllable, the waiting time of the front end is reduced, the timely response feedback is given to the user, and the user experience is improved.
As an alternative embodiment, the aforementioned operation S540 (determining whether the re-addressing condition is satisfied) includes: and determining that the re-addressing condition is met under the condition that the processing request and the global request frame skipping times are failed to send and the global request frame skipping times are not exhausted.
As an alternative embodiment, the aforementioned operation S540 (determining whether the re-addressing condition is satisfied) may include: and determining that the re-addressing condition is not met under the condition that the processing request and the global request frame skipping times are successfully transmitted. And/or determining that the aforementioned re-addressing condition is not satisfied in the case that the aforementioned global request frame skipping number has been exhausted.
As an alternative embodiment, the foregoing method further comprises: and terminating the transmission of the processing request to the proxy terminal when the global request frame hopping number is exhausted.
According to different requests sent by the client, the number of the agent terminals which are required to request agent processing by the appointed terminal is different. One proxy terminal agent process may be requested, or a plurality of proxy terminal agent processes may be requested. The client (front end) initiates a request to the terminal (back end), the topology of each terminal of the back end can be a linked list structure, and each node in the linked list structure can be a cluster service. The topology of the terminals at the back end can also be a distributed architecture. Background network topologies include, but are not limited to, the above. The present disclosure has no explicit link requirements for the topology of the back-end terminals, but each terminal knows the next terminal address for the traffic it handles. In the case of a proxy terminal, the request processing method between the designated terminal and the proxy terminal may refer to the aforementioned method.
As an alternative embodiment, the agent terminal includes a first agent terminal for processing a first sub-request and a second agent terminal for processing a second sub-request, the second agent terminal is a lower terminal of the first agent terminal, and the sending the processing request and the global request frame skipping number to the agent terminal includes: and transmitting the first sub-request and the global request frame skipping number to the first proxy terminal, and causing the first proxy terminal to transmit the second sub-request and the global request frame skipping number to the second proxy terminal when the first sub-request and the global request frame skipping number are successfully transmitted.
As an alternative embodiment, the foregoing method further comprises: and terminating the transmission of the second sub-request to the second proxy terminal when the first sub-request and the global request frame skipping number are failed to be transmitted and the global request frame skipping number is exhausted.
In the case of a plurality of proxy terminals, the request processing method between the designated terminal and the proxy terminal refers to the method described above, and the request processing method between the proxy terminal and the proxy terminal may refer to the method described below.
Fig. 6 schematically shows a flowchart of a request processing method applied to a proxy terminal according to an embodiment of the present disclosure. As shown in fig. 6, the method 600 includes operations S610 to S660.
In operation S610, a processing request and a global request frame hopping number transmitted by a designated terminal are received.
In operation S620, it is determined whether a second proxy terminal exists based on the processing request.
According to an embodiment of the present disclosure, the first proxy terminal is configured to process the first sub-request, the second proxy terminal is configured to process the second sub-request, and the second proxy terminal is a subordinate terminal of the first proxy terminal. And the first agent terminal knows the terminal address of the next terminal of the service handled by itself, i.e. the second agent terminal.
In operation S630, if there is a second proxy terminal, a second sub-request and a global request frame skip number are transmitted to the second proxy terminal.
In operation S640, it is determined whether a re-addressing condition is satisfied. In operation S650, if the re-addressing condition is satisfied, the global request frame skip number minus the actually consumed request frame skip number is determined as a new request frame skip number.
In operation S660, the transmitting step and the determining step are repeatedly performed with the new request frame hopping number as the global request frame hopping number until the re-addressing condition is not satisfied, to return the processing result of the first proxy terminal and the processing result of the second proxy terminal to the designated terminal.
By the embodiment of the disclosure, the global request frame skipping times are sent to the proxy terminal, so that the global request frame skipping times can be transmitted between the proxy terminal and the proxy terminal along with the circulation of processing requests, and the request frame skipping times are consumed once per addressing, so that the global request frame skipping times are reduced once, before the proxy terminal is successfully addressed, the actually consumed request frame skipping times are reduced from the global request frame skipping times, the global request frame skipping times can be dynamically updated, so that the addressing can be executed again under the condition that the global request frame skipping times are not exhausted, and the sending of the request is timely terminated under the condition that the global request frame skipping times are exhausted, so that the response of the front-end client becomes controllable, the waiting time of the front end is reduced, the timely response feedback is given to a user, and the user experience is improved.
As an alternative embodiment, the aforementioned determining whether the re-addressing condition is satisfied comprises: and determining that the re-addressing condition is satisfied when the second sub-request and the global request frame skipping times fail to be transmitted and the global request frame skipping times are not exhausted.
As an alternative embodiment, the aforementioned determining whether the re-addressing condition is satisfied comprises: and determining that the re-addressing condition is not met under the condition that the second sub-request and the global request frame skipping times are successfully transmitted. And/or determining that the aforementioned re-addressing condition is not satisfied in the case that the aforementioned global request frame skipping number has been exhausted.
As an alternative embodiment, the foregoing method further comprises: and if the second agent terminal does not exist, returning the processing result of the first agent terminal to the specified terminal.
Fig. 7 schematically shows a general flowchart one of a request processing method according to an embodiment of the present disclosure. As shown in fig. 7, the method 700 may include operations S711 to S717.
In operation S711, the client sets the TTL preset value to 128 as a request parameter. In the present disclosure, TTL is the number of requested frame hops. In operation S712, the client initiates a request to the terminal 1 to pass through the ISP network 1, accompanied by a request for the number of frame skipping 128. In operation S713, the terminal 1 is addressed 10 times by frame skipping in the ISP network 1. In operation S714, terminal 1 initiates a request to terminal 2 to pass through the ISP network 2. In operation S715, the ISP network 2 is addressed to the terminal 2 10 times by skipping frames. In operation S716, if the total number of requested TTL is 20 and is less than the preset value 128, the terminal 2 processes the task and returns the result. In operation S717, the terminal 2 returns the processing result to the client via the original route layer, and the whole request link is ended.
Fig. 8 schematically shows an overall flow chart of a request processing method according to an embodiment of the present disclosure. As shown in fig. 8, the method 800 may include operations S811 through S8110.
In operation S811, the client sets a request TTL of 128 as a request parameter. In operation S812, the client initiates a request to the terminal 1 to pass through the ISP network 1. In operation S813, frame skipping in the ISP network 1 is addressed to the terminal 110 times, i.e., the ISP network consumes 10 frame skipping halfway in addressing the terminal 1. In operation S814, the terminal 1 receives the request sent by the client and the remaining number of frame skipping requests 118, which is greater than 0, and continues to send the next round of request. The terminal 1 initiates a request to a subsequent terminal to pass through the ISP network. In operation S815, the terminal is addressed 10 times by frame skipping in the ISP network 1. In operation S816, the terminal mutually proxies within the set, and each frame skipping request is recorded by the subsequent terminal until the total number of frame skipping request times is greater than the TTL number set by the client, if the number of frame skipping request times is greater than the TTL number, the timeout is returned, otherwise, the next proxy operation is continued, and it is assumed that the total number of frame skipping occurring in the terminal. In operation S817, the terminal initiates a request to terminal n to pass through the ISP network n. In operation S818, the ISP network n is addressed to the terminal n 10 times by skipping frames. In operation S819, if the total requested TTL is 120 and is smaller than the preset value 128, the terminal n processes the task and returns a result. In operation S8110, the terminal n returns the processing result to the client via the original route layer, and the whole request link is ended.
The request processing method provided by the disclosure is suitable for multi-level network application request/forwarding processing. The terminal 1 receiving the client request is the designated terminal and serves as an initial terminal of a request link, the terminals 2 to n are proxy terminals, the terminal n serves as a final terminal of the request link, more than 0 number of proxy terminals are allowed to participate in processing of request services between the initial terminal and the final terminal, and the terminal n. The ISP network 1 is a network between the client and the terminal 1, the ISP network n is a network between the terminal and the terminal n, and the number of ISP networks allowed to participate in the processing of the request service between the ISP network 1 and the ISP network n is greater than 0, and the request processing method between the terminals 2 and the terminal n may refer to the request processing method between the client and the specified terminal, which is not described herein again.
Fig. 9 schematically shows a block diagram of a request processing device applied to a client according to an embodiment of the present disclosure. As shown in fig. 9, the apparatus 900 includes a first determining module 910, a first sending module 920, a second determining module 930, a third determining module 940, and a first executing module 950.
A first determining module 910, configured to determine a global request frame skipping number in response to sending a request to a specified terminal. Optionally, the first determining module 910 may be configured to perform operation S410 described in fig. 4, for example, and is not described herein again.
And a first sending module 920, configured to send the request and the global request frame skipping number to the specified terminal. Optionally, the first sending module 920 may be configured to perform operation S420 described in fig. 4, for example, and is not described herein again.
A second determining module 930 for determining whether the re-addressing condition is satisfied. Optionally, the second determining module 930 may be configured to perform operation S430 described in fig. 4, for example, and is not described herein again.
A third determining module 940, configured to determine the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times if the re-addressing condition is met. Optionally, the third determining module 940 may be configured to perform operation S440 described in fig. 4, for example, and is not described herein again.
A first executing module 950, configured to repeatedly execute the sending step and the determining step with the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, so that the designated terminal sends the request and the global request frame skipping number to the proxy terminal to obtain a response result. Optionally, the first executing module 950 may be configured to execute operation S450 described in fig. 4, for example, and is not described herein again.
As an alternative embodiment, the aforementioned first determining module 910 may include at least one of the following: the first determining submodule is used for determining the frame skipping times of the global request based on the request attribute of the request, wherein the request attribute comprises at least one attribute of a request mode, request content and request timeliness; the second determining submodule is used for determining the frame skipping times of the global request based on the terminal attribute of the specified terminal; and the third determining submodule is used for determining the frame skipping times of the global request based on the terminal attribute of the proxy terminal. The terminal attribute includes at least one attribute of a device parameter, an operation state, and an available number.
As an alternative embodiment, the second determining module 930 may be configured to determine that the re-addressing condition is satisfied when the request and the global request frame skipping number fail to be transmitted and the global request frame skipping number is not exhausted.
As an alternative embodiment, the second determining module 930 may be configured to determine that the re-addressing condition is not satisfied when the request and the global request frame skipping number are successfully transmitted; and/or determining that the aforementioned re-addressing condition is not satisfied in the case that the aforementioned global request frame skipping number has been exhausted.
As an alternative embodiment, the second determining module 930 may be further configured to terminate sending the request to the designated terminal when the global request frame skipping number is exhausted.
Fig. 10 schematically shows a block diagram of a request processing apparatus applied to a specified terminal according to an embodiment of the present disclosure. As shown in fig. 10, the apparatus 1000 includes a first receiving module 1010, a fourth determining module 1020, a second transmitting module 1030, a fifth determining module 1040, a sixth determining module 1050, and a second performing module 1060.
The first receiving module 1010 is configured to receive a request sent by a client and a global request frame skipping number. Optionally, the first receiving module 1010 may be configured to perform operation S510 described in fig. 5, for example, and is not described herein again.
A fourth determining module 1020 for determining, based on the request, a proxy terminal for processing the request. Optionally, the fourth determining module 1020 may be configured to perform operation S520 described in fig. 5, for example, and is not described herein again.
A second sending module 1030, configured to send the processing request and the global request frame skipping number to the proxy terminal. Optionally, the second sending module 1030 may be configured to perform operation S530 described in fig. 5, for example, and is not described herein again.
A fifth determining module 1040, configured to determine whether the re-addressing condition is satisfied. Optionally, the fifth determining module 1040 may be configured to perform operation S540 described in fig. 5, for example, and is not described herein again.
A sixth determining module 1050, configured to determine, if the readdressing condition is met, the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times. Optionally, the sixth determining module 1050 may be configured to perform operation S550 described in fig. 5, for example, and is not described herein again.
A second executing module 1060, configured to repeatedly execute the sending step and the determining step with the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, so as to receive a processing result of the proxy terminal, and return a response result to the client based on the processing result. Optionally, the second executing module 1060 may be configured to execute operation S560 described in fig. 5, for example, and is not described herein again.
As an alternative embodiment, the fifth determining module 1040 may be configured to determine that the re-addressing condition is satisfied when the processing request and the global request frame skipping number fail to be sent, and the global request frame skipping number is not exhausted.
As an alternative embodiment, the fifth determining module 1040 may be configured to determine that the re-addressing condition is not met when the processing request and the global request frame skipping number are successfully transmitted; and/or determining that the aforementioned re-addressing condition is not satisfied in the case that the aforementioned global request frame skipping number has been exhausted.
As an alternative embodiment, the fifth determining module 1040 may be further configured to terminate sending the processing request to the proxy terminal when the global request frame skipping number is exhausted.
As an alternative embodiment, the agent terminal includes a first agent terminal for processing a first sub-request and a second agent terminal for processing a second sub-request, the second agent terminal is a lower terminal of the first agent terminal, and the second sending module 1030 may be configured to send the first sub-request and the global request frame skipping number to the first agent terminal, and in a case that the first sub-request and the global request frame skipping number are successfully sent, the first agent terminal is enabled to send the second sub-request and the global request frame skipping number to the second agent terminal.
As an alternative embodiment, the second sending module 1030 may be further configured to terminate sending the second sub-request to the second proxy terminal when the sending of the first sub-request and the global request frame skipping number fails and the global request frame skipping number is exhausted.
Fig. 11 schematically shows a block diagram of a request processing apparatus applied to a proxy terminal according to an embodiment of the present disclosure. As shown in fig. 11, the apparatus 1100 includes a second receiving module 1110, a seventh determining module 1120, a third sending module 1130, an eighth determining module 1140, a ninth determining module 1150, and a third executing module 1160.
The second receiving module 1110 is configured to receive a processing request and a global request frame skipping number sent by a specific terminal. Optionally, the second receiving module 1110 may be configured to perform operation S610 described in fig. 6, for example, and is not described herein again.
A seventh determining module 1120, configured to determine whether a second proxy terminal exists based on the processing request, where the first proxy terminal is configured to process the first sub-request, the second proxy terminal is configured to process the second sub-request, and the second proxy terminal is a lower terminal of the first proxy terminal. Optionally, the seventh determining module 1120 may be configured to perform operation S620 described in fig. 6, for example, and is not described herein again.
A third sending module 1130, configured to send the second sub-request and the global request frame skipping number to the second proxy terminal if the second proxy terminal exists. Optionally, the third sending module 1130 may be configured to perform operation S630 described in fig. 6, for example, and is not described herein again.
An eighth determining module 1140 for determining whether the re-addressing condition is satisfied. Optionally, the eighth determining module 1140 may be configured to perform operation S640 described in fig. 6, for example, and is not described herein again.
A ninth determining module 1150, configured to determine the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times if the re-addressing condition is met. Optionally, the ninth determining module 1150 may be configured to perform operation S650 described in fig. 6, for example, and is not described herein again.
A third executing module 1160, configured to repeatedly execute the sending step and the determining step with the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, so as to return the processing result of the first proxy terminal and the processing result of the second proxy terminal to the designated terminal. Optionally, the third executing module 1160 may be used to execute operation S660 described in fig. 6, for example, and is not described herein again.
As an alternative embodiment, the eighth determining module 1140 may be configured to determine that the re-addressing condition is satisfied when the second sub-request and the global request frame skipping number are failed to be transmitted and the global request frame skipping number is not exhausted.
As an alternative embodiment, the eighth determining module 1140 may be configured to determine that the re-addressing condition is not satisfied when the second sub-request and the global request frame skipping times are successfully transmitted; and/or determining that the aforementioned re-addressing condition is not satisfied in the case that the aforementioned global request frame skipping number has been exhausted.
As an alternative embodiment, the eighth determining module 1140 may be further configured to return the processing result of the first agent terminal to the designated terminal if the second agent terminal does not exist.
It should be noted that the implementation, solved technical problems, realized functions, and achieved technical effects of each module and each sub-module in the apparatus part embodiment are respectively the same as or similar to the implementation, solved technical problems, realized functions, and achieved technical effects of each corresponding step in the method part embodiment, and are not described herein again.
Any number of modules, sub-modules, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules and sub-modules according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a field programmable gate array (FNGA), a programmable logic array (NLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging the circuit, or in any one of three implementations, or in any suitable combination of any of the software, hardware and firmware. Alternatively, one or more of the modules, sub-modules according to embodiments of the disclosure may be implemented at least partly as computer program modules, which when executed may perform corresponding functions.
For example, the first determining module 910, the first transmitting module 920, the second determining module 930, the third determining module 940 and the first executing module 950, the first receiving module 1010, the fourth determining module 1020, the second transmitting module 1030, the fifth determining module 1040, the sixth determining module 1050 and the second executing module 1060, the second receiving module 1110, the seventh determining module 1120, the third transmitting module 1130, the eighth determining module 1140, the ninth determining module 1150 and the third executing module 1160 may be combined to be implemented in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first determining module 910, the first sending module 920, the second determining module 930, the third determining module 940 and the first executing module 950, the first receiving module 1010, the fourth determining module 1020, the second sending module 1030, the fifth determining module 1040, the sixth determining module 1050 and the second executing module 1060, the second receiving module 1110, the seventh determining module 1120, the third sending module 1130, the eighth determining module 1140, the ninth determining module 1150 and the third executing module 1160 may be at least partially implemented as a hardware circuit, such as a field programmable gate array (FNGA), a programmable logic array (NLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or any other reasonable manner that can integrate or package a circuit, or in any one of three implementations, software, hardware and firmware, or in any suitable combination of any of them. Alternatively, at least one of the first determining module 910, the first transmitting module 920, the second determining module 930, the third determining module 940 and the first executing module 950, the first receiving module 1010, the fourth determining module 1020, the second transmitting module 1030, the fifth determining module 1040, the sixth determining module 1050 and the second executing module 1060, the second receiving module 1110, the seventh determining module 1120, the third transmitting module 1130, the eighth determining module 1140, the ninth determining module 1150 and the third executing module 1160 may be at least partially implemented as a computer program module, which when executed, may perform corresponding functions.
Fig. 12 schematically illustrates a schematic diagram of a computer-readable storage medium product adapted to implement the request processing method described above according to an embodiment of the present disclosure.
In some possible embodiments, aspects of the present invention may also be implemented in a form of a program product including program code for causing a device to perform the aforementioned operations (or steps) in the request processing method according to various exemplary embodiments of the present invention described in the above-mentioned "exemplary method" section of this specification when the program product is run on the device, for example, the electronic device may perform operations S410 to S450 as shown in fig. 4. The electronic device may also perform operations S510 through S560 as shown in fig. 5. The electronic device may also perform operations S610 through S660 as shown in fig. 6.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (ENROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
As shown in fig. 12, a program product 1200 for request processing according to an embodiment of the present invention is depicted, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a device, such as a personal computer. However, the program product of the present invention is not limited in this respect, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device.
A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, or device. Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAA) or a wide area network (WAA), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
Fig. 13 schematically shows a block diagram of an electronic device adapted to implement the request processing method described above according to an embodiment of the present disclosure. The electronic device shown in fig. 13 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 13, an electronic device 1300 according to an embodiment of the present disclosure includes a processor 1301 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1302 or a program loaded from a storage section 1308 into a Random Access Memory (RAM) 1303. Processor 1301 may include, for example, a general purpose microprocessor (e.g., a CNU), an instruction set processor and/or related chip sets and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1301 may also include onboard memory for caching purposes. Processor 1301 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the present disclosure.
In the RAM 1303, various programs and data necessary for the operation of the electronic apparatus 1300 are stored. The processor 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. The processor 1301 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 1302 and/or the RAM 1303. Note that the programs may also be stored in one or more memories other than the ROM 1302 and RAM 1303. The processor 1301 may also perform operations S410 to S450 illustrated in fig. 4 according to the embodiment of the present disclosure by executing the program stored in the one or more memories. The electronic device may also perform operations S510 through S560 as shown in fig. 5. The electronic device may also perform operations S610 through S660 as shown in fig. 6.
Electronic device 1300 may also include input/output (I/O) interface 1305, which is also connected to bus 1304, according to an embodiment of the present disclosure. The system 1300 may also include one or more of the following components connected to the I/O interface 1305: an input portion 1306 including a keyboard, a mouse, and the like; an output section 1307 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1308 including a hard disk and the like; and a communication section 1309 including a network interface card such as a LAA card, modem, or the like. The communication section 1309 performs communication processing via a network such as the internet. A drive 1310 is also connected to the I/O interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1310 as necessary, so that a computer program read out therefrom is mounted into the storage portion 1308 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via communications component 1309 and/or installed from removable media 1311. The computer program, when executed by the processor 1301, performs the functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement a request processing method according to an embodiment of the present disclosure, including operations S410 to S450 shown in fig. 4. The electronic device may also perform operations S510 through S560 as shown in fig. 5. The electronic device may also perform operations S610 through S660 as shown in fig. 6.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (ENROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include one or more memories other than the ROM 1302 and/or the RAM 1303 and/or the ROM 1302 and the RAM 1303 described above.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (20)

1. A request processing method is applied to a client and comprises the following steps:
responding to a request sent to a designated terminal, and determining the global request frame skipping number, wherein the global request frame skipping number is the sum of the request frame skipping number allowed by the designated terminal and the request frame skipping number allowed by a proxy terminal addressed to the designated terminal;
sending the request and the global request frame skipping times to the designated terminal;
determining whether a re-addressing condition is satisfied;
if the readdressing condition is met, determining the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times;
and repeatedly executing the sending step and the determining step by taking the new request frame skipping times as global request frame skipping times until the re-addressing condition is not met, so that the appointed terminal sends the request and the global request frame skipping times to the proxy terminal to obtain a response result.
2. The method of claim 1, wherein the determining a global request frame skip number comprises at least one of:
determining a global request frame skip number based on a request attribute of the request,
the request attribute comprises at least one attribute of a request mode, request content and request timeliness;
determining the frame skipping times of the global request based on the terminal attribute of the specified terminal;
determining a global request frame skipping number based on a terminal attribute of the proxy terminal,
wherein the terminal attribute includes at least one attribute of a device parameter, an operation state, and an available number.
3. The method of claim 1, wherein the determining whether a re-addressing condition is satisfied comprises:
determining that the re-addressing condition is satisfied if the request and the global request frame skipping number are failed to send and the global request frame skipping number is not exhausted.
4. The method of claim 1, wherein the determining whether a re-addressing condition is satisfied comprises:
determining that the re-addressing condition is not met under the condition that the request and the global request frame skipping times are successfully sent; and/or
Determining that the re-addressing condition is not satisfied in a case that the global request frame skipping number has been exhausted.
5. The method of claim 4, wherein the method further comprises:
and terminating the request sent to the specified terminal under the condition that the global request frame skipping times are exhausted.
6. A request processing method is applied to a designated terminal and comprises the following steps:
receiving a request sent by a client and the frame skipping times of the global request;
determining a proxy terminal for processing the request based on the request;
sending a processing request and the global request frame skipping times to the proxy terminal;
determining whether a re-addressing condition is satisfied;
if the readdressing condition is met, determining the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times;
and repeatedly executing the sending step and the determining step by taking the new request frame skipping times as global request frame skipping times until the re-addressing condition is not met, so as to receive the processing result of the proxy terminal and return a response result to the client based on the processing result.
7. The method of claim 6, wherein the determining whether a re-addressing condition is satisfied comprises:
determining that the re-addressing condition is satisfied if the processing request and the global request frame skipping number transmission fail and the global request frame skipping number is not exhausted.
8. The method of claim 6, wherein the determining whether a re-addressing condition is satisfied comprises:
determining that the re-addressing condition is not met under the condition that the processing request and the global request frame skipping times are successfully sent; and/or
Determining that the re-addressing condition is not satisfied in a case that the global request frame skipping number has been exhausted.
9. The method of claim 8, wherein the method further comprises:
and terminating the sending of the processing request to the proxy terminal under the condition that the global request frame skipping times are exhausted.
10. The method of claim 7, wherein the agent terminal includes a first agent terminal for processing a first sub-request and a second agent terminal for processing a second sub-request, the second agent terminal being a subordinate terminal of the first agent terminal, and the transmitting the processing request and the global request frame skip number to the agent terminal includes:
and sending the first sub-request and the global request frame skipping times to the first proxy terminal, and enabling the first proxy terminal to send the second sub-request and the global request frame skipping times to the second proxy terminal under the condition that the first sub-request and the global request frame skipping times are successfully sent.
11. The method of claim 10, wherein the method further comprises:
and under the condition that the first sub-request and the global request frame skipping times are failed to be sent and the global request frame skipping times are exhausted, stopping sending the second sub-request to the second proxy terminal.
12. A request processing method is applied to a first agent terminal and comprises the following steps:
receiving a processing request and a global request frame skipping number sent by a designated terminal;
determining whether a second proxy terminal exists or not based on the processing request, wherein the first proxy terminal is used for processing a first sub-request, the second proxy terminal is used for processing a second sub-request, and the second proxy terminal is a lower terminal of the first proxy terminal;
if the second agent terminal exists, sending the second sub-request and the global request frame skipping times to the second agent terminal;
determining whether a re-addressing condition is satisfied;
if the readdressing condition is met, determining the global request frame skipping times minus the actually consumed request frame skipping times as new request frame skipping times;
and repeatedly executing the sending step and the determining step by taking the new request frame skipping times as global request frame skipping times until the re-addressing condition is not met, so as to return the processing result of the first proxy terminal and the processing result of the second proxy terminal to the designated terminal.
13. The method of claim 12, wherein the determining whether a re-addressing condition is satisfied comprises:
and determining that the re-addressing condition is met under the condition that the second sub-request and the global request frame skipping times are failed to send and the global request frame skipping times are not exhausted.
14. The method of claim 12, wherein the determining whether a re-addressing condition is satisfied comprises:
determining that the readdressing condition is not met under the condition that the second sub-request and the global request frame skipping times are successfully sent; and/or
Determining that the re-addressing condition is not satisfied in a case that the global request frame skipping number has been exhausted.
15. The method of claim 12, wherein the method further comprises:
and if the second agent terminal does not exist, returning the processing result of the first agent terminal to the appointed terminal.
16. A request processing device applied to a client comprises:
a first determining module, configured to determine a global request frame skipping number in response to a request sent to a designated terminal, where the global request frame skipping number is a sum of a request frame skipping number allowed by a proxy terminal addressed to the designated terminal and a request frame skipping number allowed by the proxy terminal addressed to the designated terminal;
a first sending module, configured to send the request and the global request frame skipping number to the designated terminal;
a second determining module for determining whether a re-addressing condition is satisfied;
a third determining module, configured to determine, if the readdressing condition is satisfied, a new request frame skipping number by subtracting an actually consumed request frame skipping number from the global request frame skipping number;
a first executing module, configured to repeatedly execute the sending step and the determining step with the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, so that the designated terminal sends the request and the global request frame skipping number to the proxy terminal, so as to obtain a response result.
17. A request processing device applied to a designated terminal comprises:
the first receiving module is used for receiving a request sent by a client and the frame skipping times of the global request;
a fourth determining module, configured to determine, based on the request, a proxy terminal for processing the request;
a second sending module, configured to send a processing request and the global request frame skipping number to the proxy terminal;
a fifth determining module for determining whether a re-addressing condition is satisfied;
a sixth determining module, configured to determine, if the readdressing condition is satisfied, a new request frame skipping number by subtracting an actually consumed request frame skipping number from the global request frame skipping number;
and a second execution module, configured to repeatedly execute the sending step and the determining step with the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, to receive a processing result of the proxy terminal, and return a response result to the client based on the processing result.
18. A request processing device applied to a first agent terminal comprises:
the second receiving module is used for receiving a processing request and the global request frame skipping times sent by the appointed terminal;
a seventh determining module, configured to determine whether a second proxy terminal exists based on the processing request, where the first proxy terminal is configured to process a first sub-request, the second proxy terminal is configured to process a second sub-request, and the second proxy terminal is a lower-level terminal of the first proxy terminal;
a third sending module, configured to send the second sub-request and the global request frame skipping number to the second proxy terminal if the second proxy terminal exists;
an eighth determining module for determining whether a re-addressing condition is satisfied;
a ninth determining module, configured to determine, if the readdressing condition is satisfied, a new request frame skipping number by subtracting an actually consumed request frame skipping number from the global request frame skipping number;
a third executing module, configured to repeatedly execute the sending step and the determining step with the new request frame skipping number as a global request frame skipping number until the re-addressing condition is not satisfied, so as to return the processing result of the first proxy terminal and the processing result of the second proxy terminal to the designated terminal.
19. An electronic device, comprising:
one or more processors; and
a memory for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-15.
20. A computer-readable storage medium storing computer-executable instructions for implementing the method of any one of claims 1 to 15 when executed.
CN202010937692.8A 2020-09-08 2020-09-08 Request processing method and device, electronic equipment and medium Active CN112055083B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010937692.8A CN112055083B (en) 2020-09-08 2020-09-08 Request processing method and device, electronic equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010937692.8A CN112055083B (en) 2020-09-08 2020-09-08 Request processing method and device, electronic equipment and medium

Publications (2)

Publication Number Publication Date
CN112055083A true CN112055083A (en) 2020-12-08
CN112055083B CN112055083B (en) 2022-06-10

Family

ID=73611513

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010937692.8A Active CN112055083B (en) 2020-09-08 2020-09-08 Request processing method and device, electronic equipment and medium

Country Status (1)

Country Link
CN (1) CN112055083B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070110050A1 (en) * 2005-11-16 2007-05-17 Cable Television Laboratories, Inc. Method and system of determining last hop device addresses
CN101281214A (en) * 2007-04-02 2008-10-08 深圳市国电科技通信有限公司 Remote meter reading system heart-throb frame real-time detection method
CN101674320A (en) * 2008-09-12 2010-03-17 阿里巴巴集团控股有限公司 Service addressing method and device in cluster environment
CN102497309A (en) * 2011-12-02 2012-06-13 杭州华三通信技术有限公司 Label distribution protocol (LDP) remote neighbor configuration method and equipment thereof
CN107509226A (en) * 2016-06-14 2017-12-22 屈银翔 A kind of route addressing method and device that there is selection to transmit
CN110557336A (en) * 2019-09-17 2019-12-10 中国人民解放军战略支援部队信息工程大学 Addressing routing method and system
CN111416888A (en) * 2020-04-07 2020-07-14 中国建设银行股份有限公司 Addressing method and device based on service gateway

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070110050A1 (en) * 2005-11-16 2007-05-17 Cable Television Laboratories, Inc. Method and system of determining last hop device addresses
CN101281214A (en) * 2007-04-02 2008-10-08 深圳市国电科技通信有限公司 Remote meter reading system heart-throb frame real-time detection method
CN101674320A (en) * 2008-09-12 2010-03-17 阿里巴巴集团控股有限公司 Service addressing method and device in cluster environment
CN102497309A (en) * 2011-12-02 2012-06-13 杭州华三通信技术有限公司 Label distribution protocol (LDP) remote neighbor configuration method and equipment thereof
CN107509226A (en) * 2016-06-14 2017-12-22 屈银翔 A kind of route addressing method and device that there is selection to transmit
CN110557336A (en) * 2019-09-17 2019-12-10 中国人民解放军战略支援部队信息工程大学 Addressing routing method and system
CN111416888A (en) * 2020-04-07 2020-07-14 中国建设银行股份有限公司 Addressing method and device based on service gateway

Also Published As

Publication number Publication date
CN112055083B (en) 2022-06-10

Similar Documents

Publication Publication Date Title
KR102514250B1 (en) Method, Apparatus and System for Selecting a Mobile Edge Computing Node
US10659354B2 (en) Processing data packets using a policy based network path
CN109067914B (en) web service proxy method, device, equipment and storage medium
KR102519409B1 (en) Method and Apparatus for Multipath Media Delivery
EP2629466B1 (en) Method, device and system for forwarding data in communication system
US6661780B2 (en) Mechanisms for policy based UMTS QoS and IP QoS management in mobile IP networks
US10826830B2 (en) Congestion processing method, host, and system
US8402132B2 (en) Method, system and device for device capabilities exchange
US20100274922A1 (en) System and method for managing long lived connections from a plurality of applications running on a wireless device
WO2023000940A1 (en) Data processing method and apparatus, and network element device, storage medium and program product
US20160241664A1 (en) Method, device, and system for redirecting data by using service proxy
US20210160311A1 (en) Load balancing method and apparatus
KR20160041444A (en) Method for controlling transmission path for providing server-push service in heterogenous network environment and device
CN102904959A (en) Network accelerating method and gateway
CN107222561A (en) A kind of transport layer reverse proxy method
US20150127837A1 (en) Relay apparatus and data transfer method
US11489810B2 (en) Intelligently routing a response packet along a same connection as a request packet
CN111629030A (en) Communication processing method, device, medium and equipment based on edge computing platform
WO2023000936A1 (en) Data processing method, function device and readable storage medium
US10136375B2 (en) Method for service data management, apparatus, and system
CN112055083B (en) Request processing method and device, electronic equipment and medium
CN111726400A (en) Reverse connection method, device and server-side system
CN112087510B (en) Request processing method, device, electronic equipment and medium
WO2011026355A1 (en) Method for a node accessing a home agent, home agent cluster system and service router
CN111866100A (en) Method, device and system for controlling data transmission rate

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right

Effective date of registration: 20210118

Address after: 100140, 55, Fuxing Avenue, Xicheng District, Beijing

Applicant after: INDUSTRIAL AND COMMERCIAL BANK OF CHINA

Applicant after: ICBC Technology Co.,Ltd.

Address before: 071700 unit 111, 1st floor, building C, enterprise office area, xiong'an Civic Service Center, Rongcheng County, xiong'an District, China (Hebei) pilot Free Trade Zone, Hebei Province

Applicant before: ICBC Technology Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant