Page Routing Stack Tracking for Accurate Cross-Page Jump Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the React Native framework, different types of pages independently collect their own jump information, leading to redundant pageview trackings and difficulties in accurately collecting the jump relationships between pages, necessitating a second processing step to restore the real jump situation.

Innovation Solution

A method and apparatus that monitor page states using a page routing stack to accurately determine current and previous pages, detect page types, and generate page tracking information based on these types, merging identifiers to correctly count page jumps and avoid redundant tracking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If each type of page independently collects its own jump information, then the collection process is simple for each page type, but redundant pageview trackings are generated and the accuracy of jump relationship collection deteriorates

Engineering Contradiction:
Improvesimplicity of collection processVSAvoidaccuracy of jump relationship collection
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

The patent merges the independent collection processes of different page types into a unified collection mechanism. By introducing a universal page tracking identifier that works across all page types (native pages, React Native pages, and SPA pages), the system combines previously separate tracking streams into a single coherent flow, eliminating redundancy while maintaining accuracy in jump relationship collection.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of operation

If page jump information is collected independently for each page type, then the implementation is straightforward, but a second processing step is required to restore the real jump situation

Engineering Contradiction:
Improveease of implementationVSAvoidnumber of processing steps
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-establishing a unified page tracking identifier system that works across all page types before the actual page navigation occurs. This identifier is embedded in the page routing stack from the beginning, so that when page jumps occur, the tracking information is already in the correct format, eliminating the need for subsequent second-processing steps to restore the real jump situation.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If redundant pageview trackings are counted, then more data is collected, but the pageview counting accuracy deteriorates and becomes inflated

Engineering Contradiction:
Improveamount of tracking dataVSAvoidpageview counting accuracy
Core Design Contradiction:
Quantity of substanceVSMeasurement precision

Solution Approach 1:

The patent extracts the essential tracking information (page identifier, page type, and routing stack position) from the complex page navigation events and uses only this extracted core data for counting. By taking out only the necessary elements and ignoring redundant details, the system maintains accurate pageview counting without being inflated by unnecessary duplicate tracking data.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12572361B2Method, apparatus, computer device, and storage medium for determining page jump information
Publication Date: 2026.03.10 BEIJING VOLCANO ENGINE TECH CO LTD
  • US12572361B2 patent drawing
  • US12572361B2 patent drawing
  • US12572361B2 patent drawing

AI summary

The present disclosure relates to a field of computer technologies, and discloses a method, an apparatus, a computer device, and a storage medium for determining page jump information. The method includes: monitoring a page state of a page routing stack; in response to the page state changing, determining a current page and a previous page; detecting whether a page type of the current page is the same as a page type of the previous page; in response to the page type of the current page being different from the page type of the previous page, determining a first page type corresponding to the current page and a second page type corresponding to the previous page; determining page tracking information for the current page based on the first page type and the second page type; and determining page jump information corresponding to the current page based on the page tracking information.