JP2000022863A - Communication system and communication method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a communication system capable of improving the simplicity and accuracy of the business processing of the preparation of a cover page by a sender in the case of sending a reply and performing distribution for a received message or the like. SOLUTION: In this communication system, the image 4401 of the received cover page and 'TSI: 034512345' as facsimile information 4401 are received, a character recognition processing in the cover page 4401 is performed in 4402, obtained information is referred to in a data base, and 'opposite party: Suzuki', 'use replay format 4406' and 'greeting sentence 'received as specifications' are judged as indicated in 4403. The 'TSI: 0345112345' of the facsimile information 4404 received in such a manner is referred to in the data base in 4405 and the information of 4403 is obtained. The cover page 4406 of the reply is prepared by reflecting the retrieved result.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a communication system comprising at least a communication terminal having a facsimile communication function and an information terminal having a database, for example, a communication system and a communication system capable of automatically creating an invoice (cover page). It is about the method.

[0002]

2. Description of the Related Art In a conventional facsimile communication system, when sending facsimile data, it is common practice to attach a cover page (cover page) before the content of a message. It has become common sense.

[0003] However, at present, the cover page is created by the sender directly by handwriting or by using an information terminal device different from the facsimile device every time.

[0004] Even when an application for automatically attaching a cover page is used, the sender must directly input the format, destination information, and greeting.

[0005]

However, the current facsimile communication system has the following problems. (1) When replying and distributing, the sender needs to create a cover page in addition to creating a message. (2) An error may occur in the cover page because the sender inputs data.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problem, and simplifies and corrects the clerical processing of creating a cover page for a sender when replying to or delivering a received message. Another object of the present invention is to provide a communication system capable of improving the communication speed.

[0007]

The present invention has, for example, the following arrangement as one means for achieving the above-mentioned object.

That is, in a communication system including a communication terminal having a communication function and an information terminal having a database, any one of return, transfer, and distribution corresponding to received data received using the communication function can be executed. And automatic creation means for automatically creating an invoice for return, transfer, and distribution from the received data at the time of response corresponding to the received data.

For example, there is provided a judgment means for judging whether or not the invoice automatically created by the automatic creation means is complete. When the invoice is judged to be incomplete, the judgment means informs the sender that the invoice is incomplete. It is characterized by requesting input of insufficient data.

[0010] For example, the automatic creation means extracts information on a return destination or a transfer destination necessary for the invoice for retrieving and responding to the received data, information on the original sender at the time of transfer, and forms the invoice. It is characterized by automatic creation.

[0011] For example, the invention is characterized in that date information and a message included in received data are character-recognized and extracted as document name information on an invoice, and an invoice is automatically created. Alternatively, a message included in the received data is subjected to character recognition, and a part of the character recognition result is designated to automatically create an invoice.

Further, for example, the automatic creation means is characterized in that the invoice format and the greeting are automatically switched and created according to the response format. Alternatively, the format of the response is one of return, transfer, and distribution.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing a configuration example of a first document distribution system according to an embodiment of the present invention. In FIG. 1, a document distribution / management server 1001 is provided on a LAN 1000,
A multifunction device (MFD) 1010 for executing various services by connecting to the same LAN 1010 and a plurality of (here, for example, two) clients 1020 and 1021 as service environments for each user are connected to the same LAN 10.
14 shows an example in which it is arranged on the 00.

The MFD 1010 is used to perform facsimile communication with another facsimile machine via the public network 1.
050. In the public network 1050, other facsimile machines are arranged so as to be possible.

FIG. 2 is a diagram showing a configuration example of a second document distribution system according to this embodiment. The present embodiment is not limited to the example shown in FIG. 1, but may have the system configuration shown in FIG. 2, for example.

In the example of FIG. 2, the document distribution / management server 11
01, a plurality of MFDs (1110, 1111)
And a plurality of clients (1120 to 1123).

Such a system may be constructed according to the load of the service operated at the user's site. In the example shown in FIG. 2, the use of a plurality of MFDs can be flexibly dealt with by adding processing to the document distribution / management server 1101 side as needed.

FIG. 3 shows a third embodiment of the present invention.
1 shows an example of the configuration of a document distribution system. The configuration example of the third document distribution system according to the present embodiment shown in FIG. 3 shows an example in which a plurality of document distribution / management servers are logically arranged on the same logical network (LAN). ing.

Specifically, for one document distribution / management server 1201, the MFD 1210 and the client 1
220 and 1221 can be operated as one group, and as another group, an MFD 1211 centered on the document distribution / management server 1202, a client 1222,
The group can be operated in 1223.

In this case, by supporting communication between the document distribution / management servers as needed, it is possible to provide a user with more flexible document distribution / management services.

FIG. 4 shows an example of a configuration diagram of a fourth document distribution system according to this embodiment. In the example of the fourth document delivery system, a document delivery / management server 1301 and an MFD
1310 indicates that the document distribution / management service provided by only the limited clients (here, 1321 and 1322) on the same network (LAN) is provided.

The fourth example of the document distribution system shows that the document distribution / management server 1301 can flexibly perform user management as required, for example, license management and security management of this application. ing.

FIG. 5 is an example of a configuration diagram of a fifth document distribution system according to this embodiment. In the fifth document distribution system, the document distribution / management server 14
01 and one multi-function device (MFD) to connect to it and execute various services
1410 and a plurality of (here, for example, two) clients 1420 and 142 as service environments for each user.
1 shows an example in which 1 is arranged on the same LAN.

Further, the MFD 1410 is connected to a public network 1050 for facsimile communication. In the example of the fifth document distribution system, the server 1401 is also the public network 10
The public network 1050 is connected to not only a facsimile apparatus (FAX) 1450 but also an information processing terminal (PC) 1460, and is configured to be able to access the server 1401 via the public network 1050. .
The communication means for communicating with the public network on the server side can be easily dealt with by ordinary dial-up processing.

FIG. 6 is a diagram showing a detailed block configuration of a multifunction device (MFD) of each of the above document distribution systems.

In FIG. 6, reference numeral 2001 denotes a resource management unit which manages various resources supported as devices and schedules various requested jobs. An operation unit 2010 serves as a user interface for providing a user with a function as a terminal.

Reference numeral 2015 denotes a reading control unit,
016 is performed. Reference numeral 2020 denotes a recording control unit,
The printer 2021 is controlled. Reference numeral 2025 denotes a communication control unit which controls normal FAX transmission and reception via a line control unit 2026. Reference numeral 2030 denotes a memory management unit which allocates a memory 2031 resource to each control unit and performs storage management of various document data and the like.

Reference numeral 2035 denotes an image processing unit which performs paper size conversion, resolution conversion, smoothing processing, etc.
Performs necessary image processing during reception and recording. Reference numeral 2040 denotes an encoding processing unit which mainly performs encoding and decoding processes such as MH, MR, and MMR which are standardly used for FAX transmission and reception.

A PDL control unit 2045 converts PDL data received via the LAN into video data using a PDL processing unit 2046 in this embodiment. The converted data is generally stored in the recording control unit 20.
20 and output by printing from the printer 2021.

2050 is an external interface (I / F)
And a LAN controller 205 in the present embodiment.
1 to perform predetermined data communication with a server on the LAN, job management, and control. For example, processing such as receiving a transmission job and a print job from the server and transferring received data and scanner read data to the server is performed under the management of the resource management unit 2001.

In order to transfer scanner read data to a server for a specific user (client) on the network, there is also provided means for designating the client from the operation unit 2010.

The operation of the multifunction device (MFD) according to the present embodiment having the above configuration will be described below.

[Copy Operation] In the present embodiment, a copy operation instruction operation from the operation unit 2010 is performed.
The document set on the scanner 2016 is read,
Resource management unit 2 so that it is output to printer 2016
Each related control unit is controlled under the management of 001.

"Facsimile (FAX) transmission operation" Similarly, the original set on the scanner 2016 is read by the facsimile transmission operation instruction operation from the operation unit 2010, and the desired other facsimile is transmitted via the line control unit 2026 and the line network 1050. Each related control unit is controlled under the management of the resource management unit 2001 so as to be transferred as facsimile data to the device.

"Facsimile receiving operation" line control unit 20
When the 60 detects a called (incoming) call from the line network 1050, the incoming facsimile data (image data) is temporarily stored in the memory 2031 in response to this. In general, the facsimile reception data is output as a received document so that the data is printed out from the printer 2021, or the LAN control 2051, the LAN 1000
Each control unit is controlled under the control of the resource management unit 2001 so that data is transferred to the server via the server.

Processing in the multifunction device (MFD) according to the present embodiment, in particular, control for processing various jobs in connection with the server on the LAN and in cooperation with the server will be described. FIG. 7 is a flowchart showing processing in the multifunction device according to the present embodiment.

First, in step S1, it is confirmed whether or not a connection request with the server has been made. If there is no connection request with the server, wait until requested. In the present embodiment, the connection request instruction with the server is sent to the operation unit 20.
It can be performed from 10 or from the network. At this time, a server to be connected can be specified.

If a connection request with the server has been made, the flow advances to step S2 to execute a connection process with the server. For example, if the server name to connect to is specified,
The server is notified by adding the parameter value to the data transmitted on the LAN 1000.

In the next step S3, it is confirmed whether or not there is job data to be transferred to the server in the terminal.
If there is no job transfer request, the process proceeds to step S5.

On the other hand, if there is a job transfer request to the server in step S3, the flow advances to step S4 to perform processing such as job data transfer to the server. For example, when there is a received document transfer job, a scanner reading job, or the like, processing such as job data transfer for transferring these to the server is performed. Then, the process proceeds to step S5.

In step S5, it is confirmed whether there is a job request from the server to the terminal. And
If there is no job request from the server to the terminal, the process proceeds to step S10.

On the other hand, in step S5, if there is a job request from the server side to the terminal side, the process proceeds to step S6,
First, check the availability of resources in the terminal. If it is determined at this time that the source is not sufficient and that the job data cannot be accepted, the process proceeds to step S7. In step S7, the server is notified that the terminal is busy, and the process proceeds to step S10.

On the other hand, if there is a vacancy of the source in step S6 and the job data can be accepted, the process proceeds to step S8 to accept the job data from the server and perform the job processing. Then, the process proceeds to step S10. Generally, once job data is stored in memory,
Thereafter, necessary processes such as facsimile transmission process and printout process are performed.

In step S10, it is checked whether a request to release the connection with the server has been issued. In particular, when the request to release the connection with the server is not issued, the process shifts to the process of step S3 again, and the above process is continued.

On the other hand, if it is determined in step S10 that a request to release the connection with the server has been issued, the flow advances to step S11 to perform processing for disconnecting from the server. It waits for a connection request.

FIG. 8 is a block diagram showing a detailed configuration of the document distribution server of the present embodiment.

In FIG. 8, reference numeral 3001 denotes a LAN control unit. For example, when the LAN control unit 3001 is configured by software, it is desirable that basic functions are provided by a network OS in which a server application is installed.

Reference numeral 3002 denotes a transaction management unit, which performs individual communication processing with devices and clients under server management via the LAN control unit 3001 based on the results of internal processing.

Reference numeral 3003 denotes a request queue (Request queue).
Queue) management unit, which basically internally manages various request messages transferred asynchronously from the device side and the client side once in a queue and sequentially performs processing according to the request contents. In the queue management according to the present embodiment, it is assumed that a request that requires scheduling occurs in the server.

Reference numeral 3004 denotes a job management unit, which transfers processing to various job processing units in accordance with the contents of requests from the device side, the client side, and in some cases, the server. 30
Reference numeral 05 denotes a user management unit that processes a job related to user management, which is basically a connected user (client);
Performs job processing related to device management.

For example, judgment of connection (login) request processing from each client and device, handling of document information and address information managed for each user, and management of job processing status and resource status on the device side,
Control.

Reference numeral 3006 denotes a server management unit which processes jobs related to server management, and basically provides service functions such as server settings, data backup, and acquisition of service log data to server administrators. .

Reference numeral 3007 denotes a document processing unit. The document processing unit 3007 handles processing relating to the overall document processing in the document distribution server. The document processing unit 3007 is configured to transfer control authority to the scheduler 3010 as necessary, and execute various jobs 3020 under the management of the scheduler 3010.

Reference numeral 3030 denotes a memory management unit. In principle, various data handled by the document distribution server is stored and managed in the database 3031 under the management of the memory management unit 3030, and can be referred to and read out as needed. Done.

FIG. 9 shows a specific example of the various document job groups 3020 of the document distribution server of the embodiment shown in FIG. 8 described above. FIG. 9 is a diagram illustrating a group of various document processing jobs of the document distribution server according to the present embodiment.

Various document job groups 302 according to this embodiment
0 has the job configuration shown in FIG. 9 under the schedule management of the scheduler 3010, for example. Note that FIG. 9 shows only one configuration example of the job group, and it goes without saying that other job configurations can be taken in the present embodiment.

As a broad classification, a job for device 3110
Is divided into a job involving transfer processing of job data between the server and the device corresponding to the above, a job processed in the server corresponding to the server internal job 3120, or a job limited to data processing between the server and the client. Schedule is managed. Hereinafter, each job will be described in detail. <For device job> For a job corresponding to device job 3110, a facsimile transmission job 3111 receives transmission request job data from each client and transmits facsimile data to the device. Request.

Reference numeral 3112 denotes a facsimile reception job, which receives facsimile reception data from the device side,
Documents are stored and managed in the server. If the client's delivery destination data is added from the device side,
The distribution process is performed by managing the user-specific data. On the other hand, when the distribution destination is unknown, the processing is shifted to an automatic routing job 3126 to be described later, whereby the distribution processing can be performed by extracting the distribution destination from the image data.

Reference numeral 3113 denotes a print job, which controls processing of a print request job for an image document stored and managed in the server, particularly from the client side. 31
Reference numeral 14 denotes a scan job which receives original read data from a scanner device, manages the read data as a file in a read-only folder of a predetermined user, and controls the user to access the read-only folder.

<Job in Server> In the job corresponding to the server internal processing job 3120, 3121 is an OCR
This is an analysis job, and performs an OCR process on a received document, a scanner-read document, and the like, which are stored and managed as image data.

In the present embodiment, it is configured such that the whole of a directly specified document is subjected to OCR processing, and that the document can be started from another document summarizing job 3122 and a routing job 3126 according to the purpose. . For example,
It is configured so that destination data can be extracted from a received document, or the entire image data can be converted to electronic data by performing OCR processing on the entire image data.

Reference numeral 3122 denotes a document summarization job for performing a content summarization process on a character-coded document stored in the server. Reference numeral 3123 denotes a document search job, which provides a means for searching for documents stored in the server.

Reference numeral 3124 denotes an encryption processing unit which performs encryption processing on the document stored in the server as necessary.
This guarantees security for the document. 31
A document data transfer job 25 transfers image data to the client. At this time, if there is a display size reduction request, the display data subjected to the reduction processing is transferred.

Reference numeral 3126 denotes an automatic routing job. For example, when a distribution process is performed on a received document, a destination is extracted by the OCR analysis job 3121 and the extracted destination is stored in a management area for each user corresponding to the extracted destination. The distribution process is performed by moving the document.

Reference numeral 3127 denotes a manual routing job. For example, with respect to a temporarily stored received document, the contents are displayed by visually displaying each document to a specially permitted client-side user. It provides a means for confirming a predetermined destination by viewing, and a means for manually moving the document to a folder of each user on the network in the server.

Reference numeral 3128 denotes a document registration job which can register a document in the server in response to a request from the client.

Next, a specific example of the database 3031 of the present embodiment shown in FIG. 8 will be described with reference to FIG. FIG. 10 is a diagram showing a database configuration of the document distribution server in the present embodiment.

The following data is managed as the shared data 2500.

Reference numeral 2511 denotes user management information, which corresponds to a user name, a user password, user-specific settings, device setting information, and the like. Reference numeral 2512 denotes server management information, which corresponds to the number of user licenses, time, server application version, and the like. Reference numeral 2513 denotes shared address data, which corresponds to address data shared by each user.
The address of each user on the LAN on the network is automatically registered.

Reference numeral 2514 denotes shared document data, which corresponds to document data shared by each user. Reference numeral 2515 denotes shared document annotation information, which corresponds to annotation information for a document shared by each user. Reference numeral 2516 denotes communication log data, particularly communication log (history) data related to facsimile transmission / reception.

Reference numeral 2517 denotes temporary storage data.
A facsimile received document forwarded without specifying a destination corresponds to this.

Further, the database 30 according to the present embodiment is
31 manages data for each user in addition to the shared data 2500 described above. For example, user 1 data 2600, user 2 data 2700,.
And manages data described below for each user who uses the server.

The data for each user (2600, 270
0) is roughly divided into document data (2650, 275)
0) and user-specific address data (2690, 279)
0), and user-specific address data (2690,
2790) The management area corresponds to address information (2691, 2791) uniquely set by the user.

The document data (2650, 2750) includes in-box (InBOX) data (2651,
2751), outbox (OutBox) data (2652, 2752) as document data in the transmission request transferred to the device side, and scan (Scan) data (265) as document data transferred after scanning.
3, 2753).

Also, transmission facsimile data as transmission-processed document data, and discard data (Trash Data) (2655,
2755) User-specific folder data (2657, 2557, etc.) for managing documents moved and copied by the user corresponds to folders individually set by the user.

FIG. 11 is a diagram showing a data flow in the system via the document distribution server of this embodiment. The transfer control of each data in the system via the document distribution server according to the present embodiment will be described below with reference to FIG.

Multi-function device (MFD)
Data transfer processing is performed between 3301 and the server via a data buffer 3310 in the server. The data buffer 3310 includes a data buffer 3311 for facsimile fax transmission request, a data buffer 3312 for facsimile reception, a data buffer 3313 for print data, and a data buffer 3314 for scanner data.
Are prepared, and the corresponding data can be transferred by being mixed with the MFD 3301 in data packet units.

In the server, the data buffer 3310 on the MFD 3301 side and the database 3311 internally transfer data as needed.

Each client (3320-3322)
Is basically to provide various services by performing data transfer (access) to a database in a server.

For example, the user (33) as a client
In 20), various services can be provided by accessing the data area of the common data area 2500 in the server and the user 1 data area 2600 individually managed for user 1.

The basic processing in the document distribution server according to the present embodiment having the above configuration will be described below with reference to FIG. FIG. 12 is a flowchart showing basic processing in the document distribution server according to the present embodiment.

When the power is turned on, the document distribution server shifts to the processing of FIG. 12, and first checks the database at the time of turning on the power in step S3401. Then, in the next step S22, it is confirmed whether or not there is a login (Login) request to the own document distribution server from various clients and devices. If there is no login request, the process proceeds to step S24.

On the other hand, if there is a login request in step S22, the flow advances to step S25, and in step S22, login processing (connection processing) including password check and the like is performed. This login process is performed by the user management unit 3005 shown in FIG. And step S24
Proceed to.

In step S24, it is checked whether there is a request for user information. If there is no user request, the process proceeds to step S26.

On the other hand, if there is a user information request in step S24, the process proceeds to step S25, and a user information request process for transferring data individual to each user and shared data to the client according to the request is performed. This user information request processing is performed by the user management unit 30 shown in FIG.
05. Then, the process proceeds to step S26.

In step S26, it is confirmed whether or not there is a server information request from the client. If there is no server information request from the client, step S28
Proceed to.

On the other hand, if there is a server information request from the client, the flow advances to step S27 to perform a server information request process for transferring server-specific data to the client according to the request. This server information request processing is processed by the server management unit 3006 shown in FIG. Then, the process proceeds to step S28.

In step S28, it is confirmed whether or not there is a document data request from the client. If there is no document data request from the client, the process proceeds to step S30.

On the other hand, if there is a document data request from the client in step S28, the flow advances to step S29 to perform data transfer processing of the specified document. This process is performed by the document processing unit 3007 shown in FIG. Then, the process proceeds to step S30.

In step S30, it is confirmed whether or not there are various job requests from clients and devices. If there are no various job requests from the client and the device, the process proceeds to step S32.

On the other hand, if there are various job requests from the client and the device in step S30, the flow advances to step S31 to process the job data according to the specified job type. The processing of these various job data is processed by the document processing unit 3007 shown in FIG. Then, the process proceeds to step S32.

In step S32, it is confirmed whether or not there is a processing request for address book processing. If there is no processing request related to the address book processing, step S
Proceed to 34.

On the other hand, if there is a processing request for address book processing in step S32, the flow advances to step S33 to perform address book processing for collection, registration, and change of address information. Then, the process proceeds to step S34.

In step S34, it is confirmed whether or not there is a logout (Logout) request. If there is no logout request, the process proceeds to step S36. On the other hand, if there is a logout request in step S34, step S
Proceeding to 35, logout processing (disconnection processing) according to the logout request is performed. Then, the process proceeds to step S26.

In step S26, it is confirmed whether or not there is a server shutdown request. If there is no server shutdown request, the process returns to step S22, and the above-described confirmation processing of each request and various processing corresponding to the request are performed. On the other hand, if there is a server shutdown request, the process proceeds to step S37, where a shutdown process is performed, and the process ends.

Next, the document delivery /
The configuration and operation of a client connected to the management server and the MFD via the LAN 1000 will be described. FIG. 13 is a detailed block configuration diagram of the client terminal according to the present embodiment.

Referring to FIG. 13, reference numeral 4001 denotes a general document creation application; 4002, a graphic device interface provided by the OS; 4003, a printer driver; and 4004, a print manager generally provided by the OS.

The print job requested from the document creation application 4001 is composed of these modules (graphic device interface unit 4002, printer driver 4003, print manager 4004).
And is processed on the printing system provided by the network OS via the LAN control unit indicated by 4030.

Reference numeral 4005 denotes a facsimile driver. When a facsimile transmission request is made from an application, the facsimile driver is selected and a job management unit 402 described later is selected.
0 is processed as a transmission request job.

Reference numeral 4010 denotes a document distribution / management application provided in the present embodiment, which provides a GUI for accessing the document distribution / management server.

More specifically, display of various data (FAX transmission / reception document, scanner document, communication history information, etc.), document editing function, various setting functions (including mode setting for making a personal document a shared document, address book setting), Various job designation operations (F
AX transmission, document printing, etc.).

In the present embodiment, some administrator applications are prepared in addition to the general user applications. One of them is a manual distribution application for received documents. This application displays the contents of a received document temporarily stored in the server with an unknown destination (including unanalysable) in a viewer so that the destination can be checked visually, and the document is stored in a document for a predetermined user. It can be set as

Further, as an application for a server administrator, an application for an administrator capable of setting a client (user) using the server, remote setting of a device, and the like is also provided.

Reference numeral 4011 denotes a document delivery /
The management driver 402 manages various job data requested by the application.
0 through. Reference numeral 4020 denotes a job management unit which manages a job requested by the application 4010.

Reference numeral 4021 denotes a job control unit for performing data transfer processing with the server for various jobs. Reference numeral 4030 denotes a LAN control unit, which generally controls communication on a LAN provided by an OS maker.

Next, processing of the client terminal in the present embodiment having the above configuration will be described with reference to FIG. FIG. 14 is a flowchart showing processing of the client terminal in the present embodiment.

First, the client terminal first proceeds to step S41
Performs connection (Login) processing to the server. In this connection processing, user authentication (for example, using a user ID and a password) as a user of the system in the present embodiment is performed.

In the following step S42, data upload from the server and display processing are performed. In particular,
As a result of logging in to the server, data already managed on the server is downloaded as data for the user,
A process for displaying predetermined data on the GUI is performed.

Next, in step S43, it is confirmed whether or not there is a job request from the user. If there is any job request, the process proceeds to step S44, and the requested job process is performed. Then, the process proceeds to step S45. On the other hand, if there is no job request in step S43, the process immediately proceeds to step S45.

In step S45, it is confirmed whether or not there is a request for terminating the application. If there is no request for terminating the application, the process returns to step S42, where the data on the server side is uploaded again and the status such as the presence or absence of the distributed document is confirmed.

On the other hand, if there is a request to end the application in step S45, the process proceeds to step S46, where a disconnection (Logout) process with the server is performed, and the process is terminated.

The processing on the server side is performed as described above.

Next, in the system of the present embodiment including an MFD having a database function connectable to another facsimile apparatus via the switching network 1050, which is a process unique to the present embodiment, another facsimile is used. The process of automatically creating a cover page in the case where a facsimile message received from the apparatus is confirmed, and a reply and distribution are performed for the received message will be described with reference to FIGS.

FIG. 15 is a diagram for explaining automatic creation of a cover page in the present embodiment, FIG. 16 is a flowchart showing automatic cover page creation processing in the present embodiment, and FIG. 17 is a flowchart of the present embodiment. It is a figure which shows the process of automatic creation of a cover page in an example concretely.

In this embodiment, the facsimile information and facsimile message received from the facsimile apparatus to be transmitted in advance, the facsimile message, the reception time, and the information obtained by OCR of the message can be used as they are, or the information can be referred to the database. The cover page is automatically created by using the data in the database.

Further, the cover page can be automatically created by automatically switching the format of the invoice and the greeting depending on the reply, the selection of distribution, and the destination.

If automatic creation is not possible, the sender is requested to input necessary data.

In the present embodiment, for example, the MFD 1010 operating as a facsimile apparatus transmits facsimile information (information such as TSI and SUB according to CCITT-T recommendations transmitted by communication) and facsimile messages (image information). Receive. Then, the received data is L
The data is stored in the server 1001 via the AN 1000.

The facsimile information and the facsimile message stored in the server 1001 are transmitted by the server 1001 to the information terminals (clients) 1020 as the respective destinations.
1021 via the LAN 1000.

A typical example of a cover page (cover page) sent as the first page of a distributed facsimile is indicated by 4301 in the upper part of FIG. In the example of the content of the cover page indicated by reference numeral 4301, it is composed of a destination, a correspondent, a comment (greeting text), and a date. However, the present invention is not limited to the above example. Such information may be included.

The server 1001 (or 1020, 1010
21), the OCR analysis job 312
1 is performed (OCR processing in the information terminals shown in 1020 and 1021), and communication partner information (in this case, “Suzuki” as a sender) is read.

The information read by the OCR process (character recognition process) may be further collated in a database of a server or a client, or may be a telephone number other than a name such as “Sender: Suzuki”.

[0124] The facsimile information and communication partner information obtained by the server 1001 are transferred to the information terminals 1020 and 1021 as destinations together with the message. The information terminal may read the communication partner information by performing OCR processing from the transmitted message as necessary.

Reference numeral 4302 shown in the middle part of FIG. 15 is created by facsimile information and a message (including the invoice shown by 4301) received from another facsimile apparatus in the system of the present embodiment in a cover page automatic creation process described later. It is an example of a cover page for reply.

In the present embodiment, when the sender of the facsimile document selects “reply”, the reply format 4302 is selected, and the facsimile information received as the reply destination on the cover page 4301 described above is selected. “Suzuki” is automatically selected as a destination from a message or the like.

[0127] The lower part 4303 is an example of a cover page for distribution created from facsimile information and a message (including the invoice shown in 4301) received from another facsimile apparatus in this embodiment.

In this embodiment, when the sender selects “delivery”, this distribution format is selected.
“Suzuki” is automatically selected as the original sender from the facsimile information or the message received as the sender on the cover page indicated by “01”.

The destinations “Kimura” and “Eto” are automatically selected from the databases on the information terminals 1020 and 1021, or are input by the distributor who has received the received facsimile document message of the cover page 4301. It is.

The description of the comment column in the reply or distribution document shown in 4302 or 4303 is based on the facsimile information, the message, or the communication partner information.
21 automatically selected from the database on
Is information input by the distributor who received the message shown in FIG.

The contents of each cover page indicated by reference numerals 4301, 4302, and 4303 in FIG. 15 include a destination, a sender, a comment (greeting), a date, and a circulator (at the time of distribution). Phone information and email address may be included. Also, 4302, 430
The contents of the reply or the delivery document shown in 3 may be further added.

Next, the process of automatically creating a reply or distribution document in the above embodiment will be described with reference to FIG. FIG. 16 is a flowchart showing a cover page automatic creation process in this embodiment. FIG. 16 shows an information terminal 1 from the server 1001 via the LAN 1000.
An example is shown in which the recipient confirms the facsimile message sent to the user terminal 020 and automatically creates a cover page on the information terminal 1020 when replying to the message or performing facsimile distribution to another person.

First, in step S41, the information terminal 1
At 020, it is determined whether or not a selection has been made to automatically create a cover page. If the automatic creation has not been selected, the process ends without performing the automatic creation of the cover page.

On the other hand, if automatic creation is selected in step S41, the flow advances to step S42 to determine whether or not a reply is selectively specified. If a reply is selected and designated, the process proceeds to step S44, and the operation of creating a target cover page (reply cover page) is started.

On the other hand, if the reply is not selected and specified in step S42, the flow advances to step S43 to determine whether distribution is selected and specified. If the distribution is not selected and specified, the process is terminated.
On the other hand, in step S43, when the distribution is selected and designated, the process proceeds to step S44.

In step S44, if automatic creation of a reply or distribution is selected and specified in step S42 or S43, the facsimile information (TSI, SUB, etc. of the CCITT-T recommendation) to be covered is created. I do. In this case, “TSI: 034512
345 "is determined as the other party.

Subsequently, in step S45, the target message is subjected to OCR processing to extract necessary information. This extraction process is performed by the OCR performed on the server side.
This may be performed using the information after the processing. For example, FIG.
When the OCR process is performed on the cover page shown in FIG.

Next, in step S46, step S
The information obtained in step 44 and step S45 is referred to in the database. For example, “TSI: 034” in step S44
“512345”, “Suzuki” in “Sender: Suzuki” in step S45 is set as the reply destination or the original sender at the time of distribution.

Further, in step S47, the conditions for creating the cover page, such as the format of the cover page and the greeting, are selected from the reply / delivery designation and the communication partner information.
Then, in step S48, the information and data obtained by the above processing and the received message are read and returned /
For example, a cover page 4302 or 4303 in FIG. 15 is automatically created based on information on the person who has determined the distribution.

Subsequently, in step S49, it is determined whether there is no problem with the automatically created cover page. When there is no problem (when there is no error in the data portion created automatically), the process proceeds to step S51, and input processing of necessary additional data is performed. As the additional data, for example, addition of a document to a comment column or the like can be considered. Then, when the additional input is completed, the process of creating the cover page is completed, and the reply / delivery is started.

On the other hand, if there is a problem in checking the cover page in step S49, the process proceeds to step S50. For example, when the distribution cover page is created and the information of the distribution destination is not included in the database and cannot be specified, the sender is requested to input the insufficient data.
According to this request, the sender inputs necessary data to solve the problem. Then, after the data input is completed, the process returns to step S49, and the cover page is checked again.

According to the above processing, the cover page creation processing conventionally created by the sender from scratch can be automatically performed, and an accurate cover page can be created with a minimum number of operations.

In the above description, only the creation of a cover page for reply and distribution is taken as an example. However, even when a communication mode for automatically creating a cover page is designated by a user or the like, the above-described automatic creation of a cover page is performed. Needless to say, creation may be performed. The process of automatically creating a cover page described above will be specifically described. FIG.
FIG. 17 is a diagram specifically illustrating the process of automatically creating a cover page described above. In FIG. 17, the received cover page image 4401 and the facsimile information 4401 are displayed.
"TSI: 0345123345" as the information terminal 10
20 shows an example in which the information terminal 20 receives and processes all the information on the information terminal 1020.

The information terminal 1020 receives the facsimile message (the received cover page image 4401) received from the server 1001 and “TSI: 034512345” as the facsimile information 4401.

The received cover pages 4401 to 440
In step 2, the OCR process is performed, and the obtained information is referred to the database. As shown in 4403, "destination: Suzuki", "use reply format 4406", and "greeting sentence is" received specification "" Is determined.

[0146] In the received facsimile information 4404, "T
SI: 0345112345 ”is referred to in the database at 4405, and the information of 4403 is obtained.

A reply cover page is created reflecting the result of the multiple search.

As described above, according to the present embodiment, after confirming a received facsimile message, if reply or distribution is selected for the received message,
By automatically creating a cover page, it is possible to simplify and improve the accuracy of the paperwork for creating the cover page of the sender.

[Other Embodiments] Even if the present invention is applied to a system including a plurality of devices (for example, a host computer, an interface device, a reader, a printer, and the like), the present invention includes only one device. The present invention may be applied to an apparatus (for example, a copying machine, a facsimile machine, etc.).

Further, an object of the present invention is to supply a storage medium storing a program code of software for realizing the functions of the above-described embodiments to a system or an apparatus, and to provide a computer (or CPU) of the system or apparatus.
And MPU) read and execute the program code stored in the storage medium.

In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention.

As a storage medium for supplying the program code, for example, a floppy disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD
-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

When the computer executes the readout program code, not only the functions of the above-described embodiments are realized, but also the OS (Operating System) running on the computer based on the instructions of the program code. ) May perform some or all of the actual processing, and the processing may realize the functions of the above-described embodiments.

Further, after the program code read from the storage medium is written into the memory provided on the function expansion board inserted into the computer or the function expansion unit connected to the computer, the program code is read based on the instructions of the program code. It goes without saying that the CPU included in the function expansion board or the function expansion unit performs part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.

When the present invention is applied to the storage medium, the storage medium stores program codes corresponding to the flowcharts described above.

[0156]

As described above, according to the present invention, after confirming a received facsimile message and selecting reply or delivery to the received message, a cover page is automatically created. The simplification and accuracy of the paperwork for creating the sender's cover page can be improved.

[0157]

[Brief description of the drawings]

FIG. 1 shows a first embodiment according to an embodiment of the present invention.
1 is a diagram showing a configuration example of a document distribution system of FIG.

FIG. 2 is a diagram illustrating a configuration example of a second document distribution system according to the embodiment;

FIG. 3 is a diagram illustrating a configuration example of a third document distribution system according to the embodiment;

FIG. 4 is a diagram showing a configuration example of a fourth document distribution system according to the embodiment;

FIG. 5 is a diagram illustrating a configuration example of a fifth document distribution system according to the embodiment;

FIG. 6 is a detailed block configuration diagram of the multifunction device according to the embodiment.

FIG. 7 is a flowchart illustrating processing in the multifunction device according to the present embodiment.

FIG. 8 is a block diagram showing a detailed configuration of a document distribution server according to the embodiment.

9 is a diagram illustrating an example of a document processing job group of the document distribution server illustrated in FIG. 8 according to the embodiment.

FIG. 10 is a diagram showing a database configuration of a document distribution server according to the embodiment.

FIG. 11 is a diagram showing a data flow via a document distribution server in the embodiment.

FIG. 12 is a flowchart showing basic processing in the document distribution server according to the embodiment.

FIG. 13 is a detailed block configuration diagram of a client terminal in the present embodiment.

FIG. 14 is a flowchart illustrating processing of a client terminal according to the present embodiment.

FIG. 15 is a diagram for explaining automatic creation of a cover page in the present embodiment.

FIG. 16 is a flowchart showing a cover page automatic creation process in the present embodiment.

FIG. 17 is a diagram specifically showing a process of automatically creating a cover page in the present embodiment.

[Explanation of symbols]

1000 LAN 1001, 1101, 1201, 1301, 1401
Document distribution / management server 1010, 1110, 1111, 1210, 1310,
1410 Multifunction device (MFD) 1020, 1021, 1120 to 1123, 1220
To 1123, 1321, 1322, 1420, 142
An example is shown in which one client 1020 and 1021 are arranged on the same LAN 1000. 1050 Public network 1450 Facsimile machine (FAX) 1460 Information processing terminal (PC) 2001 Resource management unit 2010 Operation unit 2015 Reading control unit 2016 Scanner 2020 Recording control unit 2021 Printer 2025 Communication control unit 2026 Line control unit 2030 Memory management unit 2031 Memory 2035 Image processing unit 2040 Encoding processing unit 2045, 2046 PDL control unit 2046 PDL processing unit 2050 External interface (I / F) control unit 2051, 3001 LAN control unit 2500 Shared data 2511 User management information 2512 Server management information 2513 Shared address data 2515 Shared document annotation information 2516 Communication log data 2517 Temporary storage data 3002 Transaction management unit 3003 Request queue (Request Queue) management unit 3004 job management unit 3005 user management unit 3006 server management unit 3007 document processing unit 3010 scheduler 3020 various job groups 3030 memory management unit 3031 database 3110 paired device job 3111 facsimile transmission job 3112 facsimile reception job 3113 print job 3114 Scan job 3120 Server internal job 3121 OCR analysis job 3122 Document summarization job 3123 Document search job 3124 Encryption processing unit 3125 Document data transfer job 3126 Automatic routing job 3127 Manual routing job 3128 Document registration job

 ──────────────────────────────────────────────────続 き Continued on the front page F-term (reference) 5K033 AA03 DB12 DB14 EA07

Claims (16)

[Claims] 1. A communication system comprising a communication terminal having a communication function and an information terminal having a database, wherein one of return, transfer, and distribution corresponding to received data received using the communication function can be executed. A communication system comprising: a response unit; and an automatic creation unit for automatically creating a return, transfer, and distribution invoice from the received data when responding to the received data. 2. The apparatus according to claim 1, further comprising a determination unit configured to determine whether or not the invoice automatically created by the automatic creation unit is complete, wherein the determination unit determines that the invoice is incomplete if the invoice is determined to be incomplete. 2. The communication system according to claim 1, wherein input of minute data is requested. 3. The invoicing means automatically retrieves information on a return destination or a transfer destination necessary for the invoice for retrieving and responding to the received data, information on the original sender at the time of transfer, and automatically prepares the invoice. The communication system according to claim 1, wherein the communication system is created. 4. The communication system according to claim 3, wherein date information and a message included in the received data are character-recognized and extracted as document name information on the invoice, and the invoice is automatically created. 5. The communication system according to claim 3, wherein a message included in the received data is subjected to character recognition, and a part of the character recognition result is designated to automatically create an invoice. 6. The communication system according to claim 1, wherein said automatic creation means automatically creates an invoice format and a greeting according to a response format. 7. The communication system according to claim 6, wherein the format of the response is one of return, transfer, and distribution. 8. A communication method in a communication system including a communication terminal having a communication function and an information terminal having a database, the method comprising: returning, transferring, or distributing data corresponding to received data received using the communication function. A communication characterized in that any one of them can be executed, and a response corresponding to the received data is automatically created from a return, a transfer, and a distribution invoice from the received data, and a response is made using the automatically created invoice. Method. 9. It is possible to confirm whether or not the automatically created invoice is complete. If it is determined that the invoice is incomplete, a request is made by the sender to input data for the insufficiency. 9. The communication method according to claim 8, wherein the automatic creation of the invoice is terminated after the input of the data. 10. An invoice is automatically created by extracting information on a return destination or a transfer destination required for an invoice for responding by searching for the received data, information on an original sender at the time of transfer, and the like. The communication method according to claim 8, wherein the communication method is performed. 11. The communication method according to claim 10, wherein date information and a message included in the received data are character-recognized, extracted as document name information on the invoice, and an invoice is automatically created. 12. The communication method according to claim 10, wherein a message included in the received data is subjected to character recognition, and a part of the character recognition result is designated to automatically create an invoice. 13. The automatic invoicing method according to claim 8, wherein the invoicing format and the greeting are automatically switched according to the response format.
3. The communication method according to any one of 2. 14. The communication method according to claim 13, wherein the format of the response is one of return, transfer, and distribution. 15. A computer-readable recording medium for storing a control procedure for realizing each function according to claim 1. Description: 16. A computer program sequence for realizing each function according to any one of claims 1 to 14.