OpenID Account Binding via HiBoard Mediation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional account binding methods for third-party applications with HiBoard require complex development work, high development workload, and high costs, making it difficult for third-party applications to integrate with HiBoard.

Innovation Solution

The HiBoard replaces the third-party application to obtain an OpenID, simplifying the account binding process by eliminating the need for the third-party application to develop a login page and invoke an account management SDK, thereby reducing development workload and costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the third-party application develops a login page and invokes account management SDK to obtain OpenID, then the account binding function is achieved, but the development workload and complexity increase significantly

Engineering Contradiction:

Improveaccount binding functionVSAvoiddevelopment complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The HiBoard application performs self-service by automatically obtaining the OpenID through its own account management SDK without requiring the third-party application to invoke the SDK. The HiBoard app retrieves the OpenID associated with the user account and shares it with the third-party application, eliminating the need for the third-party app to implement complex account binding logic.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The HiBoard application acts as an intermediary between the account management system and the third-party application. Instead of the third-party application directly interacting with the account management SDK, the HiBoard app mediates the process by obtaining the OpenID and providing it to the third-party application, thereby simplifying the integration process.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the third-party application implements the complete account binding procedure, then the binding relationship is established, but the development cost and time increase

Engineering Contradiction:

Improvebinding relationshipVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The HiBoard application performs preliminary actions by pre-obtaining the OpenID through its account management SDK before the third-party application needs it. The OpenID is retrieved in advance and made available to the third-party application, eliminating the need for the third-party app to perform time-consuming SDK invocation and OpenID retrieval operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The HiBoard application serves itself by automatically managing the OpenID retrieval process. The third-party application only needs to request the OpenID from the HiBoard app, which handles the entire account management interaction autonomously, significantly reducing the development time and effort required for account binding.

Inventive Principle:

Principle #25Self-service

3Reliability

If the third-party application integrates account management SDK, then the OpenID can be obtained, but the development workload increases

Engineering Contradiction:

ImproveOpenID acquisitionVSAvoiddevelopment efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The HiBoard application serves as an intermediary that handles the interaction with the account management SDK. The third-party application does not need to integrate or invoke the SDK directly; instead, it requests the OpenID from the HiBoard app, which has already obtained it through its own SDK integration. This mediator approach eliminates the need for the third-party app to perform complex SDK integration work.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The HiBoard application performs self-service by autonomously obtaining and managing the OpenID. The third-party application only needs to make a simple request to the HiBoard app to get the OpenID, without needing to implement any account management functionality itself. This significantly improves development efficiency by reducing the workload to a simple API call.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS12519768B2Account binding method, device, and system

Publication Date: 2026.01.06 HUAWEI TECH CO LTD

AI summary

The technology of this application relates to an account binding method, a device, and a system, and relates to the field of electronic technologies. An electronic device logs in to a user account of a first application. After detecting a first preset operation of a user, the electronic device obtains, by using the first application, an OpenID corresponding to the user account of the first application, where the first preset operation is used to indicate to associate a second application with the first application. The electronic device sends the OpenID of identity information of the second application to a server of the first application, and obtains account binding success information from the server of the first application.