JPH05173910A - Network system - Google Patents

Abstract

PURPOSE:To enable sending data from a terminal to a facsimile through a server even in the case a sending user is not known the destination FAX number. CONSTITUTION:A server SV manages whether each user has a terminal ST, a facsimile FAX, or both of them and when a certain user loads up data and a destination user ID from the terminal ST or the facsimile FAX, it is decided by the destination user ID whether the destination user has the terminal ST, the facsimile FAX, or both of them. Data is transmitted to the terminal ST of the destination user in the form of mail data if the destination user has only the terminal ST, and data are transmitted to the facsimile FAX of the destination user in the form of FAX data if it has only the facsimile FAX, and the data are transmitted to the terminal ST or the facsimile FAX matching with the loaded-up data form in the data form is it has both of the terminal ST and the facsimile FAX.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network system, and more particularly to a network system in which a destination user downloads data uploaded to a server by a destination user and distributes the data.

[0002]

2. Description of the Related Art Conventionally, when a sending user uploads mail data, a transmission request to a facsimile, and a destination FAX number from a terminal to a server, the server converts the mail data into FAX data and sends the FAX data to the destination FAX. There is known a network system for transmitting a number to a facsimile. In this network system, a sending user who has only a terminal can send data to the facsimile of the destination user.

[0003]

In the above-mentioned conventional network system, the sending user sends the destination FAX to the server.
It was necessary to upload the number and could not be used if the sending user did not know the destination fax number. Also, the terminal could not be uploaded from the facsimile to the server and downloaded by the terminal.

Therefore, a first object of the present invention is to provide a network system capable of sending data from a terminal to a facsimile via a server even if the sending user does not know the destination FAX number. is there.
A second object of the present invention is to provide a network system capable of sending data from a facsimile to a terminal via a server.

[0005]

SUMMARY OF THE INVENTION In a first aspect, the present invention is a network system comprising a plurality of users having at least one of a terminal and a facsimile, a server, and a network connecting the servers. Manages whether each user has a terminal, a facsimile, or both. When a user uploads data and a destination user ID from the terminal or facsimile, the destination user has a terminal from the destination user ID. If the destination user has only a terminal, the data is transmitted to the terminal in the mail data format. If the destination user has only the facsimile, the data is transmitted to the facsimile in the FAX data format. If you are sending and the destination user has both a terminal and a facsimile, To provide a network system and to transmit that data format for those that meet the uploaded data format.

[0006]

In the network system of the present invention, the server manages whether each user has a terminal, a facsimile, or both. Then, the device possessed by the destination user of the uploaded data is checked, and the data is transmitted to the device in a data format suitable for the device. Therefore, the sender is the destination FAX.
Even if the number is not known, the data can be sent from the terminal to the facsimile via the server. Also, it becomes possible to send data from the facsimile to the terminal via the server.

[0007]

Embodiments of the present invention will be described below with reference to the drawings. The present invention is not limited to this. FIG. 1 is a block diagram showing the overall configuration of a network system NS according to an embodiment of the present invention. This network system NS includes a server SV and a plurality of terminals ST.
, ..., STn and facsimile FAX 1, ..., FAX
, and TELk are connected by a telephone line NW. A LAN or the like may be used instead of the telephone line NW.

FIG. 2 shows the configuration of the server SV. The server SV includes a keyboard 1, a display 2, a modem 3
It comprises a FAX adapter 4 for FAX transmission / reception, a voice response device 5 for telephone response, a push tone recognition device 6, a memory 8, a data file 9 and a CPU 10 for controlling them. ..

The memory 8 includes a ROM 8-1 and a RAM 8-
2 and. The form recognition program 8-1 for analyzing the uploaded OCR data is stored in the ROM 8-1.
1, a body text registration program 8-12 for registering the uploaded body data in the data file 9, and a title list transmission program 8 for transmitting a title list (FIG. 19) of the body data registered in the data file 9 to the user. -13, a text providing program 8-14 for transmitting text data to the destination user of the text data, and a telephone directory search program 8-16. In the RAM 8-2, a buffer area 8-21 for temporarily storing the uploaded data, an index table 8-22 for storing management information of the text data registered in the data file 9,
Terminal address, telephone number, and fax corresponding to the user ID
A telephone directory 8-24 for managing numbers, a user list 8-25 for storing user IDs that are permitted to access, a user ID for which a request for receiving text data provision request or reply data is scheduled and its processing Content ID (“text provided”)
Alternatively, a processing table 8-26 for storing "response storage")
And a save file management unit 8-27 for managing the text data stored in the data file 9.

FIG. 3 shows the configuration of the terminal ST. Terminal ST
Is a keyboard 11, a display 12, a modem 1
3, a memory 14, a scanner 15, and a CPU 16 for controlling them.

FIG. 4 is an explanatory diagram of an outline of processing in the network system NS. First, the text sender sends a text registration request to the server SV using the terminal ST or facsimile FAX, and uploads text data. The server SV receives and registers the text data. Then, the notification that the text data is registered is sent to the terminal ST, the facsimile FAX, or the telephone TEL of the destination user.

The destination user who received the notification makes a text providing request to the server SV by the terminal ST, the facsimile FAX or the telephone TEL. The server SV is
The text data is transmitted to the terminal ST or the facsimile FAX of the destination user in a data format suitable for the device.

If the reply to the text is requested, the destination user who has received the text data sends a reply storage request to the server SV by the terminal ST or the facsimile FAX and sends the reply data. The server SV receives the reply data and registers it. Then, a notification that the reply data is registered is sent to the terminal ST, facsimile FAX, or telephone TEL of the former sending user.

The sender who has received the notification is the terminal S
By T or facsimile FAX or telephone TEL,
A text providing request is made to the server SV. Server SV
Is the terminal ST or facsimile FA of the former sender.
The body data (response data) is transmitted to X in a data format suitable for those devices. Thereafter, data is exchanged via the server SV in the same manner.

FIG. 5 is a flowchart of the main program of the server SV. In step 51, it is checked whether there is a mail reception, and if there is a mail reception, step 5
The mail starting process of FIG. 2 (FIG. 6) is executed. Step 58
Then, it is checked whether or not there is a FAX reception, and if there is a FAX reception, the FAX activation process (FIG. 12) of step 60 is executed. In step 62, it is checked whether there is a telephone call, and if there is a telephone call, the telephone activation process (FIG. 13) in step 64 is executed. In step 65, it is checked whether or not a command is received from the terminal ST, and if the command is received, the command starting process of step 66 (FIG. 14) is executed. In step 68, it is checked whether or not an end instruction is input from the keyboard 1. If the end instruction is not input, the process returns to step 51, and if the end instruction is input, the process ends.

FIG. 6 is a detailed flowchart of the mail starting process. In step 521, the received communication data (mail) is stored in the buffer area 8-21. In step 522, the file management process (FIG. 7) is executed. And it returns to 58 of FIG.

FIG. 7 is a detailed flowchart of the file management process. In step 5221, in order to check whether or not the user is permitted to access, the buffer area 8-
The sender user ID is acquired from the communication data stored in 21 and it is checked whether the sender user ID is in the user list 8-25. If there is, go to step 5261. If not, it proceeds to step 5281. FIG. 8 shows an example of the user list 8-25.

Returning to FIG. 7, in step 5261, the processing content I is calculated from the communication data stored in the buffer area 8-21.
Acquire D and check whether it is "text registration".
If "text registration", the process proceeds to step 5262, and if not, the process proceeds to step 5264. In Step 5262,
Perform body registration processing. As a result, the buffer area 8
The save file of the communication data stored in -21 is newly created in association with the destination user ID, or if there is already a save file associated with the destination user ID, the communication data is added to it.

FIG. 9 shows the save file management unit 8-27 and the save file SF. Save file management unit 8
-27 indicates the save file SF corresponding to the destination user ID of the communication data. The save file SF is
It is composed of one or more save data (SD1, ..., SDp). As shown in FIG. 10, one save data SD is
It comprises a header section 71 and an information section 72. Header part 71
Is the destination user ID 71-1 and the sender user ID 71-
2, date data 71-3, title data 71-4
And an unreported flag 71-5. The information section 72 is
It consists of text data 72-1.

Returning to FIG. 7, in step 5263, the buffer area 8-21 is cleared. Then, the file management process ends.

On the other hand, in step 5263, the processing content I
It is checked whether D is a "title list". If it is a "title list", the process proceeds to step 5264, and if not, the process proceeds to step 5265. In step 5264, title list processing is executed. As a result, the title list (FIG. 19) of the save data SD included in the save file SF corresponding to the transmission source user ID of the communication data requesting the title list is delivered to the transmission source user.

On the other hand, in step 5265, the processing table 8-26 is referred to. An example of the processing table 8-26 is shown in FIG. In step 5266, the transmission source user ID and the processing content ID of the communication data are acquired, and it is checked whether or not the combination matches any of the contents of the processing table 8-26. If they match and the processing content ID is “text provided”,
Go to step 5267. If they match and the processing content ID is “store response”, the process proceeds to step 5272. If they do not match, the process proceeds to step 5281.

In step 5267, the save file management unit 8-27 is referred to, and the save file SF corresponding to the user ID of the transmission source of the communication data requesting the text providing is saved.
Is taken out, and one save data SD in the save file SF is taken out. In step 5268, a text providing process is executed. As a result, the text data 72-1 is delivered to the user who has requested to provide the text. In step 5270, when there are a plurality of save data SD in the save file SF, step 5267 and step 5268 are repeated for all save data SD.
At step 5280, the save file SF is deleted because all the save data SD have been delivered. In addition,
When the body ID is designated, only the save data SD corresponding thereto may be transmitted.

On the other hand, in step 5272, a text registration process is executed. This allows communication data (response data)
The save file SF associated with the destination user ID is newly created, or if a save file associated with the destination user ID already exists, reply data is added to it.

On the other hand, in step 5281, error notification processing is executed. That is, the sender user is notified of a message refusing the reception. Then, the process proceeds to step 5263.

FIG. 12 is a detailed flowchart of the FAX activation process. In step 602, the received communication data (FAX data) is stored in the buffer area 8-21. In step 604, it is checked whether the OCR data is included in the FAX data, and if it is included, the process proceeds to step 606, and if it is not included, the process proceeds to step 616.

In step 606, the form is recognized with respect to the OCR data, and the transmission source user ID, the processing content ID and the like are acquired. In step 608, the form recognition result is stored in the buffer area 8-21. In step 610,
The file management process (FIG. 7) described above is executed. And
Returning to step 62 of FIG. On the other hand, in step 616, general FAX processing is performed. Then, the process returns to step 62 of FIG.

FIG. 13 is a detailed flowchart of the telephone activation process. In step 642, push-tone input of a user ID, a processing content ID, text data, etc. is prompted by a voice response guidance. In step 644, the push tone input sent from the telephone TEL is received and stored in the buffer area 8-21. Step 6
At 46, push-tone recognition is performed to acquire the user ID, the processing content ID, and the like. In step 648, the push tone recognition result is stored in the buffer area 8-21. In step 649, the above-mentioned file management process (FIG. 7) is executed. Then, the process returns to step 65 of FIG.
Note that general voice recognition may be performed instead of push-tone recognition, and the user ID and processing content ID may be input by voice.

FIG. 14 is a detailed flowchart of the command starting process. In step 564, it is checked whether or not the received command is a registration command. If it is a registration command, in step 566 the text registration process is executed. Step 5
At 76, an error message is transmitted to the terminal ST which has transmitted the command. Then, the process proceeds to step 68 in FIG.

FIG. 15 is a detailed flowchart of the text registration process. In step 5662, the activation factor of the text registration process is the mail activation process 52 or the FAX activation process 6
It is checked whether it is 0, the telephone activation process 64, or the command activation process 66. Mail activation process 52 or FAX activation process 6
If it is 0 or the telephone activation process 64, the process proceeds to step 5676.
If it is the command activation process 66, the process proceeds to step 5664.

In step 5664, the data is transmitted to the terminal ST so that the index input screen as shown in FIG. 17 is displayed on the display 12 of the terminal ST, and the data necessary for creating the index table 8-22 is input. Encourage. FIG. 16 shows an example of the index table 8-22.
The data required to create the index table 8-22 is
A destination user ID 75, a title 77, a reply deadline 78, and a text data format 79. The other items in the index table 8-22 are automatically added.

In step 5666, the body data format 7
It is checked whether 9 is a code or an image. If it is a code, the process proceeds to step 5668.
Proceed to 674.

In step 5668, it is checked whether the document file already created is registered. If the already created document file is registered, the procedure proceeds to step 5670, and if not, the procedure proceeds to step 5672. In step 5670, the document file is received from the terminal ST and stored in the buffer area 8-21. In step 5672, the terminal ST
A document is created in the buffer area 8-21 based on the input from the.

On the other hand, in step 5674, the image data from the scanner 15 of the terminal ST is received and stored in the buffer area 8-21.

At step 5676, the buffer area 8-
The communication data stored in 21 is read. The communication data is mail data, FAX data, voice data, code data, and image data. In step 5678, a save file is newly created that is associated with the destination user ID of the read communication data, or the communication data is added to the save file that is already associated with the destination user ID. At step 5680,
Information about the communication data is stored in the index table 8-
Add to 22. In step 5684, the set of the destination user ID of the communication data and the processing content ID of "text providing" is added to the processing table 8-26. If this group is already in the processing table 8-26, nothing is done.

In step 5686, notification processing (see FIG.
Perform 2). That is, the destination user of the communication data is notified that the save file SF is held.

FIG. 17 is a display transition diagram of an index input screen for text registration. At 100, the user is prompted to enter the title of the text to be registered, the destination user ID, and whether or not a response is required. If there is an input that requires a reply, the user is prompted to input at 102 whether there is a reply deadline. If there is an entry with a response deadline, the user is prompted to enter a response deadline at 104.

At step 106, the user is prompted to enter the text data format to be registered. If the text data format is a code, the user is prompted to enter the presence / absence of a created document file in step 108. If there is a created document file, 110 is prompted to input the file name. If there is no created document, the document creation screen is displayed at 112.

If the text data format is image, step 114 prompts the scanner 15 to input image data. At 116, a registration completion message and a body ID are displayed.

FIG. 18 is a detailed flowchart of the title list processing. In step 650, the request source user ID is changed to the destination user ID from the index table 8-22.
The body text ID 73 and title 77 of the save data SD to be
And the registration date 76 is acquired, and a title list is created. An example of the title list is shown in FIG. In step 651, the activation factor of the title list process is checked. If mail reception is received, the process proceeds to step 652. If fax reception or telephone reception is performed, the process proceeds to step 653.

At step 652, the title list is mailed to the terminal ST. In step 653, the telephone directory 8
The fax number corresponding to the request source user ID is acquired from -24. An example of the telephone directory 8-24 is shown in FIG. In step 654, the title list is transmitted to the facsimile FAX having the FAX number. If a fax number different from the fax number registered in the telephone directory 8-24 is input, the title list may be transmitted to the facsimile.

FIG. 21 is a detailed flowchart of the text providing process. In step 2112, it is checked by searching the index table 8-22 whether or not the save data SD fetched in step 5267 of FIG. 7 requires a response. If it does not require a response, step 2
If so, the procedure proceeds to step 2114.

At step 2113, the processing table 8-
The column of the user ID 26 is deleted. On the other hand, in step 2114, a response request message is added to the save data SD. In step 2115, the processing table 8-
A set of the user ID and the processing content “store response” is added to 26.

At step 2116, the activation factor is checked. If mail is received, step 2117 follows.
If it is AX reception or telephone reception, the process proceeds to step 2119.

At step 2117, mail data is created. In step 2118, the mail is transmitted.

On the other hand, in step 2119, the telephone directory 8-
The terminal address corresponding to the request source user ID is acquired from 24. If the acquisition is successful (if there is a terminal), the process proceeds to step 2117. If the acquisition fails (if there is no terminal), the process proceeds to step 2120. In step 2120, the F corresponding to the requesting user ID is read from the telephone directory 8-24.
Get the AX number. If the acquisition is successful (if there is a facsimile), the process proceeds to step 2121. If the acquisition fails (if there is no facsimile), the process proceeds to step 2123. In step 2121 FAX data is created.
In step 2122, FAX transmission is performed.

In step 2130, the telephone number corresponding to the requesting user ID is acquired from the telephone directory 8-24. If the acquisition is successful (if there is a telephone call), the process proceeds to step 2131. If the acquisition fails (if there is no phone), then it ends. In step 2131, the text is sent by mail or F
A voice notification is sent by telephone that the AX has been transmitted.

On the other hand, in step 2124, the telephone directory 8-
The telephone number corresponding to the requesting user ID is acquired from 24. If the acquisition is successful (if you have a phone call), step 21
Go to 25. If the acquisition is unsuccessful (if there is no telephone call), the process proceeds to step 2127. In step 2125, voice data is created. In step 2126, the voice data is transmitted by telephone. On the other hand, in step 2127, error notification processing is executed.

In the method of determining the data format when transmitting the above-mentioned text data, the data is preferentially transmitted in the order of the terminal, the facsimile, and the telephone, but the device that matches the data format when the data is uploaded. The data format at the time of transmitting the text data may be determined so that the data is preferentially transmitted to the device or the device used for the request to provide the text is preferentially transmitted.

FIG. 22 is a detailed flowchart of the notification process. In step 2201, the destination user ID is acquired from the registered save data SD. Step 210
In 2, the terminal address corresponding to the destination user ID is acquired from the telephone directory 8-24. If the acquisition is successful (if there is a terminal), the process proceeds to step 2203. If the acquisition fails (if there is no terminal), the process proceeds to step 2104. In step 2203, a message indicating that the saved save data SD is held is sent by mail.

At step 2104, the FAX number corresponding to the destination user ID is acquired from the telephone directory 8-24. If the acquisition is successful (if there is a facsimile), step 2
Proceed to 205. If the acquisition fails (if there is no facsimile), the process proceeds to step 2206. In step 2205, a message indicating that the saved save data SD is held is transmitted by FAX.

At step 2106, the telephone number corresponding to the destination user ID is acquired from the telephone directory 8-24. If the acquisition is successful (if there is a telephone call), the process proceeds to step 2207. If acquisition fails (no phone), step 2
Proceed to 208. In step 2207, a message indicating that the saved data SD is held is given by telephone TE.
Send to L.

At step 2208, since the notification could not be made, the unnotified flag 71-5 of the save data SD is set. The server SV notifies the administrator of the server SV that there is save data SD with the unreported flag 71-5 set at an appropriate timing.

FIG. 23 is a detailed flowchart of the error notification process. In step 2116, the activation factor is checked. If it is a mail reception, the flow proceeds to step 2302. If it is a fax reception, the flow proceeds to step 2303. If it is a telephone reception, the flow proceeds to step 2305.

At step 2302, an error message is sent by mail. In step 2303, the telephone directory 8-
The FAX number corresponding to the transmission source user ID is acquired from 24. In step 2304, the error message FA
Send X. In step 2305, the error message is transmitted by voice.

[0056]

According to the network system of the present invention, the server manages the data format that can be used by the user, and the uploaded data format can be used by the user regardless of the data format of the uploaded data. Sent data to the destination user. Therefore, the sending user can upload without considering the data format of the destination user. On the other hand, the destination user can download using any device.

[Brief description of drawings]

FIG. 1 is an overall configuration diagram of a network system of the present invention.

FIG. 2 is a configuration diagram of a server.

FIG. 3 is a configuration diagram of a terminal.

FIG. 4 is an explanatory diagram of an outline of processing in the network system of the present invention.

FIG. 5 is a flowchart of a main program of the server.

FIG. 6 is a flowchart of a mail activation process.

FIG. 7 is a flowchart of file management processing.

FIG. 8 is a view showing an example of a user list.

FIG. 9 is an explanatory diagram of a save file.

FIG. 10 is an explanatory diagram of save data.

FIG. 11 is a view showing an example of a processing table.

FIG. 12 is an explanatory diagram of FAX startup processing.

FIG. 13 is an explanatory diagram of a telephone activation process.

FIG. 14 is an explanatory diagram of command activation processing.

FIG. 15 is a flowchart of a text registration process.

FIG. 16 is a view showing an example of an index table.

FIG. 17 is an index input screen display transition diagram for text registration.

FIG. 18 is a flowchart of title list processing.

FIG. 19 is a view showing an example of a title list.

FIG. 20 is a view showing an example of a telephone directory.

FIG. 21 is a flowchart of a text providing process.

FIG. 22 is a flowchart of notification processing.

FIG. 23 is a flowchart of error notification processing.

[Explanation of symbols]

 NS network system SV server ST terminal FAX facsimile TEL telephone NW network 3 Modem 4 FAX adapter 5 Voice response device 6 Push tone recognition device 8 Memory 9 Data file 10 CPU

Front page continuation (72) Inventor Tetsuo Machida 1099 Ozenji, Aso-ku, Kawasaki-shi, Kanagawa Ltd. Hitachi, Ltd. System Development Laboratory

Claims (9)

[Claims] 1. A network system comprising a plurality of users each having at least one of a terminal and a facsimile, a server and a network connecting the servers, wherein the server has both a terminal and a facsimile. When a user uploads data and a destination user ID from a terminal or a facsimile, it is determined from the destination user ID whether the destination user has a terminal or a facsimile and has both the destination and the destination. If the user has only the terminal, the data is transmitted to the terminal in the mail data format, if the destination user has only the facsimile, the data is transmitted to the facsimile in the FAX data format, and if the destination user has both the terminal and the facsimile. For those who match the uploaded data format A network system characterized by transmitting in that data format. 2. The network system according to claim 1, wherein the server preferentially transmits the data in the mail data format to the terminal if the destination user has both the terminal and the facsimile. .. 3. The network system according to claim 1, wherein the server, when a user uploads FAX data from a facsimile,
A network system characterized by analyzing uploaded FAX data, recognizing contained characters, and extracting data and a destination user ID. 4. The network system according to any one of claims 1 to 3, wherein the server holds the uploaded data and holds the data for a destination user terminal or facsimile. A network system characterized by notifying, waiting for access from a destination user, and transmitting data after the destination user has accessed. 5. The network system according to claim 4, wherein the server has a voice recognition function and accepts telephone access from the destination user. 6. The network system according to any one of claims 1 to 5, wherein the server has a voice recognition function and a voice synthesis function, and allows a user to upload data by voice using a telephone. If accepted and the destination user has only a terminal, the data is transmitted to the terminal in the mail data format. If the destination user has only the facsimile, the data is transmitted to the facsimile in the FAX data format, and if the destination user has only the telephone. A network system characterized in that uploaded data is transmitted as voice data to the telephone, and if there is any one of a terminal, a facsimile, and a telephone that matches the uploaded data format, the data is transmitted in that data format. 7. The network system according to claim 6, wherein the server preferentially transmits data in the order of the terminal, the facsimile, and the telephone. 8. The network system according to any one of claims 4 to 7, wherein data is transmitted to any one of a terminal, a facsimile, and a telephone used for access by a destination user. Network system. 9. The network system according to claim 7 or 8, wherein when the data is transmitted to a terminal or a facsimile of the destination user, and the destination user has a telephone, the data transmission is performed by the telephone. A network system characterized by notifying to.