Method and device for processing information in terminal

Abstract

The embodiments of the present disclosure disclose a method and device for processing information for a terminal. A specific implementation of the method includes: triggering a tracking point pre-set for a target client; obtaining a tracking point log generated after the tracking point is triggered from the target client; analyzing the obtained tracking point log to obtain an analysis result for characterizing the performance of the target client. In this implementation, after the tracking point log is generated by the client, the terminal analyzes the tracking point log, thereby obtaining the analysis result more quickly, which helps to improve the timeliness of information processing.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and more particularly, to a method and apparatus for processing information in a terminal. Background Art

[0002] Tracking is a logging solution used to record specific characteristics of specific events. Currently, tracking is commonly performed on client applications to determine their performance. For example, a tracking point can be set up for a client application to record page load duration, where the page load is the event recorded by the tracking point, and the duration is the time characteristic.

[0003] Currently, after the client application obtains the tracking log through tracking, it will report the tracking log to the client application's backend server so that the backend server can analyze the tracking log to obtain analysis results used to characterize the performance of the client application, such as the page loading time. Summary of the Invention

[0004] Embodiments of the present disclosure provide a method and apparatus for processing information in a terminal.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for processing information for a terminal, the method comprising: triggering a burrowing point pre-set for a target client; obtaining a burrowing point log generated after the burrowing point is triggered from the target client; analyzing the obtained burrowing point log to obtain an analysis result for characterizing the performance of the target client.

[0006] In some embodiments, before analyzing the acquired burial point logs to obtain analysis results for characterizing the performance of the target client, the method also includes: filtering the acquired burial point logs; and analyzing the acquired burial point logs to obtain analysis results for characterizing the performance of the target client includes: analyzing the filtered burial point logs to obtain analysis results for characterizing the performance of the target client.

[0007] In some embodiments, triggering the pre-set tracking points for the target client includes: using a pre-installed test script for testing the performance of the target client to trigger the pre-set tracking points for the target client.

[0008] In some embodiments, analyzing the acquired tracking logs to obtain analysis results for characterizing the performance of the target client includes: using a preset analysis script to analyze the acquired tracking logs to obtain analysis results for characterizing the performance of the target client.

[0009] In some embodiments, obtaining the burying point log generated after the burying point is triggered from the target client includes: obtaining the burying point log generated after the burying point is triggered from the target client through a pre-installed hook.

[0010] In the second aspect, an embodiment of the present disclosure provides a device for processing information of a terminal, which device includes: a triggering unit, configured to trigger a burrowing point pre-set for a target client; an acquisition unit, configured to acquire a burrowing point log generated after the burrowing point is triggered from the target client; and an analysis unit, configured to analyze the acquired burrowing point log to obtain an analysis result for characterizing the performance of the target client.

[0011] In some embodiments, the device further includes: a screening unit configured to screen the acquired tracking logs; and the analysis unit is further configured to analyze the screened tracking logs to obtain analysis results for characterizing the performance of the target client.

[0012] In some embodiments, the trigger unit is further configured to: utilize a pre-installed test script for testing the performance of the target client to trigger the pre-set tracking points for the target client.

[0013] In some embodiments, the analysis unit is further configured to: analyze the acquired tracking logs using a preset analysis script to obtain analysis results for characterizing the performance of the target client.

[0014] In some embodiments, the acquisition unit is further configured to: acquire, from the target client through a pre-installed hook, the tracking point log generated after the tracking point is triggered.

[0015] In a third aspect, an embodiment of the present disclosure provides a terminal comprising: one or more processors; a storage device storing one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement the method of any embodiment of the above-mentioned method for processing information for a terminal.

[0016] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method of any embodiment of the above-mentioned method for processing information for a terminal.

[0017] The method and apparatus for processing information on a terminal provided by the embodiments of the present disclosure triggers a pre-set tracking point for a target client, then obtains a tracking point log generated from the target client after the tracking point is triggered, and finally analyzes the obtained tracking point log to obtain an analysis result used to characterize the performance of the target client. This allows the terminal to analyze the tracking point log after the tracking point log is generated on the client. Compared to the prior art solution of analyzing tracking point logs by a remote server, the embodiments of the present disclosure can obtain analysis results more quickly, which helps to improve the timeliness of information processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Other features, objects and advantages of the present disclosure will become more apparent from a reading of the detailed description of non-limiting embodiments made with reference to the following drawings:

[0019] Figure 1 is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;

[0020] Figure 2 is a flowchart of an embodiment of a method for processing information for a terminal according to the present disclosure;

[0021] Figure 3 is a schematic diagram of an application scenario of a method for processing information for a terminal according to an embodiment of the present disclosure;

[0022] Figure 4 is a flowchart of another embodiment of a method for processing information for a terminal according to the present disclosure;

[0023] Figure 5 is a structural diagram of an embodiment of an apparatus for processing information in a terminal according to the present disclosure;

[0024] Figure 6 It is a structural diagram of a computer system of a terminal device suitable for implementing an embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] The present disclosure will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are intended only to illustrate the relevant invention and are not intended to limit the invention. It should also be noted that, for ease of description, only portions relevant to the relevant invention are shown in the accompanying drawings.

[0026] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0027] Figure 1An exemplary system architecture 100 is shown to which an embodiment of a method for processing information of a terminal or an apparatus for processing information of a terminal of the present disclosure may be applied.

[0028] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. Network 104 is a medium for providing communication links between terminal devices 101, 102, 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0029] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various client applications can be installed on terminal devices 101, 102, and 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0030] Terminal devices 101, 102, 103 can be hardware or software. When terminal devices 101, 102, 103 are hardware, they can be various electronic devices, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, Moving Picture Experts Group Audio Layer 3), MP4 (Moving Picture Experts Group Audio Layer IV, Moving Picture Experts Group Audio Layer 4) players, laptop computers and desktop computers, etc. When terminal devices 101, 102, 103 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, multiple software or software modules used to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0031] The server 105 may be a server providing various services, such as a backend server of a client installed on the terminal devices 101, 102, and 103. The backend server may analyze and process requests initiated by the terminal devices using the client, and feed back the processing results to the terminal devices.

[0032] It should be noted that the method for processing information for a terminal provided in the embodiments of the present disclosure is generally executed by the terminal devices 101 , 102 , and 103 . Accordingly, the apparatus for processing information for a terminal is generally provided in the terminal devices 101 , 102 , and 103 .

[0033] It should be noted that the server can be either hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the server is software, it can be implemented as multiple software or software modules (e.g., multiple software or software modules used to provide distributed services), or as a single software or software module. No specific limitations are given here.

[0034] It should be understood that Figure 1 The number of terminal devices, networks, and servers described is merely illustrative. Any number of terminal devices, networks, and servers may be provided as needed. If the data used in generating analysis results characterizing the performance of the target client does not need to be acquired remotely, the system architecture described above may include only terminal devices, omitting the network and servers.

[0035] Continue to refer Figure 2 , shows a process 200 of an embodiment of a method for processing information for a terminal according to the present disclosure. The method for processing information includes the following steps:

[0036] Step 201: trigger the pre-set tracking point for the target client.

[0037] In this embodiment, the execution subject of the method for processing information of the terminal (for example Figure 1 The terminal device shown in FIG. 1 may trigger a pre-set tracking point for a target client in various ways. The target client may be a client whose performance is to be determined. The target client may be pre-installed on the execution entity. Specifically, the target client may be various types of client applications, such as a communication client application, a shopping client application, and the like.

[0038] In practice, after completing client application development, technicians typically set up tracking points for the client application. Tracking points can record performance-related data generated during user use of the client application, allowing optimization of client application performance based on this data. For example, technicians can set up tracking points to record page load time or the number of control failures on a page.

[0039] Specifically, technicians can encapsulate tracking points into a set of programs. Then, the client only needs to pass specific business parameters (such as pageType, actionType) and extended parameters to this set of programs to implement tracking points.

[0040] It is understood that when the event recorded by the tracking point occurs, the tracking point will be triggered. Therefore, in this embodiment, the execution subject can trigger the tracking point corresponding to the target client by executing the operation used to generate the event recorded by the tracking point.

[0041] Specifically, as an example, the execution entity may execute an operation for triggering tracking under the user's instruction. For example, a user may click on the target client's icon. Upon detecting the user clicking on the target client's icon, the execution entity may execute an operation for loading the target client's homepage, thereby triggering a tracking point for recording the loading time of the target client's homepage.

[0042] In some optional implementations of this embodiment, the execution entity may also utilize a pre-installed test script for testing the performance of the target client to trigger a tracking point pre-set for the target client. The test script may simulate a user operation, such as a user clicking on an icon of the target client. After running the test script, the execution entity may then, under the instruction of the test script, perform the operation for triggering the tracking point.

[0043] It is understood that user actions can generate user instructions, and test scripts can generate script instructions after they are executed. The reason test scripts can simulate user actions is that the script instructions corresponding to the test scripts can be the same as the user instructions corresponding to the user actions. Furthermore, the execution entities can execute actions that trigger tracking under the guidance of user instructions, or they can execute actions that trigger tracking under the guidance of script instructions.

[0044] Step 202: Obtain the tracking point log generated after the tracking point is triggered from the target client.

[0045] In this embodiment, after executing step 201, the execution entity may obtain, from the target client, a tracking log generated after the tracking point is triggered. The tracking log may include target feature information representing target features of the event recorded by the triggered tracking point. The target feature may be a feature to be analyzed, and the target feature may be related to the performance of the target client. For example, the event recorded by the triggered tracking point may be page loading, and the target feature may be the duration of the page loading.

[0046] In addition, the tracking point log may also include information used to characterize other characteristics of the event recorded by the triggered tracking point, for example, it may include time information used to characterize the time when the event occurred.

[0047] In practice, after a tracking log is generated, the client typically reports it to the corresponding server, which then analyzes it and obtains the results. However, this reporting process is time-consuming due to network transmission and other steps. Consequently, server-side analysis of the tracking logs is difficult to obtain results quickly, resulting in poor timeliness in information processing.

[0048] In this embodiment, after the tracking log is generated, the above-mentioned execution entity of the target client is used to obtain the tracking log and analyze the tracking log. This can obtain the analysis results more quickly without going through network transmission and other links, which helps to improve the timeliness of information processing.

[0049] Specifically, the execution entity may use various methods to obtain the tracking point logs generated after the tracking point is triggered from the target client.

[0050] In some optional implementations of this embodiment, the above-mentioned execution entity can obtain the tracking point log generated after the tracking point is triggered from the target client through a pre-installed hook.

[0051] In practice, hooking technology is a technique used to intercept messages from a specific process (for example, a process that reports tracking logs to a server) and perform customized processing on them. Developers can develop hook software specifically for a specific interception and processing process. Hook software can record the rules for intercepting and processing information. Then, when the hook software detects information to be intercepted, it can intercept and process it.

[0052] In this implementation method, developers can develop hooks for intercepting tracking logs and install them on the above-mentioned execution entity. Then, the above-mentioned execution entity can use the installed hooks to detect tracking logs, and when tracking logs are detected, obtain the tracking logs and store them locally. At this point, the above-mentioned execution entity has obtained the tracking logs through the hooks.

[0053] Step 203: Analyze the acquired tracking logs to obtain analysis results that characterize the performance of the target client.

[0054] In this embodiment, based on the tracking log obtained in step 202, the execution entity may analyze the obtained tracking log to obtain an analysis result that characterizes the performance of the target client. The analysis result may include, but is not limited to, at least one of the following: text, numbers, symbols, images, audio, and video.

[0055] In practice, after obtaining the analysis results, the above-mentioned execution entity can present the analysis results to technical personnel so that the technical personnel can optimize the target client based on the analysis results.

[0056] Specifically, the execution entity may use various methods to analyze the acquired tracking logs to obtain analysis results. For example, the execution entity may first extract at least two page load times from at least two tracking logs, then average the at least two page load times to obtain the average value as the analysis result; or the execution entity may extract the longest page load time from the at least two page load times corresponding to the at least two tracking logs as the analysis result.

[0057] In some optional implementations of this embodiment, the execution entity may analyze the acquired tracking logs using a preset analysis script to obtain analysis results that characterize the performance of the target client. The analysis script may be a script pre-set by a technician for analyzing tracking logs. The analysis script may record rules for analyzing tracking logs. The execution entity may obtain analysis results that characterize the performance of the target client by running the analysis script with the acquired tracking logs as input.

[0058] It should be noted that since the process of testing client performance typically includes analyzing the test data, the test script used to test client performance and the analysis script used to analyze the test data are typically used together. Therefore, the analysis script in this implementation and the test script used to test the target client performance can be part of a single master script. Furthermore, when testing client performance, only one master script needs to be installed, which installs both the analysis script and the test script. This helps simplify the client performance testing process and improves client performance testing efficiency.

[0059] Continue to see Figure 3 , Figure 3 FIG. 1 is a schematic diagram of an application scenario of the method for processing information for a terminal according to this embodiment. Figure 3 In an application scenario, mobile phone 301 can trigger a pre-set embedding point 303 for target client 302 (for example, a embedding point for recording the loading time of the main page), so that target client 302 generates an embedding point log 304. Then, mobile phone 301 can obtain embedding point log 304 generated after embedding point 303 is triggered from target client 304. Finally, mobile phone 301 can analyze the acquired embedding point log 304 to obtain analysis results 305 (for example, the average loading time of the main page) for characterizing the performance of target client 302.

[0060] The method provided by the above-mentioned embodiment of the present disclosure can analyze the tracking log after the client generates the tracking log. Compared with the solution of the prior art that the tracking log is analyzed by a remote server, the embodiment of the present disclosure can obtain analysis results more quickly, which helps to improve the timeliness of information processing.

[0061] Further references Figure 4 , which shows a process 400 of another embodiment of a method for processing information for a terminal. The process 400 of the method for processing information for a terminal includes the following steps:

[0062] Step 401: trigger the pre-set tracking point for the target client.

[0063] In this embodiment, the execution subject of the method for processing information of the terminal (for example Figure 1 The terminal device shown in FIG. 1 may trigger a pre-set tracking point for a target client in various ways. The target client may be a client whose performance is to be determined. The target client may be pre-installed on the execution entity. Specifically, the target client may be various types of client applications.

[0064] Step 402: Obtain the tracking point log generated after the tracking point is triggered from the target client.

[0065] In this embodiment, after executing step 401, the execution entity may obtain, from the target client, a tracking log generated after the tracking point is triggered. The tracking log may include target feature information representing target features of the event recorded by the triggered tracking point. The target feature may be a feature to be analyzed and may be related to the performance of the target client.

[0066] In addition, the tracking log may also include information used to characterize other features of the events recorded by the triggered tracking.

[0067] The above steps 401 and 402 can be respectively performed in a manner similar to steps 201 and 202 in the aforementioned embodiment. The above descriptions of steps 201 and 202 also apply to steps 401 and 402 and are not repeated here.

[0068] Step 403: Filter the acquired tracking logs.

[0069] In this embodiment, based on the tracking logs obtained in step 402, the execution entity may filter the tracking logs based on preset conditions. The preset conditions may be conditions predetermined by a technician for filtering out tracking logs of analytical value from multiple tracking logs.

[0070] Specifically, as an example, the preset condition may be that the occurrence time of the event corresponding to the buried point log is within the target time period. The target time period may be a preset time period, such as March 2019, or a time period determined based on the current time, such as the past 3 days. As another example, the preset condition may also be that the characteristic value of the target feature recorded in the buried point log for characterizing the event is greater than or equal to a preset threshold. For example, if the event is page loading and the target feature is page loading duration, the preset condition may be that the page loading duration recorded in the buried point log is greater than or equal to the preset duration.

[0071] Step 404: Analyze the filtered tracking logs to obtain analysis results that characterize the performance of the target client.

[0072] In this embodiment, based on the filtered tracking logs obtained in step 403, the above-mentioned execution entity can analyze the filtered tracking logs to obtain analysis results for characterizing the performance of the target client.

[0073] Specifically, the execution entity may refer to the method of analyzing the tracking logs in step 203 to analyze the filtered tracking logs to obtain analysis results, which will not be described in detail here.

[0074] from Figure 4 It can be seen that Figure 2 Compared with the corresponding embodiment, the process 400 of the method for processing information of the terminal in this embodiment highlights the steps of screening the acquired tracking logs, and then analyzing the screened tracking logs to obtain analysis results for characterizing the performance of the target client. Therefore, the scheme described in this embodiment can screen out tracking logs that meet the preset conditions from the acquired tracking logs, and analyze the tracking logs that meet the preset conditions. In this way, on the basis of being able to obtain analysis results for characterizing the performance of the target client, the number of tracking logs analyzed can be reduced, thereby simplifying the tracking log analysis steps, improving the efficiency of generating analysis results, and reducing the resources consumed for analyzing tracking logs.

[0075] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a device for processing information of a terminal. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0076] like Figure 5As shown, the apparatus 500 for processing information of a terminal in this embodiment includes: a triggering unit 501, an acquiring unit 502, and an analyzing unit 503. The triggering unit 501 is configured to trigger a tracking point pre-set for a target client; the acquiring unit 502 is configured to acquire a tracking point log generated after the tracking point is triggered from the target client; and the analyzing unit 503 is configured to analyze the acquired tracking point log to obtain an analysis result for characterizing the performance of the target client.

[0077] In this embodiment, the triggering unit 501 of the apparatus 500 for processing terminal information can use various methods to trigger the pre-set tracking point for the target client. The target client can be a client whose performance is to be determined. The target client can be pre-installed on the electronic device used by the apparatus 500. Specifically, the target client can be various types of client applications.

[0078] In practice, after developing a client application, technicians typically set up tracking points for the client application. Tracking points can record performance-related data generated by users during the client application's use, allowing optimization of the client application's performance based on this data.

[0079] In this embodiment, the acquisition unit 502 may acquire, from the target client, a tracking log generated after the tracking point is triggered. The tracking log may include target feature information representing target features of the event recorded by the triggered tracking point. The target feature may be a feature to be analyzed and may be related to the performance of the target client.

[0080] In addition, the tracking log may also include information used to characterize other features of the events recorded by the triggered tracking.

[0081] In this embodiment, based on the tracking logs obtained by the acquisition unit 502, the analysis unit 503 can analyze the obtained tracking logs to obtain analysis results that characterize the performance of the target client. The analysis results can include, but are not limited to, at least one of the following: text, numbers, symbols, images, audio, and video.

[0082] In some optional implementations of this embodiment, the device 500 also includes: a screening unit (not shown in the figure), configured to screen the acquired tracking logs; and the analysis unit 503 can be further configured to: analyze the filtered tracking logs to obtain analysis results for characterizing the performance of the target client.

[0083] In some optional implementations of this embodiment, the trigger unit 501 may be further configured to: utilize a pre-installed test script for testing the performance of the target client to trigger a pre-set tracking point for the target client.

[0084] In some optional implementations of this embodiment, the analysis unit 503 may be further configured to: analyze the acquired tracking logs using a preset analysis script to obtain analysis results for characterizing the performance of the target client.

[0085] In some optional implementations of this embodiment, the acquisition unit 502 may be further configured to: obtain, from the target client through a pre-installed hook, the tracking point log generated after the tracking point is triggered.

[0086] It is understood that the units described in the device 500 are similar to those in the reference Figure 2 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the device 500 and the units included therein, and will not be repeated here.

[0087] The apparatus 500 provided in the above-described embodiment of the present disclosure can generate a tracking log on the client, and then analyze the tracking log by the terminal. Compared to the prior art solution of analyzing tracking logs by a remote server, the embodiment of the present disclosure can obtain analysis results more quickly, which helps to improve the timeliness of information processing.

[0088] Reference below Figure 6 , which shows an electronic device (eg Figure 1 The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0089] like Figure 6As shown, the electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. Various programs and data required for the operation of the electronic device 600 are also stored in the RAM 603. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0090] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0091] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network via the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0092] It should be noted that the computer-readable medium described in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0093] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device. The computer-readable medium carries one or more programs. When executed by the electronic device, the electronic device: triggers a pre-set tracking point for a target client; obtains a tracking point log generated after the tracking point is triggered from the target client; and analyzes the obtained tracking point log to obtain an analysis result that characterizes the performance of the target client.

[0094] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0095] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0096] The units involved in the embodiments described in this disclosure may be implemented by software or hardware. In some cases, the name of the unit does not constitute a limitation on the unit itself. For example, the trigger unit may also be described as a "triggering point unit."

[0097] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also encompasses other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in the present disclosure.

Claims

1. A method for processing information for a terminal, comprising: Use pre-installed test scripts for testing the performance of target clients to trigger pre-set tracking points for target clients. Obtaining, from the target client through a pre-installed hook, a tracking log generated after the tracking point is triggered; Filter the acquired tracking logs; The filtered tracking logs are analyzed using a preset analysis script to obtain analysis results that characterize the performance of the target client. The analysis script and the test script belong to a general script.

2. A device for processing information at a terminal, comprising: The trigger unit is configured to trigger a pre-set tracking point for the target client using a pre-installed test script for testing the performance of the target client; an acquisition unit, configured to acquire, from the target client through a pre-installed hook, a tracking point log generated after the tracking point is triggered; A screening unit, configured to screen the acquired tracking logs; The analysis unit is configured to analyze the filtered tracking logs using a preset analysis script to obtain analysis results for characterizing the performance of the target client. The analysis script and the test script belong to a general script.

3. A terminal comprising: one or more processors; a storage device having one or more programs stored thereon, When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method according to claim 1 .

4. A computer-readable medium having a computer program stored thereon, wherein: When the program is executed by a processor, the method according to claim 1 is implemented.

Images