Scanner, control program

Abstract

To suppress reduction in usability of a user interface in a case of executing a scanning process.SOLUTION: A controller 56 determines whether a user ID associated to a destination is stored in a memory. When it is determined that the user ID is not stored, an operation key is invalidated. When it is determined that the user ID is stored, the operation key is validated. When the validated operation key is operated, a push scanning process for transmitting created scan data to the destination is executed.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a technique for transmitting scan data to a predetermined destination. [Background technology]

[0002] Patent Document 1 describes a scanner capable of executing a scan process. In the scan process, the scanner creates scan data and transmits the created scan data to a preregistered destination. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-195100 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the scanner having the above configuration, since it is possible to register or delete a destination, there are cases where a destination is not registered when a user uses a scan process. In such a case, for example, there is a concern that the user cannot execute a push scan even if he or she operates the user interface.

[0005] The present invention has been made in consideration of the above-mentioned problems, and has an object to suppress a decrease in the usability of a user interface when performing a scan process. [Means for solving the problem]

[0006] In order to solve the above problem, the present invention relates to a scanner including a memory, a controller, and a user interface having operation keys. The controller executes a destination storage process for storing destination information corresponding to the destination of scan data in the memory, a judgment process for judging whether destination information is stored in the memory, a disabling process for disabling the operation key when it is judged by the judgment process that the destination information is not stored, and for enabling the operation key when it is judged that the destination information is stored, and a scan process for transmitting the created scan data to the destination specified by the destination information when the enabled operation key is operated. "Destination information" is information that can identify the destination, and "storing destination information" means that the destination can be specified from the destination information stored in the memory. For example, the destination information may be information that uses consecutive numbers or letters other than information that is uniquely set according to the destination. In this case, when a new destination is registered, destination information with the same value as the destination information that has already been deleted for this destination may be set again. "Enabling the operation key" means that the operation key is put into a state in which it can perform its normal function, specifically, that a signal is output to the controller in response to the operation of the operation key, and the controller accepts the output signal. On the other hand, disabling an operation key means putting the operation key in a state where it cannot perform its normal function, and means that the operation of the operation key is not accepted, or the controller does not accept signals associated with the operation of the operation key.

[0007] In the above configuration, when the destination information is not stored in the memory and it is determined that the destination information is not stored, the operation keys are disabled to not accept an operation to execute the scan process, and when it is determined that the destination information is stored, the operation keys are enabled to accept an operation to execute the scan process. This makes it possible to prevent the user from inputting an instruction to execute the scan process when the destination information is not stored in the memory and the scan data cannot be sent. As a result, it is possible to improve user convenience.

[0008] The present invention can be realized in various forms. In addition to being an invention of a scanner, it can also be realized as an invention of a control program executed by a controller of a scanner. Effect of the Invention

[0009] According to the present invention, [Brief description of the drawings]

[0010] [Figure 1] A diagram showing the configuration of a scanning system. [Diagram 2] FIG. [Diagram 3] 11 is a timing chart showing a procedure for updating management information. [Figure 4] 11 is a flowchart illustrating a procedure of a process after the standby screen is displayed. [Diagram 5] FIG. [Figure 6] FIG. [Figure 7] 10 is a flowchart showing a processing procedure when disabling an operation icon. [Figure 8] FIG. 4 is a diagram illustrating a function selection screen. [Figure 9] FIG. [Figure 10] FIG. 4 is a diagram illustrating a scan execution screen. [Figure 11] 13A and 13B are diagrams illustrating a function selection screen on which an operation icon is disabled. [Figure 12] 10 is a flowchart showing the procedure of a process for disabling an operation icon according to the second embodiment. [Figure 13] 13 is a timing chart showing a procedure of a process for disabling an operation icon according to the third embodiment. [Figure 14] FIG. 13 is a diagram illustrating an EWS screen when a destination is not registered. [Figure 15] FIG. 13 is a diagram illustrating an EWS screen when a destination is registered. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] (First embodiment) The scanning system according to the present embodiment will be described with reference to the drawings. The scan system 100 shown in FIG. 1 includes a terminal 10, servers 30, 31, and 32, and an MFP (abbreviation of Multifunction Peripheral / Printer / Product) 50. The terminal 10, the servers 30, 31, and 32, and the MFP 50 are connected to a network 200. In this embodiment, the network 200 may be the Internet, a local area network (LAN), or a combination of a LAN and the Internet. The network 200 may be wired, wireless, or a combination of wired and wireless. In this embodiment, the terminal 10 and the MFP 50 are wirelessly connected to a router (not shown) that constitutes a part of the network, and the terminal 10 or the MFP 50 and the servers 30, 31, and 32 are connected via the Internet. In this embodiment, the MFP 50 is an example of a scanner.

[0012] The following describes the hardware configuration of the MFP 50. The MFP 50 includes a bus 51, a communication IF 52, a printer unit 53, a reading unit 54, a user IF 55, a controller 56, a memory 57, and a FAX unit 58. The various units that make up the MFP 50 are connected to each other so as to be able to communicate with each other via the bus 51. IF is an abbreviation for Interface.

[0013] The communication IF 52 connects the MFP 50 to the network 200 in accordance with a predetermined communication protocol. The communication IF 52 is capable of performing wireless communication of the Wi-Fi® (registered trademark) system based on the IEEE 802.11 standard or a standard equivalent thereto. The communication IF 52 may also perform short-range wireless communication with the terminal 10 using Bluetooth (registered trademark) or the like.

[0014] The user IF 55 is an interface between the controller 56 and the user, and in this embodiment, includes a touch panel 551 and operation keys 552 as physical keys. The touch panel 551 has a touch sensor and outputs a signal according to the detection result by the touch sensor. Note that "touch" in this embodiment includes the general operation of bringing an input medium into contact with the display screen of the touch panel 551. In addition, the concept of "touch" described above may include bringing the input medium close to a position where the distance between the input medium and the touch panel 551 is very small. Furthermore, the input medium may be a user's finger, a touch pen, or the like.

[0015] The printer unit 53 executes a print operation to print an image on a recording medium such as a sheet or a disk. The printer unit 53 may employ a recording method such as an inkjet method in which ink is ejected onto a recording medium, or an electrophotographic method in which a toner image is formed on a photoreceptor and the formed toner image is transferred onto the recording medium. The reader unit 54 executes a scan process to read an image recorded on a document and create scan data. The controller 56 of the MFP 50 causes the reader unit 54 to read a document set on an ADF (Auto Document Feeder) or a reading table to create scan data, and the created scan data can be transmitted to the server 30 or the terminal 10 via the communication IF 52. The FAX unit 58 executes a FAX process according to a predetermined protocol. The MFP 50 may also be capable of executing a composite operation that combines a plurality of operations. A copy process that combines a print operation by the printer unit 53 and a scan process by the reader unit 54 is an example of a composite operation.

[0016] In this embodiment, the scan process includes individual processes of "Scan to File", "Scan to Email", "Scan to Mobile", "Scan to OCR", "Scan to Image", and "Scan to Media". "Scan to File" is an individual process for storing scan data in an FTP server (not shown) connected to the network 200. "Scan to Email" is an individual process for sending scan data by email to a specified email address. "Scan to OCR" is an individual process for converting scan data into text data. "Scan to Image" is an individual process for starting a graphic application and editing the scan data by the graphic application. "Scan to Media" is an individual process for storing scan data in an external medium such as a USB connected to the MFP 50.

[0017] "Scan to Mobile" is an individual process that, upon receiving an instruction to execute a scan process from a user via the user IF 55, causes the MFP 50 to create scan data and upload the created scan data to the service providing server 30. The scan data uploaded to the service providing server 30 can be downloaded by operating the terminal 10. In this embodiment, "Scan to Mobile" is an example of a push scan process.

[0018] The controller 56 is configured with a CPU, an ASIC (application specific integrated circuit), etc., and controls the operations of the printer unit 53, the reader unit 54, and the user IF 55. The memory 57 stores various programs executed by the controller 56.

[0019] In this embodiment, the memory 57 is configured by combining, for example, a RAM, a ROM, and a flash memory. The memory 57 may also be a storage medium that can be read by the controller 56, which is a computer. The storage medium also includes recording media such as a CD-ROM and a DVD-ROM. The same applies to the memory 15 described below.

[0020] The memory 57 stores a control program 40. The controller 56 executes the control program 40 to perform the above-mentioned operations such as scanning, printing, and faxing. The data storage area of ​​the memory 57 stores capability information 41 and management information 42 (FIG. 2) as data referenced by the controller 56.

[0021] The capability information 41 includes a plurality of items indicating the performance of the MFP 50, and is, for example, information in a structure format. The capability information 41 stores the items of "original size," "resolution," "color setting," "reading format," and "file format" as items related to the scan process. "Original size" is information indicating the read range of the original when the MFP 50 executes the scan process. For example, "A4" is information indicating that the original is read in a read range of A4 size, and "automatic" is information indicating that the read range can be automatically adjusted according to the original. "Resolution" is information indicating the resolution of the scan data when the scan process is executed. "Color setting" is information setting the presence or absence of color in the scan data when the MFP 50 executes the scan process, and includes, for example, "color" and "monochrome." "Reading format" is information indicating the read side (double-sided, single-sided) of the original when the MFP 50 executes the scan process. "File format" is information indicating the file format (JPEG, TIFE) of the scan data when the MFP 50 executes the scan process. The capability information 41 may include items such as "ADF tilt correction," "brightness," "contrast," and "blank page removal."

[0022] The management information 42 stores information about destinations registered in "Scan to Mobile". In this embodiment, as shown in FIG. 2, the management information 42 includes each item of "user ID", "display name", and "scan setting". In the management information 42, the "user ID" is information assigned to manage a destination device on the scan system 100. The "display name" is information indicating a display name when the destination is displayed on the user IF 55 of the MFP 50. In this embodiment, the display name is an example of information for identifying the destination. The "scan setting" is a scan setting when performing a scan process for the destination, and can be set within a range indicated by the capability information 41. In addition, the management information 42 may include identification information for identifying the destination device, such as the MAC address of the device and the program ID of the control program 40.

[0023] Next, the servers 30, 31, and 32 will be described. Each of the servers 30, 31, and 32 includes a CPU as a computer, a communication IF, and a memory. The service providing server 30 is a server to which scan data created by the MFP 50 is uploaded. The service providing server 30 can cause the terminal 10 to download the uploaded scan data in response to an instruction from the terminal 10. The information collecting server 31 is a server that manages management information 42.

[0024] The push notification server 32 is a server that transmits a push notification to a destination device when scan data is uploaded to the service providing server 30. Examples of mechanisms by which the push notification server 32 provides push notifications include APNS (Apple Push Notification Service) and GCM (Google Cloud Messaging for Android). In this embodiment, when using the APNS or GCM service, the push notification server 32 registers an address indicating the location of the destination device as notification information in association with a push notification ID, and the destination device acquires the push notification ID from the push notification server 32. The push notification is a notification according to the APNS or GCM protocol. The "push notification ID" is information for identifying the destination when a push notification is performed.

[0025] Next, the terminal 10 will be described. The terminal 10 is a smartphone or a tablet terminal. The terminal 10 includes a bus 11, a terminal side CPU 12, a user IF 13, a communication IF 14, and a memory 15. These components are connected to each other via the bus 11 so as to be able to communicate with each other.

[0026] The user IF 13 has a similar configuration to the user IF 55 of the MFP 50, and includes a touch panel and operation keys. The communication IF 14 has a similar configuration to the communication IF 14 of the MFP 50. Note that the communication IF 14 may perform wireless communication using a mobile communication system via a base station.

[0027] The terminal CPU 12 controls each part of the terminal 10 by executing programs stored in the memory 15. The memory 15 stores an OS 20 (abbreviation of Operating System), an application program 21, and a browser program 22. In the following, the application program will be abbreviated to "application." The CPU that executes a program may also be referred to simply as the program name. For example, the description "application 21" may mean "the terminal CPU 12 that executes application 21."

[0028] In this embodiment, the processing of the CPU according to the instructions written in the program is mainly shown. That is, the processing of "judgment", "extraction", "selection", "calculation", "decision", "identification", "acquisition", "acceptance", "control" and the like in the following description represents the processing of the CPU and the controller. The processing by the CPU also includes hardware control via the OS 20. Note that "acquisition" is used as a concept that does not require a request. That is, the processing of receiving data without the application 21 requesting it is also included in the concept of "the CPU acquires data". In addition, "data" in this specification is expressed in a computer-readable format. And data with the same substantial meaning but different formats are treated as the same data. The same applies to "information" in this specification.

[0029] The OS 20 has an API (Application Programming Interface) that enables the application 21 to use the functions of the OS 20, to communicate with the servers 30, 31, 32 and the MFP 50, and to use the functions of other programs. The application 21 issues instructions for print processing, scan processing, etc. to the MFP 50 that can be connected via the communication IF 14 using the functions of the OS 20. The browser program 22 communicates with the MFP 50 or the servers 30, 31, 32, and can display Web page data transmitted from the MFP 50.

[0030] Next, a process for registering or deleting a destination used in the individual process "Scan to Mobile" will be described with reference to Fig. 3. Among the processes shown in Fig. 3, the processes executed by the terminal 10 are executed by the application 21, and the processes executed by the MFP 50 are executed by the control program 40. It is assumed that network connections between the terminal 10, the MFP 50, and the servers 30 and 31 have already been established.

[0031] In step S11 (hereinafter simply referred to as S11), the application 21 displays a registration screen on the user IF 13 and accepts an input operation by the user via the user IF 13. The registration screen is a screen for registering or deleting information of the terminal 10 in the management information 42 in response to an input operation by the user. When registering a new destination, the user designates the MFP 50 on the registration screen displayed on the user IF 13 and inputs a display name and scan settings as information related to the destination to be registered (i.e., the terminal 10). On the other hand, when deleting a destination that has already been registered, the information related to the destination to be deleted is erased on the registration screen. Here, an example of registering a destination will be described.

[0032] In S12, the application 21 transmits the device ID of the MFP 50, the display name and scan settings inputted in S11, and the push notification ID of its own device together with a registration request as the destination of the push scan process of the MFP 50. The device ID is information for identifying the MFP, and may be acquired in advance by the application 21 from the MFP 50 or the like. In S13, the service providing server 30 performs an update process for storing each piece of information transmitted from the terminal 10 in the management information 42. Specifically, a user ID is assigned to the destination to be registered, and a display name and scan settings related to the destination are associated with the user ID and stored. In this embodiment, an upper limit is set for the number of user IDs that can be managed by the management information 42. For example, the management information 42 shown in FIG. 2 can store information (display name, scan settings, push notification ID) related to the device that is the destination in association with N number of user IDs from "User1" to "UserN" (N is an integer equal to or greater than 1). When a new destination is registered, a user ID to which no device-related information is associated is assigned from among N user IDs, and information about the destination is stored for the assigned user ID. Although not shown in Fig. 2, the push notification ID transmitted from the destination device and the device ID are stored in the management information 42 stored in the service providing server 30 in association with the user ID.

[0033] In S14, the service providing server 30 transmits the management information 42 updated in S13 together with the device ID to the information collecting server 31. In this embodiment, the service providing server 30 transmits the management information 42 to which the information of the newly destination device has been added all at once to the information collecting server 31. Note that in S14, the service providing server 30 may transmit a URL indicating the address of its own device to the information collecting server 31 together with the management information 42.

[0034] In S15, the information collecting server 31 transmits the updated management information 42 and the device ID transmitted from the service providing server 30 to the MFP 50 as is. The device ID may be stored in advance in the memory 57 of the MFP 50 prior to the processing shown in FIG.

[0035] When the control program 40 of the MFP 50 receives the updated management information 42 transmitted from the information collecting server 31, it performs a destination storage process in S16. In this destination storage process, the control program 40 updates the management information 42 all at once by overwriting the received updated management information 42 on the management information 42 currently stored in the memory 57. In this way, the control program 40 registers the terminal 10 as a destination. Note that the device ID transmitted from the information collecting server 31 is stored in association with the user ID in the management information 42 stored in the memory 57 of the MFP 50.

[0036] Next, the procedure of the process executed by the controller 56 when the destination is registered by storing information on a new destination in the management information 42 will be described with reference to FIG. 4. In S20, a standby screen is displayed. The standby screen is a screen displayed on the touch panel 551 of the user IF 55 when the main power of the MFP 50 is turned on. As shown in FIG. 5, the standby screen 60 is a screen that accepts a designation operation of a process that the MFP 50 can execute. In this embodiment, the standby screen 60 includes a FAX designation icon 61, a copy designation icon 62, a scan designation icon 63, and a shortcut icon 64. The FAX designation icon 61 is an icon that accepts an execution operation for a FAX process. The copy designation icon 62 is an icon that accepts an execution operation for a copy process. The scan designation icon 63 is an icon that accepts an execution operation for a scan process. The shortcut icon 64 is an icon that accepts an instruction to display a shortcut screen including a shortcut key that has already been registered.

[0037] In S21, it is determined whether or not the management information 42 has been updated. As described above, when a destination is registered or deleted, the updated management information 42 is transmitted in a lump from the service providing server 30 via the information collecting server 31, and the management information 42 stored in the memory 57 is updated. In this embodiment, the control program 40 stores history information indicating the update of the management information 42 in the memory 57, and by referring to this history information, it is possible to determine whether or not the management information 42 has been updated. Note that if a negative determination is made in S21, the process returns to S21.

[0038] If an affirmative decision is made in S21, the process proceeds to S22, where the management information 42 is referenced. In S23, it is determined whether or not new destination-related information, including a user ID, is stored in the management information 42. If the management information 42 has been updated to show that no destination-related information is stored, a negative decision is made in S23, and the process returns to S21. On the other hand, if the management information 42 has been updated to show that destination-related information, including a user ID, is stored, a positive decision is made in S23, and the process proceeds to S24.

[0039] In S24, a notification icon is displayed on the standby screen 60. In the standby screen 60 shown in Fig. 5, a notification icon 66 is displayed at the top. The notification icon 66 includes a text image indicating that the individual function "Scan to Mobile" can be executed as a result of a new destination being registered. In this embodiment, the user ID is an example of destination information.

[0040] In S25, it is determined whether or not an operation on the notification icon 66 displayed in S24 has been detected. If an operation on the notification icon 66 has not been detected, a negative judgment is made in S25, and the process returns to S21. On the other hand, if an operation on the notification icon 66 has been detected, an affirmative judgment is made in S25, and the process proceeds to S26.

[0041] In S26, a notification screen indicating that the individual function "Scan to Mobile" is now executable is displayed on the user IF 55. A text image indicating that the individual function "Scan to Mobile" is now executable as a result of the destination being registered is displayed on the notification screen 67 shown in FIG. 6. Furthermore, a text image prompting the terminal 10 to install an application program for executing the individual function "Scan to Mobile" is displayed on the notification screen 67. Note that if the application program has already been installed, it is not necessary to display a text image notifying the user that the application program should be installed on the notification screen 67. In this embodiment, the processes executed by the control program 40 in S24 to S26 are an example of a notification process.

[0042] In S27, if an instruction operation to hide the notification screen 67 is detected, the process proceeds to S28. However, if an instruction operation to hide the notification screen 67 is not detected, the process waits. In S28, the notification screen 67 and the notification icon 66 displayed on the standby screen 60 are hidden. Then, the process returns to S21.

[0043] Next, the process executed when the scan designation icon 63 is operated on the standby screen 60 will be described with reference to Fig. 7. The process shown in Fig. 7 is executed by the control program 40, and therefore the subject will not be described.

[0044] In S30, the management information 42 stored in the memory 57 is referenced. In S31, it is determined whether or not a user ID is stored in the management information 42. If a user ID is stored in the management information 42 and a positive determination is made in S31, the process proceeds to S32, and a function selection screen having an operation icon corresponding to "Scan to Mobile" is displayed on the user IF 55.

[0045] The function selection screen 70 displayed on the user IF 55 in S32 includes operation icons 71, 72, and 73 that accept the selection of individual processes among the scan processes, as shown in FIG. 8. Among them, the operation icon 71 is an icon that accepts an instruction operation for the individual function "Scan to Media". The operation icon 72 is an icon that accepts an instruction operation for the individual function "Scan to Mobile". The operation icon 73 is an icon that accepts an instruction operation for the individual function "Scan to Email". In this embodiment, the operation icons 71 to 73 can be set to be able to accept a designated operation by the user by positioning them in the center of the function selection screen 70 in response to the operation of the change icons 74 and 75. In the function selection screen 70 shown in FIG. 8, the operation icon 72 is set to be an icon that can accept an instruction by the user.

[0046] When it is detected that the operation icon 72 has been operated on the function selection screen 70 displayed in S32, an affirmative decision is made in S34, and the process proceeds to S35. Note that when it is detected that the operation icons 71 and 73 have been operated on the function selection screen 70, a process different from the process shown in FIG.

[0047] In S35, it is determined whether or not there are two or more destinations registered in the management information 42. For example, when two destinations are registered by the process shown in Fig. 3, two user IDs and display names associated with these user IDs are stored in the management information 42. If an affirmative determination is made in S35, the process proceeds to S36.

[0048] In S36, a destination screen is displayed on the user IF 55. The destination screen is a screen on which a list of display names stored in the management information 42 is displayed. A destination screen 76 shown in Fig. 9 includes destination icons 77, 78, and 79 for receiving destination designation. Each of the destination icons 77 to 79 displays one of the display names stored in the management information 42, namely, "User A," "User B," and "User C."

[0049] In S37, it is determined whether or not a designation operation of any of the destination icons 77 to 79 included in the destination screen 76 has been detected. If a negative determination is made in S37, the process waits. On the other hand, if a positive determination is made in S37, a scan execution screen 80 shown in FIG. 10 is displayed on the user IF 55. The scan execution screen 80 is a screen that accepts an instruction to execute the individual process "Scan to Mobile" targeted at the designated destination. The scan execution screen 80 shown in FIG. 10 is a screen that is displayed when the destination icon 77 is operated on the destination screen 76. The scan execution screen 80 includes a setting change icon 81 and an execution icon 82.

[0050] The setting change icons 81 are icons that accept a user's designated operation when changing scan settings associated with a specified destination. Each setting change icon 81 displays the current scan settings (paper size "A4", color setting "monochrome", resolution "200 dpi") that are stored in association with the user ID "User1" in the management information 42. The execution icon 82 is an icon that accepts a user's designated operation when starting the individual process "Scan to Mobile" for the currently specified destination.

[0051] Returning to S35, if there is only one registered destination, the process proceeds to S38, where the scan execution screen 80 corresponding to the currently registered destination is displayed on the user IF 55. If the execution icon 82 is specified on the scan execution screen 80, "Scan to Mobile" is executed for the destination. Specifically, the control program 40 creates scan data by causing the reading unit 54 to read the document set on the reading table. Note that if the user touches the icon to cancel the execution of the scan process, the control program 40 does not execute the scan process.

[0052] The control program 40 transmits the created scan data to the service providing server 30. At this time, the control program 40 transmits a user ID related to the destination to the service providing server 30 together with the scan data. When the service providing server 30 receives the scan data transmitted from the MFP 50, it uploads the scan data to memory. At this time, the service providing server 30 stores the label name, model name, execution date and time, data size, and thumbnail image contained in the scan data in a job management table for managing the scan data in association with the transmitted user ID.

[0053] The service providing server 30 transmits to the push notification server 32 a push notification ID and a URL specifying the upload destination of the scan data together with a request to transmit a push notification. The push notification ID transmitted from the service providing server 30 is a push notification ID corresponding to the user ID of the destination (terminal 10 in this case). When the push notification server 32 receives a request to transmit a push notification, it refers to the address of the device (terminal 10 in this case) associated with the push notification ID in the notification information stored in the push notification server 32. Then, it transmits a push notification to the referenced address. In this embodiment, the push notification includes a URL specifying the upload destination of the scan data and web page data for displaying this URL on the screen.

[0054] When the application 21 of the terminal 10 receives the push notification, it displays a notification image indicating that the push notification has been received on the top screen. This allows the user operating the terminal 10 to confirm that the scan data addressed to the terminal 10 has been uploaded to the service providing server 30. When the application 21 detects an operation on the notification image via the user IF 13, it causes the browser program 22 to display a download designation screen using the web page data included in the push notification. The URL included in the push notification is displayed on the download designation screen. When the application 21 accepts an operation to designate a URL on the download designation screen, it transmits a download request for the scan data uploaded to the designated URL to the service providing server 30.

[0055] On the other hand, if the user ID associated with the destination is not stored in the management information 42 and a negative judgment is made in S31, the process proceeds to S33, and the user IF 55 is caused to display the function selection screen 70 on which the operation icon 72 corresponding to the individual process "Scan to Mobile" is not displayed. As shown in Fig. 11, the function selection screen 70 displayed in S33 displays only the operation icons 71 and 73. In other words, it becomes impossible to accept an operation to specify the individual process "Scan to Mobile" on the function selection screen 70. Thereafter, the process in Fig. 7 ends.

[0056] The present embodiment described above can provide the following advantages. The controller 56 of the MFP 50 determines whether or not a user ID is stored in the management information 42, and if it determines that a user ID is not stored, it does not display the operation icon 72 for receiving an instruction to execute the individual process "Scan to Mobile" on the function selection screen 70. This makes it possible to prevent the user from inputting an instruction to execute the individual process "Scan to Mobile" when scan data cannot be sent to the destination. As a result, it is possible to improve user convenience.

[0057] When the controller 56 determines that the user ID is stored, it displays an operation icon 72 on the function selection screen 70 displayed on the touch panel 551. This allows the user to visually recognize that the MFP 50 can execute the individual process "Scan to Mobile". As a result, it is possible to improve user convenience.

[0058] When the controller 56 determines that the user ID is not stored in the management information 42, the controller 56 does not display the operation icon 72 on the function selection screen 70. This allows the user to visually recognize that the MFP 50 cannot execute the individual process "Scan to Mobile". As a result, the convenience for the user can be improved.

[0059] When a user ID is stored in the management information 42 from a state in which the user ID was not stored, and the individual process "Scan to Mobile" becomes executable, the controller 56 notifies the user on the standby screen 60. This allows the user to recognize that the individual process "Scan to Mobile" is executable by checking the standby screen 60, thereby further improving user convenience.

[0060] The controller 56 of the MFP 50 stores the management information 42 updated in response to the operation of the terminal 10 in the memory 57. This makes it possible to apply the present invention to an MFP 50 that can delete a user ID in response to the operation of the terminal 10.

[0061] (Modification of the first embodiment) In the process of S28 in the first embodiment described above, the operation icon 72 is hidden on the function selection screen 70. Alternatively, the operation icon 72 may be disabled by maintaining its display but not accepting any operation. In this case, the disabled operation icon 72 may be distinguished from the operation icon 72 that is not disabled, for example, by being displayed in a grayed-out state.

[0062] In the above-described first embodiment, when a new destination is registered, the notification icon 66 is displayed on the standby screen 60. Instead of this, when a new destination is registered, a notification may be displayed on the function selection screen 70 indicating that the individual function "Scan to Mobile" is now executable.

[0063] In the above-described first embodiment, the scan settings are stored in the management information 42. Alternatively, the scan settings may not be stored in the management information 42. In this case, the control program 40 may individually accept changes in the scan settings, etc. via the user IF 55 when executing the individual process “Scan to Mobile”.

[0064] Second embodiment In the second embodiment, the configuration different from the first embodiment will be mainly described. In the second embodiment, the same components as those in the first embodiment are denoted by the same reference numerals, and the description thereof will not be repeated.

[0065] In this embodiment, when a user is logged in to the MFP 30 and the user ID of the logged-in user is stored, the controller 56 displays an operation icon 72 relating to the individual process "Scan to Mobile" on the user IF 55. In this embodiment, the process executed when the scan designation icon 63 is operated on the standby screen 60 will be described with reference to Fig. 12. The process shown in Fig. 12 is executed by the control program 40, and therefore the subject will not be described.

[0066] In S40, it is determined whether or not a user is currently logged in to the MFP 50. In this embodiment, a login screen can be displayed on the touch panel 551 in response to an operation of the user IF 55. For example, the login screen displays an input field for inputting a user name and password information, and a login button. When the user inputs the user name and password information and operates the login button, authentication is performed for the input user name and password information. If the authentication is successful, the MFP 50 can be shifted to a logged-in state. If the user is not currently logged in, a negative judgment is made in S40, and the process proceeds to S33. On the other hand, if the user is currently logged in, a positive judgment is made in S40, and the process proceeds to S30.

[0067] In S30, the management information 42 stored in the memory 57 is referred to. In S41, based on a comparison result between a display name, which is information for recognizing a destination stored in the management information 42, and a user name input on the login screen, it is determined whether or not the management information 42 contains information about the login user. Specifically, when the display name stored in the management information 42 matches the user name of the login user, it is determined that the management information 42 contains information about the login user. In addition, when the user name input on the login screen is included in the display name stored in the management information 42, it may be determined that the management information 42 contains information about the login user. In this case, the user name and the display name do not need to correspond one-to-one, and when the login user registers two or more devices as destinations, the user name and the display name may correspond one-to-many. When the judgment in S41 is affirmative, the process proceeds to S32, and a function selection screen (FIG. 8) having an operation icon corresponding to the individual function "Scan to Mobile" is displayed on the user IF 55.

[0068] If the user ID stored in management information 42 contains characters or the like that can individually identify the user related to the destination, in S41, it may be determined whether or not the management information 42 contains information related to the logged-in user based on the result of comparing the user ID stored in management information 42 with the user name entered on the login screen.

[0069] As in the first embodiment, when it is detected that the operation icon 72 has been operated on the function selection screen 70 displayed in S32, an affirmative decision is made in S34 and the process proceeds to S35. Then, after the processes of S35 to S37 are performed, in S38 the scan execution screen 80 (FIG. 10) is displayed on the user IF 55.

[0070] On the other hand, if information about the logged-in user is not stored in the management information 42 and a negative judgment is made in S41, the process proceeds to S33, and the function selection screen 70 (FIG. 11) in which the operation icon 72 corresponding to the individual process "Scan to Mobile" is not displayed is displayed on the user IF 55. In other words, it is made impossible to accept an instruction operation for the individual process "Scan to Mobile". When S38 or S33 is ended, the process shown in FIG. 12 is ended.

[0071] In the present embodiment described above, when the control program 40 determines that the user ID of the logged-in user is stored in the management information 42, it displays the operation icon 72 corresponding to the individual process "Scan to Mobile" on the function selection screen 70. As a result, when the logged-in user is logged in to the MFP 50, if the user ID indicating the destination of the logged-in user is stored, an instruction to execute the individual process "Scan to Mobile" is accepted, thereby further improving user convenience.

[0072] Third embodiment In the third embodiment, the configuration different from the first embodiment will be mainly described. In the third embodiment, the same components as those in the first embodiment are denoted by the same reference numerals, and the description thereof will not be repeated.

[0073] In the first embodiment, the user IF 55 of the MFP 50 had a touch panel 551. Instead, in this embodiment, the user IF 55 of the MFP 50 does not have a touch panel 551, and has only operation keys 552 which are physical keys. The control program 40 can set, for the operation keys 552, a process to be executed by operating the operation keys 552, among the individual processes executable by the MFP 50. This allows the user to operate the operation keys 552 to cause the MFP 50 to execute the set individual process.

[0074] 13 is a timing chart for explaining the procedure of a process for setting individual processing for operation key 552. In S50, terminal 10 (application 21) transmits a display request for a web screen to MFP 50. MFP 50 of this embodiment has a web server function (hereinafter referred to as EWS: Embedded Web Server) and is capable of displaying a screen in response to a request from a web browser of terminal 10 or the like. When control program 40 of terminal 10 receives the display request from terminal 10, it transmits EWS screen data in S51. The EWS screen data is web page data for displaying an EWS screen in browser program 22 of terminal 10.

[0075] When the control program 40 receives the EWS screen data, in S52, the control program 40 causes the browser program 22 to display an EWS screen based on the received EWS screen data. FIGS. 14 and 15 are diagrams for explaining an EWS screen 300 displayed on the user IF 55 by the browser program 22 as an example. The EWS screen 300 includes a setting area 301 and an item designation area 302. The item designation area 302 is an area in which a list of items indicating services that can be provided by the MFP 50 (EWS) is displayed. The user can specify an item displayed in the item designation area 302 by operating the terminal 10 to execute a service or perform settings related to the service. The setting area 301 is an area in which a screen related to the service specified in the item designation area 302 is displayed. Note that in S52, no screen is displayed in the setting area 301 because no item is designated in the item designation area 302.

[0076] When the user performs a designation operation for an item 303 ("Scan to XXX") included in an item designation area 302 on an EWS screen 300 displayed on the user IF 13 of the terminal 10, in S53 the application 21 requests screen data corresponding to the designated item 303 from the MFP 50. The screen data is data for displaying an image to be displayed in the setting area 301 of the EWS screen 300. In this embodiment, the control program 40 does not transmit Web page data for displaying the entire EWS screen 300, but transmits image data for displaying a portion of the EWS screen 300 (in this embodiment, the setting area 301) to the terminal 10 in response to the request transmitted from the terminal 10.

[0077] When the control program 40 receives a request for screen data, in S54, it refers to the management information 42. In S55, it is determined whether or not a user ID associated with the destination is stored in the management information 42. If a negative determination is made in S55, the process proceeds to S56. In S56, first candidate data, which is screen data in which processes other than the individual process "Scan to Mobile" among the services classified in the "Scan to XX" item 303 are selected as selection candidates, is transmitted to the terminal 10. In this embodiment, the individual processes belonging to the item "Scan to XX" include the individual processes "Scan to File", "Scan to OCR", "Scan to Image", "Scan to Email", and "Scan to Mobile" described above.

[0078] When the application 21 receives the first candidate data from the MFP 50, in S57, the application 21 causes the browser program 22 to display the EWS screen 300 using the first candidate data. In this embodiment, a drop box 304 displaying specifiable individual processes is displayed in the setting area 301 of the EWS screen 300. Specifically, as shown in FIG. 14, in the setting area 301, a partial name of each of the individual processes "File", "OCR", "Image", and "Email" indicated by the first candidate data is displayed in the drop box 304. In other words, in S57, "Mobile", which is a partial name of the individual process "Scan to Mobile", is not displayed in the drop box 304. For this reason, the user cannot operate the EWS screen 300 to set the individual process "Scan to Mobile" as a process to be executed by operating the operation key 552.

[0079] Returning to S55, if the user ID associated with the destination is stored in the management information 42, an affirmative judgment is made in S55 and the process proceeds to S58. In S58, second candidate data, which is screen data in which all individual processes classified in item 303 are candidates, is transmitted to the terminal 10. That is, the second candidate data includes the individual process "Scan to Mobile" as a candidate.

[0080] When the application 21 receives the second candidate data from the MFP 50, in S59, the application 21 causes the browser program 22 to display the EWS screen 300 using the second candidate data. On the EWS screen 300 displayed in S59, as shown in Fig. 15, in a setting area 301, partial names of all the individual processes "File", "OCR", "Image", "Email", and "Mobile" classified by items 303 are displayed in a drop box 304. Therefore, by operating the EWS screen 300, the user can set the individual process "Scan to Mobile" as a process to be executed by operating the operation key 552.

[0081] The following description will be given taking as an example a case where a "Mobile" designation operation is performed on the EWS screen 300 displayed on the terminal 10. The application 21 transmits setting information including the individual process designated by the user in S60.

[0082] When the control program 40 receives the setting information transmitted from the terminal 10, in S61, the control program 40 performs a setting process to set the individual process (here, "Scan to Mobile") as a process executed by operating the operation key 552. As a result, when the user operates the operation key 552, the control program 40 executes the individual process "Scan to Mobile".

[0083] Thereafter, when a destination is deleted by operating the terminal 10, the management information 42 from which the information (user ID, display name, scan setting) about the destination to be deleted is overwritten in the service providing server 30 according to the process shown in Fig. 3. In S62, the updated management information 42 is transmitted from the service providing server 30 to the MFP 50 via the information collecting server 31.

[0084] When the control program 40 receives the updated management information 42, in S63, it overwrites the memory 57 with the received management information 42, thereby updating the management information 42 in one go. In S64, the control program 40 changes the individual process executed by operating the operation key 552 from the individual process "Scan to Mobile" to another individual process. This is because the individual process "Scan to Mobile" can no longer be executed due to the deletion of the destination. In this embodiment, the control program 40 changes from the individual process "Scan to Mobile" to the individual process set by default. For example, the individual process set by default is the individual process "Scan to Media".

[0085] In the present embodiment described above, when the control program 40 determines that a user ID is stored in the management information 42, it displays the individual process "Scan to Mobile" as a selection candidate on the EWS screen 300, and when the individual process "Scan to Mobile" is selected, it sets the individual process "Scan to Mobile" as a process to be executed by operating the operation key 552. On the other hand, when the control program 40 determines that a user ID is not stored in the management information 42, it does not display the individual process "Scan to Mobile" as a selection candidate on the EWS screen 300. As a result, the same effect as the present invention can be achieved even in a configuration in which the presence or absence of an instruction to execute the individual process "Scan to Mobile" can be switched by operating the terminal 10.

[0086] If information related to the destination, including the user ID, is deleted after the individual process "Scan to Mobile" is set to operation key 552, control program 40 changes the process executed in response to operation of operation key 552 from the individual process "Scan to Mobile" to a default individual process. This causes MFP 10 to start execution of some individual process when the user mistakenly operates operation key 552 in a state where the push notification ID is not stored, so that it is possible to prevent the user from mistakenly recognizing that MFP 10 is malfunctioning, compared to a case where MFP 10 does not perform any operation even when operation key 552 is operated.

[0087] (Modification of the third embodiment) In the above-described third embodiment, an individual process is set on the EWS screen 300 to be executed by operating the operation keys 552. Alternatively, an individual process may be set on the EWS screen 300 to be executed by operating an operation icon displayed on the touch panel 551. In this case as well, the control program 40 only needs to set the individual process in S61.

[0088] In the above-described third embodiment, the EWS screen 300 is displayed on the terminal 10 to set an individual process to be executed by operating the operation key 552. Alternatively, the EWS screen 300 may be displayed on the MFP 10.

[0089] (Other embodiments) The technology disclosed in this specification is not limited to the above-described embodiments, and can be modified in various forms without departing from the spirit of the invention. For example, the following modifications are also possible. In the above-described embodiments, the destination information is a push notification ID, and the individual process "Scan to Mobile" is taken as an example. Alternatively, when the control program 40 performs the individual process "Scan to Email", the operation icon 73 (FIG. 8) may be displayed or hidden depending on whether the email address, which is the destination information, has been deleted. In this case, the control program 40 may display the function selection screen 70 with the operation icon 73 hidden in S33 of FIG. 7.

[0090] In each of the above-described embodiments, the terminal 10 is identified by using a user ID in the management information 42. Alternatively, the management information 42 may use identification information such as a device serial number or a program ID for identifying the application 21, instead of the user ID.

[0091] The MFP 50 has been described as a scanner, but this is merely an example, and the scanner may be a device equipped with only a scanning process. [Explanation of symbols]

[0092] 40: control program, 50: MFP, 55: user IF, 56: controller, 57: memory

Claims

1. A scanner comprising a memory, a controller, and a user interface having operation keys for receiving an instruction for a scan function, The controller: a destination storage process for storing destination information corresponding to the destination of the scan data in the memory; a determination process for determining whether the destination information is stored in the memory; a disabling process of disabling the operation key when it is determined by the determination process that the destination information is not stored, and disabling the operation key when it is determined that the destination information is stored; a scan process for transmitting the created scan data to a destination specified by the destination information when the enabled operation key is operated; Scanner to run.

2. the user interface has a display unit, and the operation keys are icons displayed on the display unit, 2. The scanner according to claim 1, wherein, in the invalidation process, when it is determined by the determination process that the destination information is stored, the operation key is enabled by displaying the operation key on the display unit.

3. 3. The scanner according to claim 2, wherein the invalidation process invalidates the operation keys by not displaying the operation keys on the display unit when it is determined in the determination process that the destination information is not stored.

4. The controller: a setting screen is displayed, the setting screen being a screen for accepting settings of a process to be executed by operating the operation key among a plurality of processes that the scanner can execute, including the scanning process; In the invalidation process, When it is determined that the destination information is stored by the determination process, the scanning process is displayed as a selection candidate on the setting screen, and when the scanning process is selected, the operation key is enabled; The scanner according to claim 1 , wherein when it is determined that the destination information is not stored in the determination process, the operation key is disabled by not displaying the scan process as a selection candidate on the setting screen.

5. 5. The scanner according to claim 4, wherein, when the destination information is deleted from the memory after the operation key is enabled by the disablement process, the controller changes the process to be executed in response to the operation of the operation key from the scanning process to a predetermined process different from the scanning process.

6. A scanner as described in any one of claims 1 to 5, wherein the controller performs a notification process to notify that the scanning process is now executable when the destination information is stored in the memory from a state in which the destination information is not stored in the memory and the scanning process becomes executable.

7. The controller is capable of accepting input of a login user for the scanner; the destination information determined by the determination process is information indicating a destination related to the logged-in user, 7. The scanner according to claim 1, wherein the invalidation process enables the operation key when the determination process determines that the destination information related to the logged-in user is stored.

8. In the destination storage process, information for identifying the destination is stored in the memory in association with the destination information; A scanner as described in claim 7, wherein the determination process determines that the memory stores the destination information related to the logged-in user based on a comparison result between information entered by the logged-in user and information for identifying the destination stored in the memory.

9. Equipped with a communication interface, The controller is capable of communicating with a server via the communication interface; the server is capable of storing the destination information, receives an instruction to add or delete the destination information from a terminal, updates the destination information in response to the received instruction, and transmits the updated destination information to the scanner; 9. The scanner according to claim 1, wherein the destination information transmitted from the server is stored in the memory in the destination storage process.

10. A control program executable on a controller of a scanner device having a memory and a user interface, The control program causes the controller to a destination storage process for storing destination information indicating a destination of the scan data in the memory; a determination process for determining whether the destination information is stored in the memory; a disabling process for disabling an operation key of the user interface for receiving an instruction for a scan function when it is determined by the determination process that the destination information is not stored, and for enabling the operation key when it is determined that the destination information is stored; a scan process for transmitting the created scan data to a destination specified by the destination information when the enabled operation key is operated; A control program that executes the above.

Images