USB4 Connection Manager Automatic Switching Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The transition between software-based and firmware-based USB4 Connection Managers is not seamlessly managed, particularly during OS upgrades, downgrades, or dual boot scenarios, leading to potential disruptions in USB4 functionality and interoperability across different host and device silicon vendors.
Innovation Solution
A mechanism for automatic switching between software and firmware-based USB4 Connection Managers is implemented, involving a handshake between BIOS and the operating system to dynamically switch between CMs based on capability mismatches, and a deployment mechanism using class codes and identifiers to ensure the correct driver is loaded, maintaining consistent CM mode across BIOS and OS environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a firmware-based Connection Manager is used, then USB4 functionality is maintained in legacy OS versions and during BIOS pre-boot, but switching between FW and SW CM modes during OS upgrades or downgrades causes disruptions in USB4 operation
Solution Approach 1:
The system dynamically selects between firmware-based and software-based Connection Manager modes based on runtime conditions. The BIOS determines the appropriate CM mode during boot, and the OS can later switch between modes through a defined handshake mechanism, allowing the system to adapt to different operational contexts (pre-boot vs. OS runtime, legacy vs. modern OS versions) without disruption
Solution Approach 2:
The system changes the operational parameter of Connection Manager mode (FW vs. SW) based on detected conditions. A capability bit in the OS indicates support for SW CM mode, and the BIOS uses this information along with runtime conditions to select the appropriate mode, ensuring continuous USB4 functionality across different scenarios
2Adaptability or versatility
If a software-based Connection Manager is used, then interoperability is improved across different host and device silicon vendors, but legacy OS versions without native SW CM support cannot operate USB4
Solution Approach 1:
The system applies different Connection Manager implementations to different operational contexts. Software-based CM with class codes and identifiers is used when OS support is available (improving vendor interoperability), while firmware-based CM is used for legacy OS versions (maintaining functionality). The capability bit mechanism allows the system to locally adapt to each OS's features
Solution Approach 2:
The Connection Manager system is designed to perform multiple functions through two implementation modes. The firmware-based CM provides universal support across all OS versions including legacy systems, while the software-based CM provides enhanced vendor interoperability for modern OS versions. Both modes implement the same core USB4 management functions
3Ease of operation
If manual configuration of Connection Manager mode is required, then control over CM selection is improved, but complexity of setup and potential for errors increases
Solution Approach 1:
The system automatically determines the appropriate Connection Manager mode without requiring manual user configuration. The BIOS automatically detects OS capability bits and runtime conditions, then selects and configures the appropriate CM mode (FW or SW). The OS similarly automatically switches modes based on detected conditions, eliminating the need for users to manually configure CM settings while maintaining full control over mode selection
4Adaptability or versatility
If separate CM modes are maintained for BIOS and OS environments, then each environment can be optimized, but maintaining consistency between BIOS and OS CM modes becomes difficult
Solution Approach 1:
The system uses a feedback mechanism where the OS detects the CM mode configured in BIOS through capability bits and runtime condition checks. The OS then adjusts its CM mode selection based on this feedback to maintain consistency. The defined handshake mechanism ensures that mode changes in one environment are communicated to and coordinated with the other environment, maintaining CM mode consistency while allowing environment-specific optimizations
Data Source
AI summary
Automatic-switching and deployment of software (SW)- or firmware (FW)-based USB4 connection managers (CMs) and associated methods, apparatus, software and firmware. A handshake is defined between BIOS and an operating system (OS) to discover supported CM capability and dynamically switch from a FW CM to a SW CM and visa verse if there is a mismatch. In addition, a mechanism is defined to deploy the correct FW or SW CM driver based on class code, 2-part or 4-part ID. Support for continued USB4 operation during an OS upgrade or downgrade is provided, while ensuring that the best possible CM solution is used based on the advertised platform and OS capability. USB4 controllers support a pass-through mode under which the host controller FW redirects control packets sent between an SW CM and a USB4 fabric, and a FW CM mode under which control packets are communicated between the host controller FW and the USB4 fabric to configure USB4 peripheral devices and/or USB4 hubs in the USB4 fabric.