1. Field of the Invention
The invention relates to a centralized computer system, i.e., so-called blade PC system, and more particularly, to a centralized computer system capable of pairing the hosts and the I/O peripherals.
2. Description of the Prior Art
Many commercial businesses and enterprises make extensive use of personal computers (PCs) in their daily operations. Typically, each user of a PC in the enterprise has a networked PC at his/her desk or work area. As the number of networked computer systems utilized in an enterprise increases, the management of resources in the network may become increasingly complex and expensive. Referring to FIG. 1, FIG. 1 is a schematic diagram illustrating an infrastructure of a typical centralized computer system. As shown in FIG. 1, the centralized computer system 1 comprises a plurality of hosts 12 and a plurality of sets of I/O peripherals 14 . Each set of I/O peripherals 14 comprises at least one peripheral device. The hosts 12 in the centralized computer system 1 are bladed, i.e., each host 12 is implemented into a “card”. In other words, each host 12 comprised on a circuit card comprises standard computer system components. The centralized computer system 1 also comprises a network 16 for the hosts 12 to communicate with the remote peripherals. The network 16 may be Local Area Network (LAN), such as intranet, or Wide Area Network (WAN), such as internet. As shown in FIG. 1, each set of I/O peripherals 14 comprises a display 142 , a keyboard 144 , a mouse 146 , and/or other peripheral devices for human interface. Each host 12 in the centralized computer system 1 transmits and receives encoded I/O signals via the network 16 to communicate with each set of I/O peripherals 14 .
In general, a large blade PCs (hosts), I/O peripherals, and end users are required in enterprises. Relatively, the following problems bring the service manager a heavy burden: (a) how to pair the I/O peripherals and the hosts; (b) how to pair the end users and the hosts; (c) the authority of the I/O peripherals relates to the hosts; and (d) the authority of the end users relates to the hosts.
Therefore, the scope of the invention is to provide a centralized computer system and the pairing method for pairing the hosts and the I/O peripherals.
A scope of the invention is to provide a centralized computer system and the pairing method for pairing the hosts and the I/O peripherals by a hierarchical directory.
Another scope of the invention is to provide a centralized computer system and the pairing method for pairing the hosts and the end users by a hierarchical directory.
According to a preferred embodiment, the pairing method of the invention is applied to the centralized computer system. The centralized computer system comprises a network, at least one host, and at least one set of I/O peripherals. The pairing method is capable of selectively enabling one of the sets of I/O peripherals to operate one of the hosts via the network. According to the pairing method of the invention, first, a hierarchical directory is established. Afterward, in the hierarchical directory, a first connecting relation for each host and each set of I/O peripherals and a second connecting relation for each host and at least one end user are selectively defined.
If the first connecting relation exists between one of the hosts and one of the sets of I/O peripherals, the set of I/O peripherals can be used to operate the host via the network. If the second connecting relation exists between one of the hosts and one of the end users, the end user can use any set of I/O peripherals to operate the host via the network. If the second connecting relation is absent between one of the hosts and one of the end users, the end user can only use the set of I/O peripherals having the first connecting relation related to the host to operate the host via the network.
According to the centralized computer system and the pairing method of the invention, the service manager can use the hierarchical directory to define connecting relation for each host and each set of I/O peripherals and further define connecting relation for each host and each end user. Therefore, the invention not only can reduce the burden on the server manager but also can avoid wasting network management resource.
The advantage and spirit of the invention may be understood by the following recitations together with the appended drawings.
FIG. 1 is a schematic diagram illustrating an infrastructure of a typical centralized computer system; and
FIG. 2 is a schematic diagram illustrating an infrastructure of a centralized computer system according to a preferred embodiment of the invention.
Referring to FIG. 2, FIG. 2 is a schematic diagram illustrating an infrastructure of a centralized computer system 3 according to a preferred embodiment of the invention. The centralized computer system 3 comprises a network 30 , a plurality of hosts H 1 ˜Hn, a plurality of I/O peripherals I/O 1 ˜I/On, and a hierarchical server 32 . In this embodiment, the hierarchical server 32 complies with but is not limited to a Lightweight Directory Access Protocol (LDAP). In this embodiment, each host H 1 ˜Hn has a plurality of operating functions, wherein these operating functions comprise at least one selected from a group consisting of: console redirection, audio redirection, keyboard and mouse redirection, virtual storage redirection, monitoring and controlling, and other operating functions.
In the invention, a hierarchical directory is stored in the hierarchical service 32 . The hierarchical directory is used for defining a first connecting relation for each host H 1 ˜Hn and each set of I/O peripherals I/O 1 ˜I/On and for defining a first authority for each set of I/O peripherals related to each host H 1 ˜Hn. The first connecting relation comprises a first user name and a first password corresponding to the first user name. For example, if the first connecting relation exists between the host H 1 and the set of I/O peripherals I/O 1 , the set of I/O peripherals I/O 1 can be used to operate the host H 1 via the network 30 . The first user name and the first password are stored in the set of I/O peripherals I/O 1 and cannot be modified. Additionally, the first authority allows the set of I/O peripherals I/O 1 to operate at least one of the operating functions of the host H 1 via the network 30 .
Furthermore, as shown in FIG. 2, if an end user 34 wants to use the set of I/O peripherals I/O 1 to operate the host H 1 , the set of I/O peripherals I/O 1 can utilize the predetermined first user name and the predetermined first password to login the hierarchical server 32 (as the transmitting path P 1 shown in FIG. 2). According to the first connecting relation defined in the hierarchical directory, the set of I/O peripherals I/O 1 can connect with the host H 1 . Afterward, the set of I/O peripherals I/O 1 transmits the first user name and the first password to the host H 1 (as the transmitting path P 2 shown in FIG. 2). Finally, the host H 1 utilizes the first user name and the first password to login the hierarchical server 32 (as the transmitting path P 3 shown in FIG. 2), so as to obtain the first authority. Whereby, according to the first authority, the set of I/O peripherals I/O 1 can be used to operate at least one of the operating functions of the host H 1 via the network 30 . It should be noted that the service manager can define the first authority according to the capacity of each end user.
In this embodiment, the service manager can also selectively define the second connecting relation for each host H 1 ˜Hn and at least one end user and selectively define a second authority for each end user related to each host H 1 ˜Hn in the hierarchical directory. The second connecting relation comprises a second user name and a second password corresponding to the second user name. For example, if the second connecting relation exists between the host H 2 and the end user 34 , the end user 34 can use any set of I/O peripherals I/O 1 ˜I/On to operate the host H 2 via the network 30 , even if the first connecting relation is absent between any set of I/O peripherals I/O 1 ˜I/On and the host H 2 . In other words, due to the absence of the second connecting relation between the host H 1 and the end user 34 , the end user 34 can only use the set of I/O peripherals having the first connecting relation related to the host H 1 to operate the host H 1 via the network 30 .
Moreover, as shown in FIG. 2, if the end user 34 wants to use the set of I/O peripherals I/O 1 to operate the host H 2 , the end user 34 can use the set of I/O peripherals I/O 1 to input the second user name and the second password to login the hierarchical server 32 (as the transmitting path P 1 ′ shown in FIG. 2). According to the second connecting relation defined in the hierarchical directory, the connection between the set of I/O peripherals I/O 1 and the host H 2 is allowed. Afterward, the set of I/O peripherals I/O 1 transmits the second user name and the second password to the host H 2 (as the transmitting path P 2 ′ shown in FIG. 2). Finally, the host H 2 utilizes the second user name and the second password to login the hierarchical server 32 (as the transmitting path P 3 ′ shown in FIG. 2), so as to obtain the second authority. Whereby, according to the second authority, the end user 34 can use the set of I/O peripherals I/O 1 to operate at least one of the operating functions of the host H 2 via the network 30 . It should be noted that the service manager can define the second authority according to the capacity of each end user.
Compared to the prior art, according to the centralized computer system and the pairing method of the invention, the service manager utilizes the hierarchical directory to define the connecting relation for each host and each set of I/O peripherals and the connecting relation for each host and each end user. Additionally, the service manager can utilizes the hierarchical directory to define the authority for each set of I/O peripherals related to the host and the authority for each end user related to the host. Therefore, the invention not only can reduce the burden on the server manager but also can avoid wasting network management resource.
With the example and explanations above, the features and spirits of the invention will be hopefully well described. Those skilled in the art will readily observe that numerous modifications and alterations of the device may be made while retaining the teaching of the invention. Accordingly, the above disclosure should be construed as limited only by the metes and bounds of the appended claims.