GraphQL API for 6G Service-Based Architecture Data Query

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data query and manipulation services in 5G networks face issues such as over-fetching and under-fetching, where NF service consumers cannot specify exact data needs, leading to performance, efficiency, and security problems, and require multiple requests to fetch all necessary data.

Innovation Solution

Adoption of GraphQL as a query language for the Service-Based Architecture (SBA) API in 6G systems, enabling more efficient data query and manipulation by allowing clients to specify needed data precisely and aggregating multiple requests through a single URI, along with the use of GraphQL API in NFs paired with data repositories, services, or as a unified mediation network function.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If RESTful APIs are used for data query services in 5G networks, then service compatibility is maintained, but data retrieval efficiency deteriorates due to over-fetching and under-fetching problems

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidunnecessary data transfer
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary data fields from the complete data structure by introducing field selection capabilities in GraphQL queries. Clients can specify exactly which fields they need (e.g., user profile fields), preventing over-fetching of unnecessary data while ensuring complete data retrieval when needed, thus improving data retrieval efficiency and reducing energy consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements a unified GraphQL API gateway that handles multiple data retrieval scenarios (over-fetching, under-fetching, partial data needs) through a single interface. This multi-functional approach consolidates various data query patterns into one standardized mechanism, improving overall system efficiency without requiring separate solutions for different data access needs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of time

If multiple separate requests are made to fetch all necessary data, then data completeness is achieved, but request processing time increases

Engineering Contradiction:
Improverequest processing timeVSAvoidnumber of requests
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent merges multiple data retrieval operations into a single GraphQL query by aggregating data from different sources (user profile, authentication state, preferences) through one unified request interface. This consolidation eliminates the need for sequential multiple requests, significantly reducing request processing time while maintaining data completeness through the graph structure that relationships between data fields.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements nested data structures where child fields can be accessed within parent field selections. This allows clients to retrieve hierarchical data (e.g., user profile containing nested authentication and preference fields) in a single request, reducing the number of requests needed while maintaining complete data access through the nested graph structure.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Object-affected harmful factors

If all data is returned in API responses, then data availability is ensured, but security risks increase due to potential privacy violations

Engineering Contradiction:
Improveprivacy violationsVSAvoiddata availability
Core Design Contradiction:
Object-affected harmful factorsVSLoss of information

Solution Approach 1:

The patent extracts only the specific data fields that are both available and authorized for sharing by implementing field-level selection in GraphQL queries. The system can selectively include or exclude sensitive fields (e.g., excluding personal identification data while including public profile information) based on user preferences and security policies, thereby reducing privacy violations while maintaining necessary data availability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different data exposure policies to different fields based on their sensitivity and usage context. Public fields can be freely accessed, while sensitive fields require additional authorization or can be selectively omitted from responses. This localized quality control allows the system to maintain data availability for appropriate fields while preventing privacy violations through field-specific security management.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20240320069A1Graph query language API for data query and manipulation services in sixth generation service-based architectures
Publication Date: 2024.09.26 INTEL CORP
  • US20240320069A1 patent drawing
  • US20240320069A1 patent drawing
  • US20240320069A1 patent drawing

AI summary

This disclosure describes systems, methods, and devices for providing data query and manipulation services. A wireless communications network service-based architecture for providing data query and manipulation services may detect a request from a service consumer, received at a GraphQL interface of a network function, to query or manipulate data; and provide, using the GraphQL interface, a response to the request.