Converged call flow and web service application integration using a processing engine

US9229726B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9229726-B2
Application numberUS-55330806-A
CountryUS
Kind codeB2
Filing dateOct 26, 2006
Priority dateOct 26, 2006
Publication dateJan 5, 2016
Grant dateJan 5, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Given a SIP call flow definition and WSDL extended with SIP/call flow interactions, a converged application integration (CAI) engine provides service-oriented application practitioners with an ability to reuse existing Web services integration techniques in a new converged application integration green space. The converged application integration engine “wraps” a pre-existing converged Web service/SIP or a SIP-only application, listens to application-specific signaling, and based on a supplied WSDL with SIP/call flow extensions, makes and accepts interaction requests using Web services. Given a SIP call flow definition, a WSDL extended with SIP/call flow interactions, and the converged application integration engine, a converged application execution (CAE) engine that greatly eases developing new converged applications. At runtime, the CAE engine “stitches” the signaling onto the decomposed servlet model by following the WSDL extended with SIP/call flow interactions. At appropriate binding points, the CAE engine invokes the listener callback interfaces.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for providing converged application integration, the method comprising: receiving a converged application in a converged application integration engine, wherein the converged application defines a plurality of Web services components, a plurality of call flow segments, each of the plurality of call flow segments having a series of message steps, and at least one binding between a given Web services component within the plurality of Web services components and a given call flow segment within the plurality of call flow segments, wherein the binding is associated with an interaction and has a binding interaction type; determining, by the converged application integration engine, whether the interaction is invoked by the given Web services component or the given call flow segment; responsive to invocation of the interaction, performing an interaction operation based on the binding interaction type; consuming, by the converged application integration engine, a Web services description language document with call flow extensions to form the converged application, wherein the Web services description language document describes a pre-existing application; and generating, by the converged application integration engine, one or more Web service implementations and one or more session initiation protocol servlets for the converged application. 2. The method of claim 1 , wherein determining whether the interaction is invoked comprises: listening, by the converged application integration engine, to signaling sent between the converged application and its clients. 3. The method of claim 2 , wherein the signaling comprises session initiation protocol signaling from a session initiation protocol platform. 4. The method of claim 2 , wherein the signaling comprises Web services invocations from a service oriented application integration platform. 5. The method of claim 1 , further comprising: storing, by the converged application integration engine, state information for the converged application. 6. The method of claim 5 , further comprising: responsive to the given call flow segment reaching a predetermined binding point, making a Web service invocation with state information corresponding to the predetermined binding point. 7. The method of claim 6 , wherein the state information is a simple object access protocol attachment. 8. The method of claim 6 , wherein the state information comprises changes in operation parameters or changes in execution history since a last time an interaction of the same type occurred. 9. A computer program product comprising a computer storage medium having a computer readable program stored thereon, wherein the computer readable program, when executed on a computing device, causes the computing device to: receive a converged application in a converged application integration engine, wherein the converged application defines a plurality of Web services components a plurality of call flow segments, each of the plurality of call flow segments having a series of message steps, and at least one binding between a given Web services component and a given call flow segment within the plurality of Web services components and a given call flow segment within the plurality of call flow segments, wherein the binding is associated with an interaction and has a binding interaction type; determine, by the converged application integration engine, whether the interaction is invoked by the given Web services component or the given call flow segment; responsive to invocation of the interaction, perform an interaction operation based on the binding interaction type; consume, by the converged application integration engine, a Web services description language document with call flow extensions to form the converged application, wherein the Web services description language document describes a pre-existing application; and generate, by the converged application integration engine, one or more Web service implementations and one or more session initiation protocol servlets for the converged application. 10. The computer program product of claim 9 , wherein determining whether the interaction is invoked comprises: listening, by the converged application integration engine, to signaling sent between the converged application and its clients. 11. The computer program product of claim 10 , wherein the signaling comprises session initiation protocol signaling from a session initiation protocol platform. 12. The computer program product of claim 10 , wherein the signaling comprises Web services invocations from a service oriented application integration platform. 13. The computer program product of claim 9 , wherein the computer readable program, when executed on a computing device, further causes the computing device to: store, by the converged application integration engine, state information for the converged application. 14. The computer program product of claim 13 , wherein the computer readable program, when executed on a computing device, further causes the computing device to: responsive to the given call flow segment reaching a predetermined binding point, make a Web service invocation with state information corresponding to the predetermined binding point. 15. The computer program product of claim 14 , wherein the state information is a simple object access protocol attachment. 16. A data processing system for providing converged application integration, the data processing system comprising: a processor, and a memory coupled to the processor, wherein the memory contains instructions which, when executed by the processor, cause the processor to: receive a converged application in a converged application integration engine, wherein the converged application defines a plurality of Web services components, a plurality of call flow segments, each of the call flow segments having a series of message steps, and at least one binding between a given Web services component and a given call flow segment within the plurality of Web services components and a given call flow segment within the plurality of call flow segments, wherein the binding is associated with an interaction and has a binding interaction type; determine, by the converged application integration engine, whether the interaction is invoked by the given Web services component or the given call flow segment; responsive to invocation of the interaction, perform an interaction operation based on the binding interaction type; consume, by the converged application integration engine, a Web services description language document with call flow extensions to form the converged application, wherein the Web services description language document describes a pre-existing application; and generate, by the converted application integration engine, one or more Web service implementations and one or more session initiation protocol servlets for the converted application.

Assignees

Inventors

Classifications

  • G06F9/44Primary

    Arrangements for executing specific programs · CPC title

  • H04L67/02Primary

    based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

  • Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9229726B2 cover?
Given a SIP call flow definition and WSDL extended with SIP/call flow interactions, a converged application integration (CAI) engine provides service-oriented application practitioners with an ability to reuse existing Web services integration techniques in a new converged application integration green space. The converged application integration engine “wraps” a pre-existing converged Web serv…
Who is the assignee on this patent?
Gilfix Michael A, Ulerich Rhys D, IBM
What technology area does this patent fall under?
Primary CPC classification G06F9/44. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jan 05 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).