Interworking Broker Function for Legacy Network Appliances
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data centers often have a mix of legacy and virtualized network appliances, making it challenging to manage both types seamlessly within a single interface, especially during gradual migration processes.
Innovation Solution
The implementation of an interworking broker function (IBF) that scans the network for legacy devices, queries them using standard protocols like SNMP, and builds translation drivers to translate MANO commands into formats consumable by legacy devices, allowing them to be managed as if they were virtual network functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If legacy network appliances are integrated into NFV/SDN infrastructures, then network management is simplified and administration is streamlined, but the legacy devices lack native interoperability with orchestrators and require additional translation mechanisms
Solution Approach 1:
An interworking broker function is introduced as an intermediary component that sits between the legacy network appliance and the NFV orchestrator. This broker translates MANO commands into formats consumable by legacy devices and translates device messages into formats the orchestrator can understand, enabling seamless integration without modifying the legacy appliance itself.
Solution Approach 2:
The integration architecture is segmented into distinct functional components: the legacy network appliance, the interworking broker function, and the NFV orchestrator. This segmentation allows each component to operate independently with its own interface and protocol, reducing the complexity burden on any single element while enabling manageable integration.
2Adaptability or versatility
If translation drivers are built to convert MANO commands for legacy devices, then legacy appliances can be managed through standard orchestration interfaces, but additional software components and protocols are required
Solution Approach 1:
The interworking broker function serves multiple purposes: it acts as a translation engine for commands, a message router for telemetry and events, and a protocol adapter for different communication formats. This multi-functionality reduces the need for separate specialized components for each integration task.
Solution Approach 2:
The translation driver creates a virtual representation or copy of the legacy device's interface within the NFV environment. This virtual interface mimics the legacy device's native protocols and formats, allowing the orchestrator to interact with it as if it were a standard virtual network function, while the broker handles the actual translation to the legacy device's native format.
3Extent of automation
If legacy devices are scanned and queried using standard protocols, then device discovery and integration are automated, but the integration process requires additional processing and communication overhead
Solution Approach 1:
The interworking broker performs preliminary actions by scanning the network for legacy devices and querying them using standard protocols like SNMP before full integration occurs. This advance discovery and characterization of legacy devices allows the system to prepare translation drivers and integration configurations in advance, reducing the time required during actual deployment.
Data Source
AI summary
A computing apparatus, including: a hardware platform; and an interworking broker function (IBF) hosted on the hardware platform, the IBF including a translation driver (TD) associated with a legacy network appliance lacking native interoperability with an orchestrator, the IBF configured to: receive from the orchestrator a network function provisioning or configuration command for the legacy network appliance; operate the TD to translate the command to a format consumable by the legacy network appliance; and forward the command to the legacy network appliance.