Service discovery associated with real time composition of services

• US 20090113077A1
• Filed: 10/26/2007
• Published: 04/30/2009
• Est. Priority Date: 10/26/2007
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Dahlen, Torbjorn
• Application Number:
  US11/977,931
• Publication Number:
  US 20090113077A1
• Time in Patent Office: Days
• US Class Current: 709/250
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• 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]

Abstract

Real-time service composition is provided by a Session Initiation Protocol (SIP) transport binding for Simple Object Access Protocol (SOAP) messages. A SOAPAction header and SOAP envelope can be included in a SIP message to identify a requested service. The SIP message recipient can parse out the SOAP envelope and forward same to a corresponding Web Service. An intermediary node, including a SIP Proxy, can evaluate incoming SIP/SOAP messages and provide requested services to which they have access. Service discovery is facilitated by adding Universal Description, Discovery and Integration (UDDI) services requests and responses.

Claims

1. A service discovery method comprising:

receiving a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header, said SOAP action header indicating that said SIP message includes a Universal Description, Discovery and Integration (UDDI) service discovery request;

parsing said SOAP envelope to identify said SOAP action header within said SOAP envelope;

accessing a UDDI registry to obtain a service list; and

forwarding said service list.

2. The method of claim 1, wherein said SIP message is a SIP INVITE message.

3. The method of claim 1, wherein said SIP message is a non-session related SIP message.

4. The method of claim 3, wherein said SIP message is one of OPTIONS and MESSAGE.

5. The method of claim 1, wherein said SIP message also includes a Session Description Protocol (SDP).

6. The method of claim 5, wherein said SIP message is constructed using MIME multi-part.

7. The method of claim 1, wherein said step of forwarding said service list further comprises:

modifying said SIP message to include a Record route header;

receiving a response to said SIP message;

adding said service list to said response; and

forwarding said response.

8. The method of claim 1, wherein said service list is a list of Web Services available at a node which receives said SIP message.

21. The method of claim 1, wherein said SOAP envelope includes a parameter which instructs an intermediary node to store said service list and to forward said service list in a response to said SIP message.

9. A computer-readable medium containing instructions which, when executed on a processor, perform the steps of:

receiving a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header, said SOAP action header indicating that said SIP message includes a Universal Description, Discovery and Integration (UDDI) service discovery request;

parsing said SOAP envelope to identify said SOAP action header within said SOAP envelope;

accessing a UDDI registry to obtain a service list; and

forwarding said service list.

10. The computer-readable medium of claim 9, wherein said SIP message is a SIP INVITE message.

11. The computer-readable medium of claim 9, wherein said SIP message is a non-session related SIP message.

12. The computer-readable medium of claim 11, wherein said SIP message is one of OPTIONS and MESSAGE.

13. The computer-readable medium of claim 9, wherein said SIP message also includes a Session Description Protocol (SDP).

14. The computer-readable medium of claim 9, wherein said SIP message is constructed using MIME multi-part.

15. The computer-readable medium of claim 9, wherein said step of forwarding said service list further comprises:

modifying said SIP message to include a Record route header;

receiving a response to said SIP message;

adding said service list to said response; and

forwarding said response.

16. The computer-readable medium of claim 9, wherein said service list is a list of Web Services available at a node which receives said SIP message.

22. The computer-readable medium of claim 9, wherein said SOAP envelope includes a parameter which instructs an intermediary node to store said service list and to forward said service list in a response to said SIP message.

17. A communications node comprising:

a processor operating as one of;

a Session Initiation Protocol (SIP) proxy and a SIP user agent server (UAS) and which receives a SIP message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header indicating that said SIP message includes a

Universal Description, Discovery and Integration (UDDI) service discovery request;

a SOAP parser/dispatcher for parsing said SOAP envelope from said SIP message; and

a UDDI registry which provides a list of services which are accessible via said communications node in response to said UDDI service discovery request.

18. The communications node of claim 17, wherein said list of services includes a list of Web Services and further comprising:

a corresponding applications programming interface (API) between each of a plurality of Web Service entities which are accessible via said communications node and said SOAP parser/dispatcher.

19. The communications node of claim 17, wherein if said processor is operating as a SIP proxy, then said processor modifies said SIP message to include a Record route header, receives a response to said SIP message, adds said service list to said response, and forwards said response.

20. The communications node of claim 17, wherein if said processor is operating as a SIP UAS, then said processor modifies said SIP message to include said service list.

23. The communications node of claim 17, wherein said SOAP envelope includes a parameter which instructs an intermediary node to store said service list and to forward said service list in a response to said SIP message.