RAN OAM Configuration Schema API Retrieval With Request Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies lack a method for an API consumer to retrieve configuration schemas for radio access network (RAN) operation and maintenance (OAM) functions efficiently, leading to potential data validation errors.
Innovation Solution
A method and apparatus for an API producer to receive a HTTP GET configuration schema request from an API consumer, validate it based on resource URI and query criteria, and send a response including the configuration schema if valid, thereby avoiding data validation errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If configuration schema retrieval is implemented without validation, then API consumer can access schema data, but data validation errors occur
Solution Approach 1:
The patent applies preliminary action by validating the request before retrieving the configuration schema. The API producer checks whether the request is valid (e.g., checking for authorized access, proper parameters) before actually retrieving and returning the schema data. This prevents data validation errors while maintaining ease of operation for authorized consumers.
2Reliability
If request validation is performed, then data integrity is ensured, but retrieval process complexity increases
Solution Approach 1:
The validation mechanism is designed to be universal and multi-functional. The same validation logic handles multiple aspects of request verification (authorization, parameter checks, schema format validation) within a single integrated process. This reduces the apparent complexity while ensuring comprehensive data integrity.
3Quantity of substance
If configuration schema is retrieved without query criteria, then all schema data is returned, but data processing efficiency decreases
Solution Approach 1:
The patent implements partial action by allowing the API consumer to specify query criteria (such as filtering by schema type, version, or other attributes) to retrieve only the necessary portion of the configuration schema. This is contrasted with excessive action where all schema data would be returned without filters. The system supports both scenarios but optimizes for efficiency by enabling selective retrieval based on consumer needs.
Data Source
AI summary
Example embodiments of the present disclosure relate to retrieving configuration schemas API's for radio access network (RAN) operation and maintenance (OAM) functions. In particular, a method may be implemented by an API producer and include receiving a configuration schema request originating from an API consumer, the configuration schema request including a resource URI and query criteria, the query criteria including at least one or more of a scope parameter and a filter parameter; determining whether the configuration schema request is valid or not; upon determining that the configuration schema request is valid, obtaining a configuration schema based on the resource URI and the query criteria; and sending a response, wherein the response includes a message based on the determination of whether the configuration schema request is valid or not, wherein the message includes the configuration schema if the configuration schema request was determined as being valid.