Method and session initiation protocol (SIP) server for the exchange of end-point capabilities

• US 20060047840A1
• Filed: 08/31/2004
• Published: 03/02/2006
• Est. Priority Date: 08/31/2004
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Postmus, Peter
• Application Number:
  US10/929,402
• Publication Number:
  US 20060047840A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities

Abstract

A method and Session Initiation Protocol (SIP) application server for efficiently creating a SIP message, such as a SIP request or response message. A new service is installed in the server, and a service engine of the server acquires information regarding end-point capabilities (e.g. option tags or feature tags) associated with the service, possibly from a deployment descriptor file of the SIP service. During operation, a SIP message is created by the service, and sent to the engine, which detects if end-point capabilities should be added to the message. If so,the engine includes in the appropriate headers of the SIP message the proper end-point capabilities information, which may be zero, one or more option tags, and/or zero, one or more feature tags.

Claims

1. A method for creating a Session Initiation Protocol (SIP) message, the method comprising the steps of:

a. sending a SIP message from a SIP service running on a SIP application server to a SIP engine of the server;

b. including by the SIP engine in the SIP message information relative to end-point capabilities; and

c. sending the SIP message including the information relative to end-point capabilities from the SIP application server.

2. The method claimed in claim 1, wherein the information relative to end-point capabilities comprises option tags.

3. The method claimed in claim 1, wherein the information relative to end-point capabilities comprises feature tags.

4. The method claimed in claim 1, the method further comprising before step b. the step of:

d. detecting a need to add the end-point capabilities to the SIP message;

wherein step b. is performed responsive to step d.

5. The method claimed in claim 1, the method further comprising, prior to step a., the steps of:

d. installing the SIP service on the SIP application server; and

e. analysing by the SIP engine the SIP service and acquiring knowledge about the information relative to end-point capabilities of the SIP service.

6. The method claimed in claim 5, wherein step e. comprises analysing by the SIP engine a deployment descriptor file associated with the SIP service and acquiring knowledge about the information relative to end-point capabilities of the SIP service from the deployment descriptor file.

7. The method claimed in claim 5, further comprising the steps of:

f. receiving an incoming SIP request message at the SIP application server, the incoming SIP request message being destined to an end-point associated to the SIP service;

g. detecting that the incoming SIP message is destined to the end-point associated to the SIP service;

h. responsive to step g., relaying the incoming SIP request message from the SIP engine to the SIP service; and

i. upon receipt of the incoming SIP request message by the SIP service, processing the message;

wherein step a. is performed as a result of step i.

8. The method claimed in claim 1, wherein the SIP message including the information relative to end-point capabilities is a SIP request message.

9. The method claimed in claim 1, wherein the SIP message including the information relative to end-point capabilities is a SIP response message.

10. A Session Initiation Protocol (SIP) application server comprising:

a SIP engine supporting SIP communications; and

a SIP service running on the SIP server;

wherein a SIP message is sent from the SIP service to the SIP engine, which includes in the SIP message information relative to end-point capabilities and further sends the SIP message including the information relative to end-point capabilities from the SIP application server.

11. The SIP application server claimed in claim 10, wherein the information relative to end-point capabilities comprises option tags.

12. The SIP application server claimed in claim 10, wherein the information relative to end-point capabilities comprises feature tags.

13. The SIP application server claimed in claim 10, wherein the SIP engine first detects a need to add the end-point capabilities to the SIP message, and then includes the information relative to end-point capabilities in the SIP message.

14. The SIP application server claimed in claim 10, wherein the SIP service is installed in the SIP application server, and the SIP engine analyses the SIP service for acquiring knowledge about the information relative to end-point capabilities of the SIP service.

15. The SIP application server claimed in claim 14, wherein:

the SIP service is associated with a deployment descriptor file that includes information about the SIP service end-point capabilities, wherein when the SIP engine analyses the SIP service, the SIP engine analyses the deployment descriptor file associated with the SIP service and acquires knowledge about the information relative to end-point capabilities of the SIP service from the deployment descriptor file.

16. The SIP application server claimed in claim 14, wherein an incoming SIP message is received at the SIP application server, the incoming SIP message being destined to an end-point associated to the SIP service, the SIP engine detects that the incoming SIP message is destined to the end-point associated to the SIP service and relays the incoming SIP message to the SIP service, which processes the message, wherein the SIP message is sent from the SIP service to the SIP engine as a result of the message processing.

17. The SIP application server claimed in claim 10, wherein the SIP message including the information relative to end-point capabilities is a SIP request message.

18. The SIP application server claimed in claim 10, wherein the SIP message including the information relative to end-point capabilities is a SIP response message.