JP5272625B2 - Incoming data notification system, network device, and incoming data notification method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system of notifying incoming data, a network device, and a method of notifying incoming data, which are capable of notifying reception when facsimile data is received. <P>SOLUTION: When a receiving apparatus 11 (a facsimile apparatus or the like) receives facsimile data or automatic telephone message sound (incoming data 4), the incoming data is transmitted to a terminal apparatus 31. When the terminal apparatus 31 receives the incoming data, first of all, the incoming data 4 is transmitted to a server 51 via an Internet network 3, and stored in the server 51. Next, the server 51 transmits an incoming notification to the effect that the server 51 stores the incoming data to a client 71. On receiving the incoming notification, the client 71 accesses the server 51 to refer to the incoming data. Thereby, even when failure or the like occurs in the receiving apparatus 11, the incoming data can be held certainly. <P>COPYRIGHT: (C)2010,JPO&amp;INPIT

Description

  The present invention relates to an incoming data notification system, a network device, and an incoming data notification method. More specifically, the incoming data, which is incoming fax or answering machine voice data, is received by the network device, the incoming data is backed up to the server, and the incoming call is notified to the client that the incoming data has been received. The present invention relates to a data notification system, a network device, and an incoming data notification method.

Conventionally, in a situation where a common fax machine is used by a plurality of people in an office, data received by the fax machine is uploaded to a server via a network, and the uploaded data can be viewed by a specific person. A method has been proposed (see, for example, Patent Document 1). As a result, the received data can be confirmed without bothering to approach the FAX device.
JP 2002-232633 A

  However, the above-described method has a problem in that it is necessary to periodically access the server and check the presence or absence of the received data because the timing at which the FAX device receives the data is unknown.

  The present invention has been made to solve the above-described problems. When a FAX device receives data, the incoming data notification system, network device, and incoming data notification that can notify that the data has been received. It aims to provide a method.

In order to solve the above-mentioned problems, an incoming data notification system according to the first aspect of the present invention includes a receiving device that receives and transfers incoming data that is FAX or voice mail data transmitted from a transmitting terminal; A network device that receives the incoming data transferred from the receiving device, and a server that receives and backs up the incoming data transmitted from the network device, and a client from at least one of the network device and the server An incoming data notification system for notifying that the incoming data has been received, wherein the receiving device includes: device receiving means for receiving the incoming data; and the incoming call received by the device receiving means. Device transmitting means for transmitting data, and the network device transmits by the apparatus transmitting means First device receiving means for receiving the received data received, and first device transmitting means for transmitting the incoming data received by the first device receiving means to the server, wherein the server includes the network A first server receiving means for receiving the incoming data transmitted from the device; a server storage means for storing the incoming data received by the first server receiving means; and notification that the incoming data has been stored. First server transmission means for transmitting to the client an incoming notification that includes at least location information that is information for specifying a storage location of the incoming data. An acquisition sent from the client in response to the incoming call notification sent by the means for requesting acquisition of the incoming data A second server receiving unit that receives the request notification; and when the acquisition request notification is received by the second server receiving unit, the incoming data stored in the server storage unit is transmitted to the client. Second server transmitting means, wherein the client receives the incoming notification transmitted by the first server transmitting means, and the client received by the first client receiving means. A first client transmitting means for transmitting the acquisition request notification for receiving the incoming data from the storage location specified by the location information included in the incoming notification; and Second network receiving means for receiving the incoming data after the acquisition request notification is transmitted, and the network device further includes the first client device. Receivability determination for determining whether the server can receive the incoming data when the incoming data is received by one device receiving means and the incoming data is transmitted to the server by the first device transmitting means Means and means for determining whether or not the server can receive the incoming data, and device storage means for storing the incoming data, and the incoming data is stored in the device storage means. The second device transmitting means for transmitting the incoming notification including at least location information for specifying the storage location of the incoming data to the client and the incoming notification transmitted by the second device transmitting means. In response, when the acquisition request notification is received by the second device reception unit that receives the acquisition request notification from the client, and the second device reception unit, The incoming data stored in the serial device memory means and a third device transmitting unit that transmits to the client.

In addition to the configuration of the invention according to claim 1, the incoming data notification system of the invention according to claim 2 includes a partner that is information for specifying a destination of the incoming data in the incoming notification. It is characterized in that at least one of destination specifying information and incoming date / time specifying information which is information for specifying the date / time when the incoming data was received is included.

According to a third aspect of the present invention, in addition to the configuration of the first or second aspect of the invention, the network device may be configured such that the server receives the incoming data by the reception availability determination unit. Device monitoring means for monitoring whether or not the incoming data can be received in the server when it is determined that the server is not, the first device transmission means is the device monitoring means When it is determined that the incoming data can be received, the incoming data is transmitted to the server.

Further, the incoming data notification system of the invention according to claim 4, in addition to the configuration of the invention according to any one of claims 1 to 3, wherein the network equipment, the incoming data stored in the device storage means Device encryption means for encrypting the encrypted data, wherein the third device transmission means transmits encrypted incoming data which is the incoming data encrypted by the device encryption means, and the client transmits the second data When the client receiving means receives the encrypted incoming data, the client receiving means comprises client decrypting means for decrypting the encrypted incoming data.

Further, the incoming data notification system of the invention according to claim 5, in addition to the structure of the invention according to claim 4, wherein the network equipment, VoIP (Voice over IP) VPN for relaying data (Virtual Private Network ) It functions as a router, and the device encryption means encrypts the incoming data by a VPN function.

Further, the incoming data notification system of the invention according to claim 6, a network device that receives incoming data is the data of FAX or answering machine telephone voice transmitted from the transmitting terminal, the incoming data that has been transmitted from the network device A server that receives and backs up, and is an incoming data notification system in which at least one of the network device and the server notifies the client that the incoming data has been received. A first device receiving means for receiving the incoming data, and a first device transmitting means for transmitting the incoming data received by the first device receiving means to the server, wherein the server includes the network device A first server receiving means for receiving the incoming data transmitted by the first server; Server storage means for storing the incoming data received by the receiving means, and incoming notification for notifying that the incoming data has been stored, information for specifying the storage location of the incoming data A first server transmitting means for transmitting an incoming notification including at least certain location information to the client; and a notification transmitted from the client in response to the incoming notification transmitted by the first server transmitting means. A second server receiving unit that receives an acquisition request notification that is a notification for requesting acquisition of the incoming data, and the server storage unit when the acquisition request notification is received by the second server receiving unit Second server transmission means for transmitting the incoming data stored in the client to the client, wherein the client transmits the first server A first client receiving means for receiving the incoming call notification transmitted at the first client receiving means, and the storage location specified by the location information included in the incoming call notification received by the first client receiving means. First client transmission means for transmitting the acquisition request notification for receiving incoming data, and second client reception means for receiving the incoming data after the acquisition request notification is transmitted by the first client transmission means The network device is further configured to receive the incoming data at the first device receiving means, and when the incoming data is transmitted to the server at the first device transmitting means, The server receives the incoming data at a reception availability determination unit that determines whether or not reception data can be received, and the reception availability determination unit. The device storage means for storing the incoming data when it is determined that there is not, and the incoming notification including at least location information for specifying the storage location of the incoming data after the incoming data is stored in the device storage means In response to the incoming notification transmitted by the second device transmitting means, second device receiving means for receiving the acquisition request notification from the client, A third device transmitting unit configured to transmit the incoming data stored in the device storage unit to the client when the acquisition request notification is received by a second device receiving unit ;

According to a seventh aspect of the present invention, there is provided a network device that receives the incoming data from a receiving device that receives and forwards incoming data that is FAX or voice mail data transmitted from a transmitting terminal, and receives the incoming data. A network device that backs up to a server and notifies a client that the incoming data has been received, the first device receiving means for receiving the incoming data, and the first device receiving means received by the first device receiving means The server receives the incoming data at a first device transmitting means for transmitting incoming data to the server, a reception availability determining means for determining whether the server can receive the incoming data, and a reception availability determining means. If it is determined that the incoming data is not, the device storage means for storing the incoming data and the incoming data are stored in the device storage means. The incoming call notification for notifying that the incoming call data is stored, the incoming call notification including at least location information as information for specifying the storage location of the incoming call data to the client A second device transmitting means for transmitting, and a notification transmitted from the client in response to the incoming notification transmitted by the second device transmitting means, for requesting acquisition of the incoming data. A second device receiving means for receiving an acquisition request notification; and when the acquisition request notification is received by the second device receiving means, the incoming data stored in the device storage means is sent to the client. A third device transmitting means for transmitting.

According to an eighth aspect of the present invention, in addition to the configuration of the seventh aspect of the invention, the network device according to the eighth aspect includes a destination identification that is information for identifying a destination of the incoming data in the incoming notification. It includes at least one of information and incoming date / time information which is information for specifying the date / time when the incoming data was received.

Further, in the network device of the invention according to claim 9 , in addition to the configuration of the invention of claim 7 or 8 , it is determined by the reception availability determination means that the server has not received the incoming data. A device monitoring unit that monitors whether or not the incoming data can be received by the server, wherein the first device transmitting unit is configured to receive the incoming data at the device monitoring unit. When it is determined that a possible state is reached, the incoming data is transmitted to the server.

The network equipment of the invention according to claim 1 0, in addition to the configuration of the invention according to any one of claims 7 to 9, the device encryption to encrypt the incoming data stored in the device storage means And the third device transmitting unit transmits the encrypted incoming data that is the incoming data encrypted by the device encryption unit.

The network equipment of the invention according to claim 1 1, in addition to the configuration of the invention according to claim 1 0, wherein the network equipment, VoIP (Voice over IP) VPN for relaying data (Virtual Private Network ) It functions as a router, and the device encryption means encrypts the incoming data by a VPN function.

The network equipment of the invention according to claim 1 2 receives the incoming data is the data of FAX or answering machine telephone voice transmitted from the transmitting terminal, as well as back up the incoming data to the server, the incoming data to the client A first device receiving means for receiving the incoming data, and a first device for transmitting the incoming data received by the first device receiving means to the server. When the server determines that the incoming data is not received by the transmission means, the reception availability judgment means for judging whether the server can receive the incoming data, and the reception availability judgment means, the incoming call Device storage means for storing data, and after the incoming data is stored in the device storage means, the incoming data is stored A second device transmitting means for transmitting to the client an incoming notification including at least location information, which is information for specifying a storage location of the incoming data, Second device receiving means for receiving an acquisition request notification which is a notification transmitted from the client in response to the incoming notification transmitted by the device transmitting means and is a request for requesting acquisition of the incoming data; And a third device transmitting means for transmitting the incoming data stored in the device storage means to the client when the acquisition request notification is received by the second device receiving means. .

Further, the incoming data notification method of the invention according to claim 1 3, receiving apparatus, the called transferred from the receiver for receiving the incoming data is the data of FAX or answering machine telephone voice transmitted from the transmitting terminal transfers Executed in a network device that receives data and a server that receives and backs up the incoming data transmitted from the network device, and receives the incoming data from at least one of the network device and the server to a client. An incoming data notification method for notifying that the reception has been performed, in which the reception device receives the incoming data, and the reception device transmits the incoming data received in the device reception step . Device transmission step, and the network device transmits in the device transmission step A first device receiving step for receiving the received data, a first device transmitting step for the network device to transmit the incoming data received in the first device receiving step, and the server a first server receiving step of receiving the incoming data that has been transmitted from the network device, the server stores the incoming data received by the first server receiving step to servers storing means, before A first incoming notification for notifying that the incoming data has been stored, the incoming notification including at least location information as information for specifying the storage location of the incoming data to the client In response to the incoming notification transmitted in the first server transmission step, the server sends a server transmission step, A second server receiving step of receiving an acquisition request notification that is a notification for requesting acquisition of the incoming data, and the server receives the acquisition request notification in the second server receiving step. Is received, the second server transmission step of transmitting the incoming data stored in the server storage means to the client, and the client is transmitted in the first server transmission step A first client receiving step of receiving an incoming call notification; and the incoming data from the storage location specified by the location information included in the incoming call notification received by the client in the first client receiving step. A first client transmission step of transmitting the acquisition request notification to receive the request, and the client After the acquisition request notification at the client transmitting step is transmitted, a second client reception step of receiving the incoming data, the network equipment, the incoming data is received by the first device receiving step, the first When the incoming data is transmitted to the server in one device transmission step, a reception availability determination step for determining whether the server can receive the incoming data; and the network device in the reception availability determination step. When it is determined that the server has not received the incoming data, the incoming data is stored in the device storage means, and after the incoming data is stored in the device storage means, the storage location of the incoming data A second device transmission step for transmitting the incoming notification including at least location information for identifying the client to the client. A second device receiving step in which the network device receives the acquisition request notification from the client in response to the incoming notification transmitted in the second device transmitting step; and A third device transmission step of transmitting the incoming data stored in the device storage means to the client when the acquisition request notification is received in the reception step .

Further, the incoming data notification method of the invention according to claims 1 to 4, the network device receiving the incoming data is the data of FAX or answering machine telephone voice transmitted from the transmitting terminal, and the call that has been transmitted from the network device An incoming data notification method that is executed in a server that receives and backs up data, and that notifies the client that the incoming data has been received from at least one of the network device and the server, the network device A first device receiving step for receiving the incoming data, a first device transmitting step for the network device to transmit the incoming data received in the first device receiving step, and the server Receiving the incoming data transmitted from the network device; A server receiving step, the server, the incoming data received by the first server receiving step is stored in the servers storage means, the incoming notification for the previous SL incoming data to notify that it has been stored A first server transmission step of transmitting an incoming notification including at least location information, which is information for specifying a storage location of the incoming data, to the client; and the server in the first server transmission step. A second server receiving step of receiving an acquisition request notification that is a notification transmitted from the client in response to the incoming notification transmitted in response to requesting acquisition of the incoming data; and When the acquisition request notification is received in the second server reception step, the incoming data stored in the server storage means is A second server transmission step for transmitting to the client, a first client reception step for the client to receive the incoming notification transmitted in the first server transmission step, and a client for the first client reception step. A first client transmission step of transmitting the acquisition request notification to receive the incoming data from the storage location specified by the location information included in the incoming notification included in A second client reception step for receiving the incoming data after the acquisition request notification is transmitted in the first client transmission step; and the network device receives the incoming data in the first device reception step. In the first device transmission step, the incoming data is transmitted to the server. And the network device determines that the server has not received the incoming data in the reception availability determination step and the network device in the reception availability determination step. The incoming data is stored in the device storage means, and after the incoming data is stored in the device storage means, the incoming notification including at least location information for specifying the storage location of the incoming data is sent to the client A second device transmitting step for transmitting to the network device, the second device receiving step for receiving the acquisition request notification from the client in response to the incoming notification transmitted in the second device transmitting step, When the network device receives the acquisition request notification in the second device receiving step, the device A third device transmission step of transmitting the incoming data stored in the device storage means to the client .

In the incoming data notification system of the invention according to claim 1, since the incoming data is backed up by the server, it is possible to reliably retain the incoming data even if the incoming device that receives the incoming data breaks down. Become. The client can obtain incoming data from the server. Even when the server is down and the incoming data cannot be backed up, the network device stores the incoming data, so that the incoming data can be reliably held. The client can acquire incoming data from the network device.

In addition, in the incoming data notification system of the invention according to claim 2 , in addition to the effect of the invention of claim 1, the information on the destination of the incoming data and the information of the incoming date and time are sent to the client together with the incoming notification. It becomes possible to transmit. As a result, the client can specify the destination of the incoming data and the incoming date and time as well as the presence of the incoming data.

In the incoming data notification system of the invention according to claim 3 , in addition to the effect of the invention of claim 1 or 2, when uploading of incoming data to the server fails, the network device performs a health check of the server. Do. When the server returns, incoming data is transmitted to the server. This ensures that incoming data can be uploaded to the server even if the server is temporarily out of order or the communication line is temporarily unavailable. .

In addition, in the incoming data notification system of the invention according to claim 4 , in addition to the effect of the invention according to any one of claims 1 to 3 , the incoming data is transmitted from the network device to the client in an encrypted state. Therefore, it is possible to improve the confidentiality of incoming data.

In addition, in the incoming data notification system of the invention according to claim 5 , in addition to the effect of the invention of claim 4 , the incoming data is encrypted using the VPN function. As a result, encrypted incoming data can be communicated without depending on the form of the network to which the server, network device, and client are connected. In addition, the confidentiality of incoming data within the network can be further enhanced.

In the incoming data notification system according to the sixth aspect of the present invention, since incoming data can be received directly from the transmission source terminal, a separate receiving device for receiving incoming data is not required.

In the network device of the invention according to claim 7 , even if the server is down and the incoming data cannot be backed up, the network device stores the incoming data to ensure that the incoming data is retained. Is possible. The client can acquire incoming data from the network device.

The network device according to the eighth aspect of the invention, in addition to the effect of the invention according to the seventh aspect , transmits information on the destination of the incoming data and information on the incoming date and time to the client together with the incoming notification. It becomes possible. As a result, the client can specify the destination of the incoming data and the incoming date and time as well as the presence of the incoming data.

In addition, in the network device of the invention according to claim 9 , in addition to the effect of the invention of claim 7 or 8, when the upload of incoming data to the server fails, the network device performs a health check of the server. When the server returns, incoming data is transmitted to the server. This ensures that incoming data can be uploaded to the server even if the server is temporarily out of order or the communication line is temporarily unavailable. .

Further, in the network device of the invention according to claim 1 0, in addition to the effect of the invention according to any of claims 7 to 9, since the incoming data is sent to the client from the network device in a state of being encrypted Therefore, it is possible to improve the confidentiality of incoming data.

Further, in the network device of the invention according to claim 1 1, in addition to the effect of the invention according to claim 1 0, it encrypts the incoming data using the VPN functionality. As a result, encrypted incoming data can be communicated without depending on the form of the network to which the server, network device, and client are connected. In addition, the confidentiality of incoming data within the network can be further enhanced.

Further, in the network device of the invention according to claim 1 2, since it is possible to call directly incoming data from the transmission source terminal, it becomes unnecessary reception apparatus for receiving additional incoming data.

Further, the incoming data notification method of the invention according to claim 1 3, since the incoming data is backed up to the server, even if the incoming equipment coming incoming data has failed, to reliably hold the incoming data Is possible. The client can obtain incoming data from the server.

Further, the incoming data notification method of the invention according to claims 1 to 4, since the incoming data is backed up to the server, even if the incoming equipment coming incoming data has failed, to reliably hold the incoming data Is possible. The client can obtain incoming data from the server. Furthermore, since the network device can receive incoming data directly from the transmission source terminal, a receiving device for receiving incoming data separately becomes unnecessary.

  Embodiments of an incoming data notification system, a network device, and an incoming data notification method according to the present invention will be described below with reference to the drawings. These drawings are used for explaining the technical features that can be adopted by the present invention, and the configuration of the apparatus described, the flowcharts of various processes, etc., unless otherwise specified. It is not intended to be limited to that, but merely an illustrative example.

  First, with reference to FIG.1 and FIG.2, the system configuration | structure of the incoming data notification system 1 of this invention is demonstrated. FIG. 1 is a schematic diagram showing a system configuration of an incoming data notification system 1. As shown in FIG. 1, the incoming data notification system 1 includes a receiving device 11, a terminal device 31, a server 51, and a client 71.

  The terminal device 31 is connected to the Internet network 3 and the receiving device 11. The terminal device 31 is a device having a function as a so-called router or bridge that performs relay processing of data flowing through the network. Further, the terminal device 31 can receive from the receiving device 11 a FAX document (the one obtained by demodulating the received signal and restoring the document) and the answering machine voice received by the receiving device 11. The received FAX document or answering machine voice is converted into a data format (image data, voice data, etc., hereinafter referred to as “incoming data”) that can be referred to by the client 71. The terminal device 31 can communicate with the server 51 and the client 71 connected to the Internet network 3 via the Internet network 3 in the same manner.

  The receiving device 11 is connected to a public switched telephone network (hereinafter referred to as “PSTN network”) 2 and a terminal device 31. The receiving device 11 can receive a FAX document and an answering machine voice transmitted to itself via the PSTN network 2. Further, the receiving device 11 can transmit the received FAX document or answering machine voice to the terminal device 31 in response to a request from the terminal device 31. As the receiving device 11, for example, a facsimile machine can be used.

  The server 51 is connected to the Internet network 3. The server 51 can communicate with the terminal device 31 and the client 71 connected to the Internet network 3 through the Internet network 3 in the same manner.

  The client 71 can be connected to the Internet network 3. The connection method is not particularly limited, and may be connected by a wired cable, or may be connected to the Internet network 3 by communicating with an access point (not shown) by radio waves. The client 71 can communicate with the terminal device 31 and the server 51 connected to the Internet network 3 while being connected to the Internet network 3. As the client 71, for example, a mobile phone or a PC can be used.

  An outline of processing executed in the incoming data notification system 1 when a FAX document or an answering machine voice is received by the receiving device 11 will be described. When the receiving apparatus 11 receives a FAX document or answering machine voice via the PSTN network 2, the terminal apparatus 31 first acquires the FAX document or answering machine voice received by the receiving apparatus 11. Next, in the terminal device 31, the received FAX document or answering machine voice is converted into incoming data 4. Then, the terminal device 31 transmits the incoming data 4 to the server 51 via the Internet network 3. In the server 51, the incoming data 4 received from the terminal device 31 is stored and saved in the HDD 55 (see FIG. 5, described later). The incoming data 4 stored in the HDD 55 of the server 51 can be acquired from the client 71 via the Internet network 3. As a result, the incoming data 4 received by the receiving device 11 can be backed up to the server 51. Therefore, even if a failure occurs in the receiving device 11, the incoming data 4 can be safely held. It becomes possible to do. Further, the client 71 can acquire the FAX original received by the receiving apparatus 11 and the incoming data 4 of the answering machine voice via the server 51.

  Here, as shown in FIG. 2, it is assumed that the server 51 cannot receive the incoming data 4 from the terminal device 31 due to a failure of the server 51 or the like. In such a case, the terminal device 31 stores and stores the incoming data 4 in a storage device 40 (see FIG. 3, which will be described later) included in the terminal device 31. The incoming data 4 stored in the terminal device 31 can be acquired from the client 71 via the Internet network 3. As a result, even if the incoming data 4 cannot be backed up in the server 51, the incoming data 4 can be stored in the terminal device 31, so that the incoming data 4 can be safely held. It becomes. Further, even when the incoming data 4 cannot be backed up to the server 51, the client 71 acquires the incoming data 4 of the FAX manuscript received by the receiving device 11 or the answering machine voice via the terminal device 31. It becomes possible.

  The electrical configuration of the terminal device 31 will be described with reference to FIG. FIG. 3 is a schematic diagram illustrating an electrical configuration of the terminal device 31. As shown in FIG. 3, the terminal device 31 is a CPU 32 that controls each process executed by the terminal device 31, and a nonvolatile storage element that stores programs, parameters, setting values, and the like executed by the CPU 32. A ROM 33, a RAM 34 which is a volatile storage element for providing a temporary storage area necessary for the CPU 32 to execute processing, and a storage device 40 (memory card or the like) in which various tables and incoming data are stored. It is provided. The CPU 32 and the ROM 33, the RAM 34, and the storage device 40 are electrically connected via the bus 39 so that the CPU 32 can access the storage areas of the ROM 33, the RAM 34, and the storage device 40. .

  The terminal device 31 includes an Ethernet (registered trademark) interface (Ethernet (registered trademark) I / F) 35. The Ethernet (registered trademark) I / F 35 is electrically connected with a WAN port 36 and a LAN port 37. The WAN port 36 is provided to connect to the Internet network 3 (see FIG. 1) and perform communication via the Internet network 3. The LAN port 37 is provided for connecting to the receiving device 11 and communicating with the receiving device 11. The CPU 32 recognizes various data received from the Internet network 3 and the receiving device 11 so that various data output from the CPU 32 can be transmitted to the Internet network 3 and the receiving device 11. The CPU 32 and the Ethernet (registered trademark) I / F 35 are electrically connected via a bus 39.

  The terminal device 31 includes an analog telephone line interface (Foreign Exchange Office / Foreign Exchange Station, FXO / FXS) 38 for connection to the PSTN network. Then, the CPU 32 and the FXO / are connected so that the various data output from the CPU 32 can be transmitted to the PSTN network, and the various data received from the PSTN network can be recognized by the CPU 32. The FXS 38 is electrically connected via the bus 39.

  As described above, in the present embodiment, the terminal device 31 includes both the Ethernet (registered trademark) I / F 35 and the FXO / FXS 38, thereby enabling communication via the Internet network 3 and the receiving device 11, and the PSTN network. Both communication via 2 can be executed. With such a configuration, the terminal device 31 is directly connected to the PSTN network 2 and directly receives a FAX document or an answering machine voice via the PSTN network 2 (refer to modified examples (FIGS. 16 and 17), Even after that, the terminal device 31 having the above-described configuration can be used. As shown in the system configuration of FIG. 1, when the receiving device 11 is connected to the terminal device 31 and the terminal device 31 is configured to receive a FAX document or an answering machine voice from the receiving device 11, the terminal The apparatus 31 may be configured without the FXO / FXS 38.

  With reference to FIG. 4, the electrical configuration of the receiving apparatus 11 will be described. FIG. 4 is a schematic diagram illustrating an electrical configuration of the receiving device 11. As shown in FIG. 4, the reception device 11 is a CPU 12 that controls each process executed by the reception device 11, and a nonvolatile storage element that stores programs, parameters, setting values, and the like executed by the CPU 12. A ROM 13 and a RAM 14 which is a volatile storage element for providing a temporary storage area necessary for the CPU 12 to execute processing are provided. The CPU 12, the ROM 13, and the RAM 14 are electrically connected via the bus 22 so that the CPU 12 can access the storage areas of the ROM 13 and the RAM 14.

  The receiving apparatus 11 includes an input / output unit 23 for performing common input / output control (impedance conversion, timing control, etc.). The input / output unit 23 is electrically connected to the CPU 12 via the bus 22. The receiving device 11 includes an operation unit 16 for inputting an instruction from the outside and a display unit 19 capable of displaying a desired image, which are electrically connected to the input / output unit 23, respectively. Has been. Thereby, it is possible for the CPU 12 to recognize an input signal from each interface. Each interface can be controlled by the CPU 12.

  The receiving device 11 includes an Ethernet (registered trademark) I / F 20. A LAN port 23 is electrically connected to the Ethernet (registered trademark) I / F 20. The LAN port 23 is provided to connect to the terminal device 31 and perform communication with the terminal device 31. The CPU 12 and the CPU 12 are configured so that the various data output from the CPU 12 can be transmitted to the terminal device 31 and the various data received from the terminal device 31 can be recognized by the CPU 12. The Ethernet (registered trademark) I / F 20 is electrically connected.

  The receiving apparatus 11 includes an FXO / FXS 21 for connecting to the PSTN network 2. The CPU 12 and the CPU 12 are configured so that various data output from the CPU 12 can be transmitted to the PSTN network 2 and the various data received from the PSTN network 2 can be recognized by the CPU 12. The FXS / FXO 21 is electrically connected via the bus 22.

  The receiving device 11 includes a printing unit 15 for printing and outputting desired data. The CPU 12 and the printing unit 15 are electrically connected via the bus 22 so that the printing process can be performed based on the data output from the CPU 12.

  The electrical configuration of the server 51 will be described with reference to FIG. FIG. 5 is a schematic diagram showing an electrical configuration of the server 51. As shown in FIG. 5, the server 51 is necessary for the CPU 52 to control each process executed by the server 51, the ROM 53, which is a nonvolatile storage element in which the BIOS and the like are stored, and the CPU 52 to execute the process. A RAM 54 that is a volatile storage element for providing a temporary storage area, and a hard disk (HDD) 55 that is a storage element for storing programs, various tables, incoming data, and the like are provided. The CPU 52, the ROM 53, the RAM 54, and the HDD 55 are electrically connected via the bus 60 so that the CPU 52 can access the storage areas of the ROM 53, the RAM 54, and the HDD 55.

  The server 51 includes an input / output unit 58 for performing common input / output control (impedance conversion, timing control, etc.). The input / output unit 58 and the CPU 52 are electrically connected via the bus 60. The server 51 also includes a keyboard 56 for accepting an input operation from the user and a display 57 capable of displaying a desired video, and are electrically connected to the input / output unit 58, respectively. Thus, the CPU 52 can recognize an input signal from the keyboard 56. Further, the CPU 52 can display a desired video on the display 57.

  The server 51 includes an Ethernet (registered trademark) I / F 59. A LAN port 61 is electrically connected to the Ethernet (registered trademark) I / F 59. The LAN port 61 is provided for communicating with the terminal device 31 and the client 71 via the Internet network 3. The various data output from the CPU 52 can be transmitted to the Internet network 3, and the various data received via the Internet network 3 can be recognized by the CPU 52. The CPU 52 and the Ethernet (registered trademark) I / F 59 are electrically connected via the bus 60.

  The electrical configuration of the client 71 will be described with reference to FIG. FIG. 6 is a schematic diagram showing an electrical configuration of the client 71. As shown in FIG. 6, the client 71 is a CPU 72 that controls each process executed by the client 71, and a ROM 73 that is a nonvolatile storage element in which programs, parameters, setting values, and the like executed by the CPU 72 are stored. , A RAM 74 that is a volatile storage element for providing a temporary storage area necessary for the CPU 72 to execute processing, and a storage device 75 (such as a flash memory) for storing received incoming data are provided. It has been. The CPU 72, the ROM 73, the RAM 74, and the storage device 75 are electrically connected via the bus 82 so that the CPU 72 can access the storage areas of the ROM 73, the RAM 74, and the storage device 75.

  The client 71 includes an input / output unit 80 for performing common input / output control (impedance conversion, timing control, etc.). The input / output unit 80 is electrically connected to the CPU 72 via the bus 82. The client 71 includes an operation unit 76 for inputting an external instruction, a microphone 77 for inputting sound, a speaker 78 for outputting sound, and a display unit capable of displaying a desired image. 79, which are electrically connected to the input / output unit 80, respectively. Thereby, it is possible for the CPU 72 to recognize an input signal from each interface. Each interface can be controlled by the CPU 72.

  The client 71 includes a communication I / F 81 for connecting to the Internet network 3 and performing communication via the Internet network 3. Then, various data output from the CPU 72 can be transmitted to the terminal device 31 and the server 51 via the Internet network 3, and various data received via the Internet network 3 are stored in the CPU 72. The CPU 72 and the Ethernet (registered trademark) I / F 81 are electrically connected.

  Details of the storage area of the storage device 40 included in the terminal device 31 will be described with reference to FIGS. FIG. 7 shows various storage areas provided in the storage device 40. FIG. 8 shows a received data table stored in the incoming data table storage area 401. FIG. 9 shows a notification destination table stored in the notification destination table storage area 402.

  The details of the storage area of the storage device 40 will be described with reference to FIG. As shown in FIG. 7, the storage device 40 stores an incoming data table storage area 401 for storing information related to incoming data of FAX documents and answering machine voices received from the receiving device 11, the address of the client 71, and the like. Notification destination table storage area 402, a program storage area 403 for storing programs used by the CPU 32 of the terminal device 31, an incoming data storage area 404 for storing incoming data, and other storage areas. Yes.

  Details of the incoming data table stored in the incoming data table storage area 401 will be described with reference to FIG. In the incoming data table, information related to incoming data of FAX manuscripts and voice mails received by the terminal device 31 from the receiving device 11 is stored. As shown in FIG. 8, the incoming data table stores information corresponding to the information items of incoming date and time, transmission source number, classification, and data name. As the incoming date and time, the incoming date and time when a FAX document or answering machine voice is received by the receiving device 11 is stored. As the transmission source number, the telephone number of the transmission source of the FAX document or answering machine voice is stored. As the ward section, a classification of whether incoming data is FAX data or answering machine voice data is stored. As the data name, the file name added to the incoming data is stored. These pieces of information can be obtained by receiving from the receiving apparatus 11 together with a FAX document or an answering machine voice.

  In the example illustrated in FIG. 8, for example, the receiving apparatus 11 is set to “August 27, 2008 10:20:30”, the transmission source telephone number is “052-xxx-yyyy”, and the classification is “answer machine voice”. Data "and the incoming data whose file name is" xxx.mp3 "is stored.

  Details of the notification destination table stored in the notification destination table storage area 402 will be described with reference to FIG. The notification destination table stores contact information of the client 71 and is referred to when the terminal device 31 transmits incoming data to the client 71.

  As shown in FIG. 9, in the notification destination table, information corresponding to each information item of the notification destination address and the terminal classification is stored for each predetermined group (extension group or the like). As the notification destination address, the address of the client 71 is stored. As the terminal classification, a classification of whether the client 71 is a PC or a mobile phone is stored. In the terminal device 31, when an incoming notification (details will be described later) and incoming data are transmitted to the client 71, the notification destination address stored in the notification destination table is referred to. Then, the incoming data is transmitted to the client 71 of the stored notification destination address.

  In the example illustrated in FIG. 9, for example, information of the client 71 whose notification destination address is “userA@brother.co.jp” and whose terminal classification is “PC” is stored.

  With reference to the flowchart shown in FIG. 10, a reception device process executed by the reception device 11 will be described. FIG. 10 is a flowchart of the receiving device process. In the reception device process, when the reception device 11 receives a FAX document or answering machine voice via the PSTN network 2, a process of transmitting the FAX document or answering machine voice to the terminal device 31 is executed. The receiving device process is activated and executed by the CPU 12 when the receiving device 11 detects a FAX document or an answering machine voice.

  As shown in FIG. 10, when a fax document or answering machine voice is detected and processing is started, the detected fax document or answering machine voice is first received (S11). Next, a reception notification for notifying the terminal device 31 that the FAX document or the answering machine voice has been received is transmitted to the terminal device 31 (S13).

  On the other hand, when the above-described reception notification is received by the terminal device 31, a transmission request notification which is a notification for requesting reception of a FAX document or an answering machine voice is returned to the receiving device 11 (S23). , See FIG. The receiving device 11 receives the transmission request notification returned from the terminal device 31 (S15).

  The receiving apparatus 11 that has received the transmission request notification determines that the terminal apparatus 31 has requested acquisition of a FAX document or an answering machine voice. Therefore, the FAX document or answering machine voice received in S11 is transmitted to the terminal device 31 (S17). At the same time, the date and time when the FAX manuscript or answering machine voice was received, the source number of the FAX manuscript or answering machine voice, the destination number (own phone number), classification, and data name of the FAX manuscript or answering machine voice (Hereinafter referred to as “incoming data related information”) is transmitted to the terminal device 31. Then, the receiving device process ends. Through the above processing, the FAX document or answering machine voice received by the receiving device 11 is transmitted to the terminal device 31.

  Various processes executed by the terminal device 31 will be described with reference to the flowcharts shown in FIGS. 11 and 12. FIG. 11 is a flowchart of the upload process. FIG. 12 is a flowchart of incoming data transmission processing. The upload process is started and executed by the CPU 32 when a reception notification transmitted from the receiving device 11 is detected. The incoming data transmission process is activated and executed by the CPU 32 when an acquisition request notification transmitted from the client 71 is detected.

  The upload process will be described with reference to FIG. In the upload process, a FAX document or answering machine voice is received from the receiving apparatus 11 and converted into incoming data. Then, a process of uploading incoming data to the server 51 is executed. When the reception notification transmitted from the receiving device 11 is detected in S13 (see FIG. 10), the detected reception notification is first received as shown in FIG. 11 (S21). As a result, the terminal device 31 determines that the receiving device 11 has received a fax document or an answering machine voice.

  Next, in order to receive the notified FAX document or answering machine voice from the receiving apparatus 11, a transmission request notification for requesting transmission of the FAX document or answering machine voice is transmitted to the receiving apparatus 11 (S23). ).

  Here, when the above-described transmission request notification is received by the receiving apparatus 11, a process of returning a FAX document or an answering machine voice is executed in response thereto (S17, see FIG. 10). The terminal device 31 receives the FAX manuscript and the answering machine voice transmitted from the receiving device 11 (S25). The received FAX document or answering machine voice is converted into incoming data. In addition, incoming data related information is received. The converted incoming data and the received incoming data related information are temporarily stored in the RAM 14.

  After receiving a FAX document or answering machine voice from the receiving apparatus 11 and converting it to incoming data, processing for uploading the incoming data to the server 51 is executed (S27 to S39). First, incoming data is transmitted to the server 51 via the Internet 3 (S27). Next, the received incoming data reaches the server 51 and is stored in the HDD 55 of the server 51, and it is determined whether or not the upload is successful (S29). If it is determined that the upload to the server 51 is successful (S29: YES), the upload process ends without performing any special process. On the other hand, when it is determined that the upload to the server 51 has failed (S29: NO), the incoming data stored in the RAM 14 is stored in the incoming data storage area 404 of the storage device 40. The incoming data related information is stored in the incoming data table storage area 401 of the storage device 40 (S31).

  As a method for determining whether or not the upload is successful, for example, a method using an ACK signal / NACK signal can be used. Specifically, when the incoming data is normally stored in the server 51, an ACK signal is returned to the terminal device 31. On the other hand, when the incoming data is not normally stored, a NACK signal is returned. When the terminal device 31 receives an ACK signal from the server 51, it determines that the incoming data has been successfully uploaded. When a NACK signal is received or when neither an ACK / NACK signal is received, it is determined that the incoming data upload has failed.

  If it is determined that the upload has failed, an incoming notification for notifying that the incoming data has been stored is transmitted to the client 71 via the Internet 3 (S35). This incoming notification is added with at least location information, which is information for specifying the storage location where the incoming data is stored (the incoming data storage area 404 in the storage device 40 of the terminal device 31). As a result, the client 71 can recognize that the incoming data is stored in the incoming data storage area 404 of the storage device 40 of the terminal device 31.

  When an incoming notification is transmitted, all notification destination addresses stored in the notification destination table storage area 402 are addressed. Specifically, as the incoming call notification, an email describing the content of notification that the incoming data has been received may be transmitted to the client 71. In addition, an instant message may be transmitted in which contents for notifying that the incoming data has been received are described.

  Next, a health check process for monitoring whether or not the server 51 has returned to the uploadable state is executed (S37). If it is determined by the health check that the server 51 has returned to the uploadable state (S39: YES), the process returns to S27, and processing for uploading incoming data to the server 51 is executed. On the other hand, if the server 51 does not return to the uploadable state (S39: NO), the process returns to S37 and the health check is continuously executed.

  Here, as a health check method, for example, a method using a PING command can be used. Specifically, when a PING command is transmitted to the IP address of the server 51 and REPLY is returned in response to this, it is determined that the server 51 has returned to a state where uploading is possible. In addition, for example, an inquiry notification for inquiring whether or not uploading is possible is sent to the server 51. When a response to this is detected, a method of determining that the server 51 has returned to a state where uploading is possible can be used.

  As described above, when receiving a FAX document or answering machine voice from the receiving device 11, the terminal device 31 transmits incoming data of the FAX document or answering machine voice to the server 51. In the server 51, since the incoming data is stored in the HDD 55, it is possible to safely hold the incoming data even if a failure or the like occurs in the receiving device 11.

  If the terminal device 31 determines that the server 51 cannot receive incoming data, the terminal device 31 stores the incoming data in the incoming data storage area 404 of its own storage device 40. Thus, even when incoming data cannot be uploaded to the server 51, incoming data can be safely held. Further, the terminal device 31 sends an incoming call notification with at least location information added to the client 71. As a result, the client 71 can specify the storage location where the incoming data is stored.

  Furthermore, the terminal device 31 specifies the client 71 and transmits an incoming call notification. As a result, it is possible to notify the client 71 that wishes to obtain incoming data that the incoming data has been stored.

  The incoming data transmission process will be described with reference to FIG. The incoming data transmission process is a process that is started when an acquisition request notification transmitted from the client 71 in response to the incoming notification transmitted in S35 (see FIG. 11) is detected. In the incoming data transmission process, incoming data stored in the incoming data storage area 404 is transmitted to the client 71 in response to an incoming data acquisition request from the client 71.

  Note that setting information (hereinafter referred to as “encryption setting information”) as to whether to encrypt / decrypt communication data during communication with the client 71 is set in the terminal device 31 in advance. When the terminal device 31 is set to perform encryption in the encryption setting information, the incoming data is encrypted and transmitted to the client 71. Further, since the acquisition request notification received from the client 71 is encrypted, it can be recognized by decrypting it.

  Here, the specific method of encryption / decryption is not particularly limited, and a conventionally known encryption method can be used. For example, when communication is performed between the terminal device 31 and the client 71 using VPN (Virtual Private Network), it is possible to encrypt / decrypt communication data using the VPN function. It is.

  As shown in FIG. 12, when the acquisition request notification is detected, first, the encryption setting information is referred to and it is determined whether or not the acquisition request notification is to be decrypted (S53). When the setting for performing the decryption is made (S53: YES), the detected acquisition request notification is decrypted (S55). Then, the decrypted acquisition request notification is received (S56). On the other hand, when the setting for performing the decryption is not made (S53: NO), the detected acquisition request notification is received as it is (S56).

  Next, it is determined whether or not incoming data to be transmitted to the client 71 is encrypted (S57). If the encryption setting information is set to perform encryption (S57: YES), the incoming data stored in the incoming data storage area 404 is encrypted (S59) and encrypted. The incoming data (“encrypted incoming data”) is sent to the client 71 that sent the acquisition request notification (S61). Then, the incoming data transmission process is terminated. On the other hand, if the encryption setting information is set not to perform encryption (S57: NO), the incoming data stored in the incoming data storage area 404 is acquired without being encrypted. The request notification is transmitted to the client 71 (S61). Then, the incoming data transmission process is terminated.

  As described above, when receiving an acquisition request notification from the client 71, the terminal device 31 returns incoming data stored in the incoming data storage area 404 to the client 71. As a result, the incoming data can be referred to by the client 71. Further, since communication data during communication with the client 71 can be encrypted, the confidentiality of the communication data can be improved.

  Each process executed by the server 51 will be described with reference to FIGS. 13 and 14. FIG. 13 is a flowchart of incoming data storage processing. FIG. 14 is a flowchart of incoming data transmission processing. The incoming data storage process is activated and executed by the CPU 52 when incoming data transmitted from the terminal device 31 is detected. The incoming data transmission process is activated and executed by the CPU 52 when an acquisition request notification transmitted from the client 71 is detected.

  The incoming data storage process will be described with reference to the flowchart of FIG. In the incoming data storage process, a process for storing the received incoming data is executed. As shown in FIG. 13, in the incoming data storage process, first, the detected incoming data is received (S71). Next, the received incoming data is stored in the HDD 55 (S73). Next, an incoming call notification is transmitted to the client 71 (S75). At least location information for specifying the HDD 55 of the server 51 is added to the incoming notification. As a result, the client 71 that has received the incoming call notification can recognize that the incoming data is stored in the HDD 55 of the server 51.

  As a method for specifying the client 71 to which the server 51 transmits incoming data, for example, the notification destination table stored in the notification destination table storage area 402 in the storage device 40 of the terminal device 31 is referred to. Then, all of the stored notification destination addresses may be determined as the address of the client 71. Further, for example, the HDD 55 may store the same table as the notification destination table stored in the notification destination table storage area 402 of the terminal device 31. In this case, the address of the client 71 is determined by referring to the table stored in the HDD 55.

  The incoming data transmission process will be described with reference to FIG. In the incoming data transmission process, when an acquisition request notification is received from the client 71, a process of transmitting incoming data to the client 71 is executed. As shown in FIG. 14, when the acquisition request notification transmitted from the client 71 is detected, first, the detected acquisition request notification is received (S81). Next, the incoming data stored in the HDD 55 is transmitted to the client 71 that has transmitted the acquisition request notification (S83). Then, the incoming data transmission process ends.

  As described above, when receiving incoming data from the terminal device 31, the server 51 stores the received incoming data in the HDD 55. As a result, even if a failure or the like occurs in the receiving apparatus 11 that receives a FAX document or an answering machine voice, it is possible to safely hold incoming data. In addition, since the incoming notification is transmitted to the client 71 after receiving the incoming data and stored in the HDD 55, the client 71 can specify the location where the incoming data is stored. Further, in response to the acquisition request notification transmitted from the client 71, the server 51 transmits incoming data stored in the HDD 55 to the client 71. Thus, the client 71 can acquire incoming data.

  Each process executed by the client 71 will be described with reference to FIG. FIG. 15 is a flowchart of client processing. The client process is activated and executed by the CPU 72 when an incoming notification transmitted from the terminal device 31 or the server 51 is detected. In the client process, when an incoming notification is received from the terminal device 31 or the server 51, a process for receiving incoming data is executed.

  Note that setting information (hereinafter referred to as “encryption setting information”) indicating whether or not communication data during communication with the terminal device 31 is encrypted is set in the client 71 in advance. When the client 71 is set to perform encryption in the encryption setting information, the acquisition request notification transmitted to the terminal device 31 is encrypted and transmitted. Also, since the incoming data received from the terminal device 31 is encrypted, it can be recognized by decrypting it. Note that the communication data during communication with the server 51 is not encrypted.

  As described above, when incoming data is stored in the terminal device 31 or the server 51, an incoming notification is transmitted to the client 71 (S35 (see FIG. 11), S75 (see FIG. 13)). When this incoming notification is detected by the client 71, the incoming notification detected first is received (S91). Next, the location information added to the incoming call notification is referred to in order to specify the transmission destination for transmitting the acquisition request notification for acquiring the incoming data (S93).

  When the storage location of the incoming data specified by the location information is the HDD 55 of the server 51 (S93: YES), it is not necessary to encrypt the communication data between the server 51 and the client 71. Therefore, an acquisition request notification is transmitted to the identified server 51 without performing encryption (S109). In response to this acquisition request notification, the server 51 returns incoming data (S83, see FIG. 14), so the client 71 receives the incoming data (S111). The received incoming data is stored in the storage device 75 (S113), and the client process is terminated.

  On the other hand, when the storage location of the incoming data specified by the location information is the storage device 40 of the terminal device 31 (S93: NO), first, the encryption setting information is referred to and acquired to be transmitted to the terminal device 31. It is determined whether to encrypt the request notification (S97). If encryption is set (S97: YES), the acquisition request notification is encrypted (S99), and the encrypted acquisition request notification is sent to the terminal device 31 that has transmitted the incoming notification. It is transmitted (S101). On the other hand, when the setting to perform encryption is not made (S97: NO), the acquisition request notification is not encrypted and is transmitted to the terminal device 31 as it is (S101).

  Here, the server 51 or the terminal device 31 that has received the acquisition request notification returns incoming data. When this incoming data is detected, the client 71 refers to the encryption setting information and determines whether or not to decrypt the incoming data (S105). If the setting for performing the decryption is made (S105: YES), the detected incoming data is decrypted (S107). The decoded incoming data is received (S108). On the other hand, when the setting not to perform decryption is not made (S105: NO), the detected incoming data is received as it is (S108). The received incoming data is stored in the storage device 75 (S113), and the client process ends.

  As described above, in the client process, when the client 71 receives an incoming notification, the client 71 can acquire incoming data by transmitting an acquisition request notification to the terminal device 31 or the server 51. Moreover, since it becomes possible to encrypt the communication data at the time of communication with the terminal device 31, it becomes possible to improve the confidentiality of communication data.

  The terminal device 31 in FIG. 1 corresponds to the “network device” of the present invention, the CPU 12 that performs the process of S25 of FIG. 11 corresponds to the “first device receiving means” of the present invention, and the CPU 12 that performs the process of S27. Corresponds to the “first device transmission means” of the present invention. The CPU 52 that performs the process of S71 in FIG. 13 corresponds to the “first server receiving means” of the present invention. The HDD 55 in FIG. 5 corresponds to the “server storage unit” of the present invention. The CPU 52 that performs the process of S75 in FIG. 13 corresponds to the “first server transmission unit” of the present invention. The CPU 52 that performs the process of S81 in FIG. 14 corresponds to the “second server reception unit” of the present invention, and the CPU 52 that performs the process of S83 corresponds to the “second server transmission unit” of the present invention. The CPU 72 that performs the process of S91 in FIG. 15 corresponds to the “first client reception unit” of the present invention, and the CPU 72 that performs the processes of S109 and S101 corresponds to the “first client transmission unit” of the present invention. The CPU 72 that performs the processing corresponds to the “second client receiving means” of the present invention.

  The CPU 12 that performs the process of S29 in FIG. 11 corresponds to the “reception availability determination unit” of the present invention. The incoming data storage area 404 in FIG. 7 corresponds to the “device storage unit” of the present invention, and the CPU 12 that performs the process of S35 in FIG. 11 corresponds to the “second device transmission unit” of the present invention. The CPU 12 that performs the process of S56 in FIG. 12 corresponds to the “second device reception unit” of the present invention, and the CPU 12 that performs the process of S61 corresponds to the “third device transmission unit” of the present invention. The CPU 12 that performs the process of S37 in FIG. 11 corresponds to the “device monitoring unit” of the present invention. The CPU 12 that performs the process of S59 in FIG. 12 corresponds to the “device encryption unit” of the present invention. The CPU 72 that performs the process of S107 in FIG. 15 corresponds to the “client decryption unit” of the present invention.

  In addition, this invention is not limited to the content of the above-mentioned embodiment, A various change is possible. In the above-described embodiment, only the location information is added to the incoming notification, but the present invention is not limited to this configuration. For example, information related to incoming data in an incoming call notification (the date and time when a fax document or answering machine voice was received, the transmission source number of the fax document or answering machine voice, the destination number of the fax document or answering machine voice (the telephone number of the receiving device 11) , Division, and data name) may be added. As a result, when the incoming call notification is received, the client 71 can recognize the incoming data related information together with the information on the location where the incoming data is stored.

  In the above-described embodiment, the communication data between the server 51 and the client 71 is not encrypted / decrypted, but the present invention is not limited to this configuration. Accordingly, the communication data between the server 51 and the client 71 may be encrypted / decrypted in the same manner as the communication data between the terminal device 31 and the client 71.

  In the above-described embodiment, in the terminal device 31, the FAX manuscript and the answering machine voice received from the receiving device 11 are converted into incoming data having a data format that can be referred to by the client 71. However, the present invention is not limited to this configuration. For example, the receiving apparatus 11, the server 51, and the client 71 may be configured to convert a FAX document or an answering machine voice into incoming data.

  In the above-described embodiment, the receiving apparatus 11 receives a FAX document or answering machine voice, and the terminal apparatus 31 receives the FAX document or answering machine voice from the receiving apparatus 11. However, the present invention is not limited to the above-described configuration. Hereinafter, modifications of the present invention will be described.

  A modification of the present invention will be described with reference to FIGS. FIG. 16 shows a system configuration of the incoming data notification system 1 in the modification. FIG. 17 is a flowchart of the upload process executed by the terminal device 31 according to the modification. Since the configuration excluding the terminal device 31 is the same as that of the above-described embodiment, the description thereof is omitted.

  With reference to FIG. 16, the system configuration of the incoming data notification system 1 according to the modification will be described. As illustrated in FIG. 16, the incoming data notification system 1 includes a terminal device 31, a server 51, and a client 71.

  The terminal device 31 is connected to the Internet network 3 and the PSTN network 2. The terminal device 31 can perform relay processing of data flowing through the network, and can receive a fax document and an answering machine voice transmitted to the terminal device 31 via the PSTN network 2. Other functions are the same as those in the above-described embodiment, and thus description thereof is omitted.

  The upload process executed by the CPU of the terminal device 31 will be described with reference to the flowchart of FIG. The upload process is started and executed by the CPU of the terminal device 31 when the terminal device 31 detects a FAX document or an answering machine voice.

  As shown in FIG. 17, in the upload process, first, the detected FAX document or answering machine voice is received (S125). The received FAX document or answering machine voice is converted into incoming data. In addition, the incoming data related information is acquired. Next, processing for uploading incoming data to the server 51 is executed (S127 to S139). First, incoming data is transmitted to the server 51 via the Internet 3 (S127). Next, the received incoming data reaches the server 51 and is stored in the HDD 55 of the server 51, and it is determined whether or not the upload is successful (S129). If it is determined that the upload to the server 51 is successful (S129: YES), the upload process terminates the process without performing any special process. On the other hand, when it is determined that the upload to the server 51 has failed (S129: NO), the incoming data is stored in the incoming data storage area 404 of the storage device 40. The incoming data related information is stored in the incoming data table storage area 401 of the storage device 40 (S131).

  Next, an incoming call notification is transmitted to the client 71 via the Internet network 3 (S135). Next, a health check process for monitoring whether or not the server 51 has returned to the uploadable state is executed (S137). If it is determined by the health check that the server 51 has returned to the uploadable state (S139: YES), the process returns to S127, and processing for uploading incoming data to the server 51 is executed. On the other hand, if the server 51 does not return to the uploadable state (S139: NO), the process returns to S37 and the health check is continuously executed.

  As described above, in the modification of the present invention, since the terminal device 31 can receive a FAX document or an answering machine voice, it is not necessary to provide a separate receiving device in the system. As a result, the system configuration can be simplified, and the cost required for the receiving apparatus can be reduced.

1 is a schematic diagram showing a system configuration of an incoming data notification system 1. FIG. 1 is a schematic diagram showing a system configuration of an incoming data notification system 1. FIG. 3 is a schematic diagram showing an electrical configuration of a terminal device 31. FIG. 3 is a schematic diagram showing an electrical configuration of a receiving device 11. FIG. 3 is a schematic diagram showing an electrical configuration of a server 51. FIG. 3 is a schematic diagram showing an electrical configuration of a client 71. FIG. Various storage areas provided in the storage device 40 are shown. The received data table stored in the incoming data table storage area 401 is shown. The notification destination table stored in the notification destination table storage area 402 is shown. It is a flowchart of a receiving device process. It is a flowchart of an upload process. It is a flowchart of an incoming data transmission process. It is a flowchart of an incoming data storage process. It is a flowchart of an incoming data transmission process. It is a flowchart of a client process. It is a schematic diagram which shows the system configuration | structure of the incoming data notification system 1 in a modification. It is a flowchart of the upload process in a modification.

1 Incoming Data Notification System 4 Incoming Data 11 Receiving Device 12 CPU
15 Printing unit 31 Terminal device 32 CPU
40 storage device 51 server 52 CPU
71 Client 75 Storage device 76 Operation unit 77 Microphone 78 Speaker 79 Display unit 80 Input / output unit 82 Bus 404 Incoming data storage area

Claims (14)

A receiving device that receives and transfers incoming data, which is fax or answering machine voice data transmitted from a transmitting terminal, a network device that receives the incoming data transferred from the receiving device, and a network device that receives the incoming data. A server for receiving and receiving the incoming data, and an incoming data notification system for notifying the client that the incoming data has been received from at least one of the network device and the server,
The receiving device is:
Device receiving means for receiving the incoming data;
Device transmitting means for transmitting the incoming data received by the device receiving means,
The network device is:
First device receiving means for receiving the incoming data transmitted by the device transmitting means;
A first device transmitting means for transmitting the incoming data received by the first device receiving means to the server;
The server
First server receiving means for receiving the incoming data transmitted from the network device;
Server storage means for storing the incoming data received by the first server reception means;
A first incoming notification for notifying that the incoming data has been stored, the incoming notification including at least location information as information for specifying a storage location of the incoming data to the client Server transmission means;
A second server that receives an acquisition request notification that is a notification transmitted from the client in response to the incoming notification transmitted by the first server transmission means, and is a notification for requesting acquisition of the incoming data. Receiving means;
A second server transmission unit configured to transmit the incoming data stored in the server storage unit to the client when the acquisition request notification is received by the second server reception unit;
The client
First client receiving means for receiving the incoming notification transmitted by the first server transmitting means;
First client transmission for transmitting the acquisition request notification for receiving the incoming data from the storage location specified by the location information included in the incoming notification received by the first client receiving means Means,
A second client receiving means for receiving the incoming data after the acquisition request notification is transmitted by the first client transmitting means ;
The network device further includes:
Reception for determining whether or not the server can receive the incoming data when the incoming data is received by the first device receiving unit and the incoming data is transmitted to the server by the first device transmitting unit. Availability determination means;
Device storage means for storing the incoming data when the reception possibility determination means determines that the server has not received the incoming data;
Second device transmission means for transmitting to the client the incoming notification including at least location information for specifying the storage location of the incoming data after the incoming data is stored in the device storage means;
Second device receiving means for receiving the acquisition request notification from the client in response to the incoming call notification transmitted by the second device transmitting means;
Third device transmission means for transmitting the incoming data stored in the device storage means to the client when the acquisition request notification is received by the second device reception means;
Incoming data notification system comprising the. The incoming notification includes at least one of destination identification information that is information for specifying a transmission destination of the incoming data and incoming date and time specification information that is information for specifying the date and time when the incoming data was received. The incoming data notification system according to claim 1, wherein any one of them is included. The network device is:
Device monitoring means for monitoring whether or not the server can receive the incoming data when the server determines that the server has not received the incoming data. ,
The first device transmission means includes
Incoming described in the equipment monitoring device, when the reception of the incoming data is determined to become ready to claim 1 or 2, characterized in that transmitting the incoming data to the server Data notification system. The network device is:
Device encryption means for encrypting the incoming data stored in the device storage means,
The third device transmission means includes
Sending encrypted incoming data that is the incoming data encrypted by the device encryption means,
The client
When receiving the encrypted incoming data at the second client reception unit, according to any one of claims 1 to 3, further comprising a client decoding means for decoding the encrypted incoming data Incoming data notification system. The network device functions as a VPN (Virtual Private Network) router for relaying VoIP (Voice over IP) data,
The device encryption means is
5. The incoming data notification system according to claim 4 , wherein the incoming data is encrypted by a VPN function. A network device that receives incoming data, which is fax or answering machine voice data transmitted from a transmission terminal, and a server that receives and backs up the incoming data transmitted from the network device; An incoming data notification system that notifies the client that the incoming data has been received from at least one of the servers,
The network device is:
First device receiving means for receiving the incoming data;
A first device transmitting means for transmitting the incoming data received by the first device receiving means to the server;
The server
First server receiving means for receiving the incoming data transmitted from the network device;
Server storage means for storing the incoming data received by the first server reception means;
A first incoming notification for notifying that the incoming data has been stored, the incoming notification including at least location information as information for specifying a storage location of the incoming data to the client Server transmission means;
A second server that receives an acquisition request notification that is a notification transmitted from the client in response to the incoming notification transmitted by the first server transmission means, and is a notification for requesting acquisition of the incoming data. Receiving means;
A second server transmission unit configured to transmit the incoming data stored in the server storage unit to the client when the acquisition request notification is received by the second server reception unit;
The client
First client receiving means for receiving the incoming notification transmitted by the first server transmitting means;
First client transmission for transmitting the acquisition request notification for receiving the incoming data from the storage location specified by the location information included in the incoming notification received by the first client receiving means Means,
A second client receiving means for receiving the incoming data after the acquisition request notification is transmitted by the first client transmitting means ;
The network device further includes:
Reception for determining whether or not the server can receive the incoming data when the incoming data is received by the first device receiving unit and the incoming data is transmitted to the server by the first device transmitting unit. Availability determination means;
Device storage means for storing the incoming data when the reception possibility determination means determines that the server has not received the incoming data;
Second device transmission means for transmitting to the client the incoming notification including at least location information for specifying the storage location of the incoming data after the incoming data is stored in the device storage means;
Second device receiving means for receiving the acquisition request notification from the client in response to the incoming call notification transmitted by the second device transmitting means;
Third device transmission means for transmitting the incoming data stored in the device storage means to the client when the acquisition request notification is received by the second device reception means;
Incoming data notification system comprising the. Receives the incoming data from a receiving device that receives and transfers incoming data, which is fax or answering machine voice data transmitted from the transmitting terminal, backs up the incoming data to a server, and receives the incoming data to the client. A network device for notifying
First device receiving means for receiving the incoming data;
First device transmission means for transmitting the incoming data received by the first device reception means to the server; and reception availability determination means for determining whether the server can receive the incoming data;
Device storage means for storing the incoming data when the reception possibility determination means determines that the server has not received the incoming data;
After the incoming data is stored in the device storage means, an incoming notification for notifying that the incoming data has been stored, and location information that is information for specifying a storage location of the incoming data Second device transmission means for transmitting an incoming notification including at least to the client;
A second device that receives an acquisition request notification that is a notification transmitted from the client in response to the incoming notification transmitted by the second device transmission means and is a request for requesting acquisition of the incoming data. Receiving means;
A network device comprising: a third device transmission unit configured to transmit the incoming data stored in the device storage unit to the client when the acquisition request notification is received by the second device reception unit; . The incoming notification includes at least one of destination identification information that is information for specifying the destination of the incoming data and incoming date and time information that is information for specifying the date and time when the incoming data was received. The network device according to claim 7 , further comprising: Device monitoring means for monitoring whether or not the server can receive the incoming data when the server determines that the server has not received the incoming data. ,
The first device transmission means includes
9. The network according to claim 7 or 8 , wherein when the device monitoring unit determines that the incoming data can be received, the incoming data is transmitted to the server. machine. Device encryption means for encrypting the incoming data stored in the device storage means,
The third device transmission means includes
Network device according to any of claims 7 to 9, characterized in that transmitting the encrypted incoming data is the incoming data encrypted by the device encryption means. The network device functions as a VPN (Virtual Private Network) router for relaying VoIP (Voice over IP) data,
The device encryption means is
Network equipment according to claim 1 0, characterized by encrypting the incoming data by VPN functionality. A network device that receives incoming data that is FAX or voice mail data transmitted from a transmitting terminal, backs up the incoming data to a server, and notifies a client that the incoming data has been received;
First device receiving means for receiving the incoming data;
First device transmission means for transmitting the incoming data received by the first device reception means to the server; and reception availability determination means for determining whether the server can receive the incoming data;
Device storage means for storing the incoming data when the reception possibility determination means determines that the server has not received the incoming data;
After the incoming data is stored in the device storage means, an incoming notification for notifying that the incoming data has been stored, and location information that is information for specifying a storage location of the incoming data Second device transmission means for transmitting an incoming notification including at least to the client;
A second device that receives an acquisition request notification that is a notification transmitted from the client in response to the incoming notification transmitted by the second device transmission means and is a request for requesting acquisition of the incoming data. Receiving means;
A network device comprising: a third device transmission unit configured to transmit the incoming data stored in the device storage unit to the client when the acquisition request notification is received by the second device reception unit; . A receiving device that receives and transfers incoming data, which is FAX or voice mail data transmitted from a transmitting terminal, a network device that receives the incoming data transferred from the receiving device, and the network device that is transmitted from the network device An incoming data notification method that is executed in a server that receives and backs up incoming data, and that at least one of the network device and the server notifies the client that the incoming data has been received,
A device receiving step in which the receiving device receives the incoming data; and
A device transmitting step in which the receiving device transmits the incoming data received in the device receiving step ;
A first device receiving step in which the network device receives the incoming data transmitted in the device transmitting step;
A first device transmitting step in which the network device transmits the incoming data received in the first device receiving step to the server;
A first server receiving step in which the server receives the incoming data transmitted from the network device;
The server, the said incoming data received by the first server receiving step is stored in the servers storage means, a call notification for the previous SL incoming data to notify that it has been stored, the incoming A first server transmission step of transmitting an incoming notification including at least location information, which is information for specifying a data storage location, to the client;
The server receives an acquisition request notification which is a notification transmitted from the client in response to the incoming notification transmitted in the first server transmission step and is a notification for requesting acquisition of the incoming data. A second server receiving step,
A second server transmission step of transmitting the incoming data stored in the server storage means to the client when the server receives the acquisition request notification in the second server reception step;
A first client receiving step in which the client receives the incoming notification transmitted in the first server transmitting step;
The client transmits the acquisition request notification to receive the incoming data from the storage location specified by the location information included in the incoming notification received in the first client reception step. A first client sending step;
A second client receiving step in which the client receives the incoming data after the acquisition request notification is transmitted in the first client transmitting step ;
When the network device receives the incoming data in the first device reception step and the incoming data is transmitted to the server in the first device transmission step, the server receives the incoming data in the server. A reception propriety judging step for judging propriety; and
When the network device determines that the server does not receive the incoming data in the reception availability determination step, the network device stores the incoming data in device storage means, and stores the incoming data in the device storage means. A second device transmitting step of transmitting to the client the incoming notification including at least location information specifying a storage location of the incoming data
A second device receiving step in which the network device receives the acquisition request notification from the client in response to the incoming notification transmitted in the second device transmitting step;
A third device transmission step of transmitting the incoming data stored in the device storage means to the client when the network device receives the acquisition request notification in the second device reception step; An incoming data notification method characterized by comprising: Executed in a network device that receives incoming data that is fax or answering machine voice data transmitted from a transmission terminal, and a server that receives and backs up the incoming data transmitted from the network device, and the network device and An incoming data notification method in which at least one of the servers notifies the client that the incoming data has been received,
A first device receiving step in which the network device receives the incoming data;
A first device transmitting step in which the network device transmits the incoming data received in the first device receiving step to the server;
A first server receiving step in which the server receives the incoming data transmitted from the network device;
The server, the said incoming data received by the first server receiving step is stored in the servers storage means, a call notification for the previous SL incoming data to notify that it has been stored, the incoming A first server transmission step of transmitting an incoming notification including at least location information, which is information for specifying a data storage location, to the client;
The server receives an acquisition request notification which is a notification transmitted from the client in response to the incoming notification transmitted in the first server transmission step and is a notification for requesting acquisition of the incoming data. A second server receiving step,
A second server transmission step of transmitting the incoming data stored in the server storage means to the client when the server receives the acquisition request notification in the second server reception step; A first client receiving step in which the client receives the incoming notification transmitted in the first server transmitting step;
The client transmits the acquisition request notification to receive the incoming data from the storage location specified by the location information included in the incoming notification received in the first client reception step. A first client sending step;
A second client receiving step in which the client receives the incoming data after the acquisition request notification is transmitted in the first client transmitting step ;
When the network device receives the incoming data in the first device reception step and the incoming data is transmitted to the server in the first device transmission step, the server receives the incoming data in the server. A reception propriety judging step for judging propriety; and
When the network device determines that the server does not receive the incoming data in the reception availability determination step, the network device stores the incoming data in device storage means, and stores the incoming data in the device storage means. A second device transmitting step of transmitting to the client the incoming notification including at least location information specifying a storage location of the incoming data
A second device receiving step in which the network device receives the acquisition request notification from the client in response to the incoming notification transmitted in the second device transmitting step;
A third device transmission step of transmitting the incoming data stored in the device storage means to the client when the network device receives the acquisition request notification in the second device reception step; An incoming data notification method characterized by comprising:

Images