Page browsing data processing method and device, equipment and storage medium

Abstract

The application relates to the technical field of data processing, and discloses a page browsing data processing method and device, equipment and a storage medium, which comprises the following steps: updating a page level stack according to a page state change event collected by a monitoring component to obtain an effective display page; constructing standardized behavior data according to an effective browsing duration of the effective display page and page information corresponding to the page state change event; obtaining a semantic template corresponding to the effective display page, filling the standardized behavior data into the semantic template, and generating semantic description data. The effective browsing duration of a real visual page under multi-frame nesting is filtered through the page level stack, discrete page state data is converted into semantic description carrying a user operation intention in combination with the semantic template, the collected data is upgraded from simple numerical recording to semantic information which can directly support user portrait, personalized recommendation and other upper-layer services, and the data utilization rate is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, device and storage medium for processing page browsing data. Background Technology

[0002] In the field of Android mobile application development, page view duration is a core foundational data for user behavior analysis, user profile construction, and personalized recommendations. However, existing page view duration collection methods can only collect raw, structured basic data such as page dwell time and page identifiers. They cannot perform semantic analysis of user page view behavior, and can only output numerical data. They cannot uncover deeper business information such as user interests, preferences, and operational intentions behind user behavior, resulting in low data utilization. Summary of the Invention

[0003] The main purpose of this application is to provide a page browsing data processing method, apparatus, device and storage medium, which aims to solve the technical problem that existing page duration can only output numerical data and cannot extract deeper business information such as user interests and operational intentions behind user behavior, resulting in low data utilization.

[0004] To achieve the above objectives, this application proposes a page browsing data processing method, the method comprising: The page hierarchy stack is updated based on the page state change events collected by the listening component to obtain the effectively displayed page; Standardized behavioral data is constructed based on the effective browsing time of the effectively displayed page and the page information corresponding to the page state change event; Obtain the semantic template corresponding to the effective display page, and fill the standardized behavioral data into the semantic template to generate semantic description data.

[0005] Optionally, updating the page hierarchy stack based on page state change events collected by the listening component to obtain a valid display page includes: Obtain the first page and change type corresponding to the page state change event, where the first page is the page whose page state has changed, and the change type includes at least one of push type, pop type, and replacement type; The page hierarchy stack is updated according to the change type and the first page; Based on the updated top page and the second page in the page hierarchy stack, the valid display page is determined. The second page is the page corresponding to the current timing subject, and the current timing subject is the page currently granted browsing time timing permission.

[0006] Optionally, updating the page hierarchy stack based on the change type and the first page includes: When the change type is a push type, the first page is pushed onto the current top of the page hierarchy stack, and it is determined whether to switch the current timing subject to the first page according to the preset page hierarchy priority rules. When the change type is a pop type, the top page of the page hierarchy stack is popped, and based on the timing status of the popped top page, it is determined whether to roll back the current timing subject to the top page of the current stack. When the change type is a replacement type, the top page of the page hierarchy stack is replaced with the first page, and the current timing subject is switched to the first page.

[0007] Optionally, before updating the page hierarchy stack based on page state change events collected by the listening component to obtain a valid display page, the process further includes: In response to the initialization result of the application program, a lifecycle listening component is registered for the application program. The lifecycle listening component includes a global page lifecycle callback interface, a global fragment lifecycle listening interface, and a route page switching listening interface. The lifecycle monitoring component collects page state change events of the application program.

[0008] Optionally, before constructing standardized behavioral data based on the effective browsing duration of the effectively displayed page and the page information corresponding to the page state change event, the method further includes: Acquire system device status events and user interaction behavior events, which are triggered when the listening component collects page status change events; The pause duration of the valid display page is determined based on the system device status events and the user interaction behavior events; The effective browsing time is determined based on the pause duration and the browsing time of the effective displayed page.

[0009] Optionally, determining the pause duration of the valid display page based on the system device status event and the user interaction behavior event includes: When the system device status event indicates that the device enters a non-interactive state, the first pause start time is recorded, and when the device returns to the interactive state, the first pause end time is recorded. The first pause duration is determined based on the first pause start time and the first pause end time. When the user interaction event indicates that the effective display page has no operation within a preset time threshold, the second pause start time is recorded, and the second pause end time is recorded when the user re-interacts. The second pause duration is determined based on the second pause start time and the second pause end time. The pause duration of the effective display page is determined based on the first pause duration and the second pause duration.

[0010] Optionally, the step of filling the standardized behavioral data into the corresponding semantic template to generate semantic description data includes: Obtain the page identifier and user interaction behavior of the effectively displayed page; Based on the page identifier and the user interaction behavior, determine a semantic template that matches the standardized behavior data; The standardized behavioral data is filled into the semantic template to obtain the filled semantic template; Based on the filled semantic template, semantic description data is generated to describe the user's browsing intent.

[0011] Furthermore, to achieve the above objectives, this application also proposes a page browsing data processing apparatus, which includes: The update module is used to update the page hierarchy stack based on the page state change events collected by the listening component, so as to obtain a valid display page; The construction module is used to construct standardized behavioral data based on the effective browsing time of the effective display page and the page information corresponding to the page state change event; The generation module is used to obtain the semantic template corresponding to the effective display page, and fill the standardized behavior data into the semantic template to generate semantic description data.

[0012] In addition, to achieve the above objectives, this application also proposes a page browsing data processing device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the page browsing data processing method described above.

[0013] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the page browsing data processing method described above.

[0014] This application utilizes a page hierarchy stack to filter the effective browsing time of real visual pages under multiple nested frames, and combines semantic templates to transform discrete page state data into semantic descriptions carrying user operation intentions. Through templated configuration, semantic parsing can be rapidly expanded without modifying the core code. This upgrades the collected data from simple numerical records to semantic information that can directly support upper-level business such as user profiling and personalized recommendations, significantly improving data utilization. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating the first embodiment of the page browsing data processing method of this application; Figure 2 This is a schematic diagram of the structure of the page browsing data processing system of this application; Figure 3 This is a flowchart illustrating the second embodiment of the page browsing data processing method of this application; Figure 4 This is a flowchart illustrating the third embodiment of the page browsing data processing method of this application; Figure 5 This is a schematic diagram of the module structure of the page browsing data processing device according to an embodiment of this application; Figure 6 This is a schematic diagram of the device structure of the hardware operating environment involved in the page browsing data processing method in the embodiments of this application.

[0018] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0019] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0020] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0021] In the current Android mobile application development field, page view duration collection is a core foundation for user behavior analysis, user profile construction, and personalized content recommendation, and is widely used in various Android client scenarios such as finance, e-commerce, and news. Currently, industry-standard Android application page view duration statistics solutions mainly rely on a single page lifecycle or a single routing framework to collect data, which is only suitable for simple, single-page navigation scenarios.

[0022] Existing Android page duration collection technologies generally suffer from limitations in scenario adaptation. Current mainstream Android projects commonly employ a development model that mixes multiple page containers and multiple routing frameworks, and also involve various page display and navigation formats such as Activity, nested Fragments, custom routes, and Jetpack Navigation. Traditional collection solutions can only monitor a single dimension of the page lifecycle and cannot recognize the characteristics of scenarios with multi-level page nesting and overlapping route navigation, leading to problems such as missed statistics, duplicate statistics, and duration gaps in page view duration statistics.

[0023] Meanwhile, existing technologies can only collect basic structured data such as raw page dwell time and page identifiers, and cannot perform semantic analysis of user page browsing behavior. They can only output cold numerical data and cannot mine deeper business information such as user interests and operational intentions behind user behavior. The data utilization rate is extremely low, making it difficult to support upper-level business scenarios such as accurate user profiling, personalized recommendations, and user experience optimization. It cannot meet the current development needs of intelligent and refined operation of Android applications.

[0024] Therefore, this application dynamically updates the page hierarchy stack by listening to page state change events collected by the component, accurately identifying the currently valid display page. This fundamentally avoids problems such as missed duration statistics, duplicate statistics, and incorrect statistical subjects caused by unclear page hierarchy in scenarios with multiple nested pages and mixed routing. On this basis, the effective browsing time and page information are structurally assembled according to a unified data model to generate standardized behavioral data, breaking the limitations of traditional solutions with chaotic output fields and missing dimensions. Furthermore, the standardized behavioral data is filled into semantic templates to generate semantic description data, giving the basic behavioral data semantic attributes at the level of user browsing intent. This upgrades the collected data from simple numerical records to understandable and inferable semantic information that can directly support upper-level business such as user profiling and personalized recommendations, significantly improving data utilization and intelligence level.

[0025] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device capable of performing the above functions. The following description uses a page browsing data processing device as an example to illustrate this embodiment and the subsequent embodiments.

[0026] Based on this, embodiments of this application provide a page browsing data processing method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the page browsing data processing method of this application.

[0027] In this embodiment, the page browsing data processing method includes: Step S10: Update the page hierarchy stack based on the page state change events collected by the listening component to obtain a valid display page.

[0028] It should be noted that page state change events are collected and reported by pre-registered listening components to characterize state changes such as page switching, overwriting, or exiting in the Android application. These listening components include a global page lifecycle callback interface, a global fragment lifecycle listening interface, and a route page switching listening interface, used to monitor state changes for Activity pages, Fragment pages, and Navigation route pages, respectively. The page hierarchy stack is a data structure maintained in memory, used to record all currently active pages and their hierarchical relationship, with the top page of the stack being the page currently visible to the user.

[0029] Specifically, when a page state change event is triggered, the page and event type corresponding to the event can be parsed. Event types include at least page push (i.e., a new page is opened and covers the current page), page pop (i.e., the current page is closed or back), and page replacement (i.e., the top page of the stack is directly replaced by a new page). Based on the event type, corresponding update operations can be performed on the page hierarchy stack. For example, for push events, the target page is pushed onto the top of the page hierarchy stack; for pop events, the top page is popped; for replacement events, the top page is removed and the target page is placed as the new top page. After completing the above update operations, the top page is read from the updated page hierarchy stack and determined as the valid display page.

[0030] It should be understood that the effective display page represents the page that the user is actually viewing at the current moment. Subsequent time-accumulation operations all revolve around the effective display page, thereby ensuring that the page that should be timed can always be accurately located in complex scenarios such as multiple nested pages and overlapping routes.

[0031] It should be noted that the page state change events collected by the listening component may be triggered intensively within a certain time window (for example, Activity switching and Fragment switching occur at the same time). In order to ensure the consistency of the page hierarchy stack state, the system can perform timing alignment and deduplication processing on the above events in the global event scheduling center.

[0032] Step S20: Construct standardized behavioral data based on the effective browsing duration of the effectively displayed page and the page information corresponding to the page state change event.

[0033] In this embodiment, the standardized behavioral data refers to page browsing behavior records obtained by structuring and assembling them according to a preset unified data model. These page browsing behavior records have a fixed set of fields and data type specifications.

[0034] Understandably, after obtaining the effective browsing time, the collected effective browsing time data, basic page information, page hierarchy information, user interaction status, device status, access time, and other multi-dimensional page information can be integrated and structurally assembled according to a preset unified data model. The standardized data fields after assembly include the page's unique identifier, page name, effective browsing time, page entry method, page hierarchy, interaction period, device status, and user behavior type.

[0035] It should be understood that standardized behavioral data can achieve a unified format for behavioral data across all scenarios, avoid the problems of chaotic data dimensions and missing fields in multiple scenarios, and provide a standardized data foundation for subsequent semantic parsing.

[0036] Step S30: Obtain the semantic template corresponding to the effective display page, and fill the standardized behavior data into the semantic template to generate semantic description data.

[0037] It should be noted that the semantic template is a pre-configured template used to convert structured behavioral data into natural language descriptions. The semantic template may contain statement frames and parameter placeholders set in the statement frames. The parameter placeholders are empty spaces in the statement frames to be filled with specific data content. Each parameter placeholder is associated with a preset parameter name, and the parameter name has a mapping relationship with the field name in the standardized behavioral data.

[0038] It should be understood that semantic templates correspond to page types or business scenarios. Different page types or business scenarios are associated with different semantic templates to adapt to the differentiated expression needs of user behavioral intentions in different business domains. Semantic description data is readable natural language text generated by filling the structured information such as specific values ​​and identifiers in standardized behavioral data into semantic templates. It can endow the data with intuitive semantic meaning and business interpretation value while retaining all the information of the original behavioral data.

[0039] Specifically, semantic templates corresponding to various pages and user behaviors can be pre-generated, with each semantic template corresponding to a unique logic for interpreting behavioral intent. During semantic parsing, standardized structured behavioral data is automatically retrieved, accurately matched to the corresponding semantic template, and automatically populated with parameters such as page attributes, browsing duration, and interaction characteristics. This transforms cold, numerical behavioral data into natural language semantic descriptions that can identify user interests and operational intentions. For example, for prolonged browsing of a financial product details page, a semantic description is automatically generated: "The user actively entered the financial product details page, with an effective browsing time of 48 seconds, without any redirects or exits, indicating that the user has a deep understanding of the financial product and exhibits potential investment preferences."

[0040] Optionally, before performing semantic template matching, different types of semantic templates can be generated based on historical browsing behavior sequences. Specifically, page sample data corresponding to each business type tag can be obtained. The page sample data includes page identifiers, page functional attributes, and the historical browsing behavior sequences generated by users on the page. For any business type tag, a statement frame adapted to that business type tag is generated based on the page functional attributes corresponding to that business type tag. The statement frame is a natural language sentence skeleton containing one or more parameter placeholders, and different business type tags correspond to different statement frames. At the same time, statistical analysis is performed on the historical browsing behavior sequences to determine the expression method of each behavior parameter in the statement frame, and then the filling rules for each parameter placeholder are determined. The filling rules include the conversion logic from parameter values ​​to natural language expressions. For example, the filling rule for browsing duration can be set to "more than 30 seconds is described as deep browsing, less than 30 seconds is described as fast browsing"; the filling rule for page entry method can be set to "click to enter is described as active entry, back to enter is described as returning to view". After completing the above configuration, the statement framework, the parameter placeholders, and the filling rules can be encapsulated into a semantic template. The semantic template can then be associated with the business type tag and stored in a pre-set semantic template library. When a new business scenario is added, the extension can be achieved simply by configuring a new semantic template according to the above process and registering it in the pre-set semantic template library.

[0041] In the specific implementation process, page identifiers and user interaction behaviors of valid display pages can be obtained. Based on the page identifiers and user interaction behaviors, corresponding semantic templates can be accurately matched. Standardized behavioral data is then filled into the semantic templates to generate semantic description data in natural language form. This achieves automated conversion from structured numerical data to readable and understandable natural language semantic data, enabling upper-layer business systems to directly obtain semantic information containing user interests, preferences, and operational intentions without additional data understanding and processing, significantly reducing the data usage threshold on the business side. At this time, step S30 may include: Obtain the page identifier and user interaction behavior of the effectively displayed page; Based on the page identifier and the user interaction behavior, determine a semantic template that matches the standardized behavior data; The standardized behavioral data is filled into the semantic template to obtain the filled semantic template; Based on the filled semantic template, semantic description data is generated to describe the user's browsing intent.

[0042] Specifically, the system first extracts page identifiers and user interaction behavior types from standardized behavioral data. The standardized behavioral data is structured and assembled according to a unified data model, including a unique page identifier field and a user interaction behavior type field. The page identifier uniquely identifies a page instance or a type of page within the application's global scope, while the user interaction behavior type characterizes the user's operation on that page, such as clicking to view, swiping to browse, or entering a query. The page identifier reflects which page the user browsed on, and the user interaction behavior type reflects how the user interacted with the content on that page. Based on this, using the page identifier as the first matching key, a matching query is performed in a pre-set semantic template library to obtain a target semantic template that has a mapping relationship with the page identifier. If no semantic template directly mapped to the page identifier exists in the pre-set semantic template library, the system uses the business type tag corresponding to the page identifier as the second matching key to obtain a general semantic template associated with the business type tag from the pre-set semantic template library as the target semantic template.

[0043] After determining the target semantic template, all parameter placeholders and their corresponding parameter names within the statement frames of the target semantic template are parsed. Parameter placeholders are marked with predefined delimiters in the semantic template. Subsequently, using the extracted parameter names as field retrieval criteria, the field values ​​corresponding to each parameter name are read from the standardized behavioral data. The field names in the standardized behavioral data and the parameter names corresponding to the parameter placeholders in the semantic template follow the same naming convention. For example, the "pageName" field in the standardized behavioral data corresponds to the parameter placeholder named "pageName" in the semantic template, the "effectiveDuration" field corresponds to the parameter placeholder named "effectiveDuration," and the "interactionType" field corresponds to the parameter placeholder named "interactionType."

[0044] Next, according to the mapping relationship between the parameter names and the parameter placeholders, the read field values ​​are substituted one by one into the corresponding parameter placeholder positions in the semantic template, replacing the parameter placeholders and completing the filling of standardized behavioral data into the semantic template. After filling is completed, according to the preset sentence order in the sentence frame (e.g., the narrative order of subject-verb-object), the fixed text part in the sentence frame with the filled parameters is sequentially concatenated and syntactically integrated with each filled parameter value to generate a complete natural language sentence as semantic description data.

[0045] Optionally, the semantic template may also include conditional logic configuration, which is used to switch different expression branches in the statement frame according to different value ranges or states of parameter values. For example, when the effective browsing time is greater than a preset threshold, the statement frame automatically selects the deep browsing expression branch; when the effective browsing time is less than the preset threshold, the statement frame automatically selects the fast browsing expression branch. When performing the fill operation, the conditional logic configuration is first evaluated based on the parameter values ​​to determine the expression branch to be used, and then the parameter value fill is performed. The resulting semantic description data has stronger expression accuracy and business interpretation capabilities.

[0046] In one example, reference Figure 2 , Figure 2 This is a schematic diagram of the page browsing data processing system of this application. The page browsing data processing system consists of a terminal page layer, a multi-source lifecycle monitoring and acquisition layer, a page hierarchy stack correction layer, an invalid duration filtering layer, a standardized data encapsulation layer, a semantic intent parsing layer, a local cache persistence layer, and an asynchronous reporting business layer. The terminal page layer is the data source layer, containing Activity pages, Fragment pages, and Navigation routing pages, providing the source of raw page state change events for the entire architecture. The multi-source lifecycle monitoring and acquisition layer captures various page state change events from the terminal page layer by registering global page lifecycle callback interfaces, global fragment lifecycle monitoring interfaces, and routing page switching monitoring interfaces, serving as the raw input for subsequent processing. The page hierarchy stack correction layer receives event data reported by the monitoring and acquisition layer, maintains the page hierarchy stack, and determines the currently valid display page according to preset page hierarchy priority rules, solving the problem of timing subject identification in multi-page nested scenarios. The invalid duration filtering layer, based on the determination of the valid display page, purifies the browsing duration according to system device status events and user interaction behavior events. The system removes invalid browsing time such as screen-off, background, and inactive periods, and outputs the corrected valid browsing time. The standardized data encapsulation layer structures and assembles the valid browsing time and page information according to a preset unified data model to generate standardized behavioral data for semantic processing by the upper layer. The semantic intent parsing layer obtains the semantic template corresponding to the valid display page, fills the template with standardized behavioral data, and generates semantic description data with the ability to describe the user's browsing intent. The local cache persistence layer stores the semantic description data and the corresponding standardized behavioral data in the local database to ensure that the data is not lost when the application exits or there is a network error. The asynchronous reporting business layer reads data from the local cache and reports it to the server in batches asynchronously through a sub-thread. This ensures complete data reporting while avoiding blocking the main thread, forming a complete closed-loop processing link from data collection, cleaning, enhancement to reporting.

[0047] Optionally, after generating semantic description data, the complete behavioral data with semantic parsing can be preferentially stored in a lightweight local Room database to avoid data loss due to application exit or network anomalies. Simultaneously, an asynchronous batch reporting mechanism using a sub-thread is employed to bypass the Android main thread UI rendering process and avoid consuming core application resources. For weak network or network outage scenarios, the system automatically caches all behavioral data and automatically resends it in batches once the network is restored. In strong network environments, data is reported in batches at fixed time intervals, ensuring 100% complete data reporting while preventing application lag, increased power consumption, and wasted bandwidth.

[0048] In this embodiment, the effective browsing time of real visual pages under multiple nested frames is filtered using a page hierarchy stack. Semantic templates are used to transform discrete page state data into semantic descriptions carrying user operation intentions. This upgrades the collected data from simple numerical records to semantic information that can directly support upper-level business such as user profiling and personalized recommendations, significantly improving data utilization.

[0049] Reference Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the page browsing data processing method of this application. Based on the first embodiment described above, a second embodiment of the page browsing data processing method of this application is proposed.

[0050] In the second embodiment, step S10 includes: Step S101: Obtain the first page and change type corresponding to the page state change event. The first page is the page where the page state change has occurred. The change type includes at least one of push type, pop type and replacement type.

[0051] In this embodiment, the first page is the target page instance involved in this state change, i.e., the specific page object whose state change occurred, and the change type represents the way the page changes relative to the current page hierarchy stack. When obtaining a page state change event, the event payload field can be parsed from the event data packet to extract the target page instance reference and the event type identifier carried therein.

[0052] Specifically, when the listener component captures a page lifecycle callback or route switching callback, it encapsulates a page state change event according to a preset event data format. The reference to the target page instance is represented by a page object pointer or a unique page identifier, and the event type identifier is determined based on the callback method name of the triggering source or the event category field in the callback parameters. Taking Activity page lifecycle callbacks as an example, when the Activity's `onResume()` method is called, the listener component determines the event type identifier as a push type; when the Activity's `onPause()` method is called, if the Activity is at the top of the page hierarchy stack, the event type identifier is determined as a pop type. Taking Fragment lifecycle callbacks as an example, when the Fragment's `onResume()` method is called and the Fragment is attached to the foreground Activity, the event type identifier is determined as a push type; when the Fragment's `onPause()` method is called and the Fragment is currently visible, the event type identifier is determined as a pop type. Taking the Navigation route switching callback as an example, when NavController executes the navigate() method to complete the page navigation, if the navigation target is a new page, the event type identifier of the event is determined to be a push type; when NavController executes the popBackStack() method to complete the page back, the event type identifier of the event is determined to be a pop type; when NavController executes the navigate() method and the target page replaces the current page's position, the event type identifier of the event is determined to be a replacement type.

[0053] Furthermore, for push-type events, the first page recorded is the new page pushed onto the top of the stack, i.e., the target page the user is currently navigating to; for pop-type events, the first page recorded is the page that will be popped from the top of the stack, i.e., the current page the user is going back to or closing; for replacement-type events, the first page recorded by the system is the new page that replaces the old page, i.e., the new page instance that overwrites the current top position of the stack. After obtaining the first page and the change type, these can be passed as input parameters to the stack management module for subsequent page hierarchy stack update operations, driving the state changes of the page hierarchy stack.

[0054] In the specific implementation process, three types of lifecycle listening components—global page lifecycle callback interface, global fragment lifecycle listening interface, and route page switching listening interface—can be uniformly registered during the application initialization phase to achieve full-scene, comprehensive event capture of Activity pages, Fragment pages, and Navigation route pages. This overcomes the limitations of single-frame listening and achieves full coverage of multi-page and multi-route mixed scenarios, avoiding data omissions and under-collection issues from the source. At this point, before step S10, the following steps are also included: In response to the initialization result of the application program, a lifecycle listening component is registered for the application program. The lifecycle listening component includes a global page lifecycle callback interface, a global fragment lifecycle listening interface, and a route page switching listening interface. The lifecycle monitoring component collects page state change events of the application program.

[0055] In this embodiment, the initialization result of the application is an identifier indicating that the Android application's Application body has entered a ready state after completing system-level initialization. This identifier signifies that the application environment is ready and can be registered with global listening components. Lifecycle listening components are a collection of callback interfaces registered on the application framework layer or page management component. They are used to proactively call back by the system framework and report the corresponding page event data to the listener when the page lifecycle state changes or a route navigation event occurs.

[0056] Understandably, after detecting that the application has completed initialization, three independent lifecycle listener components can be registered with the application framework layer.

[0057] In one example, after the Android application's main body (Application) completes initialization, three types of native lifecycle listener components are uniformly registered to achieve comprehensive behavior capture across all pages and routes, covering the blind spots of traditional solutions. First, a global page lifecycle callback interface is registered to continuously monitor the entire lifecycle state of all Activity pages, from creation and foreground display to background hiding and destruction. When a page enters the foreground and becomes interactive, a high-precision system start timestamp is recorded; when a page leaves the foreground or is destroyed, an end timestamp is recorded. Second, through the FragmentManager, a global fragment lifecycle listener is registered to capture the display and hiding states of all nested pages, such as ViewPager nested fragments, Tab switching child fragments, and pop-up fragments, supplementing sub-page scenarios that traditional single Activity listeners cannot cover. Third, through the NavController, a route page switching listener is registered to capture JetpackNavigation route jumps, page replacements, and route parameter changes in real time, adapting to the modern Android component-based and route-based development architecture. All page state change events are uniformly aggregated in the global event dispatch center, completing the initial collection of raw page behavior data and providing a complete event data source for subsequent duration correction. Compared to existing technologies, this step breaks through the limitations of single-frame monitoring, achieving full coverage of multi-page and multi-route mixed scenarios, and avoiding data omissions and under-collection issues from the source.

[0058] Step S102: Update the page hierarchy stack according to the change type and the first page.

[0059] In this embodiment, the page hierarchy stack is a last-in, first-out (LIFO) data structure used to maintain the hierarchical coverage relationship between all opened and not yet destroyed pages in the current application. The top element of the stack represents the currently top-level, user-visible page instance. Update operations on the page hierarchy stack can be performed by pushing, popping, or replacing elements in the stack based on the change type of the page state change event and the first page involved in that event, ensuring that the state of the page hierarchy stack remains consistent with the actual hierarchical coverage relationship of the pages in the current application.

[0060] In one example, the global visual page hierarchy stack structure is constructed with the following priorities in the default Android page hierarchy rules, from highest to lowest: Navigation route subpages, nested Fragment subpages, root Fragment page, and root Activity page. The system dynamically updates the page data in the stack in real time based on page push, pop, and replacement events. When it is detected that the parent page has not triggered an exit or hide event, and the inner new page has completed foreground rendering and display, the system automatically determines the top inner page of the stack as the currently valid visible page and switches the timing subject in real time; when the inner page exits and is destroyed, it automatically reverts to the top page of the previous stack and resumes the original page timing.

[0061] In the specific implementation process, a differentiated stack update and timing subject switching mechanism can be used to ensure that the timing subject remains synchronized with the currently active visible page in any page jump scenario. This solves the technical defects of timing subject confusion, repeated timing, and duration discontinuity in nested scenarios, ensuring the continuity and accuracy of browsing duration data. At this time, step S102 may include: When the change type is a push type, the first page is pushed onto the current top of the page hierarchy stack, and it is determined whether to switch the current timing subject to the first page according to the preset page hierarchy priority rules. When the change type is a pop type, the top page of the page hierarchy stack is popped, and based on the timing status of the popped top page, it is determined whether to roll back the current timing subject to the top page of the current stack. When the change type is a replacement type, the top page of the page hierarchy stack is replaced with the first page, and the current timing subject is switched to the first page.

[0062] It is understood that the current timing subject refers to the page currently granted browsing time timing permission, i.e., the currently valid display page being timed. The page hierarchy stack update operation and the timing subject switching operation are related but logically independent. Stack updates determine the hierarchical coverage relationship between pages, while timing subject switching determines which page the system will accumulate time for. The system executes the corresponding stack update operation based on the change type, and, based on the stack update, combines the timing subject status and page hierarchy priority rules to determine whether to switch the timing subject.

[0063] Specifically, after receiving the first page and the change type, the stack management module first performs a branch judgment on the change type to determine the stack operation branch to be executed and the corresponding timing subject switching logic.

[0064] When the change type is a push type, it indicates that the user jumps from the current page to a new page, and the first page is the instance of the new page being jumped to. The stack management module performs a push operation, pushing the first page onto the current top of the page hierarchy stack, making the first page the new top element. After the push operation is completed, the first page is at the top of the page hierarchy stack, indicating that it has become a candidate valid display page that the user is currently viewing. However, not all push scenarios require the timing subject to switch to the first page. In practical applications, there are situations where some low-priority page overlays are on top of high-priority core pages, such as a briefly appearing Toast-style page or an unimportant intermediate page that the user quickly scrolls through. If the timing subject is unconditionally switched to the low-priority page in this case, the browsing time of the underlying core page will be incorrectly interrupted, causing serious distortion of the duration data.

[0065] Therefore, after the stacking operation is completed, the system further determines whether to switch the current timing subject to the first page based on the preset page hierarchy priority rules. The preset page hierarchy priority rules are pre-configured priority comparison logics between different page types or page hierarchies, with different page types or page hierarchies assigned different priority levels. Specifically, the system obtains the first priority level of the first page and the second priority level of the current page corresponding to the current timing subject, comparing the magnitude of the first and second priority levels. If the first priority level is higher than or equal to the second priority level, it indicates that the first page is not lower than the currently timing page in terms of business importance or display level. In this case, the appearance of the first page should interrupt the timing of the current timing subject, and the system switches the current timing subject from the original timing page to the first page. Subsequent time accumulation is performed on the first page. Conversely, if the first priority level is lower than the second priority level, it indicates that the first page is lower than the currently timing page in terms of business importance or display level. In this case, the appearance of the first page is only a temporary coverage scenario and should not interrupt the effective timing of the current page. The system keeps the current timing subject unchanged, and subsequent time accumulation is still performed on the original timing page. Taking a common application scenario as an example, when a full-screen wealth management details page is covered by a brief privacy policy pop-up, the system keeps the timing focus on the wealth management details page because the priority level of the wealth management details page is higher than that of the pop-up page, and the cumulative duration of the wealth management details page is not interrupted during the existence of the pop-up. Conversely, when a user jumps from the wealth management details page to an equally important holdings page, the system switches the timing focus to the holdings page because the priority level of the target page is no lower than that of the wealth management details page.

[0066] When the change type is a pop operation, it indicates that the user has performed a back operation from the current page or the current page has been closed. The first page is the page instance that will be removed from the current top of the stack. The stack management module performs a pop operation, popping the top page of the page hierarchy stack, making the next page in the original stack the new top page. After the pop operation is completed, the system determines whether to roll back the current timing subject to the new top page based on the timing status of the popped top page. The timing status is a status indicator indicating whether a page is currently being accumulated for browsing time by the system. If the popped page is the current timing subject (i.e., the page is being timed), the system terminates the time accumulation for that page, switches the current timing subject to the new top page after the pop, and resumes the time accumulation for the new top page. If the popped page is not the current timing subject (i.e., the page is not being timed), the system keeps the current timing subject unchanged and does not need to perform a rollback operation for the timing subject.

[0067] When the change type is a replacement type, this change type indicates that the user directly replaces the current page with another page at the same stack position, and the first page is the new page instance that replaces the old page. The stack management module performs the replacement operation, removing the top page of the page hierarchy stack and pushing the first page onto the top of the stack, making the first page the new top element. In the replacement scenario, the original top page is completely removed and no longer exists in the page hierarchy stack, while the new page replaces the original page at the same level depth, and the user's visible content has been completely switched from the original page to the first page. Therefore, after the system completes the replacement operation, it switches the current timing subject to the first page. Regardless of whether the original top page was previously in a timing state, its timing is terminated, and subsequent time accumulation is performed on the first page. The key difference between the replacement operation and the push operation is that in the replacement operation, the old page is completely removed and there is no possibility of subsequent rollback and restoration. Therefore, there is no need to retain the timing state of the old page, and the timing subject is unconditionally switched to the new page. In the push operation, the original page is still retained in the stack and can be restored when rollback. Therefore, it is necessary to determine whether to switch the timing subject according to the priority rules.

[0068] Step S103: Based on the updated top page and the second page in the page hierarchy stack, determine the valid display page. The second page is the page corresponding to the current timing subject, and the current timing subject is the page currently granted browsing time timing permission.

[0069] It should be noted that after the updated page hierarchy stack undergoes push, pop, or replacement operations, the top element represents the topmost page instance in the current application's page stack, which is theoretically the page the user is currently viewing. The current timing subject is the page currently granted viewing time timing permissions, i.e., the page object currently accumulating viewing time. The second page is the page corresponding to the current timing subject.

[0070] Understandably, since the updates to the page hierarchy stack and the switching of the timing subject are relatively independent in execution logic, in some scenarios, the top page of the stack and the second page corresponding to the current timing subject may point to different page instances. That is, the first page and the second page may be the same page, for example, when the page involved in the change event happens to be the page currently being timed; or they may be different pages, for example, the target page involved in the change event is not the current timing subject.

[0071] Specifically, if the top page of the stack and the second page are the same page, it means that the current top-level page reflected in the page hierarchy stack is completely consistent with the page that the system is currently timing, and there is no discrepancy. In this case, the top page of the stack is determined as the valid display page. If the top page of the stack and the second page are not the same page, then they need to be arbitrated according to the preset page hierarchy priority rules, and the page with higher priority is determined as the valid display page.

[0072] In one example, the top of the current page hierarchy is a floating login pop-up page with a priority level of 5; the current timing subject is a product details page with a priority level of 10. Since the top page (pop-up) and the second page (product details page) are inconsistent, their priority levels are compared. The second page is determined to have a higher priority, and the system identifies the product details page as the valid display page. The pop-up page is not included in the valid display pages or the time accumulation.

[0073] In another example, suppose a user navigates from the product details page to an order confirmation page. The order confirmation page is pushed onto the top of the stack to become the new top page with a priority level of 10; the current timing subject is still the product details page. If the system detects a discrepancy between the top page (order confirmation page) and the second page (product details page), it compares their priority levels. Determining that the top page's priority level is not lower than the second page, the system identifies the top page (order confirmation page) as the valid display page and switches the timing subject to the order confirmation page.

[0074] In this embodiment, the page hierarchy stack is updated in a targeted manner by distinguishing specific change types such as push, pop and replacement. The effective display page is dynamically determined based on the real-time comparison between the updated top page and the current timing subject. This allows the system to clearly define the visible subject in the process of complex page jumps, avoid the timing subject confusion caused by multiple page overlaps or horizontal switching, and ensure the continuity and accuracy of the subsequent duration statistics.

[0075] Reference Figure 4 , Figure 4 This is a flowchart illustrating the third embodiment of the page browsing data processing method of this application. Based on the first embodiment described above, a third embodiment of the page browsing data processing method of this application is proposed.

[0076] In the third embodiment, before step S20, the method further includes: Step S201: Obtain system device status events and user interaction behavior events, which are triggered when the listening component collects page status change events.

[0077] It should be noted that system device state events are events that characterize changes in the operating state of the Android terminal device itself, including but not limited to screen on / off state changes (such as screen off, screen on), device lock state changes (such as user manually locking the screen, screen automatically locking after timeout, user unlocking the screen), and application foreground / background running state changes (such as user switching the application to the background, user switching the application back to the foreground). User interaction behavior events are events that characterize user actions performed on the effectively displayed page, including but not limited to user clicks on the screen (such as button clicks, list item clicks), user swipes on the page (such as list scrolling, page turning), and user input in input boxes.

[0078] Step S202: Determine the pause duration of the effective display page based on the system device status event and the user interaction behavior event.

[0079] In this embodiment, the pause duration is the cumulative length of time during which the browsing time is interrupted due to device malfunction or lack of user interaction while the page is displayed in the foreground. By analyzing the time series of system device status events and user interaction events, the various time periods in which the time should be paused can be identified, and the lengths of these time periods can be summed to obtain the total pause duration.

[0080] In one example, a dual-dimensional monitoring system of system status and user interaction can be built to automatically identify and eliminate invalid browsing time, thus purifying the original collected data. On one hand, it monitors the Android system device status in real time, capturing system events such as screen-off, screen-locked, and applications running in the background. Once these states are triggered, the current page's timer is immediately paused, the already counted valid time is locked, and the accumulation of invalid time is terminated. The timer automatically resumes when the device screen is on, unlocked, or the application returns to the foreground. On the other hand, it monitors user page interaction behavior in real time, with a preset 5-second inactivity threshold. If the current page remains inactive for more than 5 seconds without any user-initiated actions such as clicking, swiping, switching, or input, it is determined to be an invalid browsing state, and the timer is paused. The timer restarts when user interaction is detected again. These steps can completely eliminate invalid data such as idle browsing, background activity, and accidental touches, solving the shortcomings of traditional solutions such as mechanical timing and excessive data impurities, and significantly improving the authenticity and effectiveness of the collected data.

[0081] In the specific implementation process, the device state dimension is responsible for capturing system-level interruption scenarios such as screen-off, screen-locked, and background switching, while the user interaction dimension is responsible for capturing human-computer interaction-level interruption scenarios such as no-operation pauses. Through a dual-dimensional calculation mechanism, invalid dwell time is accurately extracted from both the device physical state and user behavior characteristics levels. This avoids the omissions caused by single-dimensional monitoring and comprehensively covers various invalid browsing scenarios, improving the accuracy and robustness of valid browsing time calculation. At this point, step S202 may include: When the system device status event indicates that the device enters a non-interactive state, the first pause start time is recorded, and when the device returns to the interactive state, the first pause end time is recorded. The first pause duration is determined based on the first pause start time and the first pause end time. When the user interaction event indicates that the effective display page has no operation within a preset time threshold, the second pause start time is recorded, and the second pause end time is recorded when the user re-interacts. The second pause duration is determined based on the second pause start time and the second pause end time. The pause duration of the effective display page is determined based on the first pause duration and the second pause duration.

[0082] Specifically, regarding the system device status dimension, system device status events can be monitored in real time to identify whether the device has entered or returned to an interactive state. When a system device status event indicates that the device has entered a non-interactive state, the system timestamp at the time of the event is recorded as the first pause start time. Situations where the device enters a non-interactive state include, but are not limited to: the screen being off, the screen being locked, or the application switching from the foreground to the background. After any of these situations occur, an invalid browsing period is determined for the valid display page in the system device dimension, and the browsing time of the page is paused and accumulated. Subsequently, when a system device status event indicates that the device has returned to an interactive state, the system timestamp at the time of the event is recorded as the first pause end time. Situations where the device returns to an interactive state include, but are not limited to: the screen being turned on again, the screen being unlocked, or the application switching from the background back to the foreground. Finally, the first pause duration is determined based on the time interval between the first pause start time and the first pause end time.

[0083] For user interaction behavior, the temporal distribution of these events can be monitored in real time. A no-operation timer is maintained on the active display page. Whenever a user interaction event is detected, the timer is reset and restarted. When a user interaction event indicates that the active display page has been inactive for a preset duration threshold (i.e., the cumulative duration of the no-operation timer reaches the threshold and no user interaction event is detected within that time period), the system timestamp when the threshold is reached is recorded as the second pause start time. Subsequently, when a user is detected to have re-executed an interaction (i.e., the user interaction event reappears), the system timestamp when that event occurs is recorded as the second pause end time. The second pause duration is determined based on the time interval between the second pause start time and the second pause end time.

[0084] Understandably, after determining the first pause duration and the second pause duration respectively, the two pause durations can be integrated. Since the first pause period corresponding to the first pause duration and the second pause period corresponding to the second pause duration may overlap (for example, when the device is locked, there is naturally no user interaction, and the two pause periods completely overlap), the first pause period and the second pause period can be projected onto the same time axis for merging and deduplication, and the total union duration of all pause periods can be calculated. This total union duration is then used as the pause duration of the effective display page.

[0085] Step S203: Determine the effective browsing time based on the pause duration and the browsing time of the effective displayed page.

[0086] It should be noted that when a valid display page is determined, the start time of the corresponding timer for that page can be recorded. When that page is covered by a new valid display page, replaced, popped up and destroyed, or the application exits, the system records the corresponding end time of the timer. The system subtracts the start time of the timer from the end time to obtain the browsing duration of the valid display page.

[0087] Specifically, after obtaining the browsing duration of the valid display page, the corresponding pause duration for that page is read. The valid browsing duration of the valid display page is obtained by subtracting the pause duration from the obtained browsing duration of the valid display page.

[0088] In this embodiment, the pause duration of the effective display page is dynamically determined based on the device interaction status and user operation behavior, and the original browsing duration is corrected based on the pause duration. Invalid browsing periods such as device screen off, screen locked, application background running, and long periods of user inactivity are eliminated. This solves the technical defects of traditional solutions that mechanically count the entire time from page opening to closing, resulting in too much data impurity and an inability to truly reflect the user's effective browsing behavior.

[0089] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the page browsing data processing method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0090] This application also provides a page browsing data processing device, please refer to... Figure 5 The page browsing data processing device includes: Update module 10 is used to update the page hierarchy stack based on the page state change events collected by the listening component, so as to obtain a valid display page; The construction module 20 is used to construct standardized behavioral data based on the effective browsing time of the effective display page and the page information corresponding to the page state change event; The generation module 30 is used to obtain a semantic template corresponding to the effective display page, and fill the standardized behavior data into the semantic template to generate semantic description data.

[0091] The page browsing data processing apparatus provided in this application, employing the page browsing data processing method in the above embodiments, can solve the technical problem that existing page duration data can only output numerical data and cannot extract deeper business information such as user interests and operational intentions behind user behavior, resulting in low data utilization. Compared with the prior art, the beneficial effects of the page browsing data processing apparatus provided in this application are the same as those of the page browsing data processing method provided in the above embodiments, and other technical features in the page browsing data processing apparatus are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0092] This application provides a page browsing data processing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the page browsing data processing method in Embodiment 1 above.

[0093] The following is for reference. Figure 6 This document illustrates a structural schematic diagram of a page browsing data processing device suitable for implementing embodiments of this application. The page browsing data processing device in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The page browsing data processing device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0094] like Figure 6As shown, the page browsing data processing device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory 1002 or a program loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the page browsing data processing device. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. The communication device 1009 allows the page browsing data processing device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows page browsing data processing devices with various systems, it should be understood that it is not required to implement or possess all of the systems shown. More or fewer systems may be implemented alternatively.

[0095] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0096] The page browsing data processing device provided in this application, employing the page browsing data processing method in the above embodiments, can solve the technical problem that existing page duration data can only output numerical data and cannot extract deeper business information such as user interests, preferences, and operational intentions, resulting in low data utilization. Compared with the prior art, the beneficial effects of the page browsing data processing device provided in this application are the same as those of the page browsing data processing method provided in the above embodiments, and other technical features of this page browsing data processing device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0097] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0098] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0099] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the page browsing data processing method in the above embodiments.

[0100] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0101] The aforementioned computer-readable storage medium may be included in a page browsing data processing device; or it may exist independently and not be assembled into a page browsing data processing device.

[0102] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the page browsing data processing device, cause the page browsing data processing device to perform the page browsing data processing method described above.

[0103] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0104] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0105] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0106] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described page browsing data processing method. This solves the technical problem that existing page duration methods can only output numerical data and cannot extract deeper business information such as user interests, preferences, and operational intentions, leading to low data utilization. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the page browsing data processing method provided in the above embodiments, and will not be repeated here.

[0107] The above description is only a part of the embodiments of this application and does not limit the scope of this application. All equivalent structural transformations made under the technical concept of this application and using the content of this application specification and drawings, or direct / indirect applications in other related technical fields, are included within the protection scope of this application.

[0108] It should be noted that the data collection, tag management, rule setting, and push decision-making processes involved in this application are designed to work with other technical features to solve technical problems. They do not involve or support any illegal activities. Any data processing that may violate laws and regulations (such as unauthorized collection of privacy data, generation of discriminatory tags, setting unfair rules, or pushing illegal information) is not within the scope of protection of this application's technical solution. Of course, the user data in this application will be encrypted, anonymized, or de-identified before storage to ensure user data security.

Claims

1. A method for processing page browsing data, characterized in that, The page browsing data processing method includes: The page hierarchy stack is updated based on the page state change events collected by the listening component to obtain the effectively displayed page; Standardized behavioral data is constructed based on the effective browsing time of the effectively displayed page and the page information corresponding to the page state change event; Obtain the semantic template corresponding to the effective display page, and fill the standardized behavioral data into the semantic template to generate semantic description data.

2. The page browsing data processing method as described in claim 1, characterized in that, The step of updating the page hierarchy stack based on page state change events collected by the listening component to obtain a valid display page includes: Obtain the first page and change type corresponding to the page state change event, where the first page is the page whose page state has changed, and the change type includes at least one of push type, pop type, and replacement type; The page hierarchy stack is updated according to the change type and the first page; Based on the updated top page and the second page in the page hierarchy stack, the valid display page is determined. The second page is the page corresponding to the current timing subject, and the current timing subject is the page currently granted browsing time timing permission.

3. The page browsing data processing method as described in claim 2, characterized in that, The step of updating the page hierarchy stack according to the change type and the first page includes: When the change type is a push type, the first page is pushed onto the current top of the page hierarchy stack, and it is determined whether to switch the current timing subject to the first page according to the preset page hierarchy priority rules. When the change type is a pop type, the top page of the page hierarchy stack is popped, and based on the timing status of the popped top page, it is determined whether to roll back the current timing subject to the top page of the current stack. When the change type is a replacement type, the top page of the page hierarchy stack is replaced with the first page, and the current timing subject is switched to the first page.

4. The page browsing data processing method as described in claim 2, characterized in that, Before updating the page hierarchy stack based on page state change events collected by the monitoring component to obtain a valid display page, the process also includes: In response to the initialization result of the application program, a lifecycle listening component is registered for the application program. The lifecycle listening component includes a global page lifecycle callback interface, a global fragment lifecycle listening interface, and a route page switching listening interface. The lifecycle monitoring component collects page state change events of the application program.

5. The page browsing data processing method as described in claim 1, characterized in that, Before constructing standardized behavioral data based on the effective browsing duration of the effectively displayed page and the page information corresponding to the page state change event, the method further includes: Acquire system device status events and user interaction behavior events, which are triggered when the listening component collects page status change events; The pause duration of the valid display page is determined based on the system device status events and the user interaction behavior events; The effective browsing time is determined based on the pause duration and the browsing time of the effective displayed page.

6. The page browsing data processing method as described in claim 5, characterized in that, Determining the pause duration of the valid display page based on the system device status events and the user interaction behavior events includes: When the system device status event indicates that the device enters a non-interactive state, the first pause start time is recorded, and when the device returns to the interactive state, the first pause end time is recorded. The first pause duration is determined based on the first pause start time and the first pause end time. When the user interaction event indicates that the effective display page has no operation within a preset time threshold, the second pause start time is recorded, and the second pause end time is recorded when the user re-interacts. The second pause duration is determined based on the second pause start time and the second pause end time. The pause duration of the effective display page is determined based on the first pause duration and the second pause duration.

7. The page browsing data processing method according to any one of claims 1 to 6, characterized in that, The step of filling the standardized behavioral data into the corresponding semantic template to generate semantic description data includes: Obtain the page identifier and user interaction behavior of the effectively displayed page; Based on the page identifier and the user interaction behavior, determine a semantic template that matches the standardized behavior data; The standardized behavioral data is filled into the semantic template to obtain the filled semantic template; Based on the filled semantic template, semantic description data is generated to describe the user's browsing intent.

8. A page browsing data processing device, characterized in that, The device includes: The update module is used to update the page hierarchy stack based on the page state change events collected by the listening component, so as to obtain a valid display page; The construction module is used to construct standardized behavioral data based on the effective browsing time of the effective display page and the page information corresponding to the page state change event; The generation module is used to obtain the semantic template corresponding to the effective display page, and fill the standardized behavior data into the semantic template to generate semantic description data.

9. A page browsing data processing device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the page browsing data processing method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the page browsing data processing method as described in any one of claims 1 to 7.

Images