API Request Verification Platform for Security and Resource Conservation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current techniques fail to inspect API requests before they reach a service, leading to invalid requests being processed, which exposes services and data to security threats and wastes computing resources.

Innovation Solution

A verification platform inspects API requests before processing, authenticating users and determining permission to perform requested actions, discarding unauthorized or improperly formed requests to prevent them from reaching the service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the service processes all incoming API requests without inspection, then the service maintains simplicity and fast response, but security is compromised and computing resources are wasted on invalid requests

Engineering Contradiction:
Improveservice securityVSAvoidrequest processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The verification platform performs authentication and permission verification actions before the service processes the request. This preliminary inspection validates the request contents, checks user permissions, and determines whether the request should be forwarded to the service, thereby preventing security issues and resource waste while maintaining service simplicity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A verification platform is introduced as an intermediary component between the client application and the service. This intermediary intercepts API requests, performs verification operations, and selectively forwards valid requests to the service, resolving the contradiction by adding verification functionality without complicating the core service logic

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the service processes all incoming requests including invalid ones, then ease of operation is maintained, but computing resources are wasted

Engineering Contradiction:
Improvecomputing resource efficiencyVSAvoidrequest processing simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system performs preliminary verification of request validity, authentication, and permission checks before the service executes the request. This early validation filters out invalid requests that would waste computing resources, while the service itself remains simple and focused on processing only verified requests

Inventive Principle:
Principle #10Preliminary action

3Reliability

If no request inspection is performed, then the system responds quickly to all requests, but unauthorized actions may be executed

Engineering Contradiction:
Improveauthorization securityVSAvoidrequest processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Authentication and permission verification are performed as preliminary actions before request execution. The verification platform checks user credentials and determines whether the user has permission to perform the requested action before forwarding the request to the service, preventing unauthorized actions while minimizing time loss through efficient pre-validation

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11381568B2Systems and methods for inspection of the contents of an application programing interface request
Publication Date: 2022.07.05 VERIZON PATENT & LICENSING INC
  • US11381568B2 patent drawing
  • US11381568B2 patent drawing
  • US11381568B2 patent drawing

AI summary

A device may receive, from a user equipment (UE), authentication data that includes user information associated with a user of the UE. The device may determine whether the user is authorized to make requests to a service. The device may grant access to the user to make requests to the service. The device may receive, from the UE, a request that is intended for the service. The request may relate to an action that is to be performed by the service. The device may determine whether the user has permission to request the action. The device may provide the request to the service. The device may receive, from the service, a response to the request. The device may provide, to the UE, the response.