SIP Messaging Disposition Notification After Session Termination

Solution Overview

Problem

Current messaging technologies fail to efficiently send disposition notifications for session-based messaging in mobile environments, where sessions often terminate before notifications can be sent, and message IDs are insufficient for routing in multi-server environments.

Innovation Solution

Implementing a method using SIP MESSAGE with a Contact Header field and feature tags to send disposition notifications after a session has terminated, associating the notification with the original server and session, and modifying messaging clients to retain SIP contact addresses and feature tags outside the session.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If session-based messaging is used to improve security and presence indicators, then messaging reliability is improved, but the system cannot send disposition notifications after session termination

Engineering Contradiction:

Improvemessaging reliabilityVSAvoidnotification delivery capability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by establishing the SIP session and exchanging message IDs before the actual messaging occurs. The server stores the message ID and contact information in advance, enabling it to route disposition notifications even after the session terminates, thus resolving the contradiction between session-based reliability and post-session notification capability

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The messaging server acts as an intermediary that maintains the message ID and contact information independently of the session state. This intermediary role allows the server to receive and route disposition notifications from recipients back to senders even when the original session has terminated, enabling notification delivery without requiring session re-establishment

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If message ID is used for routing disposition notifications, then routing simplicity is improved, but routing fails in multi-server environments with reused message IDs

Engineering Contradiction:

Improverouting complexityVSAvoidrouting accuracy

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The system adds another dimension to the routing information by including the server identifier (contact information) alongside the message ID. This dimensional extension transforms the routing from a single-parameter message ID lookup to a two-parameter system (server ID + message ID), enabling accurate routing in multi-server environments where message IDs may be reused across different servers

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The messaging server acts as an intermediary that maintains the message ID and contact information independently of the session state. This intermediary role allows the server to receive and route disposition notifications from recipients back to senders even when the original session has terminated, enabling notification delivery without requiring session re-establishment

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If session reestablishment is used to send disposition notifications, then notification delivery is enabled, but session setup and teardown overhead increases

Engineering Contradiction:

Improvenotification deliveryVSAvoidsession setup time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by establishing the SIP session and exchanging message IDs before the actual messaging occurs. The server stores the message ID and contact information in advance, enabling it to route disposition notifications even after the session terminates, thus resolving the contradiction between session-based reliability and post-session notification capability

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The messaging server acts as an intermediary that maintains the message ID and contact information independently of the session state. This intermediary role allows the server to receive and route disposition notifications from recipients back to senders even when the original session has terminated, enabling notification delivery without requiring session re-establishment

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8898235B2Method and devices for message disposition notification after session termination

Publication Date: 2014.11.25 INFINITE CONVERGENCE SOLUTIONS INC

AI summary

This provides a method as well as a client apparatus and server apparatus which will support sending and receiving a disposition notification to session based messaging clients after the message session has terminated.