vBRAS Control Plane Message Parsing via Vendor-Specific Plug-ins
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The separation of control and forwarding planes in a virtual Broadband Remote Access Server (vBRAS) system poses challenges in parsing private-format data defined by different vendors, as there is no standard interface defined between the control plane and forwarding plane, leading to compatibility issues when managing devices from various vendors.
Innovation Solution
A message processing method that involves a control-plane device receiving private-format data, determining the target device's identification information, and selecting a matching message parsing plug-in to parse the data, allowing the control plane to manage forwarding-plane devices from different vendors by using category and unique identification information to match with corresponding plug-ins.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the vBRAS control plane centrally controls and manages forwarding-plane devices from different vendors, then the management capability and versatility are improved, but the complexity of parsing private-format data from different vendors increases
Solution Approach 1:
The parsing function is segmented into independent plug-ins, each responsible for a specific vendor's private-format data. The control plane device loads and invokes the appropriate plug-in based on the vendor identifier in the message, avoiding the need to embed multiple parsing implementations within a single complex parser.
Solution Approach 2:
A standardized interface acts as an intermediary between the control plane device and various vendor-specific parsing plug-ins. This interface defines uniform methods for message parsing, allowing the control plane to manage diverse vendors through a consistent mechanism without directly implementing multiple vendor-specific protocols.
2Ease of operation
If a standardized interface is defined between control plane and forwarding plane, then the ease of operation and compatibility are improved, but the device complexity increases due to plug-in management
Solution Approach 1:
The standardized interface is designed with universal methods that can handle multiple vendor formats through a common structure. The interface includes functions for parsing private attributes, extracting vendor identifiers, and converting to standardized formats, making it applicable to all vendor types without requiring vendor-specific control logic.
Solution Approach 2:
Each parsing plug-in is self-contained and automatically identifies its applicable vendor through vendor identifier matching. The control plane device simply loads available plug-ins and invokes them based on the message's vendor identifier, without requiring manual configuration or complex registration processes.
3Measurement precision
If vendor-specific private attributes are parsed, then the measurement precision and data accuracy are improved, but the loss of time increases due to multiple parsing operations
Solution Approach 1:
The vendor identifier is extracted and matched in advance to select the appropriate parsing plug-in before the actual parsing operation begins. This preliminary selection avoids trial-and-error parsing attempts and ensures the correct parser is invoked immediately, reducing overall processing time.
Solution Approach 2:
Each parsing plug-in is optimized for its specific vendor format with specialized parsing logic tailored to that vendor's private attribute structure. This localized optimization ensures accurate and efficient parsing for each vendor type without requiring a generic, slower parsing approach to work for all vendors.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Provided are a message processing method and apparatus, a control-plane device and a computer storage medium. The method includes receiving a first message containing at least one type of private-format data; determining identification information of a target device according to the first message and selecting a message parsing plug-in that matches the determined identification information of the target device; and sending the first message to the selected message parsing plug-in and receiving parsed data from the selected message parsing plug-in, where the parsed data is data obtained after the selected message parsing plug-in parses the at least one type of private-format data in the first message; and determining, according to the parsed data, a manner in which the target device processes a second message used for accessing a website.