Block Link Server for Multi-Dimensional Hyperledger Cross-Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current billing systems in 5G networks are inefficient and resource-intensive when trying to identify and bill for actual resource usage, as they require searching through multiple hyperledgers, and contact tracing is also cumbersome due to the need for extensive searches through blockchain data structures.
Innovation Solution
Implementing a method to create and manage linking structures between hyperledger blocks, allowing for efficient data access and storage of links between network elements and subscriber devices, enabling faster and more efficient billing and contact tracing by creating links at the time of billing events or network interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional billing systems search through multiple hyperledgers to identify billable events, then billing accuracy is improved, but time consumption and resource usage increase significantly
Solution Approach 1:
The system creates link data structures in advance that pre-establish relationships between hyperledger blocks from different hyperledgers. These links are created at the time of network interactions rather than during billing events, so when billing needs to occur, the system can directly query these pre-established links without searching through multiple hyperledgers, thus maintaining billing accuracy while dramatically reducing time consumption
Solution Approach 2:
The invention introduces a block link server as an intermediary component that maintains link data structures between hyperledger blocks. This intermediary stores and manages the relationships between blocks from different hyperledgers, allowing the billing system to query billable events through this centralized link management layer rather than directly searching through multiple hyperledgers, thereby reducing resource usage while maintaining accurate billing
2Measurement precision
If traditional systems search through multiple hyperledgers to identify billable events, then complete event identification is improved, but resource consumption increases
Solution Approach 1:
The system extracts and separates the link management functionality from the hyperledger structures themselves. By creating a dedicated block link server that maintains link data structures, the system removes the burden of searching through multiple hyperledgers and concentrates link management in a single location, ensuring complete event identification through centralized link tracking while significantly reducing resource consumption across the network
Solution Approach 2:
The system creates simplified copies of block relationship information in the form of link data structures. Instead of accessing and analyzing the full hyperledger blocks from multiple hyperledgers, the system uses these lightweight link copies that contain only the essential relationship information, ensuring complete event identification while minimizing resource consumption during billing operations
3Measurement precision
If contact tracing searches through extensive blockchain data structures, then contact tracing accuracy is improved, but search time and complexity increase
Solution Approach 1:
The system pre-establishes link data structures that document network interactions between elements before contact tracing is needed. These links are created at the time of actual network communications, so when contact tracing is required, the system can directly query these pre-existing links to identify contacts accurately without having to perform complex searches through blockchain data structures, thereby maintaining tracing accuracy while reducing search complexity
4Speed
If the system stores detailed link information between hyperledger blocks, then data access efficiency is improved, but storage requirements increase
Solution Approach 1:
The system extracts only the essential link relationship information from full hyperledger blocks and stores only these extracted link identifiers in the link data structures. By separating the link management from the complete block data and storing only the necessary identification and relationship information, the system achieves fast data access efficiency while minimizing storage requirements
Solution Approach 2:
The system creates simplified copy structures (link data structures) that contain only the essential relationship information needed for billing and contact tracing operations. These copies include link identifiers and basic relationship data rather than full block contents, enabling efficient data access while keeping storage requirements low by storing only the minimal necessary information
Data Source
AI summary
A method for creating a link between hyperledger blocks by a block link server. The method comprises receiving by a block link server executing on a computer system a first link creation message from a first network element, the first link creation message comprising first block information comprising a first hyperledger identifier and a first block identifier, both associated with a first hyperledger, receiving by the block link server a second link creation message, comprising second block information comprising a second hyperledger identifier and a second block identifier, both associated with a second hyperledger, storing by the block link server a link data structure comprising the first block information and the second block information, and sending by the block link server a link identifier of the link data structure to the first network element.


