Hierarchical Data Bus Architecture for NFV Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As modern networks transition to software-based service functions, there is a need for efficient automation and management of Virtual Network Functions (VNFs) across complex networks, particularly in deployments like 5G cellular mobile communications and Mobile Edge Computing, where traditional hardware-centric approaches are being replaced, requiring enhanced data exchange and orchestration capabilities.
Innovation Solution
A hierarchical data bus system is employed, comprising multiple interconnected data buses and inter-bus hubs, which enables efficient configuration, monitoring, and management of VNFs by facilitating data exchange between NFV-MANO components and VNFs, using a Kafka Bus-like DMaaP system for data movement and processing, and inter-bus hubs for data aggregation, routing, and isolation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a flat data bus architecture is used in NFV systems, then data exchange between NFV-MANO components and VNFs is simplified, but traffic overhead increases and broadcast storms occur
Solution Approach 1:
The patent divides the flat data bus into multiple hierarchical levels (Level 1, Level 2, Level 3 data buses) with distinct functional domains. Level 1 handles local VNF communication, Level 2 handles regional aggregation, and Level 3 handles centralized management. This segmentation reduces traffic overhead by confining broadcast domains to local levels while maintaining operational simplicity through clear hierarchical routing rules.
Solution Approach 2:
The patent introduces a hierarchical dimension to the traditional flat data bus architecture, transforming it from a two-dimensional flat structure to a three-dimensional hierarchical structure. This adds vertical levels of data exchange (local, regional, centralized) while maintaining horizontal connectivity, thereby reducing broadcast storm propagation and traffic overhead without sacrificing operational simplicity.
2Loss of energy
If a hierarchical data bus architecture is implemented, then traffic overhead is reduced and broadcast storms are avoided, but system complexity increases
Solution Approach 1:
The architecture segments the data bus into independent hierarchical levels with clear functional boundaries. Each level handles specific communication tasks (local VNF, regional aggregation, centralized management), reducing the complexity burden on any single level while collectively providing comprehensive system management capabilities.
Solution Approach 2:
The patent introduces inter-bus hubs as intermediary components that connect different hierarchical levels. These hubs act as mediators that handle data exchange between levels, abstracting the complexity of hierarchical routing from individual VNFs and simplifying the interface between different architectural layers.
3Extent of automation
If centralized management is implemented at the top level, then orchestration control is improved, but response time for local operations increases
Solution Approach 1:
The patent segments management responsibilities across hierarchical levels: Level 1 handles local VNF operations independently for fast response, Level 2 performs regional aggregation and coordination, and Level 3 provides centralized orchestration. This segmentation enables automated centralized control where needed while maintaining fast local response for time-sensitive operations.
Solution Approach 2:
The hierarchical architecture adds a vertical dimension to management control, enabling differentiated response strategies at different levels. Local levels can respond immediately to operational needs while centralized levels provide coordinated orchestration, thereby reducing overall response time compared to purely centralized approaches.
Data Source
AI summary
An inter-bus hub, within a hierarchical data bus system, has a partitioned log that includes a first partition and a second partition, where the inter-bus hub is coupled to a first data bus residing in a first segment and to a second data bus residing in a second segment. The inter-bus hub aggregates, based on at least one set of rules, first data from the first data bus, and stores the first data in the first partition. The inter-bus hub aggregates, based on the at least one set of rules, second data from the second data bus, and stores storing the second data in the second partition. The inter-bus hub relays the first data from the first partition to a first destination and relays the second data from the second partition to a second destination.