Connection Management for Wireless Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication technologies, such as Bluetooth Low Energy (BLE), face challenges in concurrent device communication, limited bandwidth, and inefficient data transfer due to single connection limitations and complex packet management, which hinder seamless and secure data exchange between devices, especially in IoT applications.

Innovation Solution

The implementation of packet compression techniques and address mapping allows for concurrent communication with multiple devices using default value compression, enabling efficient data transfer and secure communication by reducing packet size and managing sessions without significant state information, while utilizing standards-based protocols for interoperability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If single connection protocols are used, then security is maintained, but concurrent communication capability is limited

Engineering Contradiction:
Improveconcurrent communication capabilityVSAvoidconnection security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the connection management into multiple independent connection contexts, each with its own state information. This allows the system to maintain multiple concurrent connections while keeping each connection's security state isolated and manageable, resolving the contradiction between concurrent capability and security maintenance

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an address mapping table as an intermediary layer between the physical connection and the application layer. This mapping table allows multiple physical connections to be mapped to logical addresses, enabling concurrent communication while maintaining security through controlled address resolution

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If full packet headers are transmitted, then data integrity is ensured, but bandwidth efficiency is reduced

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent extracts and removes redundant header fields from packets that can be inferred from context or have default values. By taking out only the essential information needed for data integrity while removing redundant parts, the system achieves both bandwidth efficiency and data integrity

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the parameter representation by using compressed header formats where fields are either fully transmitted, fully omitted (using defaults), or selectively transmitted based on change detection. This parameter change approach optimizes bandwidth usage while preserving necessary data integrity information

Inventive Principle:
Principle #35Parameter changes

3Reliability

If connection state information is maintained, then communication reliability is improved, but device resource consumption increases

Engineering Contradiction:
Improvecommunication reliabilityVSAvoiddevice resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by maintaining connection state information only when necessary - using compressed representations and omitting state tracking for connections that use default parameters. This partial maintenance approach reduces resource consumption while preserving communication reliability for active connections

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent inverts the traditional approach by using address mapping tables that map logical addresses to physical connections, rather than maintaining full state information for each connection. This inversion allows the system to track connections through address mapping without storing complete connection state information, reducing resource consumption

Inventive Principle:
Principle #13The other way round (Inversion)

4Adaptability or versatility

If multiple devices communicate concurrently, then communication versatility is improved, but protocol complexity increases

Engineering Contradiction:
Improvemulti-device communication capabilityVSAvoidprotocol management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal address mapping mechanism that handles multiple device connections through a single standardized interface. The address mapping table serves as a universal structure that can map any number of physical connections to logical addresses, providing multi-functionality without increasing protocol complexity

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

Solution Approach 2:

The patent adds an address mapping dimension between the physical connection layer and the application layer. This additional dimensional layer allows multiple devices to communicate concurrently by mapping their connections through address tables, managing complexity through dimensional separation rather than protocol complexity

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11616850B1Connection management techniques
Publication Date: 2023.03.28 FITBIT INC
  • US11616850B1 patent drawing
  • US11616850B1 patent drawing
  • US11616850B1 patent drawing

AI summary

Devices communicating wirelessly may experience temporary disconnections. While disconnected, a device may be unable to notify the other device that an update has occurred and that data previously used for communication may no longer be current. An ephemeral characteristic can be used by a service device that is updated each time a change occurs on the service device that may impact communications. A client device can use cached service data to attempt to write to this ephemeral characteristic. If the write does not complete successfully, it can be determined that the cached data is no longer current and a service request change can be used to cause the client device to flush the cached data and request current data from the service device.