Application-Level Acknowledgements for Data Packet Processing Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication systems lack the ability to verify that data packets are not only received but also successfully processed by the intended application on receiving devices, leading to inefficiencies in data management across networked devices.

Innovation Solution

Implementing application-level acknowledgements, where devices send acknowledgments not only upon receipt but also upon successful processing of data packets by the application, allowing for better management of communications and retransmissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If standard acknowledgements are used to verify data packet receipt, then transmission reliability is improved, but application-level processing verification is lost

Engineering Contradiction:
Improvedata packet delivery verificationVSAvoidapplication processing status
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the acknowledgement mechanism into two distinct types: transmission-level acknowledgements that confirm packet receipt, and application-level acknowledgements that confirm successful processing. This segmentation allows each layer to provide specific verification information without conflating the two functions, thereby maintaining both delivery reliability and processing status information.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a feedback mechanism where the receiving device sends application-level acknowledgements back to the sending device after the application successfully processes the data packet. This feedback loop provides end-to-end verification that the data not only reached the destination but was also correctly processed by the intended application, preventing information loss about processing status.

Inventive Principle:
Principle #23Feedback

2Reliability

If application-level acknowledgements are implemented to verify processing, then communication reliability is improved, but communication complexity increases

Engineering Contradiction:
Improveapplication processing verificationVSAvoidcommunication protocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent designs the application-level acknowledgement mechanism to be universally applicable across different applications and data types. The same acknowledgement framework can be used regardless of the specific application processing the data, reducing the need for application-specific custom protocols and thereby limiting the increase in overall system complexity.

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

Solution Approach 2:

The patent introduces an intermediary acknowledgement message that mediates between the transmission layer and the application layer. This intermediary mechanism simplifies the interaction by providing a standardized way for applications to signal successful processing without requiring complex direct communication protocols between all components, thus managing complexity while maintaining reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of energy

If only receipt acknowledgements are sent, then communication overhead is reduced, but data processing verification is insufficient

Engineering Contradiction:
Improvecommunication overheadVSAvoidprocessing completion verification
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent applies partial action by sending application-level acknowledgements only when necessary - specifically when the application has successfully processed the data packet. This selective approach avoids the excessive overhead of sending acknowledgements for every single transmission event, while still providing verification when it matters most for reliability.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the parameter of acknowledgement timing from immediate (upon receipt) to delayed (upon processing completion). This parameter change allows the system to reduce communication overhead by batching or selectively sending acknowledgements only when processing is complete, rather than for every intermediate step, thus balancing overhead with verification reliability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11088807B2Application-level acknowledgements
Publication Date: 2021.08.10 APPLE INC
  • US11088807B2 patent drawing
  • US11088807B2 patent drawing
  • US11088807B2 patent drawing

AI summary

Application-level acknowledgements may be used to verify that a data packet has not only been received, but has been successfully processed by the appropriate application operating on a device that received the data packet. For example, in one embodiment, two devices may be registered with an identity service that enables security and push messaging. A first device may communicate a data packet to another device that is associated with the same identity account through the identity service. The device receiving the data packet may send an acknowledgement verifying receipt of the data packet. After an application has processed the data packet, an acknowledgement that the data packet was processed may also be send from the second device to the first device.