A method for efficient creation of notifications in SIP
Original Publication Date: 2009-Sep-22
Included in the Prior Art Database: 2009-Sep-22
This article presents an effective way to re-send presence notification to clients using the SIP protocol without the CPU use overhead.
One of the main challenges when developing a SIP Presence Server is to be able to support high rate of SIP Message Notifications. Every SIP Publish message that is sent into the server may result in thousands of SIP Notify message (to all subscribers). The method suggested here is based on the existing SIP WAS Infrastructure - The SIP Container component.
Background: The SIP Container is an existing component inside WAS that implements JSR116 - SIP Servlet API. This container can be used by a server-side application that would like to act as a presence server. The IMS Presence Server uses this architecture model.
Our idea is based on the fact that in most cases each Publish from user1
result in a similar notify request to all subscribers on user1.
The following example is a notify message that was sent to user "email@example.com" as a result of a Publish message from user "firstname.lastname@example.org".
From: <sip: email@example.com > ;transport=TCP;tag=7537713594590189
To: <sip: firstname.lastname@example.org >;tag=1
Call-ID: email@example.com Max-Forwards: 70
CSeq: 2 NOTIFY
Content-Type: application/pidf+xml Content-Length: 393
<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:lwp="http://