Wireless Data Access Architecture for Local Storage Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Wireless devices face limitations in bandwidth, processing power, storage, and user interaction capabilities, making it cumbersome to access and navigate large data files, and existing Internet browsers transfer unnecessary data, leading to slow data access and limited functionality.

Innovation Solution

A wireless data access architecture that reduces data transmission by storing application files and presentation elements on the device, transmitting only status updates, and enabling data linking between software components to enhance efficiency and user interaction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If Internet browsers download all icons, formatting information, and text each time a WebPage is accessed, then complete data presentation is achieved, but data transmission time and bandwidth consumption increase significantly

Engineering Contradiction:
Improvedata completenessVSAvoiddata access time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent applies preliminary action by storing application files, presentation elements, and data locally on the wireless device before they are needed. The device maintains local copies of web pages, icons, formatting information, and other data elements, so when a user accesses a web page, the device can retrieve this information from local storage rather than downloading it from the remote server, significantly reducing data access time while maintaining complete data presentation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements copying by creating local replicas of remote data on the wireless device. The system downloads and stores copies of application files, presentation elements, icons, and formatting information in local storage. When accessing web pages, the device uses these local copies instead of retrieving them from the remote server, thereby reducing bandwidth consumption and access time while preserving data completeness.

Inventive Principle:
Principle #26Copying

2Quantity of substance

If large files are transmitted over wireless networks, then complete data is delivered to the device, but bandwidth limitations cause transmission to be cumbersome and slow

Engineering Contradiction:
Improvedata volumeVSAvoiddata transmission speed
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-downloading and storing large data files, application files, and presentation elements in the device's local storage before they are needed. This allows the system to have large quantities of data available locally without requiring high-speed transmission at the moment of access, effectively bypassing bandwidth limitations while maintaining access to complete data sets.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements copying by creating local replicas of large data files on the wireless device. Instead of transmitting large files over the network each time they are needed, the system downloads them once and stores local copies in persistent storage. This dramatically improves data transmission speed and productivity while maintaining access to the complete data volume.

Inventive Principle:
Principle #26Copying

3Device complexity

If wireless devices have limited processing power and storage capacity, then device complexity is reduced, but the ability to process and navigate large data files is impaired

Engineering Contradiction:
Improvedevice simplicityVSAvoiddata navigation capability
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent applies segmentation by dividing data into distinct components: application files, presentation elements, data content, icons, and formatting information. Each segment is stored separately in local storage and can be independently managed. This segmentation allows the device to handle large data sets through modular processing, improving ease of operation while maintaining device simplicity by treating each segment as a manageable unit rather than overwhelming the system with monolithic data files.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements copying by creating local replicas of remote data structures and organization schemes. The device copies not only the data content but also the presentation elements, icons, and formatting information that define how data is organized and navigated. This allows users to navigate large data files with the same ease as on the remote server, while the actual processing remains distributed between the copied local structures and the device's limited processing resources.

Inventive Principle:
Principle #26Copying

4Reliability

If all data is retrieved from remote servers each time a web page is accessed, then data currency is maintained, but response time and user interaction are delayed

Engineering Contradiction:
Improvedata currencyVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent applies preliminary action by pre-fetching and storing data, application files, and presentation elements in local storage before they are explicitly requested. The system anticipates user needs and loads data in advance, so when a user accesses a web page, the data is already available locally. This maintains data currency while dramatically improving response time, as the device can immediately display locally stored data without waiting for remote server retrieval.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7761871B2Data access architecture
Publication Date: 2010.07.20 HANDMARK INC
  • US7761871B2 patent drawing
  • US7761871B2 patent drawing
  • US7761871B2 patent drawing

AI summary

Methods and apparatuses for remotely accessing data through a wireless device are disclosed. Preferably, the wireless device includes an ability to link data between software components operating on the wireless device. Additionally, the wireless device preferably includes an ability to reduce remote data access by identifying a first data type and a second data type used by a software component, retrieving data corresponding to the first data type from a service provider, retrieving data corresponding to the second data type from the portable device, and displaying on the portable device a return content result including both the first data type and the second data type.