Client Device Data Retrieval via Field-Level Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As users generate larger amounts of data, mobile devices face increased resource consumption due to larger data transfers, necessitating techniques to reduce data transmission and reception, particularly in maintaining a current state of object lists like inboxes and social media accounts.

Innovation Solution

Implementing a system that uses a filter to selectively retrieve data from a data repository based on configurable options, such as logical operators and keywords, to populate object lists with a subset of fields, thereby reducing the amount of data continuously retrieved and updated.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is retrieved from a data repository to maintain current state of object lists, then the object list is kept updated, but data transfer volume and resource consumption increase

Engineering Contradiction:
Improveobject list currencyVSAvoiddata transfer volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments data retrieval by filtering and selecting only specific fields needed for object list maintenance, rather than retrieving complete objects. This is achieved through field-level filtering where the system identifies and retrieves only the subset of fields necessary for maintaining current object list state, significantly reducing data transfer volume while preserving list currency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts only the necessary fields from the complete data objects and retrieves them separately from the data repository. By extracting and retrieving only the essential fields needed for object list maintenance rather than complete objects, the system reduces data consumption while maintaining list updates.

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of information

If complete objects are retrieved to ensure data completeness, then no information is lost, but resource utilization and data consumption increase

Engineering Contradiction:
Improvedata completenessVSAvoidresource consumption
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by retrieving only the necessary fields required for object list maintenance rather than complete objects. This partial retrieval approach ensures sufficient data completeness for list operations while avoiding excessive data consumption that would result from retrieving full objects.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the retrieval parameter from complete objects to specific field subsets. By modifying the retrieval scope to target only necessary fields rather than complete objects, the system maintains adequate information completeness for list maintenance while significantly reducing resource consumption and data transfer.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If continuous data retrieval is performed to maintain current state, then object list is always updated, but data transmission frequency and overhead increase

Engineering Contradiction:
Improveobject list currencyVSAvoiddata transmission frequency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary identification of necessary fields and filters before data retrieval. By pre-determining which fields are needed for object list maintenance, the system optimizes subsequent retrieval operations to fetch only essential data, reducing transmission frequency and overhead while maintaining list currency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes retrieval parameters to target specific field subsets rather than complete objects. This parameter modification enables more efficient data transmission by focusing on only the necessary fields, reducing both data volume and transmission frequency requirements while maintaining object list updates.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10664536B2Consumption of user-filtered data on a client device
Publication Date: 2020.05.26 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10664536B2 patent drawing
  • US10664536B2 patent drawing
  • US10664536B2 patent drawing

AI summary

Various techniques for consumption of user-filtered data on a client device are described herein. In one example, a method includes storing a detected filter corresponding to an object list and generating a data request based on the stored filter, wherein the data request can populate the object list. The method can also include retrieving data from a data repository based on the data request in response to a detected action, the retrieved data comprising a subset of fields corresponding to at least one object to be retrieved. Additionally, the method can include updating the object list based on the retrieved data and displaying the subset of fields of the at least one object in the object list.