API Counter Tracking With Blockchain Usage Records

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional billing models for computing resources face challenges such as inflexibility in tracking usage and security issues, leading to potential inaccuracies and vulnerabilities in recorded data.

Innovation Solution

Implementing a decentralized blockchain system to securely record computing resource usage by scanning APIs for labels with key-value pairs that dynamically track and increment counters, ensuring tamper-resistant storage and flexible adjustment of tracking rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a decentralized blockchain system is implemented to securely record computing resource usage, then data integrity and security are improved, but system complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a blockchain network as an intermediary layer between the computing resource usage tracking and billing systems. This mediator provides tamper-proof recording of usage data through distributed consensus mechanisms, ensuring data integrity without requiring direct trust between billing authorities and resource consumers. The blockchain acts as a neutral third party that both sides can verify independently.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If dynamic counter tracking is implemented through API labels, then tracking flexibility is improved, but implementation complexity increases

Engineering Contradiction:
Improvetracking flexibilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic counter tracking by associating increment counters with API labels that can be dynamically configured. The counters automatically increment based on API interaction events, allowing the tracking rules to adapt to different usage patterns without manual intervention. This dynamic approach enables flexible billing models where tracking parameters can change based on real-time conditions while maintaining automated operation.

Inventive Principle:
Principle #15Dynamics

3Measurement precision

If usage-based billing tracking is implemented with dynamic counters, then billing accuracy is improved, but development time increases

Engineering Contradiction:
Improvebilling accuracyVSAvoiddevelopment time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring increment counters and API labels during system setup. The tracking infrastructure is established in advance with predefined rules for counting API interactions, resource usage events, and billing metrics. This preliminary configuration enables accurate usage-based billing from the outset without requiring complex custom development for each billing scenario, as the system can handle various billing models through the pre-built counter mechanism.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250377893A1Tracking and securely recording computing resource usage
Publication Date: 2025.12.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20250377893A1 patent drawing
  • US20250377893A1 patent drawing
  • US20250377893A1 patent drawing

AI summary

According to examples, an apparatus includes a processor and a memory on which is stored machine-readable instructions that when executed by the processor, cause the processor to scan an application programming interface (API) for a specified label in the API, in which the specified label includes a counter that increments based on an API interacting with a computing resource for a caller of the API. The processor also reads a value of a counter in the specified label and records the read value of the counter and an identifier of an entity associated with the caller of the API onto a decentralized blockchain. The computing resource usage by the entity may thus be securely recorded, such that the computing resource usage may be used for any of a number of purposes, such as invoicing, usage tracking, and/or security.