Page anomaly identification method and device, electronic equipment and storage medium

Abstract

The present disclosure relates to a page anomaly identification method and device, electronic equipment and storage medium. The method comprises: obtaining a unit time transmission frame number array of a to-be-detected page; the unit time transmission frame number array comprises a plurality of sequentially arranged unit time transmission frame numbers of the to-be-detected page; determining a target number of unit time transmission frame numbers that are continuously lower than a unit time transmission frame number threshold from the unit time transmission frame number array; and determining an anomaly identification result of the to-be-detected page according to the target number. The present method can improve the accuracy of page anomaly identification.

Description

Technical Field

[0001] This disclosure relates to the field of Internet technology, and in particular to a method, apparatus, electronic device and storage medium for identifying page anomalies. Background Technology

[0002] In internet scenarios, browser pages are frequently used, and whether a page in the browser is abnormal (such as lagging) is an important indicator of its usability and user-friendliness.

[0003] In related technologies, FPS (Frames Per Second) can be used to determine if a page is abnormal; for example, if the FPS is low at a certain moment, the page is considered abnormal and lagging. However, judging whether a page is lagging based solely on the FPS at a single moment will result in low accuracy in identifying page anomalies. Summary of the Invention

[0004] This disclosure provides a method, apparatus, electronic device, and storage medium for page anomaly identification, to at least solve the problem of low accuracy in page anomaly identification in related technologies. The technical solution of this disclosure is as follows:

[0005] According to a first aspect of the present disclosure, a method for identifying page anomalies is provided, comprising:

[0006] Obtain an array of transmission frames per unit time for the page to be detected; the array of transmission frames per unit time includes multiple sequentially arranged transmission frames per unit time for the page to be detected;

[0007] From the array of frames transmitted per unit time, determine the target number of frames transmitted per unit time that are continuously lower than the threshold number of frames transmitted per unit time.

[0008] Based on the target number, the anomaly identification result for the page to be detected is determined.

[0009] In an exemplary embodiment, determining the anomaly identification result for the page to be detected based on the target number includes:

[0010] When the target number is greater than or equal to the preset number, the page to be detected is determined to be abnormal.

[0011] In an exemplary embodiment, determining the anomaly identification result of the page to be detected based on the target number further includes:

[0012] When the target number is less than the preset number, the next unit time transmission frame number after the target unit time transmission frame number is identified from the unit time transmission frame number array; the target unit time transmission frame number is the last unit time transmission frame number among the unit time transmission frame numbers that are continuously lower than the unit time transmission frame number threshold.

[0013] The average of the number of frames transmitted per unit time that are continuously below the threshold for the number of frames transmitted per unit time, and the next number of frames transmitted per unit time after the target number of frames transmitted per unit time.

[0014] When the average value is less than the threshold for the number of frames transmitted per unit time, the page to be detected is determined to be abnormal.

[0015] In one exemplary embodiment, before obtaining the array of transmission frame counts per unit time for the page to be detected, the method further includes:

[0016] The number of transmission frames per unit time for the page to be detected is obtained; each number of transmission frames per unit time is identified by a corresponding acquisition time.

[0017] The multiple unit time transmission frame counts are stored in the unit time transmission frame count array in ascending order of the acquisition time.

[0018] In an exemplary embodiment, obtaining the number of transmission frames per unit time for the page to be detected includes:

[0019] When the page to be detected is visible, listen for the frame request event of the page to be detected;

[0020] When a frame request event of the page to be detected is detected, the number of times the frame request event of the page to be detected is executed is updated, and the execution timestamp of the frame request event of the page to be detected is recorded.

[0021] When the difference between the execution timestamp and the start timestamp is greater than a preset difference, the number of frames transmitted per unit time for the page to be detected is counted based on the difference and the updated execution count; the start timestamp indicates the start time of this count of the number of frames transmitted per unit time.

[0022] When the difference between the execution timestamp and the start timestamp is less than or equal to the preset difference, the frame request event of the page to be detected is re-listened until the difference between the execution timestamp and the start timestamp of the listened frame request event is greater than the preset difference.

[0023] In one exemplary embodiment, the method further includes:

[0024] When the page to be detected is in an invisible state, stop listening to the frame request event of the page to be detected, and count the total time the page to be detected is in an invisible state.

[0025] The step of calculating the number of frames transmitted per unit time for the page to be detected based on the difference and the updated execution count includes:

[0026] Subtract the difference from the total time the page to be detected was invisible to obtain the updated difference;

[0027] Based on the updated difference and the updated execution count, the number of frames transmitted per unit time for the page to be detected is calculated.

[0028] In an exemplary embodiment, obtaining the array of transmission frames per unit time for the page to be detected includes:

[0029] Obtain the page identifier of the page to be detected;

[0030] Obtain the array of transmission frames per unit time corresponding to the page identifier, and use it as the array of transmission frames per unit time for the page to be detected.

[0031] According to a second aspect of the present disclosure, a page anomaly identification device is provided, comprising:

[0032] The acquisition unit is configured to acquire an array of transmission frames per unit time for a page to be detected; the array of transmission frames per unit time includes multiple sequentially arranged transmission frames per unit time for the page to be detected.

[0033] The determining unit is configured to perform the task of determining a target number of consecutively lower than the unit time transmission frame number threshold from the unit time transmission frame number array.

[0034] The identification unit is configured to perform anomaly identification results for the page to be detected based on the target number.

[0035] In one exemplary embodiment, the identification unit is further configured to determine that the page to be detected is abnormal when the number of targets is greater than or equal to a preset number.

[0036] In an exemplary embodiment, the identification unit is further configured to perform the following actions when the target number is less than the preset number: identifying the next unit-time transmission frame number after the target unit-time transmission frame number from the unit-time transmission frame number array; the target unit-time transmission frame number is the last unit-time transmission frame number among the unit-time transmission frame numbers that are continuously lower than the unit-time transmission frame number threshold; calculating the average of the unit-time transmission frame numbers that are continuously lower than the unit-time transmission frame number threshold and the next unit-time transmission frame number after the target unit-time transmission frame number; and determining that the page to be detected is abnormal when the average value is less than the unit-time transmission frame number threshold.

[0037] In one exemplary embodiment, the page anomaly identification device further includes a storage unit configured to acquire a plurality of unit time transmission frames of the page to be detected; each unit time transmission frame is identified by a corresponding acquisition time; and the plurality of unit time transmission frames are stored in the unit time transmission frame array in ascending order of the acquisition time.

[0038] In an exemplary embodiment, the storage unit is further configured to: listen for frame request events of the page to be detected when the page to be detected is visible; update the execution count of the frame request event of the page to be detected when the frame request event of the page to be detected is detected, and record the execution timestamp of the frame request event of the page to be detected; when the difference between the execution timestamp and the start timestamp is greater than a preset difference, count the number of frames transmitted per unit time of the page to be detected based on the difference and the updated execution count; the start timestamp represents the start time of this count of the number of frames transmitted per unit time; when the difference between the execution timestamp and the start timestamp is less than or equal to the preset difference, listen for the frame request event of the page to be detected again until the difference between the execution timestamp of the detected frame request event and the start timestamp is greater than the preset difference.

[0039] In one exemplary embodiment, the page anomaly identification device further includes a statistics unit configured to stop listening to the frame request event of the page to be detected when the page to be detected is in an invisible state, and to count the total time the page to be detected is in an invisible state.

[0040] The storage unit is further configured to subtract the difference from the total time the page to be detected was in an invisible state to obtain an updated difference; and to count the number of frames transmitted per unit time for the page to be detected based on the updated difference and the updated execution count.

[0041] In an exemplary embodiment, the acquisition unit is further configured to acquire the page identifier of the page to be detected; and acquire the unit time transmission frame count array corresponding to the page identifier as the unit time transmission frame count array of the page to be detected.

[0042] According to a third aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the page anomaly identification method as described in any embodiment of the first aspect.

[0043] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the page anomaly identification method described in any embodiment of the first aspect.

[0044] According to a fifth aspect of the present disclosure, a computer program product is provided, the computer program product including instructions that, when executed by a processor of an electronic device, enable the electronic device to perform the page anomaly identification method described in any embodiment of the first aspect.

[0045] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0046] By acquiring an array of unit-time transmission frames for the page to be inspected, which includes multiple sequentially arranged unit-time transmission frames for the page, and then determining the target number of unit-time transmission frames that are consecutively below a threshold, the anomaly identification result for the page is determined based on the target number. In this way, by considering the total number of unit-time transmission frames that are consecutively below the threshold, the operation of the page to be inspected can be accurately determined over a continuous period of time, rather than just considering the unit-time transmission frames at a single moment. This avoids the drawback of low accuracy in page anomaly identification caused by relying solely on the unit-time transmission frames at a specific moment, thus improving the accuracy of page anomaly identification.

[0047] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0048] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0049] Figure 1 This is a flowchart illustrating a page anomaly identification method according to an exemplary embodiment.

[0050] Figure 2 This is a flowchart illustrating the steps for determining the anomaly identification result of a page to be detected, according to an exemplary embodiment.

[0051] Figure 3 This is a flowchart illustrating another page anomaly identification method according to an exemplary embodiment.

[0052] Figure 4 This is a flowchart illustrating a method for statistical FPS according to an exemplary embodiment.

[0053] Figure 5 This is a block diagram illustrating a page anomaly identification device according to an exemplary embodiment.

[0054] Figure 6 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation

[0055] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0056] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0057] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0058] Figure 1 This is a flowchart illustrating a page anomaly identification method according to an exemplary embodiment, such as... Figure 1 As shown, this page anomaly detection method is used in the terminal and includes the following steps:

[0059] In step S110, an array of transmission frames per unit time for the page to be detected is obtained; the array of transmission frames per unit time includes multiple sequentially arranged transmission frames per unit time for the page to be detected.

[0060] The page to be tested refers to the page that needs to be checked for abnormalities (such as lag), such as information browsing pages, video browsing pages, and image browsing pages.

[0061] The number of frames transmitted per unit time refers to the number of frames transmitted per unit time, such as frames per second (FPS).

[0062] The array of transmission frames per unit time stores multiple transmission frames per unit time for the page to be detected, such as [10, 20, 29, 35, 55, 60]. These transmission frames per unit time are sorted according to the acquisition time; the acquisition time refers to the time when the transmission frames per unit time of the page to be detected are acquired.

[0063] Specifically, the terminal obtains the array of transmission frames per unit time for the page to be detected from the array of transmission frames per unit time that stores multiple pages, thereby obtaining the multiple transmission frames per unit time for the page to be detected.

[0064] In step S120, a target number of consecutively lower than the threshold number of frames transmitted per unit time is determined from the array of frames transmitted per unit time.

[0065] The frame rate threshold per unit time refers to the critical value for the number of frames transmitted per unit time, specifically the frame rate threshold per second, such as 30. Of course, the frame rate threshold per unit time can also refer to other values ​​and can be adjusted according to actual circumstances; no specific limitations are made here.

[0066] The target number refers to the total number of consecutive frames transmitted per unit time that are below the threshold number of frames transmitted per unit time in the array of frames transmitted per unit time. For example, if the array of frames transmitted per unit time is [10, 20, 29, 35, 55, 60], and the frames transmitted per unit time are consecutive and all below the threshold number of frames transmitted per unit time of 30, then the total number of consecutive frames transmitted per unit time below the threshold number is 3, and therefore the target number is 3.

[0067] Specifically, the terminal sequentially compares each unit time transmission frame count in the unit time transmission frame count array with the unit time transmission frame count threshold to obtain a comparison result; based on the comparison result, the total number of unit time transmission frames in the unit time transmission frame count array that are continuously lower than the unit time transmission frame count threshold is determined as the target number.

[0068] For example, in the array of frames per second [10, 20, 29, 35, 55, 60], if the frames per second of 10, 20, and 29 are consecutive and all are below the threshold of 30, then the target number of consecutive frames per second below the threshold in this array is 3.

[0069] In step S130, the anomaly identification result of the page to be detected is determined based on the target quantity.

[0070] Among them, the anomaly identification results of the page to be detected are used to describe whether the page to be detected is abnormal, specifically to describe whether the page to be detected is lagging.

[0071] Specifically, when the target number of consecutive frames transmitted per unit time that are lower than the threshold number of frames transmitted per unit time in the array of frames transmitted per unit time is greater than or equal to the preset number, it indicates that there are multiple consecutive frames transmitted per unit time that are less than the threshold number of frames transmitted per unit time, and the page to be detected is confirmed to be abnormal.

[0072] In the above-described page anomaly detection method, an array of unit-time transmission frame counts for the page to be detected is obtained. This array includes multiple sequentially arranged unit-time transmission frame counts for the page to be detected. Then, a target number of unit-time transmission frame counts that are consecutively lower than a unit-time transmission frame count threshold is determined from the unit-time transmission frame count array. Finally, the anomaly detection result for the page to be detected is determined based on the target number. In this way, by considering the total number of unit-time transmission frame counts that are consecutively lower than the unit-time transmission frame count threshold, the operation of the page to be detected over a continuous period of time can be accurately determined, rather than simply considering the unit-time transmission frame count at a single moment. This avoids the drawback of low accuracy in page anomaly detection caused by using the unit-time transmission frame count at a single moment to identify whether a page is abnormal, thereby improving the accuracy of page anomaly detection.

[0073] In an exemplary embodiment, in step S130, the abnormal identification result of the page to be detected is determined according to the target number, including: when the target number is greater than or equal to a preset number, the page to be detected is determined to be abnormal.

[0074] The preset quantity refers to the critical number of frames transmitted per unit time that are continuously lower than the threshold number of frames transmitted per unit time in the array of frames transmitted per unit time. The preset quantity is greater than or equal to 2, and can also be adjusted according to the actual situation. No specific limit is set here.

[0075] For example, in the array of frames per second [10, 20, 29, 35, 55, 60], the three frames per second of 10, 20, and 29 are consecutive and all lower than the frame per second threshold of 30. This means that the target number of consecutive frames per second below the frame per second threshold in the array is 3, which is equal to the preset number of 3. This indicates that the page to be tested has multiple consecutive frames per second that are less than the frame per second threshold, thus indicating that the page to be tested is experiencing lag.

[0076] It's important to note that a low frame rate (fps) at a single moment does not necessarily indicate page lag. Only by combining multiple consecutive fps data points can we determine if the page is lagging within a specific timeframe. When a low fps is detected at a particular moment, it doesn't immediately indicate page lag. Instead, the lag level is assessed by combining fps data from multiple consecutive time periods.

[0077] The technical solution provided in this disclosure determines that the page to be detected is abnormal when the target number of consecutively lower than the threshold ...

[0078] In one exemplary embodiment, such as Figure 2 As shown, in step S130, the anomaly identification result of the page to be detected is determined according to the number of targets. This can be achieved through the following steps:

[0079] In step S210, when the target number is less than the preset number, the next unit time transmission frame number after the target unit time transmission frame number is identified from the unit time transmission frame number array; the target unit time transmission frame number is the last unit time transmission frame number among the unit time transmission frame numbers that are continuously lower than the unit time transmission frame number threshold.

[0080] In step S220, the average number of frames transmitted per unit time that are continuously lower than the threshold for the number of frames transmitted per unit time is calculated, along with the average number of frames transmitted per unit time after the target number of frames transmitted per unit time.

[0081] In step S230, when the average value is less than the threshold for the number of frames transmitted per unit time, the page to be detected is determined to be abnormal.

[0082] The number of frames transmitted per unit time in the next unit time can be greater than or equal to the threshold number of frames transmitted per unit time; this disclosure does not specify the exact threshold.

[0083] Specifically, if the target number of consecutive unit-time transmission frames below the unit-time transmission frame count threshold in the unit-time transmission frame count array of the page to be detected is less than a preset number, the terminal determines the last unit-time transmission frame count among the consecutive unit-time transmission frames below the unit-time transmission frame count threshold as the target unit-time transmission frame count; obtains the next unit-time transmission frame count after the target unit-time transmission frame count from the unit-time transmission frame count array; adds the unit-time transmission frame count consecutively below the unit-time transmission frame count threshold to the next unit-time transmission frame count after the target unit-time transmission frame count, and calculates their average value; if the average value is greater than or equal to the unit-time transmission frame count threshold, the page to be detected is determined to be normal; if the average value is less than the unit-time transmission frame count threshold, the page to be detected is determined to be abnormal.

[0084] For example, in the array of frames per second (fps) [10, 20, 51, 35, 55, 60], fps values ​​of 10 and 20 are consecutive and both are below the fps threshold of 30. This indicates that the target number of fps values ​​consecutively below the fps threshold in this array is 2, which is less than the preset number of 3. In this case, the average value of the next fps value (51) after the consecutive fps values ​​below the fps threshold can be used to determine whether the page to be detected is abnormal. The average value of the consecutive fps values ​​below the fps threshold and the next fps value is (10+20+51) / 3 = 27, which is less than 30, indicating that the page to be detected is abnormal.

[0085] The technical solution provided in this disclosure, when the target number of consecutive transmission frames per unit time below the threshold in the array of transmission frames per unit time of the page to be detected is less than a preset number, combines the next transmission frame per unit time below the threshold and calculates the average value to determine whether the page to be detected is abnormal. By comprehensively considering the number of consecutive transmission frames per unit time below the threshold and the next transmission frame per unit time, it is beneficial to improve the accuracy of page anomaly identification.

[0086] In an exemplary embodiment, in step S110, before obtaining the array of transmission frames per unit time for the page to be detected, the method further includes: obtaining multiple transmission frames per unit time for the page to be detected; each transmission frame per unit time is identified by a corresponding acquisition time; and storing the multiple transmission frames per unit time into the array of transmission frames per unit time in ascending order of acquisition time.

[0087] For example, the terminal sequentially obtains multiple unit time transmission frame counts of the page to be detected, and stores the multiple unit time transmission frame counts into a unit time transmission frame count array in ascending order of the acquisition time, thus obtaining the unit time transmission frame count array of the page to be detected, such as [10, 20, 51, 35, 55, 60].

[0088] The technical solution provided in this disclosure stores multiple unit-time transmission frame counts of the page to be detected in ascending order of acquisition time into a unit-time transmission frame count array. This facilitates the subsequent determination of the target number of unit-time transmission frame counts that are consecutively lower than the unit-time transmission frame count threshold from the unit-time transmission frame count array of the page to be detected, thereby determining whether the page to be detected is abnormal. By comprehensively considering multiple unit-time transmission frame counts that are consecutively lower than the unit-time transmission frame count threshold, it is beneficial to improve the accuracy of page anomaly identification.

[0089] In an exemplary embodiment, obtaining multiple unit-time transmission frame counts of a page to be detected includes: when the page to be detected is visible, listening for frame request events of the page to be detected; when a frame request event of the page to be detected is detected, updating the execution count of the frame request event of the page to be detected and recording the execution timestamp of the frame request event of the page to be detected; when the difference between the execution timestamp and the start timestamp is greater than a preset difference, counting the unit-time transmission frame count of the page to be detected based on the difference and the updated execution count; the start timestamp indicates the start time of this unit-time transmission frame count; when the difference between the execution timestamp and the start timestamp is less than or equal to the preset difference, listening for the frame request event of the page to be detected is resumed until the difference between the execution timestamp and the start timestamp of the detected frame request event is greater than the preset difference.

[0090] The page to be tested being visible means that it is displayed on the current terminal interface. The frame request event is used to request frames. It should be noted that the frame request event is a system-automated timed task. If the page is not lagging, it typically executes once every 16.6ms; if the page is lagging, it will execute more than once every 16.6ms. Furthermore, the frame request event runs automatically when the page to be tested is in the foreground, and stops running when the page to be tested is in the background or when switching to another page.

[0091] Specifically, each time a frame request event of the page to be detected is detected, the execution count of the frame request event of the page to be detected is incremented by 1 to update the execution count of the frame request event of the page to be detected.

[0092] The execution timestamp of the frame request event refers to the time value of the current execution of the frame request event; the start timestamp refers to the start time value of the current unit time frame transmission count. After obtaining the number of frames transmitted in one unit time, the start timestamp is recorded again to count the number of frames transmitted in the next unit time. The preset difference is specifically 1 second.

[0093] The execution timestamp of the monitored frame request event refers to the new execution timestamp.

[0094] Specifically, when the page to be detected is visible, the terminal records the start timestamp T1 and listens for the frame request event of the page to be detected. When the frame request event of the page to be detected is detected, the execution count F of the frame request event of the page to be detected is incremented by 1 to obtain the updated execution count F, and the execution timestamp T2 of the frame request event of the page to be detected is recorded. If the difference between the execution timestamp T2 and the start timestamp T1 is greater than a preset difference (e.g., 1 second), the number of frames transmitted per unit time of the page to be detected is F / [(T2-T1)×1000]. This number of frames transmitted per unit time is stored in the number of frames transmitted per unit time array, and the start timestamp T1 is recorded again to count the number of frames transmitted per unit time for the next time. If the difference between the execution timestamp T2 and the start timestamp T1 is less than or equal to a preset difference (e.g., 1 second), the terminal retains the start timestamp T1 and continues to listen for frame request events on the page to be detected. When a frame request event is detected, the execution count F of the frame request event is incremented by 1 to obtain the updated execution count F, and the execution timestamp T2 of the frame request event is recorded as the new execution timestamp. If the difference between the new execution timestamp T2 and the start timestamp T1 is greater than the preset difference (e.g., 1 second), the number of frames transmitted per unit time for the page to be detected is F / [(new T2-T1)×1000]. This number of frames transmitted per unit time is stored in the number of frames transmitted per unit time array, and the start timestamp T1 is recorded again to count the number of frames transmitted per unit time for the next time. By repeating the above process, multiple number of frames transmitted per unit time for the page to be detected can be obtained.

[0095] The technical solution provided in this disclosure, when the page to be detected is visible, listens to the frame request event of the page to be detected, and if the difference between the execution timestamp and the start timestamp of the listened frame request event is greater than a preset difference, the number of frames transmitted per unit time of the page to be detected is calculated based on the difference and the updated execution count, which helps to improve the accuracy of determining the number of frames transmitted per unit time.

[0096] In an exemplary embodiment, the page anomaly identification method provided in this disclosure further includes: when the page to be detected is in an invisible state, stopping the listening to the frame request event of the page to be detected and counting the total time the page to be detected is in an invisible state; and counting the number of frames transmitted per unit time of the page to be detected based on the difference and the updated execution count, specifically including: subtracting the difference from the total time the page to be detected is in an invisible state to obtain the updated difference; and counting the number of frames transmitted per unit time of the page to be detected based on the updated difference and the updated execution count.

[0097] The state where the page to be tested is invisible means that the page to be tested is in the background or has been switched to another page and does not appear on the current terminal interface.

[0098] Specifically, when the page to be detected is invisible, the frame request event stops running. The total time the page is invisible represents the total time the frame request event has stopped running. It should be noted that if the page to be detected is in the background or switched to another page, the total time the frame request event has stopped running will be ignored, resulting in an underestimation of the number of frames transmitted per unit time, and consequently, a lower accuracy rate for page anomaly detection.

[0099] Specifically, when the page to be detected is invisible, the listening for frame request events of the page to be detected is stopped, and the total time the page to be detected is invisible is counted. When the page to be detected is visible, the listening for frame request events of the page to be detected is resumed. When a frame request event of the page to be detected is detected, the execution count F of the frame request event of the page to be detected is incremented by 1 to obtain the updated execution count F, and the execution timestamp T2 of the frame request event of the page to be detected is recorded. If the difference between the execution timestamp T2 and the start timestamp T1 is greater than a preset difference (e.g., 1 second), the number of frames transmitted per unit time of the page to be detected is F / [(T2-T1-total time)×1000]. This number of frames transmitted per unit time is stored in the number of frames transmitted per unit time array, and the start timestamp T1 is recorded again to count the number of frames transmitted per unit time for the next time.

[0100] The technical solution provided in this disclosure, when counting the number of frames transmitted per unit time for the page to be detected, comprehensively considers the total time the page to be detected is in an invisible state. This is beneficial for comprehensively considering the total time the frame request event stops running, further improving the accuracy of determining the number of frames transmitted per unit time. It avoids the defect of ignoring the total time the frame request event stops running, which would lead to an underestimation of the number of frames transmitted per unit time and consequently a low accuracy of page anomaly identification, thus further improving the accuracy of page anomaly identification.

[0101] In an exemplary embodiment, step S110, obtaining the unit time transmission frame count array of the page to be detected includes: obtaining the page identifier of the page to be detected; and obtaining the unit time transmission frame count array corresponding to the page identifier as the unit time transmission frame count array of the page to be detected.

[0102] The page identifier of the page to be tested refers to the unique identification information of the page to be tested, such as the page name and page number.

[0103] For example, the terminal obtains the page identifier of the page to be detected by using the page identifier acquisition instruction; from the preset correspondence between page identifiers and the number of transmission frames per unit time array, it obtains the number of transmission frames per unit time array corresponding to the page identifier of the page to be detected, and uses it as the number of transmission frames per unit time array of the page to be detected.

[0104] The technical solution provided in this disclosure query the correspondence between a preset page identifier and a unit time transmission frame count array based on the page identifier of the page to be detected. This facilitates the rapid acquisition of the unit time transmission frame count array of the page to be detected, thereby improving the acquisition efficiency of the unit time transmission frame count array of the page to be detected.

[0105] Figure 3 This is a flowchart illustrating another page anomaly identification method according to an exemplary embodiment, such as... Figure 3 As shown, this page anomaly detection method is used in the terminal and includes the following steps:

[0106] In step S310, when the page to be detected is visible, the frame request event of the page to be detected is listened to; when the frame request event of the page to be detected is heard, the execution count of the frame request event of the page to be detected is updated, and the execution timestamp of the frame request event of the page to be detected is recorded.

[0107] In step S320, when the difference between the execution timestamp and the start timestamp is greater than a preset difference, the number of frames transmitted per unit time for the page to be detected is counted based on the difference and the updated number of executions; the start timestamp indicates the start time of this count of the number of frames transmitted per unit time.

[0108] In step S330, when the difference between the execution timestamp and the start timestamp is less than or equal to a preset difference, the frame request event of the page to be detected is listened to again until the difference between the execution timestamp and the start timestamp of the listened frame request event is greater than the preset difference, then step S320 is executed.

[0109] In step S340, when the page to be detected is in an invisible state, the listening for frame request events of the page to be detected is stopped, and the total time the page to be detected is in an invisible state is counted; when the difference between the execution timestamp and the start timestamp is greater than a preset difference, the difference is subtracted from the total time to obtain the updated difference; based on the updated difference and the updated execution count, the number of frames transmitted per unit time of the page to be detected is counted.

[0110] In step S350, the number of transmission frames per unit time of the page to be detected is stored in the array of transmission frames per unit time of the page to be detected in ascending order of acquisition time; each transmission frame per unit time is identified by a corresponding acquisition time.

[0111] In step S360, the array of transmission frames per unit time of the page to be detected is obtained; from the array of transmission frames per unit time, the target number of transmission frames per unit time that are continuously lower than the threshold of transmission frames per unit time is determined.

[0112] In step S370, when the target number is greater than or equal to the preset number, the page to be detected is determined to be abnormal.

[0113] In step S380, when the target number is less than the preset number, the next unit time transmission frame number after the target unit time transmission frame number is identified from the unit time transmission frame number array; the target unit time transmission frame number is the last unit time transmission frame number among the unit time transmission frame numbers that are continuously lower than the unit time transmission frame number threshold.

[0114] In step S390, the average number of frames transmitted per unit time that are continuously lower than the threshold for the number of frames transmitted per unit time, and the average number of frames transmitted per unit time after the target number of frames transmitted per unit time; when the average number of frames transmitted per unit time is less than the threshold for the number of frames transmitted per unit time, the page to be detected is determined to be abnormal.

[0115] In the aforementioned page anomaly detection method, by considering the total number of consecutive frames transmitted below the threshold per unit time, the operation of the page under test can be accurately determined over a continuous period of time, rather than simply considering the number of frames transmitted per unit time at a single moment. This avoids the drawback of low accuracy in page anomaly detection caused by relying solely on the number of frames transmitted per unit time at a particular moment, thus improving the accuracy of page anomaly detection. Furthermore, considering whether the page under test is visible helps to comprehensively consider the total time during which the frame request event stops running, further improving the accuracy of obtaining the number of frames transmitted per unit time. This avoids the drawback of underestimating the number of frames transmitted per unit time due to ignoring the total time during which the frame request event stops running, which would result in a lower accuracy in page anomaly detection, further improving the accuracy of page anomaly detection.

[0116] To more clearly illustrate the page anomaly identification method provided in this disclosure, a specific embodiment is described below. In an exemplary embodiment, the page stuttering situation is determined by accurately calculating the number of frames transmitted per second and combining the calculations of multiple consecutive frames transmitted per second. Specifically, this includes the following:

[0117] Step 1: Reference Figure 4 As long as the user remains on the current page, the process of calculating the number of frames transmitted per second (fps) is initiated. This begins by listening for frame request events and recording the initial timestamp T1. Each time a frame request event is executed, the execution count F is incremented by 1. Simultaneously, the difference between the time T2 of each execution and the initial timestamp T1 is compared. If the difference is greater than 1 second, the number of fps is calculated; where the number of fps = F / [(T2-T1)×1000]. After obtaining the number of fps within that second, it is stored in a `frames-per-second` array. This process is repeated, continuously adding the number of fps to the array. In addition to listening for frame request events, the process of calculating fps also begins listening for page visibility change events. When a user leaves the page, such as when the user switches to the background or switches to another page in the browser, the frame request event listener is stopped in the callback of the page visibility change event. When the user returns to the page, the frame request event listener is restarted. This avoids the situation where the number of times the frame request event is stopped due to the page being in the background increases, which would cause the statistically obtained number of frames transmitted per second to be underestimated. This allows for an accurate calculation of the number of frames transmitted per second.

[0118] Step Two: Determine page stuttering by combining multiple frame rate (FR) values, rather than relying on a single FFR value. Step One has already stored all FFR values ​​in an array. The next step is to analyze these FFR values ​​to determine the page stuttering level. The specific analysis process is as follows:

[0119] (1) In the array of frames per second (fps), if N consecutive frames per second are lower than the frame per second threshold, the page is considered to be lagging. N and the frame per second threshold can be determined according to the actual situation.

[0120] (2) In the array of frames per second (fps), if the number of fps is lower than the threshold, the number of fps is recorded and stored in the statistics array. If the number of records is N consecutive times, the page is considered to be lagging. If the number of records of fps lower than the threshold is not N consecutive times, the calculation continues until the number of fps exceeds the threshold. The current number of fps is compared with the average number of fps stored in the statistics array and the threshold. If the average is lower than the threshold, the page is confirmed to be lagging. If the average is greater than or equal to the number of fps, the page is confirmed to be normal.

[0121] The above-mentioned page anomaly identification method can achieve the following technical effects: (1) By accurately calculating the number of frames transmitted per second, it is beneficial to improve the accuracy of determining the number of frames transmitted per second. (2) By comprehensively considering multiple consecutive number of frames transmitted per second, it is beneficial to accurately reflect the page stuttering situation, thereby improving the accuracy of page anomaly identification.

[0122] It should be understood that, although Figures 1-3 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figures 1-3 At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0123] It is understood that the same / similar parts between the various embodiments of the methods described above in this specification can be referred to each other. Each embodiment focuses on the differences from other embodiments, and relevant parts can be referred to the description of other method embodiments.

[0124] Figure 5 This is a block diagram illustrating a page anomaly identification device according to an exemplary embodiment. Referring to FIGA X, the device includes an acquisition unit 510, a determination unit 520, and an identification unit 530.

[0125] The acquisition unit 510 is configured to acquire an array of unit time transmission frames of the page to be detected; the array of unit time transmission frames includes multiple sequentially arranged unit time transmission frames of the page to be detected.

[0126] The determining unit 520 is configured to determine, from the array of frames transmitted per unit time, the target number of frames that are consecutively lower than the threshold number of frames transmitted per unit time.

[0127] The identification unit 530 is configured to perform anomaly identification results on the page to be detected based on the target number.

[0128] In one exemplary embodiment, the identification unit 530 is further configured to determine that the page to be detected is abnormal when the number of targets is greater than or equal to a preset number.

[0129] In an exemplary embodiment, the identification unit 530 is further configured to perform the following actions when the target number is less than a preset number: identifying the next unit time transmission frame number after the target unit time transmission frame number from the unit time transmission frame number array; the target unit time transmission frame number is the last unit time transmission frame number among the unit time transmission frame numbers that are continuously lower than the unit time transmission frame number threshold; calculating the average value of the unit time transmission frame numbers that are continuously lower than the unit time transmission frame number threshold and the next unit time transmission frame number after the target unit time transmission frame number; and determining that the page to be detected is abnormal when the average value is less than the unit time transmission frame number threshold.

[0130] In one exemplary embodiment, the page anomaly identification device further includes a storage unit configured to acquire multiple unit time transmission frames of the page to be detected; each unit time transmission frame is identified by a corresponding acquisition time; and the multiple unit time transmission frames are stored in a unit time transmission frame array in ascending order of acquisition time.

[0131] In one exemplary embodiment, the storage unit is further configured to: listen for frame request events of the page to be detected when the page to be detected is visible; update the execution count of the frame request event of the page to be detected when the frame request event of the page to be detected is detected, and record the execution timestamp of the frame request event of the page to be detected; when the difference between the execution timestamp and the start timestamp is greater than a preset difference, count the number of frames transmitted per unit time of the page to be detected based on the difference and the updated execution count; the start timestamp indicates the start time of this count of the number of frames transmitted per unit time; when the difference between the execution timestamp and the start timestamp is less than or equal to the preset difference, listen for the frame request event of the page to be detected again until the difference between the execution timestamp and the start timestamp of the detected frame request event is greater than the preset difference.

[0132] In one exemplary embodiment, the page anomaly identification device further includes a statistics unit configured to perform the following: when the page to be detected is in an invisible state, stop listening to the frame request event of the page to be detected and count the total time the page to be detected is in an invisible state.

[0133] The storage unit is also configured to subtract the difference from the total time the page to be detected was in an invisible state to obtain a new difference; based on the new difference and the updated number of executions, the number of frames transmitted per unit time for the page to be detected is counted.

[0134] In an exemplary embodiment, the acquisition unit 510 is further configured to acquire the page identifier of the page to be detected; and acquire the unit time transmission frame count array corresponding to the page identifier as the unit time transmission frame count array of the page to be detected.

[0135] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0136] Figure 6 This is a block diagram illustrating an electronic device 600 for performing a page anomaly identification method according to an exemplary embodiment. For example, the electronic device 600 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0137] Reference Figure 6 The electronic device 600 may include one or more of the following components: processing component 602, memory 604, power supply component 606, multimedia component 608, audio component 610, input / output (I / O) interface 612, sensor component 614, and communication component 616.

[0138] Processing component 602 typically controls the overall operation of electronic device 600, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 602 may include one or more modules to facilitate interaction between processing component 602 and other components. For example, processing component 602 may include a multimedia module to facilitate interaction between multimedia component 608 and processing component 602.

[0139] Memory 604 is configured to store various types of data to support the operation of electronic device 600. Examples of such data include instructions for any application or method operating on electronic device 600, contact data, phonebook data, messages, pictures, videos, etc. Memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, optical disk, or graphene storage.

[0140] Power supply component 606 provides power to various components of electronic device 600. Power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 600.

[0141] Multimedia component 608 includes a screen that provides an output interface between the electronic device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 608 includes a front-facing camera and / or a rear-facing camera. When the electronic device 600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0142] Audio component 610 is configured to output and / or input audio signals. For example, audio component 610 includes a microphone (MIC) configured to receive external audio signals when electronic device 600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 604 or transmitted via communication component 616. In some embodiments, audio component 610 also includes a speaker for outputting audio signals.

[0143] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0144] Sensor assembly 614 includes one or more sensors for providing state assessments of various aspects of electronic device 600. For example, sensor assembly 614 can detect the on / off state of electronic device 600, the relative positioning of components such as the display and keypad of electronic device 600, changes in position of electronic device 600 or its components, the presence or absence of user contact with electronic device 600, orientation or acceleration / deceleration of device 600, and temperature changes of electronic device 600. Sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 614 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0145] Communication component 616 is configured to facilitate wired or wireless communication between electronic device 600 and other devices. Electronic device 600 can access wireless networks based on communication standards, such as WiFi, carrier networks (such as 2G, 3G, 4G, or 5G), or combinations thereof. In one exemplary embodiment, communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 616 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0146] In an exemplary embodiment, the electronic device 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0147] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions, which can be executed by a processor 620 of an electronic device 600 to perform the above-described method. For example, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0148] In an exemplary embodiment, a computer program product is also provided, which includes instructions that can be executed by a processor 620 of an electronic device 600 to perform the above-described method.

[0149] It should be noted that the above-mentioned apparatus, electronic equipment, computer-readable storage medium, computer program product, etc., may also include other implementation methods according to the description of the method embodiments. For specific implementation methods, please refer to the description of the relevant method embodiments, which will not be elaborated here.

[0150] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0151] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method of page anomaly recognition, characterized by, The method comprises the following steps: obtaining an array of unit time transmission frame numbers of a to-be-detected page, comprising: obtaining a plurality of unit time transmission frame numbers of the to-be-detected page; each unit time transmission frame number is marked with a corresponding acquisition time; storing the plurality of unit time transmission frame numbers in the array of unit time transmission frame numbers in ascending order of the acquisition time; the array of unit time transmission frame numbers comprises a plurality of sequentially arranged unit time transmission frame numbers of the to-be-detected page; determining a target number of unit time transmission frame numbers that are continuously lower than a unit time transmission frame number threshold from the array of unit time transmission frame numbers; determining an abnormality recognition result of the to-be-detected page according to the target number, comprising: when the target number is greater than or equal to a preset number, determining that the to-be-detected page is abnormal; when the target number is less than the preset number, identifying a next unit time transmission frame number of a target unit time transmission frame number from the array of unit time transmission frame numbers; the target unit time transmission frame number is the last unit time transmission frame number in the unit time transmission frame numbers that are continuously lower than the unit time transmission frame number threshold; calculating an average value of the unit time transmission frame numbers that are continuously lower than the unit time transmission frame number threshold and the next unit time transmission frame number of the target unit time transmission frame number; when the average value is less than the unit time transmission frame number threshold, determining that the to-be-detected page is abnormal.

2. The page anomaly identification method of claim 1, wherein The method further comprises: when the to-be-detected page is in a visible state, listening to a frame request event of the to-be-detected page; when the frame request event of the to-be-detected page is detected, updating the execution times of the frame request event of the to-be-detected page and recording the execution time stamp of the frame request event of the to-be-detected page; when the difference between the execution time stamp and a start time stamp is greater than a preset difference, calculating the unit time transmission frame number of the to-be-detected page according to the difference and the updated execution times; the start time stamp represents the start time of the current unit time transmission frame number calculation; when the difference between the execution time stamp and the start time stamp is less than or equal to the preset difference, re-listening to the frame request event of the to-be-detected page until the difference between the execution time stamp of the detected frame request event and the start time stamp is greater than the preset difference.

3. The page anomaly identification method according to claim 2, characterized by, The method further comprises: when the to-be-detected page is in an invisible state, stopping listening to the frame request event of the to-be-detected page and calculating the total time of the to-be-detected page in the invisible state; The method further comprises: subtracting the difference from the total time of the to-be-detected page in the invisible state to obtain an updated difference; calculating the unit time transmission frame number of the to-be-detected page according to the updated difference and the updated execution times.

4. The page anomaly identification method of claim 1, wherein The method further comprises: obtaining a page identifier of the to-be-detected page; Obtain a unit time transmission frame number array corresponding to the page identifier as a unit time transmission frame number array of the page to be detected.

5. A page anomaly recognition apparatus characterized by comprising: Comprise: An obtaining unit configured to obtain a unit time transmission frame number array of a page to be detected; The unit time transmission frame number array includes a plurality of sequentially arranged unit time transmission frame numbers of the page to be detected; A determination unit configured to determine a target number of unit time transmission frame numbers that are continuously below a unit time transmission frame number threshold from the unit time transmission frame number array; An identification unit configured to determine an abnormality identification result of the page to be detected according to the target number; The obtaining unit is further configured to obtain a plurality of unit time transmission frame numbers of the page to be detected; Each unit time transmission frame number is identified by a corresponding acquisition time; and the plurality of unit time transmission frame numbers are stored in the unit time transmission frame number array in ascending order of the acquisition time; When the target number is greater than or equal to a preset number, the identification unit is further configured to determine that the page to be detected is abnormal; When the target number is less than the preset number, the identification unit is further configured to identify a next unit time transmission frame number of a target unit time transmission frame number from the unit time transmission frame number array; The target unit time transmission frame number is the last unit time transmission frame number in the unit time transmission frame numbers that are continuously below the unit time transmission frame number threshold; An average value of the unit time transmission frame numbers that are continuously below the unit time transmission frame number threshold and the next unit time transmission frame number of the target unit time transmission frame number is calculated; and when the average value is less than the unit time transmission frame number threshold, it is determined that the page to be detected is abnormal.

6. The page anomaly identification apparatus according to claim 5, characterized by The obtaining unit is further configured to listen to a frame request event of the page to be detected when the page to be detected is in a visible state; When the frame request event of the page to be detected is listened to, the number of executions of the frame request event of the page to be detected is updated, and an execution timestamp of the frame request event of the page to be detected is recorded; When a difference between the execution timestamp and a start timestamp is greater than a preset difference value, a unit time transmission frame number of the page to be detected is calculated according to the difference and the updated number of executions; The start timestamp represents a start time of the current unit time transmission frame number calculation; When the difference between the execution timestamp and the start timestamp is less than or equal to the preset difference value, the frame request event of the page to be detected is listened to again until the difference between the execution timestamp of the listened frame request event and the start timestamp is greater than the preset difference value.

7. The page anomaly identification apparatus according to claim 6, characterized by The page abnormality identification device further comprises a statistical unit configured to stop listening to the frame request event of the page to be detected when the page to be detected is in an invisible state, and to calculate a total time during which the page to be detected is in the invisible state; The acquisition unit is further configured to perform subtraction of the difference value from a total time during which the to-be-detected page is in an invisible state to obtain an updated difference value; and according to the updated difference value and an updated execution number, count a unit-time transmission frame number of the to-be-detected page.

8. The page anomaly identification apparatus according to claim 5, characterized by The acquisition unit is further configured to acquire a page identifier of the to-be-detected page; and acquire a unit-time transmission frame number array corresponding to the page identifier as a unit-time transmission frame number array of the to-be-detected page.

9. An electronic device, comprising: Comprise: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the page anomaly identification method according to any one of claims 1 to 4.

10. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device can perform the page anomaly identification method according to any one of claims 1 to 4.

11. A computer program product, comprising instructions therein, characterised in that, The instructions are executed by the processor of the electronic device, so that the electronic device can perform the page anomaly identification method according to any one of claims 1 to 4.

Images