Deep Link Verification for Native Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing deep link verification systems for native applications fail to ensure compatibility with different version levels, leading to a poor user experience when serving deep links to users with outdated native applications, as they assume forward compatibility without testing for version compatibility, resulting in inoperable links.

Innovation Solution

A method that verifies deep links for specific version levels of native applications, storing verification data, and serving only compatible deep links based on the installed version level, eliminating the need for recrawling and reducing publisher errors, while maintaining transparency and efficiency in deep link maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If deep links are served without version compatibility verification, then deep link maintenance is simple and fast, but user experience deteriorates due to inoperable links for outdated applications

Engineering Contradiction:
Improvedeep link operabilityVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary verification of deep links against specific version levels of native applications before serving them to users. Verification data is generated in advance and stored, so when users access deep links, the system can quickly determine compatibility without real-time testing. This resolves the contradiction by ensuring reliability through advance preparation while maintaining operational simplicity through pre-computed results.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates verification data that copies the essential compatibility information of deep links for different version levels. Instead of maintaining complex verification systems that continuously test links, the system stores verified deep link data structures that can be quickly retrieved and matched against user application versions. This copying approach ensures reliability while reducing operational complexity significantly.

Inventive Principle:
Principle #26Copying

2Ease of operation

If deep links are verified for specific version levels, then user experience improves through compatible link delivery, but system complexity increases due to version level tracking and verification processes

Engineering Contradiction:
Improvedeep link serving accuracyVSAvoidversion management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system segments deep link verification by version levels, creating distinct verification data for each version level rather than managing a single complex verification system. This segmentation allows the system to handle version-specific deep links independently, improving accuracy for each version while managing complexity through modular organization of verification data structures.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces verification data as an intermediary between deep links and user devices. This intermediary layer contains pre-verified compatibility information that mediates the interaction between the deep link system and version-specific application requirements. The verification data acts as a buffer that simplifies version management complexity while ensuring accurate deep link delivery to appropriate users.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If recrawling is performed for each version level, then deep link compatibility is ensured, but processing time and resources increase significantly

Engineering Contradiction:
Improveversion compatibilityVSAvoidrecrawling time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs recrawling and verification actions in advance for each version level, creating verification data before the actual deep link serving occurs. By preparing and storing verified deep link information beforehand, the system eliminates the need for time-consuming recrawling operations during user access. This preliminary action ensures version compatibility while dramatically reducing processing time and resource consumption during actual link delivery.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If deep links are served to all users regardless of version, then system simplicity is maintained, but user experience deteriorates due to inoperable links for outdated applications

Engineering Contradiction:
Improvedeep link accessibilityVSAvoidlink operability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system dynamically adjusts deep link delivery based on user device version levels. Instead of serving all deep links uniformly to all users, the system adapts its behavior by selecting appropriate deep links from version-specific verification data based on the detected application version. This dynamic approach maintains ease of operation for users with updated applications while ensuring reliability for all user segments through intelligent adaptation.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10068028B1Deep link verification for native applications
Publication Date: 2018.09.04 GOOGLE LLC
  • US10068028B1 patent drawing
  • US10068028B1 patent drawing
  • US10068028B1 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for verifying deep links in for a native application. In one aspect, a method includes verify a deep link for a first version level of a native application and serving the deep link only if aversion level of a native application installed on a requesting user device is the same as or subsequent to the version level for which the deep link is verified.