SIP Proxy Server Embedding Ancillary Data in Emergency Calls

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current SIP-based communication systems lack a mechanism to effectively include and securely transmit ancillary data alongside location information, particularly in emergency calls, which is essential for comprehensive data delivery and security.

Innovation Solution

A SIP proxy server is introduced to embed ancillary data within the SIP message header using an XML/tagged structure, allowing for the inclusion of various types of data such as medical history or multimedia, and enabling encryption and digital signing for secure transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If URIs are provided with SIP messaging, then location information can be delivered, but ancillary data cannot be embedded within the SIP body part

Engineering Contradiction:
Improveancillary data deliveryVSAvoidSIP message structure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent embeds ancillary data within the SIP message body by nesting XML-tagged data structures inside the SIP protocol framework. The ancillary data is contained within <AncillaryData> tags that are nested within the SIP message body, allowing multiple levels of data organization and encryption while maintaining SIP protocol compatibility.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent introduces an XML tagging system as an intermediary layer between the SIP protocol and the ancillary data. This intermediary structure allows diverse data types to be standardized, encrypted, and transmitted within the SIP message body without requiring fundamental changes to the SIP protocol itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data is provided as separate body parts, then encryption can be applied, but the data cannot be integrated within the SIP message itself

Engineering Contradiction:
Improvedata securityVSAvoiddata integration
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent merges the ancillary data with the SIP message by embedding the encrypted XML-tagged data directly within the SIP message body. This combining approach ensures that the ancillary data travels with the SIP message through the same communication channel, maintaining both security and integration.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent applies encryption and digital signature parameters to the ancillary data within the XML structure. By changing the state of the data through encryption before embedding it in the SIP message, the system maintains security while achieving seamless integration.

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If multiple databases are queried for location and routing information, then comprehensive data can be obtained, but transmission time increases

Engineering Contradiction:
Improvelocation and routing dataVSAvoiddata transmission time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent performs database lookups for location and routing information before the SIP message is transmitted. By completing these data retrieval operations in advance and embedding the results within the ancillary data structure, the system eliminates delays during message transmission while ensuring comprehensive information is available.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7929530B2Ancillary data support in session initiation protocol (SIP) messaging
Publication Date: 2011.04.19 TELECOMMUNICATION SYSTEMS INC
  • US7929530B2 patent drawing
  • US7929530B2 patent drawing
  • US7929530B2 patent drawing

AI summary

A SIP ancillary data server provides host to auxiliary data for an emergency SIP session (call) uniquely referred to in a transported SIP header. In a manner similar to how location is represented in an emergency call, a SIP header is extended. The extended SIP Header contains one of two possible types of content elements: either (a) a content pointer element to a SIP Message body part (a “cid:”, or content identifier); or (b) an &lt;information_URI&gt; (a.k.a, “info_URI” in this document).