Interaction ID for SIP Session Continuation in DNS Mode

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication servers face challenges in managing multiple communication pathways within a single session, particularly when in a Deny New Service (DNS) mode, as they struggle to associate new messages with existing sessions across different protocols, leading to disruptions and inefficiencies.

Innovation Solution

The introduction of an 'interaction ID' allows servers to associate new messages with existing SIP sessions even in DNS mode, enabling the continuation of communication sessions without additional overhead, by specifying the interaction ID in callback URLs and ensuring that messages related to ongoing interactions are processed, even when the server is in DNS mode.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server is placed in Deny New Service (DNS) mode to shed communications when overloaded or enable maintenance, then existing communication tasks are allowed to continue but new tasks are declined, but this causes the server to be unable to accept new communication sessions even when they are associated with existing interactions

Engineering Contradiction:
Improvecontinuation of existing communication tasksVSAvoidability to accept new communication sessions
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the communication session identification into two distinct components: session ID and interaction ID. The session ID identifies a specific communication session, while the interaction ID identifies the broader interaction context. This segmentation allows the server to distinguish between completely new interactions (which should be denied in DNS mode) and new sessions that are part of existing interactions (which should be accepted), thereby resolving the contradiction between maintaining existing tasks and accepting relevant new sessions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension to session identification by adding the interaction ID layer above the traditional session ID. This dimensional enhancement allows the server to evaluate incoming sessions from multiple perspectives: the specific session level and the broader interaction level. By checking both dimensions, the server can make more nuanced decisions about whether to accept or deny new sessions in DNS mode, resolving the binary contradiction.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If the server denies all new messages in DNS mode to manage load, then server overload is reduced, but this prevents association of new messages with existing sessions across different protocols

Engineering Contradiction:
Improveserver load managementVSAvoidloss of interaction context across protocols
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The interaction ID serves as a universal identifier that spans multiple communication protocols (SIP, HTTP, web chat). By using this protocol-agnostic identifier, the server can maintain interaction context across different protocol boundaries even when in DNS mode. This universality allows the server to selectively accept cross-protocol messages that belong to existing interactions while still denying unrelated new messages, thus managing load without losing interaction context.

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

Solution Approach 2:

The interaction ID acts as an intermediary that bridges different communication protocols and sessions. When a new message arrives with an interaction ID that matches an existing interaction, this intermediary identifier enables the server to recognize the message's relevance and process it appropriately, even in DNS mode. This mediator mechanism prevents loss of interaction context while maintaining load management.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If the server uses traditional session ID identification, then individual communication sessions can be tracked, but this prevents recognition that multiple sessions belong to the same interaction

Engineering Contradiction:
Improvesession tracking accuracyVSAvoidloss of interaction-level context
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent segments the identification hierarchy into session ID (for tracking individual sessions with precise accuracy) and interaction ID (for recognizing broader interaction context). This segmentation allows the system to maintain precise session-level tracking while simultaneously enabling interaction-level recognition, resolving the contradiction between measurement precision and information completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

By adding the interaction ID dimension to the traditional session ID system, the patent enables multi-level identification. The session ID provides precise tracking at the session level, while the interaction ID adds a new dimension that reveals the broader interaction context. This dimensional enhancement allows the server to recognize that multiple sessions with different session IDs belong to the same interaction, preventing loss of interaction-level context.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11750528B2Communication session addition via a host in deny new service mode
Publication Date: 2023.09.05 AVAYA INC
  • US11750528B2 patent drawing
  • US11750528B2 patent drawing
  • US11750528B2 patent drawing

AI summary

Communication servers hosting interactions between requesting devices and resources may require load sheading or maintenance and, as a result, be placed in Deny New Service (DNS) mode, whereby a subsequent session request is refused while existing sessions continue until concluded. However, an interaction comprising an existing session may be supplemented by a subsequent session, often utilizing a different application layer implementation. By providing the requesting device with an interaction identifier, a subsequent session made after the server has been placed in DNS mode, may be accepted and associated with the same resource associated with the existing session.