HTTP Acknowledgement Control for Message Viewing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication systems do not provide a mechanism for the originator of HTTP messages to confirm whether the recipient has viewed the content of the message, leading to uncertainty about delivery and reading status.

Innovation Solution

Incorporating a digital packet structure with a header and user data segment, where an acknowledgement request command is included, requiring the recipient to authorize and send a reply before the content can be viewed, and implementing a self-addressed HTTP message to manage multiple device access without re-authorizing the acknowledgement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If HTTP messages are sent without acknowledgement requests, then ease of operation is improved, but reliability of message receipt confirmation deteriorates

Engineering Contradiction:
Improveease of operationVSAvoidreliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements an acknowledgement request mechanism where the originator sends an acknowledgement request command with the HTTP message, and the addressee's device automatically sends an acknowledgement reply when the message is viewed. This feedback loop provides reliable confirmation of message receipt and viewing status without requiring manual intervention from either party.

Inventive Principle:
Principle #23Feedback

2Reliability

If acknowledgement confirmation is required before viewing, then reliability of message receipt confirmation is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovereliabilityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent incorporates the acknowledgement request command in advance within the HTTP message itself, so that when the addressee's device receives and views the message, the acknowledgement reply is automatically generated and sent without requiring the user to manually confirm or authorize anything. The action is prepared beforehand and executed automatically.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple devices can access the same HTTP account, then adaptability is improved, but device complexity deteriorates

Engineering Contradiction:
ImproveadaptabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a self-addressed HTTP message mechanism where an acknowledgement reply sent from one device is automatically recognized and applied across all devices accessing the same HTTP account. The system treats multiple devices as equivalent access points to the same account, allowing any device to send or receive acknowledgements without requiring separate authorization for each device.

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

Data Source

PatentUS10038735B2Delivery control for HTTP communications among multiple end user communication devices
Publication Date: 2018.07.31 LOMENT INC
  • US10038735B2 patent drawing
  • US10038735B2 patent drawing
  • US10038735B2 patent drawing

AI summary

An exemplary method is implemented by end-user communication devices for transmitting and receiving HTTP messages in which acknowledgement of receipt by an addressee of an email is requested by an originator of the email. An acknowledgement request command is stored in a command portion of a user data segment of a received HTTP message. Upon receipt of the HTTP message by the addressee device, a reply HTTP message with an acknowledgement request must be authorized to be transmitted to the originator in order to allow the addressee to be able to view the content of the received HTTP message.