Native Application Deep Link Indexing via URI Patterns

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Native applications present challenges for search engines in discovering and indexing deep links due to their unique nature, which differs from web pages, making it difficult for search engines to crawl and serve relevant content to users.

Innovation Solution

The system automatically generates native application deep links by determining URI patterns, indexing content accessible by these links, and iteratively processing linked application pages, allowing for the inclusion of both web-based and custom URI structures, and prioritizing links based on user activity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If search engines use traditional web page crawling methods, then web content can be indexed, but native application deep links cannot be discovered and indexed

Engineering Contradiction:
ImproveAbility to index different content typesVSAvoidIndexing system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal indexing system that handles both traditional web pages and native application deep links through a common framework. The system uses publisher affiliation data and URI patterns to uniformly process different content types, making the indexing system adaptable to multiple platforms and content formats without requiring separate specialized systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces publisher affiliation data as an intermediary layer between native applications and the search engine. This mediator contains URI patterns that enable the search engine to generate and discover deep links without directly interacting with the native application's internal structure, thus simplifying the indexing process while maintaining versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If manual indexing of native applications is implemented, then deep links can be indexed, but the barrier for application developer participation increases

Engineering Contradiction:
ImproveCompleteness of indexed contentVSAvoidEase of participation for developers
Core Design Contradiction:
Loss of informationVSEase of manufacture

Solution Approach 1:

The patent enables native applications to be indexed automatically through self-service mechanisms. Application developers simply need to include publisher affiliation data and URI patterns in their applications, and the system automatically generates deep links and indexes content without requiring manual submission or complex configuration, thus lowering the barrier to participation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-defining URI patterns and publisher affiliations during application development. This allows the indexing system to automatically generate deep links without requiring real-time manual intervention, ensuring complete indexing while maintaining ease of developer participation through automated processes.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automatic URI generation is implemented for all native applications, then deep link discovery improves, but false positives increase for unaffiliated applications

Engineering Contradiction:
ImproveSpeed of deep link discoveryVSAvoidAccuracy of affiliation determination
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies local quality by making URI generation selective rather than universal. The system generates deep links only for applications that have publisher affiliation data matching the content URI patterns, ensuring high reliability by avoiding false positives for unaffiliated applications while maintaining productivity through automated processing of qualified applications.

Inventive Principle:
Principle #3Local quality

4Loss of information

If iterative processing of application pages is performed, then comprehensive indexing is achieved, but processing time increases

Engineering Contradiction:
ImproveCompleteness of indexed pagesVSAvoidIndexing processing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent applies partial action by performing iterative processing selectively on application pages that contain outbound URIs rather than processing every page uniformly. The system iterates through pages to discover linked content, but can cease iteration when cessation events occur or when sufficient coverage is achieved, balancing comprehensive indexing with reasonable processing time constraints.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3161678B1Deep links for native applications
Publication Date: 2020.12.16 GOOGLE LLC
  • EP3161678B1 patent drawingFigure 1
  • EP3161678B1 patent drawingFigure 2
  • EP3161678B1 patent drawingFigure 3

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for automatically generating native application deep links and indexing content retrieved from the deep links.