Network Slice Intent Consensus Automation With Distributed Ledger Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network slicing systems face challenges in ensuring consensus and maintaining shared understanding of slice intent and content among multiple participants, particularly in scenarios with limited trust relationships, leading to potential breaches and the need for extensive human intervention.
Innovation Solution
A distributed ledger-based system that automates the process of updating slice content and intent by enforcing consensus through update rules, ensuring that transactions adhere to predefined constraints and participant agreements, minimizing human interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual consensus processes are used among network slice participants, then trust relationships can be established, but the system requires extensive human intervention and is inefficient
Solution Approach 1:
The system enables participants to automatically validate transactions and reach consensus through predefined update rules stored in the distributed ledger. Each participant independently checks whether transactions fulfill the rules, eliminating the need for manual intervention while maintaining reliable consensus through automated rule-based validation.
Solution Approach 2:
The distributed ledger acts as an intermediary that stores and enforces update rules, mediating between participants to ensure consistent consensus. The ledger automatically validates transactions against stored rules, serving as a trusted mediator that eliminates manual coordination while maintaining reliability through rule-based enforcement.
2Extent of automation
If distributed ledger technology is implemented to automate consensus, then human intervention is minimized, but ensuring consistent understanding of slice intent among participants becomes challenging
Solution Approach 1:
The distributed ledger serves multiple functions: it stores update rules, validates transactions, maintains transaction history, and ensures consistent understanding of slice intent across all participants. By centralizing these functions in a shared ledger, the system maintains automated operation while preventing information loss through universal access to the same truth.
Solution Approach 2:
The system provides feedback to participants through the distributed ledger, which records and broadcasts transaction validation results and updated slice intent. This feedback mechanism ensures all participants maintain consistent understanding by automatically notifying them of state changes and validation outcomes, preventing information divergence.
3Manufacturing precision
If update rules are enforced through distributed ledger, then transaction consistency is improved, but the system complexity increases
Solution Approach 1:
The system manages complexity by parameterizing update rules in the distributed ledger, allowing flexible configuration of validation criteria without changing the underlying system architecture. Participants can modify transaction consistency parameters (rules) independently, achieving high transaction precision while maintaining manageable system complexity through configurable parameters rather than hard-coded complexity.
Data Source
AI summary
A method comprising: retrieving update rules stored in a distributed ledger from the distributed ledger; checking whether or not a received initial transaction fulfills all the retrieved update rules; creating a block comprising the initial transaction if the initial transaction fulfills all the retrieved update rules; broadcasting the block into a network of the distributed ledger, wherein, the initial transaction requests to modify a content of a slice and/or an intent of the slice; if the initial transaction requests to modify the content of the slice, at least one of the update rules constrains the content of the slice or the modifying of the content of the slice, and if the initial transaction requests to modify the intent of the slice, at least one of the update rules constrains the intent of the slice or the modifying of the intent of the slice.


