Control program, terminal

Abstract

To improve convenience for a user who operates a terminal capable of causing a scanner to execute push scan processing.SOLUTION: A terminal side CPU 12 acquires scan data created by push scan processing, from a server 30 via a communication IF 16. The terminal side CPU 12 acquires job information in the push scan processing with its own device as the destination of scan data, from the server 30 via the communication IF 16, and causes a user interface to display an execution state of the push scan processing on the basis of the job information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a technique for creating scan data by reading an original. [Background technology]

[0002] Patent Document 1 describes a device capable of executing a so-called push scan process, which uploads scan data created by a scanner to a server. This allows a user, for example, even if the user is located far away from the device, to operate a terminal to access the server and download the scan data stored on the server to the terminal. [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] There are cases where a user who operates a terminal has difficulty in understanding the current state of scan data created by push scan processing. For example, when a large amount of scan data is uploaded, there is a concern that the user who operates the terminal may have difficulty in understanding the state of each piece of scan data.

[0005] The present invention has been made in consideration of the above problems, and has an object to improve the convenience of a user who operates a terminal capable of causing a scanner to execute push scan processing. [Means for solving the problem]

[0006] In order to solve the above problems, the present invention provides a control program executable by a controller of a terminal having a communication interface and a user interface, the control program causing the controller to execute a data acquisition process for acquiring scan data created by a push scan process of a scanner from a server via the communication interface. The push scan process is a process for causing the scanner to create scan data and upload the created scan data to the server. The control program causes the controller to execute a job information acquisition process for acquiring, via the communication interface, job information for the push scan process in which the device itself is the destination of the scan data, and a display process for displaying the execution status of the push scan process on the user interface based on the job information.

[0007] In the above configuration, the controller of the terminal acquires scan data created by the push scan process from the server via the communication interface. The controller acquires job information for the push scan process in which the terminal is the destination of the scan data via the communication interface, and displays the execution status of the push scan process on the user interface based on the acquired job information. This allows the user to grasp the execution status of the push scan process by viewing the terminal, thereby improving user convenience.

[0008] The present invention can be realized in various forms, and can be realized not only as an invention of a control program executed by a computer, but also as an invention of an information processing device. Effect of the Invention

[0009] This can improve user convenience when executing push scan processing. [Brief description of the drawings]

[0010] [Figure 1] A diagram showing the configuration of a scanning system. [Diagram 2]FIG. 4 is a diagram for explaining a job management table. [Diagram 3] 11 is a timing chart illustrating a registration process. [Figure 4] 11 is a timing chart illustrating a procedure for displaying a history screen. [Diagram 5] FIG. 4 is a diagram illustrating a function selection screen. [Figure 6] FIG. [Figure 7] 5 is a flowchart for explaining the process in S29 of FIG. 4. [Figure 8] 11 is a flowchart illustrating a process that is executed when an operation on a history screen is accepted. [Figure 9] FIG. 4 is a diagram illustrating a preview screen. [Figure 10] FIG. 4 is a diagram illustrating a scan setting screen. [Figure 11] 10 is a timing chart illustrating a procedure for displaying a history screen according to the second embodiment. 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.

[0012] The scan system 100 shown in FIG. 1 includes a terminal 10, a server 30, and an MFP (Multifunction Peripheral / Printer / Product) 50. The terminal 10, the server 30, 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 server 30 are connected via the Internet. In this embodiment, the MFP 50 is an example of a scanner device.

[0013] 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 FAX unit 55, a user IF 56, a controller 57, and a memory 58. The various units constituting 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.

[0014] The communication IF 52 connects the MFP 50 to the network 200 in accordance with a predetermined communication protocol. The user IF 56 is an interface between the MFP's controller 57 and the user, and includes a touch panel and operation keys in this embodiment. The controller 57 controls the operations of the printer unit 53, the reading unit 54, the FAX unit 55, and the user IF 56.

[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 operation to read an image recorded on a document and create scan data. The controller 57 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 can transmit the created scan data to the server 30 or the terminal 10 via the communication IF 52. The FAX unit 55 transmits and receives image data in a method conforming to the FAX protocol. The MFP 50 may also be capable of executing a composite operation that combines a plurality of operations. A copy operation that combines a print operation by the printer unit 53 and a scan operation by the reader unit 54 is an example of a composite operation.

[0016] In this embodiment, the MFP 50 can execute push scan processing and pull scan processing as scan operations. The push scan processing is a process in which, upon receipt of an instruction to execute a scan operation from a user via the user IF 56, the MFP 50 creates scan data and uploads the created scan data to the server 30. The scan data uploaded to the server 30 can be downloaded by operating the terminal 10. The pull scan processing is a process in which, upon receipt of an instruction to execute a scan operation from a user via the user IF 13 of the terminal 10, the terminal 10 transmits an instruction to execute a scan operation to the MFP 50, and the MFP 50 creates scan data in response and transmits the created scan data to the terminal 10.

[0017] The controller 57 is configured with a CPU, an ASIC (Application Specific Integrated Circuit), etc., and controls each unit that configures the MFP 50. The memory 58 stores various programs that the controller 57 executes.

[0018] In this embodiment, the memory 58 is configured by combining, for example, a random access memory (RAM), a read only memory (ROM), and a flash memory. The memory 58 may also be a storage medium that can be read by the controller 57, which is a computer. The storage medium also includes recording media such as CD-ROM and DVD-ROM. The same applies to the memories 17 and 35 described below.

[0019] The memory 58 stores destination information 41 and capability information 42 as data referenced by the controller 57. The destination information 41 is information for identifying devices that are candidate destinations of scan data created by push scan processing. The destination information 41 includes, for example, items such as "display name" and "program ID." The "display name" is information indicating the name of the candidate destination device when it is displayed on the user IF 56. The "program ID" is an ID for identifying a control program stored in the candidate destination device. For example, in the terminal 10, the program ID is an ID for identifying the control program 21.

[0020] The capability information 42 includes a plurality of items indicating the performance of the MFP 50, and is, for example, information in a structure format. The capability information 42 stores the items of "original size", "resolution", "color setting", "reading format", "file format", and "ADF tilt correction" as items related to the scan operation. "Original size" is information indicating the read range of the original when the MFP 50 executes the scan operation. 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 operation is executed. "Color setting" is information setting the presence or absence of color in the scan data when the MFP 50 executes the scan operation, 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 operation. "File format" is information indicating the file format (JPEG, TIFE) of the scan data when the MFP 50 executes the scan operation. "ADF tilt correction" is information that indicates whether or not to correct the tilt of the read image when reading a document set in the ADF. Note that the items of capability information 42 may also include items of "brightness," "contrast," and "blank page removal."

[0021] Next, a description will be given of the hardware configuration of the server 30. The server 30 includes a bus 31, a server-side CPU 32, a user IF 33, a communication IF 34, and a memory 35. The components constituting the server 30 are connected via the bus 31 so as to be able to communicate with each other.

[0022] 2 is stored in the data storage area of ​​the memory 35. The job management table 40 is information about scan data uploaded to the server 30 by execution of a push scan process. The job management table 40 will be described later.

[0023] 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 16, and a memory 17. These components are capable of communicating with each other via the bus 11.

[0024] The user IF 13 includes a touch panel 14 and an operation key 15. The touch panel 14 has a touch sensor and outputs a signal according to the detection result by the touch sensor. In this embodiment, "touch" includes the general operation of bringing an input medium into contact with the display screen of the touch panel 14. Specifically, a tap operation in which the touched input medium is separated from the touch panel 14 within a predetermined time will be described as an example of touch, but a long touch operation, a slide operation, a flick operation, a pinch-in operation, a pinch-out operation, etc. may also be used. In addition, bringing the input medium close to a position where the distance between the input medium and the touch panel 14 is very small may be included in the concept of "touch" described above. Furthermore, the input medium may be a user's finger or a touch pen, etc.

[0025] The communication IF 16 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 16 may perform short-distance wireless communication with the MFP 50 using Bluetooth (registered trademark) or the like, or may perform wireless communication using a mobile communication system via a base station.

[0026] The terminal CPU 12 controls each unit of the terminal 10 by executing a program stored in the memory 17. In this embodiment, the terminal CPU 12 is an example of a controller.

[0027] The memory 17 stores an OS 20 (Operating System) and a control program 21. In the following, the CPU that executes the program may be described simply as the program name. For example, the description "the control program 21" may mean "the terminal side CPU 12 that executes the control program 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 represent 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 control program 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. 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 control program 21 to use the functions of the OS 20, to communicate with the server 30 and the MFP 50, and to use the functions of other programs. The control program 21, using the functions of the OS 20, causes the MFP 50 that can be connected via the communication IF 16 to execute a print operation, a scan operation, a FAX operation, etc. In addition, when a push scan process is executed by the MFP 50, the control program 21 can execute a process for downloading the scan data uploaded to the server 30.

[0030] Next, a registration process executed between the terminal 10, the server 30, and the MFP 50 will be described with reference to Fig. 3. The registration process is a process for causing the server 30 and the MFP 50 to register destination candidates for scan data created by the push scan process. Of the processes shown in Fig. 3, the processes executed by the terminal 10 are executed by the control program 21. Note that the processes executed between the terminal 10 and the MFP 50 are performed by local communication such as Wi-Fi or short-range wireless communication.

[0031] In step S10 (hereinafter simply referred to as S10), the terminal side CPU 12 (control program 21) displays a registration screen on the user IF 13 and accepts the user's input operation of registration information via the user IF 13. The registration screen is a screen for registering the terminal 10 in the destination information 41 of the MFP 50 in response to the user's operation. For example, the registration screen accepts the selection of the device to be registered as the registration destination and the input of a "display name" to be registered in the destination information 41. The "program ID" is automatically set by the control program 21.

[0032] In S11, the control program 21 transmits the items set in S10 together with a registration request to the MFP 50 selected as the registration destination. In S12, the controller 57 of the MFP 50 performs a registration process to store the items transmitted from the terminal 10 in the destination information 41. As a result, the MFP 50 registers the terminal 10 as a destination candidate. In S13, the controller 57 transmits the items registered in S12 and the identification information of the MFP 50 together with a registration request to the server 30.

[0033] In S14, the server-side CPU 32 stores the items transmitted from the MFP 50 in the memory 35, thereby storing destination information 41 related to the terminal 10. This enables the server 30 to determine that the terminal 10 has been registered as a destination candidate for the MFP 50. In S15, the server-side CPU 32 sends a completion notification to the MFP 50 indicating that the registration has been completed. In S16, the controller 57 of the MFP 50 sends a completion notification to the terminal 10 indicating that the registration has been completed.

[0034] Next, the process executed among the terminal 10, the server 30, and the MFP 50 when the push scan process is executed will be described with reference to Fig. 4. The process shown in Fig. 4 is started when an operation to instruct the execution of the push scan process is performed on the operation screen displayed on the user IF 56 of the MFP 50. It is also assumed that the terminal 10 has been registered as a destination candidate for the push scan process by the process shown in Fig. 3 prior to the process in Fig. 4.

[0035] In S20, the controller 57 of the MFP 50 displays a destination list on the user IF 56. In the destination list displayed on the user IF 56, display names of destination candidates stored in the destination information 41 are displayed as a list.

[0036] When the user operates the user IF 56 to specify a display name corresponding to the terminal 10 among the display names displayed in the destination list, in S21, the controller 57 causes the user IF 56 to display the scan settings of the MFP 50. In this embodiment, the scan settings displayed in S21 are preset scan settings for the push scan process. For example, each of the setting values ​​of "original size", "resolution", "color setting", "read format", "file format", and "ADF tilt correction" is displayed. Each of the displayed setting values ​​can be changed by the user within the range of the setting values ​​included in the capability information 42. In addition to this, the program ID associated with the display name specified as the destination may be read out, and the scan settings associated with this program ID may be displayed on the user IF 56.

[0037] When the user operates an icon for confirming the execution of push scan processing, in S22, the controller 57 creates scan data, for example, by having the reading unit 54 read the document set on the document platen. Note that, when the user touches an icon for canceling the execution of the scan operation, the controller 57 does not execute the scan operation.

[0038] In S23, the controller 57 transmits the scan data created in S22 to the server 30, specifying the terminal specified by the user (in this embodiment, the terminal 10) as the destination. Specifically, the controller 57 transmits the program ID associated with the display name specified on the destination information 41 to the server 30 together with the scan data created in S22.

[0039] In this embodiment, the scan data includes image data created by reading a document, as well as a thumbnail image, a label name, a model name, an execution date and time, and a data size. The label name is information for identifying the scan data, and is set by the controller 57 when the scan data is created. The model name is the name of the device that executed the push scan process, and in this embodiment, is the model name of the MFP 50. The execution date and time is information indicating the date and time when the push scan process was executed.

[0040] When the server-side CPU 32 of the server 30 receives the scan data transmitted from the MFP 50, in S24 it registers job information in the job management table 40. Specifically, the label name, model name, execution date and time, data size, and thumbnail image contained in the scan data are stored as job information in the job management table 40 in association with the program ID transmitted in S23. As shown in Fig. 2, the job management table 40 stores the thumbnail image, model name, execution date and time, data size, and program ID in association with the label name.

[0041] 4, in S25, the server-side CPU 32 uploads the scan data transmitted from the MFP 50 by storing the scan data in the memory 35. The uploaded scan data is stored in the memory 35 in association with the label name in the job management table 40. Note that the server 30 may upload the scan data by having the scan data stored in another server such as a management server.

[0042] Next, a procedure for a job information acquisition process will be described, in which job information corresponding to the scan data uploaded to the server 30 is acquired by operating the terminal 10. In this embodiment, the control program 21 displays on the user IF 13 a history screen showing the execution status of the scan process based on the acquired job information.

[0043] The control program 21 displays a function selection screen 60 shown in FIG. 5 on the user IF 13 in response to an operation of instructing activation received via the user IF 13. The function selection screen 60 includes a device designation area 61 and a function display area 62. The device designation area 61 is an area in which a device to be controlled is displayed. In the function selection screen 60 shown in FIG. 5, "MFP-0001" is displayed as the model name of the MFP 50 to be controlled. The control program 21 can change the model name displayed in the device designation area 61 in response to an operation received via the user IF 13. The function display area 62 is an area in which icons for receiving instructions regarding the functions of the device designated on the device designation area 61 are displayed. In the function display area 62 shown in FIG. 5, an operation icon 63 for receiving an instruction to execute a "print operation", an operation icon 64 for receiving an instruction to execute a "pull scan process", and an operation icon 65 for receiving an instruction to execute a "copy operation" are displayed for the designated MFP 50. Furthermore, a history display icon 66 for receiving an instruction to display a history screen in a scan operation is displayed in the function display area 62. The history screen will be described later.

[0044] 4, when the control program 21 receives an instruction operation on the history display icon 66 on the function selection screen 60 via the user IF 13, in S26, the control program 21 transmits a request for job information on scan data addressed to the own device to the server 30. Specifically, the control program 21 transmits a program ID to the server 30 together with the request for job information.

[0045] When the server-side CPU 32 receives the program ID together with the request for job information, in S27, it refers to the job management table 40 stored in the memory 35 and reads out the job information associated with the transmitted program ID. If the push scan process is not being executed, the scan data is not uploaded and the job information is not stored. In addition, in this embodiment, the server 30 deletes the job information for the downloaded scan data. Therefore, if the push scan process is executed between the time when the history display icon was displayed last time and the time when the history display icon is displayed this time, the job information is registered in the job management table 40 in the memory 35, so the job information is read out. On the other hand, if the push scan process is not executed between the time when the history display icon was displayed last time and the time when the history display icon is displayed this time, the job information is not registered in the job management table 40, so the job information is not read out.

[0046] In S28, the server-side CPU 32 responds to the request for job information in S26. If the job information has not been read out in S27, the server-side CPU 32 returns a response to the terminal 10 in S28 without transmitting the job information of the scan data addressed to the terminal 10. On the other hand, if the job information has been read out in S27, the terminal 10 transmits the job information of the scan data addressed to the terminal 10 to the terminal 10 in S28. In this embodiment, the process executed by the terminal-side CPU 12 in S26 is an example of a job information acquisition process. If the response to the request in S26 is not received even after a certain period of time has elapsed, the terminal 10 displays a history screen 70 (described later) by adding information indicating a connection error with the server to a display field in which "not downloaded" is stored in the history information (described later).

[0047] When the control program 21 receives the response sent from the server 30, in S29, it performs a process of displaying a history screen 70 shown in Fig. 6. The history screen 70 is a screen that shows the execution status of the push scan process and the pull scan process. The history screen 70 has a display field for displaying information related to the scan data. In this embodiment, the display field is a rectangular area aligned in the height direction. The history screen 70 has a push scan display field 72 in which information related to the scan data created by the push scan process is displayed, and a pull scan display field 73 in which information related to the scan data created by the pull scan process is displayed.

[0048] In the push scan display field 72, a thumbnail image 170, a model name 171, a label name 172, an execution date and time 173, and status information 174 are displayed as history information. The thumbnail image 170, the model name 171, the label name 172, and the execution date and time 173 are job information related to the scan data. The status information 174 is information indicating the status of the push scan process, and in this embodiment, includes information indicating each status of "not downloaded", "downloaded", and "expired". In this embodiment, instead of displaying the status information 174 indicating "downloaded" in the top push scan display field 72, the label name 172 of the downloaded scan data is displayed. In this way, the status information 174 does not have to be a character string that directly indicates the download state of the scan data. In addition, in the second push scan display field 72 from the top, the status information 174 indicating "expired" is displayed. "Expired" indicates that the scan data uploaded to the server 30 was automatically deleted from the server 30 without being downloaded because a predetermined storage period (for example, one week) has passed since the execution date and time of the push scan process. In this case, only the scan data is deleted, and only the job information remains. Also, in the third push scan display field 72 from the top, "Server connection error" is displayed. In addition to the job information and status information, when a "favorite registration" setting is accepted by the user via the user IF 13, the favorite registration may be displayed in the display fields 72 and 73.

[0049] In the pull scan display field 73, a thumbnail image 180, a model name 181, and an execution date and time 182 are displayed as history information. Each of the pieces of information 180, 181, and 182 is similar to the pieces of information 170, 171, and 173 displayed in the push scan display field 72. Status information may be displayed in the pull scan display field 73. In this case, the status information displayed in the pull scan display field 73 may be, for example, the "update date and time" when an additional pull scan is performed after a pull scan has already been performed.

[0050] When the icon 74 is operated on the history screen 70, the control program 21 causes the function selection screen 60 to be displayed on the user IF 13. That is, the screen transition is returned to the previous state.

[0051] 7 is a flow chart for explaining the procedure of the display process executed by the control program 21 in S29. In S40, it is determined whether or not it is necessary to add a push scan display field 72 to the history screen 70. If job information has been acquired in response to the request for job information in S26 and the acquired job information is not job information that has already been acquired, a positive judgment is made in S40 and the process proceeds to S41. This is because, in the case where scan data is stored without being downloaded from the server 30, job information may be acquired multiple times for the same scan data at the timing of displaying the history screen 70. Note that, in S40, if job information has not been acquired in response to the request for job information in S26 or the acquired job information is job information that has already been acquired, a negative judgment is made in S40 and the process proceeds to S42.

[0052] In S41, the newly acquired job information is used to create the push scan display field 72. In this embodiment, data corresponding to the push scan display field 72 is added to the history screen data for displaying the history screen 70. When S41 ends, the process proceeds to S42.

[0053] In S42, it is determined whether or not it is necessary to add a pull scan display field 73 to the history screen 70. If the pull scan display field 73 has not been created among the scan data created in the pull scan process, an affirmative decision is made in S42 and the process proceeds to S43. In S43, the pull scan display field 73 is created using the job information stored in the memory 17. When the process of S43 is completed or a negative decision is made in S42, the process proceeds to S44.

[0054] In S44, the target data for which the status information is to be updated is set among the scan data for which the display fields 72 and 73 have already been created. In this embodiment, the status information is updated for all scan data displayed in the push scan display field 72 and the pull scan display field 73.

[0055] When the control program 21 downloads scan data and job information created by push scan processing from the server 30, and when scan data is created by pull scan processing, the control program 21 saves each piece of data in a dedicated folder and creates history information. The history information includes job information acquired from the server, status information, "Favorite registration" settings, and the creation date and time of the display field. The control program 21 can then determine whether each piece of scan data has been downloaded by referring to the history information. The server-side CPU 32 of the server 30 deletes the job information for the downloaded scan data from the job management table 40.

[0056] In S45, it is determined whether the display columns 72 and 73 are in a display period. In this embodiment, if a predetermined display period has elapsed since the creation date and time of the display columns 72 and 73 included in the history information, a negative determination is made in S45, and the process proceeds to S47. In the case where the target data is scan data created by a pull scan process, the date and time for determining the display period may be the update date and time, which is the date and time of an additional scan described later, in addition to the execution date and time. On the other hand, if a positive determination is made in S45, the process proceeds to S46. Note that the automatic deletion of the display columns 72 and 73 by the terminal side CPU 12 can be set by the settings on the function selection screen 60. In S47, the display columns of the target data included in the history image data are deleted. After the process of S47, the process proceeds to S54.

[0057] In S46, it is determined whether the target data is scan data created by a push scan process. If the result of S46 is negative, that is, if the target data is scan data created by a pull scan process, the process proceeds to S54. On the other hand, if the result of S46 is positive, the process proceeds to S48.

[0058] In S48, it is determined whether the target data has not yet been downloaded from the server 30. In this embodiment, if no job information has been transmitted from the server 30 in response to the current request in S26, and the history information stores that the data has been downloaded or has expired, a negative determination is made in S48, assuming that the data has been downloaded. On the other hand, if job information has been transmitted from the server 30, and the history information does not store that the data has been downloaded or has expired, a positive determination is made in S48, assuming that the data has not yet been downloaded.

[0059] If a negative judgment is made in S48 and the process proceeds to S49, text indicating the status information included in the history information is added to an area in the history screen data corresponding to the push scan display field 72. Specifically, text indicating that the data has been downloaded or that the expiration date has expired is added. Note that, as in this embodiment, the label name of the downloaded scan data may be added instead of the text indicating that the data has been downloaded. When the process of S49 ends, the process proceeds to S54.

[0060] On the other hand, if in S48 the job information has been sent from the server 30 and the history information does not store information indicating that the job has been downloaded or that the validity period has expired, then a positive determination is made and the process proceeds to S50. In S50, "not downloaded" is recorded as status information included in the history information. Then, text indicating that the job has not been downloaded is added as status information to an area in the history image data corresponding to the push scan display field 72. The text "not downloaded" is an example of information indicating that downloading is possible. When the process of S50 ends, the process proceeds to S51.

[0061] In S51, the "execution date and time" in the job information is used to determine whether the storage period has expired. For example, if the storage period for scan data in the server 30 is set to storage period T1, it is determined whether the calculated period, which is the period from the current time to the "execution date and time", is equal to or longer than the storage period T1. In this embodiment, if the calculated period is equal to or longer than the storage period T1 and the storage period has expired, the target data has been deleted from the server 30 and cannot be downloaded from the server 30.

[0062] In S52, it is determined whether the target data can be downloaded. If it is determined in S51 that the calculated period exceeds the storage period, a negative determination is made in S52, the process proceeds to S53, and expiration is recorded as status information included in the history information. Then, text indicating that the scan data cannot be downloaded is added as status information to an area corresponding to the push scan display field 72 in the history image data. In this embodiment, the text "Expired" is added as status information instead of the text "Not downloaded" added to the history screen data in S48. The text "Expired" is an example of information indicating that downloading is not possible. When the process of S53 is completed, the process proceeds to S54. On the other hand, if an affirmative determination is made in S52, the process proceeds to S54.

[0063] In S54, it is determined whether or not the process has been performed on all the target data. If the result of S54 is negative, the process proceeds to S55, where the target data is changed, and the process returns to S45. Then, the process from S45 to S53 is performed on the new target data. If the process from S45 to S53 is repeated, the process proceeds to S56. In S56, the history screen 70 is displayed on the user IF 13 using the updated history screen data. Then, the process of S29 is terminated. The display order of the display columns 72 and 73 in S56 can be changed according to the job information. In this case, the display order of the display columns 72 and 73 may be determined according to the order indicated by any one of the information items "model name", "label name", "execution date and time", and "data size", for example.

[0064] Next, a process executed by the control program 21 by touching the display fields 72 and 73 included in the history screen 70 will be described with reference to Fig. 8. The process shown in Fig. 8 is executed when the history screen 70 is displayed on the user IF 13 of the terminal 10.

[0065] In S60, it is determined whether or not a touch operation has been received on either of the display columns 72 and 73 via the user IF 13. If a negative determination is made in S60, the process waits. If a positive determination is made in S60, the process proceeds to S61, where it is determined whether or not the instruction by the touch operation is for the push scan display column 72.

[0066] If the result of S61 is affirmative, the process proceeds to S62, where it is determined whether the scan data specified by the touch operation has not yet been downloaded. Specifically, if the "status information" associated with the push scan display field 72 indicates "not yet downloaded," the result of S62 is affirmative.

[0067] If an affirmative decision is made in S62, the process proceeds to S63, where a download request for the specified scan data is sent to the server 30. Specifically, a label name for identifying the scan data and a program ID for identifying the own device are sent together with the download request. The label name is job information associated with the push scan display field 72 that has been touched. In this embodiment, the process executed by the terminal side CPU 12 in S63 is an example of a data acquisition process.

[0068] In S64, it is determined whether the specified scan data has been downloaded from the server 30. If a negative determination is made in S64, the process proceeds to S65, where it is determined whether the download is in an error state. The download error state may be a "connection error" caused by an inability to connect to the server 30, or a "download error" indicating that the scan data has already been deleted on the server side. In addition, if authentication such as a token is required for communication between the terminal 10 and the server 30, the unsuccessful authentication may be determined as an error state. If a positive determination is made in S65, the process proceeds to S66, where an error state is displayed in the push scan display field 72. On the other hand, if a negative determination is made in S65, the process returns to S64. If the specified scan data has been received from the server 30, a positive determination is made in S64, and the process proceeds to S67.

[0069] When the server-side CPU 32 of the server 30 receives a download request from the terminal 10, it identifies the scan data to be downloaded from the job management table 40 using the label name and the program ID, and transmits the identified scan data and job information to the terminal 10. As a result, the scan data specified by the touch operation is downloaded to the terminal 10.

[0070] In S67, when the scan data and job information are received, the status information of the downloaded scan data is changed to "downloaded." As a result, in the subsequent processing, when the control program 21 requests acquisition of job information in S26, "downloaded" is displayed as the status information on the history screen displayed in S29. When the processing of S67 is completed, the process proceeds to S68.

[0071] In S68, the first preview screen is displayed on the user IF 13. The first preview screen is a preview screen for scan data created by the push scan process. As shown in FIG. 9, the first preview screen 80 includes a preview area 81 in which downloaded scan data is displayed. The preview area 81 displays a scanned image scanned in one push scan process (i.e., one job). For example, when multiple documents are scanned in one push scan process, the preview area 81 displays scanned images corresponding to the multiple documents. Note that, in FIG. 9, three scanned images can be displayed in the preview area 81. The user can switch the display of the scanned image by scrolling the preview area 81.

[0072] When the operation icon 82 is operated on the first preview screen 80, the control program 21 causes the user IF 13 to display the function selection screen 60. When the operation icon 83 is operated on the first preview screen 80, the control program 21 causes the user IF 13 to display the history screen 70. The display format of the scanned images on the eleventh preview screen 80 may be other than that shown in FIG. 9, and may be a format in which a list of multiple scanned images is displayed.

[0073] On the other hand, if a negative judgment is made in S62, the scan data specified by the touch operation has already been downloaded to the terminal 10, so the process proceeds to S68, where the first preview screen 80 for the scan data specified by the touch operation is displayed. Even in this case, the first preview screen 80 shown in Fig. 9 is displayed on the user IF 13. When the process of S68 ends, the process shown in Fig. 8 ends.

[0074] Returning to S61, if the touch operation is performed on the pull scan display field 73, the control program 21 proceeds to S69. In S69, the second preview screen is displayed on the user IF 13. The second preview screen is a preview screen of the scan data created by the pull scan process. The second preview screen, like the first preview screen 80, includes a preview area in which the downloaded scan data is displayed. Meanwhile, unlike the first preview screen, the second preview screen includes a scan instruction icon that accepts additional scanning of the document. When an instruction operation on the scan instruction icon is accepted via the user IF 13, the control program 21 causes the user IF 13 to display an execution instruction screen 90 shown in FIG. 10.

[0075] As shown in FIG. 10, the execution instruction screen 90 is a screen for receiving an execution instruction for additional scanning. The execution instruction screen 90 includes a cancel operation receiving area 91, a scan setting area 92, and an execution operation receiving area 93. The cancel operation receiving area 91 is an area for receiving a cancellation of the execution of additional scanning. The execution operation receiving area 93 is an area for receiving the execution of additional scanning. The scan setting area 92 is an area for receiving a change operation of the scan setting in the additional scanning. In FIG. 10, the scan setting area 92 includes an area 95 illustrating the setting direction of the document relative to the MFP 50, an area 96 for receiving a change operation of the "color setting", an area 97 for receiving a change operation of the "document size", an area 98 for receiving a change operation of the "reading format", and an area 99 for receiving a change operation of the "resolution". Each scan setting can be changed within the range stored in the capability information. The scan setting area 92 may include an area for receiving a change of each setting value of the "file format" and the "ADF tilt correction". When the process of S69 is completed, the process of FIG. 8 is completed.

[0076] The present embodiment described above can provide the following advantages. The terminal side CPU 12 of the terminal 10 acquires job information for a push scan process in which the terminal itself is the destination of scan data from the server via the communication IF 16, and based on the acquired job information, displays the execution status of the push scan process on the user IF 13. This allows the user to grasp the execution status of the push scan process by viewing the terminal 10, thereby improving user convenience.

[0077] The server 30 stores scan data in association with a program ID, and the terminal-side CPU 12 transmits a request to obtain job information corresponding to the program ID to the server 30 via the communication IF 16, thereby obtaining job information for scan data addressed to the terminal from the server 30. This makes it possible to obtain job information for scan data addressed to the terminal even in a configuration in which multiple terminals can access the server 30.

[0078] The terminal side CPU 12 acquires job information upon receiving an instruction operation to display the history screen 70 via the user IF 13. As a result, the job information is acquired from the server 30 every time the history screen 70 is displayed on the terminal 10, so that the execution status of the push scan process can be displayed on the terminal 10 in real time in accordance with the timing at which the user views the history screen 70.

[0079] When the terminal side CPU 12 cannot acquire the job information, it determines that the scan data has already been downloaded, and displays the download status of the scan data on the user IF 13 according to the determination result. This allows the user to know whether the scan data has already been downloaded from the display on the terminal 10.

[0080] When the terminal-side CPU 12 receives an instruction to download scan data that is displayed as not yet downloaded on the history screen 70, the terminal-side CPU 12 transmits a download request for the scan data that has been instructed to the server 30. This allows the download of the scan data to be started by an operation on the history screen 70.

[0081] The terminal side CPU 12 judges whether or not the scan data can be downloaded based on the execution date and time of the push scan process and the storage period of the scan data, and displays the judgment result as an execution status on the user IF 13. This allows the user to know on the history screen 70 whether or not the scan data can be downloaded.

[0082] The terminal side CPU 12 does not display the execution status of scan data that has already been displayed on the history screen 70 and whose execution date and time is longer than a predetermined period from the present time, thereby improving user convenience.

[0083] The terminal side CPU 12 displays the execution status of the pull scan process on the user IF 13 based on the job information in the pull scan process in addition to the execution status of the push scan process. This allows the execution status to be displayed for the scan data created in the pull scan process executed between the terminal 10 and the MFP 50.

[0084] (Modification of the first embodiment) In the first embodiment, the history screen 70 displays the push scan display field 72 and the pull scan display field 73. Alternatively, the history screen 70 may display only the push scan display field 72.

[0085] In the first embodiment, the terminal CPU 12 requests job information for scan data addressed to the own device using the program ID in S26 of Fig. 4. Alternatively, the terminal CPU 12 may request job information for scan data addressed to the own device using identification information other than the program ID, such as the serial number of the device, in S26. In this case, it is sufficient that identification information other than the program ID is registered in the destination information 41.

[0086] In S29, the terminal-side CPU 12 may display "downloading" as the status information in addition to "not downloaded", "downloaded", and "expired". In this case, when the push scan display field 72 is operated to start downloading, the status information "downloading" may be displayed in the push scan display field 72.

[0087] 7, the terminal-side CPU 12 may determine whether to delete the display columns 72, 73 according to the data size of the scan data in addition to whether the display period has elapsed. In this case, for example, the display columns 72, 73 may be deleted when the execution date and time exceeds the display period and the data size is equal to or greater than a size judgment value. Also, instead of determining whether a predetermined display period has elapsed, the display columns 72, 73 may be deleted when the number of display columns is equal to or greater than a predetermined number.

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

[0089] In the second embodiment, when scan data is uploaded by push scan processing, the server 30 notifies the terminal 10 of a push notification. As an example of a mechanism for providing a push notification service, APNS (Apple Push Notification Service) or GCM (Google Cloud Messaging for Android) can be used. In this embodiment, when using an APNS or GCM service, it is assumed that the server 30 has already registered an address or the like indicating the location of the terminal 10 that uses the service. In addition, the push notification is a notification according to the APNS or GCM protocol.

[0090] Next, the process executed among the terminal 10, the server 30, and the MFP 50 when executing the push scan process according to the present embodiment will be described with reference to Fig. 11. In S25, the server-side CPU 32 uploads the scan data transmitted from the MFP 50 by storing the scan data in the memory 35. The uploaded scan data is saved in the memory 35 in association with the label name in the job management table 40.

[0091] In S70, the server-side CPU 32 transmits a push notification using the APNS or GCM service to the terminal 10. In this embodiment, the push notification transmitted in S70 includes job information related to scan data addressed to the terminal 10. For example, upon receiving the push notification, the control program 21 stores the job information included in the push notification in the memory 17 in S71.

[0092] When the control program 21 receives the push notification transmitted from the server 30 in S70, the control program 21 may transmit a request to obtain job information to the server 30. In this case, the program ID may be transmitted together with the request to obtain job information.

[0093] Thereafter, when an instruction operation for the history display icon 66 is accepted on the function selection screen 60 via the user IF 13, in S72, a display process for the history screen 70 is performed using the job information saved in S71. In this embodiment, the display process for the history screen 70 performed in S72 is similar to the process performed in S29 in the first embodiment.

[0094] The above-described embodiment can achieve the following effects. When scan data is uploaded by push scan processing, the server 30 transmits a push notification to the terminal 10. Upon receiving the push notification, the terminal-side CPU 12 acquires job information from the server 30. This makes it possible to acquire job information in real time at the timing when the scan data is uploaded.

[0095] The terminal side CPU 12 acquires job information included in the push notification received from the server 30, and uses the acquired job information to display the history screen 70. This makes it possible to reduce the number of communications between the terminal and the server 30 each time scan data is uploaded to the server 30, and thus to suppress an increase in the processing load on the terminal.

[0096] (Modification of the second embodiment) In the above-described second embodiment, the server 30 transmits a push notification to the terminal 10 in S70 of Fig. 11. Alternatively, the MFP 50 may transmit a push notification to the terminal 10. In this case, the controller 57 of the MFP 50 transmits the scan data to the server 30 in S23 of Fig. 11, and then transmits a push notification including job information to the terminal 10. Also, the process of S70 may be deleted.

[0097] (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. The MFP 50 has been described as a scanner only as an example, and the scanner may be a device that only has a scanning operation.

[0098] In the above-described embodiments, the execution status of the push scan process is displayed on the history screen. However, instead of this, the execution status of the push scan process may be displayed on a screen other than the history screen. [Explanation of symbols]

[0099] 10: terminal, 12: terminal side CPU, 13: user IF, 30: server, 50: MFP, job management table 40

Claims

1. A control program executable by a controller of a terminal having a communication interface and a user interface, The control program includes: causing the controller to execute a data acquisition process for acquiring scan data created by a push scan process of a scanner from a server via the communication interface, the push scan process being a process for causing the scanner to create the scan data and upload the created scan data to the server; The controller, a job information acquisition process for acquiring, via the communication interface, job information in the push scan process in which the device itself is a destination of the scan data; a display process for displaying an execution status of the push scan process on the user interface based on the job information; the server stores the scan data in association with identification information for identifying the control program or the terminal; In the job information acquisition process, a control program acquires the job information addressed to the device from the server by sending a request to acquire the job information including the identification information to the server via the communication interface.

2. A control program executable by a controller of a terminal having a communication interface and a user interface, The control program includes: causing the controller to execute a data acquisition process for acquiring scan data created by a push scan process of a scanner from a server via the communication interface, the push scan process being a process for causing the scanner to create the scan data and upload the created scan data to the server; The controller, a job information acquisition process for acquiring, via the communication interface, job information in the push scan process in which the device itself is a destination of the scan data; a display process for displaying an execution status of the push scan process on the user interface based on the job information; A control program for displaying, as the execution status, a history screen of the push scan process on the user interface based on the job information in the display process.

3. The control program according to claim 2 , wherein the job information acquisition process is executed when an instruction operation for displaying the history screen is accepted via the user interface.

4. When the scan data is uploaded by the push scan process, the server or the scanner transmits a push notification to the terminal; 4. The control program according to claim 1, wherein in the job information acquisition process, the job information is acquired from the server upon receipt of the push notification.

5. When the scan data is uploaded by the push scan process, the server or the scanner transmits a push notification including the job information to the terminal; 4. The control program according to claim 1, wherein the job information acquisition process acquires the job information included in the received push notification.

6. A control program executable by a controller of a terminal having a communication interface and a user interface, The control program includes: causing the controller to execute a data acquisition process for acquiring scan data created by a push scan process of a scanner from a server via the communication interface, the push scan process being a process for causing the scanner to create the scan data and upload the created scan data to the server; The controller, a job information acquisition process for acquiring, via the communication interface, job information in the push scan process in which the device itself is a destination of the scan data; a display process for displaying an execution status of the push scan process on the user interface based on the job information; In the display process, a control program determines that the scan data has already been downloaded based on at least one condition that the job information cannot be acquired by the job information acquisition process, and displays whether or not the scan data has been downloaded as the execution status on the user interface depending on the judgment result.

7. The control program according to claim 6, wherein when the control program receives a download instruction operation for scan data that is displayed as not downloaded as the execution status on the controller, the control program causes the controller to send a download request for the scan data that has been subjected to the instruction operation to the server.

8. The control program according to claim 6 or 7, wherein when an instruction operation is performed on scan data that is displayed in the controller as being downloaded as the execution status, the control program causes the user interface to display a preview screen of the scan data that has been subjected to the instruction operation.

9. A control program executable by a controller of a terminal having a communication interface and a user interface, The control program includes: causing the controller to execute a data acquisition process for acquiring scan data created by a push scan process of a scanner from a server via the communication interface, the push scan process being a process for causing the scanner to create the scan data and upload the created scan data to the server; The controller, a job information acquisition process for acquiring, via the communication interface, job information in the push scan process in which the device itself is a destination of the scan data; a display process for displaying an execution status of the push scan process on the user interface based on the job information; The uploaded scan data has a storage period set, The job information includes an execution date and time of the push scan process, In the display process, a control program determines whether or not the scan data can be downloaded based on the execution date and time of the push scan process and the storage period of the scan data, and displays the determination result as the execution status on the user interface.

10. A control program executable by a controller of a terminal having a communication interface and a user interface, The control program includes: causing the controller to execute a data acquisition process for acquiring scan data created by a push scan process of a scanner from a server via the communication interface, the push scan process being a process for causing the scanner to create the scan data and upload the created scan data to the server; The controller, a job information acquisition process for acquiring, via the communication interface, job information in the push scan process in which the device itself is a destination of the scan data; a display process for displaying an execution status of the push scan process on the user interface based on the job information; The job information includes an execution date and time of the push scan process, The control program is a control program that does not display the execution status of scan data for which the execution status has already been displayed on the controller, where the period from the present to the execution date and time is greater than or equal to a predetermined period.

11. the terminal is capable of causing the scanner to execute a pull scan process by transmitting an execution request to the scanner via the communication interface, and storing the scan data created by the pull scan process; A control program according to any one of claims 1 to 10, wherein the display process displays the execution status of the pull scan process on the user interface based on job information in the pull scan process in addition to the execution status of the push scan process.

12. A terminal comprising a communication interface, a user interface, and a controller, the controller executes a data acquisition process to acquire scan data created by a push scan process of a scanner from a server via the communication interface, the push scan process being a process of causing the scanner to create the scan data and uploading the created scan data to the server; The controller, a job information acquisition process for acquiring, via the communication interface, job information in the push scan process in which the device itself is a destination of the scan data; a display process for displaying an execution status of the push scan process on the user interface based on the acquired job information; the server stores the scan data in association with identification information for identifying the terminal; In the job information acquisition process, the terminal transmits a request to acquire the job information, including the identification information, to the server via the communication interface, thereby acquiring the job information addressed to the terminal from the server.

Images