Method and device for identifying anti-shake state of front-end interaction element

Abstract

One or more embodiments of the invention provide a method and a device for identifying an anti-shake state of a front-end interaction element. According to the method, based on a user session sequence, jump elements which do not adopt an anti-shake mechanism and the use frequency level of each jump element are identified. Then, a generated data table including jump elements that do not employ an anti-shake mechanism and use frequency levels of the jump elements is generated. Afterwards, in response to a received query request of a platform user for the anti-shake state of a front-end interaction element in a corresponding service product, a corresponding anti-shake state report is displayed to the platform user, so that the platform user can execute the anti-shake state report according to the use frequency level corresponding to each jump element which does not adopt the anti-shake mechanism in the anti-shake state report. And determining an anti-shake strategy for each jump element which does not adopt the anti-shake mechanism.

Description

TECHNICAL FIELD

[0001] One or more embodiments of the present specification relate to the technical field of computer network, and particularly relate to a method and device for identifying anti-shake state of front-end interactive element. BACKGROUND

[0002] With the rapid development of information technology, digital service products enrich people's life scenes. These digital service products can be presented in one or more applications or systems. Taking a payment service application as an example, the process of a terminal user using the payment service application is a process of the terminal user interacting with the front-end interactive elements of the payment service application.

[0003] In order to guarantee the fluency and stability of the page in the process of the terminal user interacting with the front-end interactive elements, in the related technology, the anti-shake strategy is mainly set for the front-end interactive elements in a static configuration manner. Specifically, the developer manually specifies which front-end interactive elements need to add an anti-shake mechanism and sets the corresponding anti-shake threshold according to his own experience.

[0004] However, this static configuration anti-shake strategy according to the developer's experience is difficult to comprehensively and accurately identify the front-end interactive elements that need to add the anti-shake strategy, so as to effectively balance the page performance and user experience. SUMMARY

[0005] In order to better balance the page performance and user experience, one or more embodiments of the present specification provide a method and device for identifying anti-shake state of front-end interactive element.

[0006] In a first aspect, one or more embodiments of the present specification provide a method for identifying anti-shake state of front-end interactive element, the method comprising: obtaining a plurality of user session sequences, wherein each user session sequence comprises at least one page session sub-sequence; extracting a first jump element from each page session sub-sequence, wherein the first jump element is a front-end interactive element satisfying a first condition, and the first condition is that in response to a click operation on a front-end interactive element located at a first page, jumping to a second page different from the first page; determining a usage frequency level of each first jump element; identifying a second jump element in each first jump element which does not adopt an anti-shake mechanism based on the user session sequence; and generating a data table, the data table comprising each second jump element and the usage frequency level corresponding to each second jump element respectively.

[0007] In a possible implementation manner, the extracting the first jump element from each page session sub-sequence comprises: determining whether a last operation behavior in each page session sub-sequence belongs to a click operation; in the case that the last operation behavior belongs to the click operation, determining that the front-end interactive element corresponding to the click operation satisfies the first condition; and extracting the front-end interactive element satisfying the first condition as the first jump element.

[0008] In a possible implementation, the second jump element that does not adopt the anti-shake mechanism is identified based on the user session sequence, including: based on the user session sequence, the first jump element that meets the second condition is identified as the second jump element that does not adopt the anti-shake mechanism, where the second condition includes that the first jump element opens multiple same second pages at the same time after being continuously clicked on the first page.

[0009] In a possible implementation, the usage frequency level of each first jump element is determined, including: obtaining actual usage frequencies of each first jump element in a preset time period; obtaining frequency thresholds respectively corresponding to the first jump elements; and determining the usage frequency level of each first jump element based on the actual usage frequency and the corresponding frequency threshold; where the usage frequency level of the first jump element with the actual usage frequency greater than the corresponding frequency threshold is high frequency, and the usage frequency level of the first jump element with the actual usage frequency less than or equal to the corresponding frequency threshold is low frequency.

[0010] In a possible implementation, each first jump element has a specific coding identifier, and the specific coding identifier is used to identify and distinguish each first jump element; where the actual usage frequency of each first jump element in a preset time period is obtained, including: the actual usage frequency of each first jump element in a preset time period is obtained through the specific coding identifier; and the actual usage frequency of each first jump element is determined based on the actual usage frequency and the preset time period.

[0011] In a possible implementation, the method further includes: marking the usage frequency level respectively corresponding to each first jump element.

[0012] In a possible implementation, after the data table is generated, the method further includes: in response to receiving a query request of a platform user for an anti-shake state of a front-end interaction element in a target service, querying the second jump element corresponding to the target service and the usage frequency level respectively corresponding to each second jump element from the data table; generating an anti-shake state report of the target service based on the second jump element corresponding to the target service and the usage frequency level respectively corresponding to each second jump element; and displaying the anti-shake state report to the platform user, so that the platform user determines an anti-shake strategy for each second jump element according to the usage frequency level respectively corresponding to each second jump element in the anti-shake state report.

[0013] In a second aspect, one or more embodiments of the present specification also provide a device for identifying an anti-shake state of a front-end interaction element, the device comprising: The obtaining module is configured to obtain a plurality of user session sequences, where each user session sequence includes at least one page session sub-sequence. extract a first jump element from each of the page session subsequences, wherein the first jump element is a front-end interaction element satisfying a first condition, and the first condition is that, in response to a click operation on the front-end interaction element located on a first page, a jump is made to a second page different from the first page; determine a usage frequency level of each of the first jump elements; identify, based on the user session sequence, a second jump element from each of the first jump elements that does not employ a debounce mechanism; generate a data table, the data table including each of the second jump elements and a usage frequency level corresponding to each of the second jump elements.

[0014] In a possible implementation, the extraction module is specifically configured to: determine whether a last operation behavior in each of the page session subsequences is a click operation, and in a case where the last operation behavior is the click operation, determine that a front-end interaction element corresponding to the click operation satisfies the first condition, and extract the front-end interaction element satisfying the first condition as the first jump element.

[0015] In a possible implementation, the identification module is specifically configured to: identify, based on the user session sequence, a first jump element satisfying a second condition as a second jump element that does not employ a debounce mechanism, wherein the second condition includes that, after the first jump element is continuously clicked on a first page, multiple same second pages are opened at the same time.

[0016] In a possible implementation, the determination module is specifically configured to: obtain an actual usage frequency of each of the first jump elements in a preset time period, obtain a frequency threshold corresponding to each of the first jump elements, and determine a usage frequency level of each of the first jump elements based on the actual usage frequency and the corresponding frequency threshold, wherein the usage frequency level of the first jump element with the actual usage frequency greater than the corresponding frequency threshold is high frequency, and the usage frequency level of the first jump element with the actual usage frequency less than or equal to the corresponding frequency threshold is low frequency.

[0017] In a possible implementation, each of the first jump elements has a specific coding identifier used to identify and distinguish each of the first jump elements, and the determination module is specifically configured to: obtain, through the specific coding identifier, an actual usage frequency of each of the first jump elements in a preset time period, and determine the actual usage frequency of each of the first jump elements based on the actual usage frequency and the preset time period.

[0018] In a possible implementation, the apparatus further includes: a marking module configured to mark a usage frequency level corresponding to each of the first jump elements.

[0019] In a possible implementation, the apparatus further includes: The query module is configured to, in response to receiving a query request of the platform user for the anti-shake state of the front-end interaction element in the target service, query the second jump elements corresponding to the target service and the use frequency levels respectively corresponding to each of the second jump elements from the data table; The anti-shake state report generation module is configured to generate an anti-shake state report of the target service based on the second jump elements corresponding to the target service and the use frequency levels respectively corresponding to each of the second jump elements; The display module is configured to display the anti-shake state report to the platform user, so that the platform user determines an anti-shake strategy for each of the second jump elements according to the use frequency levels respectively corresponding to each of the second jump elements in the anti-shake state report.

[0020] In a third aspect, one or more embodiments of the present specification also provide an electronic device, which includes a memory and a processor; the memory is configured to store a computer program product; the processor is configured to execute the computer program product stored in the memory, and when the computer program product is executed, the method for identifying the anti-shake state of the front-end interaction element of the first aspect is implemented.

[0021] In a fourth aspect, one or more embodiments of the present specification also provide a computer-readable storage medium, which stores computer program instructions, and when the computer program instructions are executed, the method for identifying the anti-shake state of the front-end interaction element of the first aspect is implemented.

[0022] In summary, one or more embodiments of the present specification provide a method and apparatus for identifying the anti-shake state of the front-end interaction element. In the method, the use frequency level of the first jump element is extracted and analyzed by obtaining the user session sequence, the second jump element that does not use the anti-shake mechanism is identified, and finally the data table and the anti-shake state report are generated, thereby providing the platform user with a scientific and dynamic anti-shake strategy decision basis. Compared with the traditional static configuration method relying on the experience of the developer, the method can more comprehensively and accurately identify the front-end interaction element that needs to add the anti-shake strategy, balance the page performance and user experience based on the actual use of the user, and better solve the performance overhead and page fluency problem caused by frequent clicking. BRIEF DESCRIPTION OF DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of one or more embodiments of the present specification, the drawings needed in the embodiment description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of one or more embodiments of the present specification, and other drawings can be obtained by those skilled in the art without creating any creative labor.

[0024] Figure 1 An application scenario diagram provided for one or more embodiments of the present specification; Figure 2 A flow diagram of a front-end interactive element anti-shake state identification method provided for one or more embodiments of the present specification; Figure 3 A structural block diagram of a front-end interactive element anti-shake state identification device provided for one or more embodiments of the present specification; Figure 4 A structural block diagram of an electronic device provided for one or more embodiments of the present specification. DETAILED DESCRIPTION

[0025] One or more embodiments of the present specification will be further described in detail below with the aid of the accompanying drawings and embodiments. Through these descriptions, the characteristics and advantages of one or more embodiments of the present specification will become more apparent.

[0026] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations. Although various aspects of embodiments are illustrated in the drawings, the drawings are not necessarily drawn to scale.

[0027] In addition, the technical features involved in different implementations of one or more embodiments of the present specification described below can be combined with each other as long as there is no conflict.

[0028] For ease of understanding, some technical terms related to one or more embodiments of the present specification will be described first.

[0029] 1. Front-end interactive element The front-end interactive element refers to a component or control that a user can directly see and interact with on a page displayed by a web page or application. For example, front-end interactive elements include buttons, input boxes, drop-down menus, radio buttons, check boxes, etc. on the front-end interface.

[0030] 2. Debounce mechanism The debounce mechanism is a technology used to improve page performance and optimize user interaction experience. Its core purpose is to reasonably control high-frequency triggering events in a short period of time. For example, high-frequency triggering events can include events triggered when entering content into an input box, corresponding events triggered when adjusting the size of a window, etc. The debounce mechanism limits the execution frequency of these high-frequency triggering events to avoid unnecessary performance overhead caused by frequent triggering, reduce the number of repeated network requests, or avoid excessive consumption of browser resources, thereby ensuring the smoothness and stability of the page.

[0031] With the rapid development of information technology, digital service products are enriching people's lives. For example, digital service products include a variety of services such as payment services, shopping services, travel services, utility bill payment services, and healthcare services, forming a service ecosystem that covers daily needs.

[0032] These digital service products can be presented in one or more applications or systems. Taking a payment service application as an example, the process of an end user using a payment service application is the process of the end user interacting with the front-end interactive elements of the payment service application.

[0033] To ensure the smoothness and stability of the page during interaction between end users and front-end interactive elements, related technologies primarily rely on static configuration to set debouncing strategies for these elements. Specifically, developers, based on their experience, manually specify which front-end interactive elements require debouncing mechanisms and set corresponding debouncing thresholds.

[0034] However, this method of statically configuring debouncing strategies based on developers' experience makes it difficult to comprehensively and accurately identify front-end interactive elements that require debouncing, thus making it difficult to effectively balance page performance and user experience.

[0035] To address the aforementioned technical problems, one or more embodiments of this specification provide a method for identifying the stabilization status of front-end interactive elements. This method, based on a user session sequence, identifies jump elements that do not employ stabilization mechanisms and the usage frequency level of each jump element. Then, a generated data table is created, including the jump elements that do not employ stabilization mechanisms and the usage frequency level of each jump element. Subsequently, in response to a query request from a platform user regarding the stabilization status of front-end interactive elements in their corresponding service product, a corresponding stabilization status report can be displayed to the platform user. This allows the platform user to determine a stabilization strategy for each jump element that does not employ stabilization mechanisms based on the usage frequency level corresponding to each jump element in the stabilization status report.

[0036] Figure 1 This is a schematic diagram illustrating an application scenario provided for one or more embodiments of this specification.

[0037] For example, such as Figure 1 As shown, this application scenario may include an experience management platform 10 and a user terminal 20. The user terminal 20 may run various service products such as service C1, service C2, ..., service Cn. Taking the centralized presentation of these service products in a single application as an example, the terminal user B1 interacts with the front-end of these service products.

[0038] The ordered behavior track generated based on the time dimension of the interaction process can be referred to as a user session sequence. The user session sequence records the whole-process interaction behavior of the user from initial contact to final conversion or loss. For example, the interaction behavior includes page access, module exposure, module click, page swipe, and the like.

[0039] The service C1, the service C2, and the service Cn can correspond to respective service providers, which can be platform users of the experience management platform 10. For example, the platform user corresponding to the service C1 is the platform user A1, the platform user corresponding to the service C2 is the platform user A2, and the platform user corresponding to the service Cn is the platform user An.

[0040] The experience management platform 10 can collect actual user session sequences generated when each terminal user (for example, the terminal user B1) Figure 1 The experience management platform 10 can collect actual user session sequences generated when each terminal user (for example, the terminal user B1)

[0041] Further, the experience management platform 10 can respond to a query request of the platform user for the anti-shake state of the front-end interaction element in the service product managed by the platform user, and display a corresponding anti-shake state report to the platform user, so that the platform user determines an anti-shake strategy for each front-end interaction element without an anti-shake mechanism according to the use frequency level of the front-end interaction element without the anti-shake mechanism in the anti-shake state report.

[0042] The following describes an embodiment of a method for identifying the anti-shake state of the front-end interaction element provided by one or more embodiments of the present specification.

[0043] Referring to Figure 2 , Figure 2 A flowchart of a method for identifying the anti-shake state of the front-end interaction element provided by one or more embodiments of the present specification. The method can be applied to a server, a terminal device, or an experience management platform or an electronic device running the experience management platform. The following takes the application to the experience management platform as an example to introduce the content of the embodiment. As shown in Figure 2 The method can include the following steps: Step S102, acquiring a plurality of user session sequences.

[0044] A user session sequence can focus on a series of interaction behaviors performed on one page or multiple pages. A series of interaction behaviors performed on each page can be referred to as a page session sub-sequence. That is, when a specific page is involved in the entire user session, a series of interaction behaviors performed by the user on the page, such as clicking a button, inputting information, in-page jumping, etc., constitutes a page session sub-sequence, and a user session sequence includes at least one such page session sub-sequence.

[0045] For example, a user session sequence includes: opening a home page - browsing a product recommendation block - clicking a search bar - jumping to a search page - inputting "sports shoes" - clicking search - jumping to a search result page - clicking a certain "sports shoes" - jumping to a detail page of sports shoes - clicking exit.

[0046] The above user session sequence can include the following four page session sub-sequences: Page session sub-sequence A: opening a home page - browsing a product recommendation block - clicking a search bar.

[0047] Page session sub-sequence B: jumping to a search page - inputting "sports shoes" - clicking search.

[0048] Page session sub-sequence C: jumping to a search result page - clicking a certain "sports shoes".

[0049] Page session sub-sequence D: jumping to a detail page of sports shoes - clicking exit.

[0050] Page session sub-sequence A is a series of interaction behaviors of the user on the home page. Page session sub-sequence B is a series of interaction behaviors of the user on the search page. Page session sub-sequence C is a series of interaction behaviors of the user on the search result page. Page session sub-sequence D is a series of interaction behaviors of the user on the detail page of sports shoes.

[0051] It should be noted that one or more embodiments of the present specification do not limit the specific implementation of obtaining the above user session sequence. For example, the user session sequence can be obtained by means of burying points on the user terminal. Further, the user session sequence can be filtered and processed to filter out repeated and invalid user session sequences.

[0052] Step S104, extracting a first jump element from each page session sub-sequence.

[0053] The first jump element is a front-end interaction element that meets a first condition. The first condition is that in response to a click operation on a front-end interaction element located on a first page, a second page different from the first page is jumped to.

[0054] In a possible implementation, the first jump element can be extracted from each page session subsequence in the following manner: determining whether the last operation behavior in each page session subsequence is a click operation; in the case where the last operation behavior is a click operation, determining that the front-end interaction element corresponding to the click operation satisfies a first condition; and extracting the front-end interaction element satisfying the first condition as the first jump element.

[0055] That is, the first condition is that, after the last operation behavior in the page session subsequence, no subsequent operation is performed on the current first page, but a jump is made to a second page different from the current first page.

[0056] For example, taking the page session subsequence A as an example, the last operation behavior in the page session subsequence A is a click on a search bar, which is a click operation. After the click on the search bar, no subsequent operation is performed on the first page (i.e., the home page) to which the search bar belongs. In this way, the front-end interaction element “search bar” corresponding to the click on the search bar can be extracted as the first jump element. Similarly, the front-end interaction element “search button” corresponding to the click on the search in the page session subsequence B can be extracted as the first jump element.

[0057] It should be noted that a plurality of first jump elements can be extracted from each page session subsequence in each user session sequence according to the above method, which will not be listed one by one here.

[0058] In step S106, the usage frequency level of each first jump element is determined.

[0059] The first jump element described above is a front-end interaction element that can trigger a page switch. Frequent triggering of these front-end interaction elements can easily cause unnecessary performance overhead and affect the smoothness and stability of the page. A debounce mechanism often needs to be used for frequently used first jump elements.

[0060] Based on this, one or more embodiments of the present specification can count the usage frequency level of each first jump element based on the actual usage of the user, to assist the platform user in deciding whether a debounce mechanism needs to be used.

[0061] In a possible implementation, the usage frequency level of each first jump element can be determined in the following manner: obtaining the actual usage frequency of each first jump element in a preset time period; obtaining the frequency threshold corresponding to each first jump element, respectively; and determining the usage frequency level of each first jump element based on the actual usage frequency and the corresponding frequency threshold. The usage frequency level of the first jump element whose actual usage frequency is greater than the corresponding frequency threshold is high frequency, and the usage frequency level of the first jump element whose actual usage frequency is less than or equal to the corresponding frequency threshold is low frequency.

[0062] Each first jump element can have a specific coding identifier for identifying and distinguishing each first jump element. In this way, the actual use frequency of each first jump element can be counted by the specific coding identifier in the preset time period. Then, the actual use frequency of each first jump element is determined based on the actual use frequency and the preset time period.

[0063] Each platform user can input the frequency threshold corresponding to each first jump element involved in the service product of each platform user in the experience management platform in advance.

[0064] In this way, the use frequency level corresponding to each first jump element can be determined according to the actual use frequency and the frequency threshold corresponding to each first jump element.

[0065] For example, taking the first jump element "search bar" as an example, the actual use frequency of the "search bar" is 15,000 times / hour, and the corresponding frequency threshold is 10,000 times / hour. Obviously, the actual use frequency of the "search bar" exceeds the corresponding frequency threshold, and therefore the use frequency level of the "search bar" can be determined as high frequency.

[0066] For example, taking the first jump element "search button" as an example, the actual use frequency of the "search button" is 10,000 times / hour, and the corresponding frequency threshold is 12,000 times / hour. Obviously, the actual use frequency of the "search button" does not exceed the corresponding frequency threshold, and therefore the use frequency level of the "search button" can be determined as low frequency.

[0067] In one possible implementation, determining the use frequency level of each first jump element can also be implemented in the following manner: obtaining the actual use frequency of each first jump element in a preset time period; determining the use frequency level of each first jump element based on the actual use frequency of each first jump element and a reference frequency threshold. The use frequency level of the first jump element with the actual use frequency greater than the reference frequency threshold is high frequency, and the use frequency level of the first jump element with the actual use frequency less than or equal to the reference frequency threshold is low frequency.

[0068] In this implementation, each first jump element can correspond to the same reference frequency threshold. In the case where the actual use frequency of the first jump element is greater than the reference frequency threshold, the use frequency level of the first jump element is high frequency. In the case where the actual use frequency of the first jump element is less than or equal to the reference frequency threshold, the use frequency level of the first jump element is low frequency.

[0069] In one possible implementation, after determining the use frequency level corresponding to each first jump element, the use frequency level corresponding to each first jump element can be marked.

[0070] In a possible implementation, after determining the use frequency levels corresponding to the first jump elements respectively, frequency level record information can also be generated, where the frequency level record information is used to record the use frequency levels corresponding to the first jump elements respectively.

[0071] In step S108, based on the user session sequences, the second jump elements that do not employ the anti-shake mechanism among the first jump elements are identified.

[0072] Specifically, it can be determined whether the first jump elements meet a second condition in the user session sequences corresponding to the first jump elements. If the first jump elements meet the second condition, the first jump elements are the second jump elements that do not employ the anti-shake mechanism. If the first jump elements do not meet the second condition, the first jump elements are the jump elements that employ the anti-shake mechanism.

[0073] The second condition includes that the first jump elements open multiple same second pages simultaneously after being clicked continuously on the first pages corresponding to the first jump elements. The continuous clicking refers to being clicked multiple times within a preset time length (which is a very short time length).

[0074] For example, the user session sequence includes a first jump element “click search”, and the “click search” is clicked continuously for 3 times, and 3 same “search result pages” are opened simultaneously. In this case, the first jump element “click search” meets the second condition.

[0075] According to the principle of the anti-shake mechanism, if the first jump element meets the second condition, it indicates that the anti-shake mechanism is not added to the first jump element.

[0076] It should be noted that in one or more embodiments of the present specification, the anti-shake state of the front-end interactive element includes that the front-end interactive element has employed the anti-shake mechanism and has not employed the anti-shake mechanism.

[0077] In step S110, a data table is generated, and the data table includes the second jump elements and the use frequency levels corresponding to the second jump elements respectively.

[0078] After obtaining the second jump elements and the use frequency levels corresponding to the second jump elements respectively based on the multiple user session sequences, the information can be integrated into a data table.

[0079] It should be noted that the data table can include the second jump elements corresponding to multiple service products.

[0080] Further, after the data table is generated, a query request for the anti-shake state of the front-end interactive element in a service product (which can be referred to as a target service) of a platform user can be received.

[0081] In response to receiving the query request of the platform user for the anti-shake state of the front-end interaction element in the target service, the second jump elements corresponding to the target service and the use frequency levels corresponding to each of the second jump elements are queried from the data table. Then, the anti-shake state report of the target service can be generated based on the second jump elements corresponding to the target service and the use frequency levels corresponding to each of the second jump elements.

[0082] Afterwards, the anti-shake state report can be displayed to the platform user, so that the platform user determines the anti-shake strategy for each second jump element according to the use frequency level corresponding to each second jump element in the anti-shake state report.

[0083] For example, the platform user can add an anti-shake mechanism for the second jump element belonging to high frequency in the anti-shake state report.

[0084] It should be noted that the above data table can be updated by acquiring the latest user session sequence in real time or at regular intervals. In this way, the platform user can query the latest anti-shake state report to dynamically decide the anti-shake strategy according to the latest anti-shake state report. Since the anti-shake strategy is based on the actual use of the user, the page performance and user experience can be effectively balanced.

[0085] The method for identifying the anti-shake state of the front-end interaction element provided by one or more embodiments of the present specification includes obtaining a user session sequence, extracting and analyzing the use frequency level of the first jump element, identifying the second jump element that does not use the anti-shake mechanism, and finally generating a data table and an anti-shake state report, thereby providing a scientific and dynamic anti-shake strategy decision basis for the platform user. Compared with the traditional static configuration method relying on the experience of the developer, the method can more comprehensively and accurately identify the front-end interaction element that needs to add an anti-shake strategy, balance the page performance and user experience based on the actual use of the user, and better solve the performance overhead and page fluency problems caused by frequent clicks.

[0086] It can be understood that the above embodiments are only examples, and the above embodiments can be deformed in actual implementation. Those skilled in the art can understand that the deformed methods of the above embodiments without creative labor fall within the protection scope of one or more embodiments of the present specification, and the embodiments will not be described again.

[0087] Based on the same inventive concept, one or more embodiments of the present specification also provide an anti-shake state identification device for a front-end interaction element. Since the anti-shake state identification device for the front-end interaction element solves the same problem as the anti-shake state identification method for the front-end interaction element, the implementation of the anti-shake state identification device for the front-end interaction element can be referred to the implementation of the anti-shake state identification method for the front-end interaction element, and the repeated parts will not be described again.

[0088] Referring to Figure 3 , Figure 3 A structural block diagram of an identification device of a front-end interactive element anti-shake state is provided for one or more embodiments of the present specification. As shown in Figure 3 , the identification device of the front-end interactive element anti-shake state 300 can include an acquisition module 301, an extraction module 302, a determination module 303, an identification module 304, and a data table generation module 305. Among them, The acquisition module 301 is configured to acquire a plurality of user session sequences, wherein each user session sequence includes at least one page session sub-sequence; The extraction module 302 is configured to extract a first jump element from each page session sub-sequence, wherein the first jump element is a front-end interactive element that meets a first condition, and the first condition is that in response to a click operation on a front-end interactive element located on a first page, jumping to a second page different from the first page; The determination module 303 is configured to determine the usage frequency level of each first jump element; The identification module 304 is configured to identify a second jump element that does not adopt an anti-shake mechanism in each first jump element based on the user session sequence; The data table generation module 305 is configured to generate a data table, and the data table includes each second jump element and the usage frequency level corresponding to each second jump element, respectively.

[0089] In a possible implementation manner, the extraction module 302 is specifically configured to: determine whether the last operation behavior in each page session sub-sequence belongs to a click operation; in the case that the last operation behavior belongs to a click operation, determine that the front-end interactive element corresponding to the click operation meets the first condition; and extract the front-end interactive element that meets the first condition as the first jump element.

[0090] In a possible implementation manner, the identification module 304 is specifically configured to: based on the user session sequence, identify a first jump element that meets a second condition as a second jump element that does not adopt an anti-shake mechanism, wherein the second condition includes that the first jump element is continuously clicked on the first page, and simultaneously opens a plurality of same second pages.

[0091] In a possible implementation manner, the determination module 303 is specifically configured to: acquire the actual usage frequency of each first jump element in a preset time period; acquire the frequency threshold value corresponding to each first jump element, respectively; and determine the usage frequency level of each first jump element based on the actual usage frequency and the corresponding frequency threshold value; wherein the usage frequency level of the first jump element whose actual usage frequency is greater than the corresponding frequency threshold value is high frequency, and the usage frequency level of the first jump element whose actual usage frequency is less than or equal to the corresponding frequency threshold value is low frequency.

[0092] In a possible implementation, each first jump element has a specific coding identifier, and the specific coding identifier is used to identify and distinguish each first jump element; the determining module 303 is specifically configured to: obtain the actual use frequency of each first jump element in a preset time period through the specific coding identifier; and determine the actual use frequency of each first jump element based on the actual use frequency and the preset time period.

[0093] In a possible implementation, the apparatus further includes: The marking module is configured to mark the use frequency level corresponding to each first jump element.

[0094] In a possible implementation, the apparatus further includes: The querying module is configured to, in response to receiving a query request for the anti-shake state of the front-end interactive element in the target service from the platform user, query the second jump element corresponding to the target service and the use frequency level corresponding to each second jump element from the data table; The anti-shake state report generation module is configured to generate an anti-shake state report of the target service based on the second jump element corresponding to the target service and the use frequency level corresponding to each second jump element; The display module is configured to display the anti-shake state report to the platform user, so that the platform user determines an anti-shake strategy for each second jump element according to the use frequency level corresponding to each second jump element in the anti-shake state report.

[0095] Referring to Figure 4 , Figure 4 A structural block diagram of an electronic device is provided for one or more embodiments of the present specification. As Figure 4 shown, the electronic device 400 can include a processor 401 and a memory 402; the memory 402 can be coupled to the processor 401. Notably, the Figure 4 is exemplary; other types of structures can also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0096] In a possible implementation, the function of the front-end interactive element anti-shake state identification apparatus 300 can be integrated into the processor 401. Wherein, the processor 401 can be configured to perform the following operations: Obtaining a plurality of user session sequences, wherein each user session sequence comprises at least one page session sub-sequence; extracting a first jump element from each page session sub-sequence, wherein the first jump element is a front-end interaction element satisfying a first condition, and the first condition is that, in response to a click operation on the front-end interaction element located on a first page, jumping to a second page different from the first page; determining a usage frequency level of each first jump element; identifying a second jump element in each first jump element which does not adopt a debounce mechanism based on the user session sequence; and generating a data table, the data table comprising each second jump element and a usage frequency level corresponding to each second jump element respectively.

[0097] In another possible implementation, the front-end interaction element debounce state identification apparatus 300 can be configured separately from the processor 401, for example, the front-end interaction element debounce state identification apparatus 300 can be configured as a chip connected with the processor 401, and the front-end interaction element debounce state identification is realized through the control of the processor 401.

[0098] In addition, in some optional implementations, the electronic device 400 can further include a communication module, an input unit, an audio processor, a display, a power supply, etc. It should be noted that the electronic device 400 does not necessarily include all the components shown in Figure 4 In addition, the electronic device 400 can further include components not shown in Figure 4 In addition, the electronic device 400 can further include components not shown in

[0099] In some optional implementations, the processor 401, also sometimes referred to as a controller or operating control, can include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of the electronic device 400.

[0100] The memory 402, for example, can be one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. Information related to the front-end interaction element debounce state identification apparatus 300 described above can be stored, and programs for executing the related information can also be stored. The processor 401 can execute the programs stored in the memory 402 to achieve information storage or processing, etc.

[0101] The input unit can provide input to the processor 401. The input unit is, for example, a key or a touch input device. The power supply can be used to provide power to the electronic device 400. The display can be used for displaying display objects such as images and text. The display can be, for example, an LCD display, but is not limited thereto.

[0102] The memory 402 can be a solid state memory such as a read only memory (ROM), a random access memory (RAM), a SIM card, and the like. It can also be a memory that retains information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes referred to as an EPROM, and the like. The memory 402 can also be some other type of device. The memory 402 includes a buffer memory (sometimes referred to as a buffer). The memory 402 can include an application / function storage section for storing application programs and function programs or a flow for executing the operation of the electronic device 400 by the processor 401.

[0103] The memory 402 can also include a data storage section for storing data such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver program storage section of the memory 402 can include various driver programs of the computer device for a communication function and / or for performing other functions of the computer device such as a messaging application, an address book application, and the like.

[0104] The communication module is a transmitter / receiver that transmits and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor 401 to provide input signals and receive output signals, which can be the same as in the case of a conventional mobile communication terminal.

[0105] Based on different communication technologies, a plurality of communication modules such as a cellular network module, a Bluetooth module, and / or a wireless local area network module, and the like can be provided in the same computer device. The communication module (transmitter / receiver) is also coupled to a speaker and a microphone via an audio processor to provide audio output via the speaker and receive audio input from the microphone, thereby implementing a general telecommunication function. The audio processor can include any suitable buffer, decoder, amplifier, and the like. In addition, the audio processor is also coupled to the processor 401, thereby enabling recording on the local by the microphone and enabling playing of a sound stored on the local by the speaker.

[0106] One or more embodiments of the present specification also provide a computer readable storage medium capable of implementing all steps of the front-end interactive element anti-shake state recognition method in the above embodiments, and the computer program is stored on the computer readable storage medium, and the computer program is executed by the processor to implement all steps of the front-end interactive element anti-shake state recognition method in the above embodiments, for example, the processor executes the computer program to implement the following steps: A plurality of user session sequences are acquired, each user session sequence comprising at least one page session sub-sequence; a first jump element is extracted from each page session sub-sequence, the first jump element being a front-end interaction element satisfying a first condition, the first condition being that, in response to a click operation on the front-end interaction element located on a first page, jumping to a second page different from the first page; a usage frequency level of each first jump element is determined; based on the user session sequences, a second jump element that does not employ a debounce mechanism is identified from each first jump element; and a data table is generated, the data table comprising each second jump element and a usage frequency level corresponding to each second jump element respectively.

[0107] Although the method operation steps provided by the one or more embodiments of the specification are as described in the embodiments or flowcharts, more or fewer operation steps can be included based on routine or non-creative labor. The order of steps listed in the embodiments is only one of the many execution orders of the steps, and does not represent the only execution order. In actual device or client product execution, the method order shown in the embodiments or the drawings can be executed in sequence or in parallel (for example, in a parallel processor or multi-thread processing environment).

[0108] Those skilled in the art will appreciate that the embodiments of the specification can be provided as a method, device (system) or computer program product. Therefore, the embodiments of the specification can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, one or more embodiments of the specification can take the form of a computer program product embodied in one or more computer usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

[0109] One or more embodiments of the specification are described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to one or more embodiments of the specification. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce a device that implements the functions specified in the flowcharts and / or block diagrams. Figure 1 The device that implements the functions specified in one or more flows and / or blocks Figure 1 The device that implements the functions specified in one or more flows and / or blocks

[0110] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flow or flows and / or blocks Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0112] Each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts among the embodiments can be mutually referred to, and each of the embodiments focuses on the difference from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0113] In this document, the terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. In addition, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. The above terms can be understood in the specific meaning in one or more embodiments of the present specification according to the specific circumstances.

[0114] It should be noted that the one or more embodiments of the present specification and the features in the embodiments can be combined with each other without conflict. The one or more embodiments of the present specification are not limited to any single aspect, nor to any single embodiment, nor to any combination and / or permutation of aspects and / or embodiments. Further, each of the aspects and / or embodiments of the one or more embodiments of the present specification can be used alone or in combination with one or more other aspects and / or embodiments.

[0115] It should be noted that the above-mentioned embodiments are only used to explain the technical solutions of one or more embodiments of the present specification, but not to limit them. Although the one or more embodiments of the present specification are described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can still be modified, or some or all of the technical features can be replaced by equivalents. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the one or more embodiments of the present specification, and they should be covered in the scope of the claims and the specification of the one or more embodiments of the present specification.

[0116] The one or more embodiments of the present specification are described above in combination with optional embodiments, but these embodiments are only exemplary and serve only to illustrate. On this basis, various substitutions and improvements can be made to the one or more embodiments of the present specification, which all fall within the protection scope of the one or more embodiments of the present specification.

Claims

1. A method for identifying a front-end interactive element anti-shake state, characterized in that, The method comprises: obtaining a plurality of user session sequences, wherein each of the user session sequences comprises at least one page session sub-sequence; extracting a first jump element from each of the page session sub-sequences, wherein the first jump element is a front-end interactive element satisfying a first condition, and the first condition is that, in response to a click operation on a front-end interactive element located on a first page, jumping to a second page different from the first page; determining a usage frequency level of each of the first jump elements; based on the user session sequences, identifying a second jump element from each of the first jump elements that does not employ a debounce mechanism; generating a data table comprising each of the second jump elements and the usage frequency level corresponding to each of the second jump elements, respectively.

2. The method of claim 1, wherein, The method comprises: determining whether the last operation behavior in each of the page session sub-sequences is a click operation; in the case where the last operation behavior is a click operation, determining that the front-end interactive element corresponding to the click operation satisfies the first condition; extracting the front-end interactive element satisfying the first condition as the first jump element.

3. The method of claim 1, wherein, The method comprises: based on the user session sequences, identifying a second jump element from each of the first jump elements that does not employ a debounce mechanism, wherein the second condition comprises that the first jump element is opened simultaneously with multiple identical second pages after being clicked continuously on the first page.

4. The method of claim 1, wherein, The method comprises: obtaining the actual usage frequency of each of the first jump elements in a preset time period; obtaining the frequency threshold value corresponding to each of the first jump elements, respectively; based on the actual usage frequency and the corresponding frequency threshold value, determining the usage frequency level of each of the first jump elements; wherein the usage frequency level of the first jump element whose actual usage frequency is greater than the corresponding frequency threshold value is high frequency, and the usage frequency level of the first jump element whose actual usage frequency is less than or equal to the corresponding frequency threshold value is low frequency.

5. The method of claim 4, wherein, Each of the first jump elements has a specific code identifier for identifying and distinguishing each of the first jump elements. The method comprises: obtaining the actual usage frequency of each of the first jump elements in a preset time period through the specific code identifier; based on the actual usage frequency and the preset time period, determining the actual usage frequency of each of the first jump elements.

6. The method of claim 4 or 5, wherein, The method further comprises: labeling the usage frequency level corresponding to each of the first jump elements, respectively.

7. The method of claim 1, wherein, After generating the data table, the method further comprises: in response to receiving a query request for the debounce state of a front-end interactive element in a target service from a platform user, querying the second jump element corresponding to the target service and the usage frequency level corresponding to each of the second jump elements from the data table; generate a shake state report of the target service based on the second jump elements corresponding to the target service and the frequency levels of the second jump elements respectively; display the shake state report to the platform user, so that the platform user determines a shake strategy for each second jump element according to the frequency levels of the second jump elements in the shake state report.

8. A device for identifying a front-end interactive element anti-jitter state, characterized in that, The apparatus comprises: an acquisition module configured to acquire a plurality of user session sequences, wherein each user session sequence comprises at least one page session sub-sequence; an extraction module configured to extract first jump elements from each page session sub-sequence, wherein the first jump elements are front-end interaction elements satisfying a first condition, and the first condition is that, in response to a click operation on a front-end interaction element located on a first page, jumping to a second page different from the first page; a determination module configured to determine frequency levels of the first jump elements; an identification module configured to identify, based on the user session sequences, second jump elements in the first jump elements that do not employ a shake mechanism; a data table generation module configured to generate a data table comprising the second jump elements and the frequency levels of the second jump elements respectively.

9. The apparatus of claim 8, wherein, The extraction module is specifically configured to: determine whether a last operation behavior in each page session sub-sequence is a click operation, and in the case where the last operation behavior is a click operation, determine that a front-end interaction element corresponding to the click operation satisfies the first condition, and extract the front-end interaction element satisfying the first condition as a first jump element.

10. The apparatus of claim 8, wherein, The identification module is specifically configured to: identify, based on the user session sequences, a first jump element satisfying a second condition as a second jump element that does not employ a shake mechanism, wherein the second condition comprises that the first jump element is continuously clicked and simultaneously opens a plurality of identical second pages.

11. The apparatus of claim 8, wherein, The determination module is specifically configured to: acquire actual frequency of each first jump element in a preset time period, acquire frequency thresholds corresponding to the first jump elements respectively, and determine the frequency levels of the first jump elements based on the actual frequency and the frequency thresholds corresponding thereto, wherein the frequency level of a first jump element whose actual frequency is greater than the corresponding frequency threshold is high frequency, and the frequency level of a first jump element whose actual frequency is less than or equal to the corresponding frequency threshold is low frequency.

12. The apparatus of claim 11, wherein, Each first jump element has a specific code identifier for identifying and distinguishing the first jump elements; and the determination module is specifically configured to: acquire actual use times of each first jump element in a preset time period through the specific code identifier, and determine the actual frequency of each first jump element based on the actual use times and the preset time period.

13. The apparatus of claim 11 or 12, wherein, The apparatus further comprises: a marking module configured to mark the frequency levels of the first jump elements respectively.

14. The apparatus of claim 8, wherein, The apparatus further comprises: The query module is configured to, in response to receiving a query request for a jitter-proof state of a front-end interaction element in a target service from a platform user, query, from the data table, second jump elements corresponding to the target service and a use frequency level corresponding to each of the second jump elements; The jitter-proof state report generation module is configured to generate a jitter-proof state report of the target service based on the second jump elements corresponding to the target service and the use frequency level corresponding to each of the second jump elements; The display module is configured to display the jitter-proof state report to the platform user, so that the platform user determines a jitter-proof strategy for each of the second jump elements according to the use frequency level corresponding to each of the second jump elements in the jitter-proof state report.

15. An electronic device, comprising: The electronic device comprises: a memory configured to store a computer program product; a processor configured to execute the computer program product stored in the memory, and when the computer program product is executed, the method in any one of claims 1-7 is implemented.

16. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and when the computer program instructions are executed, the method in any one of claims 1-7 is implemented.

Images