API-Based Virtual Console for Browser-Free Server Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote viewing technologies for server class information handling systems require a web browser and physical access, limiting their usability and flexibility.
Innovation Solution
A REST-compliant API-based service, such as Redfish, is used to provide virtual console resources including virtual keyboard, video, and mouse resources, enabling browser-free access and remote interaction through a RESTful API client.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If HTML-based remote viewing is used, then remote system management is enabled, but web browser and physical access are required
Solution Approach 1:
The patent introduces a RESTful API as an intermediary layer between the BMC and the remote client, replacing the browser-dependent HTML interface. The API service exposes standardized endpoints that allow programmatic access to virtual console functions without requiring a web browser, thus achieving browser independence while maintaining remote access capability.
Solution Approach 2:
The patent replaces the mechanical interaction model of HTML-based graphical interfaces with an automated API-based interaction model. Instead of requiring users to manually navigate web browsers and interact with graphical elements, the system enables automated scripts and applications to directly invoke API endpoints for virtual console operations, substituting manual mechanical interaction with programmatic automation.
2Reliability
If physical access is required for remote viewing, then system security is maintained, but usability and flexibility are limited
Solution Approach 1:
The RESTful API service acts as a secure intermediary between the BMC and remote clients. It implements authentication and authorization mechanisms that verify client identities and permissions before allowing access to virtual console resources. This mediator layer maintains system security by controlling access through defined API protocols rather than requiring physical presence, thus improving remote access flexibility while preserving security.
3Ease of operation
If web browser is required for remote console access, then graphical interface is provided, but automation capability is reduced
Solution Approach 1:
The patent replaces the manual graphical interface interaction model with an automated API interaction model. The RESTful API exposes endpoints that can be directly called by scripts and automation tools, enabling programmatic control of virtual console functions. This substitution eliminates the need for manual browser-based interaction while maintaining full functionality, thereby significantly enhancing automation capability.
Solution Approach 2:
The RESTful API service provides universal access to virtual console functions through standardized endpoints that can be invoked by multiple types of clients including automated scripts, applications, and manual users. The same API endpoints support both automated programmatic access and potential graphical interface implementations, making the system multi-functional and eliminating the trade-off between graphical interface availability and automation capability.
Data Source
AI summary
Disclosed systems and methods enable a RESTful API server, e.g., a Redfish server, provisioned with virtual console resources running on a system management resource, e.g., a BMC, of an information handling system, to perform virtual console operations. The virtual console features include a virtual video feature for relaying frame buffers of video data, corresponding to video output from a host application, to a RESTful API client. The virtual console features may further include virtual keyboard and mouse features, which may be collectively referred to herein as virtual HID features, for relaying keyboard and mouse data, indicative of keyboard scan codes, mouse x, y coordinates, and mouse activity, e.g., Right Click, Left Click, etc., generated by a user of the RESTful API client.