Methods, systems, and software for providing service integration framework

• US 8,135,847 B2
• Filed: 06/13/2011
• Issued: 03/13/2012
• Est. Priority Date: 03/12/2004
• Status: Expired due to Term

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Pujol, Guy, Bauer, Albert, Bass, Rodney, Dashfield, Carl, Gurrala, Shashidhar, Lawal, Gafar, Mazboudi, Wissam D., Nair, Suresh
• Primary Examiner(s): JEAN GILLES, JUDE
• Application Number:
  US13/158,533
• Publication Number:
  US 20110252148A1
• Time in Patent Office: 274 Days
• Field of Search: 709/226, 709/227, 709/229, 709/223, 709/206
• US Class Current: 709/227
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

A preferred embodiment of the subject invention comprises a system for implementing computer network services and applications, comprising a front-end component comprising one or more applications; a back-end component comprising one or more services; and an abstraction layer component operable to communicate with the front-end and back-end components. In another preferred embodiment, the subject invention comprises a system for linking applications and services, comprising: a vendor connectivity component; a business integration component; a security component; a utility component; and a back end connectivity component.

Claims

1. A system for linking applications and services, comprising:

a vendor connectivity component operable to provide service location and activation capabilities using one or more standard interfaces comprising a Universal Discovery Description and Integration interface;

a business integration component operable to provide call context information that indicates at least one from the set comprising;

caller, calling channel, calling program, and calling device;

a security component operable to provide single sign-on to access a plurality of services;

a utility component operable to provide applications access to utility services through a first standardized application program interface (API); and

a back end connectivity component operable to provide applications access to backend data sources through a second standardized API.

2. A system as in claim 1, wherein said vendor connectivity component is operable to standardize exposure of said applications to said services.

3. A system as in claim 1, wherein said vendor connectivity component is operable to provide a consistent abstraction between a user interface and a middle tier.

4. A system as in claim 1, wherein said vendor connectivity component is operable to use standardized headers to provide system management integration between a caller and said applications.

5. A system as in claim 1, wherein said vendor connectivity component is operable to provide automatically generated service entry points.

6. A system as in claim 1, wherein said business integration component is operable to provide identity context information.

7. A system as in claim 1, wherein said business integration component is operable to provide application context information.

8. A system as in claim 1, wherein said security component is operable to provide distributed security.

9. A system as in claim 1, wherein said security component is operable to provide entitlement management.

10. A system as in claim 1, wherein said security component is operable to provide identity management.

11. A system as in claim 1, wherein said utility component is operable to provide centralized end-to-end system management with an ability to correlate information across a plurality of parameters.

12. A system as in claim 1, wherein said utility component is operable to enable auditing at system boundaries to manage service level agreements and method level metering.

13. A system as in claim 1, wherein said back end connectivity component is operable to provide access to back end data sources without changing a back end system.

14. A system as in claim 1, wherein said back end connectivity component is operable to enable de-coupling of said applications from said services.