Service Provisioning Platform with Generic Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service provisioning architectures lack support for the reuse of existing information, leading to delayed service provisioning and require significant updates when introducing new service enablers, as they rely on concrete data models and abstract XML-based interfaces, necessitating changes to client systems.
Innovation Solution
A service provisioning platform with a single generic, concrete, and stable interface that uses service-specific activation processes, allowing for simultaneous collection and activation of multiple services, and includes a service activator, service processing systems, and adapters to manage service orders and specifications, eliminating the need for external client changes when new services are introduced.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a current service provisioning architecture with concrete data models for each service enabler is used, then service provisioning can be performed, but the architecture does not support reuse of existing information and requires significant updates when introducing new service enablers
Solution Approach 1:
The patent applies universality by creating a single generic concrete interface that can handle multiple service enablers without requiring separate data models for each. The service activator uses a unified interface definition that works across different service types, eliminating the need to create and maintain separate concrete data models for each service enabler. This allows the system to adapt to new service enablers without modifying the core interface structure.
Solution Approach 2:
The patent introduces an intermediary layer (the service activator with its generic interface) between the service ordering system and the various service enablers. This intermediary handles the conversion and adaptation to different service-specific requirements, shielding external clients from the complexity of individual service enabler data models while enabling support for multiple service types through a single stable interface.
2Stability of the object's composition
If abstract XML-based provisioning interfaces are used, then a stable interface can be maintained, but external client systems must be changed to handle new schemas
Solution Approach 1:
The patent creates a concrete copy or instantiation of the abstract XML interface. Instead of directly using abstract XML schemas that require client changes, the system generates concrete interface definitions from templates or metadata, allowing the interface structure to remain stable while adapting to new service schemas through configuration rather than code changes in external clients.
Solution Approach 2:
The patent introduces dynamics by making the interface behavior adaptable through service-specific configurations and service activator logic. While the interface structure remains stable, the system dynamically adjusts how it processes different service types based on service metadata and activation parameters, allowing new schemas to be handled without changing the external client interface definition.
3Reliability
If information collection is performed before provisioning starts, then all required information is available, but service provisioning is greatly delayed
Solution Approach 1:
The patent applies preliminary action by pre-defining interface structures, data models, and processing logic in advance. Service activators are pre-configured with templates and metadata that describe required information, allowing the system to immediately process service orders without requiring ad-hoc information collection. The preliminary setup enables rapid provisioning while ensuring all necessary information is captured through standardized interfaces.
Solution Approach 2:
The patent implements feedback mechanisms where the service activator monitors information availability and provisioning progress in real-time. Based on feedback about what information is already available versus what is still needed, the system can proceed with provisioning using existing information while simultaneously collecting additional required data, rather than waiting for complete information collection before starting provisioning.
Data Source
AI summary
A system for provisioning services may include a device that may receive a service order that identifies a service to be provisioned. The device may obtain, using the service order, a specification for the service. The device may further identify, based on the specification, a service processing system to invoke for provisioning the service, and invoke the service processing system by sending the service order and the specification to the identified service processing system.