JP4220679B2 - Network facsimile machine - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a network facsimile apparatus capable of transmitting and receiving facsimile data and electronic mail data by connecting to a telephone line network, a network such as the Internet or a LAN. In place Related.
[0002]
[Prior art]
Recently, personal computers, workstations, and fax servers are connected to a network to perform e-mail, homepage browsing, and facsimile transmission / reception.
[0003]
FIG. 23 shows a system configuration when facsimile transmission / reception is performed using a FAX server. The reception operation at the client machine (personal computer) is as follows. First, the FAX modem 1001 receives an incoming telephone line, captures image data, and passes the image data to the FAX server 1002. The FAX server software operating on the FAX server 1002 receives the image data and stores it as an image data file in the file server 1003 via the network. Up to this point, the accumulation of facsimile reception data is completed.
[0004]
In order to capture received image data into the client machine 1004, the user starts a dedicated application on the client machine 1004 and reads an image data file from the file server 1003 via the network.
[0005]
Recently, a method of reusing facsimile reception data by combining an Internet FAX and a WWW server has been proposed. This uses a function of converting data received from a telephone line by an Internet FAX into an electronic mail.
[0006]
FIG. 24 shows a system configuration in the case where facsimile transmission / reception is performed using an Internet FAX and a WWW server. The reception operation at the client machine will be described.
[0007]
First, image data received via the telephone line by the Internet FAX 1101 is converted into an email attachment file format within the Internet FAX and transmitted to the WWW server 1103 as an email attachment file.
[0008]
The e-mail transferred from the Internet FAX 1101 is received by the e-mail server 1102 via the network. The e-mail received by the e-mail server 1102 is transferred again to the destination WWW server 1103 via the network.
[0009]
The WWW server 1103 accumulates the attached file of the e-mail as image data and links it to the facsimile reception home page. Up to this point, the accumulation of facsimile reception data is completed.
[0010]
In order to capture the received data into the client machine 1104, the user starts a WWW browser on the client machine 1104 and accesses the facsimile reception home page of the WWW server 1103. Then, the image data file is read from the WWW server 1103 to the client machine 1104 via the network.
[0011]
[Problems to be solved by the invention]
However, in the system using the above-described FAX server, image data is transferred between the FAX server and the file server and between the file server and the client machine until the facsimile reception data reaches the client machine. There is a problem that network traffic increases.
[0012]
Further, in the system using the Internet FAX and the WWW server described above, before the facsimile reception data reaches the client machine, between the Internet FAX and the E-mail server, between the E-mail server and the WWW server, and the WWW server, Since image data is transferred to and from the client machine, there is a problem that network traffic increases. In addition, since the image data attached to the e-mail has a data capacity that is about 1.3 times that of binary data, the network traffic further increases.
[0013]
The present invention has been made in view of the above-described problems, and is a network facsimile apparatus capable of reducing network traffic due to data transfer. Place The purpose is to provide.
[0014]
[Means for Solving the Problems]
The present invention includes a facsimile communication unit that transmits and receives facsimile data via a telephone line, a network communication unit that transmits and receives data via a network, A storage unit for storing a telephone number or an e-mail address of a transmission partner associated with a key operation of the panel unit; The sender Includes phone number or email address Structured document describing the address book A generator that generates , Clients that accessed using a URL Machine In response to Above Address book Described Send structured document to client Machine Is the address book Additional registration of the phone number or email address of the recipient based on the structured document describing If you ask for Configure the add recipient screen where you can enter the phone number or email address of the recipient A WWW server unit for sending structured documents Then, the telephone number or e-mail address of the transmission partner associated with the key operation of the panel unit stored in the storage unit is incorporated into the structured document describing the address book by the generation unit. I did it.
[0015]
DETAILED DESCRIPTION OF THE INVENTION
A first aspect of the present invention includes a facsimile communication unit that transmits and receives facsimile data via a telephone line, a network communication unit that transmits and receives data via a network, A storage unit for storing a telephone number or an e-mail address of a transmission partner associated with a key operation of the panel unit; The sender Includes phone number or email address Structured document describing the address book A generator that generates , Clients that accessed using a URL Machine In response to Above Address book Described Send structured document to client Machine Is the address book Additional registration of the phone number or email address of the recipient based on the structured document describing If you ask for Configure the add recipient screen where you can enter the phone number or email address of the recipient A WWW server unit for sending structured documents Then, the telephone number or e-mail address of the transmission partner associated with the key operation of the panel unit stored in the storage unit is incorporated into the structured document describing the address book by the generation unit. Take the configuration.
[0016]
According to this configuration, The telephone number or e-mail address of the other party associated with the key operation on the panel can be confirmed as an address book on the client machine, and the telephone number or e-mail address of the other party can also be registered in the address book from the client machine. Will be able to .
[0017]
According to a second aspect of the present invention, in the network facsimile apparatus according to the first aspect, the WWW server unit includes: If the client machine requests deletion of the telephone number or email address of the transmission partner based on the structured document describing the address book, a destination deletion screen capable of deleting the telephone number or email address of the transmission partner is configured. To send a structured document to be deleted, and delete the telephone number or e-mail address of the transmission partner input from the structured document constituting the address deletion screen from the structured document describing the address book. Take the configuration.
[0020]
According to this configuration, the address book Described Client that received the structured document Machine When an address book address deletion is requested from the client, the structured document linked to the program corresponding to the address deletion is the client. Machine So the client enters the delete address on the structured document by doing , Address book in WWW server part Described The corresponding address is deleted from the structured document.
[0021]
First of the present invention 3 The aspect of the 1 or 2 In the network facsimile apparatus according to the aspect, the WWW server unit includes: When the client machine requests editing of the telephone number or email address of the other party based on the structured document describing the address book, a destination edit screen is displayed that allows the telephone number or email address of the other party to be edited. The structured document is sent, and the telephone number or e-mail address of the transmission partner input from the structured document constituting the destination edit screen is registered in the structured document describing the address book. Take the configuration.
[0022]
According to this configuration, the address book Described Client that received the structured document Machine When an address book edit is requested by a client, a structured document linked to a program that supports address editing is displayed on the client. Machine So that the client can edit the address on the structured document. The input by doing , Address book in WWW server part Described The corresponding address is edited from the structured document.
[0033]
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0034]
FIG. 1 shows functional blocks of the network facsimile apparatus according to this embodiment. A ROM 1, a RAM 3, and an external storage device 4 are connected to the CPU 1 operating on the operating system so that the CPU 1 can access it. Various programs including a server side processing program are stored in the ROM 2, and the RAM 3 is used as a work area for programs stored in the ROM 2. The external storage unit 4 stores compressed image data, HTML files, and the like.
[0035]
The network facsimile apparatus according to this embodiment includes a scanner 5, a printer unit 6, a panel unit 7, a compression / decompression unit 8, a FAX / voice communication unit 9, and a network control unit 10. It is configured to operate under the management of the CPU 1.
[0036]
In this network facsimile apparatus, the scanner unit 5 reads image data such as a document, and the printer unit 6 prints the read image data or the received image data. Also, the panel unit 7 allows the user to perform operations such as an image reading instruction and destination address input, and the compression / decompression unit 8 decompresses the received image data or compresses the read image data. . The FAX / voice communication unit 9 is connected to a telephone line to perform facsimile communication and voice communication, and the network control unit 10 is connected to a network to perform Internet communication.
[0037]
The programs stored in the ROM 2 include the HTML file generation unit 11, the WWW server unit 12, the electronic mail communication unit 13, and the TIFF conversion unit 14. The HTML file generation unit 11, the WWW server unit 12, the e-mail communication unit 13, and the TIFF conversion unit 14 are functions provided by the CPU 1 executing these programs. For convenience of explanation, as shown in FIG. These functions will be described using reference numerals given to the program itself.
[0038]
The HTML file generation unit 11 is a functional block that converts a list of image data received by FAX and e-mail into an HTML file that can be viewed on a home page and registers the server.
[0039]
The WWW server unit 12 provides a server function such as communication with the WWW browser according to the HTTP protocol and delivery of homepage data (HTML file).
[0040]
The e-mail communication unit 13 functions as an e-mail server in addition to sending and receiving e-mails via a network. The TIFF conversion unit 14 provides a function for converting encoded facsimile data and document file data into the TIFF format.
[0041]
FIG. 2 shows a system configuration when the network facsimile apparatus according to this embodiment is connected to a telephone line and a network. In FIG. 2, a network facsimile apparatus 201 is connected to a telephone line and to a network via a network interface. By operating a WWW browser on the client machine 202, a homepage provided on the network facsimile apparatus 201 can be browsed.
[0042]
FIG. 3 shows functional blocks of the HTML file generation unit 11, the WWW server unit 12, the e-mail communication unit 13, the TIFF conversion unit 14, and the FAX / voice communication unit 9, and the flow of data processing between the blocks.
[0043]
In the WWW server unit 12, the WWW server communication unit 31 communicates with a WWW browser operating on the client machine 202 in accordance with the HTTP protocol. The command received by the WWW server communication unit 31 from the client machine 202 is analyzed by the CGI string analysis unit 32.
[0044]
When a character string for CGI processing is detected from the received data, the CGI string analysis unit 32 passes the received data to the CGI application determination unit 33 and activates the corresponding CGI application 34. The CGI application 34 decodes the received data that has been URL-encoded and executes predetermined processing. The CGI application 34 includes applications such as transmission, deletion, editing, movement, address book generation, and device setting of HTML documents.
[0045]
The file sending unit 35 receives the file requested by the client machine 202 from the file management unit 36 and passes it to the WWW server communication unit 31. In the case of a file request for which CGI processing is not requested, the file sending unit 35 requests the file management unit 36 for the file.
[0046]
The HTML file generation unit 11 includes a document list generation unit 37 that generates an HTML file of a document list, and an address book generation unit 38 that generates an HTML file of an address book.
[0047]
The document list generation unit 37 creates an HTML file of the received list displaying the received e-mail and received FAX, and deletes, edits, moves, etc. a part of the HTML file according to a command and received data given from the CGI application 34. .
[0048]
The address book generation unit 38 modifies the HTML file of the address book according to the command and received data from the address book CGI application. The address book generation unit 38 also executes processing for incorporating the latest address table data into the HTML file of the address book when the power is turned on or when the contents of the address book are changed.
[0049]
The HTML file generation unit 11 includes a communication result list generation unit 39 and a status information generation unit 41. The communication result list generation unit 39 creates and updates an HTML file representing the communication result list by receiving log information indicating the communication result from the FAX / voice communication unit 9 and the e-mail communication unit 13. The status information generating unit 41 takes in status signals indicating their states (paper jam occurrence, toner shortage, communicating, etc.) from the scanner unit 5, the printer unit 6, the panel unit 7, and the FAX / voice communication unit 9, and the above-described units. An HTML file in which the state is registered is created / updated.
[0050]
The FAX / voice communication unit 9 and the e-mail communication unit 13 include a communication control unit, a storage processing unit, and a spooler. The communication control unit of the FAX / voice communication unit 9 is connected to a telephone line, and the communication control unit of the e-mail communication unit 13 is connected to various networks represented by the Internet by LAN or dial-up.
[0051]
Next, the operation of the network facsimile apparatus according to this embodiment will be described. In the following, description will be given separately for each operation of reception list generation, reception list editing, reception list BOX movement, address book generation, and apparatus setting.
[0052]
FIG. 4 shows a flowchart of the reception list generation operation. This network facsimile apparatus registers a reception list of received data received by the FAX / voice communication unit 9 or the e-mail communication unit 13 on the homepage.
[0053]
When data reception occurs, it is determined whether the reception form is a telephone line or the Internet (ST401). The case where the electronic mail communication unit 13 receives an electronic mail is reception from the Internet. In this case, if the e-mail communication unit 13 receives the e-mail (ST402) and the attached data is image data in a TIFF (Tag Images File Format) format, which is a standard format of the image file, for example, “mail0001.tif”. Such a file name is assigned and stored in the external storage unit 4 (ST407), and if it is audio data, a file name such as “audio0001.wav” is assigned and stored in the external storage unit 4 (ST407).
[0054]
On the other hand, when the FAX / voice communication unit 9 receives FAX data or voice data, it is received from the telephone line. In the case of reception from a telephone line, the FAX / voice communication unit 9 receives image data or voice data (ST403), and determines whether the received data is voice data (ST404). If the received data is encoded image data, the TIFF conversion unit 14 is requested to convert the encoded data into TIFF format (ST405). A file name (for example, “fax0001.tif”) is assigned to the received data (image data) converted into the TIFF format and stored in the external storage unit 4 (ST407). If the received data is audio data, the audio data is digitally converted (ST406), and the audio file with the file name is stored in the external storage unit 4 (ST407).
[0055]
After storing the received data in the external storage unit 4, the HTML file generation unit 11 adds the file name to the reception list and updates the HTML file in the reception list (ST408).
[0056]
The update of the HTML file of the reception list will be specifically described. The document list generation unit 37 of the HTML file generation unit 11 updates the HTML file of the reception list. The document list generation unit 37 manages a reception list table stored in the external storage unit 4. FIG. 5 shows a configuration example of the reception list management table. In the reception list table, the document file name, registration date, sender, and title are registered for each document number assigned in the order of reception.
[0057]
The document list generation unit 37 receives the document file name, registration date, sender, and title from the received FAX / voice communication unit 9 or e-mail communication unit 13. The reception list is read out via the file management unit 36, the document number is added to the reception list, and the document file name, registration date, sender, and title are registered there. The reception list in which the document name of the reception data is registered is returned to the reception list table, and the reception list html (HTML file of the reception list) is read.
[0058]
FIG. 6 shows a source file of the reception list html created for the reception data received from the network. As shown in the figure, a comment line is inserted at the head of each reception list, and identification data indicating a reception form and a document number are described at the position of the comment line. Following the comment line, the document number, date / time, sender, and title are described in a THML document. FIG. 12 shows a configuration example of the reception list displayed based on the reception list html of FIG.
[0059]
The document list generation unit 37 converts the document number, date and time, sender, and title of the new received data into an HTML document and generates list data. On the other hand, the reception list html is searched from the top, the first comment line (<!-) Corresponding to the first line of the current reception list is detected, and the list data of the new reception data is stored in one line of the reception list. Insert into eyes. By returning the updated reception list html to the external storage unit 4, a list of new reception data is registered on the home page. Specifically, an HTML file prepared in advance for displaying the reception list page is read, and a character string such as a document number as management data newly stored in the reception list table is written and edited. In the edited document number character string “00243”, By attaching the tag <A HREF="ifax0001.tif">, the character string “00243” and the received file ifax0001.tif are linked.
[0060]
It is assumed that a list is generated in the HTML document in the same manner for the FAX reception list related to the image data received by FAX, the voice reception list related to the received voice data, and the like.
[0061]
As described above, when the FAX / voice communication unit 9 receives the FAX data or the e-mail communication unit 13 receives the e-mail, the document list generation unit 37 stores the data (sender, title, etc.) necessary for creating the list. Since the document list generation unit 37 reads the HTML file of the reception list from the external storage unit 4 and adds it to the reception list, the client machine 202 accesses the WWW server unit 12 to receive the latest reception in the homepage format. A list can be provided.
[0062]
Next, the operation of sending the data received and accumulated by the network facsimile apparatus to the client machine 202 will be described with reference to the flowchart of FIG.
[0063]
The network facsimile apparatus is in a standby state until a home page address (URL address) is input.
[0064]
Client machine 202 connected to the network activates a WWW browser (homepage browsing software) and enters the URL address of the network facsimile apparatus to access the homepage (ST701).
[0065]
In the network facsimile apparatus that has received the access, the WWW server unit 12 starts processing through the network control unit 10. The file sending unit 35 of the WWW server unit 12 receives a command requesting the main screen file (index html) of the home page received from the client machine 202, reads the file from the external storage unit 4, and reads the WWW of the client machine 202. Return to the browser (ST702). FIG. 8 shows a file relation table of HTML files registered in the external storage unit 4. Files necessary for displaying the home page are associated with the files on the main screen of the home page.
[0066]
When the WWW browser of the client machine 202 receives the file (html) of the home page main screen, the WWW browser analyzes the contents and sends a command for requesting a file necessary for displaying the home page to the WWW server unit 12 (ST703). ). For example, if the main screen of the home page as shown in FIG. 9 is displayed, each icon display of a fax received document, Internet received document, personal box, bulletin board document, address book, communication result report, user setting, and setting list The WWW server unit 12 is requested for files (such as sdoc.gif and kdoc.gif shown in FIG.
[0067]
When WWW server unit 12 receives a file request necessary to display the main screen of the home page, it sends the file stored in external storage unit 4 to the WWW browser of client machine 202 (ST704). As a result, the home page of the network facsimile apparatus is displayed on the screen of the client machine 202 (ST705). The network facsimile apparatus waits until the next selection is made.
[0068]
It waits for the user's desired icon to be selected on the client machine 202 on which the main screen shown in FIG. 9 is displayed. For example, it is assumed that “FAX reception list” is selected from the display data. When the “FAX reception list” icon is selected, a file request for the FAX reception list linked to the icon display position is generated (ST706).
[0069]
As shown in FIG. 8, the HTML file (fdoc.html) is linked to the “FAX reception list” icon. The WWW browser is fdoc. A FAX reception list can be displayed from html. In the WWW server unit 12, the fdoc. When an html file request is received, the corresponding file is read from the external storage unit 4 and sent to the client machine 202 (ST707).
[0070]
The WWW browser of the client machine 202 displays the “FAX reception list” screen according to the “FAX reception list” HTML file received from the WWW server unit 12 (ST708).
[0071]
When the user selects and displays a desired file number from the FAX reception list on the client machine (ST709), the network facsimile apparatus transmits an image data file (ST710). If image data (for example, file0001.tif) cannot be displayed on the WWW browser of the client machine 202 (ST711), the image data is displayed via a helper application for displaying the TIFF file (ST712) (ST713).
[0072]
In the above example, the case where the data received by FAX is displayed has been described. However, when an audio file is selected, the linked audio data is reproduced from the speaker of the client machine. The voice data includes voice data received from the outside and voice data that is included in the handset of the network facsimile apparatus. The voice data can be linked to a home page or transmitted to the outside.
[0073]
Next, the operation of the WWW server unit 12 will be described. FIG. 10 is a flowchart showing the operation of the WWW server unit 12. The WWW server communication unit 31 receives a request or returns a response from the client machine 202 via the network by operating according to the HTTP protocol. Requests received by the WWW server communication unit 31 are roughly divided into two types according to commands: file requests and CGI processing requests.
[0074]
The received data (request) received by the WWW server communication unit 31 is given to the CGI string analysis unit 32. The CGI string analysis unit 32 analyzes the CGI string from the received data. When the CGI process is not performed (ST100), the file sending unit 35 extracts the corresponding file from the external storage unit 4 based on the document number included in the received data and returns it to the client (ST101).
[0075]
The CGI string analysis unit 32 decodes the URL encoded part of the received data (ST102). Decoded data that is the analysis result of the CGI string is passed to the CGI application determination unit 33. If the CGI application determination unit 33 determines an error such as when the CGI process is requested for the decoded data but the application name is not specified (ST104), the CGI application determination unit 33 issues an error notification to the file transmission unit 35 and outputs the error to the external storage unit 4 The HTML file for error notification is taken out from and sent to the client machine (ST105).
[0076]
When error processing is not performed in step ST104, processing according to the contents of the CGI application is executed. The CGI application supported by the WWW server unit 12 according to the present embodiment includes deletion, editing, movement of various reception lists, creation / embedding of an address book, device setting, and the like.
[0077]
As a result of the process determination, the CGI application determination unit 33 (1) requests to delete the designated document number from the HTML file of the reception list (ST106), and (2) changes the data of the designated document number to the edited data. When requesting replacement (ST107), (3) When requesting to move the designated document number to an HTML file of another reception list (ST108), the reception list processing is executed (ST109). The contents of the reception list process will be described later.
[0078]
As a result of the process determination by the CGI application determination unit 33, (4) When requesting that the contents of the address book (additional address, data deletion, data correction) be reflected in the address book THML file (ST110), the address The received data is passed to the book CGI application to execute address book processing (ST111).
[0079]
Further, as a result of the process determination by the CGI application determination unit 33, (5) when it is requested to update the device setting content set in the file management unit 36 (ST112), the received data is passed to the device setting CGI application. Then, update processing of the setting flag of the file management unit 36 is executed (ST113).
[0080]
As a premise that the reception list process is executed in the above step 109, necessary data is input on the HTML document screen in the client machine 202. In step 706 of the flowchart shown in FIG. 7, the Internet reception list icon is selected on the home page main screen (on the HTML document screen) shown in FIG. Thereby, a file request is made to the WWW server unit 12 for the HTML file linked to the Internet reception list.
[0081]
As described above, the HTML file of the Internet reception list is registered in the server-side external storage unit 4 and is updated by the document list generation unit 37 every time an e-mail is received. In response to a file request from the client machine 202, the WWW server unit 12 requests the file management unit 36 to read the corresponding file from the file sending unit 35 and transmits the read HTML file of the Internet reception list to the client machine 202.
[0082]
The WWW browser on the client machine 202 displays an Internet reception list screen composed of HTML documents according to the received HTML file of the Internet reception list.
[0083]
FIG. 12 shows an Internet reception list screen composed of HTML documents. In this embodiment, it is composed of a list including document numbers, registration dates, senders, titles, and check icons, and a frame menu in which icons such as transmission, print, delete, edit, and move are arranged. In this way, the Internet received document screen can be presented to the user.
[0084]
The user selects a document number to be worked on the Internet received document screen of FIG. The document number is selected by checking the selection box. After selecting the document number, an arbitrary work is selected from the frame menu.
[0085]
When the “Send” icon is selected as the work content, the file of the document number on the reception list can be sent to the transmission destination. When the “Send” icon is selected, the WWW server unit 12 is requested for an HTML document constituting a send screen. The transmission screen has a box in which a document number to be transmitted and a destination (fax number, mail address) can be input. When the WWW browser of the client machine acquires the HTML document of the transmission screen, the transmission screen is displayed based on the HTML document. Enter the document number and destination (fax number, mail address) on the send screen and press the enter button. When the determination button is pressed, a transmission CGI application is selected, and request data in which a document number and a destination are set is transmitted to the WWW server unit 12.
[0086]
When the WWW server unit 12 receives the request data, the transmission CGI application is activated. A document number and a destination to be transmitted are given to the communication unit. For example, if the destination is an email address, the document number and the destination email address are input to the email communication unit 13. The e-mail communication unit 13 takes out the file having the designated document number from the external storage unit 4 via the file management unit 36, and transmits it as an e-mail to the destination.
[0087]
In addition, when the “delete” icon is selected by the user, the WWW browser on the client machine 202 requests the WWW server unit 12 for an HTML file linked to the “delete” icon.
[0088]
When the WWW server unit 12 receives the file request, the WWW server communication unit 31 notifies the file sending unit 35 of the file name of the HTML file linked to the “delete” icon. The file sending unit 35 takes out the corresponding file from the external storage unit 4 via the file management unit 36 and sends it to the client machine 202. FIG. 13 shows an example of the configuration of an HTML document screen used for deleting a document number from the reception list. The previously selected document number is automatically inserted into the document number column.
[0089]
The user confirms the document number to be deleted automatically inserted in the document number column, and then selects the decision button. When the determination button is selected, a deletion CGI application is selected as an application type, and request data in which a document number to be deleted is set is transmitted to the WWW server unit 12.
[0090]
Further, the WWW browser on the client machine 202 selects the HTML file linked to the “edit” icon to the WWW server unit 12 when the “edit” icon is selected after the user selects the document number to be worked on. Request a file.
[0091]
When the WWW server unit 12 receives the file request, the WWW server communication unit 31 notifies the file sending unit 35 of the file name of the HTML file linked to the “edit” icon. The file sending unit 35 takes out the corresponding file from the external storage unit 4 via the file management unit 36 and sends it to the client machine 202. FIG. 14 shows a configuration example of an HTML document screen used for editing the document number, title, sender, etc. of the reception list.
[0092]
The previously selected document number, title, etc. are automatically inserted into the edit target column. Next, when the determination button is selected, an edit CGI application is selected as the application type, and request data in which the document number to be edited is set is transmitted to the WWW server unit 12.
[0093]
In addition, when the “move” icon is selected by the user, the WWW browser on the client machine 202 requests the WWW server unit 12 for an HTML file linked to the “move” icon.
[0094]
When the WWW server unit 12 receives the file request, the WWW server communication unit 31 notifies the file sending unit 35 of the file name of the HTML file linked to the “move” icon. The file sending unit 35 takes out the corresponding file from the external storage unit 4 via the file management unit 36 and sends it to the client machine 202. FIG. 15 shows a configuration example of an HTML document screen used for moving the document number on the reception list.
[0095]
The document number selected before selecting the “move” icon is automatically inserted into the column of the document number. The user enters the corresponding folder name in the column for the source folder and the column for the destination folder, and selects the enter button. When the determination button is selected, the WWW browser selects the mobile CGI application as the application type, and transmits the request data in which the document number to be moved is set to the WWW server unit 12.
[0096]
As described above, request data requesting CGI processing is transmitted from the client machine 202 to the WWW server unit 12. As shown in the flowchart of FIG. 10, in the WWW server unit 12, the CGI string data analyzed from the received data (request data) by the CGI string analysis unit 32 is passed to the CGI application determination unit 33, and the corresponding CGI application is determined. The
[0097]
When a delete, edit, or move CGI application is executed, a command and received data corresponding to the processing contents are given from the CGI application to the document list generation unit 37.
[0098]
In the above description, the case where various operations are performed from the Internet received document screen has been described, but it is possible to shift to various operations from the FAX reception screen by the same operation.
[0099]
When the address book CGI application is executed, a command and received data corresponding to the processing content are given from the CGI application to the address book generation unit 38.
[0100]
When the device setting CGI application and the transmission CGI application are executed, data is given to the file management unit 36 by an instruction and reception according to the processing content.
[0101]
The document generation unit 37 receives received data from the deletion, editing, or mobile CGI application. When the reception list processing is deletion, the document number input on the HTML document screen of FIG. 13 from the deletion CGI application is passed as reception data, and deletion of the document is instructed. When the reception list process is editing, the document number and the editing content input from the editing CGI application on the HTML document screen of FIG. 14 are passed as received data, and editing of the document is instructed. Further, when the reception list processing is movement, the document number, the movement source folder, and the movement destination folder number input from the movement CGI application to the HTML document screen of FIG. 15 are passed as received data, and the movement of the document is instructed. .
[0102]
FIG. 11 is a flowchart when the document list generation unit 37 operates according to request data for requesting CGI processing. The document number passed from the CGI application is searched from the HTML file of the reception list (ST1101). Next, it is determined whether or not an instruction is given as editing processing content (ST1102).
[0103]
For example, when editing of the Internet reception list is instructed as CGI processing, the HTML file of the Internet reception list is read from the external storage unit 4 and the position of the document number to be edited is searched. The data of the corresponding document number (title, sender, etc.) is replaced with the edited data (received data) (ST1103).
[0104]
By returning the HTML file of the Internet reception list in which the data of the corresponding document number is replaced with the edited data, the HTML file of the Internet reception list is partially rewritten.
[0105]
On the other hand, when the editing process is not instructed, the remaining process is deletion or movement, so that the corresponding document number is deleted from the current location of the reception list HTML file. Therefore, when it is determined that the processing instructed in step 1102 is not editing, the data of the corresponding document number is deleted from the reception list HTML file (ST1104).
[0106]
Next, it is determined whether or not a document movement between reception lists (for example, Internet reception list to FAX reception list) is instructed as a CGI process from the CGI application (ST1105).
[0107]
When document movement is instructed, both the HTML file of the movement source reception list and the HTML file of the movement destination reception list are read from the external storage unit 4 in the processing of step 1101. Since the corresponding document number has been deleted first from the HTML file of the movement source reception list, the data of the corresponding document number is added to the HTML file of the movement destination reception list (ST1106). By storing the HTML files of the reception list from which the data of the corresponding document number is deleted and the reception list to which the data of the corresponding document number is added in the external storage unit 4, the movement of the document data between the reception lists is completed. . If the movement of the document data is not executed, the document data is simply deleted from the reception list.
[0108]
As described above, in response to a request from the client machine 202, the WWW server unit 12 transmits a reception list operation screen (delete, edit, or move), and data input by the user to the reception list operation screen on the client machine 202 And the work content (deletion, editing, or movement) are sent to the WWW server unit 12, and the document list generation unit 37 of the WWW server unit 12 reflects the data input by the user in the HTML file of the reception list according to the work content. Since it did in this way, the receiving list shown by the WWW server part 12 in a homepage format can be corrected.
[0109]
Further, as a premise that the address book process is executed in step 111, necessary data is input on the HTML document screen in the client machine 202. In step 706 of the flowchart shown in FIG. 7, the address book icon is selected instead of the Internet reception list icon on the home page main screen (on the HTML document screen) shown in FIG. As a result, an HTML file of the address book linked to the address book icon is requested to the WWW server unit 12.
[0110]
An HTML file of the address book is registered in the external storage unit 4 on the server side. In response to the file request from the client machine 202, the WWW server unit 12 requests the file management unit 36 to read the address book html, and transmits the read HTML file of the address book html to the client machine 202. .
[0111]
On the client machine 202, an address book screen composed of HTML documents is displayed according to the HTML file of the address book received by the WWW browser.
[0112]
FIG. 16 shows an address book HTML document screen. In the present embodiment, the address book screen is composed of address information including names, types, addresses, and check icons, and a frame menu in which icons such as add, delete, and edit are arranged. A symbol indicating FAX or electronic mail is entered in the type column. In the address column, a telephone number is entered if the type is FAX, and an e-mail address is entered if the type is E-mail.
[0113]
When operating the contents of the address book registered in the homepage format on the WWW server side, the user can select an operation corresponding to the operation contents from the frame menu.
[0114]
When the “add” icon is selected by the user, the WWW browser on the client machine 202 requests the WWW server unit 12 for an HTML file linked to the “add” icon.
[0115]
When the WWW server unit 12 receives the file request, the WWW server communication unit 31 notifies the file sending unit 35 of the file number of the HTML file linked to the “add” icon. The file sending unit 35 takes out the corresponding file from the external storage unit 4 via the file management unit 36 and sends it to the client machine 202. FIG. 17 shows an example of the configuration of an HTML document screen used to add an address book from the reception list.
[0116]
The user enters the name of the additional address in the name column, inputs FAX or e-mail in the type column, and further inputs the FAX number or e-mail address in the address column, and then selects the enter button. When the determination button is selected, the address book CGI application is selected as the application type, and the request data in which information on the additional address is set is transmitted to the WWW server unit 12.
[0117]
Further, when the “delete” icon is selected by the user, the WWW browser on the client machine 202 requests the WWW server unit 12 for an HTML file linked to the “delete” icon. The WWW server unit 12 sends the HTML file linked to the “delete” icon to the client machine 202 through the process of “add”.
[0118]
FIG. 18 shows a configuration example of an HTML document screen used for deleting an address from the address book. The user inputs the name and address (phone number or e-mail address) to be deleted in the name and address fields and selects the decision. When the decision is selected, the address book CGI application is set as the application type, and the request data in which the number to be deleted is set is transmitted to the WWW server unit 12.
[0119]
In addition, when the “edit” icon is selected by the user, the WWW browser on the client machine 202 requests the WWW server unit 12 for an HTML file linked to the “edit” icon.
[0120]
When the WWW server unit 12 receives the file request, the WWW server communication unit 31 notifies the file sending unit 35 of the file number of the HTML file linked to the “edit” icon. The file sending unit 35 takes out the corresponding file from the external storage unit 4 via the file management unit 36 and sends it to the client machine 202. FIG. 19 shows a configuration example of an HTML document screen used for editing the address book name and address. The user enters the edited name and / or address in the edit target column and selects the decision. When the decision is selected, the address book CGI application is set as the application type, and the request data in which the edit address number is set is transmitted to the WWW server unit 12.
[0121]
FIG. 20 is a flowchart in the case where the address book generating unit 37 is operated by request data requesting CGI processing. The address book generation unit 38 receives commands (addition, deletion, editing) and received data (name, address, etc.) representing the contents of the CGI processing from the address book CGI application, and also receives an HTML file of the address book from the external storage unit 4 Is read.
[0122]
The address book generation unit 37 determines whether or not the command is an address addition (ST1201). If the address addition is a command content, the address book generation unit 37 adds an additional address and name to the HTML file of the address book (ST1202).
[0123]
On the other hand, if the command is not an address addition, the remaining processing is editing or deletion, so the corresponding address data included in the received data is deleted from the HTML file of the address book (ST1203). Next, it is determined whether or not the command content is editing of the address book (ST1204). If the command is editing, the corresponding address is retrieved from the HTML file, and the corresponding address is replaced with the edited address data and / or name (ST1205). By writing the HTML file of the address book changed as described above to the external storage unit 4, the latest address data is reflected on the home page of the address book.
[0124]
In this way, the WWW server unit 12 can present the address book in the form of a home page to the client machine 202, and the address book can be added and modified (deleted, edited) in response to a request from the client machine 202 Since the HTML document screen is displayed on the client machine 202, the additional correction data inputted by the user and the work contents are sucked up and transferred to the address book generation unit 38 to be reflected in the HTML file of the address book. The contents of the address book presented in the homepage format can be added and modified by the user from the client machine 202.
[0125]
Here, the network facsimile apparatus has an abbreviated dial table in which the abbreviated dial of the panel unit 7 is associated with a telephone number and an e-mail address. When the user presses the speed dial, the corresponding telephone number or e-mail data is read from the speed dial table and transferred to the FAX / voice communication unit 9 or the e-mail communication unit 13. Then, the FAX / voice communication unit 9 makes a call to the telephone number passed and transmits facsimile data, or the e-mail communication unit 13 transmits e-mail data from the network control unit 10 to the e-mail address passed.
[0126]
The speed dial table is arbitrarily added or modified by the user. On the other hand, the address book presented to the user in the homepage format by the WWW server unit 12 is not reflected in the address book of the homepage even if the speed dial table is rewritten. Therefore, it is necessary to accurately match the speed dial table with the contents of the address book HTML file.
[0127]
For this reason, the address book generation unit 38 executes address book incorporation processing in cooperation with the address book CGI application. When the power of the network facsimile apparatus is turned on, the data in the speed dial table is transferred to the address book generation unit 38. On the other hand, the HTML file of the address book is read from the external storage unit 4. The telephone number and e-mail address registered in the transferred speed dial table are incorporated into the HTML file of the address book. By this process, the contents of the speed dial table and the contents of the HTML file of the address book match. The HTML file of this address book is returned to the external storage unit 4.
[0128]
Next, an operation for setting the retention period of a document registered on the home page will be described. When a user setting icon is selected from the home page main screen in step 706, a file request regarding an HTML file linked to the user setting icon is transmitted from the client machine 202 to the WWW server unit 12. In the WWW server unit 12 that has received the file request regarding the HTML file for user setting, the file sending unit 35 takes out the corresponding user setting html from the external storage unit 4 and sends it to the client machine 202.
[0129]
In the client machine 202, the WWW browser displays the user setting screen from the user setting html. FIG. 21 shows a configuration example of the user setting screen. The user setting screen is configured so that a document retention period can be set for each fax received document and network received document. In the example shown in FIG. 21, the storage period is divided into one day, one week, and one month, but an arbitrary storage period may be set. When the user selects a storage period and document type on the user setting screen and selects a setting button, a CGI processing request for the device setting CGI application is transmitted to the WWW server unit 12 together with the setting data.
[0130]
In the WWW server unit 12, the CGI application determination unit 33 issues a CGI processing request to the device setting CGI application. The device setting CGI application passes setting data such as a storage period and a document type to the file management unit 36 and requests a change of the device setting.
[0131]
The file management unit 36 manages the storage period of documents (various HTML files, TIFF files, and audio file groups) stored in the external storage unit 4. When a retention period change instruction is received from the device setting CGI application, the table in which the retention period of the corresponding type is registered is rewritten according to the content of the instruction.
[0132]
FIG. 22 is a flowchart regarding document storage management of the file management unit 36. The retention period is managed in units of document types. When a document whose retention period is one day is detected (ST1221), a corresponding retained document is deleted (ST1222). ). For documents with a storage period of one week, if a document that has passed one week from the reception date and time is detected (ST1223), the corresponding stored document is deleted (ST1224). Further, if a document whose retention period is one month is detected when one month has passed since the reception date and time, the corresponding stored document is deleted (ST1225).
[0133]
As described above, an HTML document screen for designating a document storage period (device setting) in response to a request from the client machine 202 is displayed on the client machine, and data input from the user and device setting instructions are displayed on the WWW server unit 12, the document storage period (device setting) can be set by the same operation as accessing the home page from the client machine 202.
[0134]
【The invention's effect】
As detailed above, according to the present invention, The telephone number or e-mail address of the other party associated with the key operation on the panel can be confirmed as an address book on the client machine, and the telephone number or e-mail address of the other party can also be registered in the address book from the client machine. As a result, the convenience of the network facsimile machine is improved and the opportunity to handle image data on the client machine is reduced. Network traffic due to data transfer can be reduced Ru .
[Brief description of the drawings]
FIG. 1 is a functional block diagram of a network facsimile apparatus according to an embodiment of the present invention.
FIG. 2 is a configuration diagram of a system in which the network facsimile apparatus according to the embodiment is connected to a client machine.
FIG. 3 is a functional block diagram showing a part of processing flow in the network facsimile apparatus of the embodiment.
FIG. 4 is a flowchart of a reception list generation operation in the network facsimile apparatus of the embodiment.
FIG. 5 is a configuration diagram of a reception list management table.
FIG. 6 is a diagram showing an example of data in a source file of a reception list html
FIG. 7 is a flowchart of a transmission operation of data received and accumulated by the network facsimile apparatus according to the embodiment.
FIG. 8 is a diagram showing a file relation table of HTML files managed by the network facsimile apparatus of the embodiment.
FIG. 9 is a configuration diagram of a home page main screen provided by the network facsimile apparatus of the embodiment.
FIG. 10 is a flowchart showing the operation of the WWW server unit in the network facsimile apparatus of the embodiment.
FIG. 11 is a flowchart showing the operation of the document list generation unit in the network facsimile apparatus of the embodiment.
FIG. 12 is a configuration diagram of an Internet received document screen provided by the network facsimile apparatus according to the embodiment.
FIG. 13 is a configuration diagram of a reception list deletion screen provided by the network facsimile apparatus of the embodiment.
FIG. 14 is a configuration diagram of a reception list editing screen provided by the network facsimile apparatus according to the embodiment;
FIG. 15 is a configuration diagram of a reception list moving screen provided by the network facsimile apparatus according to the embodiment;
FIG. 16 is a configuration diagram of an address book screen provided by the network facsimile apparatus according to the embodiment.
FIG. 17 is a configuration diagram of an address book addition screen provided by the network facsimile apparatus according to the embodiment;
FIG. 18 is a configuration diagram of an address book deletion screen provided by the network facsimile apparatus according to the embodiment;
FIG. 19 is a configuration diagram of an address book editing screen provided by the network facsimile apparatus according to the embodiment;
FIG. 20 is a flowchart of address book processing in the network facsimile apparatus of the embodiment.
FIG. 21 is a configuration diagram of a retention period setting screen for user settings provided by the network facsimile apparatus according to the embodiment.
FIG. 22 is a flowchart of the deletion operation of the file management unit in the network facsimile apparatus of the embodiment.
FIG. 23 is a block diagram of a facsimile transmission / reception system using a FAX server.
FIG. 24 is a block diagram of a facsimile transmission / reception system using an Internet FAX and a WWW server.
[Explanation of symbols]
1 CPU
2 ROM
3 RAM
4 External storage
5 Scanner
6 Printer section
7 Panel section
8 Compression / decompression section
9 FAX / Voice Communication Department
10 Network controller
11 HTML file generator
12 WWW server
13 E-mail communication department
14 TIFF converter
31 WWW Server Communication Department
32 CGI string analyzer
33 CGI app decision section
34 CGI applications
35 File sending part
36 File Management Department
37 Document list generator
38 Address book generator
39 Communication result list generator
41 Status information generator

Claims (3)

Stores a facsimile communication unit that transmits / receives facsimile data via a telephone line, a network communication unit that transmits / receives data via a network, and a telephone number or e-mail address of a transmission partner associated with a key operation on the panel unit. a storage unit, describing a generating unit that generates a structured document that describes the address book that contains the phone number or e-mail address of the transmission destination, the address book in response to a request of the client machine that has been accessed using a URL When you send a structured document and the client machine requests additional registration of the phone number or email address of the recipient based on the structured document describing the address book , enter the phone number or email address of the recipient WWW for transmitting the structured document constituting the possible destination addition screen ; And a Ba unit, telephone number or e-mail address of the transmission destination associated with the key operation of the panel portion stored in the storage unit, integrated into the structured document that describes the address book by the generating unit A network facsimile machine. The WWW server unit can delete the telephone number or e-mail address of the transmission partner if the client machine requests the deletion of the telephone number or e-mail address of the transmission partner based on the structured document describing the address book. A structured document constituting a simple address deletion screen, and deleting the telephone number or e-mail address of the transmission destination input from the structured document constituting the address deletion screen from the structured document describing the address book 2. The network facsimile apparatus according to claim 1, wherein: The WWW server unit can edit the telephone number or email address of the transmission partner when the client machine requests editing of the telephone number or email address of the transmission partner based on the structured document describing the address book. A structured document constituting a simple address editing screen is transmitted, and a telephone number or an e-mail address of a transmission destination inputted from the structured document constituting the address editing screen is registered in the structured document describing the address book. The network facsimile apparatus according to claim 1 or 2, characterized in that

Images