Server IPMI Interface Using Single PCI Protocol for Remote Peripheral Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional remote peripheral device access systems are complex due to the need for multiple communication protocols, complicating the structure and increasing costs, especially when adding support for new types of devices.
Innovation Solution
A server architecture that uses a single Peripheral Component Interconnect (PCI) protocol for data communication between a controller, bridge, and interface circuit, allowing access to multiple types of peripheral devices such as USB, SATA, and IDE devices over a network, simplifying the structure and reducing the need for multiple protocol-specific chips.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple protocol-specific chips (USB chip, SATA chip, IDE chip) are used to support different peripheral device types, then the system can access diverse device types, but the device complexity and structure are significantly increased
Solution Approach 1:
The patent applies universality by implementing a single interface circuit that can handle multiple communication protocols (USB, SATA, IDE) through software configuration rather than requiring separate hardware chips for each protocol. The interface circuit is designed to be protocol-agnostic, allowing the same hardware to serve multiple functions by loading appropriate protocol handlers or drivers.
Solution Approach 2:
The patent introduces an intermediary layer (the interface circuit with protocol translation capability) between the controller and various peripheral devices. This intermediary can translate different protocol-specific signals into a unified internal format that the controller can process, eliminating the need for multiple dedicated chips while maintaining protocol compatibility.
2Adaptability or versatility
If multiple protocol-specific chips are implemented in the IPMI section, then support for multiple device types is achieved, but the firmware complexity and development time increase significantly
Solution Approach 1:
The interface circuit is designed with universal protocol handling capability, allowing a single firmware codebase to support multiple protocols through configurable drivers or translation layers. This reduces firmware development time because the core logic remains the same while only protocol-specific adaptation layers need to be implemented or configured.
Solution Approach 2:
The patent segments the protocol handling into separate modular components (protocol handlers, drivers, or translation layers) that can be independently developed, tested, and configured. This modular approach allows firmware developers to work on individual protocol support without affecting other protocols, reducing overall development complexity and time.
3Reliability
If separate chips are used for each communication protocol, then protocol-specific functionality is optimized, but the hardware cost and layout difficulty increase
Solution Approach 1:
The interface circuit is designed as a universal component that can handle multiple protocols, reducing the total number of chips required and simplifying the hardware layout. This universal design maintains protocol communication reliability through proper signal conditioning and translation while reducing PCB real estate requirements and assembly complexity.
Data Source
AI summary
A server having remote peripheral device access functions for accessing different types of peripheral devices located on a remote host, such as USB, SATA and IDE devices. The remote device access function is implemented in the IPMI section of the server. The IPMI section is connected to a bridge of the server, and communicates with the bridge using a single predetermined communication protocol, such as the PCI protocol, regardless of the type of the peripheral devices being remotely accessed. An application on the remote host communicates with the IPMI section of the server to transmit the data generate by or to be consumed by the peripheral device using a predetermined network protocol.