Enhanced HTTP Messaging Protocol for Bi-directional Communication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing communication protocols like HTTP are limited to unidirectional communication, making them unsuitable for bi-directional communication systems and unable to fully leverage device capabilities, leading to inefficiencies in device-server interactions.

Innovation Solution

An enhanced HTTP messaging protocol that enables bi-directional communication by using a mailbox system on the server for message storage and retrieval, allowing clients to check for pending messages and indicate message processing completion through special headers and notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional HTTP protocol is used for communication, then implementation is simple and standard, but communication is limited to unidirectional only

Engineering Contradiction:

Improvecommunication directionalityVSAvoidprotocol complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The communication protocol is segmented into distinct message types (request messages, response messages, notification messages) with specific structures and handling rules. This allows the system to achieve bi-directional communication capabilities while maintaining clear separation of communication patterns, reducing the complexity burden of supporting multiple communication modes.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a message queue mechanism as an intermediary layer between the HTTP protocol and the application logic. Messages are queued and processed asynchronously, enabling the system to handle both request-response patterns and push notification patterns through a unified messaging interface, thus achieving bi-directional communication without significantly complicating the core HTTP implementation.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If custom protocol is implemented for each connectivity server, then device capabilities can be fully leveraged, but development complexity increases

Engineering Contradiction:

Improvedevice capability utilizationVSAvoiddevelopment ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal message format and processing mechanism that can handle multiple communication patterns (requests, responses, notifications) within a single protocol framework. This universal messaging system can adapt to different device capabilities while maintaining a consistent interface, reducing development complexity compared to implementing separate custom protocols for each server.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The message structures include flexible parameters and headers that can be adjusted based on device capabilities and communication requirements. By changing message parameters rather than implementing entirely different protocols, the system can leverage different device capabilities while maintaining a single, manageable protocol implementation.

Inventive Principle:

Principle #35Parameter changes

3Loss of information

If HTTP status code is returned, then message receipt confirmation is provided, but actual processing acknowledgment is lacking

Engineering Contradiction:

Improveprocessing status informationVSAvoidmessage handling complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a feedback mechanism where the server sends notification messages back to the client to confirm actual message processing. This feedback loop provides comprehensive status information about message receipt and processing, going beyond simple HTTP status codes. The notification messages include detailed information about processing outcomes, enabling the client to track message status accurately.

Inventive Principle:

Principle #23Feedback

4Adaptability or versatility

If mailbox system is implemented for bi-directional communication, then communication capability is enhanced, but system complexity increases

Engineering Contradiction:

Improvecommunication capabilityVSAvoidsystem structure complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the mailbox concept with the existing HTTP message handling infrastructure. Instead of implementing a separate mailbox system, the notification messages are integrated into the HTTP response flow, and message queuring is combined with the request-response cycle. This merging approach enables bi-directional communication capabilities while reducing system structure complexity by avoiding redundant components.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS8775509B2Enhanced HTTP messaging for devices

Publication Date: 2014.07.08 DIGI INTERNATIONAL

AI summary

Disclosed in some examples is a method for communications between a client and a server using a stateless messaging protocol by transmitting from a client to a server a first message using the stateless messaging protocol; receiving from the server a response message, the response message including an indication of the presence of a second message at the server intended for the client, the indication including message retrieval information; sending a third message from the client to the server including the message retrieval information; and receiving a fourth message from the server, the fourth message including the contents of the second message.