Image reader
The image reading device addresses high hardware and operational complexities by managing sessions and preventing timeouts, enhancing usability and efficiency in networked environments.
Patent Information
- Application Number
- JP2023082474
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-05-18
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2039-04-10
AI Technical Summary
Existing image reading devices connected via networks require high hardware configuration, complex operations, and frequent IP address input, especially when accessed through web browsers, leading to inefficiencies and increased costs.
An image reading device that manages sessions without installing drivers, allows multiple users to access without administrative privileges, and prevents timeouts during errors, using session management and exclusive control to streamline operations.
Reduces hardware costs, simplifies user interactions, and ensures seamless scanning operations even during errors, allowing users to complete tasks without waiting for session timeouts.
Smart Images

Figure 0007595703000001 
Figure 0007595703000002 
Figure 0007595703000003
Abstract
Description
[Technical field]
[0001] The present invention relates to an image reading device for reading and processing the contents printed on a document. [Background technology]
[0002] In order to read the contents printed on a document and convert them into image data, an image reading device is generally connected to a personal computer (PC) that controls it via USB or the like. In such cases, the general method of use is to install software and a driver that controls the image reading device on the PC. However, in the case of a PC equipped with a general operating system, administrative authority for the PC is required to install software. Even if a user has administrative authority for the PC, if the user uses multiple image reading devices, it is necessary to install drivers for each device, which is cumbersome.
[0003] In recent years, with the development of networks, the number of image reading devices that can be directly connected to a network is increasing, and some of these image reading devices can be accessed from a web browser on a PC or the like. Patent Document 1 discloses a technique for using an image reading device by using a web browser running on a PC in a configuration in which the image reading device and the PC are connected via a network.
[0004] Image scanning devices connected to a network are often used by multiple users. In order to restrict simultaneous use by multiple users, it is common for such image scanning devices to be granted usage rights only to the one PC currently in use, with exclusive control over requests from other PCs. When a scan is completed, usage rights are granted to the next PC that makes a scan request, and the device is controlled to receive requests from that PC. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2005-45437 A Summary of the Invention [Problem to be solved by the invention]
[0006] However, when reading images via a web browser as in Patent Document 1, all image processing must be performed on the image reading device itself, which results in expensive hardware requirements for the image reading device and long processing times. In addition, each time an image reading device is used, the user must input the IP address of the image reading device into the web browser. Furthermore, in order to obtain authorization to use the image reading device, the user may need to re-enter the IP address of the image reading device multiple times. In addition, when obtaining authorization to use the image reading device, the image reading device may request the user to perform additional operations, which is cumbersome.
[0007] The present invention has been made to solve the above problems, and aims to provide a mechanism that allows even a user who is not granted special management authority over an information processing device to control an image reading device from the information processing device and read a document without the need for cumbersome operations such as re-entering an IP address or additional operations for obtaining usage authority, while keeping the required hardware configuration of the image reading device low-cost. [Means for solving the problem]
[0008] The present invention is an image reading device for reading an image from a document, a first session management means for managing first session information for performing an operation of the image reading device that does not involve image reading processing, and enabling the image reading device to be operated via a network based on the first session information; In response to a request from an information processing device capable of communicating via a network, the image reading device can be read without installing a driver for operating the image reading device. Image reading In addition to processing, Image reading If processing is in progress, it accepts requests from other information processing devices. First, the image reading process of the image reading device is monopolized. A control means for performing exclusive control; before For the exclusive control described above Second Managing session information Second a session management unit, Second The exclusive control is released when a predetermined time has elapsed since the session information was created, and when an error occurs in reading the image, Second The present invention is characterized in that the exclusive control is maintained even after the predetermined time has elapsed since the session information was created. Effect of the Invention
[0009] According to the present invention, when controlling an image reading device from a web browser of an information processing device, even if an error such as a jam occurs during scanning and the scanning is terminated, a timeout is prevented and the user can complete the scanning operation. [Brief description of the drawings]
[0010] [Figure 1] 1 is a diagram showing an example of a schematic configuration of an image reading apparatus according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a diagram showing an example of a schematic configuration of an image reading unit. [Diagram 3] FIG. 2 is a diagram showing an example of a control configuration of the image reading apparatus. [Figure 4] FIG. 2 is a diagram showing an example of a schematic configuration of a document detection sensor. [Diagram 5] 10 is a flowchart showing an example of a control process for document detection. [Figure 6] FIG. 11 is a sequence diagram for explaining a process for enabling a user to download a scan application from the image reading device to a PC. [Figure 7] 11 is a diagram showing an example of a screen obtained when a user operates a web browser running on a PC to make a screen request to an image reading device. [Figure 8] 11 is a diagram showing an example of a screen obtained when a user operates a web browser running on a PC to make a screen request to an image reading device. [Figure 9] FIG. 4 is a diagram showing an example of the configuration of a download file. [Figure 10] FIG. 13 is a diagram showing an example of a description of a device configuration. [Figure 11] 6 is a flowchart illustrating the startup of a scan application in a PC. [Figure 12] FIG. 4 is a diagram showing an example of a scan application screen. [Figure 13] FIG. 4 is a sequence diagram illustrating an operation of a scan application. [Figure 14] FIG. 11 is a sequence diagram illustrating a scan session ID acquisition process. [Figure 15] 5A and 5B are diagrams for explaining error detection in the image reading device. [Figure 16] 10 is a flowchart showing an example of processing of a task for managing a scan session ID in an image reading device. [Figure 17] FIG. 2 is a diagram showing an example of a connection configuration of an image reading device. [Figure 18] FIG. 13 is a diagram showing an example of a system configuration according to a third embodiment of the present invention. [Figure 19] FIG. 1 is a diagram explaining the flow of scanning using a mobile terminal. [Figure 20] FIG. 4 is a diagram showing an example of a menu screen displayed on a UI unit of the scanner. [Figure 21] FIG. 4 is a diagram showing an example of a URL display screen displayed on a UI unit of the scanner. [Figure 22] FIG. 13 is a diagram showing an example of a scan setting screen displayed on a UI unit of the mobile terminal according to the third embodiment. [Figure 23] FIG. 13 is a diagram showing an example of a scanning screen displayed on a UI unit of the mobile terminal. [Figure 24] FIG. 13 is a diagram showing an example of a scanning screen displayed on a UI unit of the mobile terminal. [Diagram 25] FIG. 13 is a diagram showing an example of a screen in use by other users that is displayed on a UI unit of the mobile terminal. [Figure 26] 13 is a flowchart showing an example of a process for ending a web application mode in the third embodiment. [Figure 27] FIG. 13 is a diagram showing an example of a termination confirmation screen displayed on a UI unit of the scanner according to the third embodiment. [Figure 28] FIG. 13 is a diagram showing an example of a scan setting screen displayed on a UI unit of the mobile terminal according to the fourth embodiment. [Figure 29] FIG. 13 is a diagram showing an example of a passcode input screen displayed on a UI unit of the scanner according to the fourth embodiment. [Diagram 30] FIG. 13 is a diagram showing an example of a passcode input screen displayed on a UI unit of the scanner according to the fourth embodiment. [Diagram 31] 13 is a flowchart showing an example of a process for ending a web application mode in the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] [First embodiment] Hereinafter, exemplary embodiments of the present invention will be described with reference to the drawings. Note that the following embodiments are merely examples, and the present invention is not limited to the contents of each embodiment. In addition, in the following drawings, explanations of components that are not necessary for the explanation of the embodiments will be omitted.
[0012] FIG. 1 is a diagram showing an example of a schematic configuration of an image reading device 100 according to an embodiment of the present invention. An original table 102 holds and stores an original 101 to be read. The documents on the document table 102 are detected by a document table document detection sensor 110, and are separated one by one by a paper feed roller 106 and sent to a transport path 108. The documents fed by the paper feed roller 106 are transported along the transport path 108 by a transport roller 107 and discharged to a discharge section 103. Note that the paper feed roller 106 may be composed of a pickup roller, and a separation feed section in which a feed roller and a separation roller provided downstream of the pickup roller are arranged to face each other. The discharge section 103 stores and stacks the originals 101 after the image reading process has been completed. The discharge section original detection sensor 111 detects the presence or absence of discharged originals stacked and stored in the discharge section 103 .
[0013] The registration sensor 109 detects the original 101 being transported along the transport path 108. When the registration sensor 109 detects the original 101, the image reading unit 104 starts reading the image formed on the original. In this embodiment, two image reading units 104 are provided on both sides of the transport path 108, one reading the front side of the original 101 and the other reading the back side of the original 101. Note that a configuration may be provided with only one image reading unit 104. A background plate 105 is provided at a position facing each image reading unit 104. The background plate 105 is, for example, a black member. The paper discharge port sensor 112 detects whether the original 101 remains in the transport path 108 or has been discharged to the discharge section 103 .
[0014] FIG. 2 is a diagram showing an example of a schematic configuration of the image reading unit 104. As shown in FIG. The inside of the image reading unit 104 is sealed by a housing 1041 and a glass plate 1042 provided facing the transport path .
[0015] Inside the image reading unit 104, a line image sensor 1043 and a pair of light emitting parts 1044a and 1044b are provided. The line image sensor 1043 extends in a direction (main scanning direction) perpendicular to the transport direction of the original 101, and reads one line of image in the main scanning direction at a time. The line image sensor 1043 is, for example, a CCD line sensor or a contact image sensor.
[0016] The light emitting unit 1044a is disposed upstream of the line image sensor 1043 in the transport direction of the original 101, and has a light source that emits visible light. The light emitting unit 1044b has a light source that is disposed downstream of the line image sensor 1043 in the transport direction.
[0017] The line image sensor 1043 is disposed so as to be sandwiched between a pair of light emitting parts 1044a and 1044b. Each of the pair of light emitting parts 1044a and 1044b extends substantially parallel to the line image sensor 1043, and is configured, for example, by an LED array made up of a plurality of LEDs. The line image sensor 1043 receives and detects light that is irradiated by the light emitting elements 1044a and 1044b and reflected by the original 101, as indicated by the dashed arrow in FIG.
[0018] FIG. 3 is a diagram showing an example of a control configuration of the image reading device 100. As shown in FIG. The control unit 10 of the image reading device 100 includes a CPU 11 , a ROM 12 , a RAM 13 , an input / output I / F 14 , and a communication I / F 15 .
[0019] The CPU 11 executes a program stored in the ROM 12 and controls the entire image reading device 100. The ROM 12 stores programs executed by the CPU 11 and fixed data. The RAM 13 stores variable data such as image data read by the line image sensor 1043 and calculation results of the CPU 11. The ROM 12 and the RAM 13 may be other storage devices.
[0020] A drive circuit 24 that drives the light emitting units 1044a and 1044b and an image processing circuit 26 that performs image processing such as shading correction on the image read by the line image sensor 1043 are connected to the input / output I / F 14. The ADC 25 is an analog-to-digital converter that converts the analog image signal output by the line image sensor 1043 into digital image data. The CPU 11 acquires image data output from the image processing circuit 26 via the input / output I / F 14 .
[0021] The communication I / F 15 is an interface for connecting to a personal computer (PC) 200. For example, image data read by the image reading device 100 is output to the PC 200 via the communication I / F 15. The communication I / F 15 includes a network interface, and as shown in Fig. 17 described later, the image reading device 100 is connected to the PC 200 via a network so as to be able to communicate with each other.
[0022] In addition, a light emitting unit drive circuit 123 and an analog-to-digital converter (ADC) 124 are also connected to the control unit 10. The light emitting section drive circuit 123 drives the document detection light emitting section 121. The document detection light emitting section 121 constitutes the document platen document detection sensor 110 and the discharge section document detection sensor 111. The ADC 124 converts the analog signal received by the document detection light receiving unit 122 into digital data.
[0023] Next, the process executed by the image reading device 100 will be described. The image reading device 100 starts reading the original 101 when a user issues an instruction to start reading via, for example, the PC 200. The CPU 11 first drives the paper feed roller 106 to start conveying the original 101. When the registration sensor 109 detects that the original 101 has reached the reading position of the image reading unit 104, the CPU 11 controls the emission of the light emitting portion 1044a and the light emitting portion 1044b, and drives the line image sensor 1043 to read the image of the original 101.
[0024] FIG. 4 is a diagram showing an example of a schematic configuration of document detection sensors such as document platen document detection sensor 110 and discharge section document detection sensor 111. As shown in FIG. In the document detection sensors such as the document platen document detection sensor 110 and the discharge section document detection sensor 111, the document detection light emitting unit 121 is a light emitting unit such as an LED. The document detection light emitting unit 121 turns on and off under the control of the CPU 11. The document detection light receiving unit 122 is a light receiving body including a condenser lens. The document detection light receiving unit 122 photoelectrically converts the received light and outputs it to the CPU 11 via the ADC 124. The document detection process will be described in detail below with reference to the flowchart of FIG.
[0025] 5 is a flowchart showing an example of a control process for document detection executed by the CPU 11. The process of this flowchart is realized by the CPU 11 reading out and executing a program stored in the ROM 12.
[0026] First, the CPU 11 causes the document detection light-emitting unit (LED) 121 to emit light (S501). The CPU 11 also operates the light-receiving A / D converter (S502), waits a predetermined A / D conversion time (S503), and obtains the amount of light received by the document detection light-receiving unit 122 (S504). The value obtained here is designated as V1.
[0027] Next, the CPU 11 turns off the document detection light emitting unit (LED) 121 (S505). The CPU 11 also operates the light receiving A / D converter (S506), waits for a predetermined A / D conversion time (S507), and obtains the amount of light received by the document detection light receiving unit 122 (S508). The value obtained here is designated as V2.
[0028] Next, CPU 11 judges whether or not there is a document based on the formula "|V2-V1|>S" (S509). If |V2-V1|>S (Yes in S509), CPU 11 judges the state as shown in FIG. 4(a) and judges the state as "document present (paper present)." On the other hand, if |V2-V1|≦S (No in S509), CPU 11 judges the state as shown in FIG. 4(b) and judges the state as "no document present (paper absent)."
[0029] FIG. 17 is a conceptual diagram showing an example of a connection form of the image reading device 100, in which the image reading device 100 is connected to a network environment, a Local Area Network (LAN). 17, when connected to a LAN 300, the image reading device 100 can be used by a plurality of host computers (PC 200a to PC 200n). When there is no need to distinguish between the PC 200a to PC 200n, they will be referred to as PC 200.
[0030] Hereinafter, a process in which the user downloads a scan application from the image reading device 100 to the PC 200 will be described with reference to FIGS. 6 is a sequence diagram for explaining the process until the user is able to download a scan application from the image reading device 100 to the PC 200. In this sequence diagram, the process of the PC 200 is realized by the CPU of the PC 200 executing a web browser program stored in a HDD or the like. Also, the process of the image reading device 100 is realized by the CPU 11 executing a program stored in the ROM 12.
[0031] 7 and 8 are diagrams showing examples of screens obtained when a user operates a web browser running on the PC 200 to make a screen request to the image reading device 100. In this embodiment, screen requests, scan commands, and image data requests from the PC 200 to the image reading device 100 are all implemented by the HTTP protocol using the network port 80, but the present invention is not limited to this.
[0032] Furthermore, the image reading device 100 of this embodiment is connected to the network using a fixed IP address. This IP address is device-specific data stored in advance in ROM 12, and is notified to the user, for example, by being affixed to the exterior (not shown) of the image reading device 100. The user can connect to the image reading device 100 using this IP address. Note that the IP address of the image reading device 100 is changeable, and may be automatically acquired by a method such as DHCP.
[0033] As shown in FIG. 6, first, a user operates PC 200 to establish an http connection from the web browser of PC 200 to image reading device 100 (S601). In this example, the IP address of image reading device 100 is 192.168.0.10. In response, CPU 11 of image reading device 100 instructs the web browser of PC 200 to redirect to a login screen (S602). In response, the web browser of PC 200 accesses the login screen (S603). In response, image reading device 100 transmits a login screen as shown in FIG. 7 to the web browser of PC 200 (S604). Here, image reading device 100 stores the IP address of PC 200 included in the http request header in RAM 13 as the accessing PC. The web browser of the PC 200 that receives the data transmitted in S604 displays a login screen as shown in FIG. 7 based on the received data.
[0034] Thereafter, when the user enters a login name and password on a login screen such as that shown in FIG. 7 and presses the “Login” button, the web browser of PC 200 sends the entered login name and password to image reading device 100 (S605).
[0035] When the login name and password are received, the CPU 11 of the image reading device 100 performs a login process (S606). In this login process, the CPU 11 of the image reading device 100 verifies the login name and password. The login name and password are data held by the device and stored in the ROM 12 in advance, and are notified to the user by, for example, attaching them to the exterior of the image reading device 100 (not shown). If the login name and password verification results in an incorrect login request, the CPU 11 of the image reading device 100 returns to S602 and controls to repeat the process. On the other hand, if the login name and password verification results in a correct login name and password, the CPU 11 of the image reading device 100 generates a session ID and stores it in the RAM 13, and then sets the session ID in a Cookie as well. Here, the image reading device 100 stores the IP address of the PC 200 included in the http request header in the RAM 13 as the login PC. In addition, in the login process executed in S606, the login name and password may be configured to be able to be registered in advance in ROM 12 or another database, and the image reading device 100 may refer to them in S606 to determine whether the login request is valid. Furthermore, the CPU 11 of the image reading device 100 instructs redirection to "webmenu.html" (S607).
[0036] The web browser of PC 200 that receives the instruction in S607 saves the cookie. Then, the web browser of PC 200 accesses "webmenu.html" together with the cookie (S608).
[0037] When the web browser accesses "webmenu.html", the CPU 11 of the image reading device 100 verifies the session ID stored in the RAM 13 in S606 and the session ID included in the Cookie corresponding to the access (S609). Verification using the session ID set in the Cookie is performed for all subsequent Web requests.
[0038] If the verification result shows that the session ID in RAM 13 and the session ID in the Cookie are different, or if the Cookie does not contain a session ID, CPU 11 of image reading device 100 determines that the session ID is incompatible and controls the process to return to S602 and start over. On the other hand, if the verification result shows that the session ID stored in RAM 13 and the session ID in the Cookie are the same, CPU 11 of image reading device 100 determines that the session ID is correct and sends a screen such as that shown in Fig. 8(a) to the web browser of PC 200 (S610). When the web browser of PC 200 receives this, it displays a screen such as that shown in FIG.
[0039] In a text box arranged in an input form 801 on the screen of FIG. 8(a), the IP address of the image reading device 100 is displayed. 8(a) also has a "download" button 802 for downloading a scan application. When the "download" button 802 is pressed, the web browser of PC 200 transmits a download request for the scan application to image reading device 100. In response to this download request for the scan application, CPU 11 of image reading device 100 generates a download file for the scan application as described below and transmits it to PC 200. As a result, a scan application for performing scanning locally (i.e., on PC 200) is downloaded to PC 200. Furthermore, image reading device 100 stores the IP address of PC 200, which is included in the HTTP request header of the download request, in RAM 13 as a download PC. The user can change the IP address of the image reading device to which the scan application is to be downloaded by using the text box and "Change" button arranged in the input form 801.
[0040] When the download of the scan application is completed, a message indicating the completion of the download is displayed in the status bar 803 of the web browser of the PC 200 as shown in Fig. 8(b), and the user can easily start the downloaded application. Note that the download button 802 shown in Fig. 8(a) is only an example, and a button having another function (for example, a scan setting button) may be given the same function.
[0041] Next, the download file of the scan application will be described with reference to FIG. 9 and FIG. FIG. 9 is a diagram showing an example of the configuration of a download file of a scan application generated by the image reading device 100. As shown in FIG.
[0042] 9, a launch application Launcher 901 is located at address 000000h at the beginning of the download file. When generating the download file, the CPU 11 of the image reading device 100 reads out Launcher 901 stored in the ROM 12, which is a non-volatile memory, and adds it to the download file.
[0043] A compressed file 902 is located at the address 001000h following the Launcher 901. The compressed file 902 stores an executable file ScanApplication.exe required for scanning, an image processing engine for performing gamma correction and the like, and device configuration. ScanApplication.exe is an application program that runs on the PC 200 that can communicate via a network and reads an original using the image reading device 100. The image processing engine is composed of various DLLs and the like. In this embodiment, the compressed file 902 is generated in Zip format, but is not limited to this. When generating a download file, the CPU 11 of the image reading device 100 reads out ScanApplication.exe, the image processing engine, and the like stored in the ROM 12 and adds them to the compressed file 902.
[0044] DeviceConfiguration.xml is data written in XML format, as shown in FIG. FIG. 10 is a diagram showing an example of device configuration.xml included in the download file. 10, deviceconfiguration.xml stores various device setting values. For example, in addition to a session ID and a scan session ID indicating exclusive rights regarding scanning, which will be described later, the device name, MAC address, main body IP address, image reading capability value, and other setting values are stored. The device name, MAC address, main body IP address, and the like function as information (specification information) that identifies the image reading device. When generating a download file, the CPU 11 of the image reading device 100 reads the above-mentioned setting values stored in the ROM 12, creates an XML file, and adds it to the compressed file 902.
[0045] As shown in FIG. 9, finally, the CPU 11 of the image reading device 100 adds a signature 903 to the download file by signing it using the digital signature private key stored in the ROM 12, thereby completing the generation of the download file.
[0046] Here, the above-mentioned session ID and scan session ID will be explained. The session ID is an identification ID for operations "not involving scanning" such as checking the setting values of the image reading device 100 using a web browser. Multiple users are permitted to access this "not involving scanning" operation at the same time, and a session ID may be assigned to multiple users at the same time.
[0047] On the other hand, the scan session ID is an identification ID (identification information) for occupying the reading unit of the image reading device 100, and is not assigned to multiple users at the same time. A user who has a scan session ID is the user who is authorized to perform scan operations. In other words, the scan session ID is used to manage a session with a scan application running on the PC 200.
[0048] When the CPU 11 of the image reading device 100 generates a scan session ID, it stores it in the RAM 13, and when scanning is completed, it discards (deletes) the scan session ID in the RAM 13. If a scan session ID has already been stored in the RAM 13, the CPU 11 of the image reading device 100 does not generate a new scan session ID, but transmits a download file with an invalid ID embedded therein to the PC 200. In this embodiment, the session ID and scan session ID are character strings that have been MD5 converted based on the time and MAC address, and the invalid ID is "d41d8cd98f00b204e9800998ecf8427e", but is not limited to this and may include specific character strings and blanks.
[0049] Furthermore, if scanning is not started within a predetermined time period after the scan session ID is issued, the CPU 11 of the image reading device 100 discards the scan session ID from the RAM 13.
[0050] When a scan session ID, which will be described later, is already stored in the RAM 13 when generating a download file, the CPU 11 of the image reading device 100 may display a pop-up message such as "User A is using this file" in the web browser of the PC 200 that has made the download request. This message may also be displayed on the screen shown in FIG. 8(b). In this case, a scan session ID is issued when the download button 802 is pressed. R You may notify the
[0051] The start-up of the scan application in the PC 200 will be described below with reference to FIG. FIG. 11 is a flowchart for explaining the launch of a scan application in PC 200. In a typical web browser, when a download is complete, a message is displayed in status bar 803 in FIG. 8(b) that prompts the user to launch or save the downloaded file. The same is true for the web browser of PC 200. When a user launches a downloaded file from status bar 803 or the like, the web browser of PC 200 launches Launcher 901 shown in FIG. 9. The processing of the flowchart in FIG. 11 is realized by the CPU of PC 200 executing Launcher 901. Below, the processing performed by the web browser of PC 200 based on Launcher 901 will be explained mainly with reference to Launcher 901.
[0052] First, the Launcher 901 checks the signature to determine whether the file has been tampered with and whether the download is complete (S1101). If the signature check is NG (No in S1101), the Launcher 901 determines that the file has been tampered with or the download is complete, and ends the process.
[0053] On the other hand, if the signature verification is OK (Yes in S1101), the Launcher 901 determines that the file has not been tampered with and that the download is not incomplete, and proceeds to S1102. In S1102, the Launcher 901 extracts data from offset 001000h of its own file, performs Zip decompression processing, and stores the data in a writable folder (for example, " / tmp" in a Linux (registered trademark) system). Next, the Launcher 901 launches ScanApplication.exe, which is a scan application, from the data stored in S1102 above (S1103), and ends the process.
[0054] When the scan application is started, a scan button corresponding to the reading mode is displayed as shown in FIG. FIG. 12 is a diagram showing an example of the scan application screen. In addition, if the device configuration.xml deployed in the same directory (folder) as the scan application does not contain a valid scan session ID, the scan application may display a message such as "Another user is using the device" on the scan application screen (Figure 12).
[0055] 13 is a sequence diagram for explaining the operation of the scan application. In this embodiment, the scan operation when, for example, monochrome document button 1201 is pressed will be explained. In this sequence diagram, the processing of PC 200 is realized by the CPU of PC 200 executing the downloaded scan application. Note that the processing performed by the web browser of PC 200 based on the scan application will be explained mainly with reference to the scan application. Also, the processing of image reading device 100 is realized by CPU 11 executing a program stored in ROM 12.
[0056] When a button for executing a scan (e.g., monochrome document button 1201) is pressed on a scan application screen such as that shown in Fig. 12, the scan application of PC 200 requests a scan command instruction (request to read an original) from image reading device 100 (S1301). At this time, the scan application refers to deviceconfiguration.xml deployed in the same directory (folder) as the scan application, reads the IP address, and incorporates it into the URI. The scan application also reads the session ID and scan session ID from configuration.xml deployed in the same directory, sets them in the Cookie of the request header, and issues the above-mentioned request.
[0057] In response to the request in S1301, the CPU 11 of the image reading device 100 verifies the scan session ID included in the Cookie. If the scan session ID does not match (if it is different from the scan session ID stored in the RAM 13), the CPU 11 of the image reading device 100 returns a response of "status":"InvalidID" indicating that the scan session ID is not matched to the scan application of the PC 200 (not shown). If "status":"OK" is not returned from the image reading device 100 in S1302, the scan application of the PC 200 retries S1301 a predetermined number of times, then notifies the user of an error message and terminates. In this case, the scan application of the PC 200 attempts to obtain a scan session ID by a scan session ID request shown in Fig. 14, which will be described later.
[0058] On the other hand, if the scan session ID is verified as being valid, the CPU 11 of the image reading device 100 returns a response "status": "OK" to the scan application of the PC 200 (S1302). hmm In response to a request issued by the image reading device 100, response data is returned in JSON format.
[0059] Furthermore, when the CPU 11 of the image reading device 100 transmits "status":"OK" in the above S1302, the CPU 11 starts a scanning operation and stores the image data in the RAM 13 (S1305). After receiving the "status":"OK" in S1302, the scan application sends a request ("readimage") to the image reading device 100 in order to read image data (S1303). When the CPU 11 of the image reading device 100 receives the request ("readimage") of S1303 above, and there is no image data to return, it returns "status":"Busy" (S1304). The scan application repeats the request ("readimage") of S1303 above until "status":"OK" is returned from the image reading device 100.
[0060] Then, when "status":"OK" is returned from the image reading device 100 (S1307), the scan application converts the data element included in the returned response from a character string (Base64) to binary to form image data (S1308).
[0061] Next, the scan application performs the scan on the image data formed in S1308. After image processing such as gradation correction and edge emphasis, the image is converted to two-tone, and then converted to TIF. The image is converted into an image file format such as the F file format (S1309). Furthermore, the scan application stores this image file in a storage unit (such as a hard disk) of the PC 200, completing the processing of one image (S1310).
[0062] Furthermore, the scan application and the CPU 11 of the image reading device 100 cooperate to repeat the above-mentioned process (A) of S1306 to S1310, thereby saving the front and back images of all documents to the hard disk or the like of the PC on which the scan application is running (S1311), and the process is terminated. Furthermore, when all images have been read, the image reading device 100 discards the scan session ID stored in the RAM 13 and ends the process.
[0063] Next, the scan session ID request will be described. 14 is a sequence diagram for explaining the scan session ID acquisition process. In this sequence diagram, the process of PC 200 is realized by the CPU of PC 200 executing the downloaded scan application. Note that the process performed by the web browser of PC 200 based on the scan application will be explained mainly with reference to the scan application. Also, the process of image reading device 100 is realized by the CPU 11 executing a program stored in ROM 12.
[0064] When the CPU 11 of the image reading device 100 generates a scan session ID, it stores the generated scan session ID in the RAM 13, and discards the scan session ID when scanning is completed. If a scan session ID has already been stored in the RAM 13, the CPU 11 of the image reading device 100 does not generate a new scan session ID, but sends a download file with an invalid scan session ID embedded therein to the PC 200. For this reason, when the scan application of the PC 200 wants to perform scanning again or has acquired an invalid scan session ID, it becomes necessary to request a scan session ID from the image reading device 100.
[0065] The scan application of the PC 200 transmits a scan session ID request (a request to issue a scan session ID) to the image reading device 100 (S1401) in the following cases from the image reading device 100. For example, this applies when the deviceconfiguration.xml does not contain a scan session ID or contains an invalid scan session ID, or when "status":"InvalidID" is received from the image reading device 100, indicating that the session ID is incompatible.
[0066] In response to the request in S1401, if the scan session ID is not stored in the RAM 13, the CPU 11 of the image reading device 100 generates a new scan session ID, stores it in the RAM 13, and transmits the generated scan session ID to the PC 200 (S1402). This enables the scan application of the PC 200 to receive the scan session ID transmitted from the image reading device 100 and perform scanning.
[0067] If a scan session ID has already been stored in the RAM 13, the CPU 11 of the image reading device 100 does not generate a new scan session ID, but transmits, for example, an invalid ID to the PC 200. In this case, the scan application of the PC 200 needs to request a scan session ID again.
[0068] In this embodiment, the IP address of the image reading device 100 is obtained by referring to the deviceconfiguration.xml file, but the present invention is not limited to this. For example, a response from multicast DNS (mDNS) may be used as an example of a method for obtaining an IP address. When an mDNS request is issued from the PC 200 by the program of the scan application, the MAC address or scanner name is entered in the TXT record of the response data of the image reading device 100. Then, the scan application can determine whether the image reading device 100 is the download source, a different image reading device, or a different network device by comparing the TXT record of the response data with the deviceconfiguration.xml.
[0069] In this embodiment, the application to be downloaded is configured to operate only on a specific OS. However, when creating the download file in Fig. 9, the client OS may be detected from the user agent (HTTP_USER_AGENT) information included in the HTTP request header, and the launcher or scan application may be selected based on the OS to configure the download file.
[0070] In addition, in this embodiment, the invalid session ID or invalid scan session ID is "d41d8cd98f00b204e9800998ecf8427e", but is not limited to this. For example, in deviceconfiguration.xml, the scan-session-id element does not need to be described, and an empty string or characters not normally used in MD5 (for example, double-byte characters) may be used.
[0071] As described above, according to the first embodiment, the image reading device can be configured at a low cost, and can be used by users of information processing devices who do not have administrative authority, eliminating the trouble of installing drivers. In addition, when the image reading device is connected to a network with multiple users, it is possible to reduce the number of complicated operations that require the user to re-enter an IP address or obtain usage authority, thereby reducing the amount of work required by the user. In this way, it is possible to provide an image reading device that is easy to use.
[0072] Second Embodiment The image reading device of the first embodiment described above discards the scan session ID when scanning ends, and is in a state where it can issue a scan session ID to another PC. Therefore, even if an error such as a jam occurs during scanning and the scanning ends, the scan session ID is discarded. In the case of an error ending, the user who cleared the jam may not be able to immediately rescan. For example, if a scan is requested from a scan application of another PC while the jam is being cleared, a valid scan session ID is given to the scan application. In addition, a timeout may occur while the user is clearing the error, and the right to use the image reading device may be transferred to the other PC. In such a case, the user who cleared the jam must wait until the user of the other PC finishes scanning, and the scan operation cannot be completed promptly. Therefore, in the second embodiment, when scanning ends due to an error such as a jam, the scan session is continued and a timeout is prevented. This will be described in detail below.
[0073] First, detection of a paper jam of the original 101 will be described with reference to FIG. 15 is a diagram for explaining error detection in an image reading device, taking detection of a paper jam of an original as an example.
[0074] The CPU 11 of the image reading device 100 controls the scanning operation of the original 101 based on information from various sensors. For example, when the registration sensor 109 detects that the original 101 has passed the reading position of the image reading unit 104, the CPU 11 controls the image reading unit 104 to end reading of the original 101. The CPU 11 also detects a jam error of the original 101 conveyed on the conveying path 108 based on information from the registration sensor 109 and the paper discharge port sensor 112, for example, as follows.
[0075] First, FIG. 15(a) shows the state of each sensor when the document is normally transported. The registration sensor 109 detects the arrival of the original 101 after a time T1 has elapsed since the start of transport (point A), and starts reading after the time it takes for the original to be transported the distance from the registration sensor 109 to the image reading unit 104 has elapsed. Thereafter, the registration sensor 109 detects that the original has passed (point B), and this time is defined as T3. The paper discharge port sensor 112 detects the arrival of the original 101 after a time T2 has elapsed since the registration sensor 109 detected the arrival of the original 101 (point C), and detects the passage of the original 101 after a time T3 has elapsed (point D).
[0076] In contrast, when a jam occurs on the document 101, the states of the sensors are as follows: 15B, even after a time T4 has elapsed since the start of conveyance of the original 101, the registration sensor 109 does not detect the arrival of the original 101, where T4>>T1. 15C, even if the registration sensor 109 detects the arrival of the document 101 (point A) and a time T6 has elapsed, the registration sensor 109 does not detect the passage of the document 101, where T6>>T3. 15D, even if the registration sensor 109 detects the arrival of the document 101 (point A) and a time T5 has elapsed, the paper discharge port sensor 112 does not detect the arrival of the document 101, where T5>>T2. 15E, the discharge port sensor 112 detects the arrival of the document 101 (point C) and does not detect the passage of the document 101 even after a time T6 has elapsed, where T6>>T3.
[0077] 15(b) to 15(e) occurs, the CPU 11 determines that a document jam error has occurred, and stops the document transport and image reading operations. In the present embodiment, an example has been given in which a jam error is detected based on information from the registration sensor 109 and the paper discharge port sensor 112, but a jam may be detected based on an image read by the line image sensor 1043. In addition, in this embodiment, a jam error is given as an example of an error, but it is of course possible to configure the error to include a cover open error, a double feed error, a staple detection error, and other errors. The cover open error corresponds to an error that occurs when a sensor detects that the cover of the image reading device 100 has been opened during a scanning operation. The double feed error corresponds to an error that occurs when, for example, an ultrasonic sensor detects that multiple documents are being transported in an overlapping state. The staple detection error is an error that occurs when a stapled document is transported, and is detected by a sensor detecting the jumping of the document being transported (or detecting the staple needles with a metal detection sensor), etc.
[0078] Next, the management of the scan session ID will be described with reference to the flowchart of FIG. 16 is a flowchart showing an example of processing of a task for managing a scan session ID in the image reading device 100. The processing of this flowchart is realized by the CPU 11 of the image reading device 100 executing a program stored in the ROM 12.
[0079] When the image reading device 100 is powered on, the CPU 11 generates a session management task that processes a download request from a web browser, a scan request from a scan application, a scan session ID request request, and a scan end processing request instructed by the image reading device 100. Then, the CPU 11 initializes the scan session ID address that stores the scan session ID in the RAM 13 (for example, by overwriting it with all "0"s to make it empty), initializes the scan session ID timer (sets it to 0) (S1610), and starts accepting each of the above-mentioned requests. The scan session ID timer corresponds to a timer that measures the elapsed time since the scan session ID was issued.
[0080] When the CPU 11 of the image reading device 100 receives a download request, a scan request, or a scan session ID request (S1620), the process proceeds to S1625. In S1625, the CPU 11 of the image reading device 100 judges whether the scan session ID address is empty. If the scan session ID address is empty (Yes in S1625), the CPU 11 of the image reading device 100 judges that there is no user permitted to perform a scan operation, and creates a new scan session ID and stores it in the scan session ID address (S1626). Furthermore, the CPU 11 of the image reading device 100 creates a download file to which the valid scan session ID created in S1626 is added in response to a download request, and permits scanning in response to a scan request. Furthermore, in response to a scan session ID request request, the CPU 11 of the image reading device 100 returns the valid scan session ID created in S1626. Furthermore, the CPU 11 of the image reading device 100 restarts a scan session ID timer that measures the time since the scan session ID was generated (S1628). This makes it possible to remeasure the elapsed time since the valid scan session ID was issued and extend the time until the timeout. Thereafter, the process proceeds to S1620.
[0081] On the other hand, if the scan session ID address is not empty in S1625 (No in S1625), the CPU 11 of the image reading device 100 advances the process to S1627. In S1627, the CPU 11 of the image reading apparatus 100 compares the scan session ID sent from the scan application in response to the scan request with the ID stored in the scan session ID address, and determines whether the two match.
[0082] In the above S1627, if the two IDs match (Yes in S1627), the CPU 11 of the image reading device 100 permits scanning (step not shown) and advances the process to S1628. That is, the scan session ID timer is restarted.
[0083] On the other hand, if the two IDs do not match in S1627 (No in S1627), the CPU 11 of the image reading device 100 does not permit scanning and proceeds to S1629. Note that if the request received in S1620 is a download request or a scan session ID request, the request does not include a scan session ID, so S1627 is always determined as No.
[0084] In S1629, the CPU 11 of the image reading device 100 creates an invalid scan session ID, responds to the request source, and proceeds to S1620. In the case of a download request, the CPU 11 creates a download file with an invalid scan session ID added, and responds to the request source. In this embodiment, the session ID and scan session ID are character strings that have been MD5 converted based on the time and MAC address, and the invalid ID is "d41d8cd98f00b204e9800998ecf8427e".
[0085] Furthermore, in the above S1620, if the CPU 11 of the image reading device 100 has not received any of a download request, a scan request, or a scan session ID request (No in S1620), the CPU 11 of the image reading device 100 advances the process to S1630.
[0086] In S1630, CPU 11 of image reading device 100 determines whether or not scanning has ended. Note that the state where scanning has ended refers to a state where scanning has ended but processing that would be performed when scanning has ended has not yet been performed. If scanning has ended (Yes in S1630), CPU 11 of image reading device 100 advances the process to S1635.
[0087] In S1635, CPU 11 of image reading device 100 determines whether or not an error occurred in the completed scan. If an error occurred (i.e., the completed scan ended in an error) (Yes in S1635), CPU 11 of image reading device 100 advances the process to S1628 and restarts the scan session ID timer. In this case, the scan session ID stored in the scan session ID address remains valid.
[0088] On the other hand, if no error has occurred in S1635 (that is, the completed scan has been completed normally) (No in S1635), the CPU 11 of the image reading device 100 advances the process to S1645. In S1645, the CPU 11 of the image reading apparatus 100 initializes (to null) and discards the scan session ID stored in the scan session ID address, and also initializes (to 0) the scan session ID timer, and the process proceeds to S1620.
[0089] In addition, in the above S1630, if the scan is not completed (N in S1630), In the case of o), the CPU 11 of the image reading device 100 advances the process to S1640. In S1640, CPU 11 of image reading device 100 determines whether or not the scan session ID has timed out (a predetermined time has elapsed since the scan session ID was created). If the scan session ID has not timed out (No in S1640), CPU 11 of image reading device 100 transitions to S1620.
[0090] On the other hand, if the scan session ID has timed out in S1640 (Yes in S1640), the CPU 11 of the image reading device 100 advances the process to S1645, initializes the scan session ID and the scan session ID timer, and transitions the process to S1620.
[0091] In the present embodiment, an example is given in which, in session management, when an error occurs and scanning ends, the scan session ID is not discarded but is retained as is, regardless of the type of error. However, in the case of an error that is determined to indicate an intention to interrupt scanning, such as a cover open, or an error that is predicted not to resume processing, such as a hardware error, the scan session ID may be discarded, while in the case of a predetermined error that is predicted to resume processing, such as a jam or staple detection error, the scan session ID may be retained as is, rather than discarded. In this way, control may be performed to switch processing according to the type of error that has occurred. Also, the timeout time may be changed according to the type of error. For example, in the case of a staple detection error, it is predicted that it will take a long time to resume processing, so the timeout time may be set longer than the normal timeout time. The staple detection error can be detected by detecting the jumping of the document using a sensor (not shown) provided in the document transport path, or by detecting staples using a metal sensor (not shown).
[0092] Also, in the above description, an example was given in which, in session management, when an error occurs and scanning ends, the scan session ID is not discarded but is retained as is. However, when an error occurs and scanning ends, the scan session ID may be discarded once, and another scan session ID may be created, and a scan session with that scan application may be established again. That is, if Yes is selected in S1635 of FIG. 16, S1626 and S1628 may be executed, a scan session ID may be re-created and saved, and sent to that scan application, and the scan session ID timer may be restarted.
[0093] As described above, according to the second embodiment, in addition to the effects of the first embodiment, even if an error such as a jam (document jam) occurs during scanning and the scanning ends, the scanning application can still be effectively used for other scanning applications. scan By not assigning a session ID, continuing to establish a session with the current scanning application, and preventing timeouts, the user can complete the scanning task (document reading task).
[0094] In the above first and second embodiments, the image reading device 100 is configured to return "status":"InvalidID" to the scan application of the PC 200 when an invalid scan session ID is included in the document reading request from the scan application of the PC 200. In this configuration, the PC 200 that receives "status":"InvalidID" performs the scan session ID acquisition process shown in Fig. 14 and makes a document reading request again. However, if the scan session ID is not stored in RAM 13 of image reading device 100, even if an invalid scan session ID is included in the document reading request from the scan application of PC 200, the scan operation may be started immediately while issuing a scan session ID to the scan application of PC 200, without returning "status":"InvalidID". With this configuration, it is possible to omit communication between the scan application of PC 200 and image reading device 100 and start the scan operation immediately.
[0095] Also, the scan application of the PC 200 has been described as including a scan session ID in a document reading request when the scan application requests the image reading device 100 to read a document. The image reading device 100 uses the scan session ID included in the document reading request to determine whether the document reading request is valid for the stored scan session ID. However, the document reading request may not include the scan session ID. In this configuration, for example, when issuing a scan session ID, the image reading device 100 may associate the IP address or the like (or the MAC address or the like) of the PC 200 to which the scan session ID is issued with the scan session ID and store it, and when a document reading request is made, the image reading device 100 may compare the IP address or the like of the request source with the above-mentioned stored IP address or the like to determine whether the document reading request is valid for the stored scan session ID.
[0096] In addition, in each of the above embodiments, an example has been described in which the scan session ID is generated using a MAC address or the like, but the scan session ID may be generated using a specific rule using other information related to the PC 200, such as the device name of the PC 200, an IP address, etc. Also, the scan session ID may not be embedded in the download file, but may be stored only on the image reading device 100 side. In that case, when a document reading request is received from the scan application of the PC 200, the image reading device 100 may temporarily create a scan session ID using the above specific rule based on the information of the PC 200, and compare the scan session ID with the stored scan session ID to determine whether the received document reading request is valid.
[0097] Third Embodiment Among the information processing devices connected to the image reading device 100, particularly portable information processing devices such as smartphones and tablet PCs, generally operate on storage batteries, so that the battery runs out during operation, or applications are forcibly switched due to receiving a phone call, etc., and this is likely to occur. If an application executing a scan on the information processing device side is terminated or interrupted during a scan process due to these factors, the scan process may not be completed in the image reading device. In this case, the image reading device may not be used by other information processing devices until a timeout occurs. In the third embodiment, a configuration that solves this problem will be described. Note that in this embodiment, an image reading device (scanner) will be used as an example of a peripheral device, but the peripheral device to which the present invention can be applied is not limited to a scanner, and the present invention can also be applied to peripheral devices used in a similar environment.
[0098] 18 is a diagram showing an example of the configuration of a system according to the third embodiment of the present invention. Here, a system including a scanner 1810, a mobile terminal a (1820), and a mobile terminal b (1830) will be described as an example. 18, the scanner 1810, the mobile terminal a (1820), and the mobile terminal b (1830) are connected to the same LAN 1800, and are capable of transmitting and receiving data. For example, the IP address of the scanner 1810 is assigned as 192.168.1.10, the IP address of the mobile terminal a (1820) is assigned as 192.168.1.100, and the IP address of the mobile terminal b (1830) is assigned as 192.168.1.101. Note that it is possible to further increase the number of mobile terminals, or to use regular terminals that are not mobile (e.g., PCs), but for the sake of simplicity, the above configuration is used in this example.
[0099] Scanner The scanner 1810 is an image reading device equipped with an image reading unit 1811 that has a function of reading a paper document and converting it into electronic data. The image reading unit 1811 reads an image on the document, creates electronic data, and stores it in a storage unit 1812 under the control of a control unit 1813. The control unit 1813 controls the entire scanner 1810 .
[0100] The UI unit 1814 includes, for example, a display panel (a display device with a touch panel) and various keys such as an OK key, a cancel key, an up key, a down key, a numeric keypad, etc. The screen displayed on the display panel and detection of pressing of various keys are performed under the control of the control unit 1813.
[0101] The transmitting / receiving unit 1815 transmits a UI (user interface) created by a UI providing unit 1816 (described later) to the terminal in response to a request issued from the terminal. The transmitting / receiving unit 1815 also receives requests such as a scan start request, a status confirmation request, and an image acquisition request, and transmits responses to the received requests.
[0102] The UI providing unit 1816 creates operation screens in html format, such as a scan setting screen for setting scan settings, an image saving screen for saving scanned images to the terminal, and a status display screen showing the current status such as during scanning, and provides them to the terminal. The UI providing unit 1816 may create html format data in which a program written in JavaScript (registered trademark) or the like is embedded. Also, by creating it in html format, the screens created by the UI providing unit 1816 can be displayed on the web browser of the terminal.
[0103] Furthermore, the UI providing unit 1816 has an exclusive function that performs exclusive control over requests from other terminals when the scanner 1810 is being used from a specific terminal. This exclusive function is performed by session management. Specifically, when the scanner 1810 is accessed from a web browser of a terminal, the scanner 1810 acquires the IP address of the terminal that has accessed the scanner 1810. The scanner 1810 then stores the IP address of the terminal that has accessed the scanner 1810 in the UI provision unit 1816 as a session ID for session management.
[0104] The initial value of the session ID stored in the UI providing unit 1816 is a value (such as "0") indicating an initial state. Then, when the session ID is the initial value, the IP address of the terminal that first made a UI provision request to the UI providing unit 1816 is overwritten as the session ID stored in the UI providing unit 1816. Then, when a series of processes related to scanning is completed, the UI providing unit 1816 overwrites the session ID with the initial value. With this configuration, requests can be accepted only from the terminal in session, and requests from other terminals can be excluded. If there is no access from the terminal in session for a certain period of time, the UI provision unit 1816 executes a process of overwriting the session ID to the initial value (initialization of the session ID due to a timeout).
[0105] For example, when the session ID of the UI providing unit 1816 is the initial value and the mobile terminal a (1820) accesses the UI providing unit 1816 of the scanner 1810, the UI providing unit 1816 stores the IP address "192.168.1.100" of the mobile terminal a (1820) as the session ID. Thereafter, when the UI providing unit 1816 receives access from a terminal, it compares the session ID stored in the UI providing unit 1816 with the IP address of the access source. If the comparison results are the same, the UI providing unit 1816 returns a normal response to the request. If the comparison results are different, the UI providing unit 1816 returns a response indicating that the scanner is in use. The control unit 1813 and the UI providing unit 1816 each perform various controls by executing a program stored in an internal storage unit or the storage unit 1812. The session ID is an example, and something other than the IP address may be used.
[0106] Mobile devices The mobile terminal a (1820) and the mobile terminal b (1830) are, for example, mobile terminals such as smartphones and tablet PCs. Note that the mobile terminal a (1820) and the mobile terminal b (1830) have the same configuration, and the same reference numerals are used for the same components.
[0107] The transmission / reception unit 1821 transmits and receives various data to and from devices on the LAN. The storage unit 1822 stores various programs such as the OS of the mobile terminal and applications such as a web browser, and can start up various programs under the control of the control unit 1823. The UI unit 1824 includes a touch panel and displays a home screen, a web browser screen, and the like. When a button is displayed on the screen displayed on the touch panel, the UI unit 1824 can detect a tap. The UI unit 1824 also includes a home key, and when the home key is pressed, a home screen is displayed on the touch panel. On the home screen, an application such as a web browser can be selected. The screen display of the touch panel, tap detection, and pressing detection of the home button are performed under the control of the control unit 1823.
[0108] The mobile terminal is equipped with a camera 1825, and may have a function of reading image codes such as two-dimensional bar codes (QR codes (registered trademark)) read by the camera 1825 under the control of the control unit 1823. If the mobile terminal is capable of reading QR codes, it can access a URL destination using URL information obtained from the QR code. It is also possible to access a URL destination by subjecting a character string included in a captured image to OCR processing or the like.
[0109] <Scanning process flow> The flow of scanning using the mobile terminal a (1820) will be explained below. FIG. 19 is a diagram explaining the flow of scanning using the mobile terminal a (1820). When the scanner 1810 is powered on, it transitions to a standby state in which a menu screen 1900 as shown in FIG. 20 is displayed on the display panel of the UI unit 1814 . FIG. 20 is a diagram showing an example of a menu screen displayed on the UI unit 1814 of the scanner 1810. There are two menu items: web application mode and main unit settings. The user presses the up or down key of the UI section 1814 to select an item (1901 or 1902), and then presses the OK key to confirm the item. When web application mode 1901 is selected, the scanner starts the web application mode following S2100. When main unit settings 1902 is selected, items related to main unit settings are displayed, and it becomes possible to perform scanning using those settings, but a description of these will be omitted here.
[0110] In S2100, when the UI provision unit 1816 of the scanner 1810 starts the web application mode, it displays a URL display screen 1910 as shown in FIG. 21 on the display panel of the scanner. 21 is a diagram showing an example of a URL display screen displayed on the UI unit 1814 of the scanner 1810. This screen displays a URL and a QR code with the contents of the URL embedded therein, and this screen is displayed in the web application mode. Note that in this embodiment, communication with the scanner is performed by HTTP communication using the web browser of the terminal, but a capture application may be installed on the terminal and communication between the capture application and the scanner may be performed by communication other than HTTP communication.
[0111] In S2101, the user starts the web browser of the mobile terminal a (1820), enters the URL displayed as in Fig. 21, and accesses the scanner from the mobile terminal a (1820), causing a scan setting screen 2000 as shown in Fig. 22 to be displayed on the browser. Note that if the terminal device a is equipped with a camera and is capable of reading QR codes, the QR code may be used instead of entering the URL. FIG. 22 is a diagram showing an example of a scan setting screen displayed on the UI unit 1824 of the mobile terminal in the third embodiment.
[0112] In S2102, the user operates buttons 2001 to 2003 on a scan setting screen 2000 displayed on the browser of the mobile terminal a (1820) to determine the scan settings. Here, as an example, the color mode is set to "color," the document size to "A4," and the resolution to "300 dpi," but the scan setting items and contents may be added or changed as appropriate depending on the functions of the scanner.
[0113] In S2103, when the user presses the scan start button 2004, the terminal device a issues a scan start request to the scanner 1810. When the scanner 1810 receives the scan start request, it starts the scan process based on the scan settings set in the request. Thereafter, the mobile terminal a (1820) periodically issues a status confirmation request to inquire of the scanner 1810 whether the scan process has been completed. In response to this request, the scanner 1810 creates a status display screen showing the current status and provides it to the terminal device a (1820). If the scan process is not completed, a scan in progress screen 2010 showing that scanning is in progress as shown in FIG. 23 is displayed, and when the scan process is completed, an image save screen 2020 as shown in FIG. 24 is displayed. FIG. 23 is a diagram showing an example of a scanning screen displayed on the UI unit 1824 of the mobile terminal. FIG. 24 is a diagram showing an example of an image storage screen displayed on the UI unit 1824 of the mobile terminal.
[0114] In S2104, the mobile terminal a (1820) displays an image save screen 2020 for saving scanned images as shown in FIG. 24. In the example of FIG. 24, the image save screen 2020 is displayed when four images are scanned, and four thumbnails 2021, 2022, 2023, and 2024 corresponding to the four scanned images are displayed. In the image save screen 2020, when the user taps the image to be saved, an image acquisition request is sent to the scanner 1810, and the image can be downloaded. The downloaded image is saved in the storage unit 1822 of the terminal device a (1820). When a series of processes is completed, the user presses the end button 2025 to end the series of processes in the web application mode. Note that a batch save button for saving all images displayed as thumbnails may be provided, or the end button 2025 may have that function. In that case, it is preferable to provide another button for saving only the selected image and exiting.
[0115] When a series of processes related to scanning is completed, the UI provision unit 1816 overwrites the session ID to the initial value, the scanner 1810 transitions to a standby state, and the menu screen 1900 in FIG. 20 is displayed.
[0116] <Exclusion processing flow> The above explanation was about the flow of the scan process using one mobile terminal a (1820) and a scanner. Next, the flow of the exclusive process and the release of the exclusive process that occurs when there are two mobile terminals a (1820) and b (1830) will be explained.
[0117] For example, suppose that while the mobile terminal a (1820) is displaying the image storage screen 2020 in S2104 of Fig. 19 described above, the mobile terminal a (1820) is turned off and is unable to continue the subsequent processing. In this case, the scanner 1810 excludes access from other terminals until a timeout occurs in the session with the mobile terminal a (1820). In this situation, if the scanner 1810 is accessed using the web browser of the mobile terminal b (1830), the other user in use screen 2030 shown in Fig. 25 is displayed on the web browser. FIG. 25 is a diagram showing an example of a screen indicating that the mobile terminal is in use by another user and is displayed on the UI unit 1824 of the mobile terminal.
[0118] In this way, if some accident occurs during a session that makes it impossible to continue processing, in this embodiment, the user can release the exclusive processing and end the web application mode by pressing a cancel key (not shown) on the UI unit 1814 of the main body of the scanner 1810. This will be described in detail below.
[0119] 26 is a flowchart showing an example of a process for ending the web application mode in the third embodiment. The process of this flowchart is realized by the UI provision unit 1816 of the scanner 1810 executing a program stored in the internal storage unit or the storage unit 1812.
[0120] In S2700, when a cancel key (not shown) of the UI unit 1814 is pressed during the web application mode, the UI providing unit 1816 of the scanner 1810 performs control so as to display a web application mode termination confirmation screen 1920 as shown in Fig. 27 on the display panel. On the termination confirmation screen 1920, the user can select whether or not to terminate the web application mode. FIG. 27 shows a termination confirmation screen displayed on the UI section 1814 of the scanner 1810 according to the third embodiment. FIG. 13 is a diagram showing an example of a screen.
[0121] Next, in S2701, the UI provision unit 1816 of the scanner 1810 determines whether or not to terminate the web application mode based on a user selection on a web application mode termination confirmation screen 1920. Here, when "Yes" 1921 is selected on the web application mode termination confirmation screen 1920, the scanner 1810 determines to terminate the web application mode (Yes in S2701), and proceeds to S2702.
[0122] In S2702, the UI providing unit 1816 of the scanner 1810 overwrites the session ID stored in the UI providing unit 1816 with an initial value (for example, "0"). This makes it possible to accept access from other terminals. Furthermore, in S2703, the UI provision unit 1816 of the scanner 1810 displays a menu screen 1900 as shown in FIG. 20 on the display panel of the UI unit 1814, and the process ends.
[0123] Also, in S2701, if "No" 1922 is selected on the web application mode termination confirmation screen 1920, the scanner 1810 determines not to terminate the web application mode (No in S2701), and advances the process to S2704. In S2704, the scanner 1810 displays a web application mode screen 1910 as shown in FIG. 21 on the display panel of the UI unit 1814, and ends the process.
[0124] As described above, in the third embodiment, even if the scan process cannot be continued due to some accident such as the battery running out on the mobile terminal, the web application mode can be ended without waiting for the scan session to time out, and other users can use the scanner. Note that in S2702 of FIG. 26, the selection of whether or not to end the web application mode is accepted, but this is not limited to this. For example, it is also possible to discard only the current session ID while maintaining the web application mode. In this case, instead of displaying the menu screen 1900 in S2703, a URL display screen 1910 may be displayed. In other words, even if a web application or the like is terminated or interrupted before the document reading process is completed and the scan session is not terminated normally, it is possible to use the image reading device from another information processing device without waiting for the scan session to time out.
[0125] [Fourth embodiment] In the above third embodiment, anyone can end the web application mode of the scanner 1810 by pressing the cancel key (not shown) on the UI unit 1814. Therefore, there is a possibility that the web application mode may be ended by a malicious user. Therefore, in the fourth embodiment, a configuration is made in which a passcode input operation is requested when ending the web application mode. This will be described in detail below.
[0126] In this embodiment, in S2102 of FIG. 19, the scan setting screen displayed on the mobile terminal a (1820) when the scan setting screen is being operated is the scan setting screen 2040 shown in FIG. 28 in this example. FIG. 28 is a diagram showing an example of a scan setting screen displayed on the UI unit 1824 of the mobile terminal in the fourth embodiment. 22 is that an end passcode 2045 is displayed in the scan setting screen 2040. Note that buttons 2041 to 2044 on the scan setting screen 2040 are the same as buttons 2001 to 2004 on the scan setting screen 2000, and a description thereof will be omitted.
[0127] The exit passcode 2045 is required when terminating the web application mode midway. The scanner 1810 of this embodiment stores this exit passcode in the UI provision unit 1816, determines whether it matches a passcode input by the user (described later), and controls the termination of the web application mode.
[0128] The flow of processing when the cancel key is pressed in the web application mode will be described below with reference to FIG. 31 is a flowchart showing an example of a process for ending the web application mode in the fourth embodiment. The process of this flowchart is realized by the UI provision unit 1816 of the scanner 1810 executing a program stored in the internal storage unit or the storage unit 1812.
[0129] In S3100, when a cancel key (not shown) of the UI unit 1814 is pressed during the web application mode, the UI providing unit 1816 of the scanner 1810 displays a passcode entry screen 1930 as shown in FIG. 29 on the display panel and waits for the user to enter a passcode. 29 and 30 are diagrams showing an example of a passcode input screen displayed on the UI unit 1814 of the scanner 1810 according to the fourth embodiment.
[0130] In the example of the scan setting screen shown in Fig. 28, the end passcode is set to "1234", but it is preferable that this end passcode be changed to a random value for each scan process. Alternatively, the end code may be configured so that the user can set it as desired. When the end code is entered as in 1940 in Fig. 30, the UI provision unit 1816 of the scanner 1810 advances the process to S3101.
[0131] In S3101, the UI provision unit 1816 of the scanner 1810 determines whether the entered passcode matches. If it is determined that the passcode entered by the user by operating the numeric keypad of the scanner matches the end passcode stored in the UI provision unit 1816 (Yes in S3101), the scanner 1810 advances the process to S3102.
[0132] In S3102, the UI providing unit 1816 of the scanner 1810 overwrites the session ID stored in the UI providing unit 1816 with the initial value, thereby making it possible to accept access from other terminals. Furthermore, in S3103, the UI provision unit 1816 of the scanner 1810 displays a menu screen 1900 as shown in FIG. 20 on the display panel of the UI unit 1814, and the process ends.
[0133] Also, in the above S3101, if it is determined that the passcode entered by the user by operating the numeric keypad of the scanner 1810 does not match the exit passcode stored in the UI providing unit 1816 (No in S3101), the UI providing unit 1816 of the scanner 1810 advances the processing to S3104. In S3104, the UI providing unit 1816 of the scanner 1810 displays the web application mode screen 1910, and the process ends. If the cancel key of the scanner 1810 is pressed while the passcode entry screen 1930 shown in FIG. 29 is displayed, the scanner 1810 may return the display to the web application mode screen 1910 (FIG. 21).
[0134] As described above, according to the fourth embodiment, in addition to the effects of the third embodiment, by requiring input of a passcode when terminating the web application mode of the scanner 1810, it is possible to prevent a malicious user, etc. from terminating the web application mode.
[0135] In the third and fourth embodiments, the scanner 1810 manages the session using the IP address of the mobile terminal. However, the scanner 1810 may be configured to issue a session ID other than the IP address and manage the session.
[0136] Furthermore, in the above third and fourth embodiments, a configuration has been described in which the scanner 1810 is operated via a web browser running on a mobile terminal; however, as in the first and second embodiments, the scanner 1810 may be operated by a downloaded scanning application, or the scanner 1810 may be operated using a dedicated application installed on the mobile terminal.
[0137] In the above third and fourth embodiments, a configuration has been described in which, during execution of a series of processes related to scanning, when exclusive control of the mobile terminal is performed by storing a session ID in the storage unit 1812 or the like, the session ID can be discarded by operating the cancel key on the UI unit 1814 of the scanner 1810. As another embodiment, the following configuration may be provided.
[0138] For example, each time a scan setting is made on the mobile terminal side, the setting is notified to the scanner 1810. Furthermore, the scanner 1810 is configured not to discard the scan session ID if the notification is received within a predetermined interval. Furthermore, when discarding a scan session ID, the scanner 1810 may be configured to notify the portable terminal corresponding to the scan session ID of an inquiry as to whether or not the scan session ID can be discarded, and to be able to discard the scan session ID if there is no response. Note that, when the portable terminal responds to the above-mentioned discard inquiry that the scan session ID should not be discarded, the scanner 1810 resets the discarding operation of the scan session ID (for example, the scanner 1810 does not discard the scan session ID, and restarts the scan session ID timer). Also, when the scanner 1810 discards a scan session ID, it notifies the portable terminal corresponding to the discarded scan session ID that the scan session ID has been discarded. Note that, when the portable terminal has a server function, the scanner 1810 notifies the portable terminal by notifying the server. Also, when the portable terminal is polling the scanner 1810, the notification is made by the polling. Note that the notification may be made by other methods.
[0139] In a system in which the mobile terminal side performs polling, the scanner 1810 sets a flag indicating that the scan session ID has been discarded so that the mobile terminal corresponding to the discarded scan session ID can poll to notify that the scan session ID has been discarded. When the mobile terminal recognizes that the scanner 1810 has discarded the scan session ID, the mobile terminal notifies the user of this. The method of notifying the user may be a screen display or another method.
[0140] In the fourth embodiment, a passcode is required when performing an operation to cause scanner 1810 to discard the scan session ID, but the scan session ID may be discarded without a passcode until scanner 1810 starts reading an image. After scanner 1810 has finished reading an image, if an image is being selected by thumbnail on a screen such as that shown in Fig. 24, the scan session ID may not be discarded, or input of a passcode may be required. Furthermore, the user may be allowed to set in the scanner 1810 the timing for prohibiting discarding of the scan session ID, and the scanner 1810 may prohibit discarding of the scan session ID at the set timing.
[0141] As described above, according to each embodiment, while preventing the required hardware configuration of the image reading device from becoming expensive, even a user who has not been granted special management authority over the information processing device can control the image reading device from the information processing device and read a document without complicated operations such as re-entering an IP address or additional operations to obtain usage authority. Even if an error such as a document jam occurs during document reading and the document reading process ends, the document reading process can be resumed after the error is cleared, and the document reading operation can be completed. In addition, even if a web application or the like is terminated or interrupted before the document reading process is completed and the scan session is not terminated normally, it is possible to use the image reading device from another information processing device without waiting for the session to time out.
[0142] The configurations and contents of the various data described above are not limited to those described above, and the data may have various configurations and contents depending on the application and purpose. Although one embodiment has been described above, the present invention can be embodied, for example, as a system, an apparatus, a method, a program, a storage medium, etc. Specifically, the present invention may be applied to a system composed of multiple devices, or may be applied to an apparatus composed of a single device. Furthermore, any combination of the above-described embodiments is also included in the present invention.
[0143] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. Furthermore, the present invention may be applied to a system made up of a plurality of devices, or to an apparatus made up of a single device. The present invention is not limited to the above-mentioned embodiment, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and are not excluded from the scope of the present invention. In other words, the present invention includes all configurations that combine the above-mentioned embodiments and their modifications. [Explanation of symbols]
[0144] 100 Image reader 10 Control section 11 CPU 12 ROM 13 RAM 200 PC
Claims
1. An image reading device that reads an image from an original, a first session management unit for managing first session information for performing an operation not involving image reading processing of the image reading device; a control means for enabling the image reading device to be operated via a network based on the first session information, performing image reading processing in response to a request from an information processing device capable of communicating via the network without installing a driver for operating the image reading device, and, while performing the image reading processing, not accepting requests from other information processing devices and performing exclusive control to occupy the image reading processing of the image reading device; a second session management means for managing second session information for performing the exclusive control; Equipped with The control means is configured to release the exclusive control when a predetermined time has elapsed since the second session information was created, and when an error occurs in reading the image, the control means controls so that the exclusive control is maintained even after the predetermined time has elapsed since the second session information was created.
2. the second session management means causes the second session information to time out when a predetermined time has elapsed since the second session information was created; 2. The image reading apparatus according to claim 1, wherein the control unit releases the exclusive control when the second session information times out.
3. 3. The image reading device according to claim 2, wherein the second session management means restarts a time count up to a time-out of the second session information when an error occurs during the reading of the image.
4. The image reading device according to claim 2, characterized in that, when an error occurs in reading the image, the second session management means maintains the exclusive control based on the fact that the second session management means maintains the session by temporarily discarding the first session information and then creating second session information.
5. a canceling means provided in the image reading device for issuing an instruction to release the exclusive control; 2. The image reading apparatus according to claim 1, wherein the second session management means discards the second session information when the release instruction is issued.
6. The image reading device according to claim 1 or 2, characterized in that the control means changes the specified time for maintaining the exclusive control depending on the type of the error.
7. An image reading device for reading an image from an original, comprising: a control means for performing processing in response to a request from an information processing device that can communicate with the image reading device via a network without installing a driver for operating the image reading device, and performing exclusive control not to accept requests from other information processing devices while performing the processing; a session management means for managing session information for performing the exclusive control between the web browser operating on the information processing device and the information processing apparatus; Equipped with The control means is configured to release the exclusive control when a predetermined time has elapsed since the session information was created, and when an error occurs in reading the image, the control means determines whether the error is an error that predicts that the process will be resumed or not, and depending on the result of the determination, switches between maintaining or canceling the exclusive control even when the predetermined time has elapsed since the session information was created.
8. The image reading device according to claim 7, characterized in that the control means changes the specified time for maintaining the exclusive control depending on the type of error for which resumption of the processing is predicted.
9. The image reading device according to claim 7, wherein the error for which resumption of the processing is predicted is an error due to jam detection or staple detection.
Citation Information
Patent Citations
Communication method, communication system, program and storage medium
JP2003051824A
Scanner system and method therefor
JP2005045437A
Image processing device, control method of the same and program
JP2015019125A
Image processing apparatus, mobile device, restricting method, and storage medium
JP2016015606A
Login logout system, electronic equipment, and login logout program
JP2019028719A
