Data-Driven Navigation Decoupling Links from Page Code

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional navigation systems require recoding and updating of links on multiple pages when changes are made, such as dividing a page or adding new content, leading to inefficiencies and complexity.

Innovation Solution

Implementing data-driven navigation where user interface elements are bound to a data model, allowing changes to be made in the data model without modifying page code, with the navigation system determining the next action based on the data model, thereby decoupling locations from navigation and enabling automatic updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional navigation systems are used with hard-coded links on pages, then navigation structure is stable and predictable, but any change to content structure requires recoding multiple pages and updating links, increasing complexity and time consumption

Engineering Contradiction:

Improveadaptability to content structure changesVSAvoidcomplexity of navigation maintenance

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the navigation system into independent data model objects that can be modified individually. Each page and navigation element is represented as a separate data model object, allowing changes to be made in isolation without affecting the entire navigation structure. This enables flexible content restructuring while maintaining stable navigation through the object-based architecture.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces data model objects as intermediaries between the content structure and the navigation system. These objects serve as a layer that decouples the navigation logic from the actual page implementation, allowing changes to be propagated automatically through the data model hierarchy without requiring direct modification of navigation code or links on multiple pages.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If pages are divided or new content is added in conventional systems, then content flexibility improves, but the number of pages and links increases, requiring more recoding and updates

Engineering Contradiction:

Improveflexibility to add or divide pagesVSAvoidtime for recoding and updating links

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent establishes data model objects with predefined navigation capabilities and relationships before content is actually added or divided. The object hierarchy and navigation rules are set up in advance, so when new content is added or pages are divided, the navigation system automatically adapts through the existing object structure without requiring manual recoding or link updates.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The navigation system performs self-updates through the data model object hierarchy. When content structure changes are made to data model objects, the navigation system automatically propagates these changes and updates links throughout the system without requiring manual intervention. This self-service mechanism eliminates the time-consuming process of manually recoding and updating links across multiple pages.

Inventive Principle:

Principle #25Self-service

3Ease of operation

If navigation is tightly coupled with page code in conventional systems, then navigation behavior is precisely controlled, but changes require modifying page code, reducing ease of maintenance

Engineering Contradiction:

Improveease of making navigation changesVSAvoidcoupling between page code and navigation logic

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts navigation logic from page code by representing both pages and navigation elements as separate data model objects. This extraction decouples the navigation behavior from the page implementation details, allowing navigation changes to be made by modifying data model objects rather than recoding pages. The precise control of navigation behavior is maintained through the object hierarchy and data relationships.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The data model objects serve multiple functions: they represent content pages, define navigation behavior, store link relationships, and enable automatic updates. This universal object-based approach replaces the need for separate page code and navigation logic, simplifying maintenance while maintaining precise navigation control through the multi-functional data model objects.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11537679B2Data-driven navigation and navigation routing

Publication Date: 2022.12.27 HOME BOX OFFICE INC

AI summary

The described technology is directed towards data-driven navigation, in which a next navigation location depends on variable data associated with an interactive user interface element (rather than a fixed link). The data may be in a hierarchy of data models. A menu contains interactive navigation elements, each bound to a data model. A selected interactive navigation element results in locating a data model associated with the selected element. The data model is used to determine the next navigation location. Also described is hierarchical navigation to one item of a level as well as lateral and peer navigation.