SDN API Controller for Automated Service Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunication networks face challenges in automatically determining and implementing application program interfaces (APIs) for providing network services, especially in dynamic environments where frequent changes are required without operator intervention.
Innovation Solution
A Software Defined Network (SDN) architecture that automatically determines and derives APIs for network services by analyzing user requests and matching them with stored API characteristics, enabling the creation of API chains to facilitate service delivery with minimal operator involvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual implementation of APIs for network services is used, then reliability and control are improved, but productivity and speed of service implementation deteriorate
Solution Approach 1:
The system enables self-service through automatic API determination where the network infrastructure autonomously determines, derives, and implements appropriate APIs for network services without requiring manual operator intervention. The API controller automatically analyzes service requirements and selects suitable APIs from available options, allowing the system to serve itself.
Solution Approach 2:
The patent replaces the mechanical manual process of API selection and implementation with an automated computational system. The API controller uses automated analysis and determination algorithms to substitute human operators in the API implementation process, thereby increasing productivity while maintaining reliability through systematic automated control.
2Productivity
If automated API determination is implemented, then productivity and ease of operation are improved, but device complexity increases
Solution Approach 1:
The API controller serves as an intermediary component between the network service requirements and the available APIs. This mediator automatically determines and derives the appropriate APIs by analyzing service characteristics and matching them with suitable API options, thereby managing complexity through a dedicated intermediate layer rather than requiring complex integration throughout the entire system.
Solution Approach 2:
The system segments the API implementation process into distinct functional components: service requirement analysis, API determination, API derivation, and implementation. This segmentation allows each component to be independently managed and optimized, reducing overall system complexity while maintaining high productivity through automated workflows.
3Adaptability or versatility
If frequent changes to network services are made, then adaptability is improved, but stability and reliability deteriorate
Solution Approach 1:
The system embraces dynamics by enabling frequent and flexible changes to network services through automated API determination. The API controller can dynamically adapt to changing service demands by automatically analyzing new requirements and selecting appropriate APIs, allowing the system to be fluid and responsive rather than rigid and static.
Solution Approach 2:
The automated API determination system incorporates feedback mechanisms where the API controller continuously monitors service requirements and implementation status. This feedback loop ensures that changes are systematically managed and validated, maintaining stability through controlled adaptation rather than uncontrolled fluctuation.
Data Source
AI summary
Techniques, described herein, may enable a software defined network (SDN) to determine application program interfaces (APIs) for providing network services. For instance, when a customer submits a request to access media content (e.g., images, music, videos, etc.), the SDN may determine the APIs to enable the network service to be provided to the user with little or no operator involvement. In some implementations, the APIs may be derived by the network dynamically. In some implementations, the APIs may be derived from API records that are stored by the SDN. Additionally, when new APIs are derived for a network service, the APIs may be recorded in case the same request for network services is later received (e.g., from another customer) in which case the record may be promptly used to determine the appropriate APIs for the requested network service.


