Image forming apparatus

Abstract

To operate an image forming apparatus including an operation panel without touching the operation panel while suppressing a reduction in safety.SOLUTION: A MFP (multifunction peripheral) 1 includes a mobile input function to accept input operations from a mobile terminal 2 via a network IF (interface) 141, and when the provision of the mobile input function is started, sends, to the mobile terminal 2, screen data to display an operation screen for the MFP1 on the mobile terminal 2. Furthermore, the MFP1 displays a password on a touch panel 131 in the state where the provision of the mobile input function is not started, and starts the provision of the mobile input function in receiving an access from the mobile terminal 2 using access information required for the start of the provision of the mobile input function via the network IF141, and in receiving an input of the password displayed on the touch panel 131 from the mobile terminal 2.SELECTED DRAWING: Figure 1

Description

Technical Field

[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 technology of 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

Summary of the Invention

Problems to be Solved by the Invention

[0004] In recent years, there has been an increasing tendency for users to dislike input operations on operation panels that are touched by a large number of unspecified people, and there is a growing demand to enable input operations on image forming apparatuses without touching the operation panel. Therefore, it is conceivable to provide a function for the image forming apparatus to receive input operations from a mobile terminal. However, since input operations by a third party from a location away from the image forming apparatus become possible, there is a risk of reduced security. Patent Document 1 does not disclose a technology for operating without touching the operation panel, and there is room for improvement.

Means for Solving the Problems

[0005] The image forming apparatus disclosed herein comprises a network interface, an operation panel including a touch panel, and a controller, wherein the image forming apparatus has a mobile input function that accepts input operations from a mobile terminal via the network interface, and when the provision of the mobile input function is initiated, the controller performs a transmission process that transmits display data to the mobile terminal via the network interface for displaying an operation screen for the image forming apparatus on the mobile terminal, and further, while the provision of the mobile input function is in progress, when the controller receives operation data from the mobile terminal via the network interface indicating the operation content of the operation screen, the received operation data is displayed as an image If the operation relates to setting parameters used for formation, the controller executes a setting process to set the parameters indicated in the received operation data. If the received operation data relates to performing image formation, the controller executes an image formation process to perform the image formation indicated in the received operation data. Furthermore, the controller is configured to execute a display process to display a password on the touch panel when the provision of the mobile input function has not been started. The controller is configured to start providing the mobile input function when an access request using the access information necessary to start providing the mobile input function is made from the mobile terminal via the network interface, and the password displayed on the touch panel is entered from the mobile terminal.

[0006] The image forming apparatus disclosed herein displays the password required to activate the mobile input function on the touch panel of the control panel when the mobile input function has not yet been activated. The mobile input function is then activated when the password is entered from a mobile device. This increases the likelihood that the mobile input function will be activated while the user is in front of the image forming apparatus. Furthermore, as a result, the possibility of input being performed by a third party is reduced while still providing the mobile input function.

[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, an image forming apparatus equipped with an operating panel is provided, which enables the image forming apparatus to be operated without touching the operating panel while minimizing any reduction in safety. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram showing the schematic configuration of the MFP according to the embodiment. [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] This is an explanatory diagram showing an example of a password entry screen. [Figure 7] This is an explanatory diagram showing an example of the Start screen. [Figure 8] This is a sequence diagram showing an example of the starting procedure. [Figure 9] This is an explanatory diagram showing an example of the screen being provided. [Figure 10] This is an explanatory diagram showing an example of an operation screen. [Figure 11] This is a flowchart showing the procedure for providing mobile input. [Figure 12] This is an explanatory diagram showing an example of an ending screen. [Figure 13] This is an explanatory diagram showing an example of the execution screen. [Figure 14] This is a sequence diagram showing an example of the second start procedure.

Best Mode for Carrying Out the Invention

[0010] Hereinafter, a multifunction peripheral (hereinafter referred to as "MFP") according to the 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 MFP1 of this embodiment includes a controller 10 including a CPU 11 and a memory 12. Further, the MFP1 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 MFP1 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 the control of the MFP1, and does not necessarily represent a single hardware actually existing in the MFP1.

[0013] In the memory 12 of the MFP1 of this embodiment, 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 are stored. The mobile input P22 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 P22 includes programs and data for causing the MFP1 to function as a web server.

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

[0015] Note that a computer-readable storage medium is a non-transitory medium. Non-transitory media include storage media such as CD-ROMs and DVD-ROMs in addition to the above examples. Also, non-transitory media are tangible media. On the other hand, an electrical signal that conveys a program downloaded from a server on the Internet, etc. is a computer-readable signal medium, which is a type of computer-readable medium, but is not included in non-transitory computer-readable storage media.

[0016] The operation panel 13 includes hardware for displaying a screen for notifying the user of information and hardware for receiving operations by the user. The operation panel 13 of MFP 1 in this embodiment includes a touch panel 131 having a screen display function and an operation reception function, and one or more hardware keys 132 having only an operation reception function.

[0017] The communication IF 14 includes a network interface (hereinafter referred to as "network IF") 141 for connecting MFP 1 to a network and a USB interface (hereinafter referred to as "USB-IF") 142. Note that MFP 1 may further include a communication IF corresponding to 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 valid information 25, which indicates that the mobile input function is enabled, is stored in the memory 12 (S102). When the MFP 1 receives input of the valid information 25, it stores the valid information 25 in the non-volatile storage area of ​​the memory 12, as shown in Figure 1. The mobile input function can be enabled or disabled depending on the presence or absence of the valid information 25, improving user convenience.

[0024] Furthermore, MFP1 may accept setting instructions for the valid information 25, that is, setting instructions to enable or disable the mobile input function, for example via USB-IF142. MFP1 may not accept setting instructions for the valid information 25 via network IF141. Alternatively, MFP1 may accept setting instructions via network IF141 if the instructions are given by a user with administrator privileges. 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 displays, for example, a home screen 53 as 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 the mobile input function is not enabled, the MFP1 does not provide the mobile input function, accepts operations on the touch panel 131, and operates in the same manner as described in S131 to S140 (S106) based on the accepted operations. Specifically, if the 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, for example, if a predetermined period of inactivity has elapsed without any operation on the operation panel 13, or if an operation to display the home screen is accepted, the CPU 11 returns to S102 and displays the home screen 53 on the touch panel 131 again.

[0027] 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.

[0028] Specifically, the CPU 11 generates a one-time password (S111) and stores the generated password in memory 12 (S112). S111 is an example of the generation process. The startup of MFP1 is an example of a process that satisfies predetermined execution conditions. The one-time password is, for example, a string containing multiple letters and numbers, and the CPU 11 generates a different password each time S111 is executed. As shown in Figure 1, S112 stores the latest password 26 in memory 12. Note that MFP1 may overwrite the password in S112 to store only the latest password, or it may store multiple passwords and store the latest password with information indicating that it is the latest or information indicating the generation date and time.

[0029] CPU11 acquires access information necessary to start providing the mobile input function, encodes the acquired access information, and generates a two-dimensional code (S113). The access information includes a URL containing a path that indicates information for starting the function by mobile input P22, and the two-dimensional code is, for example, a QR code (registered trademark). Hereinafter, the access information necessary to start providing the mobile input function will be referred to as "mobile access information".

[0030] Furthermore, MFP1 may store mobile access information, or information of a two-dimensional code encoding the mobile access information, in memory 12. In that case, CPU 11 may read the stored information in S113 and obtain the information of the two-dimensional code.

[0031] Then, the CPU 11 displays a standby screen on the touch panel 131 of the operation panel 13, which includes the two-dimensional code generated in S113 and the one-time password generated in S111 (S116). S116 is an example of the display process. As a result, the touch panel 131 displays a standby screen 51, 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 mobile access information is encoded, an "Exit" button 512, and the latest one-time password 513. The two-dimensional code image 511 is an example of a code.

[0032] In this state, MFP1 can accept access using mobile access information. CPU11 determines whether or not it has accepted access from a mobile terminal 2, etc. (S121). Users who use the mobile input function of MFP1 in this configuration use, for example, a mobile terminal 2 that can be connected to the same network as MFP1. Communication between the network IF141 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.

[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] Access by mobile device 2 is performed, for example, in the following steps: The user of mobile device 2 activates the camera 212 of mobile device 2 and takes a picture of the two-dimensional code image 511 displayed on the touch panel 131 of MFP1. By analyzing the captured two-dimensional code image 511, mobile device 2 can obtain the encoded mobile access information. Since the read two-dimensional code image 511 contains access information, mobile device 2 asks the user, for example, by displaying a pop-up on the touch panel 211, whether or not to perform access using that access information. Upon receiving an instruction from the user to perform access, mobile device 2 activates the browser 213 and accesses MFP1 based on the obtained mobile access information.

[0036] Browser 213 sends an HTTP request following the http protocol or an HTTPS request following the https protocol based on the acquired mobile access information. Hereafter, HTTP requests and HTTPS requests will simply be referred to as "requests." Browser 213 on mobile terminal 2 identifies the network address of the destination device indicated by the URL included in the mobile access information and sends a request to that destination device. When sending the request, mobile terminal 2 may also send information included in the mobile access information.

[0037] In this configuration, the MFP1 displays a two-dimensional code image 511 that can be read by the mobile terminal 2. Therefore, the user does not need to remember their mobile access information and can easily access the MFP1 by using the camera 212 of the mobile terminal 2 in front of the MFP1. Alternatively, the MFP1 may display the mobile access information as text instead of the two-dimensional code image 511. Although this would require the user to manually enter their mobile access information, access to the MFP1 would still be easy as the user does not need to remember it.

[0038] If the CPU determines that it has received access using mobile access information (S121: YES), the CPU 11 executes the access reception procedure, which is the procedure for when access 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 access using mobile access information.

[0039] Next, the access reception procedure will be explained with reference to the sequence diagram in Figure 5. Upon receiving access using mobile access information, MFP1 executes processing based on mobile input P22. At the start of the procedure in the sequence diagram in Figure 5, a waiting screen 51 including the password 513 is displayed on the touch panel 131 of MFP1, as shown in Figure 4.

[0040] When MFP1 receives an access request using mobile access information, it sends password input screen data, which is webpage data showing a password input screen, to the mobile terminal 2, the device that made the access (A11). As a result, MFP1 prompts the user who made the access request using mobile access information to enter a password.

[0041] The browser 213 of the mobile terminal 2 is configured to display a web page on the touch panel 211 based on the received data when it receives web page data from the MFP1 in response to a sent request. When it receives password input screen data sent in A11, the browser 213 of the mobile terminal 2 displays a password input screen 60 on the touch panel 211, for example, as shown in Figure 6 (A12). The password input screen 60 is a screen that includes a password input field 601 and a send button 602.

[0042] The user of mobile terminal 2 enters the password displayed on the standby screen 51 of MFP1 into the password input field 601 on the password input screen 60 displayed on mobile terminal 2 (A13). Furthermore, once the user has finished entering the password, they operate the send button 602 to send the entered password (A14).

[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] Mobile terminal 2 sends the password information entered in the password input field 601 to MFP1 along with operation data indicating that the send button 602 has been operated (A15). As a result, MFP1 receives a request containing the password information from mobile terminal 2 and determines whether the password included in the request matches the most recent password stored in memory 12 in S112 of Figure 2 (A16).

[0045] If the MFP1 determines that the password matches (alt:[match]), it sends the start screen data, which is web page data representing the start screen, to the mobile terminal 2, the device that sent the request (A21).

[0046] When the start screen data transmitted via A21 is received, the browser 213 of the mobile terminal 2 displays the start screen 61 on the touch panel 211, for example, as shown in Figure 7 (A23). The start screen 61 is a screen that includes the start button 611.

[0047] Even after transmitting the start screen data, the MFP1 displays the standby screen 51 on the touch panel 131 and is capable of accepting input to the "Exit" button 512 on the standby screen 51. The MFP1 determines whether it has received operation data from the mobile terminal 2 indicating an operation to the start button 611, and whether it has received an operation to the "Exit" button 512 on the touch panel 131.

[0048] 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").

[0049] 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.

[0050] Upon receiving start information, MFP1 executes the start procedure shown in Figure 8. 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.

[0051] If the MFP1 determines that the mobile input function is not currently available (alt:[Not Available]), it stops displaying the standby screen 51 and displays the availability screen 52, for example as shown in Figure 9, across the entire touch panel 131 (B10). The availability screen 52 is a screen that includes a message indicating that it is connected to another device and does not contain any objects that accept user input.

[0052] When MFP1 begins providing the mobile input function, it does not display any screens on the touch panel 131 that include access information, such as the standby screen 51 shown in Figure 4, nor any screens that include objects for accepting various operations. Furthermore, while MFP1 is providing the mobile input function to the mobile terminal 2, it does not accept input operations on the touch panel 131.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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 10 (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.

[0057] 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.

[0058] 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 11. 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 10 is displayed on the touch panel 211 of the mobile terminal 2, and the providing screen 52 shown in Figure 9 is displayed on the touch panel 131 of MFP1.

[0059] 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 8.

[0060] 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). This elapsed time is the period during which no request was received from the mobile terminal 2. As will be described later, the CPU 11 terminates the provision of the mobile input function if the elapsed time exceeds a predetermined timeout period.

[0061] When a request is received, the CPU 11 determines whether the operation data included in the received request indicates an operation to the close button 623 (see Figure 10) (S212). The close button 623 is a button that the user operates when they want to terminate the provision of the mobile input function.

[0062] 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.

[0063] For example, if the home screen 62 shown in Figure 10 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 that accepts the setting of parameters 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.

[0064] 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 8. 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 is displayed on the touch panel 211 of the mobile terminal 2.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] 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 when the copy button is operated on the MFP1's touch panel 131 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 when the copy execution command button is operated on the MFP1's touch panel 131 when the mobile input function is not provided.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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 8.

[0076] The close button 623 is a button that the user operates on the mobile terminal 2 when they want to stop using the mobile input function. Operating the close button 623 indicates the user's intention to stop using the mobile input function. The MFP1 terminates the mobile input function based on the operation of the close button 623, so the user using the mobile terminal 2 can terminate the mobile input function at the time they intend. As a result, another user can operate the MFP1, increasing the utilization rate of the MFP1. Note that the close button 623 is included in the screen displayed on the touch panel 211 of the mobile terminal 2, but is not included in the screen displayed on the touch panel 131 of the MFP1.

[0077] Furthermore, if the elapsed time since measurement began on S201 exceeds the timeout period without any request from mobile terminal 2, it is highly likely that the user on mobile terminal 2 has finished using MFP1. Alternatively, the communication connection between MFP1 and mobile terminal 2 may have been disconnected. By terminating the mobile input function when no request is 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 on mobile terminal 2 does not terminate the mobile input function when they have finished using MFP1. As a result, another user can use MFP1, thus avoiding unnecessary monopolization of MFP1 by mobile terminal 2 and increasing the utilization rate of MFP1.

[0078] 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.

[0079] 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 that an unintended operation by the user of the mobile terminal 2 may be accepted if another user inadvertently operates the control panel 13 without knowing that the mobile input function has been activated.

[0080] Furthermore, the mobile input P22 may be configured to terminate the mobile input provision process without waiting for the aforementioned 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 CPU 11 detects that mobile terminal 2 has lost its internet connection, the CPU 11 may terminate the mobile input provision process and return to the start procedure in Figure 8.

[0081] 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.

[0082] 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.

[0083] 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.

[0084] Returning to the explanation of the start procedure in Figure 8, if MFP1 determines YES in any of S203, S204, or S212 of the mobile input provision process shown in Figure 11, it terminates the mobile input provision process in B15. Then, 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 12 (B17). Note that if communication with the mobile terminal 2 is disconnected, MFP1 may skip B16.

[0085] Then, MFP1 deletes the information stored in B11, namely 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.

[0086] 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.

[0087] After discontinuing the mobile input function, the MFP1 displays the screen corresponding to the stored screen ID on the touch panel 131 (B19), and becomes capable of accepting user input on the touch panel 131. 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.

[0088] 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. The MFP1 will then become capable of accepting user input on the touch panel 131, and if it receives input on the touch panel 131, it will operate based on the received input.

[0089] For users who have started using mobile device 2 but wish to switch to using touch panel 131 midway through, pressing the close button 623 allows them to switch to touch panel 131 operation, which is convenient. Furthermore, for users who accidentally press the close button 623, it is convenient that they can continue using touch panel 131.

[0090] Furthermore, for example, if 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 provisioning process, the MFP1 will display a running screen 54 on the touch panel 131, which includes a message indicating that printing is in progress, as shown in Figure 13. After the MFP1 has displayed the running screen 54 on the touch panel 131 and has finished the image formation process, it will display the home screen 53 shown in Figure 3 on the touch panel 131 and become capable of accepting user operations on the touch panel 131.

[0091] If a user terminates the mobile input function by pressing the close button 623 while a job is being executed based on instructions from mobile device 2, and the home screen 53 or similar is displayed on the touch panel 131 immediately afterward, the user may become anxious about whether the job is still running. Displaying the execution screen 54 if the job is still running can alleviate the user's anxiety.

[0092] Furthermore, if the mobile input provision process is terminated due to a timeout or a long press of the back key 133 while the settings screen or execution instruction reception screen is being displayed, MFP1 may, for example, in B19, display the home screen 53 instead of the screen that was displayed on the mobile terminal 2.

[0093] Then, after the mobile input provision process is completed and the touch panel 131 becomes ready to accept operations, if there is no operation on the touch panel 131 for a predetermined display period, the MFP1 terminates the start procedure in Figure 8 and the access reception procedure in Figure 5, and returns to S102 of the function provision process in Figure 2. The display period is, for example, 30 seconds, and may be a predetermined fixed time or a variable time that can be set by the user. If the mobile input function is enabled, the MFP1 generates a new password and automatically displays a standby screen 51 containing the new password on the touch panel 131.

[0094] When MFP1 finishes providing mobile input, it generates a new password and does not accept access to the mobile input function with the old password. The timing of finishing the mobile input provision process is an example of the first timing. Note that after MFP1 finishes providing mobile input and deletes the information indicating that it is being provided (B18), it may generate a new password without waiting for the screen display in B19 to finish. The conditions for terminating the provision of the mobile input function, i.e., the conditions for terminating the mobile input provision process, are an example of predetermined execution conditions. Also, MFP1 may not make a determination of valid information 25 (S102) except at startup.

[0095] 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.

[0096] 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 in B01 in Figure 8 that the mobile input function is being provided. If it determines that the function is being provided (alt:[Provided]), MFP1 sends unavailable screen data to mobile terminal 2 (B21), which includes a message indicating that the function is currently being provided to another mobile terminal and is therefore unavailable.

[0097] Based on the received unavailable screen data, mobile terminal 2 displays an unavailable screen on the touch panel 211 (B22) indicating that the mobile input function is unavailable. The unavailable screen displayed in B22 is a screen that does not contain any objects that accept user input, and even if an operation is accepted on this screen, mobile terminal 2 does not send a request to MFP1. Therefore, in this case, the user of mobile terminal 2 operates the start button 611 (see Figure 7), but is unable to use the mobile input function. In this configuration, MFP1 does not provide the mobile input function to two or more mobile terminals simultaneously.

[0098] 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.

[0099] Since MFP1 displays the standby screen 51 even after sending the start screen data, it may be able to accept access from multiple terminals. For example, if it accepts access from another mobile terminal before receiving start information (A25), MFP1 may also send start screen data to the other mobile terminal. In that case, once MFP1 receives start information from one terminal, it remembers that the mobile input function is being provided (B11), so even if it receives start information from another terminal, it will determine that it is being provided and execute B21. In addition, once MFP1 receives start information from one terminal, it may also send end screen data to other terminals.

[0100] After displaying the screen on the touch panel 131 for a predetermined display time in B19, or after sending unavailable screen data to the mobile terminal 2 in B21, the MFP1 continues to provide the mobile input function to other mobile terminals that have already started providing it. Once the provision of the mobile input function to that mobile terminal is finished, the MFP1 returns to standby mode as described above.

[0101] Furthermore, if MFP1 does not receive start information within a predetermined waiting period after sending start screen data via A21, MFP1 may choose not to start providing the mobile input function.

[0102] Next, we will explain what happens when the password received after access using mobile access information does not match the latest password stored in memory 12. If a mismatch is detected in A16 of Figure 5 (alt:[Mismatch]), MFP1 notifies the user to re-enter the password. That is, MFP1 sends re-entry screen data to mobile terminal 2 (A31). As a result, the browser 213 of mobile terminal 2 displays the re-entry screen on the touch panel 211 (A32).

[0103] The re-entry screen is, for example, a screen that includes a message indicating that the entered password is incorrect, and a password input field and a submit button similar to the password input screen 60 shown in Figure 6. The MFP1 may accept password re-entry up to a predetermined number of times, such as three times. If mismatched passwords are entered consecutively beyond the predetermined number of times, the MFP1 may refuse to accept access to the mobile input function from that mobile device for a predetermined period of unacceptable access. The unacceptable access period may be, for example, one hour, and may be a predetermined fixed time or a variable time that can be set by the user. The MFP1 can determine, for example, whether the access is from an unacceptable mobile device based on the IP address indicating the source of the accepted access.

[0104] MFP1 will not provide the mobile input function if the entered password is not up-to-date. By only allowing the mobile input function to be provided if the password displayed on the MFP1's touch panel 131 at that time is entered, the likelihood that the access is by a user nearby the MFP1 at that moment can be increased, thus ensuring greater security. In addition, if an outdated password is entered, the user will be notified to re-enter the password, thus avoiding confusion. This notification may also be accompanied by voice guidance.

[0105] As described later, in the function provision process shown in Figure 2, MFP1 generates a new password, for example, after a predetermined refresh time has elapsed, and displays a waiting screen 51 containing the new password. If a password other than the one included in the currently displayed waiting screen 51 is entered, MFP1 does not send start screen data or operation screen data, but instead notifies the user to re-enter the password. By disabling access when the latest password is not entered, it is highly likely that malicious users can prevent, for example, from using the mobile input function from a location away from MFP1.

[0106] Up to this point, we have explained the operation of MFP1 when the mobile input function is not provided due to a password mismatch. Next, we will explain the operation of MFP1 when the standby screen 51 is displayed and access from mobile terminal 2, etc. is not accepted (when S121 is NO). The processing when access using mobile access information is accepted and start screen data is sent in A21, and then operation on the "Exit" button 512 on the standby screen 51 is accepted will be described later.

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

[0108] After displaying the home screen 53 via S129, the MFP1 becomes capable of accepting operations on each displayed object. 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.

[0109] 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 11. 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 changed to the set number.

[0110] 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 11. If the operation is anything other than that (S137: NO), the CPU 11 performs other operations and returns to S131.

[0111] In other words, when the MFP1 receives an operation on the "Exit" button 512 included in the standby screen 51, it displays the home screen 53 on the touch panel 131 and becomes capable of accepting input operations from the control panel 13. This means that even though the MFP1 can accept input operations from the mobile terminal 2, it is possible to perform input operations to the MFP1 from the control panel 13 as needed, thus minimizing a decrease in usability and providing high convenience for users who prefer to perform input operations from the control panel 13.

[0112] If the CPU 11 determines that it is not accepting any operations on any of the objects displayed on the touch panel 131 (S131: NO), it determines whether the continuous time during which no operations have been accepted has reached a predetermined period of inactivity (S140). 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.

[0113] If the CPU 11 determines that an inactive period has elapsed without accepting any input (S140: YES), it returns to S102, similar to after completing the access reception procedure in S122. Subsequently, the CPU 11 executes S111 to S116 again to generate a new password and automatically displays a waiting screen 51 containing the new password on the touch panel 131. The elapsed in inactive period after accepting input to the "Exit" button 512 is an example of a predetermined execution condition. Note that while the MFP1 is displaying the execution screen on the touch panel 131, it is preferable not to determine the elapsed in inactive period, but rather to determine the elapsed in inactive period after displaying a screen different from the execution screen, such as a copy screen.

[0114] Furthermore, if the screen to be displayed in S133 is the home screen 53, the CPU 11 may proceed to S102 instead of displaying the home screen 53, as shown by the dashed line in Figure 2. In that case, 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.

[0115] 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.

[0116] As mentioned above, even after sending the start screen data in A21 of Figure 5, the standby screen 51 is displayed on the touch panel 131. If, after sending the start screen data, the MFP1 determines that it has received an operation to press the "Exit" button 512 without receiving start information (alt:[Exit], A27), the MFP1 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 8, and as a result, the exit screen shown in Figure 12 is displayed on the touch panel 211 of the mobile terminal 2 (A29).

[0117] In other words, even if the access reception procedure is terminated by accepting an operation to the "Exit" button 512 after sending the start screen data, MFP1 will display a screen that accepts user input on the touch panel 131, just as in the case where YES was determined in S128, and will be able to accept user input. In this case as well, MFP1 will 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 the time in S140 when the start screen data has not been sent.

[0118] 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.

[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 using mobile access information or any operation 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, generates a new password, and displays a new standby screen 51. The elapsed refresh time after displaying the standby screen 51 is an example of a predetermined execution condition.

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

[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 in S102. Resuming display after stopping the display by entering sleep mode is one example of a predetermined execution condition.

[0123] In this configuration, MFP1 generates a new password each time the mobile input function is terminated, and does not reactivate the mobile input function even if the previous password is entered. In other words, users who wish to reactivate the mobile input function must check the waiting screen 51 again and re-enter the latest password. This increases the likelihood that the access is coming from the mobile device 2 of the user currently in front of MFP1, thereby ensuring greater security.

[0124] As mentioned above, if MFP1 receives an instruction to terminate the provision of the mobile input function after it has started providing it and terminates the mobile input provision process (B15 in Figure 8), 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 may be shorter than the idle time, which is the time it takes to display the screen that accepts input after receiving an operation on the "Exit" button 512. An operation on 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 on 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 terminated, making it easier to accept user input.

[0125] 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 8.

[0126] 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.

[0127] Based on the received start screen data, the mobile terminal 2 displays the start screen 61 shown in Figure 7. 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".

[0128] If the status information received from MFP1 indicates "Not issued" (alt:[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).

[0129] 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).

[0130] If the 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 8. This provides the mobile input function, allowing the user to operate the MFP1 using the mobile terminal 2. However, in the second start procedure, when the 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. The 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 performs processing based on the operation data and sends new screen data. On the other hand, if the MFP1 determines that the received token is incorrect, it may immediately terminate the mobile input provision process.

[0131] 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).

[0132] 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.

[0133] 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.

[0134] As described in detail above, in the first embodiment, when the mobile input function has not yet been activated, the MFP1 displays the password required to activate the mobile input function on the touch panel 131 of the operation panel 13. When the password is entered from a mobile terminal 2 or the like, the mobile input function is activated. This increases the likelihood that the mobile input function will be activated when a user who will be using the mobile input function is in front of the MFP1, and as a result, the possibility of input being performed by a third party is reduced while the mobile input function can be provided.

[0135] Next, the MFP according to the second embodiment will be described in detail with reference to the attached drawings. The MFP1 of this embodiment has the same configuration as the MFP1 of the first embodiment, but differs from the first embodiment in that it uses different access information. The same reference numerals are used for the same components and procedures as the MFP1 of the first embodiment, and their explanation is omitted.

[0136] In this configuration, the MFP1 updates not only the password but also the access information as needed. In this configuration as well, the CPU 11 performs the same processing as the function provision processing shown in Figure 2 when it starts up. However, in this configuration, for example, when the CPU 11 generates a new password in S111 in Figure 2, it also generates a new key and generates access information that includes the generated key as a query. The key is, for example, a string containing multiple letters and numbers. Even in this configuration, S111 is just one example of the generation process.

[0137] In other words, in this configuration, the CPU 11 generates a different password and a different key each time it executes S111. Also, when the CPU 11 stores a new password in S112, it also stores a new key in memory 12. Then, in S113, the CPU 11 generates access information that includes the key generated in S111 as a query, in a URL containing a path that indicates information for starting the function via mobile input P22, as mobile access information.

[0138] Furthermore, the CPU 11 generates a two-dimensional code that encodes the generated mobile access information, and in S116, a standby screen containing the generated two-dimensional code and the password generated in S111 is displayed on the touch panel 131. The displayed standby screen is the same as the standby screen 51 shown in Figure 4, except that the information contained in the two-dimensional code is different from the first form. Note that in S112, the CPU 11 may store access information containing the key, or the information of the generated two-dimensional code, instead of storing the key.

[0139] Mobile terminal 2 accesses MFP1 using mobile access information, including a key, by reading a two-dimensional code displayed on the standby screen. When MFP1 in this configuration receives access via mobile access information, it first checks the key information contained in the received mobile access information. If MFP1 determines that the key contained in the mobile access information matches the latest key stored in memory 12, it sends password input screen data to mobile terminal 2 (A11 in Figure 5). The subsequent processing is the same as in the first configuration of MFP1.

[0140] On the other hand, if MFP1 determines that the mobile access information for the received access does not contain a key, or that the included key does not match the most recent key stored in memory 12, MFP1 will not send the password input screen data. In this case, MFP1 may send screen data to the mobile terminal 2, for example, a message requesting that the QR code on the waiting screen be scanned again.

[0141] In this configuration, the MFP1 dynamically generates keys and displays mobile access information including dynamic keys. This makes it possible to configure the system to reject access using outdated mobile access information, further enhancing the security of the mobile input function compared to the first configuration.

[0142] It should be noted that each embodiment is merely illustrative and does 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 instead of MFP1.

[0143] 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 across the entire touch panel 131 as shown in the standby screen 51 in Figure 4. Also, the display format of the mobile access information included in the standby screen 51 is not limited to the two-dimensional code image 511; it may also be text information or a barcode image.

[0144] Furthermore, when the mobile input function is launched, the screen displayed on the mobile terminal 2 is not limited to the home screen 62 shown in Figure 10. 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. Moreover, the screen displayed on the mobile terminal 2 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; it may be an original screen.

[0145] Furthermore, while mobile device 2 is described as displaying a screen based on received screen data in a browser, the program that displays the screen is not limited to a browser; it could also be a dedicated application program. However, displaying it in a browser eliminates the need to install a dedicated application program, making the mobile input function easier to use.

[0146] Furthermore, while mobile device 2 is defined as 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 device without a camera. If a device without a camera is used, the user can access MFP1 from the device without a camera 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 device.

[0147] Furthermore, MFP1 may not accept the setting to enable or disable the mobile input function based on the valid information 25. In other words, MFP1 may always have the mobile input function enabled.

[0148] Furthermore, while each embodiment displays a screen containing a QR code image and a password as a waiting screen, it is also possible to display a waiting screen containing only a QR code image, and display the password after access has been accepted. In that case, the MFP1 may generate a password and store it in memory 12 upon receiving access. Alternatively, the MFP1 in the first embodiment may display only the password as a waiting screen. For example, the URL used to initiate the mobile input function may be displayed on the casing of the MFP1.

[0149] Furthermore, in each embodiment, the MFP1 displays a standby screen including the "Exit" button 512, but it is also possible to display a standby screen that does not include the "Exit" button 512. In that case, for example, it may be possible to accept operation on any of the hardware keys 132 as an alternative to operating the "Exit" button 512. Also, in each embodiment, when operation on the "Exit" button 512 is accepted, the standby screen is automatically displayed again after no operation for a minute or so, but it is not limited to this. For example, the standby screen may not be displayed until a new operation, such as operation on the back key 133, is accepted.

[0150] Furthermore, in each embodiment, while the standby screen is displayed, only access from the 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 the MFP1 receives a long press of the back key 133, unlike operation of the "Exit" button 512, instead of displaying the operation screen and waiting for 1 minute, it may immediately generate a new password and display the standby screen. In other words, if the MFP1 receives a long press of the back key 133 while the standby screen is displayed, it does not need to display the operation screen. Alternatively, if the MFP1 receives a long press of the back key 133 while the standby screen is displayed, it may display the operation screen for a shorter time than in the case of operation of the "Exit" button 512.

[0151] Furthermore, in the start procedure of each embodiment (Figure 8), the MFP1 stores information indicating that the mobile input function is being provided when it receives start information from the mobile terminal 2 (B11), and determines 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 the latest password is entered (determined to be a match in A16 of Figure 5), the MFP1 may store that the mobile input function is being provided. Also, for example, when start screen data is sent in A21 of Figure 5, the MFP1 may store information indicating that start screen data has been sent, and if this information is stored, it may not send start screen data even if there is access to the mobile input function.

[0152] Furthermore, in each embodiment, the MFP1 measures the elapsed time during which it has not received operation data while providing the mobile input function and makes a timeout determination (S203 in Figure 11). However, the mobile terminal 2 may also make the timeout determination. For example, the mobile terminal 2 may send operation data indicating the termination of the mobile input function if the time during which it has not received operation data exceeds the timeout period after receiving screen data.

[0153] Furthermore, in each embodiment, if the back key 133 is pressed and held down while the mobile input function is being provided (YES in S204 of Figure 11), 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 pressing and holding the back key 133; it may also be a press and hold 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 press and hold, the input operation may also accept a normal input operation, multiple consecutive operations, and simultaneous pressing of multiple hardware keys, and the MFP1 may perform different processing depending on the type of input operation.

[0154] Furthermore, in each embodiment, 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 8), but this is not required. In other words, the MFP1 may immediately display a new standby screen after the mobile input provision process (Figure 11) is completed. Also, even if image formation is in progress when the mobile input provision process is terminated, the MFP1 may display, for example, the home screen 53 (Figure 3) instead of the execution screen 54 (Figure 13).

[0155] Furthermore, MFP1 may be able to accept user logins, for example, when using the mobile input function. For example, there may be a button to accept logins on the home screen 62, and MFP1 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 files to be printed in stored printing.

[0156] 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.

[0157] Furthermore, the processes disclosed in the embodiments may be executed by a single CPU, multiple CPUs, ASICs or other hardware, 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]

[0158] 1 MFP 2 Mobile devices 10 Controllers 11 CPU 12 memory 13. Control Panel 131 Touch Panel 141 Network Interface

Claims

1. Network interface and Control panel including touch panel, Controller and An image forming apparatus comprising, The image forming apparatus is It has a mobile input function that accepts input operations from a mobile terminal via the aforementioned network interface, The aforementioned controller, When the provision of the aforementioned mobile input function begins, A transmission process is performed to send display data for displaying the operation screen of the image forming apparatus on the mobile terminal to the mobile terminal via the network interface. Furthermore, the controller, While the mobile input function is being provided, if operation data indicating the operation content of the operation screen is received from the mobile 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 the execution of image formation, the image formation process that performs the image formation indicated in the received operation data is executed. Furthermore, the controller, The system is configured to perform a display process to show the password on the touch panel when the mobile input function has not been initiated. When access is made from the mobile terminal via the network interface using the access information necessary to initiate the provision of the mobile input function, and the mobile terminal enters the password displayed on the touch panel, the provision of the mobile input function is initiated. An image forming apparatus configured as follows.

2. In the image forming apparatus described in claim 1, In the aforementioned transmission process, The display data for displaying the operation screen for the image forming apparatus, which virtually shows the operation panel, on the mobile terminal is transmitted to the mobile terminal via the network interface. Furthermore, the controller, While the mobile input function is being provided, if the operation data is received from the mobile terminal that received the display data via the network interface, The mobile 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.

3. In the image forming apparatus described in claim 1, The access information includes a URL used to access the image forming apparatus. The aforementioned controller, When access using the URL included in the access information is made via the network interface from a browser installed in the mobile terminal, and the password displayed on the touch panel is entered from the mobile terminal, the provision of the mobile input function is initiated. In the transmission process, the web page data, which includes the operation screen for the image forming apparatus, is transmitted to the mobile terminal via the network interface as display data to be displayed in the browser installed in the mobile terminal. An image forming apparatus configured as follows.

4. In the image forming apparatus described in claim 1, The aforementioned controller, If, via the network interface, an access request is made from the mobile terminal using the access information necessary to initiate the provision of the mobile input function, and the mobile terminal enters the password displayed on the touch panel, the provision of the mobile input function will be initiated if the mobile input function is not currently being provided, and the provision of the mobile input function will not be initiated if the mobile input function is already being provided. An image forming apparatus configured as follows.

5. In the image forming apparatus described in claim 1, The aforementioned controller, The system is configured to execute a password generation process when predetermined execution conditions are met, and to store the generated password in memory. In the display process described above, the password stored in the memory is displayed on the touch panel. Furthermore, the controller, If the mobile terminal requests input of the password stored in the memory, the mobile input function will be initiated. The mobile input function will not be provided unless the password stored in the memory is entered from the mobile device. An image forming apparatus configured as follows.

6. In the image forming apparatus described in claim 5, In the aforementioned display process, The most recent password generated in the generation process is displayed on the touch panel. An image forming apparatus configured as follows.

7. In the image forming apparatus described in claim 5, The aforementioned controller, If the password entered from the mobile device is the most recent password among those stored in the memory, the mobile input function will be initiated. The mobile input function will not be provided unless the password entered from the mobile device is the most recent password among those stored in the memory. An image forming apparatus configured as follows.

8. In the image forming apparatus described in claim 7, The aforementioned controller, If the password entered from the mobile device is not the most recent password among those stored in the memory, the mobile input function will not be initiated, and the user will be notified to re-enter the password displayed on the touch panel. An image forming apparatus configured as follows.

9. In the image forming apparatus described in claim 5, The aforementioned predetermined execution conditions include the termination of the provision of the mobile input function. The aforementioned controller, After terminating the provision of the aforementioned mobile input function at the first timing, If the password generated in the generation process executed after the first timing is entered from the mobile terminal, the provision of the mobile input function will be initiated. If the password generated in the generation process performed before the first timing is entered from the mobile device, the provision of the mobile input function will not be started. An image forming apparatus configured as follows.

10. In the image forming apparatus described in claim 1, In the aforementioned display process, The access information is encoded in a code and the password is displayed on the touch panel, and the mobile terminal has a function to read the code and obtain the access information encoded in the code. The aforementioned controller, When access is made from the mobile terminal via the network interface using the access information encoded in the code, and the password displayed on the touch panel is entered from the mobile terminal, the provision of the mobile input function is initiated. An image forming apparatus configured as follows.

11. In the image forming apparatus described in claim 10, The aforementioned controller, The system is configured to execute a generation process that generates the access information and the password when predetermined execution conditions are met, and stores the generated access information and the password in memory. In the aforementioned display process, the access information and password stored in the memory are displayed on the touch panel. Furthermore, the controller, If the access is made using the access information stored in the memory, and the password stored in the memory is entered from the mobile terminal, the provision of the mobile input function will be initiated. The mobile input function will not be provided unless the access is made using the access information stored in the memory. Even if the access is made using the access information stored in the memory, the mobile input function will not be provided unless the password stored in the memory is entered from the mobile terminal. An image forming apparatus configured as follows.

12. In the image forming apparatus described in claim 11, In the aforementioned display process, The most recent access information and password generated in the generation process are displayed on the touch panel. An image forming apparatus configured as follows.

13. In the image forming apparatus described in claim 11, The aforementioned controller, If the access is made using the most recent access information stored in the memory, and the password entered from the mobile terminal is the most recent password stored in the memory, then the mobile input function will be initiated. The mobile input function will not be provided unless the access is made using the most recent access information stored in the memory. Even if the access is made using the most recent access information stored in the memory, the mobile input function will not be initiated unless the password entered from the mobile terminal is the most recent password stored in the memory. An image forming apparatus configured as follows.

14. In the image forming apparatus described in claim 13, The aforementioned controller, Even if the access is made using the most recent access information stored in the memory, if the password entered from the mobile terminal is not the most recent password stored in the memory, the mobile input function will not be initiated, and the user will be notified to re-enter the password displayed on the touch panel. An image forming apparatus configured as follows.

15. In the image forming apparatus described in claim 11, The aforementioned predetermined execution conditions include the termination of the provision of the mobile input function. The aforementioned controller, After terminating the provision of the aforementioned mobile input function at the first timing, If the access is made using the access information generated in the generation process executed after the first timing, and the password generated in the generation process executed after the first timing is entered from the mobile terminal, the provision of the mobile input function is started. If the access is made using the access information generated in the generation process performed before the first timing, the provision of the mobile input function will not be initiated. Even if the access is made using the access information generated in the generation process executed after the first timing, if the password generated in the generation process executed before the first timing is entered from the mobile terminal, the provision of the mobile input function will not be initiated. An image forming apparatus configured as follows.

Images