Patent Application
20090037637
1. Field of Invention
The invention relates to a computer architecture, and more particularly to a multiuser-multitasking computer architecture.
2. Description of Related Arts
A conventional multiuser-multitasking computer architecture is implemented in the Server-Client architecture that communicates data by Ethernet, referring to
A thin client is considered as a computer system but without storage devices, ex hard disk device (HDD). If adopting x86-based computer systems, the cost of a thin client is almost equal to a standard Personal Computer (PC) except HDD. For the purpose of decreasing hardware cost to adopt RISC-based SOC systems, ex: ARM, the relevant OS, drivers, and even applications for the Server-Client architecture have to be modified massively. The time and money for developing the software applied on the RISC-based Server-Client architecture will be increasing extraordinarily. Besides, almost entire data computing is executed in the server; therefore the CPUs of the thin clients become a waste in terms of the hardware investment, especially when the multi-core/multi-processor server which can handle extremely heavy computing loads at the same time is available and popular now.
Referring to
Therefore, there is a demand to provide a new architecture to resolve the problems mentioned above.
An object of the present invention is to reduce the total cost of ownership of a multiuser-multitasking computer architecture.
Another object of the present invention is to increase the convenience to expand the network of a multiuser-multitasking computer architecture.
Accordingly, in order to accomplish the one or some or all above objects, the multiuser-multitasking computer architecture comprises: a computing system comprising a chip set, an interface station connected to said computing system through a connection wire to transport data bi-directionally, wherein said interface station comprises a interface circuit; a monitor connected to said interface station; and an input device connected to said interface station..
One or part or all of these and other features and advantages of the present invention will become readily apparent to those skilled in this art from the following description wherein there is shown and described a preferred embodiment of this invention, simply by way of illustration of one of the modes best suited to carry out the invention. As it will be realized, the invention is capable of different embodiments, and its several details are capable of modifications in various, obvious aspects all without departing from the invention. Accordingly, the drawings and descriptions will be regarded as illustrative in nature and not as restrictive.
In an embodiment, referring to
The chipset 302 may comprise a north bridge and a south bridge. The connection to the interface stations 303 may come from the north bridge or the south bridge, or from both of them, depending on the design option.
The interface station 303, as shown in
The interface circuit 401 may be a USB-to-PCI bridge circuit for communication between USB and PCI protocols. The interface circuit 401 connects to a PCIE-interfaced USB Hub controlling circuit 404 and a PCI-interfaced GPU 402. The USB Hub controlling circuit 404 connects with input devices, such as a mouse and a keyboard. The GPU 402 connects with a monitor.
Or, the interface circuit 401 may be a PCIE-to-PCI bridge circuit for communication between PCI Express and PCI protocols. The interface circuit 401 connects to a PCI-interfaced USB Hub controlling circuit 404 and a PCI-interfaced GPU 402. The USB Hub controlling circuit 404 connects with input devices, such as a mouse and a keyboard. The GPU 402 connects with a monitor.
Or, the interface circuit 401 may be a PCTE switch for PCI Express protocol. The interface circuit 401 connects to a PCIE-interfaced USB Hub controlling circuit 404 and a PCIE-interfaced GPU 402 The USB Hub controlling circuit 404 connects with input devices, such as a mouse and a keyboard. The GPU 402 connects with a monitor.
Or, above-mentioned interface bridge function, GPU function and USB Hub function are integrated into an ASIC chip.
The client terminal 304 may comprise a monitor and input devices, such as a keyboard and a mouse. The monitor receives signals from the GPU 402, and the input devices communicate with the USB Hub controlling circuit 404.
Referring to
The client terminal 304 may comprise a monitor and input devices, such as a keyboard and a mouse. The monitor receives signals from the GPU 502, and the input devices communicate with the USB Hub controlling circuit 501.
One skilled in the art will understand that the embodiment of the present invention as shown in the drawings and described above is exemplary only and not intended to be limiting.
The foregoing description of the preferred embodiment of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form or to exemplary embodiments disclosed. Accordingly, the foregoing description should be regarded as illustrative rather than restrictive. Obviously, many modifications and variations will be apparent to practitioners skilled in this art. The embodiments are chosen and described in order to best explain the principles of the invention and its best mode practical application, thereby to enable persons skilled in the art to understand the invention for various embodiments and with various modifications as are suited to the particular use or implementation contemplated. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents in which all terms are meant in their broadest reasonable sense unless otherwise indicated. It should be appreciated that variations may be made in the embodiments described by persons skilled in the art without departing from the scope of the present invention as defined by the following claims. Moreover, no element and component in the present disclosure is intended to be dedicated to the public regardless of whether the element or component is explicitly recited in the following claims.
