JP2008533583A - Thin client blade modular apparatus, method and system - Google Patents

Abstract

  The present invention is removable to a common midplane and to one or more management modules for simulating a composite thin client operating on one or more power supplies and one or more computer networks A modular chassis is provided that includes a composite thin client blade that can be coupled to the chassis. The present invention builds a large computer lab environment with many thin client devices and / or many simulated users that are easily connected and managed to simulate a large computer infrastructure. Enable. Further, the patent shows how to achieve a combination of functions including testing and simulation of normal and abnormal operating scenarios in a complex server computing environment.

Description

  The present invention relates generally to composite thin client modular systems, and more particularly, but not exclusively, to thin client blade systems and architectures that allow for the testing of the functionality and load of computing environments using complex servers. .

  In the first year of personal computing, each personal computer (PC) workstation was operated as a stand-alone system, so testing with many PCs deployed was a single PC in terms of functionality, stability and reliability. Was typically limited to testing. As the organization's computer system becomes extremely dependent on networked and centralized servers, PCs become dependent on network and server resources for their normal operation. The typical computer device of a large mechanism has become even more complex and therefore even more difficult to predict, simulate and test.

  Today, large mechanisms include complex interaction of complex workstations that load data billing or resource computing and communication networks, designing and analyzing the entire system as well as each PC workstation. And face the challenge of maintaining. This is particularly critical to ensure that failures or overloads in any segment do not worsen to catastrophic system failures.

  Until now, the common practice in large mechanisms has been to build a small model of the mechanism's computer system from real components (such as a PC server), and the actual user performing the tasks normally performed by each PC workstation The mechanism system was simulated by operating the. Because this approach is relatively expensive, only a small portion of the organization's system could be simulated.

  The typical large mechanism integrated computer lab described above will include many PC workstations. Each connected to a monitor or keyboard video mouse switch (KVM), network switch, multiple servers and storage devices. In this non-product environment, the mechanism can test different operating scenarios, test new software and hardware deployments, and perform system scaling, training and inspection without interfering with the operating system (production) on the mechanism. Enable.

The main disadvantages in such a simulated environment are:
Expensive building blocks-high capital expenditures in the construction of test systems due to the large floor space required for actual PCs and laboratories.
High maintenance costs due to the complex wiring required for the network and multiple channel KVM. In addition, decentralized management of the environment requires a large workforce for management and troubleshooting.
• Lack of scalability on the workstation side-it was impractical to deploy hundreds of PC workstations that would require very large spaces, peripherals and cabling.
Long-term setup and lack of flexibility-Each setup or change may take days or weeks to build and verify by doing all cabling.

  Another common choice available today is to use many virtual machines running on a small number of physical computers to rebuild the mechanism. This selection may be more cost effective than the previous selection, but the level of accuracy achieved with such systems for workstation simulation is the level required by most mechanisms. Far from. It is difficult to predict the operation of a large-scale distributed system without using actual hardware such as a workstation. In addition, virtual machines can provide the best solution for other segments in simulated systems such as servers and storage devices.

  Today, more and more PC workstations with server consolidation and computing trends with servers are operated only by clients and many are replaced by thin clients. This poses a more powerful challenge to large mechanisms for ensuring reliable and economical system operation. With the thin client trend, an inherent risk of centralized failure has emerged that can partially or completely paralyze the organization's information technology (IT) system. Scenarios such as security attacks, viruses, data center failures, network failures and sudden loads can easily cause repeated domino effects and therefore become very difficult to predict, avoid and recover.

  Thin client technology, on the other hand, has given them a unique opportunity for large mechanisms that can maintain efficient placement and large general laboratories with small space and low cost ownership. Furthermore, the use of thin client workstations can be an efficient tool for simulating PC workstations as well.

  In the case of thin client workstations, there is an option to use multiple virtual (simulated) clients running on a single platform as a simulated user workstation, but the thin client has a completely different architecture The simulation will be more unreliable on a PC workstation because it is difficult to simulate in current virtual machines.

  Practical large-scale users with actual workstation hardware and software used in the target production environment to overcome these risks and to establish and authorize a secure architecture for large thin client deployments There is a need to develop tools and methods that enable workstation simulation.

  Therefore, there is a need for a complex, thin client system that is compact, dense, rapidly deployable and highly managed with centralized management, practicality and unlimited scalability. Thin client blade systems will be provided with the essential components of information technology laboratory and data center operations to test and train different operation scenarios.

General backgrounds related to the field of thin client modular array systems can be found in the following publications:
1. "Module server architecture with Ethernet (R) through path across backplane utilizing integrated Ethernet (R) switch module"-US Patent Application No. 2002/0124114, Bottom, David A et al., 2002 9 May 5th.
2. “Blade Server Module”, US Pat. No. 6,665,179, Chou, December 16, 2003.
3. “Server blade chassis midplane printed circuit board with cover”, US Design No. D493,152, Baker et al., July 20, 2004.
4). “Server Blade Chassis with Airflow Bypass Damper Guaranteed by Blade Removal”, US Pat. No. 6,771,499, Crippen et al., August 3, 2004.
5. “Devices and Systems for Functional Expansion of Blades”, US Pat. No. 6,819,567, Baker et al., November 16, 2004.
6). “Testing System for Testing Components of Open Architecture Modular Computing System” US Patent Application No. 2004/0230866, Yates, Kirk et al., November 18, 2004.
7). “HP Integrated Client Infrastructure (CCI)” Support for Reduction of Corporate IT Costs ”HP5982-1133 EN White Paper, Second Revised Edition, November 2003.
US Patent Application No. 2002/0124114 US Pat. No. 6,665,179 US Design No. D493,152 US Pat. No. 6,771,499 US Pat. No. 6,819,567 US Patent Application No. 2004/0230866 "HP Consolidated Client Infrastructure (CCI)-Help reduction enterprise PR IT costs", HP5982-1133EN white paper, second revised edition, November 2003

  Accordingly, it is a primary object of the present invention to overcome the disadvantages of the prior art and to provide a modular thin client device, system and method using a modular thin client module.

  The present invention provides a common midplane or backplane as well as one or more management modules for enabling composite thin clients that operate on one or more power supplies and one or more computer networks. A modular chassis including a releasably connectable composite thin client blade is provided. The present invention builds a large computer lab environment with many thin client workstations and / or many simulated users that are easily connected and managed to simulate a large computer infrastructure. Make it possible. Connecting internal KVM functionality and options allows a single administrative user to easily monitor and manage multiple thin client workstations remotely and locally with a set of keyboard, mouse and display. enable.

  Furthermore, a general method for accomplishing a combination of functions including testing and simulation of normal and abnormal operating scenarios in a computing environment using complex servers is presented in the present invention.

  In another embodiment of the present invention, a modular thin client blade system is disclosed. The system is: a modular chassis with composite bays that can accept thin client blade module inserts; at least one midplane or backplane with connectors for each bay, common power bus, and management bus that interconnects the blade bays A plurality of thin client blades removably connectable to the midplane or backplane via a compatible mating connector comprising the midplane or backplane connector; each to a network via a network switch or hub; At least one network interface connecting at least one thin client blade.

  In some embodiments, the system in a more desirable embodiment includes a management module for centrally monitoring, configuring and controlling each of the plurality of thin client blade modules.

  In some embodiments, the KVM module can chain multiple similar systems to allow centralized management of more thin client blades than can be inserted into one of the chassis. become.

  In some preferred embodiments of the present invention, a thin client blade chassis configured for receiving a plurality of pluggable thin client blade modules is provided. The chassis comprises: a modular chassis with a composite bay capable of receiving thin client blade module inserts; at least one midplane or backplane with connectors for each bay, a common power bus and a management bus that interconnects the blade bays A KVM module capable of connecting a user keyboard, mouse and display to a selectable one of the thin client blade modules; and at least one power supply module for providing power to the modular thin client blade.

  In some other desirable embodiments of the present invention, a pluggable thin client blade module device is provided. The client blade module is configured to: interface with the midplane or backplane connector to receive power from the midplane or backplane connector and exchange information with the midplane or backplane A combination connector; a LAN transceiver: the mating connector, a LAN connector and a LAN controller; a processor for processing the information; a volatile memory for storing information and program instructions used by the processor; used by the processor Non-volatile memory for storing program instructions; and a bus, including: a LAN controller, non-volatile memory, volatile memory, and one connected to the processor.

  In some embodiments of the invention, an insertable management module is provided. The management module: configured to interface with a midplane or backplane connector for receiving power from the midplane or backplane connector and exchanging information with the midplane or backplane A combination connector configured to interface with a midplane connector for receiving power from the backplane connector and exchanging information with the midplane or backplane; a LAN transceiver: Mating connector and LAN controller; processor for processing the information; volatile memory for storing information and program instructions used by the processor; Non-volatile memory for storing program instructions used; I / O controller capable of exchanging information with user input / output devices; Video controller capable of generating video signals; and bus: Includes I / O controller, video controller, LAN controller, non-volatile memory, volatile memory and those connected to the processor.

  In yet another preferred embodiment of the present invention, a centrally managed multi-thin client system method is provided for building on a large scale. The method includes: providing a plurality of thin client blade chassis each configured to receive a plurality of insertable thin client blade modules, comprising: a composite bay capable of receiving a thin client blade module insert Modular chassis; at least one midplane or backplane with connectors for each bay, common power bus and management bus interconnecting the blade bays; one selectable user keyboard, mouse for the thin client blade module And a KVM module to which a display can be connected; including chaining each of the KVM modules of at least two of the plurality of thin client blade chassis.

  In an additional preferred embodiment of the present invention, a method for simulating a multi-thin client system is provided. The method includes: a plurality of thin client blade chassis each configured to accept a plurality of insertable thin client blades; each of the plurality of thin client blade chassis including a plurality of thin client blades and Inserting a single management module; connecting each of the plurality of thin client blades to a network switch; and connecting the network switch to a server.

  Further features and advantages of the present invention will become apparent from the drawings and specification contained herein.

  The following detailed description is the best mode presently contemplated for carrying out the invention. This description is not meant to be limiting, but is made merely to illustrate the general principles in accordance with the present invention. The scope of the invention is best defined by the appended claims.

  The foregoing and other objects, features and advantages of the present invention will become apparent from the following more specific description of exemplary embodiments of the invention, as illustrated in the accompanying drawings:

  In FIG. 1, a front view of an embodiment of a thin client modular blade system 100 is noted. The chassis rack mounting hole 10 is used to fix the chassis 110 to a standard rack. Typically, a standard 19-inch rack shape is used to allow vertical build-up of a composite set of thin client modular blade systems 100 and network switches as needed. The chassis 110 is attached with a composite thin client blade module 40 and a single management module 42. The thin client blade module 40 is substantially the same, but typically the user can install up to 20 modules of the same type or mixed type. The user can also partially fill the chassis 110 depending on the availability of the module and the target system defined by the user. The management module 42 enables centralized management and monitoring of all modules. The structure of the chassis 110 enables a plurality of thin client blade modules 40 installed therein. The thin client blade module 40 may be available in multiple types. Multiple modular blade types may be flexibly installed in the same or different chassis to create multiple system features as needed.

  In FIG. 2a, a more detailed front view of an exemplary thin client blade module 40 according to a preferred embodiment of the present invention is referred to. The thin client blade module 40 is selectably fixed to the chassis 110 by the fixing tool 11. The fixture 11 may be a captive screw, a loose fastener or a screw.

  Optionally, the thin client blade module 40 is equipped with an indicator 12. The indicator 12 may be in the form of a light emitting diode (LED) or combination of LEDs that can generate colored light that indicates the current state of the thin client blade module. For example, a green signal may be used to indicate a normal operating state of the module, while a red signal may indicate a module failure.

  The LAN jack 13 is used to connect the module to an external network switch, preferably a shielded RJ-45 jack. External cabling is preferably used to connect the thin client blade module 40 to a network switch or hub that allows maximum flexibility in network selection and configuration.

  Two selectable LEDs 14 and 15 integrated into the LAN jack indicate the status of the LAN connection and activity, respectively. These lights provide users with quick and visible network status information for system installation, monitoring, and maintenance.

  The selectable analog video output jack 16 allows direct connection of a computer display to the thin client blade module 40.

  The selectable power-reset switch 17 is preferably a three position instantaneous switch with dual action-pushing it upwards alternatively turns the module on and off. Pushing it down causes a thin client restart and resets the module. Desirably, resetting and powering on may be controlled centrally via the management module 42 described in more detail in FIG.

  The selectable KVM module selected for indicator 19, preferably in the form of an LED, is an internal KVM module 44 in which one of a plurality of thin client blade modules is in chassis 110 (module 44 is shown in FIG. 4). Indicates which is currently selected. Preferably, the green LED 19 illuminates to indicate which of the multiple thin client blade modules has been selected remotely by the management module 42.

  The selectable push button 18 is a KVM manual override switch. When the KVM manual override switch 18 is pressed, the KVM module 44 in the chassis is instructed to select the particular thin client blade module for which the KVM manual override switch was pressed. This manual selection may override other selections previously made by the user via the management module controls. In this case, the indicator 19 selected as KVM shines green.

  The selectable ejector 20 provides module locking and ejection assistance. The ejector 20 may be equipped with a switch for notifying the management module of imminent module removal / installation. This may be required to enable the hot swap feature when a module is replaced while the system is powered on.

  Instead, the thin client blade module 40 is a headless thin client blade with at least a LAN connector 13 on its front panel while some or all of the other above-described elements are absent.

  Alternatively or additionally, module 40 includes additional elements on its front panel. For example, one or some: keyboard connector, mouse connector, universal serial bus (USB) connector, audio connector, additional indicator, etc.

  Referring now to FIG. 2b, a front view 41 of a thin client blade module with a digital video terminal (DVI) and a universal serial bus (USB) port according to another preferred embodiment of the present invention will be referred to.

  The thin client blade module 41 is selectably fixed to the chassis 110 by the fixing tool 11. The fixture may be a captive screw, a loose fastener or a screw.

  The selectable client blade module 41 is equipped with an indicator 12 so that it can be selected. The selectable indicator 12 may be in the form of a light emitting diode (LED) or a combination of LEDs that can generate light indicative of the status of the modular blade. For example, a green signal indicates a normal operating state of the module, while a red signal indicates a module failure.

  The LAN jack 13 is used to connect the module to an external network switch, preferably a shielded RJ-45 jack.

  Two selectable LEDs 14 and 15 integrated into the LAN jack indicate the status of the LAN connection and activity, respectively.

  A selectable digital video (DVI) output jack 116 allows direct connection of a digital computer display to the module. Utilizing the DVI output jack 116 allows more flexibility than utilizing analog video output. For example, the display monitor may be placed at a greater distance from the blade module. To support older analog displays as well, DVI may be implemented using only digital signals or a combination of digital and analog outputs.

  A selectable USB port connector 117 allows direct connection of external USB peripherals such as a keyboard and mouse to the thin client blade module 41.

  The selectable power-reset switch 17 is preferably a three position instantaneous switch with dual action-pushing it upwards alternatively turns the module on and off. Pushing it down resets the module. Desirably, resetting and powering on may be controlled centrally via the management module 42 described in more detail in FIG.

  The selectable KVM selected for the indicator 19, preferably in the form of an LED, is selected by the internal KVM module 44 (module 44 is shown in FIG. 4), which of the plurality of blades is in the chassis 110. Indicates whether or not Desirably, the green LED of the indicator 19 illuminates to indicate which of the plurality of thin client blade modules has been selected remotely by the management module 42.

  The selectable push button 18 is a KVM manual override switch. When the KVM manual override switch 18 is depressed, the KVM module 44 in the chassis 110 is instructed to select the thin client blade module for which the KVM manual override switch has been depressed. In this case, the indicator 19 selected as KVM shines green.

  The selectable ejector 20 provides module locking and ejection assistance. The ejector 20 may be provided with a switch for notifying the management module of removal / installation of the module. This may be required to enable the hot swap feature when a module is replaced while the system is powered on.

  In FIG. 3, a detailed view of the management module 42 front panel is shown and will be referred to. In this front view of an exemplary embodiment of the present invention, selectable fixture 11 and selectable ejector 20 are the same as in the previous drawings.

  The selectable main power indicator 22, preferably an LED, is a power indicator for the entire system. For example, when green glows, power is available for the chassis and all modules.

  The main power switch 23, preferably a fixed toggle switch, was used for power on and off instead of the system chassis and all modules. This switch may be connected to a power source to power on and off logic commands.

  The selectable display 24 is provided with a readable alphanumeric display showing the system status code and an arbitrarily selected module number. Desirably, the display 24 is a small liquid crystal display (LCD) or a segmented LED display.

  Selectable front and rear keys 25 and 24 are used to allow the user to manually select a particular thin client blade module, even in the chassis or even in a different chassis with a chaining option.

  The analog video output connector 30 is output for a display internally connected to the KVM module 44 (shown in FIG. 4). By selecting the appropriate module, the user may monitor each one of the operating modules 40 or 41 via a single video output port 30. The USB ports 32 are preferably two USB ports for connecting a user's mouse and keyboard. These ports are connected internally to the KVM module 44 so that they can interact with each one of the thin client blade modules 40.

  In FIG. 4, a block diagram of an embodiment of the present invention showing the connections between the various components assembled in modular system 175 is shown and will be referred to. The main component of the system 175 is a chassis 110 with its insert compartment 111 that holds a plurality of thin client blade modules 40, a single management module 42, a network switch 120 and a server 133.

  The composite thin client module 40 or 41 is connected to the midplane internal bus 60 behind the insert compartment 111 via a mating connector. The thin client blade module 40 or 41 is supplied with power by the power supply 26 via the midplane internal bus 60. The thin client blade module 40 receives (and selectively transmits) certain control commands between the midplane internal buses 60. The bus 60 receives the video signal of the module 40 or 41. The midplane bus 60 transmits and receives various I / O control signals of the thin client blade module 40 or 41 such as USB, serial, system management bus, and audio. The midplane internal bus 60 is also connected to a single management module 42.

  As previously mentioned herein, the KVM module 44 is preferably installed in the chassis 110. Alternatively, the KVM module 44 may be installed outside the chassis or even remotely. The KVM module 44 is connected to the midplane internal bus 60 via a link 78 that allows it to send and receive various thin client module signals. These signals may include USB, video, audio and various control signals selected by the KVM module 44. The selected thin client module signal is connected to the KVM output bus 85.

  The KVM module 44 serves as a logical selector switch between a plurality of input / output signals connected to the thin client module 40 and a set of the same signals that allow connection of a single user display, keyboard and mouse. The KVM output bus 85 also sends the selected module signal to the management module 42 via the midplane internal bus 60 and to the KVM selectable through the IP module 46 and the KVM chain module 45. The KVM output signal that passed through the management module 42 was connected to the video connector 30 and the USB connector 32 on the front panel of the management module 42 (shown in FIG. 3).

  Optionally, the management module 42 uses a unique connector and serves as the end for all bus signals. In this embodiment, the management module 42 may be inserted at a specified position on the chassis 110. It is also connected to a KVM chain module 45 that allows cascading of several modular blade rack systems 175. Chaining between multiple chassis allows control and monitoring of multiple thin client blade modules without the need for the user to physically connect and disconnect their display, keyboard and mouse. Chaining can be done by special cables connecting behind each system chassis specifically for this purpose. These cables can carry analog and digital signals between the two chassis. Multiple cables, such as the multiple chassis chaining, can be used to build a chained structure of multiple chassis managed through a single management module. Another alternative for managing a complex system via a single console is the special chaining-in connector 88 and chaining-out via the LAN if the KVM is installed through the IP option or at the rear of the chassis 89 through the connector. These chaining connectors are used to cascade a large number of chassis to form a large structure managed by a single management module that becomes the master module.

  A selectable KVM through the IP module 46 provides remote access and control to the system via a standard web browser. This module includes a computer that runs a dedicated web server service that communicates video, audio, mouse, and keyboard interactions via standard web pages. A KVM LAN interface 27 through the IP module 46 connects the module to a network switch and an appropriate network. This allows other computers or thin clients in the network to connect to the system and manage its functions.

  A single or composite power supply 26 is provided with a low voltage DC power supply via a midplane internal bus 60 to supply power to various system modules. The power supply 26 is typically connected to a main power input or 48 DC power supply. Field effect transistor power switching may be used to assist module hot swap and remote power management via power switching.

  Optionally, a cooling module 76 may be added to provide a forced flow of cooling air through the system. In most cases, this module will not be implemented because thin clients and especially devices using reduced instruction set computers (RISC) are relatively low power devices.

  Preferably, the external or internal network switch 120 connects each one of the thin client blade modules 40 or 41 to a network using the LAN line 102 connected to the LAN connector 13 in each one of the thin client blade modules (LAN Connector 13 is shown in FIGS. 2a and 2b).

  Alternatively, the switch 120 may be integrated within the chassis. Optionally, midplane internal bus 60 may include a LAN connector that eliminates the need for line 102 and connector 13.

The switch 120 may be unmanaged or may be a managed switch that allows special programming and configuration, preferably independent of each port and attached module. Another advantage of a managed switch is its ability to define a virtual local area network for each port. Internal or external programmable bandwidth, limited features may be added to enable various local area network (LAN) and wide area network (WAN) simulations.

  The switch 120 is preferably a rack mount network switch and is preferably installed above or below the chassis 110 so as to reduce the length of the cable 102.

  The server 133 is connected to the switch 120 via the LAN cable 108. The server 133 may be a rack mount server or a standard server located near or far from the rack.

  In FIG. 5, a more detailed view of various interconnections between additional thin client blade modules 40 or 41 and the system midplane internal bus 60 is shown and referred to. These interconnections typically pass through a module connector 80a on the thin client blade module that mates with a midplane connector 80b on the midplane internal bus 60.

  Digital or analog video output 182 passes from thin client blade module 40 or 41 to midplane internal bus 60. It is then switched by the internal KVM module 44 to allow a single display device to selectively connect to any selectable blade module.

  A line 183 is a USB port for connecting the thin client blade module 40 or 41 to the midplane internal bus 60. From the midplane internal bus, the USB is wired to the KVM module through the front panel connector attached to the management module panel 42 or through other (chained) systems that are finally terminated with a USB connector. Switch to a single USB port connected to the user's mouse and keyboard.

  There is a control signal 184 that interconnects the various management functions in the management module with each thin client blade module 40. These signals are used to detect module modes and settings, send power and status information, and enable various switching functions such as module selection, reset and power switching.

  Power to the thin client blade module passes through the power plane 185. This is a high current wire that is typically routed through durable connector contacts to reduce voltage drops and power supply noise. Certain power pins in connectors 80a and 80b may be reduced to ensure that power to the module is last connected and disconnected first when the module is installed and removed under chassis power. .

  The audio input / output signal 186 passes through the midplane internal bus 60 and from there the internal KVM module 44 is wired.

  In FIG. 6, a high level system diagram is now referred to-showing the interconnection of a thin client modular blade system, according to a preferred embodiment of the present invention. One or more thin client blade modular systems 100 include one or more network switches 120 via short LAN cables 102 that bridge between each module LAN port 13 and a respective port in the network switch. Connected to.

  The management module 42 may be connected to a network switch to enable remote management over IP and remote KVM functionality.

  Uplink port 106 in network switch 120 connects to a LAN cable or fiber connection 108 to server 133 to create a complete server computing environment. The server 133 may be a physical server or a composite virtual server as necessary. This basic system may easily scale to more thin client modular blade systems, additional LAN and WAN devices and simulators, and complex servers and server blades and storage equipment.

  Using the present invention, it is relatively simple to build and manage a large number of thin clients. For example, a standard 42U rack may be fitted with a 12x3U thin client blade modular system to create a 240 thin client system. In this arrangement, each thin client modular blade chassis is surrounded by up to 20 thin client blade modules, and two similar racks share one 1U 48 port managing the network switch. Higher density chassis can be built in the same way as enabling more thin client blades in a smaller space.

  In FIG. 7, a high level system diagram illustrating the preferred embodiment thin client blade modular system 141 is depicted and referred to. One network switch 120 is sandwiched between the two chassis 110. When fully occupied, each chassis 110 includes 20 thin client blade modules 40 or 41 and one management module 42. A short LAN cable 102 connects to each LAN port 13 of the thin client blade module 40 or 41 to the network switch 120.

  Uplink port 106 in network switch 120 is connected to a LAN cable or fiber connection 108 to server 133 to create a complete server computing environment. Multiple systems 141 may be constructed and provided by a single or composite server 133.

  In FIG. 8, a block diagram 200 of a thin client blade module according to a preferred embodiment of the present invention is depicted and referred to. This figure shows a block diagram of a typical computing device as depicted in FIG.

  The thin client blade system 200 is a data processing electronic system capable of performing a thin client or simulated PC workstation function comprising one or more of the following components.

  The processor 201 processes a storage program and data, a peripheral device, and a network that are input as necessary by a user or a simulated user. The processors 201 are preferably selected from reduced instruction computer (RISC) available for their lower power consumption and low heat generation. Instead, it simulates a complex instruction set computer (CISC), security and encryption engine, digital signal processor (DSP) or any other type or combination of digital processing equipment with sufficient processing power It may be used to implement a device structure similar to the actual targeted thin client device. The processor 201 may include on-die high speed cache memory or external cache or a combination of the two.

  Memory controller / bridge 215 interfaces to processor 201 with volatile memory 216 and bus 218. This functionality and others may be integrated into the processor 201 or installed separately on different chips or chip sets. Volatile memory 216 is used by processor 201 to store temporary data as needed. The memory 216 may be a RAM type, SDRAM, DDRAM or other type of volatile memory.

  The internal bus 218 connects various parts of the thin client blade module and may be a single or composite bus, a 16, 32 or 64 bit PCI, or other bus type. If a composite bus is implemented, a bus bridge module may be added to interface and operate different buses.

  A non-volatile memory 217 connected to the bus 218 permanently stores data, programs and settings required for thin client blade module operation.

  A selectable audio controller 219 such as an AC-97 CODEC is connected to the selectable audio connector on the bus 218 and the front panel of the thin client blade module 40. The audio controller 219 is used for conversion from an analog signal to a digital stream and vice versa. Digital streams between audio controllers may be available directly on a dedicated CODEC bus such as the internal bus 218 or AC link. A dedicated bridge or glue logic may be implemented to interface between the bus 218 and the audio controller 219. In addition, the module may include various analog stages such as mixers, switches, attenuators, filters, amplifiers and the like. In addition, this module may include additional features and enhancements to support improved sound output for home theater and multimedia applications. The audio circuit may be a single channel (mono), dual channel (stereo) or more to enhance the multimedia experience. Audio input / output may be connected via link 244 to midplane connector 80a to enable the audio selection function in KVM module 44 shown in FIG.

  The I / O controller 220 connects to the bus 218 on one side and the link 239 on the other side to the front panel of the midplane connector 80b and the I / O connector on the appropriate I / O bus. The controller 220 enables direct connection to standard peripheral devices via standard ports such as USB, PS / 2, serial, parallel, IEEE 1394, etc. on the module front panel 40 or indirectly via KVM. Used to enable connection of switch-type peripheral devices. The controller 220 may be provided with a switch type power source for supplying power to an external peripheral device.

  The video controller 221 is connected from one side to the bus 218 and to the video connector on the front panel of the thin client blade module 40 and to the midplane connector 218 via the link 228 on the opposite side. It is used to move an external analog or digital monitor directly or indirectly via KVM. Video controller 221 may include internal video memory, external video memory, or it may share volatile memory 216 with processor 201 in a unified memory architecture (UMA) structure.

  A local area network controller or media access controller (MAC) 222 connected to the bus 218 is used to interface a thin client blade module with a network switch or hub via a LAN transceiver (physical layer module) 224. .

  Connectors and ports installed on the front panel of the thin client blade module 40 are used for direct connection of various external peripheral devices to the module without having to go through the KVM module. This may be useful for troubleshooting or to allow continuous monitoring of one or more blade modules of particular interest to the user. These connectors connect various ports such as audio controller 219, I / O controller 220 and video controller 221. The front panel may include several switches and indicator lights to allow direct control and monitoring of the blade module.

  The local area network transceiver 224 (physical layer module) interfaces between the LAN controller (MAC) 222 and a LAN jack installed on the front panel of the thin client blade module 40. It is also selectively connected to midplane connector 80b via link 224 to allow implementation of an internal network switch. The transceiver 224 may include individual magnetics or magnetics integrated with a LAN jack. The availability of a LAN jack on the blade module front panel 40 is particularly beneficial to allow the user to easily connect and monitor that LAN connection of each blade module. In this design, thin client blade modules on the same chassis may be connected to different network switches, routers, hubs, or networks. The LAN transceiver 224 may be connected to the local area network controller 222 by a media independent interface (mill) bus or by other interconnection buses. The local area network 224 transceiver may support 100BASE-TX, 100BASEFX, 10BASE-T and Giga LAN or other LAN protocols as required.

  The power supply 226 uses the power available on the midplane bus via the midplane connector 80b and link 225 to convert that power to the appropriate voltage output 227 required by the different thin client module circuits. The power supply module 226 may include a timing circuit in order to supply power to another continuous circuit. It may include the generation of a reset signal to allow proper initial detection and power outage detection.

  The midplane connector 80b may be connected to the same selectable non-volatile memory module 223. This memory module may be used to store a specific thin client module model, serial number, MAC address and various module settings and configurations. If a module is inserted or if power is available in the chassis, this information may be read by the management module to allow better module management functions.

  The preferred thin client blade module embodiments described herein may execute a local operating system, such as Microsoft Windows® CE, Linux, or other compatible embedded operating system. If the implemented hardware is compatible with standard x86 or limited size x86, it will use a more common x86 operating system such as Microsoft Windows XP or XP. It can also be executed. The operating system can execute multiple local programs that allow connection to a remote server. These programs may include a Citrix server, a Citrix ICA client for communicating with a Microsoft Terminal Services RDP client that supports a Remote Windows server, and various local terminal emulations that communicate directly with legacy systems. Execution of such a client allows the thin client computing device to execute a session application running on a remote server.

  In addition, the thin client computing device may execute multiple independent local applications such as web browsers, multimedia players, and dedicated user applications.

  Further, the thin client computing device may include a remote administrator. These actors enable a mechanism for the mechanism to remotely manage device and user settings. It may enable centralized software deployment and user authentication and security monitoring.

  In addition, multiple load simulation local and remote programs can be run on each thin client blade module to allow realistic simulation of users with different load profiles.

  Optionally, the system 200 further includes a memory device 233 that is installed in each thin client blade module 40 and that provides access to the management module via a bus that identifies the type model and unique features of that module.

  In FIG. 9, a block diagram of a management module 300 according to a preferred embodiment of the present invention is shown and will be referred to.

  The structure of the management module 300 may be similar to the thin client blade module described in previous FIG. 8, or it may be a simplified microcontroller design with reduced functionality. A module is composed of one or more of each of the following components:

  The processor 201 processes a storage program and data, a peripheral device, and a network input by a user as necessary. The processors 201 are preferably selected from reduced instruction computer (RISC) available for their lower power consumption and low heat generation. Alternatively, a complex instruction set computer (CISC), security and encryption engine, digital signal processor (DSP) or any other type or combination of digital processing devices with sufficient processing capability may be used. The processor 201 may include on-die high speed cache memory or two external caches or a combination of the two. Further, the processor 201 may be a simple low cost microcontroller with integrated volatile and non-volatile memory.

  Memory controller / bridge 215 interfaces to processor 201 with volatile memory 216 and bus 218. This functionality and others may be integrated into the processor 201 or installed separately on different chips or chip sets. Volatile memory 216 is used by processor 201 to store temporary data as needed. The memory 216 may be a RAM type, SDRAM, DDRAM, or other type of volatile memory.

  The internal bus 218 connects various parts of the thin client blade module and may be a single or composite bus, 16, 32 or 64 bit PCI or other bus type. If a composite bus is implemented, a bus bridge module may be added to interface and operate different buses.

  A non-volatile memory 217 connected to the bus 218 permanently stores settings required for data, program and management module operations. The management program and the various state machines required are loaded into this memory from a connected removable media or centralized management system.

  The I / O controller 220 connects to the bus 218 on one side and various control and user interface functions on the module front panel. This includes, but is not limited to, moving the panel display 24 shown in FIG. 3 above and the switches 23, 25 and 26 here. The panel display 24 may be a seven segment, alphanumeric, dot matrix or fully graphical display if desired. The switch may include various function keys and switches to allow interaction with the user.

  A selectable on-screen display (OSD) / video controller module 321 is connected to the video signal passed from one side to the bus 218 and on the other side via the management module. It is used to allow the management module to add alphanumeric text and symbols on the visible video image. The provided text may include identification and status selected for the thin client blade module, or any other system status and configuration information. The video signal generated by this module is automatically synchronized with a selectable on-screen display (OSD) / video controller module 321 may include internal video memory, external video memory, or it may be unified Volatile memory 216 with processor 201 in a memory architecture (UMA) structure may be shared. A local area network controller or media access controller (MAC) 222 connected to the bus 218 is used to interface a management module comprising a network switch or hub 120 via a LAN transceiver (physical layer module) 224.

  The video connector 30 installed on the module front panel 327 combines the KVM output connected by the link 336 and midplane connector 80b by the OSD / video processor 321 with the selectable OSD / video generated in the management module. The USB connector 32 installed on the front panel 327 is connected to the KVM module via the link 338 and the midplane connector 80b. This port allows the user to connect to the keyboard and mouse of the KVM port for managing the system.

  A selectable local area network transceiver 224 (physical layer module) interfaces between the LAN controller (MAC) 222 and a LAN jack installed on the front panel of the thin client blade module 40. It is also selectively connected to midplane connector 80b via link 224 to allow implementation of an internal network switch. The transceiver 224 may include a separate magnetic or non-magnetic direct connection implementation to the internal switch physical layer circuitry.

  The LAN transceiver 224 may be connected to the local area network controller 222 by a media independent interface (mill) bus or by other interconnection buses. The local area network 224 transceiver may support 100BASE-TX, 100BASEFX, 10BASE-T and Giga LAN or other LAN protocols as required.

  The power supply 226 uses the power available on the midplane bus via the midplane connector 80b and link 225 to convert that power to the appropriate voltage output 227 required by the different management module circuits. The power supply module 226 may include a timing circuit in order to supply power to another continuous circuit. It may include the generation of a reset signal to allow proper initial detection and power outage detection.

  The midplane connector 80b may be connected to the same selectable non-volatile memory module 223. This memory module may be used to store a specific management module model, serial number, MAC address and various module settings and configurations.

  The management module can be operated directly in override mode with push buttons 18 located on each thin client blade module panel (shown in FIG. 2a). This allows a user to quickly monitor and control a specific module when needed.

  Optionally, the management module 42 further includes accessing a memory device 233 installed in each management module 42 and a server that clearly identifies the module's type model and unique features.

  In FIG. 10, further details of the KVM module 44 are represented and referred to. For clarity, only a minimum number of signals and ports are shown. In addition, various mechanical switches can be used including digital logic, analog switches, relays, etc., but mechanical switches are used in the figures.

  The signal 400 is a thin client blade module # 1 video output signal wired via the midplane internal bus 60. 401 similar to the signal is the video signal thin client blade module # 2. The switch 408 serves as a selector switch that allows the selection of just a single video source based on a selection command generated by the KVM through the management module or IP module and passed through the midplane internal bus 60 and link 396. A single video output signal 409 is provided connected to a single connected user display.

  Similarly, switch 418 selects between different USB ports 410, 411 and 412 of different thin client blade modules. The port selected by the switch is provided with a single output 419. Additional switches may be added here to activate simultaneous switching from many sources and additional types of signals such as audio and serial ports. When KVM over IP is implemented, KVM control 396 and KVM outputs 409, 419, 429 are connected to KVM over IP modules.

  The selectable hotkey module 240 can detect specific keyboard key combinations to toggle between the different thin client blade modules shown. This is done by connecting the USB port of KVM 419, detecting preprogrammed hotkeys, and generating an appropriate switching command in KVM control signal 396.

  Another optional module in the KVM is the video overlay processor 246. This module can be combined with a single display that the video image generated by the composite thin client module displayed to the user. By connecting to different video sources 400, 401, 402, etc., the module captures video signals from all available sources. The module then remeasures the selected video inputs and synchronizes them for attachment to a large collage-type image available as a single video output 455.

  The thin client blades 40 or 41 may have different hardware structures or configurations. For example, they may differ in storage capacity, computing speed, processor type, selectable connectors, and the like.

  The modular system may operate with a partially occupied chassis. The blade may be missing or may be replaced with a blank cover. The blades may be attached independently or removed. In some embodiments of the invention, the blades may be removed or inserted while other blades are operating (hot swapping).

  In general, each thin client blade 40 or 41 may execute different software that is essentially independent of the other blades.

  To create a mechanism simulation, a special program is installed on at least one “typical user” PC or thin client in the mechanism. The program monitors in detail everything the user has done on the computer. Information about the use of the user's computer is stored with a time stamp.

  After data has been collected for a certain period of time, the same resource load (i.e. if the user types an email with a specific text and sends it to a specific address, this action will take the text and email address Can be replicated by replacing any text and any text address) and the data can be analyzed to produce any processing.

  The combination of hours and several users will create a weekly working time “script” that statistically characterizes the organization's group of employees. For example, a typical work of a bank teller. Some types of use may therefore be monitored and simulated creating an accurate representation of the mechanism workload and work balance.

  For testing, each blade "plays" one or more of these scripts to create a global image that statistically represents the overall mechanism activity profile throughout its business hours. By simulating a user.

  It should be noted that each blade will faithfully represent the user using a thin client station. Overall, however, each blade that represents a user performing a work session to test the capabilities of the server, communication link, and mechanism, and such blade may be a thin client station, PC, or server, automatic A function operated by a person other than a human such as a machine or a system composed of several computers or computer systems may be simulated.

    Although the present invention has been described with respect to certain exemplary embodiments, various modifications will be readily apparent and may be readily accomplished by those skilled in the art without departing from the spirit and scope of the above teachings. .

    Features and / or steps described with respect to one embodiment may be used with other embodiments, and all embodiments of the invention are shown in a particular figure or one of the embodiments. It should be understood that not all of the features and / or steps described with respect to FIG. The various embodiments described will occur to those skilled in the art.

  Some of the embodiments described above may describe the best mode contemplated by the inventor, and thus are not necessary for the present invention and the examples shown in the examples, structures, acts or structures and Note that details of the action may also be included. The structures and acts described herein may be substituted by equivalents that accomplish the same function, as is known in the art, even if the structures or acts are different. The terms “comprise”, “include” and their equivalents as used herein mean “including but not necessarily limited to”.

  Exemplary embodiments of the invention are described in the following sections with reference to the drawings. The same reference numbers are used to indicate the same or related features on different drawings. The drawings are not drawn to scale overall.

  For a better understanding of the present invention, reference may be made to the preferred embodiments of the present invention shown in the accompanying drawings. :

FIG. 1 shows a front view of a modular thin client blade system comprising an assembled composite thin client blade module and a single management module according to a preferred embodiment of the present invention. FIG. 2a shows a front view of a thin client blade module according to a preferred embodiment of the present invention. FIG. 2b shows the front panel of a thin client blade module with a digital video terminal (DVI) and a universal serial bus (USB) port according to another embodiment of the present invention. FIG. 3 shows a front view of a management module according to a preferred embodiment of the present invention. FIG. 4 shows a block diagram of a thin client blade system according to a preferred embodiment of the present invention. FIG. 5 shows a schematic diagram of a thin client blade module interface to a midplane internal bus according to a preferred embodiment of the present invention. FIG. 6 presents the interconnection of network switches and servers to a thin client blade system according to a preferred embodiment of the present invention. FIG. 7 illustrates a preferred embodiment of a thin client blade system. FIG. 8 depicts a block diagram of a single thin client blade module according to a preferred embodiment of the present invention. FIG. 9 shows a block diagram of a management module according to a preferred embodiment of the present invention. FIG. 10 represents a more detailed description of the KVM module and its external connections according to an embodiment of the present invention.

Claims (28)

A modular thin client blade system,
At least one backplane comprising a connector, a common power bus and a management bus;
A plurality of thin client blade modules removably connectable to the at least one backplane via mating connectors compatible with the connectors;
A modular chassis comprising a composite bay in which each said connector is located in one of said composite bays and capable of receiving said plurality of thin client blade modules;
A modular thin client blade system including at least one network interface suitable for connecting each of the plurality of thin client blade modules to a network via a network switch.   The system of claim 1, further comprising a KVM module capable of connecting a user keyboard, mouse and display to the selectable plurality of thin client blade modules.   The system of claim 2, wherein the KVM module is suitable for chaining to a plurality of substantially similar systems to allow for central management of one or more of the chassis.   The system of claim 2, wherein the KVM module is suitable for recognizing preprogrammed user keyboard input to trigger a specific KVM action.   The system of claim 2, wherein the KVM module is suitable for combining a composite video image from the plurality of thin client blade modules with a single displayed image.   The KVM module is suitable for connecting to a remote or local site using a web server for delivering video and receiving keyboard and mouse commands via a web browser. System.   The system of claim 2, wherein the KVM module is capable of overlaying alphanumeric data and system status on a visible video display.   The system of claim 1, further comprising at least one power supply module removably connectable to the chassis to provide power to the plurality of thin client blade modules.   The system of claim 1, further comprising a management module for centrally monitoring, configuring and controlling each of the plurality of thin client blade modules.   The system of claim 1, wherein at least one of the plurality of thin client blade modules is made with a RISC architecture.   The system of claim 1, wherein the network switch is manageable to allow flexible network configuration and connectivity to each of the plurality of thin client blade modules in the system.   The system of claim 1, wherein the network switch is suitable for limiting bandwidth and packet flow characteristics that allow different network implementations and simulations.   The system of claim 1, wherein one or more of the plurality of thin client blade modules are running local software that simulates a particular or typical user burden.   The system of claim 1, further comprising a cooling fan module coupled to the chassis to cool the system.   And further comprising accessing the management module via a non-volatile memory device installed in each one of the plurality of thin client blade modules and a bus that clearly identifies the module's type model and unique features. The system of claim 1. A thin client blade chassis configured to accept a plurality of insertable thin client blade modules,
A modular chassis with a composite bay capable of receiving an insertable thin client blade module;
At least one backplane comprising connectors for each said composite bay, a common power bus, and a management bus interconnecting said composite bays;
A KVM module suitable for connecting a user keyboard, mouse and display to one selectable thin client blade module;
A thin client blade chassis including at least one power supply module suitable for providing power to the insertable thin client blade module. An insertable thin client blade module device suitable for removably connecting to a backplane connector to establish an interface for receiving power from the backplane connector and exchanging information via the backplane connector Because
Combination connector suitable for connecting to backplane connector,
A LAN transceiver connected to the combination connector, to the LAN connector and to the LAN controller;
A processor for processing information;
Volatile memory for storing information and program instructions used by the processor;
A non-volatile memory for storing program instructions used by the processor;
An insertable thin client blade module device comprising a bus suitable for connecting the LAN controller, the non-volatile memory, the volatile memory and the processor.   The apparatus of claim 17, further comprising at least one indicator that indicates characteristics of the apparatus. An insertable management module suitable for releasably connecting to a backplane connector to establish an interface for receiving power from the backplane connector and exchanging information via the backplane connector. ,
A mating connector suitable for establishing an interface with the backplane connector;
A LAN transceiver connected to the mating connector and to the LAN controller;
A processor suitable for processing information,
Volatile memory for storing information and program instructions used by the processor;
A non-volatile memory for storing program instructions used by the processor;
An I / O controller suitable for exchange information with user input / output devices;
A video controller suitable for generating video signals;
An insertable management module including a bus connecting the I / O controller, the video controller, the LAN controller, the nonvolatile memory, the volatile memory, and the processor. A method of building a large, centrally manageable composite thin client system,
Each chassis includes providing a plurality of modular chassis suitable for receiving at least one of a plurality of insertable thin client blade modules, the modular chassis comprising:
i. A composite bay adapted to receive at least one of the plurality of insertable thin client blade modules;
ii. At least one backplane comprising connectors for each said composite bay, a common power bus, and a management bus interconnecting said composite bays;
iii. A KVM module suitable for connecting a user keyboard, mouse and display to one of the selectable insertable thin client blade modules;
Chaining at least two of the plurality of module chassis with the KVM module. A method of simulating a composite thin client system,
Each modular chassis is adapted to receive a plurality of insertable thin client blades to provide a plurality of modular chassis;
Inserting the plurality of insertable thin client blades and a single management module into each of the plurality of module chassis;
Connecting each of the plurality of thin client blades to a network switch;
Connecting the network switch to a server. A modular chassis comprising a composite bay suitable for receiving a plurality of thin client blade modules, the modular chassis comprising:
At least one backplane comprising a connector, a common power bus and a management bus;
Modular chassis including a KVM module suitable for connecting a user keyboard, mouse and display to a plurality of selectable thin client blade modules.   24. The modular chassis of claim 22, wherein the KVM module is suitable for cascading a plurality of substantially similar systems that allow for central management of one or more modular chassis.   The modular chassis of claim 22, wherein the KVM module is suitable for recognizing preprogrammed user keyboard input that triggers a particular KVM action.   23. The modular chassis of claim 22, wherein the KVM module is suitable for combining a composite video image from a composite thin client blade module with a single displayed image.   23. The KVM module is suitable for connecting to a remote or local site using a web server for delivering video and receiving keyboard and mouse commands via a web browser. Modular chassis.   24. The modular chassis of claim 22, further comprising at least one power supply module removably connectable to the modular chassis to provide power to the plurality of thin client blade modules.   23. The modular chassis of claim 22, including a modular chassis suitable for receiving a management module for centrally monitoring, configuring and controlling each of the plurality of thin client blade modules.

Images