CN101826061A - Shared system and management method of hardware device - Google Patents

Shared system and management method of hardware device Download PDF

Info

Publication number
CN101826061A
CN101826061A CN200910118408A CN200910118408A CN101826061A CN 101826061 A CN101826061 A CN 101826061A CN 200910118408 A CN200910118408 A CN 200910118408A CN 200910118408 A CN200910118408 A CN 200910118408A CN 101826061 A CN101826061 A CN 101826061A
Authority
CN
China
Prior art keywords
mentioned
server
hardware
main frame
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN200910118408A
Other languages
Chinese (zh)
Inventor
周家浩
沈长毅
邓天隆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Asustek Computer Inc
Original Assignee
Asustek Computer Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Asustek Computer Inc filed Critical Asustek Computer Inc
Priority to CN200910118408A priority Critical patent/CN101826061A/en
Publication of CN101826061A publication Critical patent/CN101826061A/en
Pending legal-status Critical Current

Links

Images

Abstract

The invention relates to a shared system and a management method of a hardware device, which are matched with a first client host computer of a first operation system with a hardware driver to generate a management requirement to drive the hardware device. The shared system comprises a first servo end host computer, and the first servo end host computer can be coupled with a first client host computer and is provided a second operation system. Particularly, a fake hardware driver can be installed on the servo end host computer so that the hardware device can be driven according to the management requirement generated by the first client host computer.

Description

The shared system of hardware unit and management method
Technical field
The invention relates to a kind of shared system framework of hardware unit, and particularly relevant for a kind of shared system framework of hardware unit of spanning operation system platform.
Background technology
In known LAN framework, a plurality of clients can be shared the hardware structure that is coupled on the server-side.Figure 1 shows that the network system architecture figure that known a kind of hardware is shared.Please refer to Fig. 1, in known system architecture 100, client host 110 can pass through grid line 102 and server-side main frame 130 lines, and printer 150 hardware units such as grade can be connected to server-side main frame 130 by a transmission interface 142.
In known technology, be used for driving the hardware drive program 136 of printer 150, can be installed in the core layer 132 of operating system of server-side main frame 130.In addition, in core layer 132, interface drive program 138 is installed also, it is used for driving the interface controller 140 in the hardware layer 134 of server-side main frame 130, with management transmission interface 142.
In operating system application layer 112, many application software can be installed, for example text edit software 114.When supposing that the user will print operation by text edit software 114, then client host 110 can transmit one by 102 pairs of server-side main frames of network 130 and print job requirements PReq.This print job requires 114 hardware drive programs 136 that can be sent in the core layer 132, makes to drive hardware drive program 136 interface of calls drivers 138 printer 150 with control interface controller 140 by transmission interface 142 and print operation.
Because in known system architecture 100, the hardware drive program 136 that is used for driving printer 150 is to be installed in the core layer 132 of operating system of server-side main frame 130.Therefore, the administrative power of printer 150 need be set to server-side main frame 130.If client host 110 need be controlled printer 150 by server-side main frame 130, then client host 110 just needs to install and server-side main frame 130 identical operations systems.In other words, known system architecture 100, and can't allow to allow the client host 110 that different operating system is installed by server-side main frame 130, control the hardware unit that is coupled on the server-side main frame 130.
Summary of the invention
Therefore, the invention provides a kind of shared system and a kind of management method of hardware unit, the client host that can allow different operating system is installed is controlled the hardware unit that is coupled on the server-side main frame by the server-side main frame.
The invention provides a kind of shared system of hardware unit, cooperate first client host of first operating system, drive hardware unit to produce a management expectancy with a hardware drive program.Shared system of the present invention comprises the first server-side main frame, can couple first client host, and has one second operating system.Specifically, the server-side main frame can be installed a pseudo-hardware drive program, drives this hardware unit with the management expectancy that is produced according to first client host.
From another viewpoint, the present invention also provides a kind of management method of hardware unit, is applicable to that one first client links to a server-side.Wherein, first client can be installed one first operating system, and server-side then can be installed one second operating system.Management method of the present invention comprises that when hardware unit is coupled to server-side by a transmission interface then first client is installed a pseudo-hardware drive program and controlled this server-side.In addition, when first client produces a management expectancy with the hardware management device, then issue this management expectancy, so that management expectancy is carried out at server-side by pseudo-hardware drive program.And when management expectancy server-side be performed finish after, then server-side can return execution result to first client.
In certain embodiments, when first client produces management expectancy with the hardware management device, then shield this hardware unit, make hardware unit be considered and be coupled to first client at server-side.
Because in the present invention, the driver of hardware unit is mounted in the client host, and the management expectancy that it produced then is to be sent to the server-side main frame, and is issued by the pseudo-hardware drive program that it is installed.Therefore, the present invention can allow to have the client host of different operating system platform, by a server-side main frame, uses the hardware unit that is connected on the server-side main frame jointly.
For above-mentioned feature and advantage of the present invention can be become apparent, embodiment cited below particularly, and cooperate appended graphic being described in detail below.
Description of drawings
Figure 1 shows that the system architecture diagram of known a kind of shared hardware unit;
Figure 2 shows that calcspar according to the shared system of a kind of hardware unit of a preferred embodiment of the present invention;
Figure 3 shows that system block diagrams according to a kind of client host and the server-side main frame of a preferred embodiment of the present invention;
Figure 4 shows that flow chart of steps according to the management method of a kind of hardware unit of a preferred embodiment of the present invention;
Figure 5 shows that according to a kind of of a preferred embodiment of the present invention the hardware unit administrative power is set process flow diagram to the step of client host;
Fig. 6 then is depicted as the calcspar according to the shared system of a kind of hardware unit of another embodiment of the present invention.
Embodiment
Figure 2 shows that calcspar according to the shared system of a kind of hardware unit of a preferred embodiment of the present invention.Please refer to Fig. 2, the shared system 200 that present embodiment provided comprises server-side main frame 202, and it can couple a plurality of client hosts, for example 204 and 206.In the present embodiment, client host 204 and 206 can be coupled to server-side main frame 206 by grid line 208 respectively, and can have relative operation system respectively.In the present embodiment, client host 204 and 206 is allowed to have identical operations system or different operating system.
Server-side main frame 202 has a transmission interface 210, for example is universal serial bus.And by this transmission interface 210, hardware unit 212 can be coupled to server-side main frame 202.Figure 3 shows that system block diagrams according to a kind of client host and the server-side main frame of a preferred embodiment of the present invention.Please refer to Fig. 3, in the present embodiment, is to illustrate with client host 204, however this area have know usually the knowledgeable should push away voluntarily the system architecture of other client host, below will can not add again and give unnecessary details.
Client host 204 can comprise the application layer 302 of operating system, the core layer 304 and the hardware layer 306 of operating system.Wherein, application layer 302 can be equipped with a plurality of application programs, and Transmit-Receive Unit 308 can be installed.In the present embodiment, Transmit-Receive Unit 308 can utilize the form of software to realize.
304 of the core layers of operating system are equipped with hardware drive program 310, transmission interface kernel program 312 and transmission interface driver 314.And in order to make following narration more simple and clear, below all transmission interface is got with USB and replaced, yet the present invention is not as limit.
In core layer 304, hardware drive program 310 can be linked up with application layer 302, and it can be used for driving hardware unit 212.In addition, 312 of USB kernel programs can be used as the intermediary of hardware drive program 310 and USB driver 314.Wherein, 314 of USB drivers can the USB controller 316 of drive arrangements in hardware layer 306.
Similarly, server-side main frame 202 also can comprise the application layer 322 of operating system, the core layer 324 and the hardware layer 326 of operating system.In application layer 322, equally also Transmit-Receive Unit 328 can be installed, its can with Transmit-Receive Unit 308 lines.Specifically, in the application layer 322 of server-side main frame 202, can also dispose pseudo-hardware drive program 330, its can be on server-side main frame 202 function of analogy hardware drive program 310.
Pseudo-hardware drive program 330 can be coupled to core layer 324.And core layer 324 equally also comprises USB kernel program 332 and USB driver 334.Wherein, USB driver 334 is to be used for the USB controller 336 of drive arrangements in hardware layer 326.
Figure 4 shows that flow chart of steps according to the management method of a kind of hardware unit of a preferred embodiment of the present invention.Please merge with reference to Fig. 3 and Fig. 4, in the present embodiment, the USB controller 336 that is arranged in server-side main frame 202 can continue the state of monitoring transmission interface 210 as described in the step S402.When hardware unit 212 is coupled on the server-side main frame 202 by transmission interface 210, USB controller 336 can react to core layer 324, so that USB kernel program 332 can trigger an insertion incident, this information of inserting incident then can send client host 204 to by Transmit-Receive Unit 328.
When the Transmit-Receive Unit 308 of client host 204 receives the information that the insertion incident is triggered, can inform the hardware drive program 310 that is installed on core layer 304.At this moment, hardware dynamic program 310 can produce corresponding management expectancy MReq and give USB kernel program 312.In addition, this management expectancy MReq also can be sent to Transmit-Receive Unit 308.At this moment, Transmit-Receive Unit 308 can convert management expectancy MReq to suitable form, sends server-side main frame 202 again to.
When server-side main frame 202 is received management expectancy MReq by Transmit-Receive Unit 328, it can be delivered to pseudo-hardware drive program 330, to issue the core layer 324 that this management expectancy MReq gives server-side main frame 202 by pseudo-hardware drive program 330, with the action of the normal hardware drive program of emulation.At this moment, USB kernel program 332 can be handled this management expectancy MReq.It should be noted that at this two operating system of server-side main frame 202 and client host 204 is not necessarily identical.Therefore, when server-side main frame 202 and client host 204 the two operating system not simultaneously, then pseudo-hardware drive program 330 also needs the content of identification management expectancy MReq, and converts to and generally can send USB kernel program 332 again to behind the form of identification in server-side main frame 202.
After receiving the management expectancy of being issued by pseudo-hardware drive program 330 when USB kernel program 332, can call out USB driver 334 and drive USB controller 336, and can set a virtual concentrator (Hub) 338 in the core layer 324.By this, server-side main frame 202 can utilize virtual concentrator, and by transmission interface 210 and hardware unit 212 lines.In addition, whether the state that USB kernel program 332 can also be detected hardware unit 212 by USB controller 336 is to share state, just as described in the step S404.
If USB controller 336 finds that the state of hardware unit 212 is not to be set to share state (being exactly the "No" that step S404 is indicated), then the administrative power of hardware unit 212 will be set to server-side main frame 202 (S406).Relatively, if the administrative power of hardware unit 212 is set to (being exactly the "Yes" that step S404 is indicated) when sharing state, then the administrative power of hardware unit 212 just can be set to client host 204 (S408).
Figure 5 shows that according to a kind of of a preferred embodiment of the present invention the hardware unit administrative power is set process flow diagram to the step of client host.Please merge with reference to Fig. 3 and Fig. 4, when the state of finding hardware unit 212 is when sharing state, then on server-side main frame 202, can hardware unit 212 shieldings be got up as described in the step S502.At this moment, hardware unit 212 can not be listed in the hardware list of server-side main frame 202.In other words, hardware unit 212 is considered in operation and is not present in server-side main frame 202.
On the other hand, hardware unit 212 can be set carry at client host 204 as described in the step S504.At this moment, virtual concentrator 338 can be regarded as in the core layer 304 that is present in client host 204 in operation, and USB controller 316 can be considered directly and is coupled to hardware unit 212 by virtual concentrator 338.At this moment, hardware unit 212 just can be listed in the hardware list of client host 204.In other words, hardware unit 212 is considered in operation and directly is coupled to client host 204.
In certain embodiments, suppose that hardware unit 212 is external connection type memory apparatus, and when the user will carry out the access of data to this hardware unit 212, then application layer 302 can produce instruction corresponding INS and give hardware drive program 310.At this moment, hardware drive program 310 can produce corresponding management expectancy MReq according to operational order INS, just as described in the step S506.Similarly, this management expectancy MReq also can be sent to server-side main frame 202 by Transmit-Receive Unit 308 as described in the step S508, makes Transmit-Receive Unit 328 can carry out step S510, exactly management expectancy MReq is transferred to pseudo-hardware drive program 330 and issues.
When pseudo-hardware drive program 330 was issued the management expectancy MReq that is produced by hardware drive program 310, USB kernel program 332 can drive USB controllers 336 by control USB drivers 334, makes USB controller 336 carry out management expectancy MReq.For example, when data will be written in the hardware unit 212, the data that be written into can be sent to server-side main frame 202.At this moment, USB controller 336 just can be controlled and carry out data are write operation in the hardware unit 212.When management expectancy MReq server-side main frame 202 be performed finish after, server-side main frame 202 can return execution result to client host 204 by Transmit-Receive Unit 328 again.At this moment, the user at client host 204 can think that these operations are to be done at client host 204.
In above embodiment, client host 204 is placed in respectively on the different computer apparatus with server-side main frame 202.Yet, because hardware unit 212 is not to be present in server-side main frame 202 in operation.Therefore, the user also can't be with hardware unit 212 on the computer apparatus at server-side main frame place.Fig. 6 then is depicted as the calcspar according to the shared system of a kind of hardware unit of another embodiment of the present invention.Please refer to Fig. 6, in the present embodiment, on same computer apparatus, server-side main frame 202 and 602 can be installed simultaneously.Therefore, the user just can use hardware unit 212 on the computer apparatus at server-side main frame 202 places.In other words, server-side main frame 202 can utilize any computer apparatus to serve as.
In sum, in the present invention, the driver that in fact drives hardware unit is to be installed on each client host, on the server-side main frame then is the hardware drive program that pseudo-hardware drive program comes artificial actual is installed.Therefore, client computer with different operating system can be installed suitable hardware drive program separately, the pseudo-hardware drive program that the management expectancy that is produced then can be unified to transfer on the server-side main frame is issued, and on the server-side main frame, be performed, on the server-side main frame, to share a hardware unit.
Though the present invention discloses as above with embodiment; right its is not in order to limit the present invention; have in the technical field under any and know the knowledgeable usually; without departing from the spirit and scope of the present invention; when doing a little change and retouching, so protection scope of the present invention is as the criterion when looking claims person of defining.

Claims (16)

1. the shared system of a hardware unit cooperates first client host of first operating system with hardware drive program, drives above-mentioned hardware unit to produce management expectancy, it is characterized in that, comprising:
The server-side main frame, couple above-mentioned first client host, and have second operating system, above-mentioned hardware unit is connected to above-mentioned server-side main frame by transmission interface, above-mentioned server-side main frame is equipped with pseudo-hardware drive program, in order to drive above-mentioned hardware unit according to above-mentioned management expectancy.
2. shared system according to claim 1 is characterized in that, wherein above-mentioned transmission interface is a universal serial bus.
3. shared system according to claim 1 is characterized in that, wherein above-mentioned first operating system is different with above-mentioned second operating system.
4. shared system according to claim 1 is characterized in that, wherein above-mentioned first operating system comprises:
First application layer has first Transmit-Receive Unit, in order to above-mentioned server-side main frame line; And
First core layer couples above-mentioned first application layer, comprising:
Above-mentioned hardware drive program produces management expectancy and comes the above-mentioned hardware unit of management and control; And
The first transmission interface kernel program couples above-mentioned hardware drive program, handling above-mentioned management expectancy, and above-mentioned management expectancy is delivered to above-mentioned Transmit-Receive Unit, is sent to above-mentioned server-side main frame to convert default form to.
5. shared system according to claim 4 is characterized in that, wherein above-mentioned second operating system more comprises:
Second application layer has second Transmit-Receive Unit, itself and the above-mentioned first Transmit-Receive Unit line, and above-mentioned pseudo-hardware drive program is installed, to receive the management expectancy that is sent by above-mentioned first client host by above-mentioned second Transmit-Receive Unit; And
Second core layer couples above-mentioned second application layer, comprising:
The second transmission interface kernel program couples above-mentioned pseudo-hardware drive program, to handle the management expectancy by above-mentioned client host was produced; And
The transmission interface driver couples the above-mentioned second transmission interface kernel program.
6. shared system according to claim 5 is characterized in that, wherein above-mentioned server-side main frame has more transmission interface controller, is driven according to above-mentioned management expectancy by above-mentioned transmission interface driver.
7. shared system according to claim 6, it is characterized in that, wherein above-mentioned second core layer more comprises virtual concentrator, couple above-mentioned hardware unit by above-mentioned second transmission interface, above-mentioned virtual concentrator also is coupled to above-mentioned transmission interface controller, makes that above-mentioned transmission interface controller is able to manage above-mentioned hardware unit by above-mentioned virtual concentrator.
8. shared system according to claim 1 is characterized in that, wherein above-mentioned first client host is positioned in the identical computer apparatus with above-mentioned server-side main frame.
9. shared system according to claim 1 is characterized in that, wherein above-mentioned first client host is placed in respectively in the different computer apparatus with above-mentioned server-side main frame.
10. shared system according to claim 1 is characterized in that, wherein above-mentioned client host is by network and above-mentioned server-side main frame line.
11. the management method of a hardware unit is applicable to that first client links to server-side, wherein above-mentioned first client is installed first operating system, and above-mentioned server-side is then installed second operating system, it is characterized in that, above-mentioned management method comprises the following steps:
When above-mentioned hardware unit was coupled to above-mentioned server-side by transmission interface, then above-mentioned first client was installed pseudo-hardware drive program and is controlled above-mentioned server-side;
When above-mentioned first client produces management expectancy when managing above-mentioned hardware unit, issue above-mentioned management expectancy by above-mentioned pseudo-hardware drive program, so that above-mentioned management expectancy is carried out at above-mentioned server-side; And
The execution result that is returned above-mentioned management expectancy by above-mentioned server-side is given above-mentioned first client.
12. management method according to claim 11, it is characterized in that, wherein produce management expectancy when managing above-mentioned hardware unit when above-mentioned first client, shield above-mentioned hardware unit, make above-mentioned hardware unit be considered and be coupled to above-mentioned first client at above-mentioned server-side.
13. management method according to claim 11 is characterized in that, wherein above-mentioned transmission interface is a universal serial bus.
14. management method according to claim 11 is characterized in that, wherein above-mentioned first operating system is different with above-mentioned second operating system.
15. management method according to claim 11 is characterized in that, wherein above-mentioned first client is present in the identical computer apparatus with above-mentioned server-side.
16. management method according to claim 11 is characterized in that, wherein above-mentioned first client is present in respectively in the different computer apparatus with above-mentioned server-side.
CN200910118408A 2009-03-03 2009-03-03 Shared system and management method of hardware device Pending CN101826061A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN200910118408A CN101826061A (en) 2009-03-03 2009-03-03 Shared system and management method of hardware device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN200910118408A CN101826061A (en) 2009-03-03 2009-03-03 Shared system and management method of hardware device

Publications (1)

Publication Number Publication Date
CN101826061A true CN101826061A (en) 2010-09-08

Family

ID=42689983

Family Applications (1)

Application Number Title Priority Date Filing Date
CN200910118408A Pending CN101826061A (en) 2009-03-03 2009-03-03 Shared system and management method of hardware device

Country Status (1)

Country Link
CN (1) CN101826061A (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103312746A (en) * 2012-03-12 2013-09-18 国际商业机器公司 Information device and information appliance for collaborating a plurality of information device resources
CN105075188A (en) * 2013-02-18 2015-11-18 微软公司 Controlling devices using cloud services and device-agnostic pipe mechanisms
US9891957B2 (en) 2011-06-30 2018-02-13 International Business Machines Corporation Collaborating with resources residing in multiple information devices
CN110740093A (en) * 2019-10-24 2020-01-31 北京大学 data forwarding device based on virtual host
CN112905243A (en) * 2019-11-15 2021-06-04 成都鼎桥通信技术有限公司 Method and device for simultaneously operating two systems

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9891957B2 (en) 2011-06-30 2018-02-13 International Business Machines Corporation Collaborating with resources residing in multiple information devices
CN103312746A (en) * 2012-03-12 2013-09-18 国际商业机器公司 Information device and information appliance for collaborating a plurality of information device resources
CN105075188A (en) * 2013-02-18 2015-11-18 微软公司 Controlling devices using cloud services and device-agnostic pipe mechanisms
CN105075188B (en) * 2013-02-18 2019-01-04 微软技术许可有限责任公司 Pipeline mechanism and making uses it to method, system and the medium of control equipment
CN110740093A (en) * 2019-10-24 2020-01-31 北京大学 data forwarding device based on virtual host
CN110740093B (en) * 2019-10-24 2020-09-15 北京大学 Data forwarding device based on virtual host
CN112905243A (en) * 2019-11-15 2021-06-04 成都鼎桥通信技术有限公司 Method and device for simultaneously operating two systems
CN112905243B (en) * 2019-11-15 2022-05-13 成都鼎桥通信技术有限公司 Method and device for simultaneously operating double systems

Similar Documents

Publication Publication Date Title
CN102523264B (en) USB (Universal Serial Bus) equipment remote sharing method and system for virtual machine
CN102110196B (en) Method and system for safely transmitting data among parallel-running multiple user operating systems
US8462369B2 (en) Hybrid image processing system for a single field of view having a plurality of inspection threads
US20090328038A1 (en) Computer System and Device Controlling Method for Computer System
CN102541791A (en) Data transferring apparatus and control method thereof
CN104246733A (en) Data redirection for universal serial bus devices
CN101826061A (en) Shared system and management method of hardware device
US9928206B2 (en) Dedicated LAN interface per IPMI instance on a multiple baseboard management controller (BMC) system with single physical network interface
CN1818890A (en) Rnic-based offload of iscsi data movement function by initiator
CN103262034A (en) Zoning data to a virtual machine
USRE46770E1 (en) Computer managing method
CN101533375B (en) USB equipment accessing method, device and control system thereof in virtual machine system
CN102203721A (en) Print plug-in isolation
CN101535979A (en) Management of storage resource devices
CN102177682A (en) Portable management device
CN204117142U (en) Electronic device for providing instant switching and sharing of universal serial bus electronic equipment by host
CN104063335A (en) USB equipment redirecting method, equipment and system
CN102843435A (en) Access and response method and access and response system of storing medium in cluster system
US20100228816A1 (en) Sharing system and management method for hardware device
WO2013023195A1 (en) Device and method for remote computer operation
CN116723198A (en) Multi-node server host control method, device, equipment and storage medium
CN101388906A (en) Method and system for accessing data
CN101739284A (en) Computer and information processing method
JP2008263678A (en) Servo motor controller
JP2008107997A (en) Data communication method, data communication device and data communication system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C12 Rejection of a patent application after its publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20100908