TCPv2 Error Notification and Session Re-anchoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current TCP protocols lack explicit notification and collective response mechanisms for error conditions in communication sessions, leading to data leakage and inadequate security measures, especially in cases of suspected attacks or failures.

Innovation Solution

The introduction of TCPv2, which enables explicit notification and collective response management between endpoints through a novel packet structure that allows session re-anchoring without tearing down existing sessions, and provides alternative responses to error conditions beyond simple session dropping or ignoring, such as re-negotiating session keys or transferring sessions to more secure networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TCP protocols use simple session dropping or ignoring for error conditions, then device complexity is reduced, but security reliability deteriorates due to data leakage and inadequate error handling

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidprotocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The error handling mechanism is segmented into distinct notification and response phases. The error notification message separates detection information from response coordination, allowing endpoints to process errors independently while maintaining collective security policies. This segmentation enables complex security responses without requiring complex protocol state management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements feedback mechanisms where endpoints notify others of detected error conditions and receive notifications of proposed responses. This feedback loop allows the system to adapt to error conditions collectively, with each endpoint able to contribute to the security decision-making process based on local policies and global session state.

Inventive Principle:
Principle #23Feedback

2Reliability

If TCP protocols implement explicit notification mechanisms for error conditions, then security reliability is improved through collective response management, but loss of time increases due to additional notification exchanges

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidnotification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Error notification messages are sent immediately upon error detection, before the error can propagate or cause damage. The notification includes pre-packaged detection information and proposed responses, allowing receiving endpoints to prepare appropriate reactions in advance. This preliminary action reduces the overall time required for collective security response.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The error notification mechanism changes the parameter of information availability by providing comprehensive error details and proposed responses in the notification message itself. This parameter change allows endpoints to make informed security decisions without requiring multiple back-and-forth exchanges, reducing notification time while maintaining reliability.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If TCP protocols allow alternative responses to error conditions beyond simple dropping, then security reliability is improved through policy-based responses, but device complexity increases due to additional response management logic

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidresponse management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each endpoint is empowered to independently evaluate error conditions and propose responses based on its local security policies. The error notification mechanism allows endpoints to self-serve in determining appropriate responses without requiring centralized control or complex coordination logic. This self-service approach maintains security reliability while reducing overall system complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The response selection mechanism is dynamic, allowing endpoints to adapt their responses based on the specific error condition, local security policies, and the proposed responses of other endpoints. This dynamic approach enables flexible security responses without requiring rigid protocol rules, reducing the complexity of response management while improving security reliability.

Inventive Principle:
Principle #15Dynamics

4Productivity

If TCP protocols implement session re-anchoring without tearing down sessions, then productivity is improved by maintaining continuous communication, but device complexity increases due to session management overhead

Engineering Contradiction:
Improvecommunication continuityVSAvoidsession management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The session anchoring information is extracted and maintained separately from the core session data. Error notifications and re-anchoring operations work with this extracted anchoring information without requiring manipulation of the entire session state. This extraction reduces session management complexity while maintaining communication continuity for productivity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11159361B2Method and apparatus for providing notification of detected error conditions in a network
Publication Date: 2021.10.26 AT&T INTELLECTUAL PROPERTY I L P
  • US11159361B2 patent drawing
  • US11159361B2 patent drawing
  • US11159361B2 patent drawing

AI summary

Methods for managing a communication session in a communication network are disclosed. For example, a method includes detecting, by a first endpoint comprising at least one processor, an error condition associated with the communication session, sending, by the first endpoint, a notification of the error condition to a second endpoint that is using a transport layer session and receiving, by the first endpoint, a communication from the second endpoint, proposing a response to the error condition. Another method includes receiving, by a first endpoint comprising at least one processor, a notification of an error condition associated with the communication session, selecting, by the first endpoint, a response to the error condition, and sending, by the first endpoint, a communication to a second endpoint that is using a transport layer session, proposing a response to the error condition.