Service Peering Aggregation Server for Loose Coupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service integration methods in Next Generation Networks require extensive point-to-point software integration, leading to tightly coupled systems that are inflexible and difficult to change, limiting the number of services that can be bundled and increasing deployment risks and costs.
Innovation Solution
The Service Peering Aggregation Server (SPAS) integrates service applications by using autonomous service agents that coordinate through service-specific data rather than service logic, allowing for loose coupling and flexible bundling of services across multiple providers without modifying existing applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If point-to-point software integration is used to bundle services, then services can be integrated and bundled, but the systems become tightly coupled and inflexible
Solution Approach 1:
The patent introduces an intermediary integration layer (service bus, adapter patterns) that mediates between heterogeneous service applications and the bundling logic. This intermediary absorbs the integration complexity, allowing services to be bundled without direct point-to-point connections, thereby reducing tight coupling while maintaining adaptability.
Solution Approach 2:
The patent segments the integration architecture into independent components: service adapters, integration bus, bundling engine, and service applications. Each component has a specific responsibility, allowing services to be integrated and bundled independently without affecting the entire system, thus reducing complexity while enabling versatile service bundling.
2Adaptability or versatility
If extensive point-to-point integration is performed to bundle multiple services, then more services can be bundled, but the deployment risks and costs increase
Solution Approach 1:
The integration layer acts as a buffer that isolates service deployment from the bundling logic. When services are deployed or updated, changes are contained within the service boundary and communicated through standardized interfaces, preventing cascading failures and reducing deployment risks while enabling more services to be bundled.
Solution Approach 2:
The patent implements universal integration patterns and standardized interfaces that can accommodate multiple different service applications through a common bundling framework. This universality allows diverse services to be bundled without custom point-to-point integration for each combination, thereby increasing the number of bundlable services while reducing deployment complexity and risk.
3Ease of operation
If services are tightly coupled through customization for each interconnection, then integration can be achieved, but the systems become difficult to change
Solution Approach 1:
The intermediary integration layer provides a standardized interface between services and the bundling logic. Services can be integrated through configuration rather than customization, and changes to one service do not require modifications to other services or the bundling logic, thereby maintaining ease of operation while improving system flexibility.
Solution Approach 2:
The patent implements dynamic service binding and configuration capabilities that allow service integrations to be changed, added, or removed without reconfiguring the entire system. The integration framework dynamically adapts to service changes, making the system flexible while maintaining ease of service integration through standardized processes.
4Ease of operation
If the central control logic of each service application is customized for each interconnection, then integration can be achieved, but the nature of integration is constrained to the workflow engine
Solution Approach 1:
The patent extracts the integration logic from the service applications' central control logic and places it in a separate integration layer. This extraction removes constraints imposed by workflow engines and allows integration to be implemented through independent adaptation patterns, thereby maintaining ease of service coordination while reducing integration complexity constraints.
Solution Approach 2:
The intermediary integration layer handles service coordination and data transformation without requiring modifications to service applications' central control logic. This mediator approach enables flexible integration patterns beyond workflow engine constraints while maintaining ease of operation through centralized integration management.
Data Source
AI summary
Service applications at one or more service providers are bundled through a server thereby creating new services. The server comprises service agents, each of which corresponds to one or more service applications and proxies for its application(s) to perform service bundling. When a subscriber interacts with a service application and affects service specific data, the application sends this data along with the subscriber's intent with respect to this data to the server. The server next identifies a primary service agent, which is the agent proxying for the application. This agent determines a peer group of service agents, wherein each peer agent corresponds to a service application that together define a bundled service. The principal and peer agents subsequently negotiate/coordinate with respect to the service data. As a result, the agents may communicate with their respective service applications to determine a subscriber's current service data configurations and/or to update these configurations.