WO2022105116A1

WO2022105116A1 - High-frequency request processing method and apparatus, electronic device and storage medium

Info

Publication number: WO2022105116A1
Application number: PCT/CN2021/090354
Authority: WO
Inventors: 柴瑞雪
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-11-17
Filing date: 2021-04-27
Publication date: 2022-05-27
Also published as: CN112416583A

Abstract

The present application relates to data processing, and provides a high-frequency request processing method and apparatus, an electronic device and a storage medium. The method is capable of determining a trigger terminal and a trigger user of a trigger request; obtaining a request log from the trigger terminal, and extracting target log information from the request log according to the trigger user; analyzing the target log information to determine a request type of the trigger request; when the request type is high-frequency request, creating a request stack according to the target log information, and writing the trigger request into the request stack; when the request stack is a full stack, merging all element requests in the request stack to obtain a target request; and sending the target request to a preset server for processing, so as to obtain a response result. The present application is capable of smoothly displaying a page view, while also ensuring the completeness of the request data. In addition, the present application also relates to blockchain technology, and the response result may be stored in a blockchain.

Description

High-frequency request processing method, device, electronic device and storage medium

This application claims the priority of the Chinese patent application filed on November 17, 2020 with the application number 202011290509.6 and the invention title is "High-frequency request processing method, device, electronic device and storage medium", the entire content of which is approved by Reference is incorporated in this application.

technical field

The present application relates to the technical field of data processing, and in particular, to a high-frequency request processing method, device, electronic device, and storage medium.

Background technique

In the WEB front-end field, such as in Vue, React, Angular and other frameworks, high-frequency trigger requests in a short period of time can easily cause JS thread blocking, and also cause the view of page rendering to be stuck and unsmooth. For example, in the data visualization of Ant DataV, there are the following requirements: record the trajectory of the element dragged by the user and display it. However, this requirement needs to monitor the movement of the mouse. Every time the mouse moves, a corresponding trigger request is generated, and the page view is frequently changed. It is easy to cause problems such as page display freezes.

In order to prevent the page view from being stuck, an anti-shake or interception scheme is usually adopted at present. However, the inventor realizes that this method cannot store every triggered request, resulting in the loss of the request data, which is not conducive to the response of the request.

SUMMARY OF THE INVENTION

In view of the above content, it is necessary to provide a high-frequency request processing method, device, electronic device and storage medium, which can ensure the integrity of the requested data when the page view is displayed smoothly.

A first aspect of the present application provides a high-frequency request processing method, the high-frequency request processing method comprising:

When receiving the trigger request, determine the trigger terminal and trigger user of the trigger request;

Obtain a request log from the trigger terminal, and extract target log information from the request log according to the trigger user;

Analyze the target log information to determine the request type to which the trigger request belongs, where the request type includes high-frequency requests;

When the request type is the high-frequency request, create a request stack according to the target log information, and write the trigger request into the request stack;

When the request stack is full, merge all element requests in the request stack to obtain the target request;

The target request is sent to the preset server for processing, and a response result is obtained.

A second aspect of the present application provides an electronic device, the electronic device includes a processor and a memory, the processor is configured to execute at least one computer-readable instruction stored in the memory to implement the following steps:

A third aspect of the present application provides a computer-readable storage medium having at least one computer-readable instruction stored thereon, the at least one computer-readable instruction being executed by a processor to implement the following steps:

A fourth aspect of the present application provides a high-frequency request processing device, wherein the high-frequency request processing includes:

a determining unit, configured to determine a triggering terminal and a triggering user of the triggering request when a triggering request is received;

an extraction unit, configured to obtain a request log from the trigger terminal, and extract target log information from the request log according to the trigger user;

The determining unit is further configured to analyze the target log information to determine the request type to which the trigger request belongs, and the request type includes a high-frequency request;

A creation unit, configured to create a request stack according to the target log information when the request type is the high-frequency request, and write the trigger request into the request stack;

a merging unit for merging all element requests in the request stack to obtain a target request when the request stack is full;

A sending unit, configured to send the target request to a preset server for processing, and obtain a response result.

It can be seen from the above technical solutions that the present application can accurately determine the log information recording the trigger operation of the trigger user through the determined trigger terminal and the trigger user, because all the target log information is stored in the target log information. Therefore, by analyzing the target log information, it can be accurately determined whether the trigger request is a high-frequency request, and by writing the trigger request into the request stack, the trigger can be avoided. The request is lost, thereby ensuring the integrity of the request data. By combining all element requests in the request stack, the generated target request contains multiple requests, and then multiple requests are sent to the preset server at one time. Process to avoid thread blocking. When it is determined that the trigger request belongs to a high-frequency request, the present application combines a plurality of the trigger requests into the target request, and then sends the combined target request to the preset server for processing, so as to avoid The multiple trigger requests repeatedly trigger the preset server, thereby improving the performance of the preset server, thereby improving the reflow efficiency of the response result, and improving the smoothness of the page view. In addition, due to the triggering All trigger requests generated by the user participate in the response, so the integrity of the requested data can be ensured when the page view is displayed smoothly.

Description of drawings

FIG. 1 is a flowchart of a preferred embodiment of the high-frequency request processing method of the present application.

FIG. 2 is a flowchart of an embodiment of the present application for determining a trigger terminal and a trigger user.

FIG. 3 is a flowchart of an embodiment of the present application for determining the request type to which the trigger request belongs.

FIG. 4 is a flowchart of an embodiment of the present application for creating a request stack.

FIG. 5 is a functional block diagram of a preferred embodiment of the high-frequency request processing device of the present application.

FIG. 6 is a schematic structural diagram of an electronic device implementing a preferred embodiment of the high-frequency request processing method of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in detail below with reference to the accompanying drawings and specific embodiments.

As shown in FIG. 1 , it is a flowchart of a preferred embodiment of the high-frequency request processing method of the present application. According to different requirements, the order of steps in this flowchart can be changed, and some steps can be omitted.

The high-frequency request processing method is applied to one or more electronic devices, and the electronic device is a device that can automatically perform numerical calculation and/or information processing according to pre-set or stored computer-readable instructions. Hardware includes but is not limited to microprocessors, application specific integrated circuits (ASICs), programmable gate arrays (Field-Programmable Gate Arrays, FPGAs), digital processors (Digital Signal Processors, DSPs), embedded devices, etc. .

The electronic device can be any electronic product that can interact with the user, such as a personal computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a game console, an interactive network television ( Internet Protocol Television, IPTV), smart wearable devices, etc.

The electronic equipment may include network equipment and/or user equipment. Wherein, the network device includes, but is not limited to, a single network electronic device, an electronic device group composed of multiple network electronic devices, or a cloud composed of a large number of hosts or network electronic devices based on cloud computing (Cloud Computing).

The network where the electronic device is located includes, but is not limited to, the Internet, a wide area network, a metropolitan area network, a local area network, a virtual private network (Virtual Private Network, VPN), and the like.

S10, when a trigger request is received, determine a trigger terminal and a trigger user of the trigger request.

In at least one embodiment of the present application, the scene corresponding to the trigger request may be any scene, for example, the trigger request may be displaying a track of a user dragging an element. Further, the trigger request may be triggered and generated by any user.

The trigger terminal refers to the generation terminal of the trigger request, and the trigger terminal may be a mobile phone, a computer, a tablet, or the like.

The triggering user refers to a user who triggers the generation of the triggering request.

Referring to FIG. 2, FIG. 2 is a flowchart of an embodiment of the present application for determining a trigger terminal and a trigger user. In at least one embodiment of the present application, determining, by the electronic device, a triggering terminal and a triggering user of the triggering request include:

S100, parse the trigger request to obtain data information carried by the trigger request.

Wherein, the data information includes a trigger address and a user identification code.

S101. Acquire a first preset tag and a second preset tag from a configuration tag library, where the first preset tag is used to indicate an address, and the second preset tag is used to indicate a user.

Wherein, a plurality of pre-defined tags are stored in the configuration tag library.

S102: Acquire information corresponding to the first preset tag from the data information as a trigger address, and acquire information corresponding to the second preset tag from the data information as a user identification code.

S103: Determine the terminal corresponding to the trigger address as the trigger terminal, and determine the user corresponding to the user identification code as the trigger user.

The triggering address and then the triggering terminal can be accurately determined through the first preset label. Meanwhile, the user identification code can be accurately determined through the second preset label, and then the user identification code can be accurately determined through the second preset label. The triggering user is determined.

S11: Acquire a request log from the triggering terminal, and extract target log information from the request log according to the triggering user.

In at least one embodiment of the present application, the request log refers to an operation log recorded on the trigger terminal, and the request log records all operations on the trigger terminal.

The target log information refers to all operations of the triggering user on the triggering terminal.

In at least one embodiment of the present application, the electronic device acquiring the request log from the triggering terminal, and extracting target log information from the request log according to the triggering user includes:

Obtain the log storage path of the trigger terminal;

Obtain the request log of the trigger terminal from the log storage path;

The log information corresponding to the user identification code is selected from the request log as the target log information.

The request log can be quickly acquired through the log storage path, and the target log information can be accurately determined through the user identification code.

S12: Analyze the target log information to determine a request type to which the trigger request belongs, where the request type includes a high-frequency request.

In at least one embodiment of the present application, the request type further includes a low frequency request.

Referring to FIG. 3, FIG. 3 is a flowchart of an embodiment of the present application for determining the request type to which the trigger request belongs. In at least one embodiment of the present application, the electronic device analyzing the target log information to determine the request type to which the trigger request belongs includes:

S120: Acquire the response time of all historical requests in the target log information, and acquire the generation time of the trigger request from the target log information.

The response time refers to the time when each historical request completes the response, and the generation time refers to the time when the trigger request is triggered to be generated.

S121: Calculate a first time difference between each response time and the generation time, and determine a response time when the first time difference is less than a first preset value as a target time.

S122: Sort the target time and the generation time in ascending order to obtain a time queue.

S123: Calculate a second time difference between any adjacent times in the time queue, and calculate the number of times that the second time difference is smaller than a second preset value, where the second preset value is smaller than the first preset value .

The arbitrary adjacent times refers to any two times that are adjacent to the position on the time queue.

S124, when the number is greater than or equal to a configuration value, determine that the request type to which the trigger request belongs is the high-frequency request.

The value of the configuration value may be freely configured according to the application scenario, and the present application does not limit the value of the configuration value.

S125, when the number is less than the configured value, determine that the request type to which the trigger request belongs is a low frequency request.

By comparing each response time with the generation time, premature historical requests can be eliminated, preventing premature historical requests from affecting the determination of the request type, through the comparison of any adjacent time in the time queue, and any The determination of the number of times that the time difference between adjacent times is less than the second preset value can accurately determine the request type to which the trigger request belongs.

S13, when the request type is the high-frequency request, create a request stack according to the target log information, and write the trigger request into the request stack.

In at least one embodiment of the present application, the request stack is composed of multiple storage areas.

Referring to FIG. 4, FIG. 4 is a flowchart of an embodiment of the present application for creating a request stack. In at least one embodiment of the present application, the electronic device creating a request stack according to the target log information includes:

S130: Determine the time when the second time difference is smaller than the second preset value as the analysis time, and determine the earliest time and the latest time in the analysis time.

S131: Calculate the time difference between the latest time and the earliest time as a time interval, and divide the time interval by the number to obtain the requested access frequency.

The requested access frequency refers to the access frequency of requests whose response time ranges from the earliest time to the latest time.

S132: Acquire trigger times of all historical requests from the target log information, and calculate a time difference between each trigger time and each response time as a response time.

S133: Calculate the time sum of the response time, and calculate the request quantity of all the historical requests.

S134: Divide the total time by the number of requests to obtain an average time, and multiply the request access frequency by the average time to obtain the number of storage areas.

S135. Create the request stack according to the number of storage areas.

The number of storage areas in the request stack is the number of storage areas.

Through the determination of the analysis time and the determination of the number of times that the time difference between any adjacent time is less than the second preset value, it is possible to accurately determine the request access frequency of the triggering user, and then determine the average time according to historical requests, Therefore, the number of storage areas is determined based on the requested access frequency and the average time. Since both the requested access frequency and the average time are determined through historical requests, the The number of storage areas is based on actual application scenarios, thereby improving the practicability of the present application.

In at least one embodiment of the present application, the electronic device writing the trigger request into the request stack includes:

determining the location of the storage area where the stack pointer is located in the request stack;

Determining the next empty storage area at the storage area position as the target storage area;

Write the trigger request to the target storage area.

Through the above-mentioned implementation manner, since the target storage area refers to the next empty storage area where the stack pointer is located, it is possible to prevent the target storage area from including other requests, thereby ensuring that the target storage area can be written into the target storage area. Independence of the trigger request.

In at least one embodiment of the present application, by writing the trigger request into the request stack, the loss of the trigger request can be avoided, thereby ensuring the integrity of the request data.

S14, when the request stack is full, merge all element requests in the request stack to obtain a target request.

In at least one embodiment of the present application, the fact that the request stack is full indicates that there is no empty storage area in the request stack.

The target request carries all the packet contents in the all element requests.

In at least one embodiment of the present application, the electronic device combines all element requests in the request stack to obtain the target request including:

Extract the request parameters in each element request, and encapsulate the request parameters to obtain the method body;

Extract the header of any element request as the target header;

The method body and the target header are encapsulated to obtain the target request.

By directly extracting the header of any element request as the target header of the target request, the merging efficiency of the target request can be improved.

In at least one embodiment of the present application, by combining all element requests in the request stack, the generated target request includes multiple requests, and then the multiple requests are sent to the preset server at one time for processing , to avoid thread blocking.

S15: Send the target request to a preset server for processing, and obtain a response result.

It should be emphasized that, in order to further ensure the privacy and security of the above response results, the above response results can also be stored in a node of a blockchain.

In at least one embodiment of the present application, the preset server refers to a server corresponding to the destination address of the target request.

The response results include responses to multiple requests triggered by the user.

In at least one embodiment of the present application, after obtaining the response result, the method further includes:

Get the request number of each element request;

generating prompt information according to the request number and the response result;

Encrypt the prompt information with a symmetric encryption algorithm to obtain the target ciphertext;

Send the target ciphertext to the trigger terminal.

The prompt information is generated based on the request number requested by each element, so that the triggering user can grasp the response object of the response result. Encrypting the prompt information through a symmetric encryption algorithm can not only improve the encryption efficiency, but also avoid the prompt. The information is tampered with, which improves the security of the prompt information.

It can be seen from the above technical solutions that the present application can accurately determine the log information recording the trigger operation of the trigger user through the determined trigger terminal and the trigger user, because all the target log information is stored in the target log information. Therefore, by analyzing the target log information, it can be accurately determined whether the trigger request is a high-frequency request, and by writing the trigger request into the request stack, the trigger can be avoided. The request is lost, thereby ensuring the integrity of the request data. By combining all element requests in the request stack, the generated target request contains multiple requests, and then multiple requests are sent to the preset server at one time. Process to avoid thread blocking. When it is determined that the trigger request belongs to a high-frequency request, the present application combines a plurality of the trigger requests into the target request, and then sends the combined target request to the preset server for processing, so as to avoid The multiple trigger requests repeatedly trigger the preset server, thereby improving the performance of the preset server, thereby improving the reflow efficiency of the response results, and improving the smoothness of the page view. In addition, due to the triggering All trigger requests generated by the user participate in the response, so the integrity of the requested data can be ensured when the page view is displayed smoothly.

As shown in FIG. 5 , it is a functional block diagram of a preferred embodiment of the high-frequency request processing device of the present application. The high-frequency request processing device 11 includes a determining unit 110 , an extracting unit 111 , a creating unit 112 , a merging unit 113 , a sending unit 114 , an obtaining unit 115 , a generating unit 116 and an encryption unit 117 . The module/unit referred to in this application refers to a series of computer-readable instruction segments that can be acquired by the processor 13 and can perform fixed functions, and are stored in the memory 12 . In this embodiment, the functions of each module/unit will be described in detail in subsequent embodiments.

When receiving the trigger request, the determining unit 110 determines the trigger terminal and trigger user of the trigger request.

In at least one embodiment of the present application, the determining unit 110 determines the triggering terminal and the triggering user of the triggering request include:

Parse the trigger request to obtain data information carried by the trigger request.

A first preset tag and a second preset tag are obtained from a configuration tag library, where the first preset tag is used to indicate an address, and the second preset tag is used to indicate a user.

The information corresponding to the first preset tag is acquired from the data information as a trigger address, and the information corresponding to the second preset tag is acquired from the data information as a user identification code.

A terminal corresponding to the trigger address is determined as the trigger terminal, and a user corresponding to the user identification code is determined as the trigger user.

The extracting unit 111 acquires the request log from the trigger terminal, and extracts target log information from the request log according to the trigger user.

In at least one embodiment of the present application, the extracting unit 111 acquires the request log from the trigger terminal, and extracts target log information from the request log according to the trigger user, including:

Obtain the log storage path of the trigger terminal;

Obtain the request log of the trigger terminal from the log storage path;

The determining unit 110 analyzes the target log information to determine a request type to which the trigger request belongs, where the request type includes a high-frequency request.

In at least one embodiment of the present application, the determining unit 110 analyzes the target log information to determine the request type to which the trigger request belongs:

Acquire the response time of all historical requests in the target log information, and obtain the generation time of the trigger request from the target log information.

A first time difference between each response time and the generation time is calculated, and a response time when the first time difference is less than a first preset value is determined as a target time.

Sort the target time and the generation time in ascending order to obtain a time queue.

Calculate a second time difference between any adjacent times in the time queue, and calculate the number of times that the second time difference is smaller than a second preset value, where the second preset value is smaller than the first preset value.

When the number is greater than or equal to the configuration value, it is determined that the request type to which the trigger request belongs is the high-frequency request.

When the number is less than the configured value, it is determined that the request type to which the trigger request belongs is a low frequency request.

When the request type is the high-frequency request, the creating unit 112 creates a request stack according to the target log information, and writes the trigger request into the request stack.

In at least one embodiment of the present application, the creating unit 112 creating a request stack according to the target log information includes:

The time when the second time difference is smaller than the second preset value is determined as the analysis time, and the earliest time and the latest time in the analysis time are determined.

The time difference between the latest time and the earliest time is calculated as a time interval, and the time interval is divided by the quantity to obtain the requested access frequency.

The trigger times of all historical requests are obtained from the target log information, and the time difference between each trigger time and each response time is calculated as the response time.

Calculate the time sum of the response times, and calculate the number of requests for all historical requests.

The average time is obtained by dividing the sum of the times by the number of requests, and the number of storage areas is obtained by multiplying the request access frequency by the average time.

The request stack is created according to the number of storage areas.

In at least one embodiment of the present application, the creation unit 112 writing the trigger request into the request stack includes:

Write the trigger request to the target storage area.

When the request stack is full, the merging unit 113 merges all element requests in the request stack to obtain the target request.

The target request carries all the packet contents in the all element requests.

In at least one embodiment of the present application, the merging unit 113 merges all element requests in the request stack to obtain the target request including:

Extract the header of any element request as the target header;

The sending unit 114 sends the target request to the preset server for processing, and obtains a response result.

In at least one embodiment of the present application, after obtaining the response result, the obtaining unit 115 obtains the request number of each element request;

The generating unit 116 generates prompt information according to the request number and the response result;

The encryption unit 117 uses a symmetric encryption algorithm to encrypt the prompt information to obtain the target ciphertext;

The sending unit 114 sends the target ciphertext to the trigger terminal.

As shown in FIG. 6 , it is a schematic structural diagram of an electronic device implementing a preferred embodiment of the high-frequency request processing method of the present application.

In one embodiment of the present application, the electronic device 1 includes, but is not limited to, a memory 12 , a processor 13 , and computer-readable instructions stored in the memory 12 and executable on the processor 13 , such as high-frequency request handlers.

Those skilled in the art can understand that the schematic diagram is only an example of the electronic device 1, and does not constitute a limitation on the electronic device 1, and may include more or less components than the one shown, or combine some components, or different Components, for example, the electronic device 1 may also include input and output devices, network access devices, buses, and the like.

The processor 13 may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The processor 13 is the computing core and control center of the electronic device 1, and uses various interfaces and lines to connect the entire electronic device. 1, and the operating system that executes the electronic device 1, as well as various installed applications, program codes, and the like.

Exemplarily, the computer-readable instructions may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 12 and executed by the processor 13 to Complete this application. The one or more modules/units may be a series of computer-readable instruction segments capable of accomplishing specific functions, and the computer-readable instruction segments are used to describe the execution process of the computer-readable instructions in the electronic device 1 . For example, the computer readable instructions may be divided into a determination unit 110 , an extraction unit 111 , a creation unit 112 , a merge unit 113 , a transmission unit 114 , an acquisition unit 115 , a generation unit 116 , and an encryption unit 117 .

The memory 12 can be used to store the computer-readable instructions and/or modules, and the processor 13 executes or executes the computer-readable instructions and/or modules stored in the memory 12 and invokes the computer-readable instructions and/or modules stored in the memory 12. The data in the electronic device 1 realizes various functions of the electronic device 1 . The memory 12 may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), and the like; the storage data area may Data and the like created according to the use of the electronic device are stored. The memory 12 may include non-volatile and volatile memory such as: hard disk, internal memory, plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, Flash memory card (Flash Card), at least one disk storage device, flash memory device, or other storage device.

The memory 12 may be an external memory and/or an internal memory of the electronic device 1 . Further, the storage 12 may be a storage in physical form, such as a memory stick, a TF card (Trans-flash Card) and the like.

If the modules/units integrated in the electronic device 1 are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium, and the computer-readable storage medium may be a non-volatile storage medium. Volatile, can also be volatile. Based on this understanding, the present application can implement all or part of the processes in the methods of the above embodiments, and can also be completed by instructing relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. The computer-readable instructions, when executed by the processor, can implement the steps of the above-mentioned method embodiments.

Wherein, the computer-readable instructions include computer-readable instruction codes, and the computer-readable instruction codes may be in source code form, object code form, executable file, or some intermediate form, and the like. The computer-readable medium may include: any entity or device capable of carrying the computer-readable instruction code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only). Memory), random access memory (RAM, Random Access Memory).

The blockchain referred to in this application is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain, essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

1 , the memory 12 in the electronic device 1 stores computer-readable instructions to implement a high-frequency request processing method, and the processor 13 can execute the computer-readable instructions to implement:

Specifically, for the specific implementation method of the computer-readable instruction by the processor 13, reference may be made to the description of the relevant steps in the embodiment corresponding to FIG. 1 , which is not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the modules is only a logical function division, and there may be other division manners in actual implementation.

The computer-readable storage medium stores computer-readable instructions, wherein the computer-readable instructions are used to implement the following steps when executed by the processor 13:

The modules described as separate components may or may not be physically separated, and components shown as modules may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional module in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or can be implemented in the form of hardware plus software function modules.

Accordingly, the embodiments are to be regarded in all respects as illustrative and not restrictive, and the scope of the application is to be defined by the appended claims rather than the foregoing description, which is therefore intended to fall within the scope of the claims. All changes within the meaning and scope of the equivalents of , are included in this application. Any reference signs in the claims shall not be construed as limiting the involved claim.

Furthermore, it is clear that the word "comprising" does not exclude other units or steps and the singular does not exclude the plural. The multiple units or devices described may also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to denote names and do not denote any particular order.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application rather than limitations. Although the present application has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present application can be Modifications or equivalent substitutions can be made without departing from the spirit and scope of the technical solutions of the present application.

Claims

A high-frequency request processing method, wherein the high-frequency request processing method includes:

When receiving the trigger request, determine the trigger terminal and trigger user of the trigger request;

Obtain a request log from the trigger terminal, and extract target log information from the request log according to the trigger user;

Analyze the target log information to determine the request type to which the trigger request belongs, where the request type includes high-frequency requests;

When the request type is the high-frequency request, create a request stack according to the target log information, and write the trigger request into the request stack;

When the request stack is full, merge all element requests in the request stack to obtain the target request;

The target request is sent to the preset server for processing, and a response result is obtained.
The high-frequency request processing method according to claim 1, wherein the determining the triggering terminal and triggering user of the triggering request comprises:

Parsing the trigger request to obtain data information carried by the trigger request;

Obtain a first preset tag and a second preset tag from a configuration tag library, where the first preset tag is used to indicate an address, and the second preset tag is used to indicate a user;

Obtain information corresponding to the first preset tag from the data information as a trigger address, and obtain information corresponding to the second preset tag from the data information as a user identification code;

A terminal corresponding to the trigger address is determined as the trigger terminal, and a user corresponding to the user identification code is determined as the trigger user.
The high-frequency request processing method according to claim 2, wherein the obtaining the request log from the triggering terminal, and extracting target log information from the request log according to the triggering user comprises:

Obtain the log storage path of the trigger terminal;

Obtain the request log of the trigger terminal from the log storage path;

The log information corresponding to the user identification code is selected from the request log as the target log information.
The high-frequency request processing method according to claim 1, wherein the analyzing the target log information to determine the request type to which the trigger request belongs comprises:

Obtain the response time of all historical requests in the target log information, and obtain the generation time of the trigger request from the target log information;

Calculate the first time difference between each response time and the generation time, and determine the response time when the first time difference is less than the first preset value as the target time;

Sorting the target time and the generation time in ascending order to obtain a time queue;

Calculate the second time difference of any adjacent time in the time queue, and calculate the number of the second time difference less than a second preset value, wherein the second preset value is less than the first preset value;

When the number is greater than or equal to the configuration value, determine that the request type to which the trigger request belongs is the high-frequency request; or

When the number is less than the configured value, it is determined that the request type to which the trigger request belongs is a low frequency request.
The high-frequency request processing method according to claim 4, wherein the creating a request stack according to the target log information comprises:

determining the time when the second time difference is less than the second preset value as the analysis time, and determining the earliest time and the latest time in the analysis time;

Calculate the time difference between the latest time and the earliest time as a time interval, and divide the time interval by the number to obtain the requested access frequency;

Obtain the trigger times of all historical requests from the target log information, and calculate the time difference between each trigger time and each response time as the response time;

Calculate the time sum of the response times, and calculate the number of requests for all historical requests;

Divide the sum of the time by the number of requests to obtain the average time, and multiply the request access frequency by the average time to obtain the number of storage areas;

The request stack is created according to the number of storage areas.
The high-frequency request processing method according to claim 1, wherein the writing the trigger request into the request stack comprises:

determining the location of the storage area where the stack pointer is located in the request stack;

Determining the next empty storage area at the storage area position as the target storage area;

Write the trigger request to the target storage area.
The high-frequency request processing method according to claim 1, wherein the combining all element requests in the request stack to obtain the target request comprises:

Extract the request parameters in each element request, and encapsulate the request parameters to obtain the method body;

Extract the header of any element request as the target header;

The method body and the target header are encapsulated to obtain the target request.
A high-frequency request processing device, wherein the high-frequency request processing device includes:

a determining unit, configured to determine a triggering terminal and a triggering user of the triggering request when a triggering request is received;

an extraction unit, configured to obtain a request log from the trigger terminal, and extract target log information from the request log according to the trigger user;

The determining unit is further configured to analyze the target log information to determine the request type to which the trigger request belongs, and the request type includes a high-frequency request;

A creation unit, configured to create a request stack according to the target log information when the request type is the high-frequency request, and write the trigger request into the request stack;

a merging unit for merging all element requests in the request stack to obtain a target request when the request stack is full;

A sending unit, configured to send the target request to a preset server for processing, and obtain a response result.
An electronic device, wherein the electronic device includes a processor and a memory, and the processor is configured to execute at least one computer-readable instruction stored in the memory to implement the following steps:

When receiving the trigger request, determine the trigger terminal and trigger user of the trigger request;

Obtain a request log from the trigger terminal, and extract target log information from the request log according to the trigger user;

Analyze the target log information to determine the request type to which the trigger request belongs, where the request type includes high-frequency requests;

When the request type is the high-frequency request, create a request stack according to the target log information, and write the trigger request into the request stack;

When the request stack is full, merge all element requests in the request stack to obtain the target request;

The target request is sent to the preset server for processing, and a response result is obtained.
The electronic device according to claim 9, wherein, when the trigger terminal and trigger user of the trigger request are determined, the processor executes the at least one computer-readable instruction to implement the following steps:

Parsing the trigger request to obtain data information carried by the trigger request;

Obtain a first preset tag and a second preset tag from a configuration tag library, where the first preset tag is used to indicate an address, and the second preset tag is used to indicate a user;

Obtain information corresponding to the first preset tag from the data information as a trigger address, and obtain information corresponding to the second preset tag from the data information as a user identification code;

A terminal corresponding to the trigger address is determined as the trigger terminal, and a user corresponding to the user identification code is determined as the trigger user.
The electronic device according to claim 10, wherein when the request log is obtained from the trigger terminal, and the target log information is extracted from the request log according to the trigger user, the processor executes the At least one computer readable instruction to implement the following steps:

Obtain the log storage path of the trigger terminal;

Obtain the request log of the trigger terminal from the log storage path;

The log information corresponding to the user identification code is selected from the request log as the target log information.
The electronic device according to claim 9, wherein, when the analysis of the target log information determines the request type to which the trigger request belongs, the processor executes the at least one computer-readable instruction to implement the following steps:

Obtain the response time of all historical requests in the target log information, and obtain the generation time of the trigger request from the target log information;

Calculate the first time difference between each response time and the generation time, and determine the response time when the first time difference is less than the first preset value as the target time;

Sorting the target time and the generation time in ascending order to obtain a time queue;

Calculate the second time difference of any adjacent time in the time queue, and calculate the number of the second time difference less than a second preset value, wherein the second preset value is less than the first preset value;

When the number is greater than or equal to the configuration value, determine that the request type to which the trigger request belongs is the high-frequency request; or

When the number is less than the configured value, it is determined that the request type to which the trigger request belongs is a low frequency request.
The electronic device of claim 12, wherein, when the request stack is created according to the target log information, the processor executes the at least one computer-readable instruction to implement the following steps:

determining the time when the second time difference is less than the second preset value as the analysis time, and determining the earliest time and the latest time in the analysis time;

Calculate the time difference between the latest time and the earliest time as a time interval, and divide the time interval by the number to obtain the requested access frequency;

Obtain the trigger times of all historical requests from the target log information, and calculate the time difference between each trigger time and each response time as the response time;

Calculate the time sum of the response times, and calculate the number of requests for all historical requests;

Divide the sum of the time by the number of requests to obtain the average time, and multiply the request access frequency by the average time to obtain the number of storage areas;

The request stack is created according to the number of storage areas.
9. The electronic device of claim 9, wherein, upon writing the trigger request into the request stack, the processor executes the at least one computer-readable instruction to:

determining the location of the storage area where the stack pointer is located in the request stack;

Determining the next empty storage area at the storage area position as the target storage area;

Write the trigger request to the target storage area.
A computer-readable storage medium, wherein the computer-readable storage medium stores at least one computer-readable instruction, and the at least one computer-readable instruction implements the following steps when executed by a processor:

When receiving the trigger request, determine the trigger terminal and trigger user of the trigger request;

Obtain a request log from the trigger terminal, and extract target log information from the request log according to the trigger user;

Analyze the target log information to determine the request type to which the trigger request belongs, where the request type includes high-frequency requests;

When the request type is the high-frequency request, create a request stack according to the target log information, and write the trigger request into the request stack;

When the request stack is full, merge all element requests in the request stack to obtain the target request;

The target request is sent to the preset server for processing, and a response result is obtained.
The storage medium according to claim 15, wherein, when the triggering terminal and triggering user of the triggering request are determined, the at least one computer-readable instruction is executed by a processor to implement the following steps:

Parsing the trigger request to obtain data information carried by the trigger request;

Obtain a first preset tag and a second preset tag from a configuration tag library, where the first preset tag is used to indicate an address, and the second preset tag is used to indicate a user;

Obtain information corresponding to the first preset tag from the data information as a trigger address, and obtain information corresponding to the second preset tag from the data information as a user identification code;

A terminal corresponding to the trigger address is determined as the trigger terminal, and a user corresponding to the user identification code is determined as the trigger user.
The storage medium according to claim 16, wherein when the request log is obtained from the trigger terminal, and the target log information is extracted from the request log according to the trigger user, the at least one computer is readable The instructions are executed by the processor to implement the following steps:

Obtain the log storage path of the trigger terminal;

Obtain the request log of the trigger terminal from the log storage path;

The log information corresponding to the user identification code is selected from the request log as the target log information.
The storage medium of claim 15, wherein, when the analyzing the target log information determines the request type to which the trigger request belongs, the at least one computer-readable instruction is executed by the processor to implement the following steps:

Obtain the response time of all historical requests in the target log information, and obtain the generation time of the trigger request from the target log information;

Calculate the first time difference between each response time and the generation time, and determine the response time when the first time difference is less than the first preset value as the target time;

Sorting the target time and the generation time in ascending order to obtain a time queue;

Calculate the second time difference of any adjacent time in the time queue, and calculate the number of the second time difference less than a second preset value, wherein the second preset value is less than the first preset value;

When the number is greater than or equal to the configuration value, determine that the request type to which the trigger request belongs is the high-frequency request; or

When the number is less than the configured value, it is determined that the request type to which the trigger request belongs is a low frequency request.
The storage medium of claim 18, wherein, when the request stack is created according to the target log information, the at least one computer-readable instruction is executed by the processor to implement the following steps:

determining the time when the second time difference is less than the second preset value as the analysis time, and determining the earliest time and the latest time in the analysis time;

Calculate the time difference between the latest time and the earliest time as a time interval, and divide the time interval by the number to obtain the requested access frequency;

Obtain the trigger times of all historical requests from the target log information, and calculate the time difference between each trigger time and each response time as the response time;

Calculate the time sum of the response times, and calculate the number of requests for all historical requests;

Divide the sum of the time by the number of requests to obtain the average time, and multiply the request access frequency by the average time to obtain the number of storage areas;

The request stack is created according to the number of storage areas.
16. The storage medium of claim 15, wherein, upon writing the trigger request into the request stack, the at least one computer-readable instruction is executed by a processor to:

determining the location of the storage area where the stack pointer is located in the request stack;

Determining the next empty storage area at the storage area position as the target storage area;

Write the trigger request to the target storage area.