Real time composition of services

• US 20090016377A1
• Filed: 07/12/2007
• Published: 01/15/2009
• Est. Priority Date: 07/12/2007
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Dahlen, Torbjorn
• Granted Patent: US 9,130,873 B2
• Time in Patent Office: Days
• US Class Current: 370/467
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager

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.

Claims

1. A method comprising:

transmitting, from an originator node, a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header;

receiving, at a recipient node, said SIP message;

determining whether said SOAP envelope is intended for said recipient node;

if so, parsing, at said recipient node, said SOAP envelope from said SIP message;

dispatching said SOAP envelope to a corresponding Web Service within said recipient node; and

providing, at said recipient node, a service indicated by said SOAP action header and SOAP envelope.

2. The method of claim 1, wherein said SOAP action header includes a Web Services Description Language (WSDL) Interface and a method associated with said service.

3. The method of claim 2, wherein said WDSL Interface identifies a location of said service and said method identifies a type of said service.

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

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

6. The method of claim 5, wherein said SIP message is one of OPTIONS and MESSAGE.

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

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

35. The method of claim 1, further comprising the step of:

evaluating said SOAP action header to determine whether a corresponding Web Service is available at said recipient node.

9. A method comprising:

transmitting a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header which specify a service

10. The method of claim 9, wherein said SOAP action header includes a Web Services Description Language (WSDL) Interface that identifies a location of said service and a method that identifies a type of said service.

11. The method of claim 9, wherein said SIP message is a SIP INVITE.

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

13. The method of claim 12, wherein said SIP message is one of OPTIONS and MESSAGE.

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

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

16. 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;

parsing said SOAP envelope from said SIP message;

dispatching said SOAP envelope to a corresponding Web Service; and

providing a service indicated by said SOAP action header and SOAP envelope.

17. The computer-readable medium of claim 16, wherein said SOAP action header includes a Web Services Description Language (WSDL) Interface and a method associated with said service.

18. The computer-readable medium of claim 17, wherein said WDSL Interface identifies a location of said service and said method identifies a type of said service.

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

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

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

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

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

36. The computer-readable medium of claim 16, further comprising:

evaluating said SOAP action header to determine whether a corresponding Web Service is available.

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

transmitting a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header.

25. A communications device comprising:

a processor operating as a Session Initiation Protocol (SIP) user-agent server which receives a SIP message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header; and

a SOAP parser/dispatcher for parsing said SOAP envelope from said SIP message and transmitting said SOAP envelope to a corresponding Web Service.

26. The communications device of claim 25, wherein said SOAP action header includes a Web Services Description Language (WSDL) Interface and a method associated with said service.

27. The communications device of claim 26, wherein said WDSL Interface identifies a location of said service and said method identifies a type of said service.

28. The communications device of claim 25, wherein said SIP message is a SIP INVITE message.

29. The communications device of claim 25, wherein said SIP message is a non-session related SIP message.

30. The communications device of claim 29, wherein said SIP message is one of OPTIONS and MESSAGE.

31. The communications device of claim 25, wherein said SIP message also includes a Session Description Protocol (SDP).

32. The communications device of claim 31, wherein said SIP message is constructed using MIME multi-part.

33. The communications device of claim 25, further comprising:

a plurality of Web Service entities including said corresponding Web service; and

a corresponding applications programming interface (API) between each of said plurality of Web Service entities and said SOAP parser/dispatcher.

34. The communications device of claim 33, further comprising:

a memory device for storing a list of Web services supported by said communications device;

wherein said processor evaluates said SOAP action header to determine whether a Web Service specified thereby corresponds to one of said plurality of Web Services.