Image forming apparatus

Abstract

To provide a technology that improves the input method for an image forming apparatus equipped with an operation panel, allowing the image forming apparatus to be operated without touching the operation panel. [Solution] The MFP101 has a mobile input function and a remote input function that accept input operations from a mobile terminal 2 or PC 3 via the network IF141. When either the mobile input function or the remote input function is activated, the MFP101 displays an operation screen for the MFP101 on the mobile terminal 2 or PC 3 and becomes capable of receiving operation data. While the mobile input function is being provided, the MFP101 does not display the main unit operation screen, such as the home screen, on the touch panel 131. While the remote input function is being provided, the main unit operation screen is displayed on the touch panel 131, and the content of the main unit operation screen is updated based on the operation data received from the mobile terminal 2 or PC 3.

Description

Technical Field

[0005] ,

[0001] The technical field disclosed in this specification relates to an image forming apparatus provided with an operation panel.

Background Art

[0002] There is known a technique for an image forming apparatus capable of performing image formation such as printing and scanning, and receiving various input operations via an operation panel. For example, Patent Document 1 discloses a function execution apparatus including a printing unit, an image reading unit, and an operation panel, wherein the operation panel includes a hardware key and a touch panel, and is configured to receive an input operation on the hardware key or an input operation on an icon or button displayed on the touch panel.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

[0006] The image forming apparatus disclosed herein has two input functions, a mobile input function and a remote input function, which enable input operations from an operating terminal without touching the control panel. When the mobile input function is provided, the image forming apparatus does not display the main operation screen on the touch panel. This prevents unintended operation of the operating terminal by a user operating an operating terminal in front of the image forming apparatus, for example. On the other hand, when the remote input function is provided, the image forming apparatus displays the main operation screen on the touch panel, and when operation data is received from the operating terminal while the remote input function is provided, the display content of the main operation screen is updated based on the received operation data. This allows, for example, a remote administrator to use the remote input function to cooperate with a user in front of the image forming apparatus and teach them how to operate it. In this way, the image forming apparatus can provide an input function suitable for the application.

[0007] The control method, computer program, and computer-readable storage medium for storing the computer program used to realize the functions of the above-mentioned device are also novel and useful. [Effects of the Invention]

[0008] According to the technology disclosed herein, a technology is realized that improves the input method for an image forming apparatus equipped with an operation panel, allowing the image forming apparatus to be operated without touching the operation panel. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram illustrating the schematic configuration of the first form of MFP. [Figure 2] This flowchart shows the procedure for providing the functionality. [Figure 3] This is an explanatory diagram showing an example of a home screen. [Figure 4] This is an explanatory diagram showing an example of a waiting screen. [Figure 5] A sequence diagram illustrating an example of an access reception procedure. [Figure 6] It is an explanatory diagram showing an example of a start screen. [Figure 7] It is a sequence diagram showing an example of a start procedure. [Figure 8] It is an explanatory diagram showing an example of a screen during provision. [Figure 9] It is an explanatory diagram showing an example of an operation screen. [Figure 10] It is a flowchart showing the procedure of mobile input provision processing. [Figure 11] It is an explanatory diagram showing an example of an end screen. [Figure 12] It is an explanatory diagram showing an example of a screen during execution. [Figure 13] It is an explanatory diagram showing an example of a re-scanning screen. [Figure 14] It is a sequence diagram showing an example of a second start procedure. [Figure 15] It is a block diagram showing the schematic configuration of an MFP in a second form. [Figure 16] It is an explanatory diagram showing an example of a standby screen. [Figure 17] It is a flowchart showing the procedure of access permission determination processing. [Figure 18] It is a flowchart showing the procedure of remote input provision processing. [Figure 19] It is an explanatory diagram showing a panel usage permission screen. [Figure 20] It is a flowchart showing the procedure of operation corresponding processing.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, a multifunction peripheral (hereinafter referred to as "MFP") according to a first embodiment will be described in detail with reference to the accompanying drawings. This embodiment discloses an MFP having an image processing function and a communication function.

[0011] As shown in FIG. 1, the MFP 1 of this embodiment includes a controller 10 including a CPU 11 and a memory 12. The MFP 1 also includes an operation panel 13, a communication interface (hereinafter referred to as "communication IF") 14, a printing engine 15, and a scanner 16, and these are electrically connected to the controller 10. The MFP 1 is an example of an image forming apparatus. The controller 10 or the CPU 11 is an example of a controller.

[0012] The CPU 11 executes various processes according to the program read from the memory 12 and based on the user's operations. Note that the controller 10 in FIG. 1 is a general term for the hardware and software used for controlling the MFP 1, and does not necessarily represent a single piece of hardware actually present in the MFP 1.

[0013] The memory 12 of the MFP 1 of this embodiment stores various programs and various data including an operating system (hereinafter referred to as "OS") 21 and a mobile input function program (hereinafter referred to as "mobile input P") 22. The mobile input P 22 includes an embedded web server function and is a program for providing a mobile input function using the embedded web server function. The mobile input P 22 includes programs and data for making the MFP 1 function as a web server.

[0014] The memory 12 is also used as a work area when various processes are executed. The buffer included in the CPU 11 is also an example of a memory. An example of the memory is not limited to a ROM, RAM, HDD, etc. built into the MFP 1, but may be a storage medium readable and writable by the CPU 11. For example, an external memory such as a USB memory or HDD connected to the MFP 1, or a memory or HDD provided in a device connected to the MFP 1 via the network IF 14 is also an example of a memory.

[0015] Note that computer-readable storage media are non-transitory media. In addition to the examples above, non-transitory media also include storage media such as CD-ROMs and DVD-ROMs. Furthermore, non-transitory media are also tangible media. On the other hand, electrical signals that carry programs downloaded from servers on the internet are a type of computer-readable signal medium, but they are not included in non-transitory computer-readable storage media.

[0016] The operation panel 13 includes hardware that displays a screen for informing the user of information and hardware that accepts user operations. The operation panel 13 of the MFP1 in this embodiment includes a touch panel 131 having a screen display function and an operation acceptance function, and one or more hardware keys 132 having only an operation acceptance function.

[0017] The communication interface 14 includes a network interface (hereinafter referred to as "network interface") 141 for connecting the MFP1 to a network and a USB interface (hereinafter referred to as "USB- interface") 142. The MFP1 may also be equipped with communication interfaces that support other communication standards.

[0018] The printing engine 15 includes a configuration for printing an image onto a printing medium such as a sheet. The image forming method of the printing engine 15 is, for example, an electrophotographic method or an inkjet method. The scanner 16 includes a configuration for reading an image from a document. The scanner 16 may also be equipped with an automatic document transport device.

[0019] Next, the operation of MFP1 will be explained. The following processes basically represent the processing of CPU11 in accordance with the instructions written in the program. That is, processes such as "judgment," "extraction," "selection," "calculation," "decision," "identification," "acquisition," "reception," and "control" in the following explanation represent the processing of CPU11. Processing by CPU11 also includes hardware control using the OS API. In this specification, the description of the OS is omitted when explaining the operation of each program. That is, in the following explanation, a statement to the effect that "Program B controls hardware C" may also mean "Program B controls hardware C using the OS API." In addition, the processing of CPU11 in accordance with the instructions written in the program may be described using abbreviated language. For example, it may be written as "performed by CPU11." In addition, the processing of CPU11 in accordance with the instructions written in the program may be described using abbreviated language such as "performed by Program A."

[0020] Furthermore, the term "acquisition" is used in a sense that does not necessarily require a request. That is, the process of the CPU 11 receiving data without a request is also included in the concept of "the CPU acquiring data." Also, "data" in this specification is represented by a bit sequence that can be read by a computer. Data with the same substantial meaning but different formats will be treated as the same data. The same applies to "information" in this specification. Also, "request" and "instruct" are concepts that indicate that information indicating a request or instruction is being output to the other party. Information indicating a request or instruction may also be simply referred to as "request" or "instruction."

[0021] Furthermore, the process by CPU 11 to determine whether information A indicates event B may be conceptually described as "determining from information A whether it is event B or not." Similarly, the process by CPU 11 to determine whether information A indicates event B or event C may be conceptually described as "determining from information A whether it is event B or event C."

[0022] The procedure for providing various functions in response to user operations on the MFP1, which is equipped with various functions such as mobile input functionality via mobile input P22, will be explained with reference to the flowchart in Figure 2. This function provision process is executed by the CPU 11 of the MFP1 when the MFP1 is started up.

[0023] The CPU 11 initializes various parts such as the memory 12 (S101) and determines whether or not the enabled information 25, which indicates that the mobile input function is enabled, is stored in the memory 12 (S102). The MFP 1 receives a setting instruction for the enabled information 25, that is, a setting instruction to enable or disable the mobile input function, for example via the USB-IF 142. In this case, the USB-IF 142 is an example of an external interface. When the MFP 1 receives the input of the enabled information 25, it stores the enabled information 25 in the non-volatile storage area of ​​the memory 12, as shown in Figure 1. The enabled information 25 is an example of first setting information. The enabled or disabled state of the mobile input function can be set by the enabled information 25, improving user convenience.

[0024] The MFP1 may choose not to accept setting instructions for the valid information 25 via the network interface 141. Alternatively, the MFP1 may accept setting instructions via the network interface 141 if the instructions come from a user with administrator privileges. In this case, the network interface 141 is an example of an external interface. The valid information 25 is important information regarding whether or not to enable the mobile input function, and by limiting the input of the valid information 25 to reading from a USB memory or instructions from a user with administrator privileges, unauthorized changes by third parties can be restricted.

[0025] If the CPU determines that the valid information 25 is not stored in the memory 12, that is, that the mobile input function is not enabled (S102: NO), the CPU 11 does not generate access information and instead displays, for example, the home screen 53 shown in Figure 3 on the touch panel 131 (S105). The home screen 53 is an example of a main unit operation screen. The home screen 53 is a screen that includes various objects that accept input operations such as selecting a function to be executed by the MFP1 and various setting instructions.

[0026] If mobile input P22 is not enabled, MFP1 does not provide the functions of mobile input P22, but accepts operations on the touch panel 131 and operates based on the accepted operations (S106). If mobile input P22 is not enabled, MFP1 operates based on user operations on the touch panel 131, similar to S131 to S140 described later. Specifically, if MFP1 receives an instruction to set parameters, it sets the parameters, and if it receives an instruction to execute image formation, it performs image formation using the set parameters. Then, as in the case of YES in S140, if a predetermined period of inactivity has elapsed without any operation on the operation panel 13, the CPU 11 returns to S102 and displays the home screen 53 again. Note that if an operation to display the home screen is received via the operation panel 13, the CPU 11 also displays the home screen 53 on the touch panel 131.

[0027] In this configuration, the MFP1 accepts a setting to enable or disable the mobile input function, allowing the user to choose not to use the mobile input function, thus improving usability. Furthermore, if the CPU 11, for example, initially accepts a setting to enable the mobile input function and then later accepts a setting to disable it, it may delete the stored key 26 (see Figure 1) if it is already stored.

[0028] On the other hand, if the valid information 25 is stored in memory 12, that is, if it is determined that the mobile input function is enabled (S102: YES), the CPU 11 executes the processes necessary to start providing the mobile input function.

[0029] Specifically, the CPU 11 generates a key (S111) and stores the generated key in memory 12 (S112). The key is, for example, a string containing multiple characters, and the CPU 11 generates a different key each time S111 is executed. As shown in Figure 1, S112 stores the latest key 26 in memory 12. The MFP 1 may overwrite the key in S112 to store only the latest key, or it may store multiple keys and add information indicating that the latest key is the latest or information indicating the date and time of creation to the latest key before storing it.

[0030] CPU 11 generates the latest access information (S113), which includes the latest key 26 generated and stored in S111. The access information generated in S113 is information in which the key 26 generated in S111 is added as a query to a URL that includes a path indicating the mobile input function of mobile input P22.

[0031] Furthermore, the CPU 11 encodes the latest access information generated in S113 to generate the latest two-dimensional code, for example, a QR code (registered trademark) (S115), and displays a standby screen containing the generated code on the touch panel 131 of the operation panel 13 (S116). S116 is an example of the display process. As a result, the touch panel 131 displays the latest standby screen 51 containing the latest two-dimensional code, for example, as shown in Figure 4. The standby screen 51 is a screen that includes a two-dimensional code image 511, which is an image in which the access information is encoded, and an "Exit" button 512. By displaying a standby screen 51 that includes a two-dimensional code image 511 containing the latest key 26 and does not include older two-dimensional code images, the complexity of displaying access information can be avoided.

[0032] The CPU 11 then determines whether or not it has accepted access from the mobile terminal 2, etc. (S121). Users who use the mobile input function of the MFP1 in this configuration use a mobile terminal 2 that can be connected to the same network as the MFP1. Communication between the network IF 141 and the access point may be wireless communication such as Wi-Fi (registered trademark) or wired communication such as wired LAN.

[0033] As shown in Figure 1, mobile terminal 2 is equipped with a touch panel 211 and a camera 212. The memory of mobile terminal 2 stores various programs, including a browser 213, and various data. Mobile terminal 2 is a network-connectable device, such as a smartphone or tablet computer. Mobile terminal 2 is an example of a mobile terminal and also an example of an operating terminal.

[0034] Furthermore, "the same network" refers to, for example, a network provided by the same access point. It is sufficient for mobile terminal 2 and MFP1 to be connected to the same access point. Alternatively, multiple access points may form a single network, in which case mobile terminal 2 and MFP1 only need to be connected to any of the multiple access points forming that network. Note that mobile terminal 2 and MFP1 may also be able to connect to the internet via the access point.

[0035] For example, the user activates the camera 212 of the mobile terminal 2 and takes a picture of the two-dimensional code image 511 displayed on the touch panel 131 of the MFP1. The mobile terminal 2 can obtain the encoded access information by analyzing the captured two-dimensional code image 511. Since the scanned two-dimensional code image 511 contains a URL, the mobile terminal 2 asks the user whether or not to access the destination device indicated by that URL, for example by displaying a pop-up on the touch panel 211. Upon receiving an access instruction from the user, the mobile terminal 2 activates the browser 213 and accesses the MFP1 based on the obtained access information.

[0036] As mentioned above, the access information contained in the two-dimensional code image 511 includes a URL and a key. Based on the access information, the browser 213 sends an HTTP request according to the http protocol or an HTTPS request according to the https protocol. Hereafter, HTTP requests and HTTPS requests will simply be referred to as "requests". The browser 213 of the mobile terminal 2 identifies the network address of the destination device indicated by the URL contained in the access information and sends a request to that destination device that includes a query containing the path and key indicated by the URL.

[0037] Users can easily access the MFP1 and use the mobile input function by using their mobile device 2 in front of the MFP1, without needing to remember access information. In this configuration, the MFP1 displays a two-dimensional code image 511 that can be read by the mobile device 2, so users can easily access it using the camera 212 of the mobile device 2. The MFP1 may also display a URL as text. Even in that case, although the user will need to enter access information, they do not need to remember the access information, so access to the MFP1 is easy.

[0038] If the CPU determines that it has received an access request specifying a path indicating the mobile input function (S121: YES), the CPU 11 executes the access reception procedure, which is the procedure for when an access request is received (S122). However, if the valid information 25 is not stored in memory 12 and the mobile input function is not enabled, the CPU 11 will determine NO in S121 even if it has received an access request specifying a path indicating the mobile input function.

[0039] Next, the access reception procedure will be explained with reference to the sequence diagram in Figure 5. Upon receiving an access request specifying a path indicating the mobile input function, MFP1 executes processing using mobile input P22.

[0040] MFP1 first retrieves the key included as a query in the access information (A11), and then checks whether the retrieved key matches the most recent key 26 stored in memory 12 (A12).

[0041] If MFP1 determines that the key included in the access information matches the latest key 26 stored in memory 12 (alt:[OK]), MFP1 sends the start screen data, which is web page data showing the start screen, to the mobile terminal 2, the device that sent the request (A21).

[0042] The browser 213 of the mobile terminal 2 is configured to display a web page on the touch panel 211 based on the web page data it receives from the MFP1 in response to a sent request. When it receives start screen data sent via A21, the browser 213 displays the start screen 61 on the touch panel 211, for example, as shown in Figure 6 (A23). The start screen 61 is a screen that includes a start button 611.

[0043] The browser 213 of the mobile terminal 2 is configured to send a request to the MFP1 containing operation data indicating the content of the operation when it receives an operation from the user on the touch panel 211 while displaying a screen based on web page data sent from the MFP1. The operation data may be object information indicating the object on which the operation was received, or location information indicating the location of the operation on the touch panel 211.

[0044] The MFP1 determines whether it has received operation data from the mobile terminal 2 indicating an operation to press the start button 611, and whether it has received an operation to press the "Exit" button 512 on the standby screen 51 displayed on the touch panel 131.

[0045] First, let's explain what happens when the system determines that it has received operation data indicating an operation on the start button 611 (alt:[Start]). When the mobile terminal 2 receives an operation on the start button 611 from the user (A24), it sends operation data indicating an operation on the start button 611 to the MFP1 (A25). An operation on the start button 611 is an instruction from the user to start providing the mobile input function to the MFP1. As a result, the MFP1 receives operation data indicating an operation on the start button 611 (hereinafter referred to as "start information").

[0046] The MFP1 provides functionality only after the user has clearly indicated their intention to use the mobile input function by pressing the start button 611. In other words, it prevents the mobile input function from being unintentionally activated due to user error or other reasons.

[0047] Upon receiving start information, MFP1 executes the start procedure shown in Figure 7. In the start procedure, MFP1 first determines whether or not the mobile input function is currently being provided (B01). Mobile input P22 determines that the function is being provided if, for example, information indicating that the mobile input function is being provided is stored in memory 12. Information indicating that the mobile input function is being provided is, for example, B11, and is stored in memory 12.

[0048] If MFP1 determines that the mobile input function is not currently being provided (alt:[Not being provided]), it stops displaying the standby screen 51 and displays the "Providing" screen 52, for example as shown in Figure 8, across the entire touch panel 131 (B10). The "Providing" screen 52 includes a message indicating that it is connected to another device and does not contain any objects that accept user input. When MFP1 starts providing the mobile input function, it does not display any screens on the touch panel 131 that contain access information, such as the standby screen 51 shown in Figure 4, nor any screens that contain objects that accept user input. While MFP1 is providing the mobile input function to the mobile terminal 2, it does not accept input operations on the touch panel 131.

[0049] If input operations to the touch panel 131 were accepted while the mobile input function was being provided, unintended operations by the user operating the mobile terminal 2 could occur, potentially confusing the user. In this configuration, the MFP1 does not accept input operations to the touch panel 131 while the mobile input function is being provided, thus avoiding this problem. Furthermore, in this configuration, the MFP1 displays a "Providing" screen 52 on the touch panel 131 while the mobile input function is being provided, making it clear that input operations to the touch panel 131 are not being accepted.

[0050] Furthermore, if access from other mobile devices is allowed while the mobile input function is being provided, unintended operations may occur on the mobile device 2, potentially causing confusion for the user. In this configuration, the MFP1 does not display the standby screen 51 on the touch panel 131 while the mobile input function is being provided, thus reducing the possibility of access being accepted by other users.

[0051] The MFP1 then stores information indicating that the mobile input function is being provided (B11) and sends home screen data, which is web page data representing the home screen, to the mobile terminal 2 (B12). B12 is an example of the transmission process. Home screen data is an example of display data. The MFP1 also stores a screen ID in memory 12 that represents the screen that was transmitted (B13). In this case, the screen ID is the screen data that was last transmitted to the mobile terminal 2, i.e., information representing the home screen.

[0052] Upon receiving home screen data in B12, the browser 213 of the mobile terminal 2 displays the home screen 62 on the touch panel 211, for example, as shown in Figure 9 (B14). The home screen 62 is an operation screen that virtually shows the operation panel 13 in the state of displaying the home screen 53 shown in Figure 3. The home screen 62 includes a panel screen 621 that mimics the home screen 53, a key screen 622 that mimics the hardware keys 132 of the operation panel 13, and a close button 623. The home screen 62 is an example of an operation screen for operating the MFP1.

[0053] Since the home screen 62 includes a panel screen 621 that mimics the home screen 53, the user can intuitively operate the screen displayed on the mobile device 2 in the same way as when operating the touch panel 131.

[0054] Then, MFP1 executes the mobile input provision process (B15). The mobile input provision process executed in B15 will be explained with reference to the flowchart in Figure 10. The mobile input provision process is executed by the CPU 11 of MFP1 based on the mobile input P22. When this mobile input provision process starts, the home screen 62 shown in Figure 9 is displayed on the touch panel 211 of the mobile terminal 2, and the providing screen 52 shown in Figure 8 is displayed on the touch panel 131 of MFP1.

[0055] The CPU 11 starts measuring the elapsed time since sending screen data to the mobile terminal 2 and before receiving a request from the mobile terminal 2 (S201). At the start of the mobile input provision process, the CPU 11 measures the elapsed time since sending the home screen data at B12 in Figure 7.

[0056] The CPU 11 then determines whether or not it has received a request from the mobile terminal 2 (S202). If it determines that a request has been received (S202: YES), the CPU 11 resets the elapsed time and resumes measurement (S211). The CPU 11 then determines whether or not the operation data included in the received request indicates an operation on the close button 623 (see Figure 9) (S212).

[0057] If the CPU 11 determines that it has received operation data indicating an operation other than pressing the close button 623 (S212: NO), it determines whether the received operation data is an operation to change the display screen (S221). If it determines that it is an operation to change the display screen (S221: YES), the CPU 11 sends screen data showing the changed screen to the mobile terminal 2 (S222). S222 is an example of the transmission process. The screen data sent to the mobile terminal 2 in S222 is an example of display data.

[0058] For example, if the home screen 62 shown in Figure 9 receives operation data indicating that an operation to the "Copy" button on the panel screen 621 has been accepted, the CPU 11 sends screen data of the copy screen, which is a screen that accepts the setting of parameters related to copying, to the mobile terminal 2 in S222. The operation screen for accepting parameter settings is also called the parameter setting screen. As a result, the copy screen is displayed on the touch panel 211 of the mobile terminal 2. The copy screen displayed on the touch panel 211 is an example of an operation screen.

[0059] In the mobile input provision process, the CPU 11 transmits only the web page data for the panel screen 621 portion when transmitting screen data in S222 and subsequent steps, unlike in the case of B12 in Figure 7. In other words, during the execution of the mobile input provision process, only the panel screen 621 portion of the screen displayed on the touch panel 211 of the mobile terminal 2 is changed. Therefore, even when the screen is changed by S222, etc., the close button 623 remains displayed on the touch panel 211 of the mobile terminal 2.

[0060] If the CPU determines that the received operation data is not an operation to change the display screen (S221: NO), it determines whether or not it is an operation related to setting parameters used for image formation (S224). If it determines that it is an operation related to setting parameters (S224: YES), the CPU sets the parameters based on the received operation data (S225). S225 is an example of the setting process.

[0061] Furthermore, the CPU 11 sends screen data showing the screen after the settings have been configured to the mobile terminal 2 (S226). For example, if the CPU 11 receives a request for the number of copies on the aforementioned copy screen, it sets the received number of copies as a parameter for copying and sends the copy screen data with the changed display of the number of copies to the mobile terminal 2.

[0062] If the CPU determines that the received operation data is not an operation related to setting parameters (S224: NO), it determines whether or not it is an operation related to image formation (S227). If it determines that it is an operation related to image formation (S227: YES), the CPU starts the execution of image formation based on the received operation data (S228). S228 is an example of the image formation process.

[0063] For example, when the CPU 11 receives operation data indicating that the copy execution command button has been pressed on the copy screen, it starts the copy execution by instructing the scanner 16 to start scanning the document and the print engine 15 to print based on the scanned image of the document. The operation screen for receiving execution commands is also called the execution command screen. The copy screen is an example of a parameter setting screen and an example of an execution command screen. The generation of image data by the scanner 16 and printing by the print engine 15 are examples of image formation.

[0064] The CPU 11 then sends screen data of a screen indicating that execution is in progress to the mobile terminal 2 (S229). The screen indicating that execution is in progress includes a message indicating that image formation is in progress and does not contain any objects that accept input other than the close button 623. For example, the CPU 11 sends screen data containing the message "Copying in progress" to the mobile terminal 2. Note that the CPU 11 does not accept input while image formation is in progress, i.e., while the screen indicating execution is displayed, so it may temporarily suspend the measurement of elapsed time. The screen indicating execution may also include objects that accept input, such as an object that accepts an operation to stop the execution of image formation.

[0065] The various screens displayed on the panel screen 621 are modeled after the various screens displayed on the touch panel 131 when the MFP1 is used by operating the MFP1's touch panel 131. For example, the aforementioned copy screen is the same as the screen displayed on the touch panel 131 in Figure 2, S133, when the copy button is operated on the MFP1's touch panel 131 (YES in S132 in Figure 2) when the mobile input function is not provided. Also, for example, the screen containing the aforementioned "Copy in progress" message is the same as the screen displayed on the touch panel 131 in Figure 2, S139, when the copy execution command button is operated on the MFP1's touch panel 131 (YES in S137 in Figure 2) when the mobile input function is not provided.

[0066] On the other hand, if the CPU 11 determines that the received operation data is not related to the execution of image formation (S227: NO), it returns to S202 to determine whether or not it has received operation data from the mobile terminal 2. For example, if it receives operation data indicating an operation on a part of the touch panel 211 of the mobile terminal 2 other than an object, the CPU 11 may simply reset the elapsed time in S211 and will not perform any screen changes, parameter settings, or image formation execution.

[0067] After sending screen data in S222, S226, or S229, the CPU 11 stores a screen ID that identifies the sent screen data in memory 12 (S231), and returns to S202 to determine whether or not it has received a request from the mobile terminal 2. The CPU 11 may overwrite and store the screen ID in a predetermined area, or it may store multiple screen IDs and store the last one sent as information.

[0068] On the other hand, if it is determined that no request has been received from mobile terminal 2 (S202: NO), CPU 11 determines whether the elapsed time measured in S201 has exceeded a predetermined timeout period (S203). The timeout period is, for example, 1 minute. The timeout period may be a fixed time or a variable time that can be set by the user.

[0069] If the CPU determines that the timeout period has not been exceeded (S203: NO), it determines whether or not the long press of the back key 133 (see Figure 4) was accepted (S204). The back key 133 is included in the hardware key 132 of the control panel 13.

[0070] If the CPU 11 determines that it has received operation data indicating an operation to press the close button 623 from the mobile terminal 2 (S212: YES), or if it determines that the elapsed time has exceeded the timeout period (S203: YES), or if it determines that it has received a long press of the back key 133 (S204: YES), the CPU 11 terminates the mobile input provision process and returns to the start procedure in Figure 7.

[0071] The close button 623 is a button that the user operates on the mobile terminal 2 when they want to end the use of the mobile input function. Operating the close button 623 indicates the user's intention to end the use of the mobile input function.

[0072] The MFP1 terminates the mobile input function based on the operation of the close button 623, allowing the user of the mobile terminal 2 to terminate the mobile input function at their desired timing. As a result, another user can operate the MFP1, increasing its uptime. Note that the close button 623 is included in the screen displayed on the touch panel 211 of the mobile terminal 2, but not in the screen displayed on the touch panel 131 of the MFP1.

[0073] Furthermore, if the elapsed time exceeds the timeout period without any requests from mobile device 2, it is highly likely that the user of mobile device 2 has finished using MFP1. Alternatively, the communication connection between MFP1 and mobile device 2 may have been disconnected. By terminating the mobile input function when no requests are received for more than a predetermined timeout period, MFP1 can automatically terminate the provision of the mobile input function even if, for example, the user of mobile device 2 does not terminate the mobile input function when they finish using MFP1. As a result, another user can use MFP1, thus avoiding unnecessary monopolization of MFP1 by mobile device 2 and increasing the utilization rate of MFP1.

[0074] Furthermore, pressing and holding the back key 133 is an operation performed by a user who wants to terminate the currently provided mobile input function and use the MFP1 by operating the control panel 13. For example, if a user of mobile terminal 2 leaves the MFP1 without terminating the mobile input function after finishing using the MFP1, another user can forcibly terminate the provision of the mobile input function by pressing and holding the back key 133. As a result, even if the timeout period has not been exceeded, that other user will be able to operate the MFP1, thereby increasing the uptime of the MFP1.

[0075] Furthermore, while the mobile input function is being provided, the MFP1 will not accept any operations on the hardware keys 132 or the touch panel 131, except for the instruction to terminate the mobile input function by long-pressing the back key 133. By disabling input operations on the control panel 13 other than the instruction to terminate the mobile input function, it is possible to avoid a mix of input operations from the mobile terminal 2 and input operations from the control panel 13 for the mobile input function. For example, it is possible to avoid the possibility of accepting an unintended operation from the user of the mobile terminal 2 if another user inadvertently operates the control panel 13 without knowing that the mobile input function has been activated.

[0076] Furthermore, the mobile input P22 may be configured to terminate the mobile input provision process without waiting for the elapsed time to exceed the timeout period if it determines that the communication connection between MFP1 and mobile terminal 2 has been lost. For example, if network IF141 loses its internet connection, or if the CPU11 detects that mobile terminal 2 has lost its internet connection, the CPU11 may terminate the mobile input provision process and return to the start procedure in Figure 7.

[0077] On the other hand, if the CPU determines that the conditions for terminating the mobile input provision process, such as operation on the close button 623, have not been met (S204: NO), the CPU 11 determines whether or not the image formation process has ended (S205). If it determines that the image formation process has ended (S205: YES), the CPU 11 sends home screen data to the mobile terminal 2 (S215). During the image formation process, a screen indicating that the process is in progress is displayed on the mobile terminal 2 as described in S229. In S215, the display on the mobile terminal 2 changes from the screen indicating that the process is in progress to the home screen 62. After sending the home screen data, the CPU 11 stores a screen ID that identifies the transmitted screen data in the memory 12 (S231) and returns to S202.

[0078] If the image formation process has not started, or if it is in the process of performing image formation, it is determined that the image formation process has not finished (S205: NO), and the CPU 11 returns to S202 to determine whether any of the conditions in S202 to S205 have been met.

[0079] Furthermore, MFP1 may be configured to accept various instructions even while image formation is in progress. In that case, CPU11 may send home screen data in S229 instead of screen data indicating that the process is in progress. Alternatively, MFP1 may first send screen data indicating that the process is in progress to mobile terminal2, and then send home screen data before the completion of image formation. In that case, the decision in S205 may be omitted.

[0080] Returning to the explanation of the start procedure in Figure 7, MFP1 terminates the mobile input provision process if it determines YES in any of S203, S204, or S212 of the mobile input provision process shown in Figure 10 (B15). Subsequently, MFP1 sends termination screen data, which is web page data indicating that the provision of the mobile input function has ended, to the mobile terminal 2 (B16). As a result, the browser 213 of the mobile terminal 2 displays the termination screen 63 on the touch panel 211, for example, as shown in Figure 11 (B17). Note that if communication with the mobile terminal 2 is disconnected, MFP1 may skip B16.

[0081] Then, MFP1 deletes the information indicating that the mobile input function is available (B18). Alternatively, MFP1 may change the information indicating that the function is available to information indicating that it is not available and store it.

[0082] Up to this point, we have explained the procedures from the start to the end of providing the mobile input function. Next, we will explain the operation of the MFP1 after the provision of the mobile input function has been terminated, for example, the content displayed on the touch panel 131.

[0083] After discontinuing the mobile input function, MFP1 displays the screen corresponding to the stored screen ID on the touch panel 131 (B19). As a result, the touch panel 131 displays the same screen that was displayed on the mobile terminal 2 when the mobile input function was discontinued. Note that the screen displayed on the touch panel 131 in B19 does not have to be exactly the same as the screen displayed on the mobile terminal 2; it may be a somewhat different screen containing similar information.

[0084] If the mobile input provision process is terminated while image formation is not in progress, for example, if the mobile input provision process is terminated while the home screen 62 is being displayed, the MFP1 will display the home screen 53 shown in Figure 3 on the touch panel 131. For example, if the mobile input provision process is terminated while the copy screen is being displayed, the MFP1 will display the copy screen on the touch panel 131. The MFP1 will then be able to accept user input on the touch panel 131, and when it receives input on the touch panel 131, it will operate based on the received input.

[0085] For users who have started using mobile device 2 but wish to switch to using touch panel 131 midway through, it is convenient that they can switch to touch panel 131 operation by operating the close button 623. It is also convenient for users who have accidentally operated the close button 623, as they can continue operating using touch panel 131. If the mobile input provision process is terminated due to a timeout or long press of the back key 133 while the settings screen or execution instruction acceptance screen is displayed, MFP1 may, for example, display the home screen 53 in place of the screen that was displayed on mobile device 2 in B19.

[0086] If the mobile input provisioning process is terminated while image formation is not in progress, and after the home screen 62 is displayed on the touch panel 131 in B19, if there is no operation on the touch panel 131 for a predetermined display time, the MFP1 returns to S102 in Figure 2. The display time is, for example, 30 seconds, and may be a predetermined fixed time or a variable time that can be set by the user.

[0087] On the other hand, if, for example, the MFP1 accepts an operation on the close button 623 or a long press of the back key 133 while printing is in progress and terminates the mobile input provision process, the MFP1 displays a running screen 54 on the touch panel 131, which includes a message indicating that printing is in progress, as shown in Figure 12. If the user terminates the mobile input function by operating the close button 623 while a job based on instructions from the mobile terminal 2 is in progress, and the home screen 53 or the like is displayed on the touch panel 131 immediately afterward, the user may become anxious about whether the job is still running. Displaying the running screen 54 if the job is still running can alleviate the user's anxiety.

[0088] If the MFP1 determines that it has finished image formation while displaying the execution screen 54 on the touch panel 131, it will display the home screen 53 shown in Figure 3 on the touch panel 131 and become capable of accepting user input on the touch panel 131. After that, if there is no input on the touch panel 131 for a predetermined display time, the MFP1 returns to S102 in Figure 2.

[0089] Furthermore, the display of the home screen 53 by B19 is the same process as S129 in Figure 2. Therefore, after the display of the home screen 53 by B19, MFP1 may execute the processes from S131 onwards in Figure 2. In that case, in S140, CPU11 should determine whether the display time has elapsed, rather than the idle time. CPU11 may also determine whether the idle time has elapsed, although this will be a longer period than the display time.

[0090] We have now explained the procedures after the discontinuation of the mobile input function. Next, we will explain how the MFP1 operates when the mobile input function is not provided.

[0091] When MFP1 receives start information from mobile terminal 2 (A25 in Figure 5), if information indicating that the mobile input function is already being provided is stored, that is, if the mobile input function is being provided to another mobile terminal, MFP1 determines that the mobile input function is being provided (B01). If it determines that the function is being provided (alt:[Provided]), MFP1 sends a "Provided" screen data to mobile terminal 2, which includes a message indicating that the function is currently being provided to another mobile terminal and is therefore unavailable at the moment (B21). The "Provided" screen data sent to mobile terminal 2 by B21 may be screen data showing a screen similar to the "Provided" screen 52 shown in Figure 8, or it may be screen data showing a different screen containing a similar message. In this configuration, MFP1 does not provide the mobile input function to two or more mobile terminals simultaneously.

[0092] Based on the received screen data indicating that the mobile input function is being provided, the mobile terminal 2 displays a screen on the touch panel 211 indicating that the mobile input function is being provided (B22). The screen indicating that the function is being provided, displayed in B22, does not contain any objects that accept user input, and even if an operation is received on this screen, the mobile terminal 2 does not send a request to the MFP1.

[0093] Providing mobile input functionality to multiple mobile devices simultaneously can result in receiving operation data from multiple users, potentially leading to behaviors that differ from each user's intended actions. MFP1 avoids this confusion by not starting to provide mobile input functionality to mobile device 2 if it is already providing it to another mobile device.

[0094] Furthermore, since MFP1 displays the standby screen 51 even after sending the start screen data, it may be possible to accept access from another terminal using the two-dimensional code image 511. For example, if access from another mobile terminal is accepted before receiving the start information (A25), MFP1 may also send the start screen data to the other mobile terminal. In that case, once MFP1 receives the start information from one terminal, it remembers that the mobile input function is being provided (B11), and even if it receives the start information from the other terminal, it determines that it is being provided and executes B21. Furthermore, once MFP1 receives the start information from one terminal, it may also send the end screen data to the other terminal.

[0095] After displaying the screen on the touch panel 131 for a predetermined display time in B19, or after sending the screen data being provided to the mobile terminal 2 in B21, the MFP1 completes the start procedure and the access reception procedure in Figure 5, and returns to S102 in Figure 2.

[0096] Next, the procedure for receiving access using outdated access information will be described. If, as a result of the check in A12, it is determined that the key included in the access information used when the access was received does not match the latest key 26 stored in memory 12 (alt:[NG]), MFP1 sends re-read screen data, which is web page data indicating a re-read screen requesting a re-read, to mobile terminal 2 (A31). As a result, the browser 213 of mobile terminal 2 displays the re-read screen 64 on the touch panel 211, for example, as shown in Figure 13 (A32). The re-read screen 64 includes a message requesting a re-read of the waiting screen 51 displayed on the touch panel 131 of MFP1. After sending A31, MFP1 terminates the access reception procedure in Figure 5 and returns to S102 in Figure 2.

[0097] If the key in the received access information is not up-to-date, MFP1 will not provide the mobile input function. By only allowing access using the access information displayed on MFP1's touch panel 131 at that time, the likelihood that the access is coming from a user near MFP1 can be increased, thus ensuring greater security. Furthermore, if access using outdated access information is accepted, the system will notify the user to re-enter the access information, thus avoiding user confusion. This notification may also be accompanied by voice guidance.

[0098] As described later, in the function provision process shown in Figure 2, for example, a new key is generated after a predetermined refresh time has elapsed, and a waiting screen 51 containing the new key is displayed. For example, if a long time has passed between the time the user has the mobile terminal 2 read the two-dimensional code image 511 displayed on the touch panel 131 of the MFP1 and the time the user instructs the MFP1 to access it, the key may have been regenerated. In that case, the MFP1 determines that the key included in the access information used for access is not the latest and executes A31 in Figure 5. When the MFP1 receives access using access information that does not contain the latest key, it does not send the start screen data or operation screen data, and instead notifies the user to re-enter the access information. This makes it highly likely that, for example, a malicious user could read the two-dimensional code image 511 and operate the MFP1 from a location away from it.

[0099] A user who has viewed the re-read screen 64 can, for example, use the camera 212 to read the two-dimensional code image 511 again, thereby accessing the MFP1 with the latest key attached. When access using the latest key attached access information is accepted, the MFP1 determines it as OK at A12 in Figure 5 and enables the use of the mobile input function on the mobile terminal 2.

[0100] Furthermore, if MFP1 does not receive start information within a predetermined waiting period after sending start screen data via A21, MFP1 may send screen data indicating the termination of the mobile input function to mobile terminal 2 and not start providing the mobile input function.

[0101] Up to this point, we have described the operation of MFP1 when the mobile input function is not provided. Next, we will describe the operation of MFP1 when the standby screen 51 is displayed and access from the mobile terminal 2, etc. is not accepted (when NO is selected in S121). The processing when the "Exit" button 512 on the standby screen 51 is accepted after the start screen data has been sent in A21 will be described later.

[0102] After displaying the standby screen 51 in S116 of Figure 2, if no access using access information has been received (S121: NO), the CPU 11 determines whether or not an operation to the "Exit" button 512 has been accepted (S128). If it determines that an operation to the "Exit" button 512 has been accepted (S128: YES), the CPU 11 displays the home screen 53 on the touch panel 131 (S129).

[0103] After displaying the home screen 53 via S129, the MFP1 becomes capable of accepting operations on each object displayed on the screen. The CPU 11 determines whether or not it has received an operation on the operation panel 13 (S131). If it determines that an operation has been received (S131: YES), the CPU 11 performs various operations based on the received operation. For example, if the received operation is to change the display screen (S132: YES), the CPU 11 displays the changed screen on the touch panel 131 (S133). For example, if the copy button is pressed, the CPU 11 displays the aforementioned copy screen.

[0104] The screen displayed in S133 may be a screen that can accept parameter setting instructions. If the operation received on the currently displayed screen is a parameter setting instruction (S134: YES), the CPU 11 sets the parameters (S135) and displays the screen after the settings on the touch panel 131 (S136). S135 is the same process as S225 in Figure 10. For example, the CPU 11 sets parameters such as the number of copies according to the operation received on the copy screen displayed in S133, and displays a copy screen with the number of copies displayed changed to the set number.

[0105] Furthermore, if the received operation is an instruction to execute image formation (S137: YES), the CPU 11 causes the print engine 15 and scanner 16 to execute image formation (S138) and displays the execution screen on the touch panel 131 (S139). For example, if the copy execution instruction button is pressed on the copy screen displayed in S133, the CPU 11 displays a screen on the touch panel 131 that includes the message "Copy in progress". S138 is the same process as S228 in Figure 10. If the operation is anything other than that (S137: NO), the CPU 11 performs other operations and returns to S131.

[0106] When the MFP1 receives an input to the "Exit" button 512 included in the standby screen 51, it displays the home screen 53 on the touch panel 131. The MFP1 then becomes capable of accepting input from the control panel 13. This means that even though the MFP1 can accept input from the mobile terminal 2, it can also accept input from the control panel 13 as needed, thus minimizing a decrease in usability and providing greater convenience for users who prefer to use the control panel 13 for input.

[0107] If the CPU determines that it is not accepting any operations on any of the displayed objects (S131: NO), the CPU 11 determines whether a predetermined period of inactivity has elapsed (S140). Note that while the execution screen is displayed on the touch panel 131, the CPU does not determine the elapsed period of inactivity, but rather determines the elapsed period of inactivity since a screen different from the execution screen, such as a copy screen, was displayed. The predetermined period of inactivity is, for example, 1 minute. If the period of inactivity has not elapsed (S140: NO), the CPU 11 waits until either an operation is accepted or the period of inactivity has elapsed.

[0108] If the CPU determines that a period of inactivity has elapsed without accepting any operation (S140:YES), the CPU 11 returns to S102, just as it did after completing the access reception procedure in S122.

[0109] If the screen to be displayed in S133 is the home screen 53, the CPU 11 proceeds to S102 instead of displaying the home screen 53, as shown by the dashed line in Figure 2. Then, if the mobile input function is enabled, the CPU 11 executes S111 to S116 to display the standby screen 51, and if the mobile input function is disabled, it proceeds to S105 to display the home screen 53. Alternatively, even if the screen to be displayed in S133 is the home screen 53, the CPU 11 may display the home screen 53 and accept input. In this case, the CPU 11 will proceed to S102 if there is no user input after a period of inactivity.

[0110] Furthermore, if the mobile input function is enabled, the screen displayed on the touch panel 131 based on the operation of the "Exit" button 512 may include a button that accepts a command to end the operation on the touch panel 131. In that case, if the CPU 11 accepts an operation on that button, it may proceed to S102, and for other commands, it may, based on the user's operation, for example, if it accepts a command to display the home screen 53, it may display the home screen 53.

[0111] As mentioned above, even after sending the start screen data in A21, the standby screen 51 is displayed on the touch panel 131. If the MFP1 determines that it has received an operation to press the "Exit" button 512 on the standby screen 51 (Figure 4) (alt:[Exit], A27), it sends the exit screen data to the mobile terminal 2, which is the destination of the start screen data (A28), and proceeds to S129 in Figure 2. A28 is the same process as B16 in Figure 7, and as a result, the exit screen shown in Figure 11 is displayed on the touch panel 211 of the mobile terminal 2 (A29).

[0112] By allowing the "Exit" button 512 to be pressed even after the start screen data has been sent, the user can either initiate the use of the mobile input function from the mobile terminal 2 or initiate the use of the mobile input function from the control panel 13. The ease of switching operations via the "Exit" button 512 makes it user-friendly for both users who prefer input from the mobile terminal 2 and those who prefer input from the control panel 13.

[0113] Returning to S102 in Figure 2, if the mobile input function is enabled, the MFP1 executes S111 to S116 again. In other words, if the provision of the mobile input function is terminated, if re-read screen data is sent, or if there is inactivity beyond the time limit after pressing the "Exit" button 512, the CPU 11 generates a standby screen 51 containing new keys and automatically displays it on the touch panel 131. If the mobile input function is not enabled, the CPU 11 proceeds to S105 and displays the home screen 53. This minimizes disadvantages for both users who want to use the mobile input function and those who do not.

[0114] By generating a new standby screen 51, the MFP1 becomes capable of accepting input from the mobile terminal 2 and operations on the "Exit" button 512. Note that the MFP1 does not need to immediately generate a new key after sending the reread screen data at A31 in Figure 5. Furthermore, the CPU 11 does not need to perform a determination of valid information 25 except at startup.

[0115] In this configuration, after discontinuing the provision of the mobile input function, if, for example, the back key 133 is pressed and held down while the mobile input function is being provided, the MFP1 automatically displays a new standby screen 51 without waiting for the inactivity period of S140. This makes it easier for the next user who wants to use the mobile input function immediately to do so.

[0116] Furthermore, each time the mobile input function is terminated, MFP1 generates new access information including a new key, and will not initiate the mobile input function again even if access is attempted using the previous access information. In other words, users who wish to restart the mobile input function must reread the waiting screen 51 and re-enter their access information. This increases the likelihood that the access is coming from the mobile device 2 of the user currently in front of MFP1, thus ensuring greater security.

[0117] As mentioned above, if MFP1 receives an instruction to terminate the mobile input function after it has started providing it and then terminates the mobile input provision process (B15 in Figure 7), it will display the screen corresponding to the stored screen ID on the touch panel 131 for a predetermined display time (B19). This predetermined display time is shorter than the idle time, which is the time the screen that accepts input is displayed after an operation to the "Exit" button 512 is received. An operation to the "Exit" button 512 is highly likely to be a clear indication of the user's intention to stop the display of the standby screen 51 and perform an operation on the touch panel 131. When MFP1 receives an operation to the "Exit" button 512, it displays the screen that accepts input for a period longer than the display time after the mobile input function has been terminated, making it easier to accept user input.

[0118] Furthermore, even if the access reception procedure is terminated at A27 in the access reception procedure in Figure 5 by accepting an operation to the "Exit" button 512, MFP1 will display a screen on the touch panel 131 that accepts user operations, just as when YES is determined in S128, and will be able to accept user operations. MFP1 will then make the same decisions as in S131 and S140. Note that the idle time in this case does not have to be the same as in S140. By making it possible to accept operations to the "Exit" button 512 even after sending the start screen data (A21 in Figure 5), it is possible to use MFP1 by a user other than the user who accessed from the mobile terminal 2, thereby increasing the utilization rate of MFP1.

[0119] On the other hand, if, after displaying the standby screen 51 in S116, the CPU 11 determines that it has not received any access requests or operations on the "Exit" button 512 (S128: NO), the CPU 11 determines whether a predetermined refresh time has elapsed (S141). If it determines that the refresh time has elapsed (S141: YES), the CPU 11 returns to S102 and displays a new standby screen 51.

[0120] The refresh time is the elapsed time during which the system is not accepting user access or operations until the key is regenerated, for example, 5 minutes. By regenerating the key at predetermined refresh times, MFP1 will not accept access using old access information after the refresh time has elapsed.

[0121] If the CPU 11 determines that the refresh time has not elapsed (S141: NO), it repeats the decisions in S121, S128, and S141 until the power is turned off (S142: NO). In this configuration, when the standby screen 51 is displayed, the MFP1 can only accept either access from the mobile terminal 2 or operation of the "Exit" button 512 as user operation, and does not accept other operations such as long-pressing the back key 133 (see Figure 4). Therefore, it is possible to avoid mixing input operations from the mobile terminal 2 and input operations to the operation panel 13, and the control of the MFP1 is stabilized. When the power is turned off (S142: YES), the CPU 11 terminates the function provision process.

[0122] Furthermore, if the MFP1 has not accepted user access or operation for a predetermined sleep time, it may put the operation panel 13 into sleep mode and stop displaying on the touch panel 131. In that case, if the MFP1 receives any operation on the operation panel 13 while it is in sleep mode, it will execute the function provision process based on the decision made in S102.

[0123] Next, we will explain the second start procedure, which is another procedure for determining whether or not the mobile input function is being provided, with reference to the sequence diagram in Figure 14. This second start procedure is executed in place of the start procedure shown in Figure 7.

[0124] The MFP1, executing the second start procedure, sends data containing a program to be executed in the browser 213 of the mobile terminal 2 as start screen data to be sent to the mobile terminal 2 at A21 in Figure 5. This program is, for example, a program written in JavaScript (registered trademark). When the mobile terminal 2 receives start screen data containing this program, it operates according to the received program.

[0125] Based on the received start screen data, the mobile terminal 2 displays the start screen 61 shown in Figure 6. Upon receiving an operation on the start button 611, it requests status information indicating the token issuance status from the MFP1, as shown in Figure 14 (C01). The MFP1 transmits the status information in response to the request from the mobile terminal 2 (C02). The status information indicates whether or not a token has been issued, and will show either "issued" or "not issued". If a token has never been issued, for example at startup, the MFP1 will set the status information to "not issued".

[0126] If the status information received from MFP1 indicates "not issued", mobile terminal 2 sends a token issuance request to MFP1 (C11). MFP1 issues a token in response to the request in C11 (C12) and stores the issued token in memory 12 (C13). MFP1 may overwrite the token or store it with information indicating that it is the latest version. MFP1 may also store the token with time information indicating the period during which the token is valid. Before C12, MFP1 may check the token issuance status again. Furthermore, MFP1 changes the status information indicating the token issuance status to information indicating "issued" (C14).

[0127] Then, MFP1 sends the issued token to mobile terminal 2 (C15). Upon receiving the token, mobile terminal 2 sends the received token along with a start request, which is information requesting the start of using the mobile input function, to MFP1 (C16). MFP1 determines whether the token received along with the start request is a valid token that matches the most recent token stored in C13 (C17).

[0128] If MFP1 determines that the token is correct (alt: [Correct]), it executes steps B10, B12-17, and B19, similar to the start procedure shown in Figure 7. This provides the mobile input function, allowing the user to operate MFP1 using mobile terminal 2. However, in the second start procedure, when mobile terminal 2 sends operation data based on user operations during the mobile input provision process, it adds a token each time it sends the data. MFP1 verifies the token received with the request by comparing it with the token stored in memory 12, and if it determines that it is correct, it processes the operation data and sends new screen data. On the other hand, if MFP1 determines that the received token is incorrect, it may immediately terminate the mobile input provision process.

[0129] If MFP1 determines that the token received with the start request is incorrect (alt: [Incorrect]), MFP1 sends rejection screen data to mobile terminal 2 indicating that it will not start providing the mobile input function (C21). Based on the received rejection screen data, mobile terminal 2 displays a rejection screen on the touch panel 131 (C22). After the provision of the mobile input function is terminated, or after C21, MFP1 deletes the stored token in C13 (C31) and changes the status information to information indicating "Not issued" (C32).

[0130] On the other hand, if status information indicating "issued" is received in C02, the mobile terminal 2 displays an error screen on the touch panel 211 (C41). Also, if a token is not issued within a predetermined time in response to a token issuance request in C11, or if information about an issuance error is received, the mobile terminal 2 also displays an error screen.

[0131] Even in this manner, MFP1 can determine whether or not it is providing mobile input functionality to other terminals based on the token issuance status. Mobile terminal 2 may choose not to obtain status information via C01 and instead send a token issuance request via C11. In that case, MFP1 may receive the token issuance request, determine whether or not a token has already been issued, and if it determines that a token has already been issued, send rejection screen data similar to that of C21.

[0132] As explained in detail above, the first form of the MFP1 is equipped with a mobile input function and can accept input operations from the mobile terminal 2. Before starting to provide the mobile input function, the MFP1 displays a two-dimensional code image 511 containing the necessary access information on the touch panel 131 of the operation panel 13. This makes it easy for the user to input the access information into the mobile terminal 2 by reading the two-dimensional code image 511 in front of the MFP1, even if they do not remember the access information, and thus they can easily use the mobile input function.

[0133] Next, the MFP according to the second embodiment will be described in detail with reference to the attached drawings. As shown in Figure 15, the MFP 101 of this embodiment includes, in addition to the configurations of the MFP 1 of the first embodiment, a remote input function program (hereinafter referred to as "remote input P") 23 and a function to become a Wi-Fi Direct (trademark) group owner (hereinafter referred to as "WFD") 24. The remote input function provided by remote input P 23 is a function that accepts remote operation using the embedded web server function of the MFP 101, and is a different function from the mobile input function. Note that the other configurations are the same as those of the MFP 1 of the first embodiment, and the same reference numerals are used and their description is omitted.

[0134] This configuration of the MFP101 is equipped with WFD24, enabling it to provide a WFD24 network. WFD24 is a function in which the MFP101 acts as the group owner, establishing communication with client devices using the same communication standard as Wi-Fi, and performing one-to-one wireless communication. The MFP101's WFD24 is assigned a predetermined SSID and password, and client devices can communicate with the MFP101 via the network provided by WFD24 by specifying that SSID and password. There are multiple methods for establishing communication with WFD24, and client devices may be able to select one depending on their functionality.

[0135] Furthermore, this configuration of the MFP101 is not limited to devices equipped with a camera 212, such as mobile terminals 2, but is also intended to accept requests from remote locations via the Internet using personal computers (hereinafter referred to as "PCs") 3, etc. PC 3 is an example of an operating terminal. The MFP101 can accept requests via any of the following communication paths: direct connection using WFD24, or network connection via wired or wireless connection to an access point.

[0136] Furthermore, since this configuration of MFP101 includes both a mobile input P22 and a remote input P23, it has access information for both the mobile input P22 and the remote input P23, respectively, and can provide either the mobile input function or the remote input function depending on the access information of the received access. The access information for the mobile input P22 is an example of the first access information, and access using the access information for the mobile input P22 is an example of the first access. The access information for the remote input P23 is an example of the second access information, and access using the access information for the remote input P23 is an example of the second access. Note that the mobile input P22 and the remote input P23 may share the same embedded web server function, or they may each have their own separate embedded web server function.

[0137] Furthermore, the MFP101 can accept setting instructions for valid information 27, which indicates the activation of the remote input function, similar to the valid information 25, which indicates the activation of the mobile input function. The MFP101 accepts the setting of valid information 27, for example, via USB-IF142. When the MFP101 accepts the input of valid information 27, it stores the valid information 27 in the non-volatile storage area of ​​memory 12, as shown in Figure 15. In this case, USB-IF142 is an example of an external interface. Valid information 25 is an example of first setting information, and valid information 27 is an example of second setting information. The MFP101 may also accept setting instructions for valid information 27 via network IF141, for example, if the instruction is given by a user with administrator privileges. In this case, network IF141 is an example of an external interface.

[0138] The ability to configure whether or not to enable the mobile input function and whether or not to enable the remote input function improves user convenience. Furthermore, similar to the enabled information 25, restricting the input of enabled information 27 to only from USB memory or similar devices can limit unauthorized changes.

[0139] However, if the MFP101 has enabled the mobile input function because the valid information 25 is stored in memory 12, the remote input function will not be enabled. The MFP101 may be configured in a way that it cannot accept setting instructions for the valid information 27 when the mobile input function is enabled. Alternatively, the MFP101 may be configured in a way that it accepts setting instructions for the valid information 27 but does not store it in memory 12 and does not enable the remote input function. Furthermore, if the MFP101 accepts setting instructions for the valid information 25 and the valid information 27 is stored in memory 12 and the remote input function is enabled, it may delete the valid information 27 and disable the remote input function.

[0140] Since the MFP101 is equipped with a mobile input P22, it performs the same processing as the function provision processing described above for the first form of MFP1 (see Figure 2) when it starts up. Specifically, if the mobile input function is enabled (YES in S102 of Figure 2), the MFP101 displays a standby screen containing access information on the touch panel 131 (S111 to S116 of Figure 2) and becomes capable of accepting access from external devices. In the following, an external device that accesses the MFP101 and sends a request will be referred to as the "requesting device".

[0141] However, as will be described later, this configuration of the MFP101 can only provide the mobile input function when it accepts access via the WFD24. Therefore, as shown in Figure 16, the MFP101 displays a standby screen 55 on the touch panel 131, which includes connection information 551, that is information for establishing communication with the WFD24. The standby screen 55 includes a two-dimensional code image 511, which is access information for requesting the start of the mobile input function, an "Exit" button 512, and connection information 551, which is information about a predetermined SSID and password assigned to the WFD24. By displaying the standby screen 55, which includes the two-dimensional code image 511 and connection information 551, even users who do not remember this information can easily use the mobile input function.

[0142] While displaying the standby screen 55, if the MFP 101 receives an access request from a mobile terminal 2 or the like using the access information from mobile input P22 (YES in S121 of Figure 2), it performs an access permission determination process before executing the first form of access reception procedure shown in Figure 5. The procedure for the access permission determination process will be explained with reference to the flowchart in Figure 17.

[0143] In the access permission determination process, the CPU 11 determines whether the communication path from which the request was received is via the WFD 24 (S301). The MFP 101 can accept instructions to establish communication with the WFD 24 independently of the mobile input function or remote input function.

[0144] If the CPU 11 determines that it has received access to the mobile input function via the WFD24 (S301: YES), it executes the access reception procedure (see Figure 5) in the same manner as in the first form (S122). Specifically, the MFP 101 checks the key attached to the access information used for the access (A12 in Figure 5), and if the key is the latest, it sends start screen data (A21 in Figure 5) to provide the mobile input function.

[0145] On the other hand, if the CPU 11 determines that it has received access to the mobile input function via a communication path other than WFD24 (S301: NO), it sends information indicating "404 page not found" to the request device (S302) and terminates the access permission determination process. "404 page not found" is information that the web server sends to the browser when the web page corresponding to the received request does not exist. Upon receiving the information sent in S302, the browser of the request device displays a screen corresponding to the information indicating "404 page not found". Note that the information sent in S302 may be, for example, screen data showing a screen that rejects the request.

[0146] Then, after S302, or after the access reception procedure is completed, the CPU 11 returns to the function provision process S102 (Figure 2) and displays the waiting screen 55 again.

[0147] On the other hand, if the mobile input function is not enabled, the MFP101 performs the same processing as the function provision processing of the first form (NO in S102 of Figure 2) to display a main unit operation screen on the touch panel 131 that accepts operations such as the home screen 53 instead of the standby screen 55 (S105 of Figure 2), thereby enabling operation on the touch panel 131.

[0148] If the mobile input function is not enabled, the MFP101 accepts a switch between enabling and disabling the remote input function. If the remote input function is disabled and an access request is received using the access information of remote input P23, the MFP101 sends web page data to the request device that displays a screen indicating that the remote input function is disabled. On the other hand, if the remote input function is enabled and an access request is received using the access information of remote input P23, the MFP101 can provide the remote input function even if it is currently accepting an operation to the touch panel 131.

[0149] Unlike the mobile input function, the MFP101 does not display access information on the touch panel 131 requesting the activation of the remote input function. Therefore, access requests for the remote input function are limited to users who know how to access the MFP101 regardless of the access information, thus preventing unauthorized remote operation.

[0150] If the MFP101 receives an access request using the access information of remote input P23 while valid information 27 is stored, the MFP101 executes remote input provision processing based on remote input P23. The procedure for remote input provision processing will be explained with reference to the flowchart in Figure 18. Note that if the received access is a request for the web page of the remote input function, the MFP101 does not make the decision in S301. In other words, the MFP101 can accept access to the remote input function if the request comes from a device connected to the network to which the MFP101 is connected.

[0151] In the remote input provision process, the CPU 11 first determines whether or not the remote input function is currently being provided (S400). As will be described later, when the CPU 11 starts providing the remote input function, it stores information indicating that the remote input function is being provided in memory 12. In S400, the CPU 11 determines whether or not information indicating that the remote input function is being provided is stored in memory 12. The MFP 101 may also determine whether or not the remote input function is being provided using a token-based procedure as shown in Figure 14.

[0152] If the CPU determines that the remote input function is not currently available (S400: NO), it stores information in memory 12 indicating that the remote input function is available (S401). Then, the CPU 11 sends login screen data, which is a screen that accepts authentication information for login (S402), and accepts a request containing authentication information from the request device. Upon receiving the authentication information, the CPU 11 performs user authentication and determines whether the user is authorized to use the remote input function (S403). Since the remote input function is likely to be operated by a user who is not near the MFP 101, the security of the MFP 101 is enhanced by starting it only after successful authentication. User authentication may be performed on the MFP 101 or on an authentication server, etc.

[0153] If the CPU determines that the user is authorized to use the remote input function (S403: YES), the CPU 11 displays a panel usage permission screen 56 on the touch panel 131, for example, as shown in Figure 19 (S404), and accepts user input (S405). The panel usage permission screen 56 is a screen that notifies the user that remote operation of the MFP 101 using the remote input function is requested and accepts the user's selection as to whether or not to start the remote operation, and includes a "Yes" button 561 and a "No" button 562. The panel usage permission screen 56 may also include messages that notify the user that, for example, operation on the touch panel 131 will not be accepted when remote operation using the remote input function is started, and that the results of the remote operation will be reflected on the touch panel 131. Note that when the CPU 11 provides the mobile input function in B10 to B15 of Figure 7, the panel usage permission screen 56 is not displayed.

[0154] If the "Yes" button 561 is pressed on the panel usage license screen 56, and it is determined that the remote input function has been selected to start (S405: Yes), the CPU 11 retrieves the screen ID stored in memory 12 at that time (S411) and generates screen data based on the retrieved screen ID (S412). The MFP 101 stores a screen ID in memory 12 that identifies the screen currently displayed on the touch panel 131. Here, the CPU 11 retrieves the screen ID that represents the screen immediately before displaying the panel usage license screen 56. The CPU 11 also closes the panel usage license screen 56.

[0155] The CPU 11 sends the generated screen data to the request device (S413). S413 is an example of the transmission process. As a result, the browser of the request device displays on the request device's display the same screen that was displayed on the MFP 101's touch panel 131 immediately before displaying the panel usage license screen 56. For example, if the home screen 53 (see Figure 3) was displayed on the touch panel 131, the request device's display will display a screen similar to the home screen 62 shown in Figure 9. Furthermore, when the browser of the request device receives an operation on the displayed screen, it sends a request to the MFP 101 that includes operation data indicating the received operation. Through the web page of the remote input function, the MFP 101 can receive operation data indicating, for example, instructions to change various settings, instructions to execute image formation operations, and instructions to terminate the use of the remote input function.

[0156] The CPU 11 determines whether the operation data included in the request is operation data indicating the end of the use of the remote input function (S415). If it determines that the operation data is not operation data indicating the end of the use of the remote input function (S415: NO), the CPU 11 executes the operation response processing (S421).

[0157] The procedure for operation response processing will be explained with reference to the flowchart in Figure 20. In Figure 20, the same reference numerals are used for processes that are the same as those in Figures 2 and 10. During operation response processing, the CPU 11 determines whether the operation data included in the received request is an operation to change the display screen (S221). If it is determined that it is an operation to change the display screen (S221: YES), the CPU 11 displays the changed screen on the touch panel 131, unlike in the case of the mobile input function (S133). Furthermore, the CPU 11 sends screen data showing the changed screen to the request device, similar to the case of the mobile input function (S222).

[0158] If the CPU determines that the operation data included in the received request is not an operation to change the display screen (S221: NO), the CPU 11 determines whether it is an instruction to set parameters, etc. (S224). If it determines that it is an instruction to set parameters (S224: YES), the CPU 11 sets the parameters, etc. based on the operation data, in the same way as in the case of the mobile input function (S225). S225 in this case is an example of the setting process.

[0159] Furthermore, unlike in the case of the mobile input function, the CPU 11 displays the screen after the parameters have been set on the touch panel 131 (S136). Then, as in the case of the mobile input function, the CPU 11 sends screen data showing the screen after the settings to the request device (S226).

[0160] If the CPU determines that the instruction is not for setting parameters (S224: NO), it determines whether or not it is an instruction to execute image formation (S227). If it determines that it is an execution instruction (S227: YES), the CPU starts executing image formation based on the operation data, similar to the case of the mobile input function (S228). S228 in this case is an example of the image formation process. By using the remote input function, the user can send setting instructions and execution instructions to the MFP101 by remote operation from the request device.

[0161] Furthermore, unlike in the case of the mobile input function, the CPU 11 displays a screen indicating that it is running on the touch panel 131 (S139). Then, as in the case of the mobile input function, the CPU 11 sends the screen data indicating that it is running to the request device (S229).

[0162] After S222, S226, or S229, the CPU 11 stores a screen ID that identifies the transmitted screen data in memory 12, similar to the case of the mobile input function (S231). In this case, S231 is an example of an update process. After S231, or if it is determined that it is not an execution instruction (S227: NO), the CPU 11 terminates the operation response process and returns to the remote input provision process shown in Figure 18.

[0163] Returning to the explanation of the remote input provision process in Figure 18, after the completion of the operation response process in S421, the CPU 11 becomes capable of receiving the next operation data from the requesting device. Then, the CPU 11 returns to S415 and determines again whether the operation data included in the request from the requesting device is operation data indicating an instruction to terminate the use of the remote input function.

[0164] If the CPU 11 determines that the operation data included in the received request is operation data indicating an instruction to terminate the use of the remote input function (S415: YES), the CPU 11 deletes the information stored in S401 indicating that the remote input function is being provided (S433). Then, the CPU 11 terminates the remote input provision process and returns to the access permission determination process shown in Figure 17.

[0165] Furthermore, if the CPU 11 determines, based on the received authentication information, that the user is not authorized to use the remote input function (S403: NO), or if it determines that the "No" button 562 was pressed on the panel usage permission screen 56 (S405: No), the CPU 11 sends web page data showing a screen informing the request device that remote operation is not possible (S431). As a result, the request device displays a screen informing it that remote operation is not possible, and the provision of the remote input function is not started. After S431, the CPU 11 deletes the information indicating that the remote input function is being provided (S433), terminates the remote input provision process, and returns to the access permission determination process shown in Figure 17.

[0166] If S405 determines that the "No" button 562 has been pressed, the MFP101 will not display the panel usage permission screen 56 for a certain period of time, such as one minute. If the MFP101 receives another request for the remote input function during this time, it will send web page data to the request device informing it that remote operation is not possible, similar to when the "No" button 562 was pressed in S405.

[0167] The remote input function is designed for scenarios where a remote administrator can instruct a user in front of the MFP101 on how to operate it, thus facilitating communication between the user and a remote location. By waiting for input on the panel usage permission screen 56, remote operation without a coordinating user can be prevented. On the other hand, once remote operation via the remote input function begins, the display on the touch panel 131 is automatically changed by the remote operation. For example, if a user is about to use the MFP101 independently of the remote input function, they will not be able to use the MFP101 until the remote input function is terminated. The user intending to use the MFP101 can request a delay in the start of remote operation by pressing the "No" button 562 on the displayed panel usage permission screen 56.

[0168] On the other hand, if the CPU 11 determines that the remote input function is being provided at the start of the remote input provision process (S400: YES), it sends the "Providing" screen data (S441) and terminates the remote input provision process. S441 is the same process as B21 in Figure 7. The "Providing" screen data is screen data used to display a screen such as the "Providing" screen 52 shown in Figure 8 to the request device.

[0169] This configuration of the MFP101 can provide both mobile input and remote input functions, and regardless of which function is used, the MFP101 will accept parameter settings and instructions for image formation. However, since the intended users for the mobile input function and the remote input function are different, the conditions for providing each function are different.

[0170] The mobile input function is intended for use by a user in front of the MFP101. Access information is displayed on the control panel 13 to facilitate access, while dynamic changes to access information via keys and access being limited to via the WFD24 restrict unauthorized access and remote operation. The remote input function is intended for use by an administrator in a remote location. Although the communication path is not restricted, access information is not displayed on the touch panel 131, and successful authentication is a condition for initiation, thus restricting use by users other than administrators. In this way, the MFP101 can provide each function according to its intended use.

[0171] As explained in detail above, the second form of the MFP101 supports two input functions with different operations: a mobile input function and a remote input function, which enable input operations without touching the control panel 13. This allows for the provision of the most suitable input function depending on the application.

[0172] The first and second embodiments are merely illustrative and do not limit the present invention in any way. Therefore, the technology disclosed herein can naturally be improved and modified in various ways without departing from its essence. For example, the present invention can be applied to printers, scanners, copiers, and fax machines in place of MFP1 and MFP101.

[0173] Furthermore, the screens illustrated in each figure are merely examples, and the display format is not limited to those shown. For example, the wording of messages and the shape and arrangement of buttons displayed on each screen are not limited to those shown. For instance, the two-dimensional code image 511 may be displayed on a portion of the home screen instead of covering the entire touch panel 131, as shown in the standby screen 51 in Figure 4 and the standby screen 55 in Figure 16. Also, the display format of the access information included in the standby screens 51 and 55 is not limited to the two-dimensional code image 511; it may also be text information or a barcode image.

[0174] Furthermore, when the mobile input function is launched, the screen displayed on the mobile terminal 2, etc., is not limited to the home screen 62 shown in Figure 9. For example, it does not need to include some of the hardware keys 132, and it may include buttons other than the close button 623 that are not included on the operation panel 13. Also, the arrangement and size of the panel screen 621 and the key screen 622 do not need to be a perfect replica of the operation panel 13. In addition, the screen displayed on the mobile terminal 2, etc., by the mobile input function only needs to be a screen that accepts user input, and is not limited to a replica of the operation screen displayed on the touch panel 131 of the MFP1, but may be an original screen.

[0175] Furthermore, while mobile devices 2, etc., are described as displaying the screen based on the received screen data in a browser, the program used for display is not limited to a browser; it may also be a dedicated application program. However, displaying it in a browser eliminates the need to install a dedicated application program, making it easier to use the mobile input P22 and remote input functions.

[0176] Furthermore, while the first embodiment assumes that the mobile terminal 2 is a smartphone or tablet computer equipped with a camera, it is not limited to these. For example, it could be a laptop computer or a terminal without a camera. When using a terminal without a camera, the user can access the MFP1 from the terminal by, for example, taking a picture of the 2D code image 511 with a camera on another device and sending the captured data to the terminal.

[0177] Furthermore, the first embodiment of the MFP1 may also be equipped with a remote input function similar to that of the second embodiment of the MFP101. In other words, the MFP1 may be capable of performing the processing shown in Figure 18. Also, the first embodiment of the MFP1 may further be equipped with a WFD similar to that of the second embodiment of the MFP101, and provide a mobile input function only when access is accepted via the WFD. In other words, the MFP1 may be capable of performing the processing shown in Figure 17.

[0178] Furthermore, in the first and second forms, MFP1 and MFP101 dynamically generate keys and display access information including the URL and key, but it is not necessary to include the key. However, by including a dynamic key, it is possible to configure the system to not accept access using outdated access information, thereby enhancing the security of the mobile input function.

[0179] Furthermore, in the first and second embodiments, MFP1 and MFP101 display a standby screen 51 (Figure 4) or standby screen 55 (Figure 16) that includes an "Exit" button 512, but a standby screen that does not include an "Exit" button 512 may also be displayed. In that case, for example, operation on one of the hardware keys 132 may be made possible as an alternative to operation on the "Exit" button 512.

[0180] Furthermore, in the first and second forms, if an operation is received on the "Exit" button 512, the standby screen 51 (Figure 4) or standby screen 55 (Figure 16) is automatically displayed again after a period of inactivity, such as one minute, but this is not limited to this. For example, the standby screens 51 and 55 may not be displayed until a new operation, such as an operation on the back key 133, is received.

[0181] Furthermore, in the first and second forms, while the standby screen 51 (Figure 4) or standby screen 55 (Figure 16) is displayed, only access from a mobile terminal 2 or the like, or operation of the "Exit" button 512 is accepted. However, other operations, such as a long press of the back key 133, may also be accepted. In that case, if MFP1 or MFP101 receives a long press of the back key 133, instead of displaying the operation screen and waiting for one minute, as would be the case with operation of the "Exit" button 512, it may immediately generate a new key and display the standby screen 51 or 55. In other words, if MFP1 or MFP101 receives a long press of the back key 133 while the standby screen 51 or 55 is displayed, it does not need to display the operation screen. Alternatively, if MFP1 or MFP101 receives a long press of the back key 133 while the standby screen 51 or 55 is displayed, it may display the operation screen for a shorter time than in the case of operation of the "Exit" button 512.

[0182] Furthermore, in the first and second forms of the start procedure (Figure 7), MFP1 and MFP101 store information indicating that the mobile input function is being provided when they receive start information from the mobile terminal 2 (B11), and determine whether or not the mobile input function is being provided based on that information (B01). However, the timing for determining whether or not the mobile input function is being provided is not limited to this. For example, when start screen data is sent at A21 in Figure 5, information indicating that start screen data has been sent may be stored, and if this information is stored, start screen data may not be sent even if there is access to the mobile input function.

[0183] Furthermore, in the first and second embodiments, MFP1 and MFP101 measure the elapsed time during which they have not received operation data while providing the mobile input function and make a timeout determination (S203 in Figure 10). However, the mobile terminal 2 may also make the timeout determination. For example, if the mobile terminal 2 receives screen data and the time during which it has not received any operation exceeds the timeout period, it may send operation data indicating the termination of the mobile input function.

[0184] Furthermore, in the first and second embodiments, if a long press of the back key 133 is detected while the mobile input function is being provided (YES in S204 of Figure 10), the provision of the mobile input function is forcibly terminated. However, the operation to terminate the provision of the mobile input function is not limited to a long press of the back key 133; it may also be a long press of other hardware keys. In addition, the types of input operations on hardware keys while the mobile input function is being provided may be distinguished. For example, in addition to a long press, the input operations may also include normal input operations, multiple consecutive operations, and simultaneous pressing of multiple hardware keys, and MFP1 and MFP101 may perform different processing depending on the type of input operation.

[0185] Furthermore, in the first and second embodiments, after the provision of the mobile input function is terminated, a screen based on the stored screen ID is displayed on the touch panel 131 of the operation panel 13 (B19 in Figure 7), but this display is not required. In other words, MFP1 and MFP101 may immediately display a new standby screen 51 or 55 after the mobile input provision process (Figure 10) is completed. Also, even if image formation is in progress when the mobile input provision process is terminated, MFP1 and MFP101 may display, for example, the home screen 53 (Figure 3) instead of the execution screen 54 (Figure 12).

[0186] Furthermore, in the second embodiment, MFP101 performs user authentication only when there is a request for the provision of the remote input function, but user authentication is not required. Also, for example, it may be possible to accept user login even when using the mobile input function. For example, there may be a button to accept login on the home screen 62, and MFP1 or MFP101 may send login screen data when it receives operation data indicating an operation on that button. User authentication while providing the mobile input function can be used, for example, to select the files to be printed in stored printing.

[0187] Furthermore, the remote input function is intended for use by, for example, the administrator of the MFP101, and may be a function that can accept various operations related to the MFP101, not just remote operation of the MFP101. Also, in the second form, although the instruction to start providing the remote input function is accepted regardless of the communication path, it may be set so that it is not accepted via the communication path through the WFD24. In addition, the WFD24 may be capable of one-to-many communication.

[0188] In the second embodiment, if the MFP101 displays the panel usage permission screen 56 in S404 of the remote input provision process (Figure 18), and does not accept any operation to either the "Yes" button 561 or the "No" button 562 after a predetermined time has elapsed, it may proceed to S411, assuming that an operation to the "Yes" button 561 has been accepted. Also, although the MFP101 is said to change the display on the touch panel 131 according to the received operation data when it starts providing the remote input function, it does not have to change it. For example, the MFP101 may display a screen on the touch panel 131 indicating that the remote input function is in operation.

[0189] Furthermore, in the second embodiment, the MFP101 does not accept operations on the touch panel 131 while the remote input function is being provided, but it may be possible to accept them. Alternatively, it may be possible to select whether or not to accept operations when starting to provide the remote input function. If operations are accepted, for example, by having the request device perform polling, the MFP101 can send screen data of the screen that has been changed based on user operation to the request device. In that case, the MFP101 performs various operations corresponding to S106 in Figure 2 based on the accepted operation. Also, since the mobile input function is disabled when the remote input function is enabled, if the MFP101 accepts an operation from the user to display the home screen 53, it displays the home screen 53 instead of the standby screen.

[0190] Furthermore, in any flowchart disclosed in the embodiments, the execution order of any multiple processes in any multiple steps can be arbitrarily changed or executed in parallel, as long as no inconsistencies arise in the processing content.

[0191] Furthermore, the processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as an ASIC, or a combination thereof. Also, the processes disclosed in the embodiments can be implemented in various ways, such as by a storage medium or method storing a program for executing the process. [Explanation of Symbols]

[0192] 1,101 MFP 2 Mobile devices 3 PC 10 Controllers 11 CPU 12 memory 13. Control Panel 131 Touch Panel 141 Network Interface 142 USB-IF

Claims

1. Network interface and Control panel including touch panel, Controller and An image forming apparatus comprising, The image forming apparatus is The aforementioned network interface provides input functions that accept input operations from an operating terminal, and includes two types of remote input functions with different access information: a mobile input function and a remote input function. The aforementioned controller, When either the mobile input function or the remote input function is initiated, A transmission process is performed to send display data for displaying the operation screen for the image forming apparatus on the operation terminal via the network interface to the operation terminal. Furthermore, the controller, When operation data indicating the operation content of the operation screen is received from the operation terminal via the network interface, If the received operation data is an operation related to setting parameters used for image formation, then a setting process is executed to set the parameters indicated in the received operation data. If the received operation data is an operation related to image formation, the system is configured to execute the image formation process that performs the image formation indicated in the received operation data. Furthermore, the controller, The system is configured to accept authentication information via the aforementioned network interface and perform authentication based on the accepted authentication information. Furthermore, the controller, In a state where neither the aforementioned mobile input function nor the aforementioned remote input function has been provided, When a second access is made from the operating terminal via the network interface using the second access information necessary to initiate the provision of the remote input function, the provision of the remote input function is initiated on the condition that the authentication information has been entered and the authentication has been successful. When a first access is made from the operating terminal via the network interface using first access information different from the second access information necessary to initiate the provision of the mobile input function, the provision of the mobile input function is initiated without requiring the input of the authentication information. An image forming apparatus configured as follows.

2. In the image forming apparatus described in claim 1, There are cases in which the first setting information indicating the activation of the mobile input function is stored in memory, and cases in which the first setting information is not stored in memory. There are cases in which the second setting information indicating the activation of the remote input function is stored in the memory, and cases in which the second setting information is not stored in the memory. The aforementioned controller, In a state where neither the aforementioned mobile input function nor the aforementioned remote input function has been provided, If the first access necessary to initiate the provision of the mobile input function is made from the operating terminal via the network interface, and the first setting information is stored in the memory, the provision of the mobile input function will be initiated; otherwise, the provision of the mobile input function will not be initiated. If the second access necessary to initiate the provision of the remote input function is made from the operating terminal via the network interface, and the second setting information is stored in the memory, the provision of the remote input function will be initiated; otherwise, the provision of the remote input function will not be initiated. An image forming apparatus configured as follows.

3. In the image forming apparatus described in claim 2, The aforementioned controller, If the first setting information is not stored in the memory, The main unit operation screen is displayed on the aforementioned touch panel, If there is an operation on the main unit's operation screen related to setting the parameters used for image formation, the parameters will be set according to that operation. If there is an operation related to image formation on the aforementioned main unit operation screen, the image formation will be performed according to that operation. If the first setting information is stored in the memory, When the provision of the mobile input function has not been started, the system is configured to display a standby screen on the touch panel, and while the standby screen is displayed, if the first access necessary for starting the provision of the mobile input function is made from the operating terminal via the network interface, the provision of the mobile input function is started. In the aforementioned transmission process, The display data for displaying the operation screen for the image forming apparatus, which virtually represents the main unit operation screen, on the operation terminal is transmitted to the operation terminal via the network interface. An image forming apparatus configured as follows.

4. In the image forming apparatus according to claim 2 or claim 3, The aforementioned controller, When the first setting information is acquired via an external interface provided by the image forming apparatus, the first setting information is stored in the memory. When the second setting information is acquired via the external interface provided by the image forming apparatus, the second setting information is stored in the memory. An image forming apparatus configured as follows.

5. In an image forming apparatus according to any one of claims 1 to 4, The aforementioned controller, In a state where neither the aforementioned mobile input function nor the aforementioned remote input function has been provided, When the first access necessary to initiate the provision of the mobile input function is received from the operating terminal via the network interface, the provision of the mobile input function is initiated. When the second access necessary for initiating the provision of the remote input function is made from the operating terminal via the network interface, the provision of the remote input function is initiated on the condition that the authentication information is entered and the authentication is successful. When the provision of the mobile input function has been initiated, if the first access necessary for initiating the provision of the mobile input function is received from another operating terminal via the network interface, the provision of the mobile input function will not be initiated to the other operating terminal. When the provision of the remote input function has been initiated, if the second access necessary for initiating the provision of the remote input function is received from another operating terminal via the network interface, the provision of the remote input function to the other operating terminal will not be initiated. An image forming apparatus configured as follows.

6. In an image forming apparatus according to any one of claims 1 to 5, In the aforementioned transmission process, The display data for displaying the operation screen for the image forming apparatus, which virtually represents the operation panel, on the operation terminal is transmitted to the operation terminal via the network interface. Furthermore, the controller, When the operation data is received from the operation terminal via the network interface, The operation terminal receives new display data via the network interface to display the operation screen, which virtually shows the operation panel updated based on the operation indicated in the received operation data. An image forming apparatus configured as follows.

Images