Smart Device Console Virtualization via MCTP Out-of-Band Channels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing smart device management systems face challenges in out-of-band management and lack universality, particularly when new functions or devices are added, requiring upgrades to both Baseboard Management Controller (BMC) firmware and external management software.

Innovation Solution

A method and apparatus for smart device management that virtualizes a console for smart devices using a Management Component Transfer Protocol (MCTP) out-of-band channel, enabling communication between a BMC and external management software, allowing interaction through common terminal tools without the need for BMC or software upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If MCTP binding protocols are used for out-of-band management, then communication between smart devices of different manufacturers is enabled, but new functions exceed the defined functions and require BMC firmware upgrades

Engineering Contradiction:
Improvecompatibility across manufacturersVSAvoidBMC firmware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the management functionality by introducing a gateway device that handles protocol conversion and function expansion. The BMC maintains its core MCTP protocol while the gateway device manages additional protocols and functions, separating the complexity from the BMC firmware.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a gateway device as an intermediary between the BMC and smart devices. This gateway device translates between MCTP protocol and other protocols, enabling extended functionality without requiring BMC firmware upgrades.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If manufacturer-specific implementations are used for extended functions, then switching configuration and debugging functions are provided, but the BMC cannot directly support these functions and upgrades are required

Engineering Contradiction:
Improveextended management functionsVSAvoidmanagement operation convenience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The gateway device serves as an intermediary that provides manufacturer-specific extended functions while maintaining a standardized interface with the BMC. This allows switching configuration, debugging, and other extended functions to be accessed through common tools without requiring BMC upgrades.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway device is designed with multi-functionality to handle both standard MCTP management and manufacturer-specific extended functions. It provides universal access points that work across different device types and manufacturers.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If standard MCTP protocol is used, then out-of-band communication is implemented, but external management software cannot manage smart devices with new functions

Engineering Contradiction:
Improveout-of-band communication reliabilityVSAvoidmanagement software compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The gateway device acts as a protocol mediator that translates between MCTP and other management protocols. This enables external management software to communicate with smart devices using familiar protocols while the BMC maintains reliable MCTP-based out-of-band communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway device dynamically adjusts protocol parameters and conversion methods based on the specific smart device being managed. This allows the system to maintain reliable MCTP communication while adapting to various device-specific requirements and extended functions.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3968170B1Smart device management method and apparatus, network device, and readable storage medium
Publication Date: 2025.10.22 ZTE CORP
  • EP3968170B1 patent drawingFigure 1~2
  • EP3968170B1 patent drawingFigure 3~4
  • EP3968170B1 patent drawingFigure 5~6

AI summary

Embodiments of the present disclosure provide a method for smart device management and apparatus, a network device, and a readable storage medium, comprising: virtualizing a console fora smart device; and performing at least one of console message in-put and output with external management by means of a management component transport protocol (MCTP) out-of-band channel.