JP2023139685A - Image formation apparatus - Google Patents

Abstract

To provide a technique of improving an input method which can operate an image formation apparatus having an operation panel without touching the operation panel.SOLUTION: An MFP 101 includes a mobile input function which receives an input operation via a network IF 141. The MFP 101 starts provision of the mobile input function when receiving from a mobile terminal 2 an access necessary for starting provision of the mobile input function via a WFD 24 in such a state that provision of the mobile input function has not been started, and does not start provision of the mobile input function when receiving from the mobile terminal 2 the access necessary for starting provision of the mobile input function not via the WFD 24. The MFP 101 transmits to the mobile terminal 2 via the network IF 141 display data for making the mobile terminal 2 display an operation screen to the MFP 101 when starting provision of the mobile input function.SELECTED DRAWING: Figure 15

Description

The technical field disclosed herein relates to an image forming apparatus including an operation panel.

2. Description of the Related Art Image forming apparatuses are capable of forming images such as printing and scanning, and techniques for accepting various input operations via an operation panel are known. For example, Patent Document 1 discloses a function execution device that includes a printing section, an image reading section, and an operation panel, and the operation panel includes hardware keys and a touch panel, and the operation panel can perform input operations on the hardware keys. A configuration is disclosed that accepts input operations to icons or buttons displayed on a touch panel.

Japanese Patent Application Publication No. 2012-73543

In recent years, there has been a tendency for an increasing number of users to dislike input operations on an operation panel that is touched by an unspecified number of people, and there is an increasing demand for making it possible to perform input operations on an image forming apparatus without touching the operation panel. On the other hand, it is undesirable from the viewpoint of security to allow such input operations implicitly. Patent Document 1 does not disclose a technique for operating without touching the operation panel, and there is room for improvement.

An image forming apparatus disclosed in this specification includes a network interface, an operation panel including a touch panel, and a controller, and the image forming apparatus connects to a mobile terminal via the network interface. The controller has a mobile input function that accepts an input operation from the image forming apparatus, and the controller is configured to provide the mobile input function via a network provided by the image forming apparatus in a state where the provision of the mobile input function has not started. If access necessary for starting is received from the mobile terminal, the provision of the mobile input function is started, and the provision of the mobile input function is started without going through the network provided by the image forming apparatus. When the necessary access is received from the mobile terminal, the controller does not start providing the mobile input function, and further, when the controller starts providing the mobile input function, the controller displays an operation screen for the image forming apparatus. executing a transmission process for transmitting display data to be displayed on the mobile terminal to the mobile terminal via a network provided by the image forming apparatus; and further, while providing the mobile input function; When operation data indicating operation details on the operation screen is received from the mobile terminal via the network provided by the image forming apparatus, the received operation data is an operation related to setting parameters used for image formation. If there is, execute a setting process to set the parameters indicated in the received operation data, and if the received operation data is an operation related to execution of image formation, perform image formation indicated in the received operation data. The image forming apparatus is configured to execute image forming processing.

The image forming apparatus disclosed in this specification has a mobile input function, starts providing the mobile input function by restricting access via a network provided by the image forming apparatus, and starts image forming. Do not start providing mobile input functionality if access is not via a network provided by the device. This makes it difficult for the image forming apparatus to be operated from a distance, increasing safety.

Also new and useful are control methods, computer programs, and computer-readable storage media storing the computer programs for implementing the functions of the devices described above.

According to the technology disclosed in this specification, a technology for improving an input method for operating an image forming apparatus without touching the operation panel in an image forming apparatus including an operation panel is realized.

1 is a block diagram showing a schematic configuration of a first form of MFP. FIG. 3 is a flowchart showing the procedure of function provision processing. It is an explanatory diagram showing an example of a home screen. It is an explanatory diagram showing an example of a standby screen. FIG. 3 is a sequence diagram illustrating an example of an access reception procedure. It is an explanatory diagram showing an example of a start screen. FIG. 3 is a sequence diagram showing an example of a start procedure. FIG. 3 is an explanatory diagram showing an example of an on-provision screen. It is an explanatory diagram showing an example of an operation screen. 3 is a flowchart showing the procedure of mobile input providing processing. It is an explanatory diagram showing an example of an end screen. It is an explanatory diagram showing an example of an execution screen. FIG. 7 is an explanatory diagram showing an example of a re-reading screen. FIG. 7 is a sequence diagram showing an example of a second start procedure. FIG. 2 is a block diagram showing a schematic configuration of a second form of MFP. It is an explanatory diagram showing an example of a standby screen. 3 is a flowchart illustrating the procedure of access permission determination processing. 3 is a flowchart showing the procedure of remote input providing processing. FIG. 3 is an explanatory diagram showing a panel usage permission screen. 3 is a flowchart illustrating the procedure of operation response processing.

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

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

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

The memory 12 of the MFP 1 of this embodiment includes 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. is memorized. The mobile input P22 is a program that includes an embedded web server function and provides a mobile input function using the embedded web server function. The mobile input P22 includes programs and data for making the MFP 1 function as a web server.

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

Note that the computer-readable storage medium is a non-transitory medium. In addition to the above-mentioned examples, non-transitory media also include storage media such as CD-ROM and DVD-ROM. Furthermore, non-transitory media are also tangible media. On the other hand, electrical signals that carry programs downloaded from servers on the Internet are a type of computer-readable signal medium, but non-transitory computer-readable storage Not included in media.

The operation panel 13 includes hardware that displays a screen for notifying the user of information, and hardware that accepts operations by the user. The operation panel 13 of the MFP 1 of this embodiment includes a touch panel 131 having a screen display function and an operation acceptance function, and one or more hardware keys 132 having only an operation acceptance function.

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 the MFP 1 may further include a communication IF compatible with other communication standards.

The print engine 15 includes a configuration for printing an image on a print medium such as a sheet. The image forming method of the print engine 15 is, for example, an electrophotographic method or an inkjet method. Scanner 16 includes a configuration for reading an image of a document. The scanner 16 may include an automatic document feeder.

Next, the operation of the MFP 1 will be explained. Note that the following processing basically indicates processing of the CPU 11 according to instructions written in a program. That is, the processes such as "judgment", "extraction", "selection", "calculation", "determination", "identification", "acquisition", "reception", and "control" in the following explanation are performed by the CPU 11. represents. The processing by the CPU 11 also includes hardware control using the OS API. In this specification, the operation of each program will be explained without describing the OS. That is, in the following description, a statement to the effect that "program B controls hardware C" may also refer to "program B controls hardware C using an API of the OS." Further, the processing of the CPU 11 in accordance with instructions written in a program may be described in abbreviated terms. For example, it may be written as "performed by the CPU 11". Further, the processing of the CPU 11 in accordance with instructions written in a program may be described in words such as "performed by program A", omitting the CPU.

Note that "acquisition" is used as a concept that does not require a request. That is, the process of receiving data without a request from the CPU 11 is also included in the concept of "the CPU acquires data." Furthermore, "data" in this specification is represented by a computer-readable bit string. Furthermore, data having substantially the same meaning and content but different formats shall be treated as the same data. The same applies to "information" in this specification. Furthermore, "request" and "instruction" are concepts that indicate outputting information indicating a request or information indicating an instruction to the other party. Further, information indicating that a request is being made or information indicating that an instruction is being given is simply referred to as a "request" or "instruction."

Furthermore, the process of determining whether information A indicates matter B by the CPU 11 may be conceptually described as "determining whether information A is matter B or not." There is. The process of determining whether information A indicates matter B or matter C by the CPU 11 is called ``determining whether information A is matter B or matter C. It may be described conceptually, such as ``.

The procedure of a function providing process for providing various functions in response to user operations in the MFP 1 equipped with various functions such as a mobile input function using the mobile input P22 will be described with reference to the flowchart in FIG. 2. This function providing process is executed by the CPU 11 of the MFP 1 upon activation of the MFP 1.

The CPU 11 initializes each part such as the memory 12 (S101), and determines whether or not the validity information 25, which is information indicating the validity of the mobile input function, is stored in the memory 12 (S102). The MFP 1 receives an instruction to set the enable information 25, that is, a setting instruction to enable or disable the mobile input function, via the USB-IF 142, for example. The USB-IF 142 in this case is an example of an external interface. When the MFP 1 receives the input of the valid information 25, the MFP 1 stores the valid information 25 in the nonvolatile storage area of the memory 12, as shown in FIG. Validity information 25 is an example of setting information. Since the validity information 25 allows the mobile input function to be enabled or disabled, the usability for the user is improved.

The MFP 1 may not accept an instruction to set the valid information 25 via the network IF 141. Alternatively, the MFP 1 may be able to accept setting instructions via the network IF 141 if the instructions are from a user with administrator authority. The network IF 141 in this case is an example of an external interface. The valid information 25 is important information for determining 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, instructions from a user with administrator authority, etc. Unauthorized changes by third parties can be restricted.

If it is determined that the valid information 25 is not stored in the memory 12, that is, the mobile input function is not valid (S102: NO), the CPU 11 does not generate the access information and, for example, generates the access information as shown in FIG. The home screen 53 is displayed on the touch panel 131 (S105). The home screen 53 is an example of a main body operation screen. The home screen 53 is a screen that includes various objects that accept input operations such as selection of functions to be performed by the MFP 1 and various setting instructions.

If the mobile input P22 is not valid, the MFP 1 does not provide the function of the mobile input P22, accepts an operation on the touch panel 131, and operates based on the accepted operation (S106). If the mobile input P22 is not valid, the MFP 1 operates based on the user's operation on the touch panel 131, similar to S131 to S140 described later. Specifically, when the MFP 1 receives an instruction to set parameters, it sets the parameters, and when it receives an instruction to perform image formation, it executes image formation using the set parameters. Then, as in the case of YES in S140, if the predetermined no-operation time elapses without any operation on the operation panel 13, the CPU 11 returns to S102 and displays the home screen 53 again. Note that even when receiving an operation to instruct display of the home screen via the operation panel 13, the CPU 11 causes the home screen 53 to be displayed on the touch panel 131.

Since the MFP 1 of this embodiment accepts a setting as to whether or not to enable the mobile input function, it can also be set not to use the mobile input function, improving usability for the user. Note that, for example, when the CPU 11 receives a setting to enable the mobile input function and then receives a setting to disable the mobile input function, if the key 26 (see FIG. 1), which will be described later, is stored, The stored key 26 may also be deleted.

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

Specifically, the CPU 11 generates a key (S111) and stores the generated key in the memory 12 (S112). The key is, for example, a character string including a plurality of characters, and the CPU 11 generates a different key each time S111 is executed. Through S112, the latest key 26 is stored in the memory 12, as shown in FIG. Note that in S112, the MFP 1 may overwrite the key and store only the latest key, or it may store multiple keys and store information indicating that the latest key is the latest or the generation date and time. It is also possible to add and store information indicating.

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

Furthermore, the CPU 11 encodes the latest access information generated in S113 to generate the latest two-dimensional code, for example, a QR code (registered trademark) (S115), and displays a standby screen containing the generated code. It is displayed on the touch panel 131 of the operation panel 13 (S116). S116 is an example of display processing. As a result, the latest standby screen 51 including the latest two-dimensional code is displayed on the touch panel 131, for example, as shown in FIG. The standby screen 51 is a screen that includes a two-dimensional code image 511, which is an image in which access information is encoded, and an "Exit" button 512. By displaying the standby screen 51 that includes the two-dimensional code image 511 that includes the latest key 26 and does not include the two-dimensional code image that is not the latest, it is possible to avoid complicating the display of access information.

Then, the CPU 11 determines whether access from the mobile terminal 2 or the like has been accepted (S121). A user who uses the mobile input function on the MFP 1 of this embodiment uses a mobile terminal 2 that can be connected to the same network as the MFP 1. Communication between the network IF 141 and the access point may be wireless communication using Wi-Fi (registered trademark) or the like, or wired communication using a wired LAN or the like.

The mobile terminal 2 includes a touch panel 211 and a camera 212, as shown in FIG. The memory of the mobile terminal 2 stores various programs including a browser 213 and various data. Note that the mobile terminal 2 is a device that can be connected to a network, and is, for example, a smartphone or a tablet computer. The mobile terminal 2 is an example of a mobile terminal, and is also an example of an operating terminal.

Further, the same network is, for example, a network provided by the same access point. It is only necessary that the mobile terminal 2 and the MFP 1 are connected to the same access point. Alternatively, a plurality of access points may form one network, and in that case, the mobile terminal 2 and MFP 1 only need to be connected to any one of the plurality of access points forming the network. Note that the mobile terminal 2 and the MFP 1 may be connectable to the Internet via an access point.

For example, the user activates the camera 212 of the mobile terminal 2 and photographs the two-dimensional code image 511 displayed on the touch panel 131 of the MFP 1. The mobile terminal 2 can acquire the encoded access information by analyzing the photographed two-dimensional code image 511. Since the read two-dimensional code image 511 includes a URL, the mobile terminal 2 displays a pop-up message on the touch panel 211 to inform the user whether or not to access the destination device indicated by the URL. Inquire. Upon receiving the access instruction from the user, the mobile terminal 2 starts the browser 213 and accesses the MFP 1 based on the acquired access information.

As described above, the access information included in the two-dimensional code image 511 includes a URL and a key. Based on the access information, the browser 213 sends an HTTP request according to the http protocol or an HTTPS request according to the https protocol. Note that, hereinafter, an HTTP request or an HTTPS request will simply be referred to as a "request." The browser 213 of the mobile terminal 2 identifies the network address of the destination device indicated by the URL included in the access information, and sends a request including a path indicated by the URL, a query including a key, etc. to the destination device. .

By using the mobile terminal 2 in front of the MFP 1, the user can easily access the MFP 1 and easily use the mobile input function without having to remember access information. Since the MFP 1 of this embodiment displays a two-dimensional code image 511 that can be read by the mobile terminal 2, the user can easily access it using the camera 212 of the mobile terminal 2. Note that the MFP 1 may display the URL in text. Even in this case, although the user has to input the access information, there is no need to remember the access information, so access to the MFP 1 is easy.

If it is determined that an access specifying a path indicating a mobile input function has been received (S121: YES), the CPU 11 executes an access reception procedure that is a procedure when an access is received (S122). However, if the valid information 25 is not stored in the memory 12 and the mobile input function is not valid, the CPU 11 returns NO in S121 even if it receives an access specifying a path indicating the mobile input function. to decide.

Next, the access reception procedure will be explained with reference to the sequence diagram of FIG. 5. Upon receiving the access specifying the path indicating the mobile input function, the MFP 1 executes processing using the mobile input P22.

The MFP 1 first obtains the key included in the access information as a query (A11), and checks whether the obtained key matches the latest key 26 stored in the memory 12 (A12). .

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

The browser 213 of the mobile terminal 2 is configured to, when receiving web page data from the MFP 1 in response to the transmitted request, display a web page on the touch panel 211 that is a screen based on the received data. When the browser 213 receives the start screen data transmitted in A21, the browser 213 displays the start screen 61 on the touch panel 211, for example, as shown in FIG. 6 (A23). The start screen 61 is a screen that includes a start button 611.

When the browser 213 of the mobile terminal 2 receives an operation on the touch panel 211 by the user while displaying a screen based on the web page data transmitted from the MFP 1, the browser 213 of the mobile terminal 2 includes operation data indicating the content of the received operation. It is configured to send a request to MFP1. Note that the operation data may be object information indicating the object that has accepted the operation, or may be position information indicating the operation position on the touch panel 211.

The MFP 1 determines whether or not operation data indicating an operation on the start button 611 has been received from the mobile terminal 2, and whether or not it has received an operation on the "Exit" button 512 on the standby screen 51 currently displayed on the touch panel 131. to judge.

First, a case will be described where it is determined that operation data indicating an operation on the start button 611 has been received (alt: [start]). When the mobile terminal 2 receives the user's operation on the start button 611 (A24), the mobile terminal 2 transmits operation data indicating the operation on the start button 611 to the MFP 1 (A25). The operation on the start button 611 is an instruction by the user to cause the MFP 1 to start providing the mobile input function. As a result, the MFP 1 receives operation data (hereinafter referred to as "start information") indicating an operation on the start button 611.

The MFP 1 provides a function in response to the user's clear intention to use the mobile input function, which is an operation on the start button 611. That is, it is possible to prevent the provision of the mobile input function from being started inadvertently due to a user's erroneous operation or the like.

The MFP 1 executes the start procedure shown in FIG. 7 in response to receiving the start information. In the start procedure, the MFP 1 first determines whether a mobile input function is being provided (B01). For example, if information indicating that the mobile input function is currently being provided is stored in the memory 12, the mobile input P22 determines that the mobile input function is currently being provided. Information indicating that the mobile input function is being provided is stored in the memory 12 at B11, for example.

When determining that the mobile input function is not being provided (alt: [not being provided]), the MFP 1 stops displaying the standby screen 51 and displays the providing screen 52 on the touch panel 131, for example, as shown in FIG. (B10). B10 is an example of a provision display process. The providing screen 52 is a screen that includes a message indicating that the device is connected to another device, but does not include any objects that accept operations. When the MFP 1 starts providing the mobile input function, the MFP 1 does not display on the touch panel 131 any screens that include access information, such as the standby screen 51 shown in FIG. 4, or screens that include objects that accept various operations. MFP 1 does not accept input operations on touch panel 131 while providing mobile input functionality to mobile terminal 2 .

If an input operation to the touch panel 131 is accepted while the mobile input function is being provided, an operation that is not intended by the user operating the mobile terminal 2 may be performed, which may confuse the user. Since the MFP 1 of this embodiment does not accept input operations on the touch panel 131 while providing the mobile input function, such a problem does not occur. Furthermore, since the MFP 1 of this embodiment displays the providing screen 52 on the touch panel 131 while providing the mobile input function, it is easy to understand that input operations to the touch panel 131 are not accepted.

Furthermore, if it is possible to accept access from other mobile terminals while the mobile input function is being provided, an operation that is not intended by the user operating the mobile terminal 2 may be performed, which may confuse the user. Since the MFP 1 of this embodiment does not display the standby screen 51 on the touch panel 131 while providing the mobile input function, it is possible to reduce the possibility of receiving access from other users.

Then, the MFP 1 stores information indicating that the mobile input function is being provided (B11), and transmits home screen data, which is web page data indicating the home screen, to the mobile terminal 2 (B12). B12 is an example of transmission processing. Home screen data is an example of display data. Furthermore, the MFP 1 stores the screen ID indicating the transmitted screen in the memory 12 (B13). The screen ID in this case is information indicating the last screen data transmitted to the mobile terminal 2, that is, the home screen.

Having received the home screen data at B12, the browser 213 of the mobile terminal 2 displays the home screen 62 on the touch panel 211, for example, as shown in FIG. 9 (B14). The home screen 62 is an operation screen that virtually shows the operation panel 13 in a state where the home screen 53 shown in FIG. 3 is displayed, for example. The home screen 62 includes a panel screen 621 imitating the home screen 53, a key screen 622 imitating 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 MFP 1.

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

Then, the MFP 1 executes mobile input providing processing (B15). The mobile input providing process executed at B15 will be explained with reference to the flowchart of FIG. The mobile input providing process is executed by the CPU 11 of the MFP 1 based on the mobile input P22. At the start of execution of this mobile input providing process, the home screen 62 shown in FIG. 9 is displayed on the touch panel 211 of the mobile terminal 2, and the providing screen 52 shown in FIG. 8 is displayed on the touch panel 131 of the MFP 1. Displayed.

After transmitting the screen data to the mobile terminal 2, the CPU 11 starts measuring the elapsed time in a state where no request is received from the mobile terminal 2 (S201). At the start of the mobile input providing process, the CPU 11 measures the elapsed time after transmitting the home screen data at B12 in FIG.

Then, the CPU 11 determines whether a request has been received from the mobile terminal 2 (S202). If it is determined that a request has been received (S202: YES), the CPU 11 resets the elapsed time and restarts measurement (S211). Then, the CPU 11 determines whether the operation data included in the received request is data indicating an operation on the close button 623 (see FIG. 9) (S212).

If it is determined that operation data indicating an operation other than the operation on the close button 623 has been received (S212: NO), the CPU 11 determines whether the received operation data is an operation that changes the display screen ( S221). If it is determined that the operation is to change the display screen (S221: YES), the CPU 11 transmits screen data indicating the changed screen to the mobile terminal 2 (S222). S222 is an example of transmission processing. The screen data transmitted to the mobile terminal 2 in S222 is an example of display data.

For example, when receiving operation data indicating that an operation to the "copy" button on the panel screen 621 has been accepted on the home screen 62 shown in FIG. Screen data of a copy screen, which is a screen for accepting requests, is transmitted to the mobile terminal 2. The operation screen for accepting parameter settings is also referred to as a parameter setting screen. As a result, a 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.

In the mobile input providing process, the CPU 11 transmits only the web page data of the panel screen 621, unlike the case of B12 in FIG. 7, at S222 and subsequent screen data transmission. That is, during execution of the mobile input providing 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 in S222 or the like, the close button 623 is displayed on the touch panel 211 of the mobile terminal 2.

If it is determined that the received operation data is not an operation for changing the display screen (S221: NO), the CPU 11 determines whether the operation is for setting parameters used for image formation (S224). If it is determined that the operation is related to setting parameters (S224: YES), the CPU 11 sets parameters based on the received operation data (S225). S225 is an example of setting processing.

Further, the CPU 11 transmits screen data indicating the screen after setting to the mobile terminal 2 (S226). For example, when the specification of the number of copies is accepted on the above-mentioned copy screen, the CPU 11 sets the accepted number of copies as a copy parameter, and transmits to the mobile terminal 2 the data of the copy screen in which the display of the number of copies has been changed.

If it is determined that the received operation data is not an operation related to parameter setting (S224: NO), the CPU 11 determines whether the received operation data is an operation related to execution of image formation (S227). If it is determined that the operation is related to execution of image formation (S227: YES), the CPU 11 starts execution of image formation based on the received operation data (S228). S228 is an example of image forming processing.

For example, when receiving operation data indicating that a copy execution instruction button has been operated on the copy screen, the CPU 11 causes the scanner 16 to start reading the original, and causes the print engine 11 to print based on the image of the read original. Copying starts by instructing the user to perform the copy. The operation screen for accepting execution instructions is also referred to as an execution instruction screen. The copy screen is an example of a parameter setting screen and an example of an execution instruction screen. Generation of image data by the scanner 16 and printing by the print engine 15 are examples of image formation.

Then, the CPU 11 transmits screen data of a screen indicating that the process is being executed to the mobile terminal 2 (S229). The screen indicating that image formation is in progress includes a message indicating that image formation is in progress, and does not include any objects other than the close button 623 that accept operations. For example, the CPU 11 transmits screen data including a message “copying in progress” to the mobile terminal 2. Note that the CPU 11 may temporarily stop measuring the elapsed time since it does not accept any operations while image formation is being performed, that is, while a screen indicating that image formation is being displayed is displayed. Further, the screen indicating that image formation is in progress may include an object that accepts an operation, such as an object that accepts an operation to cancel execution of image formation.

The various screens displayed on the panel screen 621 imitate the various screens displayed on the touch panel 131 when the MFP 1 is used by operating the touch panel 131 of the MFP 1. For example, when the mobile input function is not provided and the copy button is operated on the touch panel 131 of the MFP 1 (YES in S132 in FIG. 2), the copy screen described above is displayed on the touch panel in S133 in FIG. This screen is similar to the screen displayed in 131. For example, the screen containing the above-mentioned "copy in progress" message may be displayed when the copy execution instruction button is operated on the touch panel 131 of the MFP 1 (YES in S137 in FIG. 2) when the mobile input function is not provided. This screen is similar to the screen displayed on the touch panel 131 in S139 of FIG. 2 in the case of FIG.

On the other hand, if it is determined that the received operation data is not an operation related to execution of image formation (S227: NO), the CPU 11 returns to S202 and determines whether or not operation data from the mobile terminal 2 has been received. . For example, when receiving operation data indicating an operation on a part other than an object on the touch panel 211 of the mobile terminal 2, the CPU 11 may only reset the elapsed time in S211, change the screen, or change the parameters. Neither settings nor image formation are performed.

After transmitting the screen data in either S222, S226, or S229, the CPU 11 stores the screen ID that identifies the transmitted screen data in the memory 12 (S231), returns to S202, and transmits the request from the mobile terminal 2. is received. The CPU 11 may overwrite and store the screen ID in a predetermined area, or may store a plurality of screen IDs and store the screen ID as information indicating the last transmitted screen ID.

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

If it is determined that the timeout period has not been exceeded (S203: NO), the CPU 11 determines whether or not a long press of the return key 133 (see FIG. 4) has been accepted (S204). The return key 133 is included in the hardware keys 132 of the operation panel 13.

If it is determined that operation data indicating an operation to the close button 623 has been received from the mobile terminal 2 (S212: YES), or if it is determined that the elapsed time has exceeded the timeout period (S203: YES), or the return key is pressed. If it is determined that the long press of 133 has been accepted (S204: YES), the CPU 11 ends the mobile input providing process and returns to the start procedure in FIG.

The close button 623 is a button operated by the user on the mobile terminal 2 to end the use of the mobile input function. The operation on the close button 623 is an operation indicating the user's intention to end the use of the mobile input function.

Since the MFP 1 ends the mobile input function based on the operation of the close button 623, the mobile input function can be ended at the timing intended by the user using the mobile terminal 2. As a result, another user can operate the MFP 1, and the operating rate of the MFP 1 can be increased. Note that the close button 623 is included in the screen displayed on the touch panel 211 of the mobile terminal 2, but not included in the screen displayed on the touch panel 131 of the MFP 1.

Furthermore, if the elapsed time exceeds the timeout period without any request from the mobile terminal 2, it is highly likely that the user of the mobile terminal 2 has finished using the MFP 1. Alternatively, the communication connection between the MFP 1 and the mobile terminal 2 may be disconnected. By terminating the mobile input function when no request is received after a predetermined timeout period, for example, the user of the mobile terminal 2 can perform an operation to terminate the mobile input function when he or she has finished using the MFP 1. Even if the MFP 1 does not do so, the MFP 1 can automatically end providing the mobile input function. As a result, another user can use the MFP 1, so it is possible to avoid wasteful occupation of the MFP 1 by the mobile terminal 2 and increase the operating rate of the MFP 1.

Further, the long press of the return key 133 is an operation performed by a user who wants to end the mobile input function being provided and use the MFP 1 by operating the operation panel 13. For example, if the user of the mobile terminal 2 finishes using the MFP 1 and leaves the MFP 1 without performing an operation to terminate the mobile input function, another user may forcibly move the mobile input function by pressing and holding the return key 133. The provision of the input function can be terminated. As a result, the other user can operate the MFP 1 even if the timeout period has not been exceeded, and the operating rate of the MFP 1 can be increased.

Note that while the MFP 1 is providing the mobile input function, the MFP 1 does not accept any operations on the hardware keys 132 or the touch panel 131 other than an instruction to terminate the mobile input function by pressing and holding the return key 133. By disabling input operations to the operation panel 13 other than instructions to terminate the provision of the mobile input function, it is possible to prevent input operations from the mobile terminal 2 and input operations from the operation panel 13 for the mobile input function from being mixed. It can be avoided. For example, it is possible to avoid the possibility that an unintended operation by the user of the mobile terminal 2 will be accepted even if another user carelessly operates the operation panel 13 without knowing that the mobile input function has been provided.

Note that the mobile input P22 is configured to terminate the mobile input providing process without waiting for the elapsed time to exceed the timeout period when it is determined that the communication connection between the MFP 1 and the mobile terminal 2 has been disconnected. Also good. For example, if the network IF 141 becomes unable to connect to the Internet or if it is detected that the mobile terminal 2 is no longer connected to the Internet, the CPU 11 ends the mobile input providing process and returns to the start procedure in FIG. It's okay.

On the other hand, if the CPU 11 determines that the conditions for terminating the mobile input providing process such as an operation on the close button 623 are not satisfied (S204: NO), the CPU 11 determines whether or not execution of image formation has been terminated (S205). ). If it is determined that the execution of image formation has ended (S205: YES), the CPU 11 transmits the home screen data to the mobile terminal 2 (S215). Note that while image formation is being executed, a screen indicating that the image formation is being executed is displayed on the mobile terminal 2 in step S229 described above. By S215, the display on the mobile terminal 2 is changed from the screen indicating that the process is being executed to the home screen 62. After transmitting the home screen data, the CPU 11 stores the screen ID that identifies the transmitted screen data in the memory 12 (S231), and returns to S202.

If image formation has not started or if image formation is in progress, it is determined that image formation has not finished (S205: NO), and the CPU 11 returns to S202 and executes S202. It is determined whether any of the conditions from to S205 are satisfied.

Note that the MFP 1 may be configured to be able to accept various instructions even while image formation is in progress. In that case, the CPU 11 may transmit home screen data instead of screen data indicating that the process is being executed in S229. Alternatively, the MFP 1 may once transmit screen data indicating that the process is being executed to the mobile terminal 2, and then transmit the home screen data before the image formation ends. Further, in that case, the determination in S205 may be omitted.

Returning to the explanation of the start procedure in FIG. 7. If the MFP 1 determines YES in any of S203, S204, and S212 of the mobile input providing process shown in FIG. 10, it ends the mobile input providing process (B15). After that, the MFP 1 transmits end screen data, which is web page data indicating that provision of the mobile input function has ended, to the mobile terminal 2 (B16). Thereby, the browser 213 of the mobile terminal 2 displays the end screen 63 on the touch panel 211, for example, as shown in FIG. 11 (B17). Note that if communication with the mobile terminal 2 is disconnected, the MFP 1 may skip B16.

Then, the MFP 1 deletes the information indicating that the mobile input function is being provided (B18). Alternatively, the MFP 1 may change information indicating that the information is being provided to information indicating that the information is not being provided and store the changed information.

Up to this point, we have explained the steps from the start to the end of providing the mobile input function. Next, the operation of the MFP 1 after the provision of the mobile input function is finished, for example, the content displayed on the touch panel 131 will be described.

After finishing providing the mobile input function, the MFP 1 displays the screen corresponding to the stored screen ID on the touch panel 131 (B19). As a result, a screen similar to the screen displayed on the mobile terminal 2 at the end of the mobile input function is displayed on the touch panel 131. Note that the screen displayed on the touch panel 131 at B19 is not exactly the same as the screen displayed on the mobile terminal 2, but may be a somewhat different screen containing the same type of information.

Note that if the mobile input providing process ends while image formation is not in progress, for example, if the mobile input providing process ends while the home screen 62 is being displayed, the MFP 1 displays the home screen 53 shown in FIG. Displayed on the touch panel 131. For example, if the mobile input providing process ends while the copy screen is being displayed, the MFP 1 displays the copy screen on the touch panel 131. Then, the MFP 1 becomes capable of accepting a user's operation on the touch panel 131, and when accepting an operation on the touch panel 131, operates based on the received operation.

This is convenient for a user who has started an operation on the mobile terminal 2 but wants to continue the operation on the touch panel 131 midway through, since the user can switch to the operation on the touch panel 131 by operating the close button 623. Further, it is convenient for a user who accidentally operates the close button 623 because the user can continue operating the touch panel 131. Note that if the mobile input providing process is terminated due to a timeout or a long press of the return key 133 while the settings screen or execution instruction reception screen is displayed, the MFP 1 returns the information displayed on the mobile terminal 2 at B19, for example. The home screen 53 may be displayed instead of the screen.

If the mobile input providing process ends while image formation is not in progress, and there is no operation on the touch panel 131 for a predetermined display time after the home screen 62 is displayed on the touch panel 131 at B19, the MFP 1: Returning to S102 in FIG. The display time is, for example, 30 seconds, and may be a predetermined fixed time or a variable time that can be set by the user.

On the other hand, if, for example, the mobile input providing process is terminated by accepting an operation on the close button 623 or a long press of the return key 133 while printing is being executed, the MFP 1 may, for example, as shown in FIG. An execution screen 54 including a message indicating that the execution is executed is displayed on the touch panel 131. If the user operates the close button 623 to end the mobile input function while executing a job based on an instruction from the mobile terminal 2, and the home screen 53 or the like is displayed on the touch panel 131 immediately after that, The user may be concerned about whether the job is being executed. If the job is being executed, the user's anxiety can be alleviated by displaying the execution screen 54.

Note that when the MFP 1 determines that the execution of image formation has ended while the execution screen 54 is displayed on the touch panel 131, the MFP 1 displays the home screen 53 shown in FIG. It becomes possible to accept user operations. After that, if there is no operation on the touch panel 131 for a predetermined display time, the MFP 1 returns to S102 in FIG. 2.

Furthermore, the display of the home screen 53 at B19 is the same process as S129 in FIG. Therefore, after displaying the home screen 53 at B19, the MFP 1 may execute the processes from S131 onwards in FIG. In that case, in S140, the CPU 11 may determine whether the display time has elapsed, rather than the no-operation time. Although the time is longer than the display time, the CPU 11 may determine whether the no-operation time has elapsed.

Up to this point, we have explained the steps to be taken after the provision of the mobile input function ends. Next, the operation of the MFP 1 when the mobile input function is not provided will be described.

When the start information is received from the mobile terminal 2 (A25 in FIG. 5), if information indicating that the mobile input function is already being provided is stored, that is, if the mobile input function is not provided to other mobile terminals. If so, the MFP 1 determines that the mobile input function is being provided (B01). If it is determined that the function is currently being provided (alt: [currently being provided]), the MFP 1 displays a screen containing a message informing that the function is currently being provided to other mobile terminals and is not currently available. The currently provided screen data is transmitted to the mobile terminal 2 (B21). Note that the currently provided screen data sent to the mobile terminal 2 by B21 may be, for example, screen data showing a screen similar to the currently provided screen 52 shown in FIG. 8, or may be screen data of a different screen containing a similar message. good. The MFP 1 of this embodiment does not provide a mobile input function to two or more mobile terminals at the same time.

The mobile terminal 2 displays a screen indicating that the mobile input function is currently being provided on the touch panel 211 based on the received currently providing screen data (B22). The screen indicating that the provision is in progress displayed on B22 is a screen that does not include an object that accepts operations by the user, and even if an operation on this screen is accepted, the mobile terminal 2 does not send a request to the MFP 1. .

If a mobile input function is provided to multiple mobile terminals in parallel, operation data from operations by multiple users will be received, and there is a high possibility that the operation will be different from the operation desired by each user. If the MFP 1 is currently providing the mobile input function to another mobile terminal, it will not start providing the mobile input function to the mobile terminal 2, so confusion can be avoided.

Note that since the MFP 1 displays the standby screen 51 even after transmitting the start screen data, it may be possible to accept access from another terminal using the two-dimensional code image 511. For example, if the MFP 1 receives access from another mobile terminal before receiving the start information (A25), the MFP 1 may also transmit the start screen data to the other mobile terminal. In that case, when the MFP 1 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 the other terminal, it determines that the mobile input function is being provided and executes B21. do. Note that, upon receiving the start information from one terminal, the MFP 1 may transmit end screen data to the other terminal.

After displaying the screen on the touch panel 131 for a predetermined display time at B19, or after transmitting the currently provided screen data to the mobile terminal 2 at B21, the MFP 1 performs the start procedure and the access reception procedure of FIG. After finishing, the process returns to S102 in FIG.

Next, a description will be given of a procedure when an access using access information that is not the latest is accepted. As a result of the confirmation in A12, if it is determined that the key included in the access information used when accepting the access does not match the latest key 26 stored in the memory 12 (alt: [NG]) , the MFP 1 transmits re-reading screen data, which is web page data indicating a re-reading screen requesting re-reading, to the mobile terminal 2 (A31). Thereby, the browser 213 of the mobile terminal 2 displays a re-reading screen 64 on the touch panel 211, for example, as shown in FIG. 13 (A32). Rereading screen 64 includes a message requesting rereading of standby screen 51 displayed on touch panel 131 of MFP 1. After transmitting A31, the MFP 1 ends the access reception procedure in FIG. 5 and returns to S102 in FIG. 2.

MFP 1 does not provide mobile input functionality if the received access information key is not up to date. By allowing access only based on the access information displayed on the touch panel 131 of the MFP 1 at that time, it is possible to increase the possibility that the access is by a user who is near the MFP 1, and further ensure safety. Further, when access using access information that is not the latest is accepted, a notification to re-enter the access information is provided, thereby avoiding confusion on the part of the user. The notification may also be accompanied by audio guidance.

As will be described later, in the function providing process of FIG. 2, for example, a new key is generated every time a predetermined refresh time elapses, and a standby screen 51 containing the new key is displayed. For example, if a long time elapses after the user causes the mobile terminal 2 to read the two-dimensional code image 511 displayed on the touch panel 131 of the MFP 1 and then instructs the user to access the MFP 1, the key may be regenerated. there is a possibility. In this case, the MFP 1 determines that the key included in the access information used for the access is not the latest one, and executes A31 in FIG. When the MFP 1 receives an access using access information that does not include the latest key, it does not transmit start screen data or operation screen data, and notifies that the access information should be input again. Thereby, for example, it is highly possible to prevent a malicious user from reading the two-dimensional code image 511 and operating the MFP 1 from a remote location.

The user who viewed the re-reading screen 64 can access the MFP 1 by reading the two-dimensional code image 511 again using the camera 212, for example, using the access information to which the latest key has been added. If the MFP 1 receives the access using the access information to which the latest key has been added, the MFP 1 determines OK in A12 of FIG. 5 and enables the mobile terminal 2 to use the mobile input function.

Note that even if the MFP 1 does not receive start information within a predetermined waiting time after transmitting the start screen data in A21, the MFP 1 transmits screen data indicating the end of providing the mobile input function to the mobile terminal 2. You may decide not to start providing mobile input functionality.

Up to this point, the operation of the MFP 1 when the mobile input function is not provided has been described. Next, the operation of the MFP 1 when the standby screen 51 is displayed and access from the mobile terminal 2 or the like is not accepted (NO in S121) will be described. Note that the process when an operation on the "Exit" button 512 in the standby screen 51 is accepted after the start screen data is transmitted in A21 will be described later.

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

After displaying the home screen 53 in S129, the MFP 1 becomes able to accept operations on each object displayed on the screen. The CPU 11 determines whether an operation on the operation panel 13 has been accepted (S131). If it is determined that the operation has been accepted (S131: YES), the CPU 11 performs various operations based on the accepted operation. For example, if the received operation is an operation to change the display screen (S132: YES), the CPU 11 causes the touch panel 131 to display the changed screen (S133). For example, when the copy button is operated, the CPU 11 displays the copy screen described above.

The screen displayed in S133 may be a screen that can accept parameter setting instructions. If the operation received on the screen being displayed 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 FIG. The CPU 11, for example, sets parameters such as the number of copies to be made in accordance with the operation received on the copy screen displayed in S133, and displays a copy screen with the number of copies displayed changed to the set number of copies.

Further, if the received operation is an instruction to perform image formation (S137: YES), the CPU 11 causes the print engine 15 and scanner 16 to execute image formation (S138), and displays an execution screen on the touch panel 131 (S139). ). For example, when the copy execution instruction button is operated on the copy screen displayed in S133, the CPU 11 causes the touch panel 131 to display a screen including a message "Copy in progress". S138 is the same process as S228 in FIG. If the operation is other than that (S137: NO), the CPU 11 performs other operations and returns to S131.

When receiving an operation on the “Exit” button 512 included in the standby screen 51, the MFP 1 displays the home screen 53 on the touch panel 131. Then, the MFP 1 becomes able to accept input operations from the operation panel 13. As a result, even if the MFP 1 is capable of accepting input operations from the mobile terminal 2, it is possible to perform input operations to the MFP 1 from the operation panel 13 as necessary, so it is possible to suppress a decrease in operability. This is highly convenient for users who desire input operations from the operation panel 13.

If the CPU 11 determines that no operation has been accepted for each object being displayed (S131: NO), the CPU 11 determines whether or not a predetermined no-operation time has passed during which no operation has been accepted (S140). ). Note that while the running screen is displayed on the touch panel 131, the elapsed time of no operation is not determined, and the elapsed time of no operation is determined after displaying a screen different from the running screen, for example, the copy screen. to judge. The predetermined no-operation time is, for example, one minute. If the no-operation time has not elapsed (S140: NO), the CPU 11 waits until either the operation is accepted or the no-operation time has elapsed.

If it is determined that the no-operation time has passed without receiving any operation (S140: YES), the CPU 11 returns to S102 in the same way as after completing the access reception procedure of S122.

Note that if the screen to be displayed in S133 is the home screen 53, the CPU 11 proceeds to S102 instead of displaying the home screen 53, as shown by the broken line in FIG. Then, if the mobile input function is enabled, the CPU 11 executes S111 to S116 to display the standby screen 51, and if the mobile input function is disabled, the CPU 11 proceeds to S105 and displays 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 the operation. In this case, the CPU 11 will proceed to S102 if there is no user operation for a period of no operation.

Furthermore, when the mobile input function is enabled, the screen displayed on the touch panel 131 based on the operation on the "Exit" button 512 may include a button that accepts an instruction to end the operation on the touch panel 131. . In that case, if the CPU 11 receives an operation for that button, the CPU 11 proceeds to S102, and for other instructions, based on the user's operation, for example, if an instruction to display the home screen 53 is received, the CPU 11 displays the home screen 53. You can also display it.

Note that, as described above, even after the start screen data is transmitted in A21, the standby screen 51 is displayed on the touch panel 131. When it is determined that the operation to the "Exit" button 512 has been accepted on the standby screen 51 (FIG. 4) (alt: [Exit], A27), the MFP 1 sends an exit message to the mobile terminal 2, which is the destination of the start screen data. The screen data is transmitted (A28) and the process advances to S129 in FIG. A28 is the same process as B16 in FIG. 7, and as a result, the end screen as shown in FIG. 11 is displayed on the touch panel 211 of the mobile terminal 2 (A29).

By making it possible to accept an operation on the "Exit" button 512 even after transmitting the start screen data, the user can receive an instruction to start using the mobile input function from the mobile terminal 2, as well as an instruction to start using the mobile input function from the operation panel 13. Any instructions that do not use the function can also be given. By operating the "Exit" button 512, the operation can be easily switched, which is convenient for both users who want input operations from the mobile terminal 2 and users who want input operations from the operation panel 13.

Returning to S102 in FIG. 2, if the mobile input function is enabled, the MFP 1 executes S111 to S116 again. In other words, when the provision of the mobile input function is terminated, when re-reading screen data is sent, when no operation continues beyond the no-operation time after operating the "Exit" button 512, the CPU 11 A standby screen 51 including keys is generated and automatically displayed on the touch panel 131. Further, if the mobile input function is not valid, the CPU 11 proceeds to S105 and displays the home screen 53. Thereby, there is little disadvantage for both users who want to use the mobile input function and users who do not.

By generating a new standby screen 51, the MFP 1 can accept both input operations from the mobile terminal 2 and operations on the "Exit" button 512. Note that the MFP 1 does not need to immediately generate a new key after transmitting the re-read screen data at A31 in FIG. Further, the CPU 11 may not judge the validity information 25 except at the time of startup.

After the MFP 1 of this embodiment finishes providing the mobile input function, for example, if a long press of the back key 133 is received while providing the mobile input function, the MFP 1 automatically creates a new one without waiting for the non-operation time in S140. A standby screen 51 is displayed. This makes it easy for the next user who wants to use the mobile input function immediately to use the mobile input function.

Further, the MFP 1 generates access information including a new key every time the provision of the mobile input function ends, and does not start providing the mobile input function even if there is an access using the previous access information. In other words, a user who wants to restart the provision of the mobile input function will read the standby screen 51 again and input the access information again. This increases the possibility that the access is from the mobile terminal 2 of the user who is currently in front of the MFP 1, and can further ensure safety.

Note that, as described above, when the MFP 1 starts providing the mobile input function and then receives an instruction to end the provision and ends the mobile input providing process (B15 in FIG. 7), the stored screen ID A screen corresponding to is displayed on the touch panel 131 for a predetermined display time (B19). This predetermined display time is shorter than the no-operation time, which is the time for displaying a screen that accepts an operation after accepting an operation on the "Exit" button 512. It is highly likely that the operation on the "Exit" button 512 is the user's clear intention to stop displaying the standby screen 51 and operate the touch panel 131. When the MFP 1 receives an operation on the "Exit" button 512, it displays a screen that accepts the operation for a period longer than the display time after ending the mobile input function, so that the MFP 1 can easily accept the user's operation.

Furthermore, even when the access reception procedure is ended by accepting the operation of the "Exit" button 512 at A27 of the access reception procedure in FIG. A screen for accepting user operations is displayed on touch panel 131, and user operations can be accepted. Then, the MFP 1 makes the same determination as in S131 and S140. Note that the no-operation time in this case does not have to be the same time as S140. By making it possible to accept an operation on the "Exit" button 512 even after the start screen data has been transmitted (A21 in FIG. 5), it is possible to prevent the use of the MFP 1 by a user other than the user who accessed it from the mobile terminal 2. This makes it possible to increase the operating rate of the MFP 1.

On the other hand, after displaying the standby screen 51 in S116, if it is determined that neither an access nor an operation on the "Exit" button 512 has been received (S128: NO), the CPU 11 determines that the predetermined refresh time has elapsed. It is determined whether or not (S141). If it is determined that the refresh time has elapsed (S141: YES), the CPU 11 returns to S102 and displays a new standby screen 51.

The refresh time is the elapsed time until the key is regenerated in a state where no user access or operation is accepted, and is, for example, 5 minutes. By appropriately regenerating keys at a predetermined refresh time, the MFP 1 does not accept access using old access information for which the refresh time has elapsed.

If it is determined that the refresh time has not elapsed (S141: NO), the CPU 11 repeats the determinations in S121, S128, and S141 until the power is turned off (S142: NO). In the state where the standby screen 51 is displayed, the MFP 1 of this embodiment can only accept either an access from the mobile terminal 2 or an operation to the "Exit" button 512 as a user operation, and can only accept a return key. Other operations such as a long press on 133 (see FIG. 4) are not accepted. 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 MFP 1 is stabilized. Then, when the power is turned off (S142: YES), the CPU 11 ends the function providing process.

Note that when the MFP 1 does not receive user access or operation for a predetermined sleep time, the MFP 1 may put the operation panel 13 into a sleep state and stop displaying on the touch panel 131. In this case, upon receiving any operation on the operation panel 13 in the sleep state, the MFP 1 executes the function providing process from the determination in S102.

Next, the second start procedure, which is another procedure for determining whether or not the mobile input function is being provided, will be described with reference to the sequence diagram of FIG. 14. This second start procedure is executed in place of the start procedure shown in FIG.

The MFP 1 executing the second start procedure transmits data including a program to be executed by the browser 213 of the mobile terminal 2 as the start screen data to be transmitted to the mobile terminal 2 at A21 in FIG. This program is, for example, a program written in JavaScript (registered trademark). When receiving start screen data including this program, the mobile terminal 2 operates according to the received program.

Based on the received start screen data, the mobile terminal 2 displays the start screen 61 shown in FIG. 6, and upon accepting the operation of the start button 611, the mobile terminal 2 enters a state indicating the token issuance status as shown in FIG. Information is requested from MFP1 (C01). MFP 1 transmits status information in response to a request from mobile terminal 2 (C02). The status information is information indicating whether a token has been issued or not, and is information indicating either "issued" or "unissued." Note that when a token has never been issued, for example, at startup, the MFP 1 sets the state information to "not issued."

If the status information received from the MFP 1 indicates "not issued", the mobile terminal 2 transmits a token issuance request to the MFP 1 (C11). The MFP 1 issues a token in response to the request from C11 (C12), and stores the issued token in the memory 12 (C13). The MFP 1 may overwrite the token or may add and store information indicating the latest information. Furthermore, the MFP 1 may store the token with time information indicating the period during which the token can be used. Note that the MFP 1 may check the token issuance status again before C12. Furthermore, the MFP 1 changes the status information indicating the issued status of the token to information indicating "issued" (C14).

Then, the MFP 1 transmits the issued token to the mobile terminal 2 (C15). After receiving the token, the mobile terminal 2 transmits the received token and a start request, which is information requesting to start using the mobile input function, to the MFP 1 (C16). The MFP 1 determines whether the token received with the start request is a correct token that matches the latest token stored at C13 (C17).

If it is determined that the token is correct (alt: [correct]), the MFP 1 executes steps B10, B12 to B17, and B19, similar to the start procedure shown in FIG. As a result, a mobile input function is provided, and the user can operate the MFP 1 using the mobile terminal 2. However, in the second start procedure, when the mobile terminal 2 transmits operation data based on the user's operation in the mobile input providing process, it adds a token and transmits it each time. The MFP 1 confirms the token received with the request by comparing it with the token stored in the memory 12, and if determined to be correct, performs processing based on the operation data and transmits new screen data. On the other hand, if the MFP 1 determines that the received token is incorrect, the MFP 1 may immediately end the mobile input providing process.

If it is determined that the token received with the start request is incorrect (alt: [incorrect]), the MFP 1 transmits rejection screen data indicating that the provision of the mobile input function will not be started to the mobile terminal 2 (C21). The mobile terminal 2 displays a rejection screen on the touch panel 131 based on the received rejection screen data (C22). After the provision of the mobile input function is completed or after C21, the MFP 1 deletes the token stored in C13 (C31) and changes the status information to information indicating "not issued" (C32).

On the other hand, when receiving status information indicating "issued" at C02, the mobile terminal 2 displays an error screen on the touch panel 211 (C41). The mobile terminal 2 also displays an error screen when a token is not issued within a predetermined time in response to the token issuance request at C11, or when information regarding an issuance error is received.

Even in this case, the MFP 1 can determine whether the mobile input function is being provided to another terminal based on the token issuance state. Note that the mobile terminal 2 may transmit the token issuance request of C11 without acquiring the status information of C01. In that case, the MFP 1 may receive the token issuance request, determine whether or not the token has been issued, and if it determines that the token has been issued, may transmit rejection screen data similar to C21. .

As described above in detail, the MFP 1 of the first form is equipped with a mobile input function, and therefore can accept input operations from the mobile terminal 2. Then, before starting to provide the mobile input function, the MFP 1 displays a two-dimensional code image 511 including access information necessary for starting the function on the touch panel 131 of the operation panel 13. As a result, even if the user does not remember the access information, the user can easily input the access information into the mobile terminal 2 by reading the two-dimensional code image 511 in front of the MFP 1, and easily use the mobile input function. Available.

Next, an MFP according to a second embodiment will be described in detail with reference to the accompanying drawings. As shown in FIG. 15, the MFP 101 of this embodiment has a remote input function program (hereinafter referred to as "remote input P") 23 and a Wi-Fi direct ( (hereinafter referred to as "WFD") 24. The remote input function provided by the remote input P23 is a function that accepts remote operation using the embedded web server function of the MFP 101, and is a different function from the mobile input function. Note that the configuration other than these is the same as that of the MFP 1 of the first form, so the same reference numerals are given and the explanation is omitted.

Since the MFP 101 of this embodiment includes the WFD 24, it is possible to provide a network using the WFD 24. The WFD 24 is a function in which the MFP 101 becomes a group owner, establishes communication with client devices using the same communication standard as Wi-Fi, and performs one-to-one wireless communication. A predetermined SSID and password are assigned to the WFD 24 of the MFP 101, and by specifying the SSID and password, the client device can communicate with the MFP 101 via the network provided by the WFD 24. . The SSID and password are examples of information that is authenticated by the group owner. Note that there are multiple types of means for establishing communication with the WFD 24, and the client device may be selectable depending on its functions.

Furthermore, it is assumed that the MFP 101 of this embodiment is not limited to a device including a camera 212 such as a mobile terminal 2, but also accepts requests from a remote location via the Internet from a personal computer (hereinafter referred to as "PC") 3, etc. are doing. PC3 is an example of an operation terminal. The MFP 101 can accept requests through any communication path, such as a direct connection using the WFD 24 or a network connection via a wired or wireless connection to an access point.

Furthermore, since the MFP 101 of this embodiment includes both a mobile input P22 and a remote input P23, it has access information for the mobile input P22 and access information for the remote input P23, respectively, and the access information of the received access is Depending on the situation, mobile or remote input functionality can be provided. The access information of the mobile input P22 is an example of first access information, and the access using the access information of the mobile input P22 is an example of the first access. The access information of the remote input P23 is an example of second access information, and the access using the access information of the remote input P23 is an example of the second access. Note that the mobile input P22 and the remote input P23 may be provided by sharing the same embedded web server function, or may be provided with separate embedded web server functions.

Further, the MFP 101 can accept an instruction to set the validity information 27 indicating that the remote input function is valid, similar to the validity information 25 indicating that the mobile input function is valid. The MFP 101 receives the setting of the validity information 27 via the USB-IF 142, for example. Upon receiving input of valid information 27, MFP 101 stores valid information 27 in a nonvolatile storage area of memory 12, as shown in FIG. The USB-IF 142 in this case is an example of an external interface. The valid information 25 is an example of first setting information, and the valid information 27 is an example of second setting information. Note that the MFP 101 may be able to accept an instruction to set the valid information 27 via the network IF 141, for example, if the instruction is from a user with administrator authority. The network IF 141 in this case is an example of an external interface.

Since the information on whether to enable the mobile input function and the information on whether to enable the remote input function can be respectively set, usability for the user is improved. Further, similarly to the valid information 25, by limiting input of the valid information 27 to a USB memory or the like, unauthorized changes can be restricted.

However, in the MFP 101, if the enablement information 25 is stored in the memory 12 and the mobile input function is enabled, the remote input function is not enabled. The MFP 101 may be configured such that it cannot accept an instruction to set the valid information 27 when the mobile input function is enabled. Furthermore, even if the MFP 101 receives an instruction to set the valid information 27, it may not be stored in the memory 12 and the remote input function may not be enabled. Furthermore, when the MFP 101 receives an instruction to set the valid information 25, if the valid information 27 is stored in the memory 12 and the remote input function is enabled, the MFP 101 deletes the valid information 27 and performs the remote input function. You can also disable it.

Since the MFP 101 includes the mobile input P22, upon startup, it executes the same process as the function providing process (see FIG. 2) described above for the MFP 1 of the first form. Specifically, if the mobile input function is enabled (YES in S102 of FIG. 2), the MFP 101 displays a standby screen including access information on the touch panel 131 (S111 to S116 of FIG. 2), and displays an external device. It becomes possible to accept access from. Note that hereinafter, the external device that has accessed the MFP 101 and sent the request will be referred to as a "request device."

However, as will be described later, the MFP 101 of this embodiment can provide the mobile input function only when access via the WFD 24 is accepted. Therefore, as shown in FIG. 16, the MFP 101 displays a standby screen 55 including connection information 551, which is information for establishing communication with the WFD 24, on the touch panel 131. The standby screen 55 displays a two-dimensional code image 511 that is access information for requesting the start of providing the mobile input function, an "Exit" button 512, and information on a predetermined SSID and password assigned to the WFD 24. The connection information 551 is included. By displaying the standby screen 55 that includes the two-dimensional code image 511 and connection information 551, even users who do not remember these information can easily use the mobile input function.

When the MFP 101 receives an access from the mobile terminal 2 or the like using the access information of the mobile input P22 while displaying the standby screen 55 (YES in S121 of FIG. 2), the MFP 101 performs the process shown in FIG. Before executing the access reception procedure of the first form, an access permission determination process is executed. The procedure of the access permission determination process will be explained with reference to the flowchart of FIG. 17.

In the access permission determination process, the CPU 11 determines whether the communication path through which the request was received is communication via the WFD 24 (S301). Note that the MFP 101 can accept an instruction to establish communication with the WFD 24 regardless of the mobile input function or remote input function.

If it is determined that access to the mobile input function has been received via the WFD 24 (S301: YES), the CPU 11 executes the access reception procedure (see FIG. 5) similarly to the first embodiment (S122). Specifically, the MFP 101 checks the key added to the access information used for access (A12 in FIG. 5), and if the key is the latest one, sends the start screen data (A12 in FIG. 5). A21), it becomes possible to provide mobile input functions.

On the other hand, if it is determined that access to the mobile input function has been received through a communication path other than the WFD 24 (S301: NO), the CPU 11 transmits information indicating "404 page not found" to the requesting device (S302), The access permission determination process ends. “404 page not found” is information that the web server passes to the browser when there is no web page that corresponds to the received request. By receiving the information transmitted in S302, the browser of the requesting device displays a screen corresponding to the information indicating "404 page not found." Note that the information transmitted in S302 may be, for example, screen data showing a screen for rejecting the request.

Then, after S302 or after the access reception procedure ends, the CPU 11 returns to S102 (FIG. 2) of the function providing process and displays the standby screen 55 again.

On the other hand, if the mobile input function is not enabled, the MFP 101 performs a process similar to the function providing process of the first form (NO in S102 in FIG. 2), and operates the home screen 53 etc. instead of the standby screen 55. A main body operation screen to be accepted is displayed on the touch panel 131 (S105 in FIG. 2), and operations on the touch panel 131 can be accepted.

If the mobile input function is not valid, the MFP 101 accepts switching between valid and invalid remote input functions. If the MFP 101 receives an access using the access information of the remote input P23 while the remote input function is disabled, the MFP 101 transmits web page data showing a screen notifying that the remote input function is disabled to the requesting device. . On the other hand, if the MFP 101 receives access using the access information of the remote input P23 while the remote input function is enabled, the MFP 101 can provide the remote input function even if it is accepting operations on the touch panel 131. Become.

Note that unlike the mobile input function, the MFP 101 does not display access information requesting the start of providing the remote input function on the touch panel 131. Therefore, an access requesting the provision of a remote input function is limited to one from a user who knows how to access the MFP 101 without depending on the access information, and unnecessary remote operations can be avoided.

If the MFP 101 receives an access using the access information of the remote input P23 while the valid information 27 is stored, the MFP 101 executes remote input providing processing based on the remote input P23. The procedure of the remote input providing process will be explained with reference to the flowchart of FIG. 18. Note that if the received access is a request for a web page with a remote input function, the MFP 101 does not make the determination in S301. That is, the MFP 101 can accept access to the remote input function if the request is from a device connected to the network to which the MFP 101 is connected.

In the remote input providing process, the CPU 11 first determines whether a remote input function is being provided (S400). As will be described later, when starting to provide the remote input function, the CPU 11 stores information indicating that the remote input function is being provided in the memory 12. In S400, the CPU 11 determines whether the memory 12 stores information indicating that the remote input function is being provided. The MFP 101 may determine whether or not the remote input function is being provided using a procedure using a token as shown in FIG. 14.

If it is determined that the remote input function is not being provided (S400: NO), the CPU 11 stores information indicating that the remote input function is being provided in the memory 12 (S401). Then, the CPU 11 transmits login screen data, which is a screen for accepting authentication information for login (S402), and accepts a request including authentication information from the requesting device. Upon receiving the authentication information, the CPU 11 performs user authentication and determines whether the user is permitted to use the remote input function (S403). Since the remote input function is likely to be operated by a user who is not near the MFP 101, the security of the MFP 101 is increased by starting it on the condition that authentication is successful. Note that the user authentication may be executed by the MFP 101 or may be executed by an authentication server or the like.

If the CPU 11 determines that the user is permitted to use the remote input function (S403: YES), the CPU 11 displays, for example, a panel usage permission screen 56 as shown in FIG. 19 on the touch panel 131 (S404). A user's input is accepted (S405). The panel usage permission screen 56 is a screen that notifies that remote operation of the MFP 101 using the remote input function is requested and accepts the user's selection as to whether or not to start the remote operation. and a “No” button 562. The panel usage permission screen 56 further includes a message informing that, for example, once remote operation using the remote input function is started, operations on the touch panel 131 will not be accepted, and that the results of the remote operation will be reflected on the touch panel 131. may also be included. Note that the CPU 11 does not display the panel usage permission screen 56 when providing the mobile input function at B10 to B15 in FIG.

If it is determined that the start of the remote input function has been selected by operating the "Yes" button 561 on the panel usage consent screen 56 (S405: Yes), the CPU 11 selects the information stored in the memory 12 at that time. A screen ID is acquired (S411), and screen data based on the acquired screen ID is generated (S412). Note that the MFP 101 stores in the memory 12 a screen ID that identifies the screen being displayed on the touch panel 131. Here, the CPU 11 obtains a screen ID indicating the screen immediately before displaying the panel usage permission screen 56. Further, the CPU 11 closes the panel usage permission screen 56.

The CPU 11 transmits the generated screen data to the requesting device (S413). Thereby, the browser of the requesting device displays on the display of the requesting device a screen similar to the screen displayed on the touch panel 131 of the MFP 101 immediately before displaying the panel usage permission screen 56. For example, if the home screen 53 (see FIG. 3) is displayed on the touch panel 131, a screen similar to the home screen 62 shown in FIG. 9 is displayed on the display of the requesting device. Further, upon receiving an operation on the currently displayed screen, the browser of the requesting device transmits a request including operation data indicating the accepted operation to the MFP 101. Via the web page of the remote input function, the MFP 101 can receive operation data indicating, for example, instructions to change various settings, instructions to execute an image forming operation, and instructions to terminate use of the remote input function.

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

The procedure of the operation response process will be explained with reference to the flowchart of FIG. 20. In FIG. 20, processes similar to those in FIGS. 2 and 10 are denoted by the same reference numerals. In the operation response process, the CPU 11 determines whether the operation data included in the received request is an operation for changing the display screen (S221). If it is determined that the operation is to change the display screen (S221: YES), the CPU 11 displays the changed screen on the touch panel 131 (S133), unlike in the case of the mobile input function. Further, as in the case of the mobile input function, the CPU 11 transmits screen data indicating the changed screen to the requesting device (S222).

If it is determined that the operation data included in the received request is not an operation to change the display screen (S221: NO), the CPU 11 determines whether it is an instruction to set parameters or the like (S224). If it is determined that the command is a parameter setting instruction (S224: YES), the CPU 11 sets parameters and the like based on the operation data, as in the case of the mobile input function (S225).

Furthermore, unlike the case of the mobile input function, the CPU 11 causes the touch panel 131 to display a screen after setting the parameters (S136). Then, as in the case of the mobile input function, the CPU 11 transmits screen data indicating the screen after setting to the requesting device (S226).

If it is determined that the instruction is not a parameter setting instruction (S224: NO), the CPU 11 determines whether the instruction is an instruction to execute image formation (S227). If it is determined that it is an execution instruction (S227: YES), the CPU 11 starts executing image formation based on the operation data, as in the case of the mobile input function (S228). By using the remote input function, the user can send setting instructions and execution instructions to the MFP 101 by remote control from the requesting device.

Furthermore, unlike the case of the mobile input function, the CPU 11 causes the touch panel 131 to display a screen indicating that the function is being executed (S139). Then, as in the case of the mobile input function, the CPU 11 transmits screen data indicating that the function is being executed to the requesting device (S229).

After any one of S222, S226, and S229, the CPU 11 stores the screen ID that identifies the transmitted screen data in the memory 12, as in the case of the mobile input function (S231). After S231, or if it is determined that it is not an execution instruction (S227: NO), the CPU 11 ends the operation response process and returns to the remote input providing process in FIG.

Returning to the description of the remote input providing process in FIG. 18. After completing the operation response process in S421, the CPU 11 can receive the next operation data from the requesting device. Then, the CPU 11 returns to S415 and again determines whether the operation data included in the request from the requesting device is operation data indicating an instruction to end the use of the remote input function.

If the CPU 11 determines that the operation data included in the received request is operation data that indicates an instruction to end the use of the remote input function (S415: YES), the CPU 11 determines that the remote input function stored in S401 is currently being provided. Information indicating that there is is deleted (S433). Then, the CPU 11 ends the remote input providing process and returns to the access permission determination process of FIG. 17.

In addition, if it is determined that the user is not permitted to use the remote input function based on the received authentication information (S403: NO), or if the "No" button 562 is operated on the panel usage permission screen 56. If it is determined that the remote control is not possible (S405: No), the CPU 11 transmits web page data showing a screen notifying that remote control is not possible to the requesting device (S431). As a result, a screen notifying that remote control is not possible is displayed on the requesting device, and provision of the remote input function is not started. After S431, the CPU 11 deletes the information indicating that the remote input function is being provided (S433), ends the remote input providing process, and returns to the access permission determination process in FIG. 17.

Note that if it is determined in S405 that the "No" button 562 has been operated, the MFP 101 does not display the panel use permission screen 56 for a certain period of time, such as one minute, for example. If the MFP 101 receives a request for the remote input function again during this period, the MFP 101 requests web page data showing a screen notifying that remote control is not possible, in the same way as when the "No" button 562 is operated in S405. Send to device.

The remote input function is a function that assumes a case where the user and the remote location cooperate, such as when an administrator at a remote location teaches the user in front of the MFP 101 how to operate the MFP 101 . By waiting for an input operation on the panel use permission screen 56, it is possible to prevent remote control from being performed without a user to cooperate with. On the other hand, when remote operation using the remote input function is started, the display on the touch panel 131 is automatically changed by the remote operation, so for example, if a user is about to use the MFP 101 regardless of the remote input function , the MFP 101 cannot be used until the remote input function is terminated. A user who is attempting to use the MFP 101 can postpone the start of remote control by operating the "No" button 562 on the displayed panel usage permission screen 56.

On the other hand, if it is determined that the remote input function is being provided at the start of the remote input providing process (S400: YES), the CPU 11 transmits the currently providing screen data (S441), and ends the remote input providing process. S441 is the same process as B21 in FIG. The currently provided screen data is, for example, screen data for displaying a screen such as the currently provided screen 52 shown in FIG. 8 on the requesting device.

The MFP 101 of this embodiment can provide both a mobile input function and a remote input function, and regardless of which one is used, it accepts instructions to set parameters and perform image formation on the MFP 101. However, since the mobile input function and the remote input function are intended for different users, the conditions for providing each function are different.

The mobile input function is a function that is assumed to be used by a user in front of the MFP 101, and while it facilitates access by displaying access information on the operation panel 13, it also allows you to dynamically change access information using keys and change the WFD 24. By restricting access via the Internet, anonymous access and remote operation are restricted. The remote input function is intended to be used by an administrator in a remote location, and although the communication route is not limited, the access information is not displayed on the touch panel 131 and successful authentication is included as a condition for starting. Usage by users other than administrators is restricted. Thereby, the MFP 101 can provide various functions depending on the purpose.

As described above in detail, the second form of the MFP 101 has two input functions that allow input operations without touching the operation panel 13: a mobile input function and a remote input function, which have different operations. Supports input function. Thereby, suitable input functions can be provided depending on the application.

Note that the first form and the second form are merely examples, and do not limit the present invention in any way. Therefore, the technology disclosed in this specification is naturally capable of various improvements and modifications without departing from the gist thereof. For example, the present invention can be applied to printers, scanners, copiers, and fax machines instead of MFP 1 and MFP 101.

Further, the screens illustrated in each figure are merely examples, and the display format is not limited to the illustrated example. For example, the wording of messages displayed on each screen, the shape and arrangement of buttons, etc. are not limited to the illustrated examples. For example, the two-dimensional code image 511 may be displayed on a part of the home screen instead of being displayed on the entire surface of the touch panel 131 like the standby screen 51 shown in FIG. 4 or the standby screen 55 shown in FIG. . Furthermore, the display form of the access information included in the standby screens 51 and 55 is not limited to the two-dimensional code image 511, but may be text information or a barcode image.

Furthermore, the screen displayed on the mobile terminal 2 etc. when the mobile input function is started is not limited to the home screen 62 shown in FIG. Alternatively, buttons other than the close button 623 that are not included in the operation panel 13 may be included. Further, the arrangement and size of the panel screen 621 and the key screen 622 do not have to be a perfect reproduction of the operation panel 13. Furthermore, the screen displayed on the mobile terminal 2 etc. using the mobile input function may be any screen that accepts user operations, and is not limited to a screen imitating the operation screen displayed on the touch panel 131 of the MFP 1, and may be an original screen. It's okay.

Furthermore, although the mobile terminal 2 and the like have been described as having the browser display a screen based on the received screen data, the program to be displayed is not limited to the browser, and may be a dedicated application program. However, by displaying it on a browser, there is no need to install a dedicated application program, and the mobile input P22 and remote input function can be used more easily.

Further, in the first embodiment, the mobile terminal 2 is a smartphone or a tablet computer equipped with a camera, but the mobile terminal 2 is not limited to this. For example, it may be a laptop computer or a terminal without a camera. When using a terminal without a camera, the user can, for example, capture the two-dimensional code image 511 with a camera of another device and send the captured data to the terminal, thereby transferring the data from the terminal without a camera to the MFP 1. can be accessed.

Further, the first form of MFP 1 may further include a remote input function similar to that of the second form of MFP 101. In other words, the MFP 1 may be able to execute the process shown in FIG. Furthermore, the first form of MFP 1 may further include a WFD similar to the second form of MFP 101, and may provide the mobile input function only when access via the WFD is accepted. In other words, the MFP 1 may be able to execute the process shown in FIG. 17.

Furthermore, in the first and second embodiments, the MFP 1 or MFP 101 dynamically generates a key and displays access information that includes a URL and a key, but the key may not be included. However, by including a dynamic key, it is possible to create a configuration that does not accept access using old access information, thereby increasing the security of the mobile input function.

Furthermore, in the first and second embodiments, the MFP 1 or the MFP 101 displays the standby screen 51 (FIG. 4) or the standby screen 55 (FIG. 16) that includes the "Exit" button 512. A standby screen that does not include this may be displayed. In that case, for example, an operation on any of the hardware keys 132 may be accepted instead of an operation on the "Exit" button 512.

Furthermore, in the first and second embodiments, when an operation to the "Exit" button 512 is received, the standby screen 51 (FIG. 4) or the standby screen 55 (FIG. 16) is automatically displayed without any operation for one minute or the like. Although it is assumed that it will be displayed again, it is not limited to this. For example, the standby screens 51 and 55 may not be displayed until a new operation such as an operation on the return key 133 is received.

Further, in the first and second embodiments, while the standby screen 51 (FIG. 4) or the standby screen 55 (FIG. 16) is displayed, it is difficult to access from the mobile terminal 2 or the like and operate the "Exit" button 512. However, other operations, such as a long press of the return key 133, may be accepted. In that case, when the MFP 1 or MFP 101 receives a long press on the back key 133, unlike the operation on the "Exit" button 512, the MFP 1 or MFP 101 immediately presses a new key instead of displaying the operation screen and waiting for 1 minute. It is also possible to generate the standby screens 51 and 55 and display the standby screens 51 and 55. That is, when the MFP 1 or the MFP 101 receives a long press on the return key 133 while displaying the standby screens 51 and 55, it is not necessary to display the operation screen. Alternatively, when the MFP 1 or MFP 101 receives a long press on the return key 133 while displaying the standby screens 51 and 55, the operation screen is displayed for a shorter time than when the "Exit" button 512 is pressed. Also good.

Further, in the start procedure of the first and second forms (FIG. 7), when the MFP 1 or MFP 101 receives start information from the mobile terminal 2, it stores information indicating that the mobile input function is being provided (B11), Based on the information, it is determined whether or not the mobile input function is being provided (B01), but the timing for determining whether or not the mobile input function is being provided is not limited to this. For example, when start screen data is sent in A21 of FIG. 5, information indicating that the start screen data was sent is stored, and if the information is stored, even if the mobile input function is accessed. It is also possible to not send start screen data.

Further, in the first and second embodiments, the MFP 1 or the MFP 101 measures the elapsed time during which no operation data is received while providing the mobile input function, and determines whether it has timed out (S203 in FIG. 10). However, the mobile terminal 2 may make the determination of timeout. For example, after receiving the screen data, the mobile terminal 2 may transmit operation data indicating termination of the mobile input function if the time during which no operation is accepted exceeds a timeout period.

Furthermore, in the first and second embodiments, if a long press of the return key 133 is received while the mobile input function is being provided (YES in S204 in FIG. 10), the provision of the mobile input function is forcibly terminated. However, the operation for ending the provision of the mobile input function is not limited to the long press of the return key 133, but may be a long press of another hardware key. Furthermore, the modes of input operations to the hardware keys may be differentiated when the mobile input function is provided. For example, as input operation modes, in addition to long presses, normal input operations, multiple consecutive operations, and simultaneous presses of multiple hardware keys may be accepted. Different processing may be performed.

Furthermore, in the first and second embodiments, after the provision of the mobile input function is finished, a screen based on the stored screen ID is displayed on the touch panel 131 of the operation panel 13 (B19 in FIG. 7). , does not need to be displayed. In other words, the MFP 1 or the MFP 101 may display new standby screens 51 and 55 immediately after the mobile input providing process (FIG. 10) is completed. Furthermore, even if image formation is in progress at the end of the mobile input providing process, the MFP 1 or MFP 101 displays, for example, the home screen 53 (FIG. 3) instead of displaying the in-progress screen 54 (FIG. 12). It's okay.

Further, in the second embodiment, the MFP 101 performs user authentication only when there is a request to provide a remote input function, but the MFP 101 does not need to perform user authentication. Further, for example, it may also be possible to accept user login when using the mobile input function. For example, there may be a button on the home screen 62 that accepts login, and when MFP 1 or MFP 101 receives operation data indicating an operation on that button, it may transmit login screen data. User authentication while providing the mobile input function can be used, for example, to select a file to be printed in store printing.

Further, the remote input function is, for example, a function that is assumed to be used by an administrator of the MFP 101, and may be a function that can accept not only remote control of the MFP 101 but also various operations related to the MFP 101. Further, in the second embodiment, the instruction to start providing the remote input function is accepted regardless of the communication path, but it may not be accepted through the communication path via the WFD 24. Further, the WFD 24 may be capable of one-to-many communication.

Furthermore, in the second form, after displaying the panel usage consent screen 56 in S404 of the remote input providing process (FIG. 18), the MFP 101 does not allow the "Yes" button 561 to be operated even after a predetermined period of time has elapsed. If the operation on the "No" button 562 is not accepted, it may be assumed that the operation on the "Yes" button 561 has been accepted and the process may proceed to S411. Furthermore, although the MFP 101 is described as changing the display on the touch panel 131 according to the received operation data when starting to provide the remote input function, the MFP 101 does not need to change the display. For example, the MFP 101 may display a screen on the touch panel 131 indicating that a remote input function is being executed.

Further, in the second embodiment, the MFP 101 does not accept operations on the touch panel 131 while providing the remote input function, but the MFP 101 may be able to accept operations. Alternatively, it may be possible to select whether or not to accept the remote input function when starting to provide the remote input function. If acceptance is enabled, the MFP 101 can transmit screen data of a screen changed based on user operation to the requesting device, for example, by causing the requesting device to perform polling. In that case, the MFP 101 performs various operations corresponding to S106 in FIG. 2 based on the received operation. Further, if the remote input function is enabled, the mobile input function is disabled, so when a user operation to display the home screen 53 is accepted, the MFP 101 displays the home screen 53 instead of the standby screen.

Furthermore, in any of the flowcharts disclosed in the embodiments, the execution order of a plurality of processes in any plurality of steps can be arbitrarily changed or executed in parallel as long as there is no inconsistency in the processing contents.

Furthermore, the processing disclosed in the embodiments may be executed by a single CPU, multiple CPUs, hardware such as an ASIC, or a combination thereof. Further, the processes disclosed in the embodiments can be realized in various aspects such as a storage medium storing a program for executing the processes, or a method.

1,101 MFP
2 Mobile terminal 3 PC
10 Controller 11 CPU
12 Memory 13 Operation panel 131 Touch panel 141 Network IF
142 USB-IF

JP 2021-73543 Publication

Claims (11)

network interface;
An operation panel including a touch panel,
controller and
An image forming apparatus comprising:
The image forming apparatus includes:
has a mobile input function that accepts input operations from a mobile terminal via the network interface,
The controller includes:
In a state where the provision of the mobile input function has not started,
Start providing the mobile input function when an access necessary to start providing the mobile input function is received from the mobile terminal via a network provided by the image forming apparatus;
not starting to provide the mobile input function when the access necessary to start providing the mobile input function is received from the mobile terminal without going through the network provided by the image forming apparatus;
Furthermore, the controller
When we start providing the mobile input function,
executing a transmission process of transmitting display data for displaying an operation screen for the image forming apparatus on the mobile terminal to the mobile terminal via a network provided by the image forming apparatus;
Furthermore, the controller
While the mobile input function is provided, when operation data indicating operation details on the operation screen is received from the mobile terminal via the network provided by the image forming apparatus,
If the received operation data is an operation related to setting parameters used for image formation, executing a setting process for setting the parameters indicated in the received operation data;
If the received operation data is an operation related to execution of image formation, performing image formation processing to form the image indicated by the received operation data;
An image forming apparatus configured as follows. The image forming apparatus according to claim 1,
The controller includes:
In a state where the provision of the mobile input function has not started,
As the network provided by the image forming apparatus, the image forming apparatus serves as a group owner, and the mobile terminal serves as a client device connected to the group owner using information authenticated by the group owner. If the access necessary to start providing the mobile input function is received from the mobile terminal via the network, start providing the mobile input function,
not starting to provide the mobile input function when the access necessary to start providing the mobile input function is received from the mobile terminal without going through the network provided by the image forming apparatus;
An image forming apparatus configured as follows. The image forming apparatus according to claim 1,
The controller includes:
In a state where the provision of the mobile input function has not started,
As the network provided by the image forming apparatus, the image forming apparatus becomes a group owner of Wi-Fi Direct, and the mobile terminal becomes a client device of Wi-Fi Direct and connects the network to the image forming apparatus. start providing the mobile input function when the access necessary to start providing the mobile input function is received from the mobile terminal via the mobile terminal;
not starting to provide the mobile input function when the access necessary to start providing the mobile input function is received from the mobile terminal without going through the network provided by the image forming apparatus;
An image forming apparatus configured as follows. The image forming apparatus according to any one of claims 1 to 3,
In the transmission process,
The display data for causing the mobile terminal to display the operation screen, which is the operation screen for the image forming apparatus and virtually shows the operation panel, is transmitted to the image forming apparatus via a network provided by the image forming apparatus. Send to mobile device,
Furthermore, the controller
When the operation data is received from the mobile terminal that has received the display data via the network provided by the image forming apparatus while the mobile input function is provided,
The image forming apparatus provides the new display data for causing the mobile terminal to display the operation screen that virtually shows the operation panel that is updated based on the operation indicated in the received operation data. transmitting to the mobile terminal via the network;
An image forming apparatus configured as follows. In the image forming apparatus according to any one of claims 1 to 4,
There are cases in which setting information indicating validity of the mobile input function is stored in the memory, and cases in which the setting information is not stored in the memory,
The controller includes:
In a state where the provision of the mobile input function has not started,
If the setting information is stored in the memory when the access necessary to start providing the mobile input function is made from the mobile terminal via the network provided by the image forming apparatus, starting to provide the mobile input function, and not starting to provide the mobile input function unless the configuration information is stored in the memory;
An image forming apparatus configured as follows. In the image forming apparatus according to claim 5,
The controller includes:
If the configuration information is not stored in the memory,
displaying a main unit operation screen on the touch panel;
If there is an operation related to setting the parameters used for image formation on the main body operation screen, set the parameters according to the operation,
If there is an operation related to image formation on the main body operation screen, perform image formation according to the operation,
If the setting information is stored in the memory,
In the transmission process,
transmitting the display data for causing the mobile terminal to display the operation screen that is the operation screen for the image forming apparatus and that virtually represents the main body operation screen, via a network provided by the image forming apparatus; transmitting to the mobile terminal;
An image forming apparatus configured as follows. In the image forming apparatus according to claim 5 or 6,
The controller includes:
storing the setting information in the memory when the setting information is acquired via an external interface included in the image forming apparatus;
An image forming apparatus configured as follows. The image forming apparatus according to any one of claims 1 to 7,
The controller includes:
In a state where the provision of the mobile input function has not started,
The image forming apparatus is configured to execute a display process of displaying a standby screen on the touch panel, and the standby screen includes first access information necessary to start providing the mobile input function, and the image forming apparatus provides the first access information. connection information necessary for connection to the network provided by the image forming apparatus, and the mobile terminal is able to use the connection information to establish a connection to the network provided by the image forming apparatus;
Furthermore, the controller
In a state where the provision of the mobile input function has not started,
The provision of the mobile input function is started when the first access, which is the access using the first access information, is received from the mobile terminal via the network provided by the image forming apparatus. ,
not starting to provide the mobile input function when the first access is received from the mobile terminal without going through the network provided by the image forming apparatus;
An image forming apparatus configured as follows. In the image forming apparatus according to claim 8,
The controller includes:
In a state where provision of the mobile input function has started, executing a provision display process of displaying a provision screen on the touch panel indicating that the mobile input function is being provided;
After the provision of the mobile input function is finished, executing the display process of displaying the standby screen on the touch panel without requiring an input operation on the operation panel;
An image forming apparatus configured as follows. The image forming apparatus according to claim 9,
The image forming apparatus includes:
The input function includes the mobile input function and the remote input function as input functions that accept input operations from the operation terminal via the network interface,
The controller includes:
In a state where the provision of the remote input function has not started,
The second access information necessary to start providing the remote input function is configured not to be displayed on the touch panel,
The controller includes:
In a state where neither the mobile input function nor the remote input function has been started,
starting to provide the mobile input function when the first access is received from the operating terminal via the network provided by the image forming apparatus;
not starting to provide the mobile input function when the first access is received from the operating terminal without going through the network provided by the image forming apparatus;
If a second access using the second access information is received from the operating terminal via the network interface, regardless of whether it is via the network provided by the image forming apparatus. started providing the remote input function,
Furthermore, the controller
When we start providing the remote input function,
transmitting the display data for causing the operation terminal to display an operation screen for the image forming apparatus to the operation terminal via the network interface;
Furthermore, the controller
While providing the remote input function, if the operation data indicating the operation content of the operation screen is received from the operation terminal via the network interface,
If the received operation data is an operation related to setting parameters used for image formation, setting the parameters indicated in the received operation data,
If the received operation data is an operation related to execution of image formation, performing image formation indicated by the received operation data;
An image forming apparatus configured as follows. The image forming apparatus according to any one of claims 1 to 9,
The image forming apparatus includes:
The input function includes the mobile input function and the remote input function as input functions that accept input operations from the operation terminal via the network interface,
The controller includes:
In a state where neither the mobile input function nor the remote input function has been started,
starting to provide the mobile input function when the access necessary to start providing the mobile input function is received from the operation terminal via the network provided by the image forming apparatus;
If the access necessary to start providing the mobile input function is received from the operation terminal without going through the network provided by the image forming apparatus, the provision of the mobile input function is not started;
Regardless of whether access is via the network provided by the image forming apparatus, if access necessary for starting provision of the remote input function is received from the operation terminal via the network interface, the Started providing remote input function,
Furthermore, the controller
When we start providing the remote input function,
transmitting the display data for causing the operation terminal to display an operation screen for the image forming apparatus to the operation terminal via the network interface;
Furthermore, the controller
While the remote input function is being provided, if the operation data indicating the operation content of the operation screen is received from the operation terminal via the network interface,
If the received operation data is an operation related to setting parameters used for image formation, setting the parameters indicated in the received operation data,
If the received operation data is an operation related to execution of image formation, perform image formation indicated by the received operation data;
Furthermore, the controller
It is configured to accept input of authentication information via the network interface and perform authentication based on the accepted authentication information,
Start providing the remote input function on the condition that the authentication information is input and the authentication is successful,
starting to provide the mobile input function without requiring input of the authentication information;
An image forming apparatus configured as follows.

Images