Communication Protocol Abstraction Layer for Data Handlers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data sharing technologies require data handlers to be individually developed with multiple communication protocol functionalities, leading to overhead and inefficiency in processing data requests across different communication protocols.

Innovation Solution

A communication protocol abstraction layer and data transfer component handle communication protocol aspects, allowing data handlers to focus on data retrieval and be communication protocol agnostic, thereby reducing overhead and enhancing efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data handlers are individually developed with multiple communication protocol functionalities, then data handlers can process requests across different protocols, but device complexity and overhead increase

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidhandler complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments communication protocol functionality from data handler functionality. A communication protocol abstraction layer is introduced that handles protocol-specific operations separately from the data handlers, which focus solely on data retrieval. This segmentation allows data handlers to remain simple while the system maintains support for multiple protocols through the abstraction layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A communication protocol abstraction layer acts as an intermediary between the data handlers and the various communication protocols. This mediator translates protocol-specific requests into standardized data handler calls, enabling protocol compatibility without requiring data handlers to understand multiple protocols. The abstraction layer handles protocol-specific logic while data handlers remain protocol-agnostic.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If data handlers include communication protocol functionality, then they can directly process protocol-specific requests, but overhead and processing efficiency decrease

Engineering Contradiction:
Improverequest processing capabilityVSAvoiddata retrieval efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

Communication protocol functionality is extracted from data handlers and placed in a separate communication protocol abstraction layer. This extraction allows data handlers to focus exclusively on their core function of retrieving data, improving their efficiency. The protocol handling capabilities are taken out and managed independently by the abstraction layer, reducing overhead in the data retrieval process.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If data handlers are made protocol-agnostic, then they become lightweight and more efficient, but they cannot directly handle protocol-specific operations

Engineering Contradiction:
Improvedata handler efficiencyVSAvoidprotocol handling capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The communication protocol abstraction layer provides universal support for multiple communication protocols while data handlers maintain a single, simplified interface for data retrieval. The abstraction layer adapts to different protocols (peer-to-peer, web-based, etc.) without requiring data handlers to change, enabling protocol-agnostic data handlers to work with various communication protocols through the unified abstraction interface.

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

Data Source

PatentUS9124647B2Communication protocol abstraction
Publication Date: 2015.09.01 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9124647B2 patent drawing
  • US9124647B2 patent drawing
  • US9124647B2 patent drawing

AI summary

One or more techniques and/or systems are provided for processing data requests received over various communication protocols. In particular, a data transfer component may be configured to process data requests and/or responses between requesting devices and data handlers utilizing various communication protocols (e.g., peer-to-peer communication protocols, web based communication protocols, etc.). In particular, communication protocol functionality may be abstracted away from the data handlers, and may be handled by the data transfer component. In this way, data handlers may be communication protocol agnostic because the data transfer component may perform the communication protocol functionality on behalf of the data handlers, which may allow the data handlers to be more “lightweight” and focus primarily on fetching and/or formatting requested data.