Network entity for interconnecting SIP end-points of different capabilities

• US 7,554,927 B2
• Filed: 09/07/2004
• Issued: 06/30/2009
• Est. Priority Date: 09/29/2003
• Status: Expired due to Fees

• Current Assignee: Unify GmbH & Co. KG (Atos SE)
• Original Assignee: Siemens AG
• Inventors: Hanna, Thomas, Littmann, Jorg, Thiele, Ingolf, Kunte, Klaus-Josef
• Primary Examiner(s): Kizou, Hassan
• Assistant Examiner(s): ELLIOTT IV, BENJAMIN H
• Application Number:
  US10/573,675
• Publication Number:
  US 20070083658A1
• Time in Patent Office: 1,757 Days
• Field of Search: 370/260, 370/219, 370/352, 370/259, 370/261, 370/265, 370/271, 370/277, 370/310, 370/349, 370/389, 370/395.52, 370/410, 370/252, 709/227, 709/228, 709/203, 709/209, 455/415, 455/416, 455/412.2, 455/414.1, 455/417, 455/425, 455/436, 455/461, 455/407
• US Class Current: 370/252
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 3/4285 Notifying, informing or entertaining a held party while on hold, e.g. Music On Hold

Abstract

There is described a Session Initiation Protocol (SIP) network entity for operating in a communications channel between a first SIP end point and a second SIP end point in a communication network. The first SIP end point has available a first set of communication features and the second SIP end point has available a second set of communication features, including at least one communication feature, for example Music on Hold, that is unavailable to the first SIP end point. The network entity acts as a client application for the first SIP end point and as a server application for the second SIP end point and is arranged to exchange signaling information with the SIP end points to enable the second SIP end point to utilize the at least one communication feature during communications with the first SIP end point.

Claims

1. A method for operating a Session Initiation Protocol (SIP) network entity in a communication channel between a first SIP user agent and a second SIP user agent in a packet based communication network with available a first set of communication features supported by the first SIP user agent and available a second set of communication features supported by the second SIP user agent, including at least one communication feature in the second set of communication features which is not supported by the first SIP user agent, comprising:

acting as a client application for the first SIP user agent and as a server application for the second SIP user agent; and

arranging to exchange signaling information with the first and second user agents to enable the second SIP user agent to utilize the at least one communication feature which is unsupported by the first SIP user agent during communications with the first SIP user agent.

2. The method as claimed in claim 1, wherein a call routing addresses signaling information that is exchanged between the SIP network entity and the first and second SIP user agents or the SIP network entity and the communication network.

3. The method as claimed in claim 2, wherein a payload routing addresses payload data received at the SIP network entity for routing to the first or second SIP user agents.

4. A network entity for operating a Session Initiation Protocol (SIP) network in a communication channel between two end points in a packet based communication network, comprising:

a first SIP user agent being a first end point and supporting a basic SIP communication feature set;

a second SIP user agent being a second end point and supporting an enhanced SIP communication feature set; and

a SIP Basic Call Enhancer located within the communication channel between the first and second SIP user agents that enables the second SIP user agent to utilize the enhanced SIP communication feature set which is unavailable to the first SIP user agent when communicating with the first SIP user agent.

5. The network entity as claimed in claim 4, wherein the basic SIP communication feature set supports session initiation and termination.

6. The network entity as claimed in claim 4, wherein the enhanced SIP communication feature set supports session initiation and termination, and an enhanced set of telephony features selected from the group consisting of:

call waiting, call transfer, conference calling, call hold, and music on hold.

7. The network entity as claimed in claim 4, wherein the SIP Basic Call Enhancer comprises:

a user agent server part that exchanges messages with the first SIP user agent,

a user agent client part that exchanges messages with the second SIP user agent,

a local configuration store that stores information required for the Basic Call Enhancer to route messages,

a call router that involves the first and second SIP user agents in an enhanced SIP session,

a session controller that transfers messages from the user agent server part to the call router and from the call router to the user agent client part to keep track of session states and progress, and

a payload router that manages media streams so that the Basic Call Enhancer functions as a virtual end point to both the first and second SIP user agents in respect of the media streams.

8. The network entity as claimed in claim 4, wherein the SIP Basic Call Enhancer functions as a client application for the first end point.

9. The network entity as claimed in claim 4, wherein the SIP Basic Call Enhancer functions as a server application for the second endpoint.