Decentralized Trust System for Multi-Provider Virtual Network Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service models in the telecommunications industry face challenges in providing agile and flexible orchestration for multi-provider services due to complex interactions between lifecycle management domains controlled by different service providers, leading to slow and inflexible solutions for resource integration and allocation.
Innovation Solution
A decentralized trust system using Blockchain technology enables direct interactions between lifecycle management components by establishing a consensus-based negotiation mechanism, allowing for the creation of smart contracts that facilitate the discovery and provision of services across multiple providers, thereby bypassing traditional complex orchestration layers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional orchestration mechanisms are used for multi-provider services, then service providers can manage their own lifecycle domains, but the complexity of interactions between multiple providers increases and orchestration becomes slow
Solution Approach 1:
The patent introduces a decentralized trust system as an intermediary layer between multiple LCM components from different service providers. This trust system mediates interactions by providing a common framework for discovery, negotiation, and coordination without requiring complex direct peer-to-peer orchestration between providers, thereby reducing overall system complexity while enabling multi-provider collaboration
2Adaptability or versatility
If multiple lifecycle management components from different service providers interact, then service diversity and choice increase, but orchestration loops crossing multiple vertical management layers slow down service delivery
Solution Approach 1:
The patent segments the orchestration process into distinct functional layers: the decentralized trust system handles discovery and coordination at one level, while individual LCM components manage their own lifecycle operations at another level. This segmentation eliminates the need for slow orchestration loops crossing multiple vertical management layers, as each segment operates semi-independently within the trust framework
Solution Approach 2:
The decentralized trust system performs preliminary actions by pre-establishing trust relationships, capability registries, and negotiation frameworks before actual service orchestration occurs. This preliminary setup enables rapid direct interactions between LCM components without requiring time-consuming multi-layer orchestration loops during service delivery
3Loss of time
If direct interaction between lifecycle management domains is enabled, then resource allocation speed increases, but trust and coordination mechanisms between different providers become more complex
Solution Approach 1:
The decentralized trust system implements universal, standardized interfaces and protocols that work across all service providers and LCM components. This universality allows direct interaction between diverse providers without requiring custom trust mechanisms for each pair, reducing the overall complexity of trust management while enabling fast resource allocation
Data Source
AI summary
Embodiments herein provide methods and apparatus for providing multi-provider virtual network service. A first lifecycle management, LCM, component is provided controlled by a first service provider in a virtual network, wherein the virtual network comprises a trusted LCM component controlled by a trusted provider configured to provide a decentralised trust system between a plurality of LCM components controlled by different service providers in the virtual network. The first LCM component may perform a method comprising receiving a service request to provide a first service; responsive to a determination that the first service cannot be fully provided by the first service provider, generating a first tag representing a portion of the first service that the first service provider cannot provide; transmitting a discovery request to the trusted LCM component, wherein the discovery request comprises the first tag; receiving, from the trusted LCM component based on the first tag, a list of LCM components comprising a second LCM component controlled by a second service provider, wherein the second service provider is capable of providing a part of the portion of the first service; and transmitting a provision request to the second LCM component to provide the part of the portion of the first service.