Oauth API Interface Generation and Binding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for using Oauth APIs are inefficient and complex, requiring developers to write code and tightly couple authorization logic, making it difficult to integrate and manage Oauth API access effectively.

Innovation Solution

A method and system that abstract Oauth authentication logic to generate universal authentication interfaces, allowing developers to register Oauth APIs and automatically generate executable interfaces, which are then injected into an application running engine to simplify the development process and improve efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If developers use Oauth API by writing code and tightly coupling authorization logic, then the Oauth API can be integrated into applications, but the development process becomes complicated and inefficient

Engineering Contradiction:
Improveease of integrating Oauth APIVSAvoidcomplexity of development process
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent extracts the Oauth authorization logic from application code and places it in a standalone authorization service. This separation allows developers to use simple interface calls instead of writing complex authorization code, thereby easing integration while reducing development complexity

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an authorization service as an intermediary between applications and Oauth providers. This mediator handles the complex authorization logic internally and provides simplified interfaces to applications, making integration easier without increasing visible complexity for developers

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If developers write code to invoke Oauth API, then the API functionality can be accessed, but the development efficiency decreases

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidtime spent on integration
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-configuring the authorization service with Oauth provider connections and logic. This preparation work is done once, allowing multiple applications to quickly integrate without spending time on repeated configuration, thereby improving productivity and reducing integration time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The authorization service provides universal functionality that can be reused across multiple applications. By creating a multi-functional service that handles various Oauth providers and scenarios, the system improves overall development efficiency while reducing the time each application needs to spend on integration

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

Data Source

PatentEP3301881B1Method, device and system for using and invoking oauth api
Publication Date: 2019.04.10 HUAWEI TECH CO LTD
  • EP3301881B1 patent drawingFigure 1
  • EP3301881B1 patent drawingFigure 2
  • EP3301881B1 patent drawingFigure 3

AI summary

The present invention provides a method, device and system for using and invoking an Oauth API. The method for using an Oauth API includes: receiving registration information for registering an Oauth API; generating an Oauth API invoking associated interface according to the registration information, and binding it with the registered Oauth API, to generate binding information; receiving an increasing Oauth API message and responding, generating a client requesting Oauth API interface, an Oauth API returned information processing interface and a client customer serial number managing interface, which correspond to the registered Oauth API; receiving a publishing application message, responding to the publishing application message, and generating a deployment package which includes the client requesting Oauth API interface, the Oauth API returned information processing interface and the client customer serial number managing interface; sending the binding information and the deployment package to an application running engine, so that the application running engine complete Oauth API scheduling according to the binding information and the deployment package.