Reconfigurable Protocol Stack for Wearable Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing protocols for application programs in wearable body area networks are inefficient due to the need for multiple, application-specific protocols, which leads to increased memory usage and overhead, while multi-purpose protocols do not optimize quality of service (QoS) requirements in real-time dynamic environments.

Innovation Solution

A method and apparatus for reconfiguring protocols by analyzing requirement information and system data to determine optimal protocol configurations and connection relationships among component modules, using a reconfigurable protocol stack and protocol database to implement the most suitable protocol for changing QoS demands.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple application-specific protocols are used to meet different QoS requirements, then the QoS performance is improved, but the memory usage and system overhead increase

Engineering Contradiction:
ImproveQoS performanceVSAvoidmemory usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The protocol is divided into multiple independent component modules that can be selectively assembled. Each module performs a specific protocol function, allowing the system to create customized protocol configurations for different applications by selecting and connecting only the necessary modules, rather than implementing complete separate protocols for each application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A universal protocol framework is implemented using a shared set of component modules that can be configured to serve multiple different applications. The same pool of modules can be dynamically assembled into different protocol configurations depending on the specific QoS requirements of each application, reducing the need for multiple dedicated protocols.

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

2Reliability

If multiple application-specific protocols are used to meet different QoS requirements, then the QoS performance is improved, but the device complexity increases

Engineering Contradiction:
ImproveQoS performanceVSAvoidprotocol configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The protocol is divided into multiple independent component modules that can be selectively assembled. Each module performs a specific protocol function, allowing the system to create customized protocol configurations for different applications by selecting and connecting only the necessary modules, rather than implementing complete separate protocols for each application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple protocol functions are merged into a unified component module framework. Instead of maintaining separate complete protocols, the essential functions from different protocols are extracted as independent modules that can be combined in various configurations, reducing overall system complexity while maintaining the ability to meet different QoS requirements.

Inventive Principle:
Principle #5Merging (Combining)

3Quantity of substance

If multi-purpose protocols are used to reduce memory usage, then the memory efficiency is improved, but the ability to optimize QoS in real-time dynamic environments deteriorates

Engineering Contradiction:
Improvememory efficiencyVSAvoidreal-time QoS optimization capability
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The protocol configuration is made dynamic through runtime assembly of component modules. The system can adaptively select and connect modules based on current QoS requirements and environmental conditions, allowing real-time optimization without requiring multiple pre-configured protocols in memory. The modular architecture enables flexible reconfiguration as applications and requirements change.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system optimizes QoS by changing protocol parameters through different module selections and connection configurations rather than switching between entirely different protocols. By adjusting which modules are active and how they are connected, the system can dynamically optimize performance parameters while maintaining a compact memory footprint with a single reusable module set.

Inventive Principle:
Principle #35Parameter changes

4Device complexity

If a fixed protocol configuration is used to simplify the system, then the device complexity is reduced, but the adaptability to varying QoS requirements deteriorates

Engineering Contradiction:
Improvesystem simplicityVSAvoidprotocol adaptability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The protocol is divided into multiple independent component modules that can be selectively assembled. Each module performs a specific protocol function, allowing the system to create customized protocol configurations for different applications by selecting and connecting only the necessary modules, rather than implementing complete separate protocols for each application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The protocol configuration is made dynamic through runtime assembly of component modules. The system can adaptively select and connect modules based on current QoS requirements and environmental conditions, allowing real-time optimization without requiring multiple pre-configured protocols in memory. The modular architecture enables flexible reconfiguration as applications and requirements change.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2574084B1Method for reconfiguring a protocol of an application program
Publication Date: 2018.07.25 SAMSUNG ELECTRONICS CO LTD
  • EP2574084B1 patent drawingFigure 1~2
  • EP2574084B1 patent drawingFigure 3~4
  • EP2574084B1 patent drawingFigure 5

AI summary

A method of reconfiguring a protocol of an application program comprises maintaining a memory that stores a stack of a plurality of component modules, analyzing requirement information of the application program and system information obtained from a protocol layer, determining protocol configuration information comprising a reconfigured protocol of the application program and an operating parameter of the reconfigured protocol based on a result of the analyzing, and determining a connection relationship of at least one component module, among the plurality of component modules, needed to implement the reconfigured protocol based on the protocol configuration information.