IP KVM devices

Abstract

An example of an Internet Protocol (IP) keyboard, video, and mouse (KVM) device includes a universal serial bus (USB) port, a display port, a network port, a Bluetooth transceiver, a processor, and memory. The USB port is communicatively coupled to a host device. The display port is communicatively coupled to the host device. The network port is communicatively coupled to a network. The processor is communicatively coupled to the USB port, the display port, the network port, and the Bluetooth transceiver. The memory stores a unique identifier that is transmitted to the client device via Bluetooth in response to establishing a Bluetooth connection between the client device and the IP KVM device. The unique identifier is used by the client device to establish a remote connection to the IP KVM device.

Description

Background Art

[0001] An Internet Protocol (IP) keyboard, video, mouse (KVM) device (e.g., a dongle) can be used to enable a user to access a host device (e.g., a server, workstation, computer, etc.) over a network. The IP KVM device can capture Universal Serial Bus (USB) signals (e.g., keyboard signals, mouse signals, peripheral device signals, etc.) and video signals from the host device and encode them into packets for transmission to a remote client device (e.g., a computer) over an Ethernet link. The remote client device can then decode the signals and output the video signals to a single display or multiple displays, and use the USB signals for USB devices connected to the host device and / or client device. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Figure 1A is a block diagram illustrating one example of an Internet Protocol (IP) keyboard, video, mouse (KVM) device.

[0003] Figure 1B is a block diagram illustrating another example of an IP KVM device.

[0004] Figure 2 is a block diagram illustrating one example of a system including an IP KVM device.

[0005] Figure 3 is a block diagram illustrating another example of an IP KVM device.

[0006] Figure 4 is a block diagram illustrating another example of a system including an IP KVM device.

[0007] Figure 5 is a flow chart illustrating one example of a method for connecting a client device to a host device over a network. DETAILED DESCRIPTION

[0008] In the following detailed description, reference is made to the accompanying drawings, which form a part thereof, and in which specific examples in which the present disclosure may be practiced are shown by way of illustration. It is to be understood that other examples may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description should not be viewed in a restrictive sense, and the scope of the present disclosure is defined by the appended claims. It is to be understood that the features of the various examples described herein may be combined with each other in part or in whole, unless specifically noted otherwise.

[0009] Internet Protocol (IP) keyboard, video, mouse (KVM) devices enable users to connect to remote host devices (e.g., computer systems). IP KVM devices connect to remote host devices and capture and emulate keyboard, video, and mouse devices. In order to connect to a specific host device via an IP KVM device, the user must know some information that uniquely identifies the IP KVM device, such as the IP KVM's host name or IP address. Most host devices do not advertise this information. Therefore, although a user may have physical access to a host device to which the IP KVM device is attached, the user may not be able to connect to the IP KVM device due to lack of information. Being able to identify and connect to a host device via an IP KVM device that the user has physical access to would be beneficial in many situations. For example, an IT administrator can easily identify and connect to one of the many computer systems in a server rack. An instructor can easily identify and connect to one of their students' computer systems in a classroom. Meeting attendees can easily identify and connect to the computer system demonstrating a product at a meeting venue.

[0010] Thus, as described herein, an IP KVM device connected to a host device (e.g., a server, workstation, etc.) can include a unique identifier that a client device can use to establish a remote connection between the client device and the IP KVM device. In one example, the unique identifier can be transmitted to the client device via a Bluetooth connection. In another example, the unique identifier can be visible on the IP KVM device (e.g., a QR code) and scanned or manually entered into the client device. The client device can then use the unique identifier to obtain connection information to establish a remote connection between the client device and the IP KVM device over a network.

[0011] Figure 1A 1 is a block diagram illustrating an example of an IP KVM device 100a. The IP KVM device 100a includes a universal serial bus (USB) port 102, a display port 104 (e.g., a digital visual interface (DVI) port, a high-definition multimedia interface (HDMI) port, a video graphics array (VGA) port, a DisplayPort port), a network port 106 (e.g., an Ethernet port), a Bluetooth transceiver 108, a processor 110, and a memory 112. The processor 110 is communicatively coupled to the USB port 102 via a communication path 103, to the display port 104 via a communication path 105, to the network port 106 via a communication path 107, to the Bluetooth transceiver 108 via a communication path 109, and to the memory 112 via a communication path 113.

[0012] As will be referenced below Figure 2In more detail, USB port 102 can be communicatively coupled to a host device (not shown). Display port 104 can be communicatively coupled to a host device. Network port 106 can be communicatively coupled to a network (not shown). Memory 112 stores a unique identifier 114, which is transmitted to the client device via Bluetooth in response to establishing a Bluetooth connection between the client device and IP KVM device 100a. The client device can use unique identifier 114 to establish a remote connection to IP KVM device 100a.

[0013] The processor 110 may include a central processing unit (CPU), a microprocessor, and / or other suitable logic circuitry for controlling the operation of the IP KVM device 100a. In addition to the unique identifier 114, the memory 112 may also store machine-readable instructions (e.g., software and / or firmware) to be executed by the processor 110 to control the operation of the IP KVM device 100a. The memory 112 may include random access memory (RAM), read-only memory (ROM), or a combination thereof. In one example, the processor 110 may authenticate the user of the client device via Bluetooth (e.g., by requesting a username and password) before transmitting the unique identifier to the client device.

[0014] Figure 1B is a block diagram illustrating another example of an IP KVM device 100b. The IP KVM device 100b is similar to the previously described Figure 1A The IP KVM device 100a is described and illustrated, except that the IP KVM device 100b includes a button 120 and a plurality of display ports 1041 to 104 N , where "N" is any suitable number of DisplayPorts (eg, 2-4). Multiple DisplayPorts 1041 to 104 N Each of them is respectively communicated through communication paths 1051 to 105 N Communicably coupled to the processor 110. Multiple display ports 1041 to 104 N Each of can be communicatively coupled to a host device (not shown). Button 120 is electrically coupled to processor 110 via signal path 121. In this example, a user can press button 120 to initiate a Bluetooth connection between a client device and IP KVM device 100b.

[0015] Figure 2 is a block diagram illustrating one example of a system 200. The system 200 includes the Figure 1A The IP KVM device 100a, host device 202, network 204, and client device 206 are described and illustrated. In other examples, the previously referenced Figure 1BThe IP KVM device 100 b described and illustrated may be used in place of the IP KVM device 100 a in the system 200 .

[0016] The USB port 102 of the IP KVM device 100a is communicatively coupled to the host device 202 via a communication path 212 to receive USB signals from the host device. The display port 104 of the IP KVM device 100a is communicatively coupled to the host device 202 via a communication path 214 to receive display signals from the host device. The processor 110 encodes the USB signals and display signals received from the host device 202 for transmission over the network 204. The network port 106 of the IP KVM device 100a is communicatively coupled to the network 204 via a communication path 216 to transmit the encoded USB signals and display signals over the network 204.

[0017] Client device 206 is communicatively coupled to network 204 via communication path 218. Client device 206 includes a processor 208 and a Bluetooth transceiver 210. Bluetooth transceiver 210 is communicatively coupled to processor 208 via communication path 209. In this example, when a user of client device 206 desires to establish a remote connection to host device 202, the user establishes a Bluetooth connection, indicated at 220, between Bluetooth transceiver 210 and Bluetooth transceiver 108. In response to establishing Bluetooth connection 220, processor 110 of IP KVM device 100a transmits unique identifier 114 to client device 206 via Bluetooth connection 220. In one example, processor 110 may authenticate the user of client device 206 via Bluetooth connection 220 (e.g., by requesting a username and password) before transmitting unique identifier 114 to the client device. Client device 206 then uses unique identifier 114 to establish a remote connection to IP KVM device 100a to access host device 202. In one example, the remote connection to the IP KVM device 100a is established through the network 204. In another example, the remote connection to the IP KVM device 100a is established through the Bluetooth connection 220. In this case, the communication path 218 between the client device 206 and the network 204 may be eliminated.

[0018] Figure 3is a block diagram illustrating another example of an IP KVM device 300. The IP KVM device 300 includes a USB port 302, a display port 304 (e.g., a DVI port, an HDMI port, a VGA port, a DisplayPort port), a network port 306 (e.g., an Ethernet port), a processor 310, and a unique identifier 314. The processor 310 is communicatively coupled to the USB port 302 via a communication path 303, to the display port 304 via a communication path 305, and to the network port 306 via a communication path 307.

[0019] As will be referenced below Figure 4 In more detail, USB port 302 can be communicatively coupled to a host device (not shown). Display port 304 can be communicatively coupled to a host device. Network port 306 can be communicatively coupled to a network (not shown). Unique identifier 314 is on IP KVM device 300. In one example, unique identifier 314 is visible on IP KVM device 300 so that a user can physically view or read unique identifier 314. Unique identifier 314 can include a Quick Response (QR) code. In other examples, unique identifier 314 can have another suitable form (e.g., a barcode, text, etc.). The unique identifier can be entered into a client device to establish a remote connection between the client device and IP KVM device 300 over a network.

[0020] The processor 310 may include a CPU, a microprocessor, and / or other suitable logic circuitry for controlling the operation of the IP KVM device 300. The processor 310 may execute machine-readable instructions (e.g., software and / or firmware) to control the operation of the IP KVM device 300. In one example, the IP KVM device 300 may include a memory 112 ( ) storing a unique identifier 114 that matches a unique identifier 314. Figure 1A ). In this case, as will be referred to below Figure 5 As described in more detail, the visible unique identifier 314 may be entered into the client device, and the client device may then scan the network for an IP KVM device storing a matching unique identifier 114 .

[0021] Figure 4 is a block diagram illustrating another example of a system 400. The system 400 includes the Figure 3The IP KVM device 300, host device 202, network 204, and client device 406 are described and illustrated. The USB port 302 of the IP KVM device 300 is communicatively coupled to the host device 202 via a communication path 212 to receive USB signals from the host device. The display port 304 of the IP KVM device 300 is communicatively coupled to the host device 202 via a communication path 214 to receive display signals from the host device. The processor 310 encodes the USB signals and display signals received from the host device 202 for transmission over the network 204. The network port 306 of the IP KVM device 300 is communicatively coupled to the network 204 via a communication path 216 to transmit the encoded USB signals and display signals over the network 204.

[0022] Client device 406 is communicatively coupled to network 204 via communication path 218. Client device 406 includes a processor 408, memory 410, and input device 414 (e.g., a keyboard, mouse, camera, barcode scanner, QR code scanner, etc.). Processor 408 is communicatively coupled to memory 410 via communication path 409 and to input device 414 via communication path 413. In this example, when a user of client device 406 desires to establish a remote connection to host device 202, the user enters unique identifier 314 on IP KVM device 300 into client device 406 via input device 414. Client device 406 then establishes a remote connection between client device 406 and IP KVM device 300 over network 204 based on unique identifier 314, allowing client device 406 to access host device 202.

[0023] In one example, the client device 406 can access a lookup table 412 stored in memory 410 to obtain connection information for the IP KVM device 300 based on the unique identifier 314. In another example, the client device 406 can access a management system or cloud-based server 420, which can be communicatively coupled to the network 204 via a communication path 421, to obtain connection information for the IP KVM device 300 based on the unique identifier 314. The lookup table, management system, or cloud-based server can contain data linking the unique identifier of each IP KVM device on the network to the connection information for each corresponding IP KVM device. Thus, by accessing the lookup table, management system, or cloud-based server, the client device 406 can use the unique identifier 314 of the selected IP KVM device to establish a remote connection to the selected IP KVM device. If the connection information for the IP KVM device changes, the lookup table, management system, or cloud-based server can be updated to link the unique identifier of the IP KVM device to the new connection information.

[0024] Figure 5 1 is a flow chart illustrating an example of a method 500 for connecting a client device (e.g., client device 406) to a host device (e.g., host device 202) via a network (e.g., network 204). At 502, method 500 includes inputting, via the client device (e.g., via input device 414), a unique identifier of a selected IP KVM device communicatively coupled to the host device. At 504, method 500 includes querying, via the client device, a plurality of IP KVM devices on the network to receive a unique identifier from each of the plurality of IP KVM devices. At 506, method 500 includes establishing a remote connection between the client device and the queried IP KVM device if the received unique identifier matches the unique identifier of the selected IP KVM device.

[0025] In one example, inputting the unique identifier of the selected IP KVM device includes scanning a quick response (QR) code on the selected IP KVM device via the client device. In another example, inputting the unique identifier of the selected IP KVM device includes entering the unique identifier displayed on the selected IP KVM device via the client device. In one example, each of the plurality of IP KVM devices may include a processor and a memory communicatively coupled to the processor, wherein the memory stores the unique identifier of the IP KVM device.

[0026] Although specific examples have been illustrated and described herein, various alternative and / or equivalent implementations may be substituted for the specific examples shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptation or variation of the specific examples discussed herein. Therefore, the present disclosure is intended to be limited only by the claims and their equivalents.

Claims

1. An Internet Protocol (IP) keyboard, video, and mouse KVM device, comprising: a universal serial bus (USB) port for communicatively coupling to a host device; a display port for communicatively coupling to a host device; a network port for communicatively coupling to a network; Bluetooth transceiver; a processor communicatively coupled to the USB port, the display port, the network port, and the Bluetooth transceiver; as well as a memory storing a unique identifier to be transmitted to the client device via Bluetooth in response to establishing a first connection between the client device and the IP KVM device, the unique identifier to be used by the client device to establish a second connection to the IP KVM device, wherein the first connection is a Bluetooth connection and the second connection is a remote connection different from the first connection; The processor is configured to encode a USB signal received from the host device through the USB port and a display signal received from the host device through the display port, and transmit the encoded USB signal and display signal to the client device via the network port through the second connection.

2. The IP KVM device according to claim 1, wherein the remote connection to the IP KVM device is established through a network. 3 . The IP KVM device of claim 1 , wherein the processor is configured to authenticate a user of the client device via Bluetooth prior to transmitting the unique identifier to the client device.

4. The IP KVM device according to claim 1, further comprising: Button for initiating a Bluetooth connection between the client device and the IP KVM device. 5 . The device of claim 1 , wherein the client device is used to access a management system to obtain connection information of the IP KVM device based on the unique identifier.

6. The device of claim 1, wherein the client device is configured to access a cloud-based server to obtain connection information of the IP KVM device based on the unique identifier.

7. The device of claim 1, wherein the client device is configured to access a lookup table to obtain connection information of the IP KVM device based on the unique identifier.

8. A method for connecting a client device to a host device via a network, the method comprising: in response to establishing a first connection between the client device and the IP KVM device, transmitting a unique identifier of the IP KVM device coupled to the host device to the client device via the first connection, the unique identifier being stored in a memory of the IP KVM device; the client device establishing a second connection to the IP KVM device using the unique identifier, wherein the first connection is a Bluetooth connection and the second connection is a remote connection different from the first connection; The IP KVM device encodes a USB signal received from a host device through a USB port of the IP KVM and a display signal received from a host device through a display port of the IP KVM using a processor of the IP KVM device, and transmits the encoded USB signal and display signal to a client device via a network port of the IP KVM through a second connection.

Images