BMC UBM Protocol Implementation via Software Stack
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Baseboard Management Controllers (BMCs) require larger and more expensive microcontrollers to support Universal Backplane Management (UBM) protocols, such as VPP/SHP and SGPIO, which increases costs and complexity.
Innovation Solution
Implementing a UBM stack within the BMC that executes UBM commands and data using a co-processor or the same processing unit, communicating through I2C buses to manage backplane operations, thereby reducing the need for extensive hardware upgrades.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a BMC implements UBM protocols (VPP/SHP and SGPIO) using traditional hardware approaches, then backplane management capability is achieved, but microcontroller size and cost increase
Solution Approach 1:
The patent combines the UBM protocol processing functionality with the existing BMC processor, eliminating the need for separate dedicated hardware controllers. The BMC executes a UBM stack that handles both VPP/SHP and SGPIO protocols through software implementation, merging multiple protocol handling capabilities into a single integrated processing unit.
Solution Approach 2:
The patent replaces traditional hardware-based protocol processing (mechanical/electrical systems) with software-based processing on the BMC. Instead of using dedicated hardware circuits for UBM protocols, the invention uses a software stack that runs on the BMC's processor, substituting physical hardware complexity with flexible software implementation.
2Reliability
If a BMC implements UBM protocols using dedicated hardware controllers, then protocol processing reliability is improved, but system cost increases
Solution Approach 1:
The BMC processor is designed to perform multiple functions including general system management and UBM protocol processing. By making the BMC universal and multi-functional, the system eliminates the need for additional dedicated controllers, thereby reducing component count and overall system cost while maintaining reliable protocol processing through software implementation.
Solution Approach 2:
The BMC serves itself by handling UBM protocol processing internally through its own processor and software stack, rather than requiring external dedicated controllers. This self-service approach reduces the need for additional hardware components and lowers system complexity and cost.
3Adaptability or versatility
If a BMC uses a larger microcontroller to support UBM protocols, then protocol versatility is improved, but device complexity and cost increase
Solution Approach 1:
The patent introduces dynamic software-based protocol handling instead of static hardware configurations. The BMC's processor dynamically executes different protocol stacks (VPP/SHP and SGPIO) as needed, allowing the system to adapt to different protocol requirements through software loading and execution rather than requiring fixed hardware configurations for each protocol.
Solution Approach 2:
The invention changes the fundamental parameter of protocol processing from hardware-based to software-based implementation. This parameter change allows the same physical processor to handle multiple protocols by loading and executing different software stacks, thereby achieving multi-protocol support without increasing hardware complexity or requiring larger microcontrollers.
Data Source
AI summary
In an aspect of the disclosure, an apparatus, a computer-readable medium, and a method are provided. The apparatus may be a service processor. The service processor receives, a first command or data of a UBM protocol from a UBM host running on a host of the service processor. The UBM protocol is a first protocol supported by the service processor. The first command or data instructs a backplane controller of the host to perform a first task. The service processor generates a second command or data of a second protocol supported by the service processor. The second command or data instructs the backplane controller to perform the first task. The service processor sends the second command or data to the backplane controller.