SDK Verification via Metadata Registration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software development kits (SDKs) for third-party applications often fail to obtain necessary data for verification, leading to incomplete verification processes and failed calls.

Innovation Solution

A method and device that register required components and metadata into a system, allowing the SDK to transmit responses to target applications, ensuring verification can be performed smoothly by determining and registering the necessary metadata based on identification information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the SDK obtains data relating to the application for verification, then verification can be performed, but the SDK cannot obtain the data in some cases resulting in failed verification

Engineering Contradiction:
Improveverification success rateVSAvoiddata acquisition complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a data acquisition module as an intermediary component that the SDK cannot directly access. This module resides in the same process as the target application and can acquire the required data. The system establishes a communication mechanism where the SDK can request data through this intermediary, resolving the contradiction between needing verification data and the inability of the SDK to directly obtain it.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the verification system into distinct components: the target application, the data acquisition module, and the SDK. By separating the data acquisition function into a dedicated module within the target application's process, the system allows the SDK to perform verification without directly accessing application data, thus maintaining verification reliability while managing complexity through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If the SDK verification process is simplified, then calling becomes easier, but verification may fail due to insufficient data

Engineering Contradiction:
ImproveSDK calling easeVSAvoidverification completeness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements a self-service mechanism where the target application automatically provides the necessary data to the SDK through the data acquisition module. The system includes a metadata registration mechanism that automatically configures the data acquisition capabilities based on the target application's metadata, eliminating the need for manual configuration and maintaining ease of operation while ensuring verification completeness.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by registering metadata and configuring the data acquisition module before the SDK verification process begins. The system pre-establishes the communication channels and data access mechanisms, so when the SDK needs to perform verification, the data acquisition infrastructure is already in place and ready to serve, maintaining both ease of operation and verification reliability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3418885B1Method and device for calling software development kit
Publication Date: 2024.04.24 BEIJING XIAOMI MOBILE SOFTWARE CO LTD
  • EP3418885B1 patent drawingFigure 1
  • EP3418885B1 patent drawingFigure 2
  • EP3418885B1 patent drawingFigure 3

AI summary

The present disclosure relates to a method for calling a software development kit. The method is applied in a platform and may include: according to a received preset instruction, triggering (S11) a target application to call a software development kit of a third-party application, wherein the target application runs on the platform; transmitting (S12) identification information of the target application to the software development kit; determining (S13) metadata which is required for the third-party application to verify the target application, and establishing an association relationship between the metadata and the identification information; and registering (S14) the metadata into a system which the platform resides in so that the third-party application performs verification by obtaining the metadata associated with the identification information according to the association relationship.