JP4497463B2 - Screen sharing system and printing apparatus - Google Patents

Description

  The present invention relates to remote operation using a TC (thin client) by sharing a screen of a PC (personal computer), and to collaboration using a thin client.

  Conventionally, remote operation using a TC based on PC screen sharing includes remote operation using a general Web application (FIG. 11A). In addition, there is a terminal service in which a multi-user function is added to a Windows NT system (windowsNT / 2000 / XP) Server, which is an OS of Microsoft Corporation (FIG. 11B). This is because, like the X Window System of UNIX, multiple terminals can be connected to a server at the same time through the network for processing, and all application software is executed on the server and uses a protocol called RDP. The screen is transferred to the client side. Furthermore, there is a screen sharing system well known as VNC (Virtual Network Computing: http://www.realvnc.com/) (generally called remote operation or application sharing) (FIG. 11 (c)). .

  In addition, a communication control system (for example, see Patent Document 1) that considers display capability differences in screen sharing, a personal computer remote support system in which screens are shot and transferred by a camera, and keyboard / mouse operations are performed by voice commands. (See, for example, Patent Document 2).

Japanese Patent Laid-Open No. 2004-5582 Japanese Patent Laid-Open No. 10-11399

  The above-described WEB application (FIG. 11A) can be operated using only the Internet standard protocol and is suitable for an application such as database access, but an application operating on an existing OS cannot be used. It is also unsuitable for applications such as file operations and document creation.

  In the above terminal service (FIG. 11B), an application is executed by a server-side OS, but the server-side OS is limited to Windows 2000 / XP. The same applies to the form of the UNIX X terminal. The client only needs to be able to execute software according to the protocol, and there are clients that run on linux, Windows98 / 2000 / XP, and WindowsCE. The screen is generated on the client.

  In the above-described screen sharing (also referred to as application sharing or remote operation) (FIG. 11C), the OS on the server side varies depending on the software, but usually supports a plurality of platforms. For example, VNC runs on linux and Windows 9x / 2000 / XP. Some clients also run on WindowsCE and PalmOS. The screen is generated on the server side. This realizes sharing among a plurality of clients.

  As described above, screen sharing can realize a flexible computing environment. However, conventional screen sharing systems mainly operate (always) communication (or collaboration) between a PC equipped with a screen server and a PC equipped with a screen client. It was used for remote control of a PC.

  An object of the present invention is to provide a screen sharing system that can be used even when the PC is normally turned off and remotely operated by a user himself / herself.

  In the present invention, a PC that is normally used by a user can be used by using a client terminal anywhere in an intranet environment or a VPN-connected Internet environment. At the same time, collaborative work by display screen and operation is realized.

  In the present invention (Claims 1 and 2), since the screen is shared by being remotely activated by WOL, the screen can be shared even with a stopped PC.

  In the present invention (Claim 3), since the activation of the screen server can be suppressed by pressing a key, it is convenient to use when returning to the seat.

  In the present invention (Claim 4), since the account state is restored, it is more convenient to use when returning to his / her seat.

  In the present invention (Claims 5 and 6), since the IP address can be obtained from the ID, the operation becomes easy.

  According to the present invention (Claim 7), it is not necessary to input an ID, so that the operation becomes easy.

  In the present invention (Claim 8), it is not necessary to input a password, so that the operation becomes easier.

  In the present invention (Claim 9), it is not necessary to obtain a screen sharing password from the authentication server.

In the present invention (Claim 10 ), the connection destination can be changed to a PC for communication / collaboration, which is more convenient and efficient than starting a screen client on a remotely used PC.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram when a screen is shared between a PC and a TC according to the first embodiment of the present invention. Application 2 is processed by key / mouse event 5 to form screen data 3. The screen data 3 is converted into a transfer protocol by the transmission unit 4 and transmitted. In TC7, the screen is reproduced from the data transmitted by the receiving unit 8. When there is a keyboard input 11 or a mouse input 12, it is converted into a transfer protocol and transmitted from the transmission unit 10. The reception unit 6 of the PC 1 interprets this and generates a key / mouse event 5.

  The PC 1 is a PC that is normally used by the user and a PC that is centrally managed, such as a PC placed in his or her seat or a blade server. The TC 7 is a thin client device having at least a screen display 9, a key input 11, and a mouse input 12 (of course, an ordinary PC may be used).

  FIG. 2 is a process flowchart of the first embodiment. The TC 7 determines whether it is operating based on the Ping response (steps 101 and 102) (step 103). If it is operating, the screen client is activated (step 104). If it is stopped, a WOL (Wake ON LAN) MagicPacket is sent to the corresponding PC 1 (step 105). It waits for a set time (for example, 3 minutes) that is considered to be completed, or confirms the completion of activation by a Ping response at regular time intervals (for example, 1 minute) (steps 106 to 109), and activates the screen client (step 104).

  Since the screen sharing server is not started only by starting the PC 1, the screen sharing can be performed by starting automatically by the setting program (steps 201 to 203) as shown in FIG. 3.

  At this time, since the PC placed in his / her seat is at risk of being operated by a third party, the screen server is started in a state in which his / her operation is prohibited. However, to operate when returning to his / her seat, it is necessary to set again with TC. Therefore, when the program (steps 301 to 306) as shown in FIG. 4 is automatically activated and the user returns to his / her seat, the OS can be activated normally by pressing a key during activation. If the key to be pressed is checked for the state of the Shift or Ctrl key, there will be no strange data input. By doing as described above, remote operation by screen sharing is possible even for a stopped PC.

  FIG. 5 shows a configuration example of a system according to the second embodiment of the present invention. The PC 21 is a PC that is normally used by the user and is a PC that is centrally managed, such as a PC that is placed in a seat or a blade server. The TC 22 is a thin client device having at least a screen display, key input, and mouse input (of course, an ordinary PC may be used). The authentication server 24 is a server that authenticates the user of the TC 22. Authentication can be performed by an operation from the TC 22, but since the input is troublesome, if the IC card 23 is used, it only needs to be attached to the TC 22. In the information for managing the user ID, the IP address of the PC normally used and the information of MagicPacket are stored.

  FIG. 6 shows a processing flowchart for receiving the ID from the TC 22 and transmitting the IP address of the PC 21 at the time of authentication. A determination is made as to whether or not it is operating based on the Ping response (step 404). If it is operating, the IP address is sent to the TC (step 405). If it is stopped, the WOL MagicPacket is sent to the PC (steps 406 to 408).

  A processing flowchart of the TC 22 is shown in FIG. If the target PC is being activated (step 503), it waits for a set time (for example, 3 minutes) that is assumed to be completed (step 504), receives the IP address, and activates the screen client (steps 505 and 506). If the PC is operating, it immediately receives an IP address and starts the screen client.

  Since the PC 21 does not activate the screen sharing server just by being activated, it is possible to share the screen by automatically starting it with the setting program as shown in FIG. At this time, since the PC placed in his / her seat is at risk of being operated by a third party, the screen server is started in a state in which his / her operation is prohibited. However, to operate when returning to his / her seat, it is necessary to set again with TC. Therefore, when returning to his / her seat by automatically starting the program as shown in FIG. 4, the OS can be normally activated by pressing a key during activation. If the key to be pressed is checked for the state of the Shift or Ctrl key, there will be no strange data input. In this way, remote operation by screen sharing can be more easily performed on a stopped PC.

  FIG. 8 shows a configuration example of a system according to the third embodiment of the present invention. If the personal environment differs only in the data, network storage is allocated to the individual, and the PC can use any machine.

  The authentication server 32 manages the PC group 31, and when an ID is sent from the TCs 33 and 34, the screen sharing is performed by sending the IP address of one of the free PCs 31 and the screen sharing password to the TCs 33 and 34. . The TC activates the screen client using the sent IP address and password. By doing so, it is only necessary to prepare a PC with the maximum number of users, and efficient use of the PC becomes possible.

  FIG. 9 shows a system configuration example according to the fourth embodiment of the present invention. In communication and collaborative work, a plurality of people may view and operate the screen of one PC. However, in a thin client system using screen sharing, a TC cannot directly connect to a third party's PC. This can be done by exchanging information on a remotely operated PC and operating the screen client, but it is inefficient. Therefore, the information exchanged is transferred to the TC as follows, and the connection destination is changed to enable connection from the TC to the third party's PC.

  The PC 41 that sends the IP address and password of the PC by e-mail or IM and receives the e-mail or IM stores the IP address and password in the clipboard 43 as shown in FIG. 9, and responds to another PC connection request from the TC side. The clipboard information is transmitted 42, and the connection destination is changed 45 by the IP address and password on the TC side 44.

  FIG. 10 shows the configuration of the fifth embodiment of the present invention. An MFP (multifunction printer) or the like usually has an operation panel. If the printer has a simple console, PDA level operation like WindowsCE is possible. If a screen client is installed in the printer and it can be started with the screen sharing start button as shown in FIG. be able to. At this time, if the display screen is received in the screen size of the PC and the display is reduced, the screen is accumulated by the save operation and printed together by the print operation. In FIG. 10, if the save operation is assigned to the x button and the print operation is assigned to the Copy button, the operation can be easily performed. By doing so, it is possible to acquire and print information on the PC with the printer.

1 shows a system configuration example of Embodiment 1 of the present invention. 3 is a process flowchart of Embodiment 1. It is a processing flowchart of starting setting. It is a processing flowchart of Wakeon. The structural example of the system of Example 2 of this invention is shown. 10 is a process flowchart of Embodiment 2. It is a processing flowchart of TC22. The structural example of the system of Example 3 of this invention is shown. The system configuration example of Example 4 of this invention is shown. The structure of Example 5 of this invention is shown. A conventional example is shown.

Explanation of symbols

1 PC
2 Application 3 Screen data 4, 10 Transmitter 5 Key / Mouse event 6, 8 Receiver 7 TC
9 Display 11 Key input 12 Mouse input

Claims (10)

  In a system in which a device 1 that operates WOL that operates a screen server and a device 2 that operates a screen client share a screen via a network, the device 1 is configured to automatically start the screen server. A screen sharing system characterized in that the screen server is set to be automatically started in the device 1, is stopped, a WOL MagicPacket is sent from the device 2 to the device 1, is started, and a screen client is started after waiting for a certain period of time. .   In a system in which a device 1 that operates WOL that operates a screen server and a device 2 that operates a screen client share a screen via a network, the device 1 is configured to automatically start the screen server. The device 1 is set to automatically start the screen server in the device 1, is stopped, the WOL MagicPacket is sent from the device 2 to the device 1, the ping is transmitted at regular time intervals, the response is confirmed, and the screen client is started. A screen sharing system characterized by that.   3. The screen sharing system according to claim 1 or 2, wherein the state of the key is checked by means for automatically starting the apparatus 1, and the screen server is not started if the key is pressed.   4. The screen sharing system according to claim 3, wherein the state of the account is restored when the screen server is not activated.   In a system for sharing a screen via a network between a device 1 compatible with WOL that operates a screen server and a device 2 that operates a screen client, a device 3 that performs authentication is provided, and the device 1 automatically starts the screen server. The device 3 is set to automatically start the screen server and stopped, and the device 3 stores the IP address of the device 1 and MagicPacket information, and the ID information obtained from the device 2 Device 1 is identified, WOL's MagicPacket is sent to device 1 and activated, and information indicating that device 1 is activated and an IP address are sent to device 2, and device 2 waits for a certain period of time and then activates the screen client. A screen sharing system.   In a system for sharing a screen via a network between a device 1 compatible with WOL that operates a screen server and a device 2 that operates a screen client, a device 3 that performs authentication is provided, and the device 1 automatically starts the screen server. The device 3 is set to automatically start the screen server and stopped, and the device 3 stores the IP address of the device 1 and MagicPacket information, and the ID information obtained from the device 2 Device 1 is identified, WOL's MagicPacket is sent to device 1 and activated, and information indicating that device 1 is activated and an IP address are sent to device 2, and device 2 sends a ping to device 1 at regular time intervals. After confirming the response, the screen sharing system starts the screen client.   7. The screen sharing system according to claim 5, wherein authentication is performed using an IC card storing an ID.   8. The screen sharing system according to claim 7, wherein an authentication password is stored in the IC card.   8. The screen sharing system according to claim 7, wherein a screen sharing password is stored in an IC card. In the screen sharing system according to any one of claims 1 to 9, sends the PC IP address and password in e-mail or IM, stores the IP address and the password to the clipboard in PC that has received the e-mail or IM A screen sharing system, wherein clipboard information is transmitted in response to another PC connection request from the TC side, and the connection destination is changed by the IP address and password on the TC side.

Images