Protocol Interface Device for Mobile Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communications systems face challenges in efficiently accessing data across different operating protocols, leading to complexity and overhead in supporting multiple clients and protocols, particularly in constrained devices like mobile wireless communications devices.

Innovation Solution

A communications system featuring a protocol interface device with a protocol engine module and a front-end proxy module, which includes a common core service module for routing traffic and rendering data, allowing access to multiple data storage devices using various protocols, and enabling clients to access data without supporting the specific access protocol.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a transcoding proxy server sends content processing software to clients, then protocol conversion capability is improved, but device complexity and overhead increase

Engineering Contradiction:
Improveprotocol conversion capabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a protocol interface device as an intermediary component between data storage devices and mobile wireless communications devices. This intermediary handles all protocol conversion and translation tasks, allowing clients to access data without needing protocol-specific software. The protocol interface device translates requests from various client protocols into统一的 internal representation and vice versa, eliminating the need for clients to install complex protocol conversion software.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The protocol interface device provides universal access to multiple data storage devices regardless of their native protocols. It implements a unified interface that can communicate with different protocol types (e.g., proprietary protocols, standard protocols) and present consistent data formats to diverse client devices. This multi-functional approach allows a single interface to handle various protocol requirements without requiring each client to be protocol-specific.

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

2Adaptability or versatility

If multiple protocol-specific services are written for each client type, then client compatibility is improved, but development overhead increases

Engineering Contradiction:
Improveclient compatibilityVSAvoiddevelopment overhead
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system segments protocol handling into separate components: protocol-specific interface modules within the protocol interface device. Each module handles a specific protocol type independently, allowing developers to create and maintain protocol-specific logic in isolated units. This segmentation enables client compatibility without requiring monolithic protocol-specific services for each client type, reducing overall development complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The protocol interface device acts as a mediator that abstracts protocol differences between servers and clients. Instead of writing protocol-specific services for each client type, developers only need to implement protocol adapters on the server side, which then automatically handle communication with various client types through the standardized interface. This significantly reduces development overhead while maintaining broad client compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If protocol translation functionality is added to existing systems, then protocol support versatility is improved, but system complexity increases

Engineering Contradiction:
Improveprotocol support versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The protocol interface device implements a nested architecture where protocol-specific interface modules are contained within a unified framework. Each protocol handler is nested within the protocol interface device, which itself is nested within the mobile wireless communications device architecture. This nesting allows protocol translation functionality to be added without proportionally increasing overall system complexity, as each layer handles only its specific protocol requirements while relying on lower layers for common operations.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The protocol interface device provides universal protocol translation capabilities through a standardized internal representation layer. All protocol-specific operations are translated into this universal representation, which then serves as the basis for all subsequent processing. This universality allows the system to support multiple protocols without requiring separate translation paths for each protocol combination, thereby limiting the increase in system complexity despite improved protocol support versatility.

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

Data Source

PatentUS7644170B2Communications system providing extensible protocol translation features and related methods
Publication Date: 2010.01.05 MALIKIE INNOVATIONS LTD
  • US7644170B2 patent drawing
  • US7644170B2 patent drawing
  • US7644170B2 patent drawing

AI summary

A communications system may include a plurality of data storage devices each using at least one of a plurality of different operating protocols, and a plurality of mobile wireless communications devices for accessing the plurality of data storage devices. Each mobile wireless communications device may also use at least one of the plurality of different operating protocols. The system may further include a protocol interface device. In particular, the protocol interface device may include a protocol engine module for communicating with the plurality of data storage devices using respective operating protocols, and a front-end proxy module coupled to the protocol engine. The front-end proxy module may include a respective proxy module for communicating with the plurality of mobile wireless communications devices using each different operating protocol, and at least one common core service module connected to the proxy modules.