DE112008001604T5 - Real-time composition of services - Google Patents

Abstract

Method, comprising:
Transmitting (300), from an originating node (100), a Session Initiation Protocol (SIP) message including a simple Object Access Protocol (SOAP) envelope and a SOAP action header;
Receiving (302), at a receiving node (110), the SIP message;
Determining (303) if the SOAP envelope is destined for the receiving node;
if yes, parsing (304), at the receiving node (110), the SOAP envelope from the SIP message;
Sending (306) the SOAP envelope to a corresponding web service (210, 212) within the receiving node; and
Providing (308), at the receiving node (110), a service indicated by the SOAP action header and the SOAP envelope.

Description

TECHNICAL AREA

The The present invention relates generally to communications and more particularly to methods, apparatus and systems for providing Real-time composition of services in communication systems.

BACKGROUND

communications systems continue to be subject to growth and development. A convergence between different types of communication systems, e.g. B. the Internet Protocol (IP), connection-based voice communications and the like progresses rapidly. Recently the term "network next generation "(NGN, Next Generation Network) has been used to perform various activities to describe those associated with this evolution. How through the International Telecommunication Union (ITU) is defined a NGN is a packet-based network that is able to provide services (including telecommunications services), and that is capable of multiple broadband, QoS-enabled To use transport technologies and in the service-related functions regardless of underlying transport-related technologies are. NGNs probably also provide unlimited access Users on different service providers and support a general mobility, which in turn is a consistent Provide service delivery to end users.

So-called "web services" are another feature that can become common with NGNs. Web services, for example, provide a mechanism for interoperability between software entities that reside on different infrastructures and that can be operated by different companies. Web services are typically considered to provide distributed services using e.g. Standard Web Services Description Language (WDDL), Simple Object Access Protocol (SOAP) and Universal Description, Discovery and Integration (UDDI, Universal Description, Discovery and Integration) ) Are defined. A description of WDSL can be viewed online by interested readers as " Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language, W3C Working Draft 3, August 2004 " under http://www.w3.org/TR/2004/WD-wsdl20-20040803/ , the disclosure of which is hereby incorporated by reference. Similarly, a description of SOAP online can be used as " SOAP Version 1.2 Part 0: Primer (Second Edition), W3C Recommendation 27 April 2007 " on http://www.w3.org/TR/soap12-part()/ can be found, the disclosure of which is hereby incorporated by reference. Additionally, a standard document for UDDI entitled " UDDI Version 3.0.2 UDDI Spec Technical Committee Draft, dated 20441019 " on http://uddi.org/pubs/uddi_v3.htm being found.

Web services can be used as a technology to expose application functionality as services for software clients or for server applications be characterized. Among other things, web services allow one Rapid creation of new services by combining existing functionality in new ways. This process is often called a composition or Called orchestration. Typically, web services come with XML-encoded SOAP messages using Hyper-Text Transfer Protocol (HTTP) accessed as a carrier. However, HTTP is for Transaction-based client / server request patterns have been designed where no real-time properties are required. Consider in this regard, the variable and sometimes prolonged delays, which can occur when a user has a web page by clicking on an HTTP hyperlink. With increasing demand on service interaction and rapid composition by the users from node to node real-time communication services, there is one Need to use the web services paradigm also on this real-time domain apply.

Corresponding It would be desirable to have this requirement through Provide techniques of real-time composition of services in communication systems.

SUMMARY

According to an exemplary embodiment, a method includes the steps of transmitting, from an originating node, a Session Initiation Protocol (SIP) message including a simple Object Access Protocol (SOAP) envelope and a SOAP action header, receiving, at a receiving node SIP message, determining whether the SOAP envelope is destined for the receiving node, if yes, the parsing, at the receiving node, the SOAP envelope from the SIP message, the Abschi SOAP envelope to a corresponding web service within the receiving node and providing a service indicated by the SOAP action header and SOAP envelope.

According to one Another exemplary embodiment includes a method the steps of sending a Session Initiation Protocol (SIP) message including a simple Object Access Log (SOAP) envelope and SOAP action headers specifying a service.

According to another exemplary embodiment a computer-readable medium instructions that when executed on a processor, the steps of receiving a Session Initiation Protocol (SIP) message including a simple Object Access Protocol (SOAP) envelope and a SOAP action header, parsing the SOAP envelope the SIP message, sending the SOAP envelope to a corresponding one Web service and receiving a service through the SOAP envelope and is indicated by the SOAP action header.

According to another exemplary embodiment a computer-readable medium instructions that when executed on a processor, the steps of sending a Session Initiation Protocol (SIP) message, a simple Object Access Protocol (SOAP) envelope and a SOAP action header.

According to another exemplary embodiment a communication device a processor acting as a Session Initiation Protocol (SIP) user agent server, receiving a SIP message containing a simple Object Access Protocol (SOAP) envelope and includes a SOAP action header, and a SOAP parser / dispatcher to parse the SOAP envelope from the SIP message and send the SOAP envelope works on a corresponding web service.

BRIEF DESCRIPTION OF THE DRAWINGS

The attached drawings illustrate exemplary embodiments, in which:

1 (a) the transmission of a SIP message containing a SOAP load, according to an example embodiment;

1 (b) confirming the SIP message containing the SOAP freight according to an exemplary embodiment;

2 FIG. 10 is a flowchart illustrating a method according to an example embodiment; FIG.

3 another flowchart illustrating another method according to another exemplary embodiment; and

4 FIG. 3 illustrates a communication device according to an example embodiment. FIG.

DETAILED DESCRIPTION

The following detailed description of the exemplary embodiments refers to the attached drawings. the same Reference numerals in different drawings identify the same or similar elements. Also limited to the following detailed description of the invention is not. Instead, that is Scope of the invention by the appended claims Are defined.

In accordance with exemplary embodiments, a solution is provided for the need for real-time composition of services through a Session Initiation Protocol (SIP) transport binding for SOAP messages. For example, SIP signaling is described in the standard document titled " Session Initiation Protocol, RFC 3261, author Rosenberg et al, IETF 2002 "Described that online http://tools.ietf.org/html/rfc3261 is available and the disclosure of which is incorporated herein by reference. As stated therein, SIP provides an application layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include, for example, Internet phone calls, multimedia distribution, and multimedia conferencing. SIP invitations are used to create sessions and session descriptions that allow attendees to agree on a set of compatible media types. Proxy servers are used in SIP environments to route route requests to the user's current location, authenticate and authorize users for services, implement vendor call routing policies, and provide features to users. Of particular interest to the present application, SIP provides real-time services through the use of timers that ensure minimal transaction delays.

SIP service requests may, for example, be either (1) a request to start an application, eg. A request to play a game of chess, or (2) a requirement of any Data to be provided or from a transaction, to do that as part of a more complex interaction is to be characterized. The required services addressing differs depending on which of the two cases be considered. For the former case (1), referred to herein as the "application start case" SIP is used to locate and provide parameters, to the request for an application that can be started z. A multimedia phone application, a chat application, a chess application, etc. to suit. In that case, the launched application application-specific signaling under Use of session SIP signaling or any other Take over log. Thus, there is a need for precise service identification and / or deployment of service parameters generally nonexistent or at least very limited to support SIP service requirements, that involve launching applications. Instead, it is for such SIP requests the identification of service capabilities significant.

Of the second case (2), referred to herein as the "business process integration case" becomes involved in accessing services on a composition complex functions from a number of more or less independent participatory functions, eg. B. Publication of a Line state notification when a SIP session is established becomes. This business case integration case applies For example, whenever a user has a specific service on the network wants or needs (as opposed to requesting any service that provides certain skills), or whenever input parameters are necessary to perform the service. Thus, in the business process integration case, the opposite is true to the application start case the ability to be precise Identification of a requested service and / or provision of service parameters important while the ability a requested ability to specify less important is. Exemplary embodiments of the present invention strive for the business process integration case to enable. However, SIP services addressing is common regarded as applicable only to the start of the application, which requires that an application that is started using SIP a second protocol (for example, HTTP) is used to call the business method perform. This makes existing SIP service addressing alone, based on capabilities, for real-time service composition ineffective.

Accordingly These example embodiments provide a SIP transport binding ready for SOAP messages, d. H. exemplary techniques for transporting SOAP messages between SOAP nodes at Use of SIP as a carrier. A reality-related Example of a business integration case is an example the usefulness of such a transport commitment. you For example, assume that a TV channel with a phone number for charity calls at one of the shows, which is sent, is associated, z. On an IPTV multicast session (Multicast). If Alice calls the TV station, z. B. using a provided link they found on a web page has the call in real time to a charity pay service who charges her with a donation before the call is made TV Studio is relayed to where she is with one of the TV show hosts can speak. This can be done according to exemplary Realizations are effected in real time by the SOAP-assisted addressing mechanism using is used effectively by SIP as a carrier. For example can by adding a SOAPAction header to a SIP message a SIP User Agent Server (UAS) as the final recipient of the SOAP envelope in the SIP payload. In addition, can a WSDL interface can be used to provide the semantics of a Describe web service requested for the corresponding ones Tools autogenerating client stubs to use the service. Note in this regard that WSDL 2.0 of "PortTypes" in However, WSDL 1.0 has migrated to "Interfaces" both can be used as examples of mechanisms which point to specific services, d. H. Web services and in one SIP / SOAP binding can be used. For example, see this Document WSDL 2.0, section 2.2, incorporated by the above reference is. Similarly, in SOAPActions minds provided "Methods" according to this exemplary embodiment, an indicator of a service type which is requested when a web service has a number of different service variants could provide. That way, having a place associated with an identification and / or input parameters of a service Provided information in the SIP message in a manner which is specific enough to the user with a particular services instance or interface to connect. Some detailed examples follow now.

First starting with the SIP / SOAP message itself below, various examples of a SIP message carrying one or more SOAP data items as payload are presented below in accordance with exemplary embodiments. A SOAPAction header is provided within the SIP content to allow the receiving SIP endpoint to determine if the embedded SOAP envelope is to be forwarded for further processing, e.g. If the receiving node supports the Web service identified in the SOAPAction header. The SOAPAction header provided in the SIP transport binding for SOAP according to these exemplary embodiments uses the URI syntax in a generic manner as follows:
SOAPAction: "URI"

A more specific example of a SOAPAction header according to these exemplary embodiments includes a uniform resource name (URN). As will be appreciated by those skilled in the art, a URN is a URI that identifies a resource by names in a particular namespace. In the context of these example embodiments, the URN syntax in a SOAPAction header may be as follows:
SOAPAction: "urn: <NID>: <NSS>",
where NID is a namespace identifier following, for example, the syntax for NIDs contained in URN Syntax, RFC 2141, R. Moats, IETF 1997 , and NSS has the following syntax:
NSS: "<Interface>! <MethodName>"

Of the SOAPAction header URI shows the final recipient the embedded in the SIP message SOAP message to which which wears according to these exemplary Embodiments. By adding a SOAPAction header An interface and method can be used to form a SIP message addressed using the namespace-specific part of the URN become. This allows SIP proxies and other nodes on the routing path of a specific message, the message is correct to process. The SOAP body references that of the addressed one Interface provided method. This procedure is used in SOAPAction header immediately after the separator called the an exclamation mark in this exemplary embodiment is. However, professionals will recognize that, according to others exemplary embodiments, any non-reserved Sign or a sign without any meaning other than a separator between the interface and the procedure in SOAPAction headers can be used.

you Consider the other example of a SOAPAction header below along with a SOAP body included in SIP / SOAP messages according to these exemplary embodiments may be used.

In This example shows the QuoteBean interface in the SOAPAction header referenced. The method provided by QuoteBean becomes Called GetLastTradePrice. This procedure is used in the SOAPAction header referenced after the exclamation mark. The SOAP body can more details regarding the specified procedure, including Parameters included. For example, consider the more detailed example below. In it, the web service is pointed to by the SOAP payload is accessed, stock quotes ready. More specific demands this particular SOAP message is the last listing for The current price of Ericsson shares referred to by a "QuoteBean" Interface. This snippet of code allows Alice to request a stock quote that they receive from the UAS who represents Bob, who will be a stockbroker can. The listing is for example in the 200 OK message returned by Bob as a SOAP envelope. alternative could be a SIP proxy on a route between the device by Alice and the device of Bob Alice provide the listing, in which case, the SIP proxy node is then in the SOAPAction header would have been addressed.

you in turn, notice that a SOAPAction header is the list of standard SIP headers is added and set bold in the example above is. The SOAPAction header contains a Uniform Resource Identifier (URI) that identifies a web service that is optional as a WSDL interface (QuoteBean) and a method name (GetLastTradePrice) can be described, creating a mechanism according to these exemplary embodiments for precise Identification of a requested service is provided. In addition, in this example, the parameter "ERIC B "in the SOAP envelope provided to the requested service to specify more completely, d. H. the current share price Ericsson shares with the ERIC B symbol. It will However, some service requirements are recognized to be more parameters may require (or no parameters) to the desired To fully specify service, and as such a SIP / SOAP message according to these exemplary ones Embodiments contain as many parameters as necessary.

Having illustrated some code snippets of an exemplary SIP / SOAP combination and exemplary SOAP syntax for implementing a SIP transport binding of an embedded SOAP message, some high level implementations using such messages will now provide a real-time composition of Services according to these exemplary embodiments. 1 (a) FIG. 10 illustrates one way in which an application or device according to these example embodiments uses a SOAP client to construct a SOAP envelope to invoke a web service method while a SIP session is between an originating node 100 and a receiving node 110 is initiated. It uses the client application 200 an application programming interface (API) to make a SOAP message using a SOAP client 202 For example, create a SOAP envelope with a SOAP body with optional additional parameters that apply to the service to be requested are indicative. The SOAP message, of which examples are provided above, is then loaded, in whole or as part of the payload, in one of the SIP User Agent Client (UAC). 204 generated SIP message, such as a SIP INVITE message, forwarded together with the SOAPAction header. The SIP UAC 204 can use client stubs generated by WSDL interfaces Syntax to create the SOAPAction header and envelope. It will be appreciated, however, that SIP messages other than SIP INVITE may be used to guide the SOAP payload according to these example embodiments, e.g. SIP OPTIONS or MESSAGE if session initiation is not required for the specific service request.

The SIP UAC 204 For example, the message is sent via a User Datagram Protocol (UPD) / IP or Transmission Control Protocol (TCP) / IP (landline or wireless) connection to the final destination indicated by the SOAPAction header provided as part of the SIP payload becomes. It can of course intervening nodes (in 2 (a) not illustrated), e.g. B. SIP proxies. The ultimate destination (receiving node 110 ) contains a SIP user agent server (UAS) 206 as well as a SOAP end PLC 208 capable of parsing and sending the SOAP message to the corresponding web service indicated in the SOAPAction header maintained as the SIP payload, for example to one of the web services 210 or 212 , via a service-specific API. The SOAPAction header is handled by the SIP UAS 206 Processes to determine if the SOAP envelope payload is becoming the SOAP parser / dispatcher 208 should be forwarded. Note in this regard that the ultimate recipient of the SIP message may or may not be the same as the ultimate recipient of the SOAP envelope it carries. For example, in the above-described case where Alice calls a charity telephone TV show, the routing of the SOAP envelope to the charity pay service charging her with a donation may be performed by a SIP proxy node located between the Alice and the application server associated with handling the call at the TV show host. Thus, in this latter case, when the intervening SIP proxy node receives the SIP / SOAP message, its analysis of the SOAPAction header will inform it that the SOAP envelope should be processed locally and its parser / dispatcher 208 extracts the SOAP envelope and directs it to a web service 210 . 212 Next, who handles payments. Then the SIP message is forwarded to its final destination, e.g. B. a VoIP application server (in 1 (a) Not shown).

The UAS 206 For example, it may be preconfigured to provide a list of currently used web services 210 . 212 within the receiving node 210 to support the processing of the SOAPAction header. Typically, the response to the SOAP message is then provided in the payload of a SIP 200 OK message, as in 1 (b) shown from the SIP UAS 230 is sent back to the client.

One of the web services 210 and 212 For example, provisioned web service may be defined as a software system designed to support interoperable machine-to-machine interactions over a network. In some implementations, Web services may be provided as Web APIs that are accessible over a network (such as the Internet) and that are executed on a remote system hosting the requested services. However, in terms of the above 1 (a) and 1 (b) Illustrated exemplary embodiments illustrate the web services 210 and 212 Part of a receiving node containing the SOAP parser / dispatcher 208 and the SIP UAS 206 contains. Similar are elements 200 . 202 and 204 Part of an originating node associated with the transmitted SOAP / SIP message. Thus, assuming a fit in the processing of the SOAPAction header from the SIP UAS 230 is found, a corresponding one of the web services 210 . 212 the requested service via the SOAP envelope to the receiving node 110 provide. It will also be recognized that a given receiving node 110 may have more or less integrated than two web services.

Of the SOAPAction header that contains the interface and procedure indications Provides and the SOAP envelope, by itself within a SIP message, as illustrated above, or with other content to be provided. For example, using "Multipurpose Internet Mail Extensions (MIME) Multipart a SIP message a session description protocol (SDP) or other content as a payload in addition to the embedded one Contain SOAP information. An example of this type of multipart SIP message according to an exemplary embodiment is provided below.

In this You can see that the content type headers defined in MIME multipart provide a structure by which a SIP message carries payloads in addition to the SOAPAction header, and optional SOAP Envelope Body according to these exemplary embodiments.

Based on the above description, it will be appreciated that various methods, e.g. For communication, by these exemplary embodiments. Such a method is in the flow chart of 2 illustrated. This is in step 300 a SIP message containing a SOAP order hit and includes a SOAP action header. The SIP message is in step 302 receive and the SOAPAction header will step in 303 evaluated to determine if the SOAP envelope is for that particular receiving node. If so, the SIP / SOAP message is parsed to remove the SOAP envelope from the SIP message (step 304 ). The SOAP envelope can then be in step 306 be forwarded to a corresponding web service. Then, the service indicated by the SOAP envelope and SOAPAction header may be used in step 308 a receiver of the SIP message. Of course, because of the basic nature of these exemplary embodiments, that disclosed in U.S. Pat 2 illustrated exemplary methods are further generalized, such as in 3 illustrated. In it are in step 400 a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header that identify a service sent, ie, a Session Initiation Protocol (SIP) transport binding for SOAP messages.

It Thus, it can be seen that by combining Web services (SOAP, WSDL and UDDI) and SIP these exemplary embodiments For example, allow an application developer to access to have access to a wide range of internet services during can be woven into the session setup phase of SIP. Furthermore, a SIP service composition can be the marketing time for new innovative end-user services as well as opening of inter-business interactions over SIP Providing a device for real-time composition shorten services. Some examples of applications These techniques have been provided above. Many are here others contemplated. For example, consider in context integrating presence notification and multimedia session setup the following. If Alice calls Bob, dial She also made that her presence for all of her Observer set to "Busy" should be. While the session is being set up, notified the application server in Alice's home domain the presence agent about having their activity status Busy is, d. H. by means of a SOAP action header and / or others SOAP data items that come with the SIP session setup message have been routed to the application server. Then all observers see on Alice's attendance list now Alice's presence status change for the duration of the call.

The previously described and other example systems and methods for communication can be through one or more processors be implemented, execute the statement sequences, which are contained in a storage device. Such instructions can be from other computer-readable media, such as secondary Data storage device (s), read into the storage device become. The execution of statement sequences that are specified in the Storage device included cause the processor, for example as described above, to send SIP / SOAP messages or receive. In alternative embodiments a hard-wired circuit instead of or in combination with software statements used to exemplify this Implementing embodiments.

It will further be appreciated that such embodiments may take various physical forms and may be used, for example, in various consumer electronics articles including, but not limited to, smart phones, personal digital assistants (PDAs), laptop computers, and the like. Generally speaking, a communication device that transmits or receives the above-described SIP / SOAP messages may include the elements of in 4 illustrated generic communication device included. This can be a communication device 500 a processor 502 (or more processor cores), memory 504 , optionally one or more secondary storage devices 506 , an operating system 508 that on the processor 502 runs and the store 504 used as well as one or more corresponding application (s) 510 contain. An interface unit 512 may be provided to facilitate communications between the device 500 and the remainder of a network or other peer-to-peer devices, or may be in the processor 502 be integrated. A radio transceiver (not shown) could be part of the interface unit 512 be included if the device 500 communicates via an air interface.

The described above exemplary embodiments Illustrative in all respects and not restrictive for be the present invention. Thus, the present invention to many variations in the detailed implementation in the Layer derived from the description contained herein by those skilled in the art can be. All such variations and modifications be considered within the scope and spirit of the present Invention as defined in the following claims considered. No element, operation or statement in the description used in the present application should be considered critical or essential to the invention, when not explicitly described as such. Also, as used herein, the item "one" means the inclusion one or more objects.

SUMMARY

A real-time service composition is provided by a Session Initiation Protocol (SIP) transport binding for single object access protocol (SOAP) messages. A SOAPAction header and a SOAP envelope may be included in a SIP message to identify a requested service. The SIP message recipient ( 110 ) can parse the SOAP envelope and send it to a corresponding web service ( 210 . 212 ) hand off.

QUOTES INCLUDE IN THE DESCRIPTION

This list The documents listed by the applicant have been automated generated and is solely for better information recorded by the reader. The list is not part of the German Patent or utility model application. The DPMA takes over no liability for any errors or omissions.

Cited non-patent literature

• - Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language, W3C Working Draft 3, August 2004 [0003]
• - http://www.w3.org/TR/2004/WD-wsdl20-20040803/ [0003]
• - SOAP Version 1.2 Part 0: Primer (Second Edition), W3C Recommendation 27 April 2007 [0003]
• - http://www.w3.org/TR/soap12-part()/ [0003]
• - UDDI Version 3.0.2 UDDI Spec Technical Committee Draft, dated 20441019 [0003]
• - http://uddi.org/pubs/uddi_v3.htm [0003]
• Session Initiation Protocol, RFC 3261, author Rosenberg et al., IETF 2002 [0018]
• - http://tools.ietf.org/html/rfc3261 [0018]
• - URN Syntax, RFC 2141, R. Moats, IETF 1997 [0023]

Claims (36)

A method, comprising: transmitting ( 300 ), from an output node ( 100 ), a Session Initiation Protocol (SIP) message including a simple Object Access Protocol (SOAP) envelope and a SOAP action header; Receive ( 302 ), at a receiving node ( 110 ), the SIP message; Determine ( 303 ), whether the SOAP envelope is destined for the receiving node; if yes, parsing ( 304 ), at the receiving node ( 110 ), the SOAP envelope from the SIP message; Send ( 306 ) of the SOAP envelope to a corresponding web service ( 210 . 212 ) within the receiving node; and deploy ( 308 ), at the receiving node ( 110 ), a service indicated by the SOAP action header and SOAP envelope. The method of claim 1, wherein the SOAP action header a Web Services Description Language (WSDL) interface and a includes associated with the service method. The method of claim 2, wherein the WDSL interface locating a place of service and the procedure a kind of Service identified. The method of claim 1, wherein the SIP message is a SIP INVITE message. The method of claim 1, wherein the SIP message is a non-session SIP message. The method of claim 5, wherein the SIP message OPTIONS or MESSAGE is. The method of claim 1, wherein the SIP message also contains a session description protocol (SDP). The method of claim 7, wherein the SIP message constructed using MIME Multi-Part. A method, comprising: sending ( 400 ) a session initiation protocol (SIP) message of a single object access protocol (SOAP) envelope and a SOAP action header that specify a service. The method of claim 9, wherein the SOAP action header contains a web service description language (WSDL) interface, which identifies a place of service, and a procedure that a type of service identified. The method of claim 9, wherein the SIP message a SIP INVITE is. The method of claim 9, wherein the SIP message is a non-session SIP message. The method of claim 12, wherein the SIP message OPTIONS or MESSAGE is. The method of claim 9, wherein the SIP message also contains a session description protocol (SDP). The method of claim 14, wherein the SIP message constructed using MIME Multi-Part. A computer-readable medium containing instructions that perform when executed on a processor: receiving ( 302 ) a Session Initiation Protocol (SIP) message including a Simple Object Access Protocol (SOAP) envelope and a SOAP action header; Parsing ( 304 ) the SOAP envelope from the SIP message; Send ( 306 ) the SOAP envelope to a corresponding web service; and deploy ( 308 ) of a service indicated by the SOAP action header and SOAP envelope. The computer-readable medium of claim 16, wherein the SOAP action header is a Web Services Description Language (WSDL) interface and a method associated with the service. The computer-readable medium of claim 17, wherein the WDSL interface locates a place of service and that Procedure identifies a type of service. The computer-readable medium of claim 16, wherein the SIP message is a SIP INVITE message. The computer-readable medium of claim 16, wherein the SIP message is a non-session-related SIP message. The computer-readable medium of claim 19, wherein the SIP message is OPTIONS or MESSAGE. The computer-readable medium of claim 16, wherein the SIP message also has a session description protocol (SDP) contains. The computer-readable medium of claim 22, wherein constructed the SIP message using MIME Multi-Part is. A computer-readable medium containing instructions that perform when executed on a processor: sending ( 400 ) a Session Initiation Protocol (SIP) message containing a Simple Object Access Protocol (SOAP) envelope and a SOAP action header. A communication device, comprising: a processor ( 502 ) acting as a Session Initiation Protocol (SIP) User Agent Server ( 206 ) receiving a SIP message containing a Simple Object Access Protocol (SOAP) envelope and a SOAP action header; and a SOAP parser / dispatcher ( 208 ) to parse the SOAP envelope from the SIP message and send the SOAP envelope to the appropriate web service ( 210 . 212 ). A communication device according to claim 25, wherein the SOAP action header is a Web Services Description Language (WSDL) interface and a method associated with the service. A communication device according to claim 26, wherein the WDSL interface locates a place of service and that Procedure identifies a type of service. A communication device according to claim 25, wherein the SIP message is a SIP INVITE message. A communication device according to claim 25, wherein the SIP message is a non-session-related SIP message. A communication device according to claim 29, wherein the SIP message is OPTIONS or MESSAGE. A communication device according to claim 25, wherein the SIP message also has a session description protocol (SDP) contains. A communication device according to claim 31, wherein constructed the SIP message using MIME Multi-Part is. A communication device according to claim 25, further full: a plurality of web service entities, which include the corresponding web service; and a corresponding Application Programming Interface (API) between each of the plurality Web service entities and the SOAP parser / dispatcher. The communication device of claim 33, further comprising: a storage device for storing a list of web services provided by the communication device be supported; wherein the processor evaluates the SOAP action header to determine if a web service specified thereby corresponds to one of the plurality of web services. The method of claim 1, further comprising Step: Evaluate the SOAP action header to determine whether a corresponding web service is available at the receiving node is. The computer-readable medium of claim 16, further full: Evaluate the SOAP action header to determine whether a corresponding web service is available.