JP2021164025A - Image forming apparatus - Google Patents

Abstract

To provide an image forming apparatus that can address a situation in which an operation input from another person from the image forming apparatus is desired to be inhibited after the start of remote connection.SOLUTION: In an image forming system 1, a CPU of a MFP, when a PC is remotely connected through a network IF, transmits screen data for displaying the same screen as a display screen displayed on a panel to the PC, receives a remote access from the PC, executes processing for displaying a display screen according to the remote access, after a transition of the image forming apparatus to a maintenance mode in response to a transition instruction to the maintenance mode included in the received remote access, stops screen update from the display screen that was displayed on the panel immediately before the transition to the maintenance mode, and when the PC is remotely connected, transmits, to the PC, screen data of a screen displayed on the panel in the maintenance mode when the PC is not remotely connected.SELECTED DRAWING: Figure 1

Description

The present application relates to a technique for remotely controlling an image forming apparatus from an information processing terminal.

In Patent Document 1, in an image forming system including an image forming apparatus and a remote operating apparatus for remotely operating the image forming apparatus, priority buttons are provided on the image forming apparatus side and the remote operating apparatus side, respectively. Describes an image forming system that enables exclusive control that enables operation input from the device on the operating side of the priority button and prohibits operation input from the device on the non-operating side when the priority button is operated. ..

Japanese Unexamined Patent Publication No. 2005-321944

However, in the image forming system described in Patent Document 1, it is not considered that the operation input on the image forming apparatus side is prohibited after the remote connection is started, so that the administrator of the image forming apparatus can perform the remote connection. After the start, it is not possible to deal with the case where it is desired to prohibit the operation input of another person from the image forming apparatus.
In addition, when the administrator remotely operates the image forming apparatus, the user of the image forming apparatus may not want to see the operation contents and screen transitions of the administrator displayed on the main body screen of the image forming apparatus. .. This is because there is a risk that confidential information may be leaked to the user who sees the operation contents of the administrator or the screen transition.

An object of the present application is to provide a technique capable of dealing with a case where it is desired to prohibit another person's operation input from an image forming apparatus or a case where confidential information is leaked to another person after the start of remote connection. do.

In order to achieve the above object, the image forming apparatus of the present application is an image forming apparatus including a communication interface, a display unit, and a control unit, and in the control unit, the information processing device is remoted via the communication interface. When connected, the screen data for displaying the same screen as the display screen displayed on the display unit on the information processing device is transmitted to the information processing device, the remote access from the information processing device is received, and the remote is remoted. After executing the display processing of the display screen according to the access and after the image forming apparatus shifts to the predetermined mode in response to the shift instruction to the predetermined mode included in the received remote access, immediately before shifting to the predetermined mode. The screen update from the display screen displayed on the display unit is stopped, and the screen data of the screen displayed on the display unit in the predetermined mode when not remotely connected is sent to the information processing device when remotely connected. Send.

According to the present application, it is possible to deal with a case where it is desired to prohibit the operation input of another person from the image forming apparatus or a case where confidential information is leaked to another person after the start of the remote connection.

It is a block diagram which shows the control structure of the image formation system which concerns on one Embodiment of this application. An example of each of the display screens ((a) and (b)) of the browser launched on the PC of FIG. 1 and the display screen ((c)) of the panel of the MFP is shown. An example of the display screen in which the display screen of the browser of FIG. 2 has changed is shown. It is a flowchart which shows the procedure of the main processing executed by the PC of FIG. 1, especially the CPU. It is a flowchart which shows the detailed procedure of the remote control screen display process included in the main process of FIG. It is a flowchart which shows the detailed procedure of the screen update process included in the main process of FIG. It is a flowchart which shows the detailed procedure of the http (s) cgi request execution process included in the main process of FIG. It is a flowchart which shows the procedure of the main processing executed by the MFP of FIG. 1, especially the CPU. It is a flowchart which shows the detailed procedure of the main body panel processing included in the main processing of FIG. It is a flowchart which shows the detailed procedure of the initial screen transmission process included in the main process of FIG. It is a flowchart which shows the detailed procedure of the screen data transmission process included in the main process of FIG. It is a flowchart which shows the detailed procedure of the screen pressing process included in the main process of FIG. It is a flowchart which shows the detailed procedure of the take-off process included in the main process of FIG.

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

FIG. 1 shows a control configuration of an image forming system 1 according to an embodiment of the present application. The image forming system 1 includes a PC 10, an MFP 100, and a router 32. MFP is an abbreviation for multifunction peripheral.

The PC 10 mainly includes a CPU 12, a storage unit 14, a user IF 16, a display 18, and a network IF 20. The CPU 12, the storage unit 14, the user IF 16, the display 18, and the network IF 20 can communicate with each other via the input / output ports 22. IF is an abbreviation for interface.

The user IF16 typically comprises a keyboard and a mouse.

The display 18 is composed of a display device such as a liquid crystal display or an organic EL display, a drive circuit for driving the display device, and the like. When a touch panel type display 18 is used, the user can perform an input operation by touching an input button on the screen. Therefore, in this case, the display 18 also serves as the user IF 16.

Based on FIG. 4, the CPU 12 executes various application programs (hereinafter abbreviated as “application”) including a main processing program described later, firmware, and the like.

The storage unit 14 includes a ROM, a RAM, an HDD, an SSD, an optical disk drive, and the like. The data storage area 28 of the storage unit 14 is an area for storing data or the like necessary for the CPU 12 to execute a program or the like for main processing. The control program area 26 of the storage unit 14 is an area for storing the OS, the main processing program, and other various applications and firmware.

The network IF20 connects the PC 10 to the communication network 40. The communication network 40 is a wired or wireless LAN. The network IF 20 is either a LAN IF or a WLAN IF, or both. In the present embodiment, the router 32 and the MFP 100 are connected to the communication network 40, so that the PC 10 can transmit and receive various data to and from the MFP 100 via the router 32.

The MFP 100 includes a CPU 101, a ROM 102, a RAM 103, and an NVM 104. NVM is an abbreviation for non-volatile memory.

The CPU 101 controls the entire MFP 100, and controls the printing engine 111 and the reading engine 112, respectively, via the engine IF 110.

The ROM 102 is a memory that stores a control program (including a main processing program described later based on FIG. 8) executed by the CPU 101. The CPU 101 reads the control program stored in the ROM 102 and executes various processes. The RAM 103 is a memory that temporarily stores image data and the like. The RAM 103 is also used as a storage area for temporarily storing data, signals, and the like used by the CPU 101 when executing a control program, or as a work area for data processing. The NVM 104 is a non-volatile memory that stores setting information and the like.

The MFP 100 also includes a panel 105 and a key 106. The panel 105 is a touch panel in the present embodiment, and various screens are displayed on the panel 105 depending on the state of the MFP 100. The user can perform an input operation by touching an input button on the screen. In the present specification, "touching the input button on the screen" may also be referred to as "pressing the input button on the screen". The key 106 is a hard key, that is, a key formed by hardware. Examples of the key 106 include a power switch, a reset switch, and a numeric keypad.

Further, the MFP 100 includes a network IF 108 similar to the network IF 20 of the PC 10. As a result, as described above, the MFP 100 can send and receive various data to and from the PC 10.

Further, the MFP 100 includes an engine IF 110. A printing engine 111 and a reading engine 112 are connected to the engine IF 110. The printing engine 111 is a device for printing an image on a sheet, and has a printing device of an electrophotographic method, an inkjet method, a thermal method, or the like. The reading engine 112 is a device for reading an image from a document, and has a reading device such as a CCD or CIS. The engine IF 110 is an IF that controls the printing engine 111 and the reading engine 112.

Further, the MFP 100 includes an image processing circuit 120. The image processing circuit 120 rasterizes the image data related to the print job and outputs it to the print engine 111. The image processing circuit 120 also processes the image data read from the document by the reading engine 112 into digital data. The image data processed into digital data is transmitted to the outside via the network IF307, or is supplied to the printing engine 111 and output to a sheet.

The CPU 101, ROM 102, RAM 103, NVM 104, panel 105, key 106, USB IF 107, network IF 108, engine IF 110, and image processing circuit 120 are connected to each other by a bus 130.

FIG. 2A shows an example of the browser screen 180 displayed on the display 18 when the user starts the browser on the PC 10 and inputs the URL “10.100.100.1” in the URL input field 181. The entered URL "10.100.100.1" indicates the storage location of EWS, which is one of the control programs of the MFP100. EWS is an abbreviation for embedded Web server.

A page provided by EWS is displayed in the page display area 182 of the browser screen 180. The page provided by EWS consists of an item pane 183 and a detail pane 184. The page shown in FIG. 2A is an initial page provided by EWS. When the user enters the password in the login password input field 182a in this initial page and clicks the login button 182b with the cursor C, the user can log in to the function setting page provided by EWS for setting various functions of the MFP100. can.

FIG. 2B shows an example of the browser screen 180 displayed when the “Remote Panel” item 183a is clicked among the plurality of items described in the item pane 183 in the function setting page. The “Remote Panel” item 183a is an item for displaying the “Remote Panel” in the detail pane 184. On the browser screen 180 of the illustrated example, a login authentication screen 190 for performing login authentication to the "Remote Panel" is displayed in a pop-up. In this way, login authentication is performed before displaying the "Remote Panel" for the following reasons.

That is, the "Remote Panel" is a virtual screen that virtually creates and displays the panel display of the device in order to perform remote access to the device that is remotely connected. Therefore, when the operation input is performed on the "Remote Panel" displayed on the detail pane 184, the result is that the same operation input is performed on the remotely accessed device, the panel 105 of the MFP 100 in the present embodiment. Therefore, if the "Remote Panel" is displayed on the PC 10, a third party can freely remotely access the MFP 100 from the outside via the PC 10, so that a person who can display the "Remote Panel" can be displayed. Need to limit. Therefore, even after logging in to the function setting page, further login authentication is required to display the "Remote Panel".

Login to the "Remote Panel" is limited to users with administrator privileges (hereinafter referred to as "administrators"). Therefore, the administrator name (“Administrator”) is entered in the user name input field 190a in the login authentication screen 190, and the administrator password is entered in the password input field 190b. Then, when the login button 190c is clicked with the cursor C, as shown in FIG. 2C, a confirmation screen 105a for confirming whether or not remote control of the MFP100 may be permitted is displayed on the panel 105 of the MFP100. NS. When the user of the MFP 100 presses the "Yes" button 105a1 in the confirmation screen 105a, the "Remote Panel" is displayed in the detail pane 184.

FIG. 3A shows an example of the “Remote Panel” displayed in the detail pane 184. The “Remote Panel” in the illustrated example includes a key display 105c that virtually displays the key 106 of the MFP 100 in addition to the panel display 105b displayed on the panel 105 of the MFP 100. The display data for displaying the "Remote Panel" is acquired from EWS. Since the EWS is software as described above, "acquiring from the EWS" is, strictly speaking, acquired from the MFP 100 by the CPU 101 of the MFP 100 executing the software of the EWS. However, it may be abbreviated as "obtain from EWS".

In the "Remote Panel", an end button 184a for terminating the "Remote Panel" is also displayed. The administrator can terminate the "Remote Panel" by clicking the exit button 184a.

Further, in the "Remote Panel", an ON / OFF button 184c for shifting the MFP 100 to the maintenance mode and ending the maintenance mode after the shift is also displayed. The administrator can shift the MFP 100 to the maintenance mode by clicking the ON / OFF button 184c. However, before shifting to maintenance mode, authentication for shifting to maintenance mode is required. Therefore, when the ON / OFF button 184c is clicked in the device mode "Remote Panel" (the "Remote Panel" in FIG. 3A is referred to as the device mode "Remote Panel"), the maintenance mode is entered. The “Remote Panel” for authentication is displayed. Then, when the authentication is successful in the "Remote Panel" for this authentication, the mode shifts to the maintenance mode.

FIG. 3B shows an example of an authentication “Remote Panel” for shifting to the maintenance mode. The administrator inputs the password in the password input field 105d1 in the panel display 105d using, for example, the software keyboard 105d2, and when the authentication is successful, the mode shifts to the maintenance mode "Remote Panel". The "Remote Panel" in the maintenance mode is almost the same as the "Remote Panel" for authentication in FIG. 3B, and only enables the operation for maintenance to be executed. The password can be input to the password input field 105d1 by using the key in the key display 105c.

The maintenance mode is a mode for performing maintenance of the MFP 100, and specific examples of maintenance include investigating the cause of failure of the MFP 100 and changing the settings of items that cannot be changed by a general user. Can be done. Since the maintenance mode is such a special mode, further authentication is required before shifting to the maintenance mode.

As described above, the panel display 105b included in the "Remote Panel" of the device mode has the same display as the screen displayed on the panel 105 of the MFP 100. Therefore, if no special control is performed, the same screen as the panel display included in the “Remote Panel” in the maintenance mode will be displayed on the panel 105 of the MFP 100. This situation also applies to the panel display 105d included in the "Remote Panel" for authentication.

If the same screen is displayed on the panel 105 of the MFP100 regardless of whether it is the "Remote Panel" for authentication immediately before the transition to the maintenance mode or the "Remote Panel" in the maintenance mode after the transition to the maintenance mode, the administrator will select the "Remote Panel". Since the operation performed on the MFP 100 is displayed on the panel 105 of the MFP 100 as it is, a third party other than the administrator who sees the display on the panel 105 can know the confidential information related to the MFP 100 from the operation content. .. That is, leakage of confidential information may occur.

Therefore, in the present embodiment, when the ON / OFF button 184c is clicked in the device mode "Remote Panel", the detail pane 184 is changed from the device mode "Remote Panel" to the authentication "Remote Panel". On the other hand, the panel 105 of the MFP 100 is controlled to stop the screen update. Therefore, in this case, although the operating state of the MFP 100 is in the state of performing authentication immediately before shifting to the maintenance mode, the same screen as the panel display 105b in the "Remote Panel" of the device mode continues as it is on the panel 105. Is displayed. It should be noted that this display control is continuously performed after shifting to the maintenance mode until the maintenance mode is terminated and the device mode is returned.

FIG. 4 is a flowchart showing a procedure of main processing executed by the PC 10, particularly the CPU 12. This main process is executed by the CPU 12 after the login authentication is performed on the login authentication screen 190 of FIG. 2B. Hereinafter, in the description of the procedure of each process, the step is referred to as "S".

In FIG. 4, first, the CPU 12 executes the remote control screen display process (S1). The remote control screen is a “Remote Panel” displayed in the detail pane 184. Therefore, the remote control screen display process indicates the process of displaying the “Remote Panel” in the detail pane 184.

FIG. 5 shows a detailed procedure of the remote control screen display process. In FIG. 5, first, the CPU 12 transmits an http (s) request for the initial screen (S11). Here, the http (s) request is a request according to the http (s) protocol. The reason why the request according to the http (s) protocol is transmitted in this way is that since the destination of the request is EWS, it is necessary to send the request of the protocol that can be interpreted by EWS. The http (s) request for the initial screen is input from the network IF 20 to the network IF 108 via the communication network 40 and the router 32. Not limited to the http (s) request for the initial screen, data transmission from the PC 10 to the MFP 100 is performed through the same route. On the contrary, the data transmission from the MFP 100 to the PC 10 is performed through the reverse route.

Next, the CPU 12 receives the http (s) response and the virtual screen data transmitted by the EWS in response to receiving the http (s) request for the initial screen (S12). The http (s) response and virtual screen data are generated and transmitted by the initial screen transmission process (FIG. 8) of S47, which will be described later.

Next, the CPU 12 stores http (s) cgi in the data storage area 28 (S13). http (s) cgi are various scripts included in the http (s) response. Note that cgi is an abbreviation for common gateway interface. As various scripts, in the present embodiment, a non-operation timer script, a screen data request script, a screen press processing script, and a release processing script are generated (see S71 to S73 in FIG. 10). By executing this script, the CPU 12 can execute non-operation timer processing, http (s) cgi request transmission processing, and the like.

Further, the CPU 12 displays the received virtual screen data in the detail pane 184 (S14), and then ends the remote control screen display process. As a result, the “Remote Panel” as shown in FIG. 3A is displayed in the detail pane 184.

Returning to FIG. 4, the CPU 12 determines whether or not the non-operation timer has clocked a predetermined time (S2). Here, the "predetermined time" is, for example, 0.5 seconds. The non-operation timer is a timer whose start is instructed in S35 (FIG. 7) described later.

If it is determined in S2 that the non-operation timer has timed a predetermined time (S2: YES), the CPU 12 executes the screen update process (S3) and then proceeds to S4. On the other hand, when it is determined that the non-operation timer has not yet timed the predetermined time (S2: NO), the CPU 12 skips S3 and advances the process to S4.

FIG. 6 shows a detailed procedure of the screen update process. In FIG. 6, first, the CPU 12 transmits a screen update http (s) request (S21). Next, the CPU 12 receives the http (s) response and the virtual screen data transmitted by the EWS in response to the reception of the screen update http (s) request (S22). The http (s) response and virtual screen data are generated and transmitted by the screen data transmission process (FIG. 8) of S49 described later.

Then, the CPU 12 updates the virtual screen, that is, the "Remote Panel" based on the received virtual screen data (S23), and then ends the screen update process. As a result, the “Remote Panel” displayed in the detail pane 184 matches the current display screen of the panel 105 of the MFP 100.

Returning to FIG. 4, in S4, the CPU 12 determines whether or not the inside of the virtual screen has been pressed. In this determination, if it is determined that the inside of the virtual screen has been pressed (S4: YES), the CPU 12 executes the http (s) cgi request execution process (S5), and then proceeds to the process in S6. On the other hand, in this determination, when it is determined that the inside of the virtual screen is not pressed (S4: NO), the CPU 12 skips S5 and proceeds to the process of S6.

FIG. 7 shows a detailed procedure of http (s) cgi request execution processing. In FIG. 7, first, the CPU 12 stops the non-operation timer (S31). Stopping the non-operation timer in this way is to postpone the execution of the screen update process in S3 above so that the screen of the "Remote Panel" will not be updated until the http (s) cgi request execution process is completed. To do. If there is an icon or button at the pressed position in the virtual screen, the screen will change or the color of the button will change. The http (s) cgi request execution process is a process for realizing such a change in the mode of the display screen in the virtual screen. Therefore, if the screen update process is executed during the execution of the http (s) cgi request execution process, a discrepancy may occur between the virtual screen and the real screen of the panel 105. The process of S31 is provided to prevent this.

Next, the CPU 12 generates an http (s) cgi request (S32) and transmits the generated http (s) cgi request (S33). Here, the generated http (s) cgi request includes screen pressing information indicating that the screen has been pressed and coordinates of the pressed position (hereinafter referred to as "pressing coordinates").

Next, the CPU 12 receives the http (s) cgi response transmitted by the EWS in response to the http (s) cgi request, and executes the process according to the http (s) cgi response (S34). The http (s) cgi response is generated and transmitted by the screen pressing process (FIG. 8) of S51 described later.

Further, the CPU 12 ends the http (s) cgi request execution process after starting the non-operation timer (S35). After that, when the non-operation timer clocks the predetermined time (for example, 0.5 seconds), the screen update process of S3 is executed once.

Returning to FIG. 4, in S6 above, the CPU 12 determines whether or not the indicator has been lifted. The indicator is an object that is instructed to be pressed when the inside of the virtual screen is pressed. That is, the indicator includes both icons, buttons, parts of the background image, and the like that are meaningful and meaningless when pressed.

If it is determined in the determination of S6 that the indicator has been released (S6: YES), the CPU 12 executes the http (s) cgi request execution process (S7) and then returns the process to the above S2. On the other hand, in this determination, when it is determined that the indicator has not been released (S6: NO), the CPU 12 skips S7 and returns the process to S2. This http (s) cgi request execution process is the http (s) cgi request execution process shown in FIG. 7 above. However, the content of the generated http (s) cgi request differs between the case where the http (s) cgi request execution process is executed in S5 and the case where the http (s) cgi request execution process is executed in S7. That is, the http (s) cgi request generated in S5 includes screen press information and the like as described above, whereas the http (s) cgi request generated in S7 is released indicating that it has been released. It contains information and the coordinates of the released position (hereinafter referred to as "release coordinates").

FIG. 8 shows a procedure of main processing executed by the MFP 100, particularly the CPU 101. In FIG. 8, first, the CPU 101 displays a standby screen on the panel 105 (S41). The standby screen is, for example, the same screen as the panel display 105b of FIG. 3A.

Next, the CPU 101 sets the update stop flag to “OFF” (S42). The update stop flag is a flag for instructing the update stop of the screen of the panel 105. When the update stop flag is "ON", the update stop of the screen of the panel 105 is instructed, and when the update stop flag is "OFF", the update of the screen of the panel 105 is instructed.

Next, the CPU 101 determines whether or not the http (s) communication, that is, the data communication according to the http (s) protocol has been received (S43). In this determination, if it is determined that the http (s) communication has not been received (S43: NO), the CPU 101 determines whether or not the main body panel operation, that is, the user operation on the panel 105 and the key 106 has been detected. (S44). In this determination, if it is determined that the main body panel operation has been detected (S44: YES), the CPU 101 executes the main body panel process (S45) and then returns the process to the above S43. On the other hand, when it is determined that the operation of the main body panel has not been detected (S44: NO), the CPU 101 skips S45 and returns the process to S43.

FIG. 9 shows a detailed procedure of the main body panel processing. In FIG. 9, first, the CPU 101 determines whether or not the update stop flag is “ON” (S61). In this determination, if it is determined that the update stop flag is "ON" (S61: YES), the CPU 101 ignores the detected panel operation (S62) and then ends the main body panel processing. As described above, when the update stop flag is "ON", even if the user performs an operation on the panel 105 and the key 106, the operation is not accepted and is ignored. As a result, when the update stop of the screen of the panel 105 is instructed, the operation input to the main body panel by the user of the MFP 100 is prohibited. It is possible to prevent intentional setting changes.

On the other hand, when it is determined in the determination of S61 that the update stop flag is "OFF" (S61: NO), the CPU 101 determines whether or not the panel operation is pressed (S63). In this determination, if it is determined that the panel operation is pressing (S63: YES), the CPU 101 ends the main body panel processing after executing the screen pressing process (S64). On the other hand, in this determination, when it is determined that the panel operation is not pressed (S63: NO), the CPU 101 ends the main body panel process after executing the take-off process (S65).

FIG. 12 shows a detailed procedure of the screen pressing process. In FIG. 12, first, the CPU 101 determines whether or not the pressing coordinates are within the area of any button image (S90). In this determination, when it is determined that the pressing coordinates are within the area of any button image (S90: YES), the CPU 101 determines whether or not the update stop flag is “ON” (S91). In this determination, when the update stop flag is determined to be "OFF" (S91: NO), the CPU 101 switches the button image to the pressing mode (S92). The button image is, for example, an icon (“Fax” icon, “Copy” icon, etc.) or button (“Basic 1” button, “Custom1” button, etc.) in the panel display 105b of FIG. 3 (a). Then, switching the pressing mode means, for example, switching the color of the button image from the color of the non-pressing mode (normal mode) to a different color.

Next, the CPU 101 generates screen data, stores it in the RAM 103 (S93), and then proceeds to the process in S94. The screen data is screen data for displaying the "Remote Panel". The screen data stored in the RAM 103 is read out and used in the screen data transmission process described later based on FIG.

On the other hand, in the determination of S90, when it is determined that the pressing coordinates are not within the area of any of the button images (S90: NO), or in the determination of S91, when the update stop flag is determined to be "ON" ( S91: YES), the CPU 101 skips S92 and S93 and proceeds to S94.

In S94, the CPU 101 determines whether or not the screen pressing process is called by the http (s) request. In this determination, when it is determined that the screen pressing process is called by the http (s) request (S94: YES), the CPU 101 transmits the http (s) cgi response (S95) and then presses the screen. End the process. On the other hand, in this determination, when it is determined that the screen pressing process is not called by the http (s) request (S94: NO), the CPU 101 skips S95 and ends the screen pressing process.

Since the screen pressing process is called not only in S64 in the main body panel process of S45 but also in S51 described later, the process content is created for general purposes. That is, the determination of S94 and the processing of S95 are not necessary when called in S64, but are necessary when called in S49.

Since the release process of S65 is also called in S53 of FIG. 8 in addition to S65, the process content is created for general purposes in the same manner as the screen press process. Before the release process is described in detail with reference to FIG. 13, the process after S46 of the main process on the MFP100 side of FIG. 8 will be described.

In the above S43 of FIG. 8, when it is determined that the http (s) communication has been received (S43: YES), the CPU 101 determines whether the http (s) communication is an http (s) request for the initial screen. Is determined (S46). In this determination, when it is determined that the http (s) communication is an http (s) request for the initial screen (S46: YES), the CPU 101 executes the initial screen transmission process (S47), and then performs the process. Return to S43.

FIG. 10 shows a detailed procedure of the initial screen transmission process. In FIG. 10, first, the CPU 101 generates a non-operation timer script (S71). The non-operation timer script is a program that causes the browser to operate the non-operation timer and perform, for example, the processing of S3.

Next, the CPU 101 generates a screen data request script (S72). The screen data request script is a program that causes a browser to execute screen data request processing and generate an http (s) request including a screen data request, for example, an http (s) request for screen update to be transmitted in S21.

Next, the CPU 101 generates a screen pressing processing script and a release processing script (S73). The screen pressing processing script causes the browser to execute the screen pressing processing, for example, the judgment processing of S4 and the processing of S31 to S33 (FIG. 7) in the processing of S5 to be executed when "YES" in this judgment processing. It is a program to be done. Further, the release processing script causes the browser to execute the release processing, for example, the determination processing of S6 and the processing of S31 to S33 in the processing of S7 to be executed when "YES" in this determination processing. It is a program.

Next, the CPU 101 reads out the screen data (S74). This screen data is the screen data of the screen currently displayed on the panel 105 of the MFP 100. When the screen is displayed on the panel 105, the MFP 100 generates the screen data, stores the screen data in the RAM 103, reads the screen data, and displays the screen data on the panel 105. Therefore, in S74, the CPU 101 reads the screen data from the RAM 103.

Next, the CPU 101 generates an http (s) response and transmits it together with the read screen data (S75). This http (s) response is a response to the http (s) request for the initial screen of S11 (FIG. 5). This http (s) response includes the script generated in S71 to S73 and information indicating that the screen data is transmitted together.

Next, the CPU 101 determines whether or not the setting for stopping the update of the main body panel is made while the "Remote Panel" is being used (S76). This setting is made on the MFP100 side. The operation of this setting may be performed by, for example, the user of the MFP 100 in the device setting, or may be performed by the administrator from the “Remote Panel” of the device mode. In addition, an on / off button is provided in the device mode "Remote Panel" to indicate on / off of the setting to stop the main panel update, and the administrator clicks the on / off button to stop the main panel update. It may be possible to select the setting to be performed and the setting to cancel the stop setting.

In the determination of S76, if it is determined that the main body panel update is stopped while the "Remote Panel" is being used (S76: YES), the CPU 101 sets the update stop flag to "ON" (S76). After S77), the initial screen transmission process is terminated. On the other hand, when it is determined that the setting for stopping the update of the main body panel is not made while using the "Remote Panel" (S76: NO), the CPU 101 skips S77 and ends the initial screen transmission process.

Returning to FIG. 8, when it is determined in the determination of S46 that the communication of http (s) is not the http (s) request for the initial screen (S46: NO), the CPU 101 updates the screen of the communication of http (s). It is determined whether or not the request is for http (s) request (S48). In this determination, when it is determined that the http (s) communication is an http (s) request for screen update (S48: YES), the CPU 101 executes the screen data transmission process (S49), and then performs the process as described above. Return to S43.

FIG. 11 shows a detailed procedure of the screen data transmission process. In FIG. 11, first, the CPU 101 reads out the screen data (S81). In S81, the screen data stored in the RAM 103 is read out in S93 (FIG. 12) above or S106 described later.

Next, the CPU 101 generates an http (s) response and transmits it together with the read screen data (S82), and then ends the screen data transmission process. The processing of S82 is different from the processing of S75 only in that the http (s) response is the response to the screen update http (s) request of S21 (FIG. 6). Omit.

Returning to FIG. 8, when it is determined in the determination of S48 that the communication of http (s) is not the http (s) request for screen update (S48: NO), the CPU 101 presses the screen for the communication of http (s). It is determined whether or not the request includes http (s) cgi including information (S50). In this determination, when it is determined that the http (s) communication is an http (s) cgi request including screen pressing information (S50: YES), the CPU 101 executes the screen pressing process (S51). , The process is returned to S43. Since the screen pressing process has been described in detail in S64 included in the process of S45, the description thereof will be omitted.

In the judgment of S50, when it is determined that the http (s) communication is not an http (s) cgi request including screen press information or the like (S50: NO), the CPU 101 determines that the http (s) communication is the release information. It is determined whether or not the request is an http (s) cgi request including the above (S52). In this determination, when it is determined that the http (s) communication is an http (s) cgi request including the release information (S52: YES), the CPU 101 executes the release process (S53). , The process is returned to S43. On the other hand, when it is determined in the determination of S52 that the communication of http (s) is not the http (s) cgi request including the release information (S52: NO), the CPU 101 returns the process to the above S43.

FIG. 13 shows a detailed procedure of the take-off process. In FIG. 13, first, the CPU 101 determines whether or not the release coordinates are within the area of any button image (S101). In this determination, when it is determined that the release coordinates are within the area of any of the button images (S101: YES), the CPU 101 determines whether or not the update stop flag is “OFF” (S102). .. In this determination, when the update stop flag is determined to be "OFF" (S102: YES), the CPU 101 determines whether or not the button of the button image in which the release coordinates are located in S101 switches the screen. Judgment (S103). In this determination, when it is determined that the button is a button for switching the screen (S103: YES), the CPU 101 determines whether or not the main body panel screen to be displayed next is the above-mentioned specific screen (S104). In this determination, when it is determined that the main body panel screen to be displayed next is a specific screen (S104: YES), the CPU 101 sets the update stop flag to "ON" (S105), and then proceeds to the process in S106.

In S106, the CPU 101 generates and stores screen data in the same manner as in S93. Since the screen data is the screen data for displaying the "Remote Panel" as described above, the CPU 101 displays the updated screen, that is, the specific screen, even if the update stop flag is "ON" in S106. Generate screen data for display. As described above, in S106, since the screen data for displaying the "Remote Panel" is generated, the CPU 101 does not control the switching of the display screen with respect to the panel 105. Therefore, the screen of the panel 105 is not switched to the specific screen, and the screen immediately before the screen is switched to the specific screen is continuously displayed on the panel 105.

Next, the CPU 101 determines whether or not the release process is called by the http (s) request (S107). In this determination, if it is determined that the release process was called by an http (s) request (S107: YES), the CPU 101 generates and transmits an http (s) cgi response (S108), and then after that. The release process is completed. On the other hand, in this determination, when it is determined that the release process is not called by the http (s) request (S107: NO), the CPU 101 skips S108 and ends the release process.

On the other hand, when it is determined in the determination of S104 that the main body panel screen to be displayed next is not a specific screen (S104: NO), the CPU 101 switches the screen display of the panel 105 to the screen instructed by the button (S104: NO). S109) After that, the process proceeds to S106. The button is, for example, the “Fax” icon in the panel display 105b of FIG. 3A. When the "Fax" icon is pressed, the panel display 105b switches to the display of the operation panel for "Fax". When the process proceeds from S109 to S106, in S106, the CPU 101 generates and stores screen data of the same screen as the screen display of the panel 105.

On the other hand, when it is determined in the determination of S103 that the button is not a button for switching the screen (S103: NO), the CPU 101 switches the button image in the display screen of the panel 105 to a normal mode (S110). After that, the process proceeds to S106. Also in this case, in S106, the CPU 101 generates and stores screen data of the same screen as the screen display of the panel 105. As a result, the button image of the released button is switched from the pressing mode to the normal mode on both the panel 105 and the "Remote Panel".

On the other hand, when it is determined in the determination of S102 that the update stop flag is "ON" (S102: NO), the CPU 101 proceeds to the process of S106. In this case, the CPU 101 does not control the switching of the display screen on the panel 105, as in the case where the process proceeds from S104 to S106 via S105. Therefore, the screen of the panel 105 is not switched to another screen, and the screen when the process proceeds to S102 is continuously displayed on the panel 105 as it is.

If the display screen of the panel 105 is not switched in this way, the user of the MFP 100 may feel uncomfortable. In order to deal with this, it is preferable to notify the user of the MFP 100 that the screen update of the panel 105 is currently stopped. Any method may be adopted as the notification method, such as display on the panel 105 or notification by voice.

As described above, the MFP 100 of the present embodiment includes a network IF 108, a panel 105, and a CPU 101. Then, when the PC 10 is remotely connected via the network IF 108, the CPU 101 transmits screen data for displaying the same screen as the display screen displayed on the panel 105 on the PC 10 to the PC 10, and remotely from the PC 10. After receiving the access, the display process of the display screen corresponding to the remote access is executed, and the image forming apparatus shifts to the maintenance mode in response to the shift instruction to the maintenance mode included in the received remote access, the maintenance mode is entered. The screen update from the display screen displayed on the panel 105 is stopped immediately before the transition, and the screen data of the screen displayed on the panel 105 in the maintenance mode when not remotely connected is displayed on the PC10 when remotely connected. Send to.

As described above, in the MFP 100 of the present embodiment, it is possible to deal with the case where it is desired to prohibit the operation input of another person from the image forming apparatus or the case where the confidential information is leaked to the other person after the start of the remote connection. ..

Incidentally, in the present embodiment, the MFP 100 is an example of an "image forming apparatus". The network IF108 is an example of a "communication interface". The panel 105 is an example of a “display unit”. The CPU 101 is an example of a “control unit”. The PC 10 is an example of an "information processing device". The maintenance mode is an example of a "predetermined mode".

Further, the MFP 100 further includes a panel 105 and a key 106, and the CPU 101 does not accept a user operation from the panel 105 and the key 106 when the screen update is stopped.

As a result, it is possible to prohibit the operation input from the panel 105 and the key 106 of another person when the screen update is stopped.

By the way, the panel 105 and the key 106 are examples of the "user interface".

The present invention is not limited to the above embodiment, and various modifications can be made without departing from the spirit of the present invention.

(1) In the above embodiment, the MFP 100 has been described as an example of the image forming apparatus, but the image forming apparatus is not limited to the MFP 100, and the image forming apparatus may be a single printer, a scanner, or a copier.

(2) In the above embodiment, the CPU 101 has been described as an example of the control unit, but the control unit may have a CPU and a dedicated circuit. Examples of the dedicated circuit include an ASIC (Application Specific Integrated Circuit) and an FPGA (Field Programmable Gate Array).

10 ... PC, 12 ... CPU, 14 ... storage, 16 ... user IF, 18 ... display, 20 ... network IF, 100 ... MFP, 101 ... CPU, 102 ... ROM, 103 ... RAM, 105 ... panel, 106 ... key , 108 ... Network IF.

Claims (5)

Communication interface and
Display and
Control unit and
It is an image forming apparatus equipped with
The control unit
When the information processing device is remotely connected via the communication interface,
Screen data for displaying the same screen as the display screen displayed on the display unit by the information processing device is transmitted to the information processing device.
Upon receiving the remote access from the information processing device, the display process of the display screen corresponding to the remote access is executed.
The display displayed on the display unit immediately after the image forming apparatus shifts to the predetermined mode in response to the shift instruction to the predetermined mode included in the received remote access and immediately before the shift to the predetermined mode. Stop updating the screen from the screen,
The screen data of the screen to be displayed on the display unit in the predetermined mode when the remote connection is not made is transmitted to the information processing apparatus when the remote connection is made.
Image forming device. The predetermined mode is a maintenance mode.
The image forming apparatus according to claim 1. The image forming apparatus further
Equipped with a user interface
The control unit
When the screen update is stopped, the user operation from the user interface is not accepted.
The image forming apparatus according to claim 1 or 2. The control unit
When the screen update is stopped, the user is notified that the screen update is stopped.
The image forming apparatus according to any one of claims 1 to 3. The control unit
When a remote access for canceling the stop of the screen update is received from the information processing device, the stop of the screen update is canceled.
The image forming apparatus according to any one of claims 1 to 4.

Images