Wireless Network API Blockchain Integration for Usage-Based Charging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless communication networks lack effective integration of blockchains and do not efficiently support Application Programming Interfaces (APIs) with distributed ledgers, limiting the efficient management and charging of wireless user device services.
Innovation Solution
Integrate distributed ledger circuitry within wireless communication networks to store API usage data in blockchain form, allowing for efficient management and charging through Application Functions (AFs) that expose APIs to external data systems, and utilize distributed ledger circuitry to terminate and deliver blockchain data blocks for accounting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If distributed ledger circuitry is integrated into wireless communication networks, then service management and charging processes are enhanced, but device complexity and integration difficulty increase
Solution Approach 1:
The patent segments the distributed ledger functionality into separate distributed ledger circuitry units that can be independently integrated into the wireless communication network. These circuitry units are divided into multiple ledger nodes that can be distributed across different network elements, allowing incremental integration without overwhelming system complexity. Each ledger node maintains a portion of the blockchain data structure, enabling parallel processing and reducing single-point complexity.
Solution Approach 2:
The patent introduces an intermediary interface layer between the existing wireless communication network elements and the new distributed ledger circuitry. This intermediary layer includes standardized APIs and communication protocols that mediate between traditional network functions (AMF, NEF, AF) and the blockchain-based service management system, simplifying integration by abstracting away the complexity of direct blockchain interactions.
2Measurement precision
If blockchain is used to store API usage data, then billing accuracy is improved, but data storage and processing overhead increase
Solution Approach 1:
The patent extracts only the essential billing-critical data elements and stores them on the blockchain, while keeping detailed raw usage data in traditional network databases. Specifically, only aggregated API usage metrics, service identifiers, and charging-relevant parameters are committed to the blockchain data blocks. This selective extraction maintains billing accuracy by preserving immutable records of chargeable events while minimizing blockchain storage overhead by excluding redundant detailed data.
Solution Approach 2:
Instead of storing all detailed usage data on the blockchain and then processing it for billing, the patent inverts the approach by first aggregating and filtering usage data at the network element level, then storing only the essential billing summary data on the blockchain. This inversion reduces the volume of data requiring blockchain storage while maintaining the precision needed for accurate billing through pre-processed aggregated metrics.
3Reliability
If multiple ledger nodes store replicated blockchain data, then system reliability is improved, but network bandwidth and processing resources are consumed
Solution Approach 1:
The patent implements local quality optimization by having different ledger nodes store different portions or different versions of the blockchain data structure based on their specific roles and requirements. Critical billing data is replicated across all nodes for reliability, while non-critical operational data is stored selectively at specific nodes. This differentiated storage approach maintains system reliability for essential functions while reducing overall network bandwidth consumption and processing overhead by avoiding unnecessary full replication of all data at every node.
Data Source
AI summary
In a wireless communication network, an Application Function (AF) exposes an Application Programming Interface (API) for User Equipment (UE) information, and in response, receives API calls from an external data system. The AF transfers API responses to the external data system. The AF transfers API usage data to distributed ledger circuitry. The distributed ledger circuitry stores the API usage data in data blocks that form a blockchain. The distributed ledger circuitry terminates the blockchain, and in response, transfers a terminating data block for delivery to a network data system. The network data system generates an API charge based on the AF API usage data in the terminating data block.