Dynamic API Messaging for Granular Resource Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing APIs lack an efficient mechanism for dynamic messaging that allows multiple applications to access and retrieve resources from various granular APIs without requiring implementation of underlying mechanisms, leading to complexity and inefficiency in resource retrieval.

Innovation Solution

A dynamic messaging system comprising a central dynamic API that maps data identifiers to granular APIs, receives messages with data identifiers, retrieves resources using the appropriate APIs, and provides the resources to clients, while managing dependencies and authorization, enabling efficient and flexible resource access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple applications directly access granular APIs to retrieve resources, then resource access flexibility is improved, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improveresource access flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a message broker as an intermediary component between applications and granular APIs. The message broker receives messages from applications, routes them to appropriate granular APIs, and returns responses. This mediator pattern allows applications to access multiple granular APIs without directly implementing the complexity of each API, thus maintaining flexibility while reducing system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the API access architecture into distinct layers: applications, message broker, and granular APIs. Each component has a specific responsibility, allowing independent development and maintenance. This segmentation enables applications to interact with a simple message interface while the complex granular APIs remain isolated, resolving the contradiction between flexibility and complexity.

Inventive Principle:
Principle #1Segmentation

2Reliability

If applications implement underlying code independently for each granular API, then resource access control is improved, but development time and effort increase

Engineering Contradiction:
Improveresource access controlVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The message broker implements self-service by automatically managing message routing, authentication, and resource access control. Instead of requiring applications to implement complex access control logic for each granular API, the message broker handles these tasks autonomously based on configured rules and credentials, significantly reducing development time while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The message broker provides universal access control functionality that serves all granular APIs through a single interface. It implements authentication, authorization, and message routing mechanisms that work across multiple APIs, eliminating the need for applications to implement separate access control for each API and reducing overall development effort.

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

3Productivity

If a centralized API gateway is used to manage multiple granular APIs, then resource retrieval efficiency is improved, but message routing complexity increases

Engineering Contradiction:
Improveresource retrieval efficiencyVSAvoidmessage routing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The message broker implements dynamic message routing based on message content, destination identifiers, and current system state. Rather than using static routing tables, the system dynamically determines the appropriate granular API for each message, optimizing resource retrieval efficiency while managing routing complexity through adaptive algorithms and configuration.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10733033B2Dynamic messaging for an application programming interface
Publication Date: 2020.08.04 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10733033B2 patent drawing
  • US10733033B2 patent drawing
  • US10733033B2 patent drawing

AI summary

Examples disclosed herein comprise dynamic message instructions to map each of a plurality of data identifiers to at least one granular application programming interface (API), receive a message comprising at least one of the plurality of data identifiers from a client, retrieve, via the at least one granular API for the at least one of the plurality of data identifiers, a data resource, and provide the retrieved data resources to the client.