JP7743330B2 - System, correction information acquisition method, and server - Google Patents

Description

The present invention relates to a system, a correction information acquisition method, and a server.

Conventionally, image reading devices such as image scanners (see, for example, Patent Documents 1 to 3) and OHRs (Over Head Readers) have been known as image reading means for reading images from media. OHRs are also called stand-type image readers, non-contact image readers, etc.

OHRs used in banks and other financial institutions are used to read media such as deposit and withdrawal slips and tax and public payment slips, as well as media that cannot be handled by auto-feeder image scanners (such as driver's licenses), and read such media as, for example, 24-bit full-color images. Images of media scanned by the OHR are then used for the following purposes: character recognition using OCR (Optical Character Recognition) processing, seal verification by overlaying a seal and stamp image, digitization and filing of tax and public payment slips brought in by customers, digitization and filing of identity documents such as driver's licenses, etc.

At financial institution branches, each counter is set up with a system configuration in which a terminal (a so-called fat client terminal) and an OHR are connected one-to-one. In this system configuration, the terminal and OHR are connected via a general-purpose IF (Interface) such as USB (Universal Serial Bus), and correction information used for image processing of images scanned by the OHR is stored on the terminal. Note that this correction information is used to correct for the state of the OHR's surrounding environment (brightness, shadows, etc.) and individual errors in the OHR.

In recent years, the financial industry has been promoting the downsizing of sales branches (reducing the number of branches, devices, and staff, etc.), which has led to a demand for a reduction in the number of terminals and input/output devices (including OHRs). In response to this, consideration is being given to introducing a system configuration in which virtual terminals are built on a server and thin client terminals and virtual desktops are used to share and operate terminals and input/output devices when needed. This system configuration makes it possible to use one OHR with multiple (N) virtual terminals, or to use multiple (N) OHRs with one virtual terminal (dynamically switching the OHR used by one virtual terminal). In other words, this system configuration includes a system configuration in which virtual terminals and OHRs are connected N-to-N.

Japanese Patent Application Laid-Open No. 2021-068274 Japanese Patent Application Laid-Open No. 2020-198555 JP 2013-246697 A

However, several issues are anticipated when attempting to implement a system configuration in which virtual terminals and OHRs are connected N-to-N based on an existing system configuration in which terminals and OHRs are connected one-to-one. These issues will be explained using Figures 7 and 8. In this explanation, we will first use Figure 7 to explain the existing system configuration in which terminals and OHRs are connected one-to-one, and then use Figure 8 to explain the issues that are anticipated when attempting to implement a system configuration in which virtual terminals and OHRs are connected N-to-N based on an existing system configuration.

Figure 7 is a diagram illustrating an existing system configuration in which a terminal and an OHR are connected one-to-one. As illustrated in Figure 7, in the existing system configuration, a terminal 1001 and an OHR 1002 are connected one-to-one via a general-purpose interface such as USB. An "OHR" folder is created in the storage (e.g., HDD (Hard Disk Drive)) 1003 of the terminal 1001, and correction information for the OHR 1002, etc., is stored in this "OHR" folder. The registry 1004 of the terminal 1001 stores the folder path of the "OHR" folder ("C:\OHR"), etc.

Such a terminal 1001 performs, for example, OPEN processing, image reading processing, and calibration processing.

In the OPEN process, the upper application 1006 requests the OHR driver 1005 to open the driver. In response, the OHR driver 1005 references the registry 1004 to obtain the folder path of the "OHR" folder ("C:\OHR"), and based on that folder path, accesses the "OHR" folder in the storage 1003 to obtain the correction information for the OHR 1002.

In the image reading process, after the OPEN process is executed, the upper application 1006 requests the OHR driver 1005 to read the image. In response, the OHR driver 1005 requests the OHR 1002 to read the image. The OHR driver 1005 then acquires the image read by the OHR 1002 from the OHR 1002, corrects the image using the correction information described above, and transfers it to the upper application 1006.

During the calibration process, the upper application 1006 requests the OHR driver 1005 to close the driver. In response, the OHR driver 1005 executes the driver close command and responds to the upper application 1006 that the execution has ended. Next, the upper application 1006 requests calibration from the OHR driver 1005. Calibration is a function that creates correction information for the OHR 1002. In response to this request, the OHR driver 1005 obtains the folder path ("C:\OHR") of the "OHR" folder from the registry 1004 and requests the OHR 1002 to read images multiple times. The OHR driver 1005 then obtains from the OHR 1002 multiple images read by the OHR 1002, creates correction information from the multiple images, and overwrites and updates the correction information stored in the "OHR" folder in the storage 1003 indicated by the obtained folder path ("C:\OHR"). However, if no correction information is stored in the "OHR" folder of the storage 1003 at this time, the created correction information is stored in the "OHR" folder of the storage 1003. When the update (or storage) of the correction information is complete, the OHR driver 1005 responds to the upper application 1006 that calibration is complete.

Figure 8 is a diagram illustrating potential issues that may arise when attempting to implement a system configuration in which virtual terminals and OHRs are connected N-to-N based on an existing system configuration in which terminals and OHRs are connected one-to-one. As shown in Figure 8, this system configuration may be configured such that multiple (e.g., three) thin client terminals 1011, a server 1013 on which multiple virtual terminals 1012 corresponding to the multiple thin client terminals 1011 are configured, and multiple (e.g., two) OHRs 1014 are connected to a network 1015 such as a LAN (Local Area Network). Note that the multiple virtual terminals 1012 become connectable to the network 1015 when the server 1013 is connected to the network 1015. Each virtual terminal 1012 may be configured to include an upper-level application 1016, an OHR driver 1017, a virtual registry 1018, and virtual storage 1019. Furthermore, since each virtual terminal 1012 will use multiple OHRs 1014, it is conceivable that the virtual storage 1019 of each virtual terminal 1012 will be configured to store correction information for multiple OHRs 1014. Note that in such a system configuration, a user can operate a corresponding virtual terminal 1012 (for example, virtual terminal (#A) 1012) by operating a thin client terminal 1011 (for example, thin client terminal (#A) 1011).

However, when realizing such a system configuration, the following three problems are expected to arise.
Problem (1): Because the virtual storage 1019 of each virtual terminal 1012 is configured from a portion of the storage provided in the server 1013, there is a limit to the storage capacity that can be allocated to the virtual storage 1019 of each virtual terminal 1012. Therefore, depending on the number of OHRs 1014 used, there is a risk that the correction information of all of the OHRs 1014 cannot be stored in the virtual storage 1019 of each virtual terminal 1012.
Problem (2): When calibrating an OHR 1014 (e.g., OHR (#A) 1014) and updating the correction information, it is necessary to update the correction information of the OHR 1012 stored in the virtual storage 1019 of each virtual terminal 1012 almost simultaneously. Therefore, when updating the correction information, traffic on the network 1015 increases, and there is a risk of delays in updating the correction information in the virtual storage 1019 of some virtual terminals 1012 (e.g., virtual terminal (#B) 1012).
Issue (3): As with existing system configurations, if an "OHR" folder is created in the virtual storage 1019 of each virtual terminal 1012 and correction information for multiple OHRs 1014 is stored in that "OHR" folder, the OHR driver 1017 of each virtual terminal 1012 can access the "OHR" folder in the virtual storage 1019 based on the folder path ("C:\OHR") obtained from the virtual registry 1018, but the folder path ("C:\OHR") alone cannot identify the correction information for the OHR 1014 used by that virtual terminal 1012, and therefore the correct correction information cannot be obtained.

In light of the above situation, the present invention aims to provide a system, a correction information acquisition method, and a server that can effectively realize a system configuration in which virtual terminals and image reading devices are connected in an N-to-N ratio.

One aspect of the system is a system comprising a plurality of terminals, a server on which a plurality of virtual terminals corresponding to the plurality of terminals are constructed, a plurality of image reading devices, and a storage device in which correction information for each of the plurality of image reading devices is stored in a folder for each image reading device, wherein the virtual registry of each of the plurality of virtual terminals stores the folder path of a folder in which the correction information for the image reading device used by that virtual terminal is stored, and the correction information for each of the plurality of image reading devices is used by each of the plurality of virtual terminals when correcting an image read by that image reading device.

One aspect of the method is a correction information acquisition method in which a server is constructed in which a plurality of virtual terminals corresponding to a plurality of terminals are constructed, and each of the plurality of virtual terminals corrects an image read by a plurality of image reading devices using correction information for each of the image reading devices, and each of the plurality of virtual terminals acquires the correction information for the image reading device used by the virtual terminal from a storage device in which the correction information for each of the plurality of image reading devices is stored in each folder for each image reading device, based on a folder path stored in a virtual registry of the virtual terminal.

One aspect of the device is a server in which a plurality of virtual terminals corresponding to a plurality of terminals are constructed, and the virtual registry of each of the plurality of virtual terminals stores the folder path of a folder in which correction information for an image reading device used by the virtual terminal is stored, the folder being a folder in a storage device, and in the storage device, the correction information for each of the plurality of image reading devices is stored in each folder for each image reading device, and the correction information for each of the plurality of image reading devices is used by each of the plurality of virtual terminals when correcting an image read by the image reading device.

This invention makes it possible to effectively realize a system configuration in which virtual terminals and image reading devices are connected in an N-to-N ratio.

FIG. 1 illustrates an example of a system configuration according to an embodiment. 10 is a flowchart illustrating the flow of an OPEN process performed in a system according to an embodiment. 10 is a flowchart illustrating the flow of an image reading process performed in a system according to an embodiment. 10 is a flowchart illustrating the flow of a calibration process performed in a system according to an embodiment. 10 is a flowchart illustrating the flow of a connection destination OHR switching process performed in a system according to an embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer. FIG. 1 is a diagram illustrating an example of an existing system configuration in which a terminal and an OHR are connected one-to-one. This figure explains the problems that can be expected when trying to realize a system configuration in which virtual terminals and OHRs are connected in an N-to-N manner based on an existing system configuration in which terminals and OHRs are connected in a one-to-one manner.

The following describes an embodiment of the present invention with reference to the drawings.

Figure 1 is a diagram illustrating the configuration of a system according to one embodiment. The system 1 illustrated in Figure 1 is installed, for example, at a branch office of a financial institution such as a bank. The system 1 illustrated in Figure 1 includes multiple (e.g., three) thin client terminals 11, a server 13 on which multiple virtual terminals 12 corresponding to the multiple thin client terminals 11 are configured, and multiple (e.g., two) OHRs 14. The server 13 also includes storage 15 in which correction information for each of the multiple OHRs 14 is stored in folders. Here, the thin client terminal 11 is an example of a terminal, the OHR 14 is an example of an image reading device, and the storage 15 is an example of a storage device.

Multiple thin client terminals 11, a server 13, and multiple OHRs 14 are connected to a network 16 such as a LAN. Multiple virtual terminals 12 and storage 15 can be connected to the network 16 by connecting the server 13 to the network 16. Note that this type of system 1 also has a system configuration in which the virtual terminals 12 and OHRs 14 are connected N-to-N (many-to-many). In this type of system 1, a user can operate a corresponding virtual terminal 12 (e.g., virtual terminal (#A) 12) by operating a thin client terminal 11 (e.g., thin client terminal (#A) 11).

Storage 15 may be storage provided by server 13, as shown in FIG. 1, or may be a NAS (Network Attached Storage) connected to network 16 outside server 13. In storage 15, for example, correction information for OHR(#A) 14 is stored in an "OHR#A" folder, and correction information for OHR(#B) 14 is stored in an "OHR#B" folder.

Each virtual terminal 12 includes an upper application 17, an OHR driver 18, and a virtual registry 19. The virtual registry 19 of each virtual terminal 12 stores the folder path of a folder storing correction information for the OHR 14 used by that virtual terminal 12. For example, if OHR(#A) 14 is set as the OHR 14 to be used in virtual terminal (#A) 12 and virtual terminal (#B) 12, and OHR(#B) 14 is set as the OHR 14 to be used in virtual terminal (#C) 12, the virtual registry 19 of each virtual terminal (#A) 12 and virtual terminal (#B) 12 stores the folder path ("Z:\OHR#A") of the "OHR#A" folder storing the correction information for OHR(#A) 14, and the virtual registry 19 of virtual terminal (#C) 12 stores the folder path ("Z:\OHR#B") of the "OHR#B" folder storing the correction information for OHR(#B) 14. The correction information for each of the multiple OHRs 14 is information for correcting the state of the surrounding environment of that OHR 14 (brightness, shadows, etc.) and individual errors of that OHR 14, and is used when correcting the image read by that OHR 14.

In such a system 1, a virtual terminal 12 (e.g., virtual terminal (#A) 12) obtains correction information for an OHR 14 (e.g., OHR (#A) 14) used by the virtual terminal 12 from storage 15 based on a folder path (e.g., "Z:\OHR#A") stored in the virtual registry 19 of the virtual terminal 12.

Furthermore, when the OHR 14 used by the virtual terminal 12 (e.g., virtual terminal (#A) 12) is switched (e.g., when switched from OHR (#A) 14 to OHR (#B) 14), the folder path (e.g., "Z:\OHR#A") stored in the virtual registry 19 of the virtual terminal 12 is updated to the folder path (e.g., "Z:\OHR#B") of the folder in which the correction information of the OHR 14 after the switch is stored.

In addition, when calibration of an OHR 14 (e.g., OHR (#A) 14) is performed, the correction information for that OHR 14 stored in storage 15 is updated to correction information based on the results of the calibration.

The various processes performed by this system 1 will be explained in more detail below using Figures 2 to 5.

Figure 2 is a flowchart illustrating the flow of the OPEN process performed in a system according to one embodiment. Here, we will explain the case where the OPEN process is performed by virtual terminal (#A) 12.

In the OPEN process illustrated in Figure 2, first, the upper application 17 of the virtual terminal (#A) 12 selects the OHR 14 (the OHR 14 used by the virtual terminal (#A) 12) to connect to in response to instructions from the user of the virtual terminal (#A) 12 (thin client terminal (#A) 11) (step (hereinafter referred to as "S") 11). Here, it is assumed that the OHR (#A) 14 has been selected.

Next, the upper application 17 of the virtual terminal (#A) 12 sets the OHR (#A) 14 selected in S11 as the OHR 14 to connect to (the OHR 14 used by the virtual terminal (#A) 12) (S12).

Next, the upper application 17 of the virtual terminal (#A) 12 overwrites and updates the folder path ("Z:\OHR#A") of the "OHR#A" folder in which the correction information of the OHR(#A) 14 selected in S11 is stored with the folder path (folder path of the folder in which the correction information of the OHR 14 is stored) stored in the virtual registry 19 of the virtual terminal (#A) 12 (S13). However, if the folder path of the folder in which the correction information of the OHR 14 is stored is not stored in the virtual registry 19 of the virtual terminal (#A) 12 at this time, the folder path ("Z:\OHR#A") of the "OHR#A" folder in which the correction information of the OHR(#A) 14 selected in S11 is stored is stored in the virtual registry 19 of the virtual terminal (#A) 12 as the folder path of the folder in which the correction information of the OHR 14 is stored. Each virtual terminal 12 may be provided with virtual storage that stores information related to the folder path of the folder in which the correction information of each OHR 14 is stored, and in S13, the upper application 17 of the virtual terminal (#A) 12 may obtain from the virtual storage the folder path ("Z:\OHR#A") of the "OHR#A" folder in which the correction information of the OHR (#A) 14 selected in S11 is stored, and perform the above-mentioned overwrite update (or storage).

Next, the upper application 17 of the virtual terminal (#A) 12 requests the OHR driver 18 of the virtual terminal (#A) 12 to open the driver (S14). In response, the OHR driver 18 of the virtual terminal (#A) 12 references the virtual registry 19 of the virtual terminal (#A) 12 to obtain the folder path ("Z:\OHR#A") of the "OHR#A" folder in which the correction information for the OHR(#A) 14 is stored (S15), and then accesses the "OHR#A" folder in the storage 15 based on that folder path to obtain the correction information for the OHR(#A) 14 (S16). When S16 is completed, the OPEN process illustrated in FIG. 2 is completed.

Figure 3 is a flowchart illustrating the flow of image reading processing performed in a system according to one embodiment. Here, we will explain an example in which the image reading processing is performed by virtual terminal (#A) 12. Note that the image reading processing is performed in a state in which the OPEN processing has finished (also known as an idle state).

In the image scanning process illustrated in Figure 3, first, the upper application 17 of virtual terminal (#A) 12 requests the OHR driver 18 of virtual terminal (#A) 12 to scan an image (S21). In response, the OHR driver 18 of virtual terminal (#A) 12 requests the OHR (#A) 14 to scan an image (S22). In response, the OHR (#A) 14 scans the medium (e.g., a form) as an image and transfers the scanned image to the OHR driver 18 of virtual terminal (#A) 12 (S23).

The OHR driver 18 of the virtual terminal (#A) 12 corrects the scanned image transferred from the OHR (#A) 14 using the correction information acquired in the above-mentioned OPEN process (S24), and transfers it to the upper application 17 of the virtual terminal (#A) 12 (S25). When S25 is completed, the image scanning process illustrated in Figure 3 is completed.

Figure 4 is a flowchart illustrating the flow of the calibration process performed in a system according to one embodiment. Here, we will explain an example in which the OHR 14 to be calibrated is OHR (#A) 14, and the calibration process is performed on virtual terminal (#A) 12.

In the calibration process illustrated in FIG. 4, first, the upper application 17 of the virtual terminal (#A) 12 requests the OHR driver 18 of the virtual terminal (#A) 12 to close the driver (S31). In response, the OHR driver 18 of the virtual terminal (#A) 12 executes the driver close command and responds to the upper application 17 of the virtual terminal (#A) 12 that the execution has ended (S32).

Next, the upper application 17 of virtual terminal (#A) 12 requests the OHR driver 18 of virtual terminal (#A) 12 to calibrate OHR (#A) 14 (S33). In response, the OHR driver 18 of virtual terminal (#A) 12 obtains the folder path of the "OHR#A" folder ("Z:\OHR#A") from the virtual registry 19 of virtual terminal (#A) 12 (S34) and requests OHR (#A) 14 to read images multiple times (S35). In response, OHR (#A) 14 reads a medium (e.g., a medium for calibration) as images multiple times and transfers the multiple read images to the OHR driver 18 of virtual terminal (#A) 12 (S36).

The OHR driver 18 of the virtual terminal (#A) 12 creates correction information for the OHR (#A) 14 based on the multiple scanned images transferred from the OHR (#A) 14 (S37), and overwrites and updates the correction information stored in the "OHR#A" folder in the storage 15 indicated by the folder path ("Z:\OHR#A") obtained in S34 with the created correction information (S38). However, if no correction information is currently stored in the "OHR#A" folder in the storage 15, the created correction information is stored in the "OHR#A" folder in the storage 15. When S38 is completed, the OHR driver 18 of the virtual terminal (#A) 12 responds to the upper application 17 of the virtual terminal (#A) 12 that calibration is complete (S39). When S39 is completed, the calibration process illustrated in FIG. 4 is completed. Note that if image scanning is to be performed after this, a driver OPEN process is performed before the image scanning process.

Figure 5 is a flowchart illustrating the flow of the connection destination OHR switching process performed in a system according to one embodiment. Here, we will explain an example in which the connection destination OHR switching process is performed in virtual terminal (#A) 12 to switch the connection destination OHR 14 of virtual terminal (#A) 12 from OHR (#A) 14 to OHR (#B) 14.

In the connection destination OHR switching process illustrated in Figure 5, first, the upper application 17 of virtual terminal (#A) 12 requests the OHR driver 18 of virtual terminal (#A) 12 to close the driver (S41). In response, the OHR driver 18 of virtual terminal (#A) 12 executes the driver close command and responds to the upper application 17 of virtual terminal (#A) 12 that the execution has ended (S42).

Next, the upper application 17 of the virtual terminal (#A) 12 selects the OHR 14 (the OHR 14 used by the virtual terminal (#A) 12) to be the connection destination after switching, in response to instructions from the user of the virtual terminal (#A) 12 (thin client terminal (#A) 11) (S43). Here, it is assumed that OHR (#B) 14 has been selected.

Next, the upper application 17 of the virtual terminal (#A) 12 sets the OHR (#B) 14 selected in S43 as the OHR 14 to connect to (the OHR 14 used by the virtual terminal (#A) 12) (S44).

Next, the upper application 17 of the virtual terminal (#A) 12 overwrites and updates the folder path ("Z:\OHR#B") of the "OHR#B" folder in which the correction information of the OHR (#B) 14 selected in S43 is stored with the folder path ("Z:\OHR#A") stored in the virtual registry 19 of the virtual terminal (#A) 12 (S45).

Next, the upper application 17 of the virtual terminal (#A) 12 requests the OHR driver 18 of the virtual terminal (#A) 12 to open the driver (S46). In response, the OHR driver 18 of the virtual terminal (#A) 12 references the virtual registry 19 of the virtual terminal (#A) 12 to obtain the folder path ("Z:\OHR#B") of the "OHR#B" folder in which the correction information for the OHR (#B) 14 is stored (S47), and based on that folder path, accesses the "OHR#B" folder in the storage 15 to obtain the correction information for the OHR (#B) 14 (S48). When S48 ends, the connection destination OHR switching process illustrated in FIG. 5 ends.

As described above, according to the system 1 of this embodiment, the correction information for each OHR 14 is stored in the storage 15 for each folder, so there is no need to store the correction information for all OHRs 1014 for each virtual terminal 1012, as in the system configuration described using Figure 8. Therefore, the storage capacity required to store the correction information for the OHRs 14 in the server 13 can be reduced, and the above-mentioned problem (1) does not exist.

Furthermore, according to system 1 of this embodiment, when calibration of OHR 14 is performed and correction information is updated, it is only necessary to update the correction information stored in a single corresponding folder in storage 15, and there is no need to update the correction information stored in a folder in virtual storage 1019 of each virtual terminal 1012 as in the system configuration described using Figure 8. Therefore, when updating correction information, traffic on network 16 does not increase, and the above-mentioned problem (2) does not exist.

Furthermore, according to the system 1 of this embodiment, the virtual registry 19 of each virtual terminal 12 stores the folder path of a folder that stores only the correction information of a single OHR 14, so there is no problem such as problem (3) described above in the system configuration described using Figure 8.

In this way, system 1 according to this embodiment can effectively realize a system configuration in which virtual terminals 12 and OHRs 14 are connected in an N-to-N ratio.

In the system 1 according to this embodiment, the server 13 may be realized, for example, by a computer having the hardware configuration shown in FIG. 6.

Figure 6 is a diagram illustrating the hardware configuration of a computer. The computer 100 illustrated in Figure 6 includes a processor 101, memory 102, input device 103, output device 104, storage device 105, portable storage medium drive device 106, communication interface 107, and input/output interface 108, each of which is connected to a bus 109 and can send and receive data to and from each other.

The processor 101 is a CPU (Central Processing Unit) or the like, and performs various processes by executing OS (Operating System) programs and application programs. The memory 102 includes RAM (Random Access Memory) and ROM (Read Only Memory). The RAM temporarily stores portions of the programs executed by the processor 101. The RAM is also used as a working memory area for the processor 101. The ROM stores programs executed by the processor 101 and various data required to execute the programs.

The input device 103 is a keyboard, mouse, touch panel, etc. The output device 104 is an LCD display, etc.

The storage device 105 is a device that stores data, such as an HDD (Hard Disk Drive) or SSD (Solid State Drive). The portable storage medium drive 106 drives the portable storage medium 106a and accesses its stored contents to read and write data. The portable storage medium 106a is a memory device, flexible disk, optical disk, magneto-optical disk, etc. This portable storage medium 106a also includes a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc), a Blu-ray Disc, a USB (Universal Serial Bus) memory, an SD card memory, etc.

The communication interface 107 is connected to the network 16 and is an interface for communicating with external devices (e.g., thin client terminal 11 and OHR 14) connected to the network 16.

The input/output interface 108 is connected to an external device (e.g., an external storage device) and is an interface for inputting and outputting data to and from the external device.

In such a computer 100, the programs executed by the processor 101 and various data required to execute the programs may be stored not only in the memory 102, but also in the storage device 105 or portable storage medium 106a. Furthermore, the programs executed by the processor 101 and various data required to execute the programs may be stored in one or more of the memory 102, storage device 105, and portable storage medium 106a from an external device via the network 16 and communication interface 107.

Furthermore, the computer 100 is not limited to the example shown in FIG. 6, and may be configured with one or more of the components shown in FIG. 6, or may be configured without some of the components. For example, the computer 100 is not limited to one processor 101, but may be configured with multiple processors. Furthermore, the computer 100 does not need to be equipped with the input device 103 and the output device 104.

The computer 100 may also be configured to include hardware such as a microprocessor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field-Programmable Gate Array). For example, the processor 101 may be implemented using at least one of these pieces of hardware.

Note that if the server 13 is implemented by the computer 100, the storage 15 may be implemented by, for example, the storage device 105. Furthermore, the multiple virtual terminals 12 may be implemented by the processor 101 executing a program, etc.

The thin client terminal 11 may also be realized, for example, by a computer having the hardware configuration shown in FIG. 6.

The above describes an embodiment of the present invention, but the present invention is not limited to the above embodiment, and various improvements and modifications are possible without departing from the spirit of the present invention.

1 System 11 Thin client terminal 12 Virtual terminal 13 Server 14 OHR
15 Storage 16 Network 17 Upper layer application 18 OHR driver 19 Virtual registry 100 Computer 101 Processor 102 Memory 103 Input device 104 Output device 105 Storage device 106 Portable storage medium drive device 106a Portable storage medium 107 Communication interface 108 Input/output interface 109 Bus 1001 Terminal 1002 OHR
1003 Storage 1004 Registry 1005 OHR driver 1006 Upper application 1011 Thin client terminal 1012 Virtual terminal 1013 Server 1014 OHR
1015 Network 1016 Upper application 1017 OHR driver 1018 Virtual registry 1019 Virtual storage

Claims (8)

Multiple devices and
a server in which a plurality of virtual terminals corresponding to the plurality of terminals are constructed;
a plurality of image reading devices;
a storage device in which correction information for each of the plurality of image reading devices is stored in a folder for each image reading device ;
Equipped with
a virtual registry of each of the plurality of virtual terminals stores a folder path of a folder in which correction information of an image reading device used by the virtual terminal is stored;
the correction information of each of the plurality of image reading devices is used when each of the plurality of virtual terminals corrects an image read by the corresponding image reading device;
A system characterized by: The storage device is provided in the server.
2. The system of claim 1. the virtual terminal acquires, from the storage device, correction information for the image reading device used by the virtual terminal, based on the folder path stored in the virtual registry of the virtual terminal;
3. The system according to claim 1 or 2. When the image reading device used by the virtual terminal is switched, the folder path stored in the virtual registry of the virtual terminal is updated to the folder path of the folder in which the correction information of the image reading device after the switch is stored.
4. The system according to claim 1, wherein the system comprises: When calibration of the image reading device is performed, the correction information of the image reading device stored in the storage device is updated to correction information based on the result of the calibration.
5. The system according to any one of claims 1 to 4, characterized in that: the image reading device is an overhead reader,
The terminal is a thin client terminal.
6. The system according to any one of claims 1 to 5, characterized in that: In a server in which a plurality of virtual terminals corresponding to a plurality of terminals are constructed , and each of the plurality of virtual terminals corrects an image read by a plurality of image reading devices using correction information for each of the plurality of image reading devices, each of the plurality of virtual terminals acquires correction information for the image reading device used by the virtual terminal from a storage device in which the correction information for each of the plurality of image reading devices is stored in a folder for each image reading device , based on a folder path stored in a virtual registry of the virtual terminal.
A correction information acquisition method comprising: Multiple virtual terminals are created to support multiple devices.
a virtual registry of each of the plurality of virtual terminals stores a folder path of a folder in which correction information of an image reading device used by the virtual terminal is stored;
the folder is a folder in a storage device,
In the storage device, the correction information for each of the plurality of image reading devices is stored in a folder for each image reading device ,
the correction information of each of the plurality of image reading devices is used when each of the plurality of virtual terminals corrects an image read by the corresponding image reading device;
A server characterized by: