NaaS API Control for On-Demand Bandwidth and Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network-as-a-service (NaaS) systems lack the ability to provide quality on demand (QoD) metrics, such as improved bandwidth and latency, to developers and users, limiting the development of applications like gaming and augmented/virtual reality.
Innovation Solution
Implementing an application programming interface (API) that allows developers to request and receive QoD metrics, processing these requests to determine network support, and transmitting responsive payloads to user devices, enabling QoD sessions based on session identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If NaaS systems provide basic network access, then network accessibility is improved, but quality of service control capability deteriorates
Solution Approach 1:
An API module is introduced as an intermediary component between user devices and the network core. This module receives QoD metric requests from user devices, processes them against network capabilities, and returns appropriate responses. The API module enables quality of service control without requiring direct modification of core network functions, thus maintaining network accessibility while adding quality control capability.
Solution Approach 2:
The system enables dynamic adjustment of network parameters such as bandwidth and latency based on requested QoD metrics. By changing these parameters on demand rather than providing fixed network conditions, the system achieves both accessibility and adaptability - users can access the network with basic parameters while also obtaining enhanced quality control when needed.
2Ease of manufacture
If developers access network functions through basic APIs, then ease of development is improved, but quality on demand control deteriorates
Solution Approach 1:
The API module is designed to handle multiple types of requests - both basic network access and quality of demand metrics through a unified interface. This multi-functional design allows developers to access network functions easily while also enabling quality control capabilities, eliminating the need for separate development paths for different service types.
Solution Approach 2:
The API implements a request-response feedback mechanism where user devices send QoD metric requests and receive processed responses from the API module. This feedback loop enables reliable quality on demand control by confirming that requested metrics are supported and providing appropriate responses, while maintaining simple developer interaction through standard API protocols.
3Adaptability or versatility
If the network supports multiple QoD metrics, then service versatility is improved, but network complexity increases
Solution Approach 1:
The network complexity is segmented and isolated within the API module, which handles all QoD metric processing independently from the core network functions. This segmentation allows the network to support multiple QoD metrics and service types without increasing overall network complexity, as the complexity is contained within the modular API layer that can be independently managed and scaled.
Data Source
AI summary
Methods and systems for providing mobile broadband services to high speed rail are provided. The method begins with receiving, at an application programming interface (API) module on the network, a request from a user device. The request comprises a request payload that comprises a quality on demand (QoD) metric to be used in the NaaS operations. The QoD metric may be selected to provide for a desired level or service or operating quality that a developer wishes to provide. The request payload is then processed at the API module, wherein the processing determines if the network supports the QoD metric being requested. After processing, a response is transmitted from the API module to the user device, wherein the response comprises a response payload responsive to the QoD metric in the request payload.