Wireless Performance Data Segmentation for Bandwidth Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for requesting and communicating wireless device performance data often result in large files that strain network bandwidth and require users to wait until all data is collected before access is granted, leading to inefficiencies in data communication and access timing.

Innovation Solution

The method involves estimating the size of requested performance data and creating optimally sized files based on factors like time span and user preferences, allowing for earlier access to data as it becomes available, using Extensible Markup Language (XML) as a communication protocol to manage and provide these files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If performance data is collected for extended periods from numerous wireless devices, then comprehensive performance data is obtained, but the cumulative data file size becomes very large (10 MB to 1 GB)

Engineering Contradiction:
Improveperformance data volumeVSAvoiddata file size
Core Design Contradiction:
Quantity of substanceVSLength of stationary object

Solution Approach 1:

The patent divides the large cumulative performance data file into multiple smaller segmented files. Each segmented file contains a portion of the total performance data, allowing the system to maintain comprehensive data collection while managing file sizes at manageable levels. This segmentation enables efficient storage, retrieval, and transmission of performance data without creating excessively large single files.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If large performance data files are transmitted over the network, then complete performance data is provided to requesting parties, but network bandwidth is strained and communication may be delayed or fail

Engineering Contradiction:
Improveperformance data completenessVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Quantity of substanceVSLoss of energy

Solution Approach 1:

The patent segments large performance data files into smaller files for network transmission. This segmentation reduces the bandwidth consumption per transmission event, lowers the risk of communication failures, and enables more efficient network utilization. Requesting parties can retrieve data in manageable chunks rather than requiring a single large file transfer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by pre-segmenting performance data files before transmission and maintaining indexes that map segmented files to their original data sources. This preliminary organization allows requesting parties to efficiently retrieve specific data segments without needing to download or process entire large files, reducing network bandwidth consumption.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If all performance data is collected before providing access to requesting parties, then complete data is available, but users must wait extended periods (e.g., monthly) before accessing any data

Engineering Contradiction:
Improveperformance data completenessVSAvoiddata access delay
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent segments the performance data collection period into multiple intervals, with each segment generating a separate file. This allows the system to provide access to requesting parties at multiple intermediate points rather than waiting for the complete collection period to end. Users can access data as it becomes available in segments, reducing wait time while still obtaining comprehensive data over the full period.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by pre-organizing performance data into time-based segments and maintaining an index structure that enables requesting parties to access specific time periods or data portions before the entire collection period completes. This preliminary organization facilitates earlier data access while preserving the ability to retrieve complete data sets.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If performance data is segmented into multiple optimally sized files, then network bandwidth efficiency is improved and earlier access is enabled, but additional file management complexity is introduced

Engineering Contradiction:
Improvenetwork bandwidth efficiencyVSAvoidfile management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal file management system that handles multiple functions through a single automated process: segmentation, indexing, storage, and retrieval. This multi-functional approach manages the complexity of segmented files through centralized automation, allowing the system to efficiently handle file operations without proportionally increasing operational complexity for users.

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

Solution Approach 2:

The patent incorporates feedback mechanisms that automatically monitor file size, network conditions, and access patterns to dynamically adjust segmentation parameters. This feedback-driven approach optimizes file segmentation and management automatically, reducing the need for manual intervention and simplifying file management despite the segmented structure.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8176167B2Methods and apparaus for requesting wireless communication device performance data and providing the data in optimal file size
Publication Date: 2012.05.08 QUALCOMM INC
  • US8176167B2 patent drawing
  • US8176167B2 patent drawing
  • US8176167B2 patent drawing

AI summary

Methods, systems, devices and computer program products are presented for requesting wireless device performance data and providing an optimal file size for the performance data. Present aspects provide for estimating the size of requested performance data, at the time of the request, and assessing other factors, such as requesting party preferences, to determine optimal performance data file size. In this regard, the performance data service provider is able to prepare and make accessible optimally sized performance data files, as the data becomes available as opposed to creating one comprehensive performance data file when all of the requested data is available. Additionally, some present aspects may provide for performance data requesting parties to implement Extensible Markup Language (XML) as the communication tool between the requesting device and the performance data-supplying network entity.