Browse Prior Art Database

A method for efficient creation of notifications in SIP

IP.com Disclosure Number: IPCOM000188098D
Original Publication Date: 2009-Sep-22
Included in the Prior Art Database: 2009-Sep-22
Document File: 2 page(s) / 27K

Publishing Venue

IBM

Abstract

This article presents an effective way to re-send presence notification to clients using the SIP protocol without the CPU use overhead.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 62% of the total text.

Page 1 of 2

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 "user1@ibm.com" as a result of a Publish message from user "user2@ibm.com".

Notify example:

NOTIFY sip:11

_fetch

From: <sip: user2@ibm.com > ;transport=TCP;tag=7537713594590189

To: <sip: user1@ibm.com >;tag=1
Call-ID: 1-3972@9.148.45.211 Max-Forwards: 70
CSeq: 2 NOTIFY
Content-Type: application/pidf+xml Content-Length: 393
Event: presence
Subscription-State: terminated;reason=timeout

Via:

SIP/2.0/TCP
9.148.45.211:5060;ibmsid=local.1209555897798

029220


Contact:

<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:lwp="http://

/

        entity="sip:user2@ibm.com">

open

<lwp:lwp

>desktop</lwp:lwp

tact>sip:user10@9.148.46.67:3365 ;trans...