SDK Penalty Container for Runtime Policy Enforcement

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Mobile app developers face challenges in identifying and addressing performance failures caused by software development kits (SDKs), leading to user dissatisfaction and financial burdens due to costly licensing fees, as issues are often unclearly attributed to either the app or the SDK.

Innovation Solution

Implementing a penalty container system that wraps SDKs, re-instruments API calls, and monitors performance, security, and privacy policies, allowing for penalty assessment and redistribution to SDK providers based on policy violations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If developers use third-party SDKs to accelerate development, then development speed and functionality are improved, but reliability and accountability deteriorate due to unclear responsibility for runtime errors

Engineering Contradiction:

Improvedevelopment speedVSAvoidaccountability for runtime errors

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent introduces a penalty container as an intermediary layer between the SDK and the app. This container wraps the SDK code and includes monitoring mechanisms that track runtime behavior, enabling clear attribution of errors to either the SDK or the app while maintaining development efficiency.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms through penalty assessments that provide information about SDK performance and violations. The penalty container monitors SDK behavior and provides feedback to developers about runtime errors, enabling them to make informed decisions about SDK usage and accountability.

Inventive Principle:

Principle #23Feedback

2Adaptability or versatility

If developers pay licensing fees for SDKs, then functionality is improved, but financial loss increases when SDK violations occur

Engineering Contradiction:

ImprovefunctionalityVSAvoidfinancial loss

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent converts the potential harm of SDK violations into a beneficial penalty assessment system. When violations occur, the penalty container automatically assesses and redistributes penalties, turning financial loss from violations into a mechanism that rewards compliant SDKs and compensates affected parties.

Inventive Principle:

Principle #22Blessing in disguise (Convert harm into benefit)

Solution Approach 2:

The system changes the financial parameter structure by introducing penalty assessments that modify the cost-benefit analysis of SDK usage. Instead of fixed licensing fees only, the system adds dynamic penalty components that adjust based on SDK compliance and performance, creating a more nuanced financial model.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If developers favor well-known SDKs to ensure trustworthiness, then reliability is improved, but adaptability deteriorates as newer SDKs cannot establish trust

Engineering Contradiction:

ImprovetrustworthinessVSAvoidadoption of newer SDKs

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The penalty container enables SDKs to self-demonstrate their reliability through automated monitoring and penalty assessment. Newer SDKs can prove their trustworthiness by consistently meeting performance targets and avoiding violations, allowing them to earn trust without relying on brand reputation.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system replaces the mechanical system of reputation-based trust with an automated digital assessment mechanism. The penalty container objectively measures SDK performance and enforces penalties based on verifiable data, eliminating the need for subjective trust assessments and enabling fair evaluation of all SDKs regardless of age or reputation.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10990984B2Assessing penalties for SDKs that violate policies in mobile apps

Publication Date: 2021.04.27 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A system, method and program product for processing software development kits (SDKs). A system is provided that includes a container creation system that wraps an inputted SDK in a penalty container to create a wrapped SDK, wherein the wrapped SDK includes re-instrumented code that redirects application programming interface (API) calls between the SDK and an associated App and operating system through a wrapper in order to monitor runtime behavior; wherein the container creation system instantiates a policy module that is configurable by an SDK provider and App developer to implement a mutual policy configuration for the penalty container; and wherein the penalty container includes a penalty manager notifies the SDK provider and App developer of SDK violations of the mutual policy configuration.