Service Connectors Mediating Protocol and Policy Differences
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing computing model for application services is limited, making Enterprise Application Integration (EAI) and Business-to-Business (B2B) solutions economically impractical due to the variety of services and individualized nature of EAI and B2B solutions, and the expense of achieving platform interoperability using ad hoc approaches.
Innovation Solution
A services network with a directory that provides access to multiple services and connectors, mediating communication protocol and business policy differences between network endpoints, allowing users to discover and consume services through a loosely coupled, service-oriented architecture using Web Services technologies like SOAP, WSDL, and BPEL, and enabling the creation of custom connectors for specific services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If ad hoc approaches are used to achieve platform interoperability, then service connectivity is enabled, but expense and duplication of effort increase significantly
Solution Approach 1:
The patent implements a universal connector framework that can interface with multiple different service platforms and protocols through a single standardized architecture. The connector uses common data structures (XML, JSON) and communication patterns (REST, SOAP) to enable broad platform interoperability without requiring custom ad hoc solutions for each service, thereby reducing both expense and duplication of effort while maintaining high adaptability
Solution Approach 2:
The patent introduces an integration layer with standardized connectors that act as intermediaries between disparate service platforms. These connectors translate and normalize communications between different protocols and data formats, enabling platform interoperability through a mediating framework rather than direct point-to-point ad hoc connections, thus eliminating redundant integration work and reducing costs
2Adaptability or versatility
If EAI and B2B solutions are customized for each enterprise, then specific business needs are met, but economic practicality deteriorates
Solution Approach 1:
The patent implements dynamic policy mediation capabilities within the connector framework that can adapt to different business requirements through configurable policies rather than custom-coded solutions. The system allows enterprises to define and modify business policies (authentication, authorization, data transformation rules) dynamically without requiring full customization of the integration architecture, thereby maintaining economic practicality while meeting specific business needs
Solution Approach 2:
The patent uses parameter-based configuration to accommodate different business policies across enterprises. Instead of customizing the entire EAI solution for each enterprise, the system allows modification of specific parameters (policy rules, data formats, communication protocols) within a standardized framework, making the solution economically viable while remaining adaptable to diverse business requirements
3Reliability
If a three-tiered architecture is used to manage application services, then service access is controlled, but connector complexity increases
Solution Approach 1:
The patent segments the integration functionality into distinct, modular connector components that operate within the three-tiered architecture. Each connector is a self-contained unit with specific responsibilities (protocol translation, data transformation, policy enforcement), reducing overall system complexity by breaking down the integration layer into manageable, reusable segments rather than a monolithic complex system
Data Source
AI summary
Methods and apparatus for facilitating consumption of services via a services network are described. Access is provided to a services directory which identifies a plurality of services and at least one connector for facilitating consumption of each of the services via the network. Each connector is operable to mediate communication protocol and business policy differences between a first network end point associated with the corresponding service and a second network end point associated with a consumer of the service. For each of selected ones of the connectors, information accessible via the services directory is provided regarding how to use the connector to consume the corresponding service. For each of selected ones of the services, access to a connector design process is provided via the services directory. The connector design process is operable to facilitate creation of a new connector for the corresponding service, and to specify at least one business process for mediating the business policy differences.