Gateway Policy Enforcement via Pre-annotated Route Binding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As the number of policies enforced by a services gateway increases, the response time to client requests also increases, leading to potential delays and negatively impacting user experience, especially when handling a large number of services and requests.

Innovation Solution

The method involves receiving configuration data from a services registry, annotating policies with flags, and binding routes to annotated policies, allowing only the necessary policies to be executed for each request, thereby maintaining constant response times as the number of services and policies grows.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the services gateway enforces more policies based on services registry data, then the policy enforcement capability and security coverage are improved, but the response time increases and system performance deteriorates

Engineering Contradiction:
Improvepolicy enforcement capabilityVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-annotating policies with flags and pre-binding routes to policies before runtime request processing. Configuration data including policy annotations and route bindings are prepared in advance and stored in the services registry, so that during request processing, the gateway can directly use pre-established bindings without performing complex lookups or decision logic at runtime, thus reducing response time while maintaining comprehensive policy enforcement

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the policy enforcement process by separating policy configuration data (annotations and bindings) from the request processing flow. Configuration data is extracted and stored independently in the services registry, allowing the gateway to enforce policies through simple route matching rather than evaluating all policies against all requests, thereby improving response time while maintaining security coverage

Inventive Principle:
Principle #1Segmentation

2Reliability

If the services gateway performs lookup of services registry data for each request, then accurate policy enforcement is achieved, but the processing speed decreases as the number of policies increases

Engineering Contradiction:
Improvepolicy accuracyVSAvoidrequest processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-computing and storing route-to-policy bindings in the services registry before runtime. Instead of performing lookups during each request, the gateway uses pre-established bindings that directly map routes to their associated policies, ensuring accurate policy enforcement while dramatically improving request processing speed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy of the essential policy enforcement data (route bindings and annotations) and stores it in the services registry. This copy contains only the necessary information for rapid route matching and policy identification, allowing the gateway to enforce policies accurately without accessing the full services registry during request processing, thus improving processing speed while maintaining policy accuracy

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10187473B2Gateway policy enforcement and service metadata binding
Publication Date: 2019.01.22 INTUIT INC
  • US10187473B2 patent drawing
  • US10187473B2 patent drawing
  • US10187473B2 patent drawing

AI summary

The invention relates to a method for gateway policy enforcement. The method includes receiving configuration data from a services registry. Also, the method includes annotating, based on the configuration data, a plurality of policies with flags. In addition, the method includes binding, using the annotations of the policies, a route to at least one of the annotated policies.