JP2000276554A - System and method for receiving request, and ocr form - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a request reception system which performs quicker and more accurate processing, a request receiving method and an OCR form and also to provide a document request system which secures the system security. SOLUTION: In a branch office 15, facsimiles 10A to 10C for request are installed. In a head office 17, a receiving terminal 20 which receives requests from the respective facsimiles 10A to 10C through a facsimile network 11 and performs various processing, an accumulating terminal 30 which accumulates results processed by the terminal 20, a printer 40 and a facsimile 50 for confirming received contents are installed. An OCR recognizing part 22 recognizes contents described in an OCR form received by a modem 21 as a specified character. An operating part 23 grasps requested contents on the basis of results recognized by the part 22 and performs various processing. A user DB 24, a reference sheet DB 25 and a received content DB 31 respectively store prescribed data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a request receiving system using an OCR function.

[0002]

2. Description of the Related Art In a company or the like, a department in charge of a head office collectively manages various documents (for example, system documents, manuals, etc.) distributed in a company, and a branch office sends a desired document to a head office. Requests are made at any time using a facsimile or the like. In that case, the requester of the branch office must use a dedicated OC
The name of the requester and the contents of the request are written on the R form according to a predetermined method, and the OCR form is facsimile-transmitted to the head office. The OCR device installed at the head office recognizes a character on the OCR form received by facsimile and outputs the recognition result. The request receptionist at the head office refers to the content of the output recognition result and determines whether or not the request can be accepted (for example, whether there is a mistake in entry of the requester or recognition error of the OCR device, and whether the requester is an employee). Or whether the requested document may be distributed to the requestor). Then, the receptionist notifies the branch office of the determination result and performs a process according to the determination result.

[0003]

In the conventional system, the requester side performs the above-mentioned OC in the document request procedure.
There is a problem that an R form must be prepared in advance. Also, in this OCR form, from the viewpoint of improving the accuracy of OCR recognition, a guide for the character entry position is indicated by a very thin line in the character entry field, and even if the user attempts to create the OCR form, There is a problem that an extremely thin line cannot be generally created even by using an ordinary word processor or the like. In addition, the receptionist has a problem that it takes a long time to perform the determination because the receptionist determines whether or not the reception is possible by hand or manually. As a result, the notification of the acceptability from the receptionist to the requester is also delayed.

[0004] Further, whether or not the requester is an employee (ie, a person having a legitimate request right) is determined by the received OC.
This is performed based only on the requester name (or requester identification code) entered in the R form. Therefore, there is a possibility that an unauthorized third party (for example, a person outside the company, etc.) may use his / her facsimile, request the name of an employee and obtain an in-house document, and in the security aspect of preventing misuse of the system. There is also a problem.

The present invention has been made in view of the above circumstances, and has as its first object to provide a request receiving system, a request receiving method, and an OCR form for performing simpler and more accurate processing. It is a second object of the present invention to provide a request reception system, a request reception method, and an OCR form that ensure system security by automatically determining the validity of a requester.

[0006]

According to a first aspect of the present invention, there is provided a request transmitting apparatus, which receives a transmitted request, and recognizes a received image of the request by OCR. A request receiving system that outputs a result of the OCR recognition, and a request receiving system that includes a relay network that relays the request transmitting device and the request receiving device. Request reception, characterized by comprising reception condition storage means for storing reception conditions, and reception permission / non-permission determining means for determining whether or not the request can be received by using the result of the OCR recognition and the reception conditions. System.

In order to solve the above-mentioned problem, the invention according to claim 2 is the request receiving system according to claim 1, further comprising a result notifying unit for notifying the request transmitting device of a result of the determination whether the request is accepted. The present invention provides a request receiving system characterized in that

[0008] In order to solve the above-mentioned problems, the invention according to claim 3 is the request reception system according to claim 1, wherein the identification code of the requester who is recognized to be able to use the request reception system; An identification code storage unit that stores a communication identification code used for communication of the request form transmitting device to be used by the requester in pairs, and from the relay network,
Identification code acquiring means for acquiring a communication identification code of the request form transmitting device which transmitted the request form, wherein the acceptability determining means comprises an identification code of the requester recognized by OCR and the identification code storage means And the requester identification code stored in the request transmission device acquired from the relay network, the communication identification code of the request transmission device and the communication identification code of the request transmission device stored in the identification code storage means. The request reception system is characterized in that it is determined whether or not the request can be received based on whether or not the request matches.

According to a fourth aspect of the present invention, in the request accepting system of the first aspect, an object identification code, which is an identification code of the object of the request, has a predetermined relationship. It has a plurality of numbers having, comprising a relationship determination means for determining whether the numbers constituting the object identification code OCR recognized has the predetermined relationship, the reception condition storage means, The recognizable object identification code is stored, and the acceptability determination unit is configured to:
Whether or not the same code as the OCR-recognized object identification code is stored in the reception storage means determines whether or not the reception is possible, and the result notification means is determined to be unacceptable by the reception possibility determination means, And a request receiving system for transmitting, to the request transmitting device, a notification of an entry error of a person who wrote the request, when the relation determining unit determines that the predetermined relationship exists. is there.

[0010] In order to solve the above-mentioned problem, the invention according to claim 5 receives a request transmitted from a request transmitting device, recognizes a received image of the request by OCR, and
In a request receiving method for outputting a result of CR recognition, a receiving condition for enabling the request to be received and the OC
A request accepting method characterized by comprising a step of judging whether or not to accept the request using the result of R recognition.

[0011] In order to solve the above-mentioned problem, the invention according to claim 6 is a method according to claim 5, wherein
A request receiving method comprising a step of transmitting a result of the determination as to whether or not the request can be received to the request transmitting device.

[0012] In order to solve the above-described problem, the invention according to claim 7 is a method according to claim 5, wherein
A step of determining whether or not the numerals constituting the OCR-recognized object identification code have the predetermined relationship; and the step of determining whether or not the acceptance is acceptable, wherein the OCR-recognized object identification code is Depending on whether or not it is stored in advance,
The step of judging acceptability and notifying the result is the step of judging that the acceptability is judged to be unacceptable by the step of judging the acceptability, and the step of judging the relationship determines that the predetermined relationship exists. 7. A notification that a person who wrote the request has made a mistake in entry to a request transmission device.
This is the request reception method described.

[0013] In order to solve the above-mentioned problems, the invention according to claim 8 is a method according to claim 5, wherein
Storing the requester's identification code and a communication identification code used for communication of the request form transmitting device to be used by the requester in pairs, and transmitting the request form from the relay network. Obtaining the communication identification code of the request form transmitting device, and the step of determining whether or not the request can be accepted includes:
The identification code of the requester recognized by the CR matches the requester identification code stored in the identification code storage means, and the communication identification code and the identification of the request form transmitting device acquired from the relay network. A request accepting method characterized in that acceptability is determined based on whether or not a communication identification code of the request form transmitting device stored in a code storage unit matches.

[0014] In order to solve the above-mentioned problem, an invention according to claim 9 is an OCR form used in the request accepting method according to claim 56, wherein the OCR form is described at a predetermined position to be subjected to OCR recognition. An OCR form that has an entry frame and an entry position guide that is described at a position that is not subject to OCR recognition and that indicates the position of a character to be entered in the entry frame.

[0015]

DETAILED DESCRIPTION OF THE INVENTION [1. Configuration] FIG. 1 shows a functional configuration of a request receiving system according to an embodiment of the present invention. In this system, "document" will be described as an example of a request object, but "document" is hereinafter referred to as "reference document". According to the figure, each user 16A-1 in the branch office 15
Request facsimile machines 10A to 10C are installed in 6C. These facsimile machines 10A to 10C transmit OCR forms indicating various requests to the head office 17, and receive various notifications such as a notice of acceptability from the head office 17.

At the head office 17, each facsimile 10A-1
A reception terminal 20 that receives the contents of the OCR form transmitted from the OC via the facsimile network 11 and performs various processes according to the contents is installed. Also, a totaling terminal 30 that stores and totals the content received by the receiving terminal 20, a printer 40 that outputs the totaling result of the totaling terminal 30, and a head office 1
A confirmation facsimile 50 for the receptionist 7 to confirm the contents of the request from the branch office 15 is installed. This confirmation facsimile 50 is provided by
This is for confirming the requested contents.

Hereinafter, each component of the reception terminal 20 constituting the reference request system will be described. Reference numeral 21 denotes a facsimile modem, which is a request facsimile 10A to 10A.
Facsimile network 11 reads the contents of the OCR form read by C
Over the Internet, or request facsimile 10A
For example, various notifications are transmitted to 10C. Reference numeral 22 denotes an OCR recognition unit that recognizes a received image of the OCR form received by the modem 21 as characters.

Reference numeral 23 denotes an arithmetic unit which determines the contents of a request based on the result recognized by the OCR recognition unit 22 and performs various processes. For example, according to the recognition result of the OCR recognition unit, the following databases 24 and 25 are searched, or predetermined data is registered or deleted. Various determinations are made with reference to the recognition result and the registered contents of each DB.
Further, it instructs the modem 21 to transmit various notifications to the facsimile machines 10A to 10C.

Reference numeral 24 denotes a user DB, and each user 16A
Attribute information about .about.16C is stored. Here, the “user” refers to a unit that can be a unit of the requester, and may be, for example, each department in the company (sales department, general affairs department, etc.) or each affiliated company. , May be each employee. In this embodiment, each department will be described as each user.

The file structure of the user DB 24 will be described with reference to FIG. According to the figure, the user DB
24, a facsimile number, an organization code, a telephone number, an organization name (company name), a postal code, an address, a building name, a person-in-charge name (user name) to be used in this system for each of the users 16A to 16C, The registration date (the date when the user attribute information is stored in the user DB 24) and the like are stored.

Each of the users 16A to 16C is required to use a facsimile registered in the user DB 24 for each user when making a request for the standard. If each of the users 16A to 16C makes a request using a facsimile other than the registered facsimile, the accepting terminal 20 transmits an error notification to the facsimile of the transmission source of the request. Does not progress.

Reference numeral 25 denotes a reference book attribute DB which stores attribute information managed by the head office 17 for each of the reference books. The file structure of the reference book attribute DB will be described with reference to FIG. According to the figure, the reference book attribute DB 25 stores the reference book number, reference book name, edition number, warehouse position, number of base papers, sales price, establishment date, establishment organization, establishment organization contact number for each reference book. A distribution management number and the like are stored.

The reference book number is an identification number of each reference book in a company that adopts this reference book request receiving system. The warehouse position is a number indicating the position of the warehouse that stores each reference book, and the reference book distribution person performs reference book distribution work based on this warehouse position. The establishment date is the date on which the head office 17 can receive requests from the users 16A to 16C. The establishment organization contact number is the communication of the organization (company) that created each standard. Number (phone number). The distribution management number is an identification number indicating whether reception from each user is possible. This is because the standard is under the control of the head office 17, but it may or may not be distributed to each of the users 16A to 16C, and “1” is registered in the distribution management number of the standard that can be distributed, “0” is registered as the distribution management number of the reference book that cannot be distributed. When receiving the request, the calculation unit 23 searches the reference book attribute DB 25 to check the distribution management number, and normally receives only the request relating to the reference book that can be distributed.

The totaling terminal 30 is configured such that the receiving terminal 20
The contents received from 6A to 16C are acquired, and the received contents D
Stored in B31. In addition, the tallying terminal 30 receives the content DB
31 is retrieved, and the content received within a predetermined period is extracted as a totaling result. The result of the aggregation is transmitted to the printer 40 and output.

The file structure of the reception content DB 31 is
This will be described with reference to FIG. According to the figure, the reception content DB 27 stores a reception number, a facsimile number, a telephone number, a reference book number, the number of received copies, and the like.

The reception number is an identification number given each time the reception terminal 20 receives a request, and is composed of, for example, a number indicating the date and time when the reception terminal 20 receives the request. The facsimile number is the facsimile number of the request facsimile that transmitted the request. The modem 21 receives each request from the facsimile network 11 when receiving the request.
In order to obtain the facsimile number of 10C, the obtained facsimile number is stored in the reception content DB 31. The request receiving system can request six types of reference documents by one facsimile transmission, and stores the reference document number and the number of copies for each type of the reference documents.

Next, the structure of a reference book number assigned to each reference book will be described with reference to FIG. According to the figure, the reference book number is composed of seven numbers. The number group from the first digit to the sixth digit of the reference book number is uniquely assigned to each reference book. The number at the end (the seventh digit) of the reference book number is the first digit of the sum of the numbers in the first to sixth digits. For example,
In FIG. 4, the sum of the first to sixth digits is "21".
The number in the ones place of "21" is "1" as the last digit of the reference book number. The number at the end is used for parity check by the arithmetic unit 23.

Hereinafter, the parity check will be described in detail. The parity check by the arithmetic unit 23 is to calculate the sum of each of the first to sixth digits in the reference book number recognized by the OCR recognition unit 22, and to calculate the first digit of the sum and the OC.
R is compared with the last digit of the recognized reference book number to determine whether the two numbers match (if they match, OK
If they do not match, NG) is determined.

On the other hand, when the reference document is requested, the calculation unit 23 uses the reference document number recognized by the OCR as a search key, and
The reference book attribute DB 25 is searched.

Parity check result and reference book attribute DB
Using the 25 search results, the following determination can be made. In the case of "reference document identification number present" and "parity check OK", it can be determined that the OCR-recognized reference document number is correctly recognized. Further, the case of “parity check NG” with “with reference document identification number” is impossible.

In the case of "no reference book identification number" and "parity check NG" (for example, when the stored reference book number is "1234561" and the reference book number recognized by OCR is "1234562") It is considered that either the requester's entry error or the OCR recognition unit 22 misrecognizes the cause. However, it cannot be determined which is the true cause.

In the case of "parity check OK" without "reference book identification number" (for example, when the stored reference book number is "1234561" and the OCR recognized reference book number is "1234572") OCR recognition unit 22
It is extremely unlikely that a false recognition of the result would result in "no reference book identification number". This is because the reference book number correctly entered by the requester is erroneously recognized, and as a result of the erroneous recognition, it is unlikely that the reference book number will pass the parity check.

For example, even though the requester has entered a correct reference book number of "1234561", the OCR recognition unit 22
Is erroneously recognized as “1234572”. In such a case, if the OCR recognizing unit 22 first erroneously recognizes the numeral “6” in the sixth digit as “7”, it must erroneously recognize “1” in the seventh digit as “2”. As described above, the OCR recognizing unit 22 compares two of the numbers of the seven-digit reference book number with the parity check O as a result.
It may be considered that the possibility of misrecognition such as K is extremely low. Therefore, it can be almost determined that the requester's entry error is the cause of "no reference book number", and only the entry error need be resolved, and the subsequent processing is promptly performed.

The OCR form used in this system is:
As shown in FIGS. 6, 7, and 8, there are three types. FIG. 6 shows an OC used for user registration or deletion in this system.
This shows an R form. Each of the users 10A to 10C is required to register as a user in this system before making a request for the standard. The four identical numbers in the upper right corner of the form are O
This is a number representing the type of the CR form (hereinafter referred to as a form type code). The form for user registration or deletion has a form type code of "0", and "0000", which is a sequence of four such codes, is printed in advance on the OCR form.

The OCR recognition unit 22 sets the form type code to OC.
By recognizing R, it is determined what request is made. At this time, if the OCR recognizing unit 22 can recognize at least one of the four consecutive form type codes, the calculation unit 23 determines the type of the form according to the recognized form type code. In this way, the possibility that the form type cannot be recognized is reduced, and the reliability of the system is improved. This is the same in FIGS. 7 and 8.

In the user registration / deletion form, the requester:
First, whether to perform the process of registering or deleting a user is designated by a “レ” mark. Hereinafter, a predetermined organization code, an organization name (company name),
Telephone number, facsimile number, postal code, address, building name, person in charge (user name), and OCR
Enter the name of the person who fills out the form.

FIG. 7 shows an OCR form used when requesting a standard from the head office 17. The form type code of “2” is attached to the OCR form of the standard document request, and “222”
2 "is printed in advance. The creator fills in the organization code, organization name, telephone number of the user making the request, and the reference book number, reference book name, and number of copies of the requested reference book. These organization codes, organization names, and telephone numbers are all registered by prior user registration.

In the standard document request receiving process, which is the main process of this system, the user is specified by the organization code and the telephone number, and the standard is specified by the standard number. It is important to enter the code, telephone number and reference number exactly (especially each letter at regular intervals). For this reason, there are pawls 60 outside the boxes of the entry fields for these entry items, which serve as guidelines for the intervals between the entered characters. The writer uses the pawls 60 as a guide and writes between adjacent pawls such that the characters are spaced at equal intervals. By filling in like that, O
The recognition accuracy of the CR recognition unit 22 is improved. In addition, this nail | claw may be provided in another description column.

The OCR form can be created by a requester or the like using a document creating device such as a word processor. This is because the positions and dimensions of the description fields (description fields such as an organization code, an organization name, etc.) and the description items are defined in advance by the system designer, and the requester or the like may create them in accordance with those regulations. Because. Furthermore, it is not necessary to provide a character entry guide using a very thin line in the character description field as in the related art, but a nail 60 using a dark line may be created outside the character description field. Therefore, even if there is no dedicated OCR form, the requester can create it by himself. This is the same in FIGS. 6 and 8.

FIG. 8 shows an OCR form used when making various inquiries to the head office 17. A form type code of “7” is attached to the inquiry form, and “7777”
Are printed in advance. The requester fills in the organization name, name, facsimile number, telephone number, and inquiry contents. The content of the inquiry is, for example, an inquiry as to whether or not the desired standard is managed by the head office 17.

[2. Operation] Next, an operation example using the system will be described with reference to FIG. Step SP11
Then, the user 16A, for example, requests the facsimile 10
Using A, the OCR form in which the requested contents are entered is transmitted by facsimile to the head office 17. At step SP12, the modem 21 of the reception terminal 20 sets the facsimile network 11
The OCR form is received via the. In step SP13, the OCR recognition unit 22 of the reception terminal 20
A process for recognizing the contents of the CR form as characters is performed.

In step SP14, the arithmetic section 23 acquires the result of the OCR recognition processing in step SP13,
It is determined whether all the characters on the R form have been recognized. As a result of this determination, if there is a character that has not been recognized,
Proceeding to step SP15, the arithmetic unit 23 sends the request facsimile 1 via the modem 21 and the facsimile network 11.
An error notification indicating that there is an unrecognizable character is transmitted to 0A and the confirmation facsimile 50. The user 16A and the receptionist at the head office 17 that have received the error notification perform predetermined operations such as checking and correcting characters. If it is determined in step SP14 that all characters have been recognized,
According to the form type code of the recognized OCR form, the process proceeds to any of user registration / deletion processing, reference request processing, and inquiry processing.

The operation of the user registration / deletion process will be described with reference to FIG. In step SP21, the calculation unit 23 determines whether the requested processing is user registration or deletion based on the recognition result by the OCR recognition unit 22. As a result of the determination, if the requested processing is user registration, the process proceeds to step SP22, where the calculation unit 23 searches the user DB 24 using the organization code, telephone number, and facsimile number as search keys, and registration is requested. It is determined whether the user is already registered.

If the result of determination in step SP22 is that the user has already been registered, the operation proceeds to step SP23, where the arithmetic unit 23 transmits an error notification to the request facsimile 16A indicating that double registration is not possible. If the result of determination in step SP22 is that the user has not been registered, step S22
Proceeding to P24, the calculation unit 23 stores the OCR-recognized contents in the user DB 24 as user attribute information.

When the storing process is completed, step SP25
Then, the arithmetic unit 23 transmits a result notification indicating completion of user registration to the request facsimile 16A. This result notification is, for example, a notification as shown in FIG. User 1
6A can confirm from the result notification that the user registration has been normally processed.

On the other hand, the result of the determination in step SP21 is
If the user is to be deleted, the process proceeds to step SP26,
The calculation unit 23 searches the user DB 24 using the organization code, the telephone number, and the facsimile number as search keys, and determines whether the attribute information of the user whose deletion is requested is stored in the user DB 24.

As a result of the determination, if there is no corresponding user, the process proceeds to step SP29, and the arithmetic unit 23 transmits an error notification to the request facsimile 16A that the corresponding user is not registered. Step SP26
As a result of the determination, if there is attribute information of the corresponding user, the process proceeds to step SP27, and the arithmetic unit 23
Delete the attribute information of the user stored in. And
In step SP28, the arithmetic unit 23 transmits a result notification indicating that the user has been deleted to the request facsimile 16A. This result notification is obtained by registering the result notification shown in FIG.
Is replaced with “delete”.

Next, the operation of the reference document request processing will be described with reference to FIG. In step SP31, the calculation unit 23 searches the user DB 24 using the facsimile number of the request facsimile 16A acquired from the facsimile network 11 as a search key. In step SP32, as a result of the search, it is determined whether or not the facsimile number of the request transmission source is registered in the user DB.

As a result of the judgment, if it is not registered,
Proceeding to step SP33, the arithmetic unit 23 transmits an error notification to the request facsimile 16A and the confirmation facsimile 50. This error notification is, for example, a notification as shown in FIG. The person who has requested the standard and the receptionist at the head office 17 can confirm the reason why the request was not received by the notification of the result. If the result of the determination is that the registered facsimile number has been registered, the operation section 23 proceeds to step SP34 and compares the organization code and telephone number of the registered facsimile number with the OCR-recognized organization code and telephone number. Then, it is determined whether or not they match. That is, if they match, it is determined that the user is a valid user, and if they do not match, it is determined that the user is not a valid user.

If the result of determination in step SP 34 is that the user is not a valid user, the flow proceeds to step SP 33, where
3 transmits an error notification indicating that the user has not been registered to the request facsimile 16A and the confirmation facsimile.

If it is determined in step SP31 that the request is valid, the process proceeds to step SP35, where the arithmetic unit 23 uses the OCR-recognized reference book number as a search key to store the reference book attribute DB 25 in the reference book attribute DB 25. Search for.

In step SP36, the arithmetic unit 23 determines whether there is a corresponding reference document as a result of the search in step SP31.

As a result of the determination, if there is no corresponding reference document, the process proceeds to step SP37, and the arithmetic unit 23 performs a parity check on the reference document number recognized by the OCR.
That is, the calculation unit 23 calculates the six digits from the first digit of the reference book number.
The sum of the digits in the digit is calculated, and the first digit of the sum is compared with the last digit of the OCR-recognized reference book number. If the two numbers match, it is determined that the parity check is OK and the process proceeds to step SP38,
If they do not match, it is determined that the parity check is NG, and the process proceeds to step SP39.

At step SP38, as described above, it is considered that there is an entry error by the entry person, so the arithmetic unit 23 transmits an error notification to that effect to the request facsimile 16A. The error notification is, for example, a notification as shown in FIG. 14, and the writer corrects a typographical error and transmits it again by facsimile.

In step SP39, the operation unit 23
Sends an error notification indicating that there is no requested reference document number to the request facsimile 16A and the confirmation facsimile 50A.
Send to The error notification transmitted to the confirmation facsimile 50 is, for example, a notification as shown in FIG.

As a result of the determination in step SP36, if the required reference document is stored,
In 40, the operation unit 23 sets the attribute information of the reference
By referring to the distribution management number, it is determined whether the requested standard can be distributed. That is, if the distribution management number is “1”, it is determined that distribution is possible, and if “0”, it is determined that distribution is impossible.

If the result of this determination is that the requested reference cannot be distributed, the operation proceeds to step SP33 and
Sends an error notification to the request facsimile 16A and the confirmation facsimile 50 that the requested standard is undistributable. If the result of the determination indicates that the requested reference can be distributed, the process proceeds to step SP41.

In step SP41, the arithmetic unit 23 sets O
Based on the result of the CR recognition, a total sum of the required number of copies of each standard is calculated. Then, it is determined whether or not the calculated total total matches the total total recognized by the OCR. As a result of the determination, if they do not match, the process proceeds to step SP33, and the arithmetic unit 23 transmits an error notification indicating that the sum does not match to the request facsimile 16A and the confirmation facsimile 50. The error notification transmitted to the confirmation facsimile 50 is, for example, a notification as shown in FIG. If the result of the determination is that they match, the process proceeds to step SP42.

In step SP42, the arithmetic unit 23 instructs the totalizing terminal 30 to search the reception content DB 31. In the search of the reception content DB 31, a range of a certain period is determined in advance. For example, a period of one week is set, and the totaling terminal 30 searches for contents of reception within the past week. This is to prevent a double request due to an error of the requester or the like.

In step SP43, it is determined whether or not there is any content identical to the content requested this time as a result of the search. As a result of the determination, if there is the same request, the process proceeds to step SP33, and the arithmetic unit 23 sets the request facsimile 1
An error notification indicating a double request is transmitted to 6A and the confirmation facsimile 50. The error notification transmitted to the request facsimile 16A is, for example, a notification as shown in FIG. If the result of the determination is that there is no identical request, the flow proceeds to step SP44.

At step 44, the received content recognized by the OCR is stored in the received content DB 31. In step 45, the calculation unit 23 transmits a result notification indicating that the reception has been completed to the request facsimile 16A and the confirmation facsimile 50. The result notification transmitted to the request facsimile 16A is, for example, a notification as shown in FIG.

Next, the flow of the inquiry process will be described with reference to FIG. In step SP61, the calculation unit 23 transmits the result of the OCR recognition to the confirmation facsimile 50. In step SP62, the calculation unit 23 sends a notification that the inquiry slip has been received to the request facsimile 1
6A. [3. Modifications] [3-1. First Modification] In the above-described embodiment, the system related to the request for the standard (that is, the document) is not limited to the document. Good. [3-2. Second Modification] In the above-described embodiment, the parity check is performed only on the reference book number (that is, the identification code of the requested object). However, not only the reference book number but also the user identification code given to each user. Etc. may be performed.

[0063]

As described above, according to the present invention, it is possible to provide a request receiving system, a request receiving method, and an OCR form that perform quicker and more accurate processing. Further, according to the present invention, it is possible to provide a request receiving system, a request receiving method, and an OCR form that ensure system security.

[Brief description of the drawings]

FIG. 1 is a diagram showing a functional configuration of a request receiving system according to an embodiment of the present invention.

FIG. 2 is a diagram showing a file configuration of a user DB in the embodiment.

FIG. 3 is a diagram showing a file configuration of a reference book DB in the embodiment.

FIG. 4 is a diagram showing a file configuration of a request content DB in the embodiment.

FIG. 5 is a diagram showing a configuration of a reference book number in the embodiment.

FIG. 6 is a diagram showing a user registration form in the embodiment.

FIG. 7 is a diagram showing a reference form request form in the embodiment.

FIG. 8 is a diagram showing an inquiry form in the embodiment.

FIG. 9 is a flowchart showing an operation of a process in the embodiment.

FIG. 10 is a flowchart showing a processing operation of user registration / deletion in the embodiment.

FIG. 11 is a diagram showing a result notification in the embodiment.

FIG. 12 is a flowchart showing a reference document request processing operation in the embodiment.

FIG. 13 is a diagram showing an error notification in the embodiment.

FIG. 14 is a diagram showing an error notification in the embodiment.

FIG. 15 is a diagram showing an error notification in the embodiment.

FIG. 16 is a diagram showing an error notification in the embodiment.

FIG. 17 is a diagram showing an error notification in the embodiment.

FIG. 18 is a diagram showing a result notification in the embodiment.

FIG. 19 is a flowchart showing an operation of an inquiry process in the embodiment.

[Explanation of symbols]

10: Request facsimile, 11: Facsimile network, 15: Branch office 16: User (department), 17: Head office, 20 ...
・ Reception terminal 21 ・ ・ ・ Facsimile modem, 22 ・ ・ ・ OCR recognition unit, 23 ・ ・ ・ Calculation unit 24 ・ ・ ・ User database, 25 ・ ・ ・ Reference book attribute database 30 ・ ・ ・ Total terminal, 31 ・ ・ ・Reception contents database, 40: Printer 50: Facsimile for confirmation

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Toru Kawachi 1-9-1-1 Konan, Minato-ku, Tokyo NTT Communicationware Co., Ltd. (72) Inventor Yoshimi Shimoda Konan-ichi Minato-ku, Tokyo (9-1) Inventor Kazumi Aoki 1-9-1, Konan, Minato-ku, Tokyo F-term in the company NTT Communicationware Co., Ltd. (Reference) 5B064 AA01 AA08 5C062 AA02 AA17 AC43 AF01 AF12 5C075 BB05 CF02 FF90

Claims (9)

[Claims] A request transmitting device, receiving the transmitted request, OCR-recognizing a received image of the request,
In a request receiving system including a request receiving device that outputs a result of CR recognition and a relay network that relays the request transmitting device and the request receiving device, a receiving condition for enabling the request to be received. Request reception system, comprising: a reception condition storage unit for storing the request; and a reception permission determination unit that determines whether the request can be received using the OCR recognition result and the reception condition. . 2. The request receiving system according to claim 1, further comprising a result notifying unit for notifying the request transmitting device of a result of the determination as to whether the request can be received. 3. The request receiving system according to claim 1, wherein an identification code of the requester recognized to be able to use the request receiving system and the request transmitting device to be used by the requester. Identification code storage means for storing a communication identification code used as a pair, and an identification code acquisition means for acquiring, from the relay network, a communication identification code of the request transmitting apparatus that transmitted the request. The request acceptability determining means, wherein the identification code of the requester recognized by OCR matches the requester identification code stored in the identification code storage means, and the request form transmitting device acquired from the relay network; Determining whether or not the request can be accepted based on whether or not the communication identification code of the request form transmitting device and the communication identification code of the request form transmitting device stored in the identification code storage unit match. Stem. 4. The request receiving system according to claim 1, wherein the object identification code that is the identification code of the object of the request is:
A plurality of numbers having a predetermined relation, comprising a relation determining means for determining whether or not the numbers constituting the object identification code recognized by the OCR have the predetermined relation; The storage means stores the recognizable object identification code, and the acceptability determination means determines whether or not the same code as the OCR-recognized object identification code is stored in the reception storage means. Determining whether or not the request is acceptable; determining whether or not the request is acceptable by the acceptability determining means; and determining that the predetermined relationship is present by the relation determining means, 2. The request receiving system according to claim 1, wherein a notice of an entry error of a person who wrote the form is transmitted. 5. A request transmitted from a request transmitting device is received, and a received image of the request is OCR-recognized.
In a request receiving method for outputting a result of CR recognition, a receiving condition for enabling the request to be received;
A request receiving method, comprising a step of determining whether or not the request can be received using a result of the CR recognition. 6. The request accepting method according to claim 5, further comprising a step of transmitting a result of the acceptability determination to the request transmitting device. 7. The request accepting method according to claim 5, further comprising a step of judging whether or not a numeral constituting the object identification code recognized by the OCR has the predetermined relationship. Is determined based on whether or not the OCR-recognized object identification code is stored in advance, and the step of notifying the result is determined as unacceptable by the step of determining whether the reception is possible. And, when it is determined that there is the predetermined relationship by the process of determining the relationship,
A request accepting method for transmitting, to the request transmitting device, a notification of an entry error of a person who has entered the request form. 8. The request receiving method according to claim 5, wherein an identification code of the requester and a communication identification code used for communication of the request form transmitting device to be used by the requester are stored in pairs. And a step of obtaining, from the relay network, a communication identification code of the request form transmitting device that transmitted the request form, wherein the step of determining whether or not the request is acceptable includes the step of determining whether or not the requester has been OCR-recognized. The identification code matches the requester identification code stored in the identification code storage means, and the communication identification code of the request form transmitting device acquired from the relay network and the request stored in the identification code storage means A request accepting method characterized in that acceptability is determined based on whether or not the communication identification code of the message transmitting device matches. 9. An OCR form used in the request accepting method according to claim 5, wherein an entry frame described in a predetermined position to be subjected to OCR recognition and a position not to be subjected to OCR recognition are described. And an entry position guide indicating a position of a character to be entered in the entry frame,
Thus, an OCR form that can be created by the document creation device.