A METHOD FOR EVENT PACKET HANDLING

• US 20100262697A1
• Filed: 12/21/2007
• Published: 10/14/2010
• Est. Priority Date: 11/16/2007
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Boberg, Christer, Lindgren, Anders
• Granted Patent: US 8,386,616 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

A method of delivering information from a Notifying node of a SIP/IMS network to a Watcher Client, via an intermediate Watcher Proxy. A connection is established between the Watcher Proxy and the Watcher Client, using a SIP session, wherein the established connection is used for forwarding a request for a SIP subscription to the Watcher Proxy as an embedded SIP subscribe message. Once a backend SIP subscription has been setup between the Watcher Proxy and the Notifying node, SIP notify messages delivered from the Notifying node will be forwarded from the Watcher Proxy to the Watcher Client via the established connection, thereby separating SIP subscribe traffic from SIP control traffic.

Claims

1. A method of retrieving information delivered from a Notifying node (203) of a SIP/INS network to a Watcher Client (200), comprising the following steps, executed by the Watcher Client:

establishing a connection with a Watcher Proxy (202), said Watcher Proxy being adapted to handle SIP subscriptions, wherein each SIP subscription is a subscription for a specific service, said service being identified by a SIP event package,

initiating a SIP subscription between said Watching Proxy and said Notifying node, by forwarding (2;

3) an embedded SIP subscribe message to said Watcher Proxy via said connection, and

receiving (2;

7) at least one notification associated with said SIP subscription from said Watcher Proxy, said notification being delivered via said connection as an embedded SIP notify message.

2. A method according to claim 1, further comprising the step of:

buffering each of said at least one received notification prior to handling them according to predetermined rules.

3. A method according to claim 1 or 2, further comprising the following step to be executed prior to the establishing step:

setting-up a SIP session (2;

1,2;

2) with the Watcher Proxy, said SIP session being used for establishing said connection.

7. A method according to any of the preceding claims, wherein said connection is a TCP connection which is established using the SIP protocol.

8. A method according to any of the preceding claims, wherein said connection is a Message Session Relay Protocol (MSRP) connection and said embedded message is embedded into an MSRP message.

4. A method of delivering information from a Notifying node (203) of a SIP/IMS network to a Watcher Client (200), comprising the following steps:

establishing a connection with said Watcher Client, in response to a session request (2;

1,2;

2) received from the Watcher Client,

receiving (2;

3) a request for a SIP subscription from said Watcher Client, said SIP subscription, being delivered as an embedded SIP subscribe message via said connection,

setting-up (2;

4,2;

5) a backend SIP subscription with said Notifying node, in response to receiving said request,

receiving (2;

6) at least one notification associated with said SIP subscription from said Notifying node, and

transmitting (2;

7) each received notification to said Watcher Client via said connection as an embedded SIP notify message,

wherein said steps are executed by an intermediate Watcher Proxy (202), said Watcher Proxy being adapted to handle SIP subscriptions, each of which is a subscription for a specific service, each service being identified by a SIP event package.

5. A method according to claim 4, wherein said session request is a SIP invite.

6. A method according to claim 4 or 5, wherein said transmitting step is executed according to predetermined priority policies, specified for said connection.

9. A client (500) for retrieving information delivered from a Notifying node (504) of a SIP/IMS network, said client comprising:

a communication unit (501) for setting-up a SIP session with a Watcher Proxy (502), said Watcher Proxy being adapted to handle SIP subscriptions, wherein each SIP subscription is a subscription for a specific service, said service being identified by a SIP event package, and for establishing another connection with the Watcher Proxy using said SIP session, said communication unit being adapted to use said other connection for initiating a backend SIP subscription between said Watcher Proxy and said Notifying node by embedding a SIP subscribe message and by forwarding said message to the Watcher Proxy via said other connection, said communication unit also being adapted to receive at least one SIP notify associated with said SIP subscription from said Watcher Proxy and for delivering said SIP notify message as an embedded SIP notify message via said other connection, and

a processing unit (506) for processing said SIP notifying message.

10. A client according to claim 9, wherein said client is a Watcher client.

11. A client according to claim 9 or 10, wherein said communication unit further comprises:

a buffer (507) adapted to buffer each of said at least one received SIP notification messages prior to handling it, said buffering procedure being executed according to predetermined rules.

12. A client according to any of claims 9-11, wherein said client is implemented in a stationary or a mobile User equipment.

13. A client according to claim 12, wherein said User equipment is any of a:

Desktop computer, a Laptop, a mobile telephone or a PDA.

14. A node (600) for delivering information from a Notifying node (601) of a SIP/IMS network to a Watcher Client (602), said node comprising:

a first communication unit (603) for setting up a SIP session (5;

1,5;

2) with the Watcher Client, and for establishing another connection (5;

3) with said Watcher Client using said SIP session, said first communication unit being further adapted to receive a request for a SIP subscription, said request being a SIP subscribe message which is delivered via said other connection as an embedded SIP subscribe message,

a second communication unit (605) for setting up a backend SIP subscription with the Notifying node, in response to receiving said embedded SIP subscribe message and for receiving at least one SIP notify message associated with said SIP subscription from the Notifying node via said backend SIP subscription, said second communication unit also being adapted to transmit each received SIP notify message to said Watcher Client via said connection as an embedded SIP notify message, and

a processing unit (606) for embedding a received SIP notify message into another message, and for forwarding said embedded message to the Watcher Client via said first communication means and said other connection.

15. A node according to claim 14, wherein said node is a Watcher Proxy which is adapted to handle SIP subscriptions, each of which is a subscription for a specific service, being identified by a SIP event package.