Service intermediary Addressing for real time composition of services

• US 20090106428A1
• Filed: 10/23/2007
• Published: 04/23/2009
• Est. Priority Date: 10/23/2007
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Dahlen, Torbjorn
• Application Number:
  US11/975,942
• Publication Number:
  US 20090106428A1
• Time in Patent Office: Days
• US Class Current: 709/227
• 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.

Claims

1. A method comprising:

receiving, at an intermediary node, a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header;

parsing, at said intermediary node, said SOAP envelope to identify at least one SOAP action header within said SOAP envelope;

determining if said at least one SOAP action header matches a Web Service accessible via said intermediary node;

accessing, if a match occurs, a service requested by said SOAP envelope;

selectively modifying said SIP message based on said provided service; and

forwarding said selectively modified SIP message.

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.

9. The method of claim 1, further comprising:

determining, by said intermediary node, whether said SIP message includes said SOAP envelope prior to forwarding said SOAP envelope to said parsing step.

10. The method of claim 1, wherein said determining if said at least one SOAP action header matches a Web Service accessible via said intermediary node further comprises:

evaluating a SOAP role parameter within a SOAP body.

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

13. The computer-readable medium of claim 12, 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 1, wherein said determining if said at least one SOAP action header matches a Web Service accessible via said intermediary node further comprises:

evaluating a SOAP role parameter within a SOAP body.

11. 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 to identify at least one SOAP action header within said SOAP envelope;

determining if said at least one SOAP action header matches a Web Service accessible via said intermediary node;

accessing, if a match occurs, a service requested by said SOAP envelope;

selectively modifying said SIP message based on said provided service; and

forwarding said selectively modified SIP message.

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

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

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

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

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

20. A communications node comprising:

a processor operating as a Session Initiation Protocol (SIP) proxy 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, determining whether a SOAP action header within said SOAP envelope matches a Web Services which is accessible via said communications node and, if a match is found, transmitting said SOAP envelope to a corresponding Web Service.

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

22. The communications node of claim 21, wherein said WDSL Interface identifies a location of said service and said method identifies a type of said service.

23. The communications node of claim 20, 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.

24. The communications node of claim 23, 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.

25. The communications node of claim 20, wherein said processor receives a result from said corresponding Web Service, modifies said SIP message and forwards said modified SIP message.