API Service Modification Framework for Cloud Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service provisioning systems lack a mechanism for on-demand modifications to existing connectivity and cloud services without requiring a new service order and cost quote.
Innovation Solution
Implementing an API that allows service providers and their partner operators to agree on parameters for service modifications in advance, enabling immediate, on-demand changes to service attributes without the need for new orders or cost quotes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If a new service order and cost quote process is used for service modifications, then service provisioning is formal and controlled, but the process is time-consuming and inefficient for on-demand changes
Solution Approach 1:
The patent applies preliminary action by pre-establishing service level agreements (SLAs) and pricing models before modifications are needed. The system pre-configures allowed modification parameters, cost ranges, and service levels, enabling rapid on-demand changes without requiring new service orders. This resolves the contradiction by allowing fast modifications while maintaining formal control through pre-agreed frameworks.
Solution Approach 2:
The patent implements dynamics by enabling flexible, on-demand service modifications that can be adjusted in real-time based on customer needs. The system allows dynamic changes to service parameters (bandwidth, connectivity levels, cloud resources) without following rigid new-service-order procedures. This resolves the time-loss contradiction by making the service modification process adaptive and responsive rather than static and procedural.
2Productivity
If existing service modification mechanisms are used, then service changes can be implemented, but multiple operators must coordinate through complex ordering processes
Solution Approach 1:
The patent introduces an intermediary system that automates coordination between multiple service operators. This intermediary handles the complexity of cross-operator modifications by managing SLAs, pricing, and provisioning automatically. The system acts as a mediator that translates modification requests into coordinated actions across operators without requiring manual coordination, thus improving productivity while reducing process complexity.
Solution Approach 2:
The patent applies universality by creating a unified service modification framework that works across multiple operators and service types. The same modification mechanism can be applied to connectivity services, cloud services, and multi-operator scenarios. This multi-functional approach improves productivity by eliminating the need for operator-specific modification procedures while reducing coordination complexity through standardization.
3Quantity of substance
If detailed cost quotes are obtained for each service modification, then pricing accuracy is maintained, but the process becomes time-consuming and costly
Solution Approach 1:
The patent applies preliminary action by pre-establishing pricing models and cost frameworks before modifications occur. Instead of obtaining detailed cost quotes for each modification, the system uses pre-agreed pricing structures that automatically apply to allowed changes. This resolves the contradiction by enabling fast modifications while maintaining pricing accuracy through pre-defined cost models rather than ad-hoc quoting.
Solution Approach 2:
The patent implements self-service by enabling the system to automatically determine and apply costs for service modifications without manual quote acquisition. The modification process automatically references pre-established pricing models and applies appropriate costs based on the modification type and service level. This resolves the time-loss contradiction by eliminating the time-consuming manual quoting process while maintaining cost accuracy through automated pricing application.
Data Source
AI summary
A method may include establishing, by a first service provider and via an application programming interface (API), an agreement with a second entity. The agreement may identify services that can be modified without submission of a new order. The method may also include receiving a first message requesting a change associated with a service and determining, by the first service provider, whether the requested change corresponds to a change that is permitted based on the agreement and whether resources are available in the first network to implement the requested change. The method may further include determining whether the requested change is accepted, sending a second message to the second entity that indicates whether the change is accepted and in response to determining that the change is accepted, automatically implementing the change to the service in the first network.