Patent Application
20210191529
Computers today are used in a variety of ways. Personal computers, for example, are used by users with a variety of user interface peripherals including keyboards, mice, displays, and so forth. Servers, on the other hand, are often operated without these peripherals and instead rely on a network connection to perform various functions such as controlling what applications should be operated on the server, what tasks are performed by the servers, what data the servers store, and so forth. Computers that have been configured to be controlled via a network without a display, keyboard, and mouse are sometimes referred to as headless systems.
The present application may be more fully appreciated in connection with the following detailed description taken in conjunction with the accompanying drawings.
Systems, methods, and equivalents associated with keyboard emulation are described. Because headless devices can generally be controlled remotely, headless devices are often stored in racks, in out of the way spaces (e.g., a locked storage), or even in remote locations. While they may generally operate without a user having to physically access the device, there are still some scenarios where being able to physically interact with a device is desirable. For example, certain operating system hangs may make it desirable to force a device to restart.
Consequently a remote signal receiver may be embedded into a device to allow receipt of wireless signals to control emulation of keyboard and power inputs to the device. The remote signal receiver may receive a signal (e.g., infrared) from a remote control that controls a component of the device to act as it were receiving inputs from a keyboard or a physical power button on the device. This may allow, for example a user to select boot settings during a basic input/output system mode of the device, hard reset the device, and so forth, without being able to physical reach the device or have a keyboard attached to the device.
While some examples herein may refer to headless devices, in other examples, techniques described herein may operate in systems that are operating with input and/or output peripherals. For example, a device controlling digital signage (e.g., advertisements on a mall or billboard) may be considered to be attached to a display, and yet still be stored in an out of reach location to prevent someone from accidentally or deliberately interfering with the digital signs. In the event the device is to be configured, a user may interact with the device using an appropriately configured remote to control emulation of keyboard and/or power signals. Thus, many types of devices may take advantage of techniques described herein.
System 100 includes a controller 110. Controller 110 may be connected with several aspects of system 100 in a manner that allows controller 110 to emulate input from various components of system 100 and or peripherals that could be attached to system 100. Thus, controller 110 may include circuitry that directly connects to the other components of system 100. Controller 110 may control the various components of system 100 based on signals received from a remote control 199 via a remote signal receiver 120. While a remote control 199 is illustrated in
In various examples, the signals received from remote control 199 may be specifically designed into remote control 199. Thus, remote control 199 may include aspects of a keyboard. In other examples, the signals received from remote control 199 may be programmatically generated either by remote control 199 itself or based on a signal received from a remote device. By way of illustration, after a system administrator detects a failure of system 100, the administrator or an application controlled by the administrator may generate a set of instructions and embed them on remote control 199. When the administrator reaches the vicinity of system 100, the administrator may press a button on remote control 199 which may cause remote control 199 to play back the set of instructions to remote signal receiver 120.
The signals received by controller 110 via remote signal receiver 120 may cause controller 110 to emulate inputs specified in the signals to the components of system 100. For example, controller 110 is connected to a super input/output (super I/O) controller 130 of system 100. Super I/O 130 may be an integrated circuit embedded in system 100 that combines interfaces for a variety of components of system 100. These components may include a keyboard controller that allows for receiving keyboard inputs that can then be interpreted by, for example, a processor of system 100. Thus, controller 110 may facilitate emulating keyboard inputs to system 100 by, for example, generating signals that would be generated by presses of a keyboard. In other examples, the controller may cause emulation of keyboard inputs by controlling super I/O 130 to act as though the keyboard inputs had been received.
While the keyboard inputs could theoretically be interpreted at a variety of points during operation of system 100, the ability to emulate keyboard inputs may be specifically desirable during a basic input/output system (BIOS) mode of operation of system 100. This may be because system 100 has limited functionality while in the BIOS state. For example, in the BIOS state, system 100 may not have networking capability that would allow selection of settings until after system 100 has successfully loaded an operating system. Consequently, selecting appropriate boot settings without the ability to emulate the keyboard may involve physical access to system 100 which may mean accessing system 100 from amongst many in a server rack, or pulling system 100 from an out of reach location. Instead, emulation of keyboard input to select boot settings based on signals received from remote control 199, system 100 may be able to boot into a mode controllable over a network without direct physical access to system 100.
In another example, controller 110 may also be connected to a power supply 140. This may allow controller 110 to emulate inputs to a physical power button 150 to power supply 140. This may allow, for example, controller 110 to turn system 100 on or off, hard reset system 100, cause system 100 to enter a sleep mode, and so forth. In some examples, controller 110 may connect directly to power supply 140. However, as illustrated here, controller 110 may interface directly with circuitry connecting power supply 140 and power button 150. Thus, controller 110 and remote signal receiver 120 may be circuitry built into system 110 during manufacturing, as opposed to an accessory or peripheral attached to system 100 after system 100 has been shipped.
In some examples, it may be desirable to ensure certain security checks are made before controller 110 takes action in response to a signal from remote control 199. In some examples, a pairing action may be performed during, for example, an initial setup of system 100, controller 110, and/or remote control 199. The pairing process may ensure that unauthorized devices and/or users cannot control system 100. In other examples, remote control 199 may be able to transmit a signal that is specifically configured to control specifically system 100, and not control other nearby systems also configured with a remote signal receiver that can emulate inputs (e.g., other similarly configured systems on the same server rack). In other examples, remote control 199 may transmit a signal that authenticates itself to controller 110 to prevent unauthorized actions from being taken by controller 110.
It is appreciated that, throughout this description, numerous specific details are set forth to provide a thorough understanding of the examples. However, it is appreciated that the examples may be practiced without limitation to these specific details. In other instances, methods and structures may not be described in detail to avoid unnecessarily obscuring the description of the examples. Also, the examples may be used in combination with each other.
“Module”, as used herein, includes but is not limited to hardware, firmware, software stored on a computer-readable medium or in execution on a machine, and/or combinations of each to perform a function(s) or an action(s), and/or to cause a function or action from another module, method, and/or system. A module may include a software controlled microprocessor, a discrete module, an analog circuit, a digital circuit, a programmed module device, a memory device containing instructions, and so on. Modules may include gates, combinations of gates, or other circuit components. Where multiple logical modules are described, it may be possible to incorporate the multiple logical modules into one physical module. Similarly, where a single logical module is described, it may be possible to distribute that single logical module between multiple physical modules.
System 200 also includes a remote signal receiver 220. Remote signal receiver 220 may communicate via, for example, infrared signals, Bluetooth, ZigBee, radio frequency, Wi-Fi, Z-Wave, and so forth. Remote signal receiver 220 may receive signals from a remote control or other device configured to communicate with remote signal receiver.
System 200 also includes a control module 230. Control module 230 may receive a first signal via remote signal receiver 220. Based on the first signal, control module 230 may communicate with input/output controller 210. For example, control module 230 may control input/output controller 210 to emulate a keyboard input. As used herein, keyboard inputs may include a variety of alphanumeric and other inputs enterable via a keyboard. The keyboard inputs are intended to include, for example, letters in various cases, numbers, special characters, spacing characters, movement directions, special functions, and so forth. The emulated keyboard inputs may control system 200 while system 200 operates in a basic input/output system (BIOS) mode. This may allow, for example, control of selection of boot options during the BIOS mode. Selection of boot options may facilitate restoring system 200 to a state in which system 200 may be controlled and/or managed by a remote entity via a network connection.
System 300 also includes a power supply 340. Control module 330 may receive a second signal via remote signal 320. Control module 330 may communicate with power supply 340 based on the second signal to emulate a power button input. The emulated power button input may control power supply 340 to, for example, power on, power off, enter a sleep mode, hard reset, and so forth.
Method 400 may perform various tasks associated with keyboard emulation. Method 400 includes receiving a first signal at 420. The first signal may be received via a remote signal receiver. The first signal may include instructions intended to control a device. The device may be, for example, a headless device operating without input and/or output peripherals.
Method 400 also includes providing a control signal to an input/output controller of the device at 430. The control signal may control the input/output controller to emulate a keyboard input. The specific keyboard actions emulated may be specified by the first signal. In one example, the keyboard input may control selection of boot settings for the device.
Method 600 also includes receiving a second signal at 540. The second signal may be received via the remote signal receiver. The second signal may seek to control a power operation of the device. Method 500 also includes providing a power signal at 550. The power signal may be provided to a power supply of the device. The power signal may emulate a power button input for the device.
Method 500 also includes receiving an authenticating signal at 510. The authenticating signal may be received from a device (e.g., a remote control) providing the control signal. In various examples, the authenticating signal may serve a variety of functions. In one example, the authenticating signal may be configured to tie the device providing the control signal to the device performing method 500. By way of illustration, this may link a specific remote control and a specific server. This may be achieved by, for example, communicating a channel for future communications. The device performing method 500 may then listen on this channel for further instructions. In another example, the authenticating signal may be a signal designed prove that the device providing the control signal is authorized to control the device performing method 500. This may prevent unauthorized interactions with the device performing method 500. In another example, the authenticating signal may be a signal designed to identify a specific device to perform actions in a subsequent control signal. This may be desirable when multiple devices that could potentially perform operations of method 500 are in close proximity to one other (e.g., in a server rack).
Computing system 600 also includes a power supply 640. Power supply 650 may be communicatively coupled to control module 630. In this examples, control module 630 is communicatively coupled to the power supply via circuitry connecting the power supply to a power button 645 of computing system 600. In response to a power signal received via remote signal receiver 620, control module 630 may provide a signal to the power supply that emulates an input to the power supply.
In various examples, computing system 600 may be a computer that includes a processor 650 and memory, and other components connected by a bus. Control module 630 may perform keyboard emulation functions for computing system 600. In different examples, control module 630 may be implemented as a non-transitory computer-readable medium storing processor-executable instructions, in hardware, software, firmware, an application specific integrated circuit, and/or combinations thereof.
The instructions may also be presented to processor 650 as data and/or processes that are temporarily stored in memory and then executed by processor 650. Processor 650 may be a variety of processors including dual microprocessor and other multi-processor architectures. Memory may include non-volatile memory (e.g., read only memory) and/or volatile memory (e.g., random access memory). Memory may also be, for example, a magnetic disk drive, a solid state disk drive, a floppy disk drive, a tape drive, a flash memory card, an optical disk, and so on. Thus, memory may store processes and/or data. Computing device 600 may also be associated with other devices including other computers, devices, peripherals, and so forth in numerous configurations (not shown).
It is appreciated that the previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/US2017/030044 | 4/28/2017 | WO | 00 |
