Link tracking method, device, equipment and computer-readable storage medium
By implementing the link tracking method between the server and the UE, intercepting and analyzing abnormal user requests, the problem of inefficient manual inspection in the prior art is solved, and efficient bug positioning and optimization are achieved.
Patent Information
- Application Number
- CN202011241842.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-09
- Publication Date
- 2025-02-28
- Estimated Expiration
- 2040-11-09
Smart Images

Figure CN114461511B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and in particular to a link tracking method, apparatus, device, and computer-readable storage medium. Background Art
[0002] An app has a debugging phase during its development process, or after it is put on the app store and released to the market. The development company debugs the app to detect whether the app's functions can meet the preset requirements and the defects (bugs) in the app, and makes corresponding optimizations.
[0003] Nowadays, most applications on user equipment (UE) involve server-side service support, such as typical social applications, information applications, map applications, game applications, etc. The local UE initiates corresponding user requests to the server, such as data query requests or data update requests, and the server then processes the data in response to the received user requests and can feedback the response results.
[0004] In the course of studying the existing related technologies, the inventors found that during the debugging of an application, if certain functional points of the application do not respond normally when initiating user requests to the server, the debugging tool may display an error prompt to remind the staff to check. In this case, the staff is required to conduct a careful inspection to check what anomalies exist in the response of the functional point to the user request. Obviously, this method that relies on manual inspection has the problem of low inspection efficiency. Summary of the invention
[0005] The present application provides a link tracking method, apparatus, device and computer-readable storage medium for effectively reducing the data scale of link tracking processing and reducing data processing costs. It is particularly suitable for debugging and processing of applications, so that staff can directly locate and optimize bugs based on tracking data, significantly improving inspection efficiency.
[0006] In a first aspect, the present application provides a link tracking method, the method comprising:
[0007] The server receives an interception request initiated by the UE, wherein the interception request is used to request the server to intercept a target user request initiated by the UE, where the target user request is a user request confirmed by the UE as an abnormal request;
[0008] The server intercepts the target user request and performs link tracking processing on the target user request, wherein the link tracking processing is used to track the initiation track of the target user request;
[0009] The server stores the tracking data obtained by link tracking processing.
[0010] In combination with the first aspect of the present application, in a first possible implementation manner of the first aspect of the present application, after the server stores the tracking data obtained by the link tracking process, the method further includes:
[0011] The server analyzes the request characteristics of the abnormal user request based on the tracking data and the historical tracking data obtained by link tracking the historical user requests, wherein the historical user requests include multiple user requests determined to be abnormal requests;
[0012] The server sends the request characteristics of the abnormal user request to the UE, so that the UE confirms whether the newly initiated user request is an abnormal request according to the request characteristics of the abnormal user request.
[0013] In combination with the first aspect of the present application, in a second possible implementation manner of the first aspect of the present application, the target user request is a user request initiated by the application to be debugged in the UE, and the application to be debugged is an application of the application performance to be debugged.
[0014] In a second aspect, the present application provides another link tracking method, the method comprising:
[0015] The UE initiates a user request to the server based on the trigger of the user operation;
[0016] The UE confirms whether the user request is an abnormal request;
[0017] If so, the UE initiates an interception request to the server, wherein the interception request is used to request the server to intercept the user request, and the interception request is also used to instruct the server to perform link tracking processing on the user request, and the link tracking processing is used to track the initiation track of the user request.
[0018] In combination with the second aspect of the present application, in a first possible implementation manner of the second aspect of the present application, after the UE initiates an interception request to the server, the method further includes:
[0019] The UE receives a request feature of an abnormal user request sent by the server, wherein the request feature of the abnormal user request is a feature obtained by analyzing tracking data obtained by the server according to link tracking processing of the user request and historical tracking data obtained by link tracking processing of historical user requests, and the historical user request includes multiple user requests determined to be abnormal requests;
[0020] The UE configures the request characteristics of the abnormal user request to confirm whether the newly initiated user request is an abnormal request according to the request characteristics of the abnormal user request.
[0021] In combination with the second aspect of the present application, in a second possible implementation manner of the second aspect of the present application, the user request is initiated by the application to be debugged in the user request UE, and the application to be debugged is an application with application performance to be debugged.
[0022] In a third aspect, the present application provides a link tracking device, the device comprising:
[0023] A receiving unit, configured to receive an interception request initiated by a UE, wherein the interception request is used to request a server to intercept a target user request initiated by the UE, where the target user request is a user request confirmed by the UE as an abnormal request;
[0024] An interception unit, used to intercept target user requests;
[0025] A tracking unit, used to perform link tracking processing on the target user request, wherein the link tracking processing is used to track the initiation track of the target user request;
[0026] The storage unit is used to store the tracking data obtained by the link tracking process.
[0027] In conjunction with the third aspect of the present application, in a first possible implementation manner of the third aspect of the present application, the device further includes an analyzing unit, which is used to:
[0028] Analyze and obtain request features of abnormal user requests based on the tracking data and the historical tracking data obtained by link tracking of historical user requests, wherein the historical user requests include multiple user requests determined to be abnormal requests;
[0029] The device also includes a sending unit, which is used to:
[0030] The request characteristics of the abnormal user request are sent to the UE, so that the UE confirms whether the newly initiated user request is an abnormal request according to the request characteristics of the abnormal user request.
[0031] In combination with the third aspect of the present application, in a second possible implementation manner of the third aspect of the present application, the target user request is a user request initiated by the application to be debugged in the UE, and the application to be debugged is an application of the application performance to be debugged.
[0032] In a fourth aspect, the present application provides another link tracking device, the device comprising:
[0033] A sending unit, used to initiate a user request to a server according to a trigger of a user operation;
[0034] A confirmation unit, used to confirm whether the user request is an abnormal request, and then trigger the transceiver unit;
[0035] The sending unit is also used to initiate an interception request to the server, wherein the interception request is used to request the server to intercept the user request, and the interception request is also used to instruct the server to perform link tracking processing on the user request, and the link tracking processing is used to track the initiation trajectory of the user request.
[0036] In conjunction with the fourth aspect of the present application, in a first possible implementation manner of the fourth aspect of the present application, the device further includes a receiving unit, which is used to:
[0037] Receive request features of abnormal user requests sent by the server, wherein the request features of the abnormal user requests are tracking data obtained by the server according to link tracking processing of user requests and historical tracking data obtained by link tracking processing of historical user requests, and features obtained by analyzing, and the historical user requests include multiple user requests determined to be abnormal requests;
[0038] The device also includes a configuration unit, configured to:
[0039] Configure the request characteristics of abnormal user requests to confirm whether a newly initiated user request is an abnormal request based on the request characteristics of the abnormal user requests.
[0040] In combination with the fourth aspect of the present application, in a second possible implementation manner of the fourth aspect of the present application, the user request is initiated by the application to be debugged in the user request UE, and the application to be debugged is an application with performance of the application to be debugged.
[0041] In a fifth aspect, the present application also provides a link tracking device, including a processor and a memory, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, it executes the steps in the first aspect of the present application, any possible implementation method of the first aspect of the present application, the second aspect of the present application, or any possible implementation method of the second aspect of the present application.
[0042] In a sixth aspect, the present application also provides a computer-readable storage medium, which stores multiple instructions, and the instructions are suitable for a processor to load to execute the steps in the first aspect of the present application, any possible implementation method of the first aspect of the present application, the second aspect of the present application, or any possible implementation method of the second aspect of the present application.
[0043] From the above content, it can be concluded that the present application has the following beneficial effects:
[0044] For the link tracking scenario, the present application determines whether the user request is an abnormal request by the UE that initiates the user request locally. When it is determined to be an abnormal request, the server intercepts the user request and performs link tracking processing on the user request based on the triggering of the interception request initiated by the UE, obtains and stores the tracking data obtained by the link tracking processing. In this process, since the link tracking processing is only performed on the user request determined to be an abnormal request, the link tracking service provided by the present application can effectively reduce the data scale of the link tracking processing and reduce the data processing cost. It is particularly suitable for the debugging processing of the application, so that the staff can directly locate and optimize the bug according to the tracking data, which significantly improves the inspection efficiency.
[0045] Secondly, since the user request for link tracking processing is triggered after the UE locally determines it as an abnormal request, this is also suitable for the UE to monitor the user request locally. In the entire link tracking mechanism, the determination of whether the user request is an abnormal request is handed over to the UE that initiates the request, which can also effectively disperse the data processing cost required for the determination process, and the UE itself can also achieve a lower monitoring cost by monitoring, further avoiding the load required for monitoring by the server. The staff can also easily intervene through the UE and flexibly participate in the link tracking process. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] Figure 1 A flowchart of the link tracking method of the present application;
[0047] Figure 2 This is another flowchart of the link tracking method of the present application;
[0048] Figure 3 A schematic diagram of a scenario of the link tracking method of this application;
[0049] Figure 4 A schematic diagram of the structure of the link tracking device of the present application;
[0050] Figure 5 This is another structural schematic diagram of the link tracking device of the present application;
[0051] Figure 6 A structural schematic diagram of the link tracking device of this application. DETAILED DESCRIPTION
[0052] First of all, before introducing this application, let me first introduce the relevant content of this application regarding the application background.
[0053] The link tracking method, device and computer-readable storage medium provided in the present application can be applied to link tracking equipment to effectively reduce the data scale of link tracking processing and reduce data processing costs. It is particularly suitable for application debugging processing, so that staff can directly locate and optimize bugs based on tracking data, significantly improving inspection efficiency.
[0054] The link tracking method mentioned in the present application may be executed by a link tracking device, or a link tracking equipment integrated with the device. The link tracking equipment may specifically be a UE or a server. The link tracking device may be implemented in hardware or software. The server may specifically be set up in the form of a server cluster.
[0055] Next, we will introduce the link tracking method provided by this application.
[0056] First, see Figure 1 , Figure 1 A flow chart of the link tracking method of the present application is shown from the server side. The link tracking method provided by the present application may specifically include the following steps:
[0057] Step S101, the server receives an interception request initiated by the UE, wherein the interception request is used to request the server to intercept a target user request initiated by the UE, and the target user request is a user request confirmed by the UE as an abnormal request;
[0058] Step S102, the server intercepts the target user request and performs a link tracking process on the target user request, wherein the link tracking process is used to track the initiation track of the target user request;
[0059] Step S103: The server stores the tracking data obtained by the link tracking process.
[0060] Next, see Figure 2 Another flowchart of the link tracking method of the present application is shown from the UE side. The link tracking method provided by the present application may also specifically include the following steps:
[0061] Step S201, the UE initiates a user request to the server according to the trigger of the user operation;
[0062] Step S201, the UE confirms whether the user request is an abnormal request, and if so, triggers step S203;
[0063] In step S203, the UE initiates an interception request to the server, wherein the interception request is used to request the server to intercept the user request, and the interception request is also used to instruct the server to perform link tracking processing on the user request, and the link tracking processing is used to track the initiation track of the user request.
[0064] From the above Figure 1 as well as Figure 2 It can be seen from the illustrated embodiment that, for the link tracking scenario, the present application determines whether the user request is an abnormal request by the UE that locally initiates the user request. When it is determined to be an abnormal request, the server intercepts the user request and performs link tracking processing on the user request based on the triggering of the interception request initiated by the UE, obtains and stores the tracking data obtained by the link tracking processing. In this process, since the link tracking processing is only performed on the user request determined to be an abnormal request, the link tracking service provided by the present application can effectively reduce the data scale of the link tracking processing, reduce the data processing cost, and is particularly suitable for the debugging processing of the application, so that the staff can directly locate and optimize the bug according to the tracking data, significantly improving the inspection efficiency;
[0065] Secondly, since the user request for link tracking processing is triggered after the UE locally determines it as an abnormal request, this is also suitable for the UE to monitor the user request locally. In the entire link tracking mechanism, the determination of whether the user request is an abnormal request is handed over to the UE that initiates the request, which can also effectively disperse the data processing cost required for the determination process, and the UE itself can also achieve a lower monitoring cost by monitoring, further avoiding the load required for monitoring by the server. The staff can also easily intervene through the UE and flexibly participate in the link tracking process.
[0066] The following is a detailed introduction to the above Figure 1 as well as Figure 2 The illustrated embodiments include the steps and specific implementation methods that may be used for the steps in practical applications.
[0067] In the present application, UE may specifically be a terminal device such as a smart phone, a tablet computer, a laptop computer, a PDA, a desktop computer, or a personal digital assistant (PDA).
[0068] Taking the application debugging scenario as an example, during the application debugging process, the UE is often required to install or call the application to be debugged and initiate a series of user requests to the server. The debugging application refers to the application of the application performance to be debugged. These user requests may be data query requests or data update requests and other types of user requests. The server needs to perform corresponding response processing based on the received user requests, such as feedback of data query results or data update results to the UE, and complete the response to a user request.
[0069] During this process, the staff can collect information related to the response results and response status of the user requests to determine whether the user request can get an effective response. If the user request initiated by a certain functional point of the application cannot get an effective response, it is obvious that there is a bug somewhere in the functional point.
[0070] However, in the existing related technologies, the method of relying on manual inspection obviously has the problem of low inspection efficiency. Therefore, this application proposes a new inspection idea, or a link tracking method, which can enable the bug inspection and optimization of the application to be carried out efficiently.
[0071] Of course, the link tracking method provided in this application can be applied not only to the debugging scenario of the application, but also to the normal use scenario of the application. In other words, the UE side can be not only the debugger of the application, but also the user of the application, that is, the normal user of the UE.
[0072] The application type may be a news application type, a social application type, a game application type, or other different application types, and the specific application types may be adjusted according to actual needs.
[0073] For example, taking the house viewing application type as an example, this type of application can display the real estate in the form of 2D image display, 3D image display or panoramic image display, and can also adjust the display method or display position according to user operation. Furthermore, it can also have functions such as booking and purchasing houses.
[0074] When the UE initiates a user request or after initiating a user request, it can determine whether the user request is an abnormal request. Taking the house viewing application as an example, it can obtain the latest property information of certain properties online under the user's touch operation, that is, query the application server for the latest property information of certain properties. In this query scenario, the house viewing application should interact with the application server normally and output the latest property information queried by the application server to the user. If the latest property information queried is not output normally, it is obvious that the query function point of the latest property information must have some bugs, such as network anomalies, query request generation anomalies, inability to parse the latest property information sent by the application server, the content of the latest property information is empty, the latest property information is garbled, and other abnormal situations. Obviously, it is contrary to the original intention of the development of this function point, and it is impossible to realize normal functions and provide normal query services to users.
[0075] In this case, after the UE determines that the user request is an abnormal request, it can report an interception request to the application server, requesting to intercept the corresponding user request.
[0076] In the link tracking mechanism provided in the present application, when the application server receives an interception request initiated by the UE, it can intercept the user request targeted by the interception request and perform link tracking processing on the user request.
[0077] Intercepting a user request may specifically refer to stopping or freezing the response processing of the user request, or restoring the response processing of the user request, etc., which may have an impact on intercepting the user request.
[0078] The link tracking process is used to track the initiation track of the user request, or in other words, to track the logical track of the user request. Specifically, it can be understood as recording the initiation of the user request from the UE end, the forwarding of the user request to the response of the user request. The tracking data obtained by the link tracking process can clearly restore the initiation track of the user request. The data can identify the devices involved in the entire initiation track process and the data processing of the devices, which can be specifically reflected in the request path, request parameters, error data and other data.
[0079] In this way, when the interception request initiated by the UE is triggered and the link tracking processing is performed on the target user request to obtain the tracking data, the developer of the house viewing application can view the initiation track of the target application request based on the tracking data stored in the server, and determine which links have bugs. After locating these bugs, the bugs can be corrected and optimized quickly, so that the subsequent house viewing application and / or application server can process the user request normally, and the user can obtain the normal house viewing service that the house viewing application originally expected to provide.
[0080] Specifically, the link tracking process may track the user request from a file such as a UE or server log that records relevant information of the user request, and capture and summarize the tracked data to form tracking data obtained from the link tracking process.
[0081] In actual applications, link tracking is performed by running an application program independent of the house viewing application locally on the UE and the server to avoid interference of the normal program of the house viewing application with the link tracking program. Alternatively, the link tracking program can be implanted into the house viewing application and link tracking can be performed based on the trigger from within the house viewing application.
[0082] Specifically, the specific tracking strategy of link tracking can be adjusted according to different influencing factors such as user requests, applications, UEs, servers, etc. For example, taking the application management level as an example, it can be divided into system operation and maintenance and application operation and maintenance. The system operation and maintenance aspect refers to the corresponding link tracking from the UE or server system itself, and the application operation and maintenance aspect refers to the corresponding link tracking from the UE's front-end application or the server's back-end application. Taking the business management level as an example, the corresponding link tracking can be performed from the business involved in the user request.
[0083] It should be understood that the link tracking process is to perform reasonable data processing under the security mechanism of the application, UE system or server system to complete the link tracking, which involves security authentication, user confirmation, program implantation and other processing, which will not be elaborated here.
[0084] In order to facilitate the UE side to accurately determine whether the user request is an abnormal request, in the present application, it can be implemented by the server based on the request characteristics of the user request confirmed as an abnormal request in the historical time period.
[0085] It can be understood that for different UEs or different applications of UEs, the abnormal user requests involved may have the same or similar request characteristics. On the server side, these request characteristics can be extracted and summarized to generate an analysis strategy for the user request, and then sent to the local UE to update the analysis strategy. In this way, the UE can determine whether the user request initiated by itself is an abnormal request based on the received analysis strategy (including the request characteristics of the abnormal user request).
[0086] For the tracking data obtained by link tracking processing, the server can add a link identifier to identify the link tracked by the local link tracking processing, and then it can not only be stored in its own local storage space, but also stored in the storage space of an external device. For example, it can be uploaded to a server that can provide cloud services. In this way, application developers can easily download tracking data directly from such servers suitable for data sharing to locate and optimize application bugs.
[0087] Among them, in the link tracking mechanism provided by the present application, the server can also analyze and obtain the request characteristics of the abnormal user request from the current tracking data (the tracking data obtained by link tracking the user request currently determined as an abnormal request) and the historical tracking data (the tracking data obtained by link tracking the user request historically determined as an abnormal request). In this way, it can play the role of real-time update, and the UE can determine whether the current user request is an abnormal request based on the request characteristics of the latest abnormal user request.
[0088] When it is determined that the current user request is an abnormal request, an interception request may be reported to the server to intercept the user request and trigger link tracking processing for the user request.
[0089] It can be understood that in the process of initiating a user request, the UE may determine that the user request is an abnormal request. At this time, the interception request can also be merged with the user request, or it can be understood that, based on the user request originally expected to be initiated, a response identifier is added to the relevant fields of the user request to identify the user request as an abnormal request determined by the UE.
[0090] Of course, in actual applications, the UE may also determine whether the user request is an abnormal request after initiating the user request. For example, in the analysis strategy, it may determine whether the user request is an abnormal request based on whether a response result of a normal user request is received.
[0091] In addition, it can be understood that in practical applications, the link tracking method provided by the present application may also have other optimization solutions. For example, the link tracking method provided by the present application can be implemented under the lightweight SpringBoot framework to reduce the program size and ensure operational efficiency.
[0092] To understand the above content, you can also refer to Figure 3 A scenario diagram of the link working method of the present application is shown, which is understood from an exemplary practical application scenario.
[0093] The above is an explanation of the link tracking method of the present application. In order to facilitate better implementation of the link tracking method provided by the present application, the present application also provides a link tracking device.
[0094] See also Figure 4 , Figure 4 A schematic diagram of the structure of the link tracking device of the present application is shown from the server side. In the present application, the link tracking device 400 may specifically include the following structure:
[0095] The receiving unit 401 is used to receive an interception request initiated by the UE, wherein the interception request is used to request the server to intercept a target user request initiated by the UE, and the target user request is a user request confirmed by the UE as an abnormal request;
[0096] An interception unit 402, used to intercept a target user request;
[0097] A tracking unit 403, configured to perform link tracking processing on the target user request, wherein the link tracking processing is used to track the initiation track of the target user request;
[0098] The storage unit 404 is used to store the tracking data obtained by the link tracking process.
[0099] In a possible implementation, the apparatus further includes an analyzing unit 405, configured to:
[0100] Analyze and obtain request features of abnormal user requests based on the tracking data and the historical tracking data obtained by link tracking of historical user requests, wherein the historical user requests include multiple user requests determined to be abnormal requests;
[0101] The apparatus further includes a sending unit 406, configured to:
[0102] The request characteristics of the abnormal user request are sent to the UE, so that the UE confirms whether the newly initiated user request is an abnormal request according to the request characteristics of the abnormal user request.
[0103] In yet another possible implementation, the target user request is a user request initiated by an application to be debugged in the UE, and the application to be debugged is an application of the application performance to be debugged.
[0104] Continue reading Figure 5 , Figure 5Another structural schematic diagram of the link tracking device of the present application is shown from the UE side. In the present application, the link tracking device 500 may further include the following structure:
[0105] The sending unit 501 is used to initiate a user request to the server according to the trigger of the user operation;
[0106] A confirmation unit 502, used to confirm whether the user request is an abnormal request, and then trigger the transceiver unit;
[0107] The sending unit 501 is also used to initiate an interception request to the server, wherein the interception request is used to request the server to intercept the user request, and the interception request is also used to instruct the server to perform link tracking processing on the user request, and the link tracking processing is used to track the initiation track of the user request.
[0108] In a possible implementation, the apparatus further includes a receiving unit 503, configured to:
[0109] Receive request features of abnormal user requests sent by the server, wherein the request features of the abnormal user requests are tracking data obtained by the server according to link tracking processing of user requests and historical tracking data obtained by link tracking processing of historical user requests, and features obtained by analyzing, and the historical user requests include multiple user requests determined to be abnormal requests;
[0110] The apparatus further comprises a configuration unit 504, configured to:
[0111] Configure the request characteristics of abnormal user requests to confirm whether a newly initiated user request is an abnormal request based on the request characteristics of the abnormal user requests.
[0112] In yet another possible implementation, the user request is initiated by an application to be debugged in the user request UE, and the application to be debugged is an application with application performance to be debugged.
[0113] This application also provides a link tracking device, see Figure 6 , Figure 6 A schematic diagram of the structure of the link tracking device of the present application is shown. The link tracking device of the present application can be a server or a UE. The link tracking device includes a processor 601, a memory 602, and an input and output device 603. The processor 601 is used to execute the computer program stored in the memory 602 to implement the following Figures 1 to 3 Corresponding to each step of the link tracking method in any embodiment; or, the processor 601 is used to execute the computer program stored in the memory 602 to implement the following Figure 4 or Figure 5 The functions of each unit in the corresponding embodiment, such as Figure 4 or Figure 5The hardware structure corresponding to the transceiver unit is the input and output device 603, the hardware structure corresponding to the processing unit is the processor 601, and the memory 602 is used to store the processor 601 to execute the above Figures 1 to 3 A computer program required for the link tracking method in any embodiment.
[0114] Exemplarily, the computer program may be divided into one or more modules / units, one or more modules / units are stored in the memory 602, and executed by the processor 601 to complete the present application. One or more modules / units may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the computer device.
[0115] The link tracking device may include, but is not limited to, a processor 601, a memory 602, and an input / output device 603. Those skilled in the art will appreciate that the illustration is merely an example of a link tracking device and does not constitute a limitation on the link tracking device. The link tracking device may include more or fewer components than shown in the illustration, or may combine certain components, or may include different components. For example, the link tracking device may also include a network access device, a bus, etc. The processor 601, the memory 602, the input / output device 603, and the network access device are connected via a bus.
[0116] The processor 601 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the link tracking device, and uses various interfaces and lines to connect various parts of the entire device.
[0117] The memory 602 can be used to store computer programs and / or modules. The processor 601 implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory 602 and calling the data stored in the memory 602. The memory 602 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function, etc.; the data storage area can store data created according to the use of the link tracking device, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.
[0118] When the processor 601 is used to execute the computer program stored in the memory 602, the following functions can be implemented:
[0119] receiving an interception request initiated by the UE, wherein the interception request is used to request the server to intercept a target user request initiated by the UE, where the target user request is a user request confirmed by the UE as an abnormal request;
[0120] Intercepting the target user request and performing link tracking processing on the target user request, wherein the link tracking processing is used to track the initiation track of the target user request;
[0121] Stores the tracking data obtained by link tracking processing.
[0122] Alternatively, when the processor 601 is used to execute the computer program stored in the memory 602, the following functions may be implemented:
[0123] Initiate a user request to the server based on the trigger of the user operation;
[0124] Confirm whether the user request is an abnormal request, and then trigger the transceiver unit;
[0125] An interception request is initiated to the server, wherein the interception request is used to request the server to intercept the user request, and the interception request is also used to instruct the server to perform link tracking processing on the user request, and the link tracking processing is used to track the initiation trajectory of the user request.
[0126] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the link tracking device, equipment and its corresponding units described above can refer to the following. Figures 1 to 3 The description of the link tracking method in any embodiment will not be repeated here in detail.
[0127] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0128] To this end, the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the present application as follows: Figures 1 to 3 For the steps in the link tracking method in any embodiment, the specific operations can be referred to as follows: Figures 1 to 3 The description of the link tracking method in any embodiment will not be repeated here.
[0129] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0130] Due to the instructions stored in the computer-readable storage medium, the present application can be executed. Figures 1 to 3 Corresponding to the steps in the link tracking method in any embodiment, therefore, the present application can be implemented as follows Figures 1 to 3 The beneficial effects that can be achieved by the link tracking method in any embodiment are detailed in the previous description and will not be repeated here.
[0131] The link tracking method, device, equipment and computer-readable storage medium provided by the present application are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A link tracking method, characterized in that: The method comprises: The server receives an interception request initiated by a user equipment UE, wherein the interception request is used to request the server to intercept a target user request initiated by the UE, and the target user request is a user request confirmed by the UE as an abnormal request; The server intercepts the target user request and performs a link tracking process on the target user request, wherein the link tracking process is used to track the initiation track of the target user request; The server stores the tracking data obtained by the link tracking process; The server analyzes the request characteristics of abnormal user requests according to the tracking data and the historical tracking data obtained by performing the link tracking process on historical user requests, wherein the historical user requests include multiple user requests determined to be abnormal requests; The server sends the request feature of the abnormal user request to the UE, so that the UE confirms whether the newly initiated user request is an abnormal request according to the request feature of the abnormal user request.
2. The method according to claim 1, characterized in that The target user request is a user request initiated by the application to be debugged in the UE, and the application to be debugged is an application with application performance to be debugged.
3. A link tracking method, characterized in that: The method comprises: The user equipment UE initiates a user request to the server according to the trigger of the user operation; The UE confirms whether the user request is an abnormal request; If yes, the UE initiates an interception request to the server, wherein the interception request is used to request the server to intercept the user request, and the interception request is also used to instruct the server to perform a link tracking process on the user request, and the link tracking process is used to track the initiation track of the user request; The UE receives a request feature of an abnormal user request sent by the server, wherein the request feature of the abnormal user request is a feature obtained by analyzing tracking data obtained by the server according to link tracking processing of the user request and historical tracking data obtained by performing the link tracking processing on historical user requests, and the historical user request includes multiple user requests determined to be abnormal requests; The UE configures the request feature of the abnormal user request to confirm whether the newly initiated user request is an abnormal request according to the request feature of the abnormal user request.
4. The method according to claim 3, characterized in that The user request is a user request initiated by the application to be debugged in the UE, and the application to be debugged is an application with application performance to be debugged.
5. A link tracking device, characterized in that: The device comprises: A receiving unit, configured to receive an interception request initiated by a user equipment UE, wherein the interception request is used to request a server to intercept a target user request initiated by the UE, and the target user request is a user request confirmed by the UE as an abnormal request; An interception unit, used to intercept the target user request; A tracking unit, configured to perform a link tracking process on the target user request, wherein the link tracking process is used to track the initiation track of the target user request; A storage unit, used to store the tracking data obtained by the link tracking process; an analyzing unit, configured to analyze and obtain request characteristics of abnormal user requests according to the tracking data and the historical tracking data obtained by performing the link tracking processing on historical user requests, wherein the historical user requests include a plurality of user requests determined to be abnormal requests; The sending unit is used to send the request characteristics of the abnormal user request to the UE, so that the UE confirms whether the newly initiated user request is an abnormal request according to the request characteristics of the abnormal user request.
6. A link tracking device, characterized in that: The device comprises: A sending unit, used to initiate a user request to a server according to a trigger of a user operation; a confirmation unit, used to confirm whether the user request is an abnormal request, and then trigger the sending unit; The sending unit is further used to initiate an interception request to the server, wherein the interception request is used to request the server to intercept the user request, and the interception request is also used to instruct the server to perform a link tracking process on the user request, and the link tracking process is used to track the initiation track of the user request; a receiving unit, configured to receive a request feature of an abnormal user request sent by the server, wherein the request feature of the abnormal user request is a feature obtained by analyzing tracking data obtained by the server according to link tracking processing of the user request and historical tracking data obtained by performing the link tracking processing on historical user requests, wherein the historical user request includes multiple user requests determined to be abnormal requests; The configuration unit is used to configure the request characteristics of the abnormal user request, so as to confirm whether the newly initiated user request is an abnormal request according to the request characteristics of the abnormal user request.
7. A link tracking device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program, and the processor executes the method according to any one of claims 1 to 4 when calling the computer program in the memory.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the method according to any one of claims 1 to 4.
Citation Information
Patent Citations
Link tracking method and device, terminal and storage medium
CN109831351A