Image forming device

Abstract

To provide an image forming apparatus that can receive remote control from an information processing apparatus, and allows a user to easily see an image included in a remote screen, thereby increasing convenience for the user.SOLUTION: When firmware 20 of an MFP 10 is instructed that an operation for a file acquisition button included in a remote screen is received from a PC 30 through a communication IF 16, the firmware transmits an electronic file of a FAX reception image displayed as a preview image to the PC 30 through the communication IF 16. With this, when the operation of the file acquisition button is received on the remote screen, data for transmission indicating the FAX reception image is transmitted to the PC 30 from the MFP 10.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology for an image forming apparatus that can accept remote control by an information processing apparatus. [Background technology]

[0002] Patent Document 1 describes a technology in which a remote screen that virtually displays the user interface of an image forming device is displayed on a remote information processing device, and the image forming device is remotely controlled by operating the remote screen. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-10265 Summary of the Invention [Problem to be solved by the invention]

[0004] In the remote operation of an image forming apparatus described in Patent Document 1, it is assumed that a remote screen virtually showing the user interface of the image forming apparatus is displayed on an information processing apparatus. When a display target image is displayed on the user interface, the display target image is also displayed on the remote screen of the information processing apparatus. In this case, depending on the size of the user interface and the display mode of the image on the user interface, the display target image displayed on the remote screen may be difficult to see. For example, if only a portion of the display target image is displayed on the user interface, only a portion of the display target image will also be displayed on the remote screen. In addition, for example, if the display target image is reduced and displayed on the user interface, the reduced display target image will also be displayed on the remote screen. [Means for solving the problem]

[0005] In order to solve the above problems, an image forming apparatus disclosed as the present embodiment includes a user interface, a communication interface, and a controller. When the controller receives a first request from a device connected via the communication interface, the controller executes a first transmission process to transmit remote screen data to the device that has requested the first request, the first request being a request to display a remote screen, the remote screen data being data for displaying the remote screen on the device that has requested the first request, and the remote screen being a screen that is displayed on the device that has requested the first request and that virtually reproduces the user interface. When the controller receives a first operation via the user interface, the controller executes a screen display process to display a first operation screen on the user interface, the first operation screen being a screen including an image to be displayed, and when the controller receives, after the first transmission process, an instruction from the device that sent the request for the first request via the communication interface indicating that the first operation has been virtually performed on the remote screen, the controller executes a second transmission process to transmit remote screen data of a second operation screen via the communication interface to the device that sent the request for the first request, the second operation screen being a screen that can accept a second operation, and the second operation being an operation for transmitting data indicating the image to be displayed to the device that sent the request for the first request. When the controller receives an instruction from the device that sent the request for the first request via the communication interface that the second operation has been accepted, the controller executes a third transmission process to transmit data indicating the image to be displayed via the communication interface to the device that sent the request for the first request.

[0006] In the above configuration, when the controller accepts a first operation via the user interface, it displays a first operation screen including an image to be displayed on the user interface. After transmitting remote screen data to the device that issued the request for the first request, when the controller accepts an instruction via the communication interface from the device that issued the request for the first request indicating that the first operation has been virtually performed on the remote screen, the controller transmits remote screen data of a second operation screen, which is a remote screen corresponding to the first operation screen, via the communication interface to the device that issued the request for the first request. When the controller is instructed via the communication interface from the device that issued the request for the first request that a second operation has been accepted, the controller transmits data indicating the image to be displayed to the device that issued the request for the first request via the communication interface. Thus, when the second operation is accepted on the second operation screen, which is a remote screen, data indicating the image to be displayed is transmitted from the image forming apparatus to the device that issued the request for the first request. Therefore, the requesting device of the first request can display the image to be displayed using the received data indicating the image to be displayed, and even if the image to be displayed on the remote screen is difficult to see, it is possible to display the image to be displayed on a separate screen, for example, thereby improving user convenience. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a configuration diagram of an image forming system. [Figure 2] 10 is a timing chart illustrating a process when a request to start remote display control is made. [Figure 3] FIG. 10 is a diagram illustrating an administrator screen. [Figure 4] 10 is a flowchart illustrating processing in the MFP under remote display control. [Figure 5] FIG. 10 is a diagram illustrating a remote screen. [Figure 6] 5 is a flowchart illustrating the process of S38 in FIG. 4. [Figure 7] FIG. 10 is a diagram illustrating a remote screen corresponding to the FAX operation reception screen. [Figure 8]FIG. 10 is a diagram illustrating a FAX execution screen displayed on a user interface. [Figure 9] FIG. 10 is a diagram illustrating a remote screen corresponding to the FAX execution screen. [Figure 10] 5 is a flowchart illustrating the process of S40 in FIG. 4. [Figure 11] 10 is a flowchart illustrating processing of a PC. [Figure 12] FIG. 10 is a diagram illustrating a state in which the entire screen showing the electronic file is displayed together with the remote screen. DETAILED DESCRIPTION OF THE INVENTION

[0008] (First embodiment) An image forming system 100 according to this embodiment will be described with reference to the drawings. The image forming system 100 shown in FIG. 1 includes an MFP 10 and PCs 30 and 50. MFP is an abbreviation for multifunction peripheral. The MFP 10 and the PCs 30 and 50 are connected to a network 200 and are capable of communicating with each other through the network 200. The network 200 is a LAN or the Internet. In this embodiment, the MFP 100 is an example of an image forming apparatus.

[0009] Next, we will explain the configuration of the MFP 10. The MFP 100 includes a controller 11, a memory 12, a printer 13, a scanner 14, a FAX-IF 15, a communication IF 16, a user IF 17, and a bus 18. IF is an abbreviation for interface.

[0010] The communication IF 16 connects the MFP 10 to the network 200 in accordance with a predetermined communication protocol. The user IF 17 is an interface that exists between the user who directly operates the MFP 10 and the controller 11, and has a touch panel 171 and operation keys 172 that are physical keys.

[0011] The printer 13 performs a printing operation to print an image on a recording medium such as a sheet or a disk. The printer 13 may use an inkjet method, an electrophotographic method, or the like as its recording method. The scanner 14 performs a scanning operation to read an image recorded on an original and generate image data. The FAX-IF 15 performs a FAX operation to send and receive image data in a method conforming to a FAX protocol. The MFP 10 may also be capable of performing a composite operation that combines multiple operations. A copy operation that combines a print operation by the printer 13 and a scan operation by the scanner 14 is an example of a composite operation.

[0012] The controller 11 is configured with a CPU, an ASIC (application specific integrated circuit), etc., and controls the operations of the printer 13, the scanner 14, the FAX-IF 15, the communication IF 16, and the user IF 17. The memory 12 has a data storage area. The data storage area is an area for storing data necessary for executing programs, etc. The memory 12 is configured by combining RAM, ROM, SSD, HDD, etc. Buffers provided in the controller 11 and used when executing various programs may also be considered part of the memory 12. The memory 12 may be a storage medium readable by the controller 11. A storage medium readable by the controller 11 is a non-transitory medium. In addition to the above examples, non-transitory media also include recording media such as CD-ROMs and DVD-ROMs. Non-transitory media are also tangible media. On the other hand, electrical signals carrying programs downloaded from servers on the Internet, etc., are computer-readable signal media, which are a type of computer-readable medium, but are not included in non-transitory computer-readable storage media.

[0013] The memory 12 stores firmware 20 as a program executable by the controller 11. In the following description, the controller 11 executing the program may be referred to simply as the program name. For example, the term "firmware" is used to mean "the controller 11 executing the firmware 20." In this embodiment, the term primarily refers to the processing of the controller 11 in accordance with instructions written in the program. In other words, processes such as "determine," "extract," "select," "calculate," "decide," "identify," "acquire," "receive," and "control" in the following description represent the processing of the controller 11. Note that "acquire" is used as a concept that does not necessarily require a request. In other words, the process of the controller 11 receiving data without a request is also included in the concept of "the controller 11 acquiring data." Furthermore, "data" in this specification refers to a bit string that can be read by the controller. Data with essentially the same meaning but different formats are treated as the same data. The same applies to "information" in this specification.

[0014] The firmware 20 also functions as a web server for displaying a predetermined web page on the PC 30. The firmware 20 can also provide remote screen control to the PCs 30 and 50. The remote screen control is a function that causes the PCs 30 and 50 to display a remote screen that simulates the user IF 17 of the MFP 10, and allows the MFP 10 to be remotely operated by performing virtual operations on this remote screen.

[0015] Management information 25 is stored in the data storage area of ​​memory 12. The management information 25 records authentication information such as login names and passwords in association with devices that can access MFP 10. Setting information 26 is stored in the data storage area of ​​memory 12. The setting information 26 records information related to remote screen control settings.

[0016] Next, we will explain the configuration of PC 30. PC 30 has a communication IF 31, memory 32, controller 33, display 34, and user IF 35. The units 31, 32, 33, and 35 of PC 30 have the same configuration as controller 11, memory 12, communication IF 16, and user IF 17 of MFP 10, and therefore their explanation will be omitted.

[0017] The memory 32 stores an OS 40 and a browser 41. The browser 41 is a program that, under the execution of the OS 40, causes the controller 33 to display on the display 34 an image corresponding to the web page data transmitted from the MFP 10. The PC 50 has the same configuration as the PC 30, and therefore a description thereof will be omitted.

[0018] Next, the processing procedure when PC 30 requests the start of remote screen control will be described with reference to Figure 2. MFP 10 displays an operation screen on user IF 17 and changes the display of the operation screen in accordance with operations via user IF 17, the operating status of MFP 10, etc. The process of changing the operation screen is executed in parallel with the process of Figure 2. The operation screen includes an execution screen that indicates that printing, scanning, etc. is in progress, an instruction screen for receiving execution instructions for copying, scanning, etc., a setting screen for changing various settings, a status screen that indicates the status of MFP 10, an execution instruction screen, a standby screen that waits for an instruction to display the setting screen, etc.

[0019] 2, in step 10 (hereinafter, step will be simply referred to as "S"), browser 41 of PC 30 transmits a request for web page data to MFP 10. The web page data requested in S10 is web page data for displaying a home screen when firmware 20 functions as a web server. For example, browser 41 transmits the request to firmware 20 when it receives input of a URL specifying firmware 20 from the user. Communication between browser 41 and firmware 20 is performed in accordance with the http(s) protocol.

[0020] In S11, the firmware 20 transmits web page data to the PC 30. Upon receiving the web page data, the browser 41 displays the web page indicated by the web page data received in S12 on the display 34. In this embodiment, the browser 41 displays a home screen as the web page on the display 34.

[0021] When a login operation to the MFP 10 is performed on the home screen, the browser 41 transmits the login password and the like to the firmware 20. When a login permission response is received from the MFP 10, the browser 41 displays an administrator screen 300, which is a web page, on the display 34, as shown in Fig. 3. The administrator screen 300 includes an item display area 301 and a function display area 302.

[0022] When a selection operation of the "Remote Screen Control" item 303 included in the item display area 301 is accepted via the user IF 35, the browser 41 requests the MFP 10 to start remote screen control in S13. Upon receiving the request to start remote screen control, the firmware 20 transmits web page data for updating the web page in S14. This web page data includes an executable program that can be interpreted by the browser 41. The executable program is a script program, such as JavaScript.

[0023] In S15, a request is made to the MFP 10 to issue a token. The token is information for authenticating the device that executes the remote screen control, and in this embodiment is a one-time token created based on the authentication information. When the firmware 20 receives the token issuance request, it issues the token to the PC 30. At this time, the firmware 20 may request authentication information from the PC 30.

[0024] In S16, the firmware 20 issues a token to the PC 30. At this time, if information indicating that a token has already been issued is stored in the memory 12, the firmware 20 determines that the token has not yet been issued, and does not need to send the token. Upon receiving the token issued by the MFP 10, the browser 41 requests display of a remote screen together with the issued token in S17. In this embodiment, the request to display the remote screen sent by the browser 41 in S17 is an example of a first request.

[0025] If the firmware 20 determines that the token transmitted from the PC 30 is valid, it responds in S18 with permission to display the remote screen. If the firmware 20 determines that the transmitted token is invalid, it responds that it has refused to execute the remote screen. For example, if the token is valid too long after its issuance time, or if the token is a forged token, it is determined to be invalid.

[0026] Next, a description will be given of the procedure for remote screen control executed between the MFP 10 and the PC 30 when display of the remote screen is permitted. Fig. 4 shows the process executed by the firmware 20 of the MFP 10 when display of the remote screen is permitted, and the firmware 20 is the subject.

[0027] In S30, a standby screen is displayed on the user IF 17. The standby screen includes a FAX instruction icon, a copy instruction icon, and a scan instruction icon. The FAX instruction icon is an icon that accepts an operation when causing the MFP 10 to perform a FAX operation. The copy instruction icon is an icon that accepts an operation when causing the MFP 10 to perform a copy operation. The FAX instruction icon is an icon that accepts an operation when causing the MFP 10 to perform a scan operation. When any of the icons is operated on the standby screen, the standby screen is switched to a FAX operation acceptance screen, a copy operation acceptance screen, or a scan operation acceptance screen depending on the icon that was operated.

[0028] In S31, it is determined whether an initial screen request has been received from the PC 30 via the communication IF 16. The initial screen request is a request to transmit remote screen data corresponding to the standby screen to the PC 30, which is the requesting device.

[0029] If the determination in S31 is affirmative, the process proceeds to S33, where an initial screen transmission process is executed. The initial screen transmission process is a process for transmitting an html script and remote screen data corresponding to the standby screen to the requesting device, PC 30. The html script is a program for causing the browser 41 to execute various processes according to operations accepted on the remote screen displayed on PC 30. When the process in S33 is completed, the process returns to S31.

[0030] When the PC 30 receives remote screen data corresponding to the standby screen and an HTML script from the MFP 10 via the communication IF 16, the PC 30 displays a remote screen 330 including the standby screen. FIG. 5 shows the remote screen 330 displayed on the display 34 of the PC 30 when the standby screen is displayed on the user IF 17. The remote screen 330 is displayed in the function display area 302 on the administrator screen 300. The remote screen 330 includes a screen display area 331 and an operation key display area 332. The screen display area 331 displays the same screen as the operation screen (here, the standby screen) currently displayed on the user IF 17 of the MFP 10. The operation key display area 332 displays button images that resemble the operation keys 172, which are physical keys provided on the user IF 17. Information indicating that a virtual operation on the user IF 17 has been executed on the remote screen 330 is notified to the MFP 10. The remote screen 330 also includes an end button 333.

[0031] The data indicating the operation screen, operation keys, and end button included in the remote screen data for displaying the remote screen 330 may be in the same data format, such as raster data, or may be in another data format. The data indicating the operation screen, operation keys, and end button may be in different data formats. Alternatively, the firmware 20 may transmit only data indicating the operation screen to the browser 41 as remote screen data, and the browser 41 may interpret the execution program to display the remote screen by superimposing data indicating the operation keys and end button on the remote screen data. Alternatively, the firmware 20 may transmit data indicating the operation screen and operation keys to the browser 41 as remote screen data, and the browser 41 may interpret the execution program to superimpose data indicating the end button on the remote screen data. Furthermore, instead of transmitting the remote screen data to the browser 41, the firmware 20 may transmit web page data for displaying the entire administrator screen 300, including the remote screen 330, to the browser 41.

[0032] 4, if a negative decision is made in S31, the process proceeds to S32, where it is determined whether or not a screen update request has been received from PC 30 via communication IF 16. The screen update request is a request to MFP 10 for remote screen data for updating remote screen 330 currently being displayed on PC 30.

[0033] If the determination in S32 is affirmative, the process proceeds to S35, where a screen data transmission process is executed. The screen data transmission process is a process for transmitting an html script and remote screen data corresponding to the updated screen to PC 30. The remote screen data transmitted to PC 30 in S35 is, for example, data generated in the process of S37 or S38, which will be described later. When PC 30 receives the remote screen data together with the html script, it updates the currently displayed remote screen to the received new remote screen. When the process of S35 ends, the process returns to S31.

[0034] If a negative judgment is made in S32, the process proceeds to S34, in which it is judged whether or not a request including press information has been received from the PC 30 via the communication IF 16. The press information is information indicating that a certain position on the remote screen 330 displayed on the PC 30 has been pressed, and includes press coordinate information. The press coordinate information is information indicating the position on the remote screen 330 that has been pressed.

[0035] If the determination in S34 is affirmative, the process proceeds to S37, where a pressing process is executed. The pressing process is a process for executing a process corresponding to an operation specified by the pressing coordinate information on the MFP 10 and transmitting an html script generated in accordance with the specified operation to the PC 30. In the pressing process, it is determined whether the received pressing coordinate information is within the area of ​​any operation icon or operation key on the remote screen 330. Specifically, the pressing coordinate information is converted into coordinates indicating the pressing position on the user IF 17 of the MFP 10, and it is determined whether the converted pressing coordinates correspond to an operation icon or operation key 172 displayed on the touch panel 171 of the user IF 17.

[0036] If the pressed coordinates correspond to an operation icon on the touch panel 171, the corresponding operation icon displayed on the user IF 17 is switched to a pressed state that indicates the state when pressed. For example, as an example of the pressed state, the color of the operation icon is changed, or the shape of the operation icon is changed to a pressed-in shape.

[0037] Then, remote screen data virtually showing the current user IF 17 is generated and stored in memory 12. Specifically, remote screen data including a screen displayed on user IF 17 with the changed pressing manner is created. Furthermore, an http(s) response is sent to PC 30. Note that if the pressed coordinates correspond to an operation icon or operation key 172 on touch panel 171, the body of the http(s) response includes a screen update script. The screen update script is a CGI script for instructing PC 30 to send an http(s) request, which is a request for a screen update, to MFP 10. When the processing of S37 ends, the process returns to S31.

[0038] If a negative judgment is made in S34, the process proceeds to S36, where it is judged whether or not lift-off information has been received from the PC 30 via the communication IF 16. The lift-off information is information indicating that a lift-off operation has been performed on the remote screen 330 displayed on the PC 30. The lift-off information includes lift-off coordinate information. The lift-off coordinate information is information indicating the position on the remote screen 330 where the indicator that was in contact has been lifted. If a positive judgment is made in S36, the process proceeds to S38, where lift-off processing is executed. The lift-off processing is a series of processes for executing processing according to the lift-off coordinate information on the MFP 10 and transmitting an html script to the PC 30. If a negative judgment is made in S36, the process returns to S31.

[0039] Here, the detachment processing executed in S38 will be described using as an example a case where a standby screen is displayed on the user IF 17, causing the remote screen 330 shown in Fig. 5 to be displayed on the PC 30. When the FAX instruction icon on the remote screen 330 shown in Fig. 5 is operated, a request including detachment coordinate information is sent from the PC 30 to the MFP 10. The firmware 20 of the MFP 10 makes a positive determination in S36 and executes the detachment processing in S38.

[0040] 6 is a flowchart illustrating the procedure for the lift-up process in S38. In S50, it is determined whether the received lift-up coordinate information is within the area of ​​any operation icon or operation key on the remote screen 330. If an affirmative determination is made in S50, the process proceeds to S51, where it is determined whether the lift-up operation within the area determined in S50 is an operation for switching the screen currently displayed on the user IF 17. Since the FAX instruction icon is an icon that accepts a screen switching operation, an affirmative determination is made in S51, and the process proceeds to S52. In S52, the standby screen displayed on the user IF 17 is switched to a FAX operation acceptance screen (not shown).

[0041] When the process of S52 is completed, the process proceeds to S54, where remote screen data corresponding to the screen of the user IF 17 switched by the process of S52 is generated and stored in the memory 12. In the above example, remote screen data corresponding to the FAX operation reception screen is generated.

[0042] In S55, an http(s) response including a screen update script is sent to the PC 30 via the communication IF 16. The screen update script is a CGI script that instructs the PC 30 to request the remote screen data generated in S54 from the MFP 10.

[0043] When the browser 41 of the PC 30 receives the http(s) response from the MFP 10 in S55, it sends a screen update request to the MFP 10 using a screen update script. When the firmware 20 of the MFP 10 receives the screen update request from the PC 30 (S32: YES), it performs a screen data transmission process to transmit remote screen data in S35. When the PC 10 receives the remote screen data, it displays on the display 34 a remote screen 330 corresponding to the FAX operation acceptance screen shown in FIG. 7.

[0044] As shown in FIG. 7, the FAX operation acceptance screen 400 included in the remote screen 330 includes a send icon 401 and a receive icon 402. The send icon 401 is an icon that accepts an operation by the user when sending an image to be sent by FAX. The receive icon 402 is an icon that accepts an operation by the user when receiving a received FAX image saved on a server (not shown) and storing it in the memory 12. When the send icon 401 and the receive icon 402 are operated on the FAX operation acceptance screen displayed on the user IF 17, the screen transition is the same as that of the operation accepted on the remote screen 330. The http(s) response includes an electronic file acquisition script. The electronic file acquisition script will be described later.

[0045] On the other hand, after making a positive determination in S50 and S51, if the operation specified by the lift-off information is not an operation for switching the screen (S51: NO), the firmware 20 of the MFP 10 proceeds to S53, where it changes the icon of the user IF 17, which has been changed to the pressed state by the pressing process, to the normal state. If the firmware 20 proceeds to S55 after the processing of S50 or S53, it sends an https response not including a screen update script to the PC 30 via the communication IF 16 in S55.

[0046] When the reception icon 402 on the FAX operation reception screen 400 is operated on the remote screen 330 (S36: YES), the firmware 20 executes a release process in S38. If an affirmative determination is made in S50 and S51 of FIG. 6, the FAX operation reception screen displayed on the user IF 17 is switched to the FAX execution screen 410 shown in FIG. 8 in S52. The FAX execution screen 410 is a screen for accepting instruction operations related to FAX operations. Alternatively, when the reception icon 402 is operated on the remote screen 330, a list screen displaying a list of received FAX images may be displayed, and when a selection operation of a received FAX image is accepted on this list screen, the FAX execution screen 410 may be displayed on the user IF 17.

[0047] FAX execution screen 410 includes a preview area 411 in which a portion of the received FAX image is displayed. The received FAX image displayed in preview area 411 can be scrolled downward by operating scroll key 412. In other words, only a portion of the received FAX image is displayed on FAX execution screen 410, and the entire received FAX image is not displayed.

[0048] When the process proceeds to S54 after the process of S52 is completed, in S54, remote screen data corresponding to the FAX execution screen 410 switched by the process of S52 is generated and stored in the memory 12. In S55, an http(s) response is sent to the PC 30.

[0049] When the browser 41 of the PC 30 receives the http(s) response from the MFP 10, it sends a screen update request to the MFP 10 using a screen update script. When the firmware 20 of the MFP 10 receives the screen update request from the PC 30 (S32: YES), it performs a screen data transmission process to transmit remote screen data in S35. When the PC 10 receives the remote screen data, it displays the remote screen 330 shown in FIG. 9 on the display 34.

[0050] 9 shows a remote screen 330 including a FAX execution screen 420. On the remote screen 330 shown in FIG. 9, a FAX execution screen 420 corresponding to the FAX execution screen 410 displayed on the user IF 17 is displayed in a screen display area 331. The FAX execution screen 420 includes a preview area 421 corresponding to the preview area 411 displayed on the user IF 17. In this embodiment, a file acquisition button 430, which is an additional icon, is added below the screen display area 331 on the remote screen 330. The file acquisition button 430 is an icon that is not included on the FAX execution screen 410 displayed on the user IF 17. The file acquisition button 430 is an icon that, when operated by a user on the remote screen 330, causes the MFP 10 to transmit an http(s) response requesting acquisition of an electronic file of the image to be displayed (here, a received FAX image) displayed in the screen display area 331. That is, the remote screen data generated in S54 is data for displaying a remote screen 330 in which a file acquisition button 430 is added to the FAX execution screen 410 currently displayed on the user IF 17. In this embodiment, the received FAX image displayed in the preview area is an example of an image to be displayed.

[0051] In this embodiment, the electronic file acquisition script included in the http(s) response displays a file acquisition button 430 on the remote screen 330. If the screen displayed on the user IF includes a preview area 411, the electronic file acquisition script generates remote screen data for displaying a remote screen with the file acquisition button 430 added. Therefore, the FAX execution screen 420 shown in FIG. 9 includes the file acquisition button 430. On the other hand, the FAX operation acceptance screen displayed on the user IF 17 does not include the preview area 411, so the remote screen 330 shown in FIG. 7 does not include the file acquisition button 430. Operations on the remote screen 330 on the FAX execution screen 420 other than operations on the file acquisition button 430 result in the same screen transition as operations on the user IF 17 on the FAX execution screen 410 displayed on the user IF 17.

[0052] The browser 41 executes an electronic file acquisition script in response to an operation on the file acquisition button 430 on the remote screen 330, thereby transmitting an electronic file acquisition request to the MFP 10. When the firmware 20 of the MFP 10 receives the electronic file acquisition request (S39: YES), the process proceeds to S40, where the firmware 20 executes an electronic file transmission process.

[0053] Note that, when the screen displayed on MFP 10 is switched by an operation on user IF 17, remote screen data corresponding to the screen displayed on user IF 17 is generated, as in S54. At this time, if a screen including preview area 411 is displayed on user IF 17, remote screen data of a remote screen to which file acquisition button 430 is added is generated. However, S55 is not executed. Note that a screen update request is periodically transmitted from browser 41 of PC 30. When a periodic screen update request is received, an affirmative determination is also made in S32. If an affirmative determination is made in S32, the process proceeds to S35, where remote screen data corresponding to the updated screen displayed on user IF 17 is transmitted to PC 30, thereby synchronizing the screen displayed on user IF 17 with the display on remote screen 330.

[0054] In this embodiment, an example of the first transmission process is a process in which the firmware 20 transmits remote screen data corresponding to a standby screen in response to a request to display a remote screen in S33. The first transmission process may be a process of transmitting remote screen data in response to a request to display a remote screen, or may be a process of transmitting remote screen data corresponding to an initial screen other than the standby screen in S33.

[0055] An example of the first operation screen is a FAX execution screen 410 displayed on the user IF 17. An example of the second operation screen is a FAX execution screen 420, which is a remote screen 330 that virtually displays the FAX execution screen 410 and includes a preview area 421 and a file acquisition button 430.

[0056] An example of the second operation screen is a remote screen in which the FAX execution screen 410 is virtually displayed on a browser, which includes the file acquisition button 430 but does not include the preview area 421. Another example of the second operation screen is a remote screen in which the FAX execution screen 410 is virtually displayed on a browser, which does not include the file acquisition button 430.

[0057] An operation on the remote screen 330 to the reception icon 402 on the FAX operation reception screen 400 is an example of a virtual first operation. An operation on the user IF 17 to the reception icon on the FAX operation reception screen displayed on the user IF 17 is an example of a first operation. A process for displaying the FAX execution screen 410 by an operation accepted by the user IF 17 is an example of a screen display process.

[0058] In this embodiment, an example of the second transmission process is the process of transmitting remote screen data corresponding to the FAX execution screen in S35 by operating the FAX operation reception screen 400 on the remote screen 330. An example of the second operation is the operation on the remote screen 330 to the file acquisition button 430 on the FAX execution screen 420.

[0059] In this embodiment, a log report screen having a preview area 421 including a log report may be displayed on the remote screen 330. The log report is stored in memory 12 of MFP 10 and is an image created based on operation log data of MFP 10. In this case, the remote screen including the log report screen is an example of a second operation screen, and the log report screen displayed on user IF 17 is an example of a first operation screen. The log report is an example of an image to be displayed. An operation on the remote screen to instruct the log report screen to display the log report is an example of a virtual first operation. An operation on the remote screen with respect to file acquisition button 430 included in the log report screen is an example of a second operation.

[0060] A setting list screen having a preview area 421 including a list image of print settings may be displayed on remote screen 330. The setting list image is stored in memory 12 of MFP 10 and is an image created based on the print settings of MFP 10. In this case, the remote screen including the setting list screen is an example of a second operation screen, and the setting list screen displayed on the user IF is an example of a first operation screen. The list image is an example of an image to be displayed. An operation on the remote screen to instruct display of the list screen of print settings is an example of a virtual first operation. An operation on the remote screen with respect to file acquisition button 430 included in the setting list screen is an example of a second operation.

[0061] A preview screen including a preview area 421 including a scan preview image may be displayed on the remote screen 330. The scan preview image is an image generated by reading an original document through a scan process or a copy process by the MFP 10 and stored in memory 12. In this case, the remote screen including the preview screen is an example of a second operation screen, and the preview screen displayed on the user IF is an example of a first operation screen. The preview screen is an example of an image to be displayed. An operation on the remote screen to instruct a scan process or an operation to instruct a copy is an example of a second operation. An operation on the remote screen with respect to a file acquisition button 430 included in the preview screen is an example of a second operation.

[0062] A download display screen having a preview area 421 including a preview image for download printing may be displayed on the remote screen 330. By download printing, the MFP 10 downloads image data from the server via the communication IF 16, stores it in memory 12, and prints the image data stored in memory 12. The preview image for download printing is an image created based on the downloaded image data. In this case, the remote screen including the download display screen is an example of a second operation screen, and the download display screen displayed on the user IF is an example of a first operation screen. An operation on the remote screen to instruct download printing is an example of a first operation. An operation on the remote screen with respect to a file acquisition button 430 included in the download display screen is an example of a second operation.

[0063] 10 is a flowchart showing in detail the electronic file acquisition process executed by the firmware 20 in S40. In S60, it is determined whether a preview of the image to be displayed (here, a received FAX image) is being displayed on the user IF 17. If an affirmative determination is made in S60, the process proceeds to S61, where the file of the image to be displayed is read from the memory 12.

[0064] In S62, the number of image pages included in the file read in S61 is confirmed. In S63, the read file is used to start generating a transmission file to be sent to PC 30. Specifically, the transmission file is generated according to the communication protocol used when sending the transmission file to PC 30 and the data format of the transmission file. The communication protocol and the data format of the transmission file are stored in setting information 26. The image data included in the transmission file is data showing the entirety of the received fax image, unlike the partial image of the received fax image displayed in preview area 411 on FAX execution screen 410.

[0065] In S64, it is determined whether there are any remaining pages in the file used to generate the transmission file. For example, if the file confirmed in S62 is composed of images of multiple pages, a negative determination is made in S64, and the process returns to S63 to continue generating the transmission file for the remaining pages.

[0066] If an affirmative decision is made in S64, the process proceeds to S65, where an http(s) response including the transmission file generated in S63 is sent to the PC 30. When the process of S65 is completed, the process returns to S31 in FIG. 4. On the other hand, if a preview is not displayed on the user IF 17, a negative decision is made in S60, and the process proceeds to S66. In S66, an http(s) response including information indicating that the transmission file requested in the electronic file acquisition request does not exist is sent to the PC 30. When the process of S66 is completed, the process returns to S31 in FIG. 4. In this embodiment, the process of sending the transmission file to the PC 30 by the firmware 20 in S65 is an example of a third transmission process.

[0067] Next, a process that is executed when the browser of the PC 30 receives an http(s) response to an electronic file acquisition request from the MFP 10 will be described with reference to FIG.

[0068] In S70, the transmission file included in the body of the http(s) response is obtained. In S71, it is determined whether the transmission file obtained in S70 is in a file format that can be displayed by the browser 41 of the PC 30. If a negative determination is made in S71, the processing in FIG. 11 is terminated. In this case, the browser 41 may display a notification screen on the display 34 indicating that the received fax image could not be displayed.

[0069] If an affirmative determination is made in S71, the process proceeds to S72, where the transmission file acquired in S70 is used to display the received fax image, which is the image to be displayed, on the display 34. In this embodiment, as shown in FIG. 12, the browser 41 superimposes a separate window W2 on the window W1 currently displaying the remote screen 330, and displays the received fax image 500 in this separate window. Note that, for ease of explanation, FIG. 12 illustrates the entire received fax image 500 displayed in the separate window W2. That is, in this embodiment, the received fax image 500, which is the image to be displayed, is displayed on a screen different from the remote screen 330.

[0070] In S73, a transmission file corresponding to multiple pages of received fax images has been acquired in S70, and it is determined whether all pages of the received fax images can be displayed in the separate window W2. If a negative determination is made in S73, the process returns to S72, and the remaining pages of received fax images are made displayable in the separate window W2. For example, when multiple pages of received fax images are displayed in the separate window W2, the next page of received fax images can be displayed below the first page of received fax images by scrolling the separate window W2.

[0071] If an affirmative decision is made in S73, the process shown in Fig. 11 is terminated. In this case, the received fax image displayed in the separate window W2 is hidden, for example, when an operation to terminate the display of the separate window W2 is performed via the user IF35.

[0072] Furthermore, when the browser 41 receives a user operation input on the end button 333, it sends a request to the firmware 20 to end the remote screen control along with the token. When the firmware 20 receives the end request from the PC, it ends the remote screen control on the condition that the token is valid. When the firmware 20 ends the remote screen control, various information stored in the memory 12 is deleted, such as information indicating the usage status of the remote screen control, information indicating that a token has been issued, and information indicating the permission status of the remote screen control. The firmware 20 may end the remote screen control after deleting this information, or another program may delete this information triggered by the end of the remote screen control. Even if there is no access from the browser 41 executing the execution program for a certain period of time after the start of the remote screen control, the firmware 20 ends the remote screen control in the same manner as when the end button is pressed.

[0073] The present embodiment described above can achieve the following effects. On the PC 30, even if the preview image displayed on the remote screen is difficult to see, it is possible to display the received fax image in a separate window W2, which is highly convenient for the user.

[0074] The user can display the preview image on the PC 30 simply by operating the file acquisition button 430 on the remote screen 330, so no complicated operations are required, and the user experience is high.

[0075] In a configuration in which an image is displayed in a preview area on a display 34 before receiving a FAX image, even if the image displayed in the preview area on a remote screen is difficult to see, the user of a PC 30 can recognize the preview image.

[0076] The firmware 20 creates remote screen data for displaying a screen in which a file acquisition button 430, which is an additional icon, is added to the FAX execution screen 410 displayed on the user IF 17. This improves the operability for the user operating the PC 30.

[0077] Even if the image to be displayed shows multiple pages, the image to be displayed can be displayed on the PC 30 sequentially for each page, so that the image to be displayed can be displayed in a format that is easy for the user to view.

[0078] (Other embodiments) The image forming apparatus is not limited to the above embodiment, and various modifications are possible without departing from the spirit thereof. In the above embodiment, an example has been described in which step S51 is not executed when the screen displayed on MFP 10 is switched by an operation on user IF 17. Alternatively, when the screen displayed on MFP 10 is switched by an operation on user IF 17, remote screen data may be transmitted to PC 30. In the above-described embodiment, an example has been described in which the MFP 10 that created the remote screen data transmits the remote screen data to the PC 30 in response to receiving a screen update request from the PC 30. Alternatively, the MFP 10 that created the remote screen data may transmit the remote screen data to the PC 30 without receiving a screen update request. In the above-described embodiment, an example has been described in which MFP 10 transmits pre-created remote screen data to PC 30 in response to receiving a screen update request from PC 30. Alternatively, MFP 10 may not create remote screen data in advance, but may instead create remote screen data corresponding to the screen currently being displayed by MFP 10 in response to receiving a screen update request from PC 30, and transmit the created remote screen data to PC 30. In the above-described embodiment, an example has been described in which S55 is not executed when the screen displayed on MFP 10 is switched by an operation on user IF 17. Alternatively, when the screen displayed on MFP 10 is switched by an operation on user IF 17, remote screen data may be transmitted to PC 30.

[0079] In the above-described first embodiment, the MFP 10 has been described as an example of an image forming apparatus, but the image forming apparatus may be a printer, a scanner, or a copier. The above-described first embodiment has been described as an example of an information processing apparatus, but the image forming apparatus may be a mobile terminal such as a smartphone. [Explanation of symbols]

[0080] 10...MFP, 11...controller, 16...communication IF, 17...user IF, 20...firmware, 30...PC, 41...browser, 100...image forming system

Claims

1. A user interface; a communication interface; a controller; The controller remote screen data can be transmitted to a device connected via the communication interface; the remote screen data is screen data for displaying on the device a remote screen that virtually reproduces a screen displayed on the user interface, The controller When switching a screen displayed on the user interface, remote screen data indicating the remote screen that virtually reproduces the screen after switching can be generated and transmitted to the device; When the screen after the switching is a screen including a preview image, script data for displaying a file acquisition button on the device can be transmitted to the device together with the remote screen data, and the preview image is not an entire image of one page based on a file that is the subject of the preview image, but an image of only a part of the one page; a screen including the preview image and a window including the file acquisition button are displayed on the device that has received the script data and the remote screen data; The controller In response to receiving a file request from the device in response to the operation of the file acquisition button, the file that is the subject of the preview image can be transmitted to the device; In the device that receives the file that is the subject of the preview image, the window including the preview image and a window including the entire image of the one page, only a portion of which is displayed as the preview image, are simultaneously displayed. Image forming device.

2. The image forming apparatus according to claim 1 , wherein the screen after switching includes the preview image relating to a FAX.

3. The image forming apparatus according to claim 1 , wherein the screen after the change includes the preview image relating to a log report.

4. The image forming apparatus according to claim 1 , wherein the screen after the change includes the preview image relating to a list of print settings.

5. The image forming apparatus according to claim 1 , wherein the screen after switching includes the preview image related to scanning.

6. The image forming apparatus according to claim 1 , wherein the screen after switching includes the preview image related to copying.

7. The image forming apparatus according to claim 1 , wherein the screen after switching includes the preview image related to download printing.

Images