JP7764705B2 - Fax sending/receiving server, fax sending/receiving system, and fax sending/receiving method - Google Patents

Description

The present invention relates to a fax sending/receiving server, a fax sending/receiving system, and a fax sending/receiving method.

Conventionally, there have been known receiving devices that store fax data received from a sending device in memory without printing it, and then display the fax data on a display in response to a user's operation (see, for example, Patent Document 1).

The receiving device described in Patent Document 1 manages the viewing status of each of the multiple fax data stored in memory, indicating whether the user has viewed it. In other words, when the receiving device displays the fax data on its display, it updates the viewing status corresponding to that fax data from an "unread" status, indicating that the fax data has not been viewed, to a "read" status, indicating that the fax data has been viewed.

A sending device can send the same fax data to multiple receiving devices, a process known as "broadcast transmission." However, the receiving device described in Patent Document 1 has the problem of not being able to know whether the fax data has been viewed by other receiving devices.

The present invention was made to solve these problems, and aims to provide technology that allows a recipient device of broadcast fax data to check the viewing status on other recipient devices.

In order to solve the above problem, one aspect of the present invention includes a fax receiving unit that receives fax data, a plurality of destination IDs that uniquely identify destination devices that are to receive the fax data, and a data ID that uniquely identifies a combination of the fax data and the plurality of destination IDs from a source device; a storage processing unit that stores in a memory, in association with each other, the data ID, the fax data, the plurality of destination IDs, and a plurality of viewing states that indicate whether the fax data has been viewed at the destination devices identified by each of the plurality of destination IDs; a reception notifying unit that notifies the destination devices identified by each of the plurality of destination IDs received from the source device that the fax data has been received from the source device; a fax sending unit that, in response to receiving a transmission request including the destination IDs from the destination device, transmits the fax data to the destination devices identified by the destination IDs included in the transmission request; and a fax sending unit that stores the viewing states corresponding to the destination IDs included in the transmission request in the fax sending unit. The fax sending unit includes a status update unit that updates a status from an unread status, which indicates that fax data has not been viewed, to a read status, which indicates that the fax data has been viewed; and a viewing status transmission unit that, in response to receiving a first viewing status confirmation request including the data ID from one of a plurality of receiving devices identified by the plurality of receiving device IDs, transmits the plurality of viewing statuses associated with the data ID to the one receiving device that is the sender of the first viewing status confirmation request, wherein the memory stores the receiving device IDs in association with user IDs, and, in response to receiving a transmission request including the user ID from a user terminal, the fax sending unit transmits the fax data to the user terminal identified by the user ID included in the transmission request, and the status update unit reads out the receiving device ID associated with the user ID included in the transmission request from the memory, and updates the viewing status corresponding to the read receiving device ID from the unread status to the read status .

According to the present invention, a device receiving broadcast fax data can check the viewing status on other receiving devices.

1 is a schematic diagram of a fax sending and receiving system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating the hardware configuration of an MFP. Hardware configuration diagram of a smartphone. Hardware configuration diagram of a fax sending/receiving server. FIG. 2 is a functional block diagram of a fax sending/receiving server. Example of fax management table data. 10A and 10B show examples of data in a data management table and a user management table. 10 is a flowchart of an upload process. 10 is a flowchart of a download process executed between the MFP and the fax sending and receiving server. 10A shows examples of a data list screen, a data display screen, and a viewing status list screen, which are displayed on the panel display unit of an MFP. 10 is a flowchart of a download process executed between a smartphone and a fax sending/receiving server.

The fax sending and receiving system, fax sending and receiving server, and fax sending and receiving method according to this embodiment will be described below with reference to the drawings.

Figure 1 is a schematic diagram of a fax sending and receiving system 1 according to this embodiment. The fax sending and receiving system 1 includes multiple MFPs 10A, 10B, 10C, and 10D (hereinafter, these may be collectively referred to as "MFPs 10"), a smartphone 20, and a fax sending and receiving server 30. The MFPs 10A, 10B, 10C, and 10D, the smartphone 20, and the fax sending and receiving server 30 are configured to be able to send and receive data to and from each other via a communications network 100. The communications network 100 may be configured, for example, by a wired LAN, a wireless LAN, the Internet, a public telephone line, or a combination of these.

As shown in FIG. 2, the MFP (Multifunction Peripheral/Product/Printer) 10 is an image forming device equipped with a scanner unit 231, a printer unit 232, and a fax unit 233. The scanner unit 231 reads an image recorded on a document and generates image data. The printer unit 232 forms an image represented by the image data on a sheet. The fax unit 233 sends and receives fax data to and from other devices in accordance with a fax protocol. However, the fax sending and receiving system 1 may be configured, instead of the MFP 10, by a single-function fax machine equipped with the fax unit 233, or a PC with a fax program installed.

A fax number is set in the fax unit 233 of each of MFPs 10A, 10B, 10C, and 10D. In the example of FIG. 1, fax number [03-1111-2222] is set in MFP 10A, fax number [03-3333-4444] is set in MFP 10B, fax number [06-5555-6666] is set in MFP 10C, and fax number [045-777-8888] is set in MFP 10D. The fax numbers are examples of device IDs (sender ID and recipient ID, described below) that uniquely identify the MFP 10.

The smartphone 20 is a user terminal carried by the user of the MFP 10. Specific examples of the user terminal are not limited to the smartphone 20, and may include a PC, laptop, or mobile phone, but it is preferable that the smartphone 20 is a portable terminal that can be carried around. A user ID that uniquely identifies the user who owns the smartphone 20 is set in the smartphone 20.

The fax sending and receiving server 30 relays the sending and receiving of fax data between, for example, the source device, MFP 10A, and the destination devices, MFPs 10B, 10C, and 10D. The fax sending and receiving server 30 also manages the viewing status of fax data on each of MFPs 10B, 10C, and 10D. The fax number set on the source device is an example of a source ID, and the fax number set on the destination device is an example of a destination ID. However, the combination of source device and destination device is not limited to the above examples.

Figure 2 is a hardware configuration diagram of the MFP 10. As shown in Figure 2, the MFP 10 includes a controller 210, a short-range communication circuit 220, an engine control unit 230, an operation panel 240, and a network I/F 250.

Of these, the controller 210 includes the CPU 201, which is the main part of the computer, system memory (MEM-P) 202, north bridge (NB) 203, south bridge (SB) 204, ASIC (Application Specific Integrated Circuit) 206, local memory (MEM-C) 207, which is a storage unit, HDD controller 208, and HD 209, which is also a storage unit, with the NB 203 and ASIC 206 connected via an AGP (Accelerated Graphics Port) bus 221.

Of these, the CPU 201 is a control unit that performs overall control of the MFP 10. The NB 203 is a bridge that connects the CPU 201 with the MEM-P 202, SB 204, and AGP bus 221, and includes a memory controller that controls reading and writing to the MEM-P 202, a PCI (Peripheral Component Interconnect) master, and an AGP target.

MEM-P 202 consists of ROM 202a, which is memory for storing programs and data that realize the various functions of controller 210, and RAM 202b, which is used for expanding programs and data and as drawing memory during memory printing. The programs stored in RAM 202b may also be provided by being recorded in installable or executable files on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

SB204 is a bridge connecting NB203 with PCI devices and peripheral devices. ASIC206 is an integrated circuit (IC) for image processing applications that contains hardware elements for image processing and acts as a bridge connecting AGP bus 221, PCI bus 222, HDD controller 208, and MEM-C 207. This ASIC206 consists of a PCI target and AGP master, an arbiter (ARB) that forms the core of ASIC206, a memory controller that controls MEM-C 207, multiple DMACs (Direct Memory Access Controllers) that rotate image data using hardware logic, and a PCI unit that transfers data between the engine control unit 230 and the ASIC206 via PCI bus 222. A USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface may also be connected to the ASIC206.

MEM-C207 is local memory used as a copy image buffer and code buffer. HD209 is storage for storing image data, font data used during printing, and forms. HD209 controls the reading and writing of data from and to HD209 under the control of CPU201. AGP bus221 is a bus interface for a graphics accelerator card proposed to speed up graphics processing, and by directly accessing MEM-P202 at high throughput, the graphics accelerator card can be made faster.

The short-range communication circuit 220 is also equipped with an antenna 220a. The short-range communication circuit 220 is a communication circuit such as NFC or Bluetooth (registered trademark). Furthermore, a scanner unit 231, a printer unit 232, and a fax unit 233 are connected to the engine control unit 230. The controller 210 controls the operation of the scanner unit 231, the printer unit 232, and the fax unit 233 via the engine control unit 230.

The operation panel 240 includes a panel display unit 240a, such as a touch panel, which displays current settings and selection screens and accepts input from the operator, and an operation panel 240b, which includes a numeric keypad that accepts settings for image formation conditions such as density settings, and a start key that accepts a command to start copying.

The network I/F 250 is an interface for data communication using a communication network. The short-range communication circuit 220 and the network I/F 250 are electrically connected to the ASIC 206 via the PCI bus 222. The controller 210 can send information to and receive information from external devices via the network I/F 250.

Figure 3 is a hardware configuration diagram of the smartphone 20. As shown in Figure 3, the smartphone 20 includes a CPU 301, ROM 302, RAM 303, EEPROM 304, a CMOS sensor 305, an image sensor I/F 306, an acceleration/orientation sensor 307, a media I/F 309, and a GPS receiver 311.

Of these, the CPU 301 controls the overall operation of the smartphone 20. The ROM 302 stores the CPU 301 and programs used to drive the CPU 301, such as the IPL. The RAM 303 is used as a work area for the CPU 301. The EEPROM 304 reads and writes various data, such as smartphone programs, under the control of the CPU 301. The CMOS (Complementary Metal Oxide Semiconductor) sensor 305 is a type of built-in imaging device that captures an image of a subject (mainly a self-portrait) and obtains image data under the control of the CPU 301. Note that instead of a CMOS sensor, an imaging device such as a CCD (Charge Coupled Device) sensor may also be used. The imaging element I/F 306 is a circuit that controls the operation of the CMOS sensor 305. The acceleration/azimuth sensor 307 is a variety of sensors, such as an electronic magnetic compass or gyrocompass that detects geomagnetism, and an acceleration sensor. The media I/F 309 controls the reading and writing (storage) of data from and to a recording medium 308, such as a flash memory. The GPS receiver 311 receives GPS signals from GPS satellites.

The smartphone 20 also includes a long-distance communication circuit 312, a CMOS sensor 313, an image sensor I/F 314, a microphone 315, a speaker 316, an audio input/output I/F 317, a display 318, an external device connection I/F (Interface) 319, a short-distance communication circuit 320, an antenna 320a for the short-distance communication circuit 320, and a touch panel 321.

Of these, the long-distance communication circuit 312 is a circuit that communicates with other devices via the communication network 100. The CMOS sensor 313 is a type of built-in imaging means that captures an image of a subject and obtains image data under the control of the CPU 301. The image sensor I/F 314 is a circuit that controls the operation of the CMOS sensor 313. The microphone 315 is a built-in circuit that converts sound into an electrical signal. The speaker 316 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and voice. The sound input/output I/F 317 is a circuit that processes the input and output of sound signals between the microphone 315 and the speaker 316 under the control of the CPU 301. The display 318 is a type of display means, such as an LCD or organic EL (Electro Luminescence), that displays images of subjects, various icons, etc. The external device connection I/F 319 is an interface for connecting various external devices. The short-distance communication circuit 320 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The touch panel 321 is a type of input means that allows the user to operate the smartphone 20 by pressing the display 318.

The smartphone 20 also includes a bus line 310. The bus line 310 is an address bus, a data bus, etc., that electrically connects the various components, such as the CPU 301, shown in FIG. 3.

Figure 4 is a hardware configuration diagram of the fax sending and receiving server 30. As shown in Figure 4, the fax sending and receiving server 30 is constructed using a computer, and is equipped with a CPU 401, ROM 402, RAM 403, HDD 404, HDD (Hard Disk Drive) controller 405, display 406, external device connection I/F (Interface) 408, network I/F 409, data bus 410, keyboard 411, pointing device 412, DVD-RW (Digital Versatile Disk Rewritable) drive 414, and media I/F 416.

Of these, the CPU 401 controls the overall operation of the fax sending/receiving server 30. The ROM 402 stores programs used to drive the CPU 401, such as IPL. The RAM 403 is used as a work area for the CPU 401. The HDD 404 stores various data, such as programs. The HDD controller 405 controls the reading and writing of various data from the HDD 404 under the control of the CPU 401. The display 406 displays various information, such as a cursor, menus, windows, characters, or images. The external device connection I/F 408 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I/F 409 is an interface for data communication using the communication network 100. The data bus 410 is an address bus, data bus, etc., for electrically connecting the various components, such as the CPU 401, shown in FIG. 4.

The keyboard 411 is a type of input device equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 412 is a type of input device for selecting and executing various instructions, selecting a processing target, moving the cursor, etc. The DVD-RW drive 414 controls the reading and writing of various data from a DVD-RW 413, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R or the like. The media I/F 416 controls the reading and writing (storing) of data from a recording medium 415, such as a flash memory.

Figure 5 is a functional block diagram of the fax sending and receiving server 30. Figure 6 shows an example of data in the fax management table. Figure 7 shows an example of data in the data management table (A) and user management table (B).

The fax sending and receiving server 30 comprises a fax receiving unit 31, a storage processing unit 32, a reception notification unit 33, a fax sending unit 34, a status update unit 35, a viewing status sending unit 36, and a memory 37. The fax receiving unit 31, the storage processing unit 32, the reception notification unit 33, the fax sending unit 34, the status update unit 35, and the viewing status sending unit 36 are realized, for example, by the CPU 401 executing a fax sending and receiving program stored in the HDD 404. The memory 37 is realized by the ROM 402, RAM 403, HDD 404, or a combination of these.

The fax receiving unit 31 receives fax data, a sender ID, a transmission date and time, multiple recipient IDs, and a data ID from the MFP 10A via the network I/F 409. The fax data is data (e.g., document data, image data, etc.) to be sent to a recipient device. The sender ID is an identifier (fax number) that uniquely identifies the sender device. The transmission date and time is the date and time when the sender device sends the first fax data. The recipient ID is an identifier (fax number) that uniquely identifies the recipient device that is to receive the fax data. The data ID is an identifier that uniquely identifies the combination of fax data and multiple recipient IDs (i.e., broadcast transmission).

More specifically, the sending device repeatedly transmits the common fax data, sender ID, sending date and time, and data ID, along with one different recipient ID from multiple recipient IDs, to the fax sending and receiving server 30. In other words, the fax receiving unit 31 repeatedly receives the common fax data, sender ID, sending date and time, and data ID, along with one different recipient ID from multiple recipient IDs, from the sending device.

The data ID is, for example, an F code that conforms to the G3 standard protocol defined by the ITU-T. The F code is a combination of a sender ID that uniquely identifies the sending device and the date and time the fax data was sent. As mentioned above, if fax data is sent repeatedly by switching the recipient ID, the F code is set to the date and time the first fax data was sent.

The storage processing unit 32 associates the F code, fax data, sender ID, transmission date and time, multiple recipient IDs, and multiple viewing states received by the fax receiving unit 31 with each other and stores them in the memory 37. More specifically, the storage processing unit 32 associates the F code and fax data with each other and stores them in the data management table shown in FIG. 7(A). The storage processing unit 32 also associates the F code, sender ID, transmission date and time, multiple recipient IDs, and multiple viewing states with each other and stores them in the fax management table shown in FIG. 6.

The view status is associated one-to-one with the recipient ID. The view status indicates whether the fax data has been viewed by the recipient device identified by the corresponding recipient ID. The view status is set to "unread" or "read." The unread status indicates that the fax data has not yet been viewed by the recipient device identified by the corresponding recipient ID. The read status indicates that the fax data has already been viewed by the recipient device identified by the corresponding recipient ID. The view status added to the fax management table by the storage processing unit 32 is set to "unread."

The reception notification unit 33 notifies the receiving device identified by each of the multiple receiving device IDs received from the sending device that fax data has been received from the sending device. More specifically, the reception notification unit 33 sends a fax reception notification to the receiving device via the network I/F 409. The fax reception notification includes at least the F code received by the fax receiving unit 31.

In response to receiving a transmission request including an F-code and a destination ID from a destination device, the fax transmission unit 34 transmits fax data associated with the F-code to the destination device identified by the destination ID via the network I/F 409. In addition, in response to receiving a transmission request including an F-code and a user ID from a user terminal, the fax transmission unit 34 transmits fax data associated with the F-code to the user terminal identified by the user ID via the network I/F 409.

In response to receiving a transmission request from a destination device via network I/F 409, the status update unit 35 updates the viewing status corresponding to the destination ID included in the transmission request from "unread state" to "read state." In addition, in response to receiving a transmission request from a user terminal via network I/F 409, the status update unit 35 reads the fax number (= destination ID) associated with the user ID included in the transmission request from the user management table shown in FIG. 7(B). Then, the status update unit 35 updates the viewing status corresponding to the read destination ID from "unread state" to "read state."

In response to receiving a viewing status confirmation request including a data ID, the viewing status transmission unit 36 transmits multiple viewing statuses associated with the data ID via the network I/F 409 to the device that sent the viewing status confirmation request (recipient device, user terminal).

In addition to the fax sending and receiving program, memory 37 stores the fax management table shown in Figure 6, the data management table shown in Figure 7(A), and the user management table shown in Figure 7(B).

As shown in Figure 6, the fax management table stores one F code, one sender ID, one transmission date and time, and N (N is an integer greater than or equal to 2) recipient IDs and N viewing statuses, in association with each other. The number of recipient IDs and viewing statuses is not particularly limited as long as it is two or more. In the example of Figure 6, one record contains multiple recipient IDs and viewing statuses, but in reality, they are normalized and stored.

As shown in Figure 7 (A), the data management table stores F-codes and fax data in a one-to-one correspondence. That is, the sender ID, sending date and time, recipient ID, and viewing status shown in Figure 6 correspond to the fax data shown in Figure 7 (A) by F-code. As shown in Figure 7 (B), the user management table stores user IDs and fax numbers in a one-to-one correspondence.

Figure 8 is a flowchart of the upload process. The upload process stores fax data uploaded from a sending device in memory 37 and notifies a receiving device that the fax data has been uploaded. Below, we will explain an example in which MFP 10A, which is a sending device, broadcasts fax data to MFPs 10B, 10C, and 10D, which are receiving devices.

First, the MFP 10A transmits the fax data, sender ID [0311112222], transmission date and time [2020/01/02 12:00], F-Code [03111122222001021200], and recipient ID [0333334444] to the fax sending and receiving server 30 via the network I/F 250 (S801). Next, the MFP 10A determines whether there are any other recipient IDs to which the fax should be sent by broadcast (S802).

If the MFP 10A determines that there is another recipient ID [0655556666] to which the fax should be sent (S802: Yes), it transmits the fax data, sender ID [0311112222], sending date and time [2020/01/02 12:00], F-code [03111122222001021200], and recipient ID [0655556666] to the fax sending and receiving server 30 via the network I/F 250 (S801).

Furthermore, if the MFP 10A determines that there is another recipient ID [0457778888] to which a broadcast transmission should be made (S802: Yes), it transmits the fax data, sender ID [0311112222], transmission date and time [2020/01/02 12:00], F-code [03111122222001021200], and recipient ID [0457778888] to the fax sending and receiving server 30 via the network I/F 250 (S801).

That is, in the first, second, and third times of step S801, the fax data, sender ID, transmission date and time, and F-code are the same, but the recipient IDs are different. That is, MFP 10A repeats the process of sending the same fax data, sender ID, transmission date and time, and F-code, and one different recipient ID from multiple recipient IDs (S801) as many times as the number of recipient IDs. Then, if MFP 10A determines that there are no other recipient IDs to which to send the fax (S802: No), it ends the upload process.

Meanwhile, the fax receiving unit 31 of the fax sending/receiving server 30 receives the fax data, sender ID, transmission date and time, F-code, and recipient ID from the MFP 10A via the network I/F 409 (S801) and notifies the storage processing unit 32.

Next, each time the fax receiving unit 31 receives fax data, the storage processing unit 32 determines whether the F-code [03111122222001021200] received by the fax receiving unit 31 is registered in the fax management table (S803). At the time of the first broadcast transmission, the F-code is not registered in the fax management table. If the storage processing unit 32 determines that the F-code is not registered in the fax management table (S803: No), it executes steps S804 to S805.

The storage processing unit 32 associates the F-code [03111122222001021200] and fax data received by the fax receiving unit 31 with each other and stores them in the data management table (S804). The storage processing unit 32 also registers the F-code [03111122222001021200], sender ID [0311112222], sending date and time [2020/01/02 12:00], and recipient ID [0333334444] received by the fax receiving unit 31, along with the viewing status set to "Unread" as a new record in the fax management table (S805).

Next, the reception notification unit 33 sends a fax reception notification via the network I/F 409 to the MFP 10B identified by the destination ID [0333334444] received by the fax receiving unit 31 (S806). The fax reception notification includes, for example, the F-code [03111122222001021200], sender ID [0311112222], and transmission date and time [2020/01/02 12:00] received by the fax receiving unit 31. The same applies to the fax reception notification sent in step S808.

MFP 10B receives a fax reception notification from fax sending and receiving server 30 via network I/F 250. MFP 10B then stores the F-code [03111122222001021200], sender ID [0311112222], and transmission date and time [2020/01/02 12:00] contained in the received fax reception notification in association with each other in HDD 209.

Next, if the storage processing unit 32 determines during the second broadcast transmission that the F-code [03111122222001021200] received by the fax receiving unit 31 is registered in the fax management table (S803: Yes), it adds the recipient ID [0655556666] and a viewing status set to "Unread" to the record containing the discovered F-code [03111122222001021200] (S807). Next, the reception notification unit 33 sends a fax reception notification via the network I/F 409 to the MFP 10C identified by the recipient ID [0655556666] received by the fax receiving unit 31 (S808).

Next, if the storage processing unit 32 determines during the third broadcast transmission that the F-code [03111122222001021200] received by the fax receiving unit 31 is registered in the fax management table (S803: Yes), it adds the recipient ID [0457778888] and a viewing status set to "Unread" to the record for the discovered F-code [03111122222001021200] (S807). Next, the reception notification unit 33 sends a fax reception notification via the network I/F 409 to the MFP 10D identified by the recipient ID [0457778888] received by the fax receiving unit 31 (S808).

Then, the fax sending and receiving server 30 ends the upload process upon receiving all the data for the broadcast transmission. In other words, the storage processing unit 32 stores only the fax data received the first time in the broadcast transmission in memory 37, and omits saving to memory 37 fax data received after the second time in the broadcast transmission.

Figure 9 is a flowchart of the download process executed between MFP 10B and fax sending and receiving server 30. Figure 10 shows examples of the data list screen (A), data display screen (B), and viewing status list screen (C) displayed on the panel display unit 240a of MFP 10B. The download process is a process for downloading fax data stored in the fax sending and receiving server 30 and the viewing status of multiple receiving devices in response to a request from the receiving device. The process in response to a request from MFP 10B, which is the receiving device, is described below. Also, assume that at the start of the process in Figure 9, two F-Codes, [03111122222001021200] and [07888899991912310456], are stored in HD 209 of MFP 10B.

First, MFP 10B displays a data list screen on panel display unit 240a (S901). As shown in FIG. 10(A), the data list screen includes records corresponding to F-codes [03111122222001021200] and [07888899991912310456] stored in HD 209, as well as a "Display Data" button, a "Print Data" button, and a "Delete Data" button. MFP 10B then accepts, via operation panel 240b, operations to select a record displayed on the data list screen and to press the "Display Data" button, the "Print Data" button, or the "Delete Data" button.

Next, in response to receiving via the operation panel 240b an operation to select a record corresponding to F-code [03111122222001021200] and an operation to press the [Data Display] button (S902), the MFP 10B transmits a download request to the fax sending/receiving server 30 via the network I/F 250 (S903). The download request is information requesting the transmission of fax data corresponding to the selected F-code [03111122222001021200]. The download request includes, for example, the F-code [03111122222001021200] and the fax number [0333334444] that identifies the MFP 10B itself.

In response to receiving a download request from MFP 10B via network I/F 409 (S903), the fax sending unit 34 of the fax sending/receiving server 30 reads, from the data management table, the fax data corresponding to the F-code [03111122222001021200] included in the received download request. The fax sending unit 34 then transmits the read fax data via network I/F 409 to MFP 10B, which is identified by the fax number [0333334444] included in the download request (S904).

The fax sending unit 34 also notifies the status update unit 35 of the received download request. The status update unit 35 then updates the viewing status corresponding to the F-code [03111122222001021200] and fax number (= recipient ID) [0333334444] included in the download request from [unread status] shown in Figure 6 (A) to [read status] shown in Figure 6 (B) (S905).

Next, upon receiving fax data from the fax sending and receiving server 30 via the network I/F 250 (S904), the MFP 10B displays a data display screen on the panel display unit 240a (S906). As shown in FIG. 10(B), the data display screen includes an image displayed by the fax data received from the fax sending and receiving server 30, as well as a "Previous Page" button, a "Next Page" button, a "Zoom In" button, a "Zoom Out" button, a "Check Destination" button, and a "End Display" button. The MFP 10B then accepts, via the operation panel 240b, an operation to press a button included in the data display screen.

When the fax data contains multiple images (pages), if the "Previous Page" button is pressed, MFP 10B displays the page previous to the currently displayed page on the data display screen. Furthermore, if the "Next Page" button is pressed, MFP 10B displays the page following the currently displayed page on the data display screen. Furthermore, if the "Enlarge" button is pressed, MFP 10B enlarges the currently displayed page and displays it on the data display screen. Furthermore, if the "Reduce" button is pressed, MFP 10B reduces the currently displayed page and displays it on the data display screen. Furthermore, if the "End Display" button is pressed, MFP 10B ends the download process without executing the processes from step S907 onwards.

When MFP 10B receives an operation to press the [Confirm Recipient] button via operation panel 240b (S907), it sends a viewing status confirmation request to fax sending/receiving server 30 via network I/F 250 (S908). The viewing status confirmation request is information for confirming whether the fax data corresponding to the F-code [03111122222001021200] selected on the data list screen has been viewed at each of the multiple recipient devices to which it was broadcast. The viewing status confirmation request includes, for example, the selected F-code [03111122222001021200] and the fax number [0333334444] that identifies the device itself.

In response to receiving a viewing status confirmation request from MFP 10B via network I/F 409 (S908), the viewing status transmission unit 36 of fax sending/receiving server 30 reads from the data management table the record corresponding to the F-code [03111122222001021200] included in the received viewing status confirmation request. Then, the viewing status transmission unit 36 transmits viewing status list data via network I/F 409 to MFP 10B identified by the fax number [0333334444] included in the viewing status confirmation request (S909). The viewing status list data includes the information set in the read record (at least all viewing statuses corresponding to F-code [03111122222001021200]).

Next, upon receiving the viewing status list data from the fax sending/receiving server 30 via the network I/F 250 (S909), the MFP 10B displays a viewing status list screen on the panel display unit 240a (S910). As shown in FIG. 10C, the viewing status list screen includes the transmission date and time [2020/01/02 12:00], sender ID [0311112222], F-code [03111122222001021200], multiple recipient ID and viewing status pairs (recipient ID [0333334444] - viewing status [read], recipient ID [0655556666] - viewing status [unread], recipient ID [0457778888] - viewing status [unread]), and an "End display" button.

Although not shown in the figure, when the [Print Data] button in Figure 10(A) is pressed, the processes of steps S903 to S905 are executed. Furthermore, in step S906, MFP 10B controls printer unit 232 to print an image indicated by the received fax data onto a sheet. Furthermore, although not shown in the figure, when the [Delete Data] button in Figure 10(A) is pressed, MFP 10B deletes the selected F-Code [03111122222001021200] from HD 209.

Figure 11 is a flowchart of the download process executed between the smartphone 20 and the fax sending/receiving server 30. Note that the same step numbers are used for processes that are common to Figure 9, and detailed explanations will be omitted; the following explanation will focus on the differences.

First, the smartphone 20 sends a download request including the user ID [satoh] and F-code [03111122222001021200] set on the smartphone 20 to the fax transmission/reception server 30 via the long-distance communication circuit 312 (S1101). The status update unit 35 of the fax transmission/reception server 30 reads the fax number [0333334444] corresponding to the user ID [satoh] included in the download request from the user management table (S1102). The status update unit 35 then updates the viewing status corresponding to the F-code [03111122222001021200] included in the download request and the read fax number [0333334444] (= recipient ID) from [unread state] to [read state] (S905).

The above embodiment provides the following advantages, for example:

In the above embodiment, the viewing status of multiple recipient devices for broadcast transmissions is centrally managed by the fax sending and receiving server 30, allowing one of the multiple recipient devices for broadcast transmissions (e.g., MFP 10B) to know the viewing status of the other recipient devices (e.g., MFP 10C, MFP 10D).

Furthermore, according to the above embodiment, by using an F code conforming to the G3 standard protocol as a data ID that uniquely identifies information related to broadcast transmission, the processing shown in Figures 8 and 9 can be realized without extending the protocol. However, the data ID is not limited to an F code as long as it can uniquely identify broadcast transmission.

In the above embodiment, an example was described in which the F code was sent from the MFP 10A to the fax sending and receiving server 30, but the sending of the F code in step S801 may be omitted. The fax sending and receiving server 30 may then generate an F code (data ID) by combining the sender ID and transmission date and time received from the MFP 10A.

Furthermore, according to the above embodiment, fax data can be viewed not only on the receiving device, but also on a user terminal linked to the receiving device. Furthermore, by managing the correspondence between user IDs and fax numbers (= recipient IDs) on the fax sending/receiving server 30, the viewing status of fax data on the user terminal can be reflected.

Furthermore, according to the above embodiment, the fax data received in the first broadcast transmission is registered in the data management table, and the registration of fax data received in the second and subsequent broadcast transmissions is omitted, thereby saving storage capacity in memory 37. However, the fax sending and receiving server 30 may also store fax data received in the second and subsequent broadcast transmissions in memory 37. Also, in the above embodiment, an example (S801-S802) in which fax data is repeatedly sent for each recipient device is described, but the specific method by which the sending device sends fax data is not limited to the above example, and multiple recipient IDs may be added to the fax data before transmission.

The functions of the above-described embodiments can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes processors programmed to perform functions by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and conventional circuit modules designed to perform the above-described functions.

Furthermore, the source device and destination device are not limited to MFP 10, as long as they are devices with communication capabilities. The source device and destination device may be, for example, a PJ (Projector), an IWB (Interactive White Board: an electronic whiteboard with a blackboard function that allows for intercommunication), an output device such as digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network home appliance, an automobile (Connected Car), a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC.

The present invention is not limited to the above-described embodiments, and various modifications are possible without departing from the technical gist of the invention. The present invention covers all technical matters included in the technical concept described in the claims. The above-described embodiments are preferred examples, but those skilled in the art will be able to realize various modifications based on the disclosed content. Such modifications are also included within the technical scope described in the claims.

1 Fax transmission/reception system 10, 10A, 10B, 10C, 10D: MFP
20: Smartphone 30: Fax transmission/reception server 31: Fax receiving unit 32: Storage processing unit 33: Reception notification unit 34: Fax transmitting unit 35: Status update unit 36: Viewing status transmitting unit 37: Memory 100: Communication networks 201, 301, 401: CPU
202a, 302, 402: ROM
202b, 303, 403: RAM
206: ASIC
208, 405: HDD controller 210: controllers 220, 320: short-range communication circuits 220a, 320a: antenna 221: AGP bus 222: PCI bus 230: engine control unit 231: scanner unit 232: printer unit 233: fax unit 240: operation panel 240a: panel display unit 240b: operation panel 250: network I/F
305, 313: CMOS sensors 306, 314: Image sensor I/F
307: Orientation sensor 308: Recording media 309, 416: Media I/F
310: Bus line 311: GPS receiver 312: Long-distance communication circuit 315: Microphone 316: Speaker 317: Sound input/output I/F
318, 406: Display 319, 408: External device connection I/F
321: Touch panel 409: Network I/F
410: Data bus 411: Keyboard 412: Pointing device 414: RW drive 415: Recording media

JP 2009-115877 A

Claims (6)

a fax receiving unit that receives fax data, a plurality of destination IDs that uniquely identify destination devices that are to receive the fax data, and a data ID that uniquely identifies a combination of the fax data and the plurality of destination IDs from a source device;
a storage processing unit that stores the data ID, the fax data, the plurality of destination IDs, and a plurality of viewing states indicating whether the fax data has been viewed at a destination device identified by each of the plurality of destination IDs in a memory in association with one another;
a reception notification unit that notifies a receiving device identified by each of the plurality of receiving device IDs received from the sending device that the fax data has been received from the sending device;
a fax sending unit that, in response to receiving a transmission request including the destination ID from the destination device, sends the fax data to the destination device identified by the destination ID included in the transmission request;
a status update unit that updates the viewing status corresponding to the destination ID included in the transmission request from an unread status indicating that the fax data has not been viewed to a read status indicating that the fax data has been viewed;
a viewing status transmission unit that, in response to receiving a first viewing status confirmation request including the data ID from one of a plurality of receiving device identified by the plurality of receiving device IDs, transmits the plurality of viewing statuses associated with the data ID to the one receiving device that is a sender of the first viewing status confirmation request ;
The memory stores the destination ID and the user ID in association with each other,
the fax sending unit, in response to receiving a transmission request including the user ID from a user terminal, sends the fax data to a user terminal identified by the user ID included in the transmission request;
The state update unit
reading from the memory the destination ID associated with the user ID included in the transmission request;
The fax sending and receiving server updates the viewing status corresponding to the read destination ID from the unread status to the read status . The fax sending and receiving server of claim 1, characterized in that the data ID is an F code that combines a sender ID that uniquely identifies the sending device and the date and time the fax data was sent. the fax receiving unit repeatedly receives the common fax data and data ID and different ones of the plurality of destination IDs from a transmission source device;
The storage processing unit
Each time the fax receiving unit receives the fax data, it determines whether the data ID is stored in the memory;
When it is determined that the data ID is not stored in the memory, the data ID, the fax data, the recipient ID, and the viewing status are stored in the memory in association with each other;
A fax sending/receiving server as described in claim 1 or 2, characterized in that when it is determined that the data ID is stored in the memory, the destination ID and the viewing status are stored in the memory in correspondence with the data ID. The fax sending and receiving server of claim 1, wherein the viewing status transmission unit transmits the plurality of viewing statuses associated with the data ID to the user terminal identified by the user ID in response to receiving a second viewing status confirmation request including the user ID and the data ID from the user terminal. a source device that transmits fax data;
a plurality of receiving devices that receive the fax data transmitted from the transmitting device;
a fax sending and receiving server that relays the fax data from the sending device to a plurality of receiving devices,
The fax sending and receiving server
a fax receiving unit that receives the fax data, a plurality of destination IDs that uniquely identify the destination devices, and a data ID that uniquely identifies a combination of the fax data and the plurality of destination IDs from the source device;
a storage processing unit that stores the data ID, the fax data, the plurality of destination IDs, and a plurality of viewing states indicating whether the fax data has been viewed at the destination devices identified by each of the plurality of destination IDs in a memory in association with one another;
a reception notification unit that notifies the receiving device identified by each of the plurality of receiving device IDs received from the sending device that the fax data has been received from the sending device;
a fax sending unit that, in response to receiving a transmission request including the destination ID from the destination device, sends the fax data to the destination device identified by the destination ID included in the transmission request;
a status update unit that updates the viewing status corresponding to the destination ID included in the transmission request from an unread status indicating that the fax data has not been viewed to a read status indicating that the fax data has been viewed;
a viewing status transmission unit that, in response to receiving a first viewing status confirmation request including the data ID from one of a plurality of receiving device identified by the plurality of receiving device IDs, transmits the plurality of viewing statuses associated with the data ID to the one receiving device that is a sender of the first viewing status confirmation request;
The memory stores the destination ID and the user ID in association with each other,
the fax sending unit, in response to receiving a transmission request including the user ID from a user terminal, sends the fax data to a user terminal identified by the user ID included in the transmission request;
The state update unit
reading from the memory the destination ID associated with the user ID included in the transmission request;
A fax sending and receiving system characterized in that the viewing status corresponding to the read recipient ID is updated from the unread status to the read status . A fax transmission/reception method for relaying fax data broadcast from a sending device to a plurality of receiving devices, comprising:
receiving, from a source device, the fax data, a plurality of destination IDs that uniquely identify destination devices, and a data ID that uniquely identifies a combination of the fax data and the plurality of destination IDs;
the data ID, the fax data, the plurality of destination IDs, and a plurality of viewing states indicating whether the fax data has been viewed at the destination devices identified by the plurality of destination IDs are stored in a memory in association with one another;
notifying the receiving device identified by each of the plurality of receiving IDs received from the sending device that the fax data has been received from the sending device;
In response to receiving a transmission request including the destination ID from the destination device, transmitting the fax data to the destination device identified by the destination ID included in the transmission request;
updating the viewing status corresponding to the destination ID included in the transmission request from an unread status indicating that the fax data has not been viewed to a read status indicating that the fax data has been viewed;
In response to receiving a first viewing status confirmation request including the data ID from one of the plurality of receiving device identified by the plurality of receiving device IDs, transmitting the plurality of viewing statuses associated with the data ID to the one receiving device that is a sender of the first viewing status confirmation request ;
The memory stores the destination ID and the user ID in association with each other,
In response to receiving a transmission request including the user ID from a user terminal, transmitting the fax data to the user terminal identified by the user ID included in the transmission request;
reading from the memory the destination ID associated with the user ID included in the transmission request;
a fax sending and receiving method for updating the viewing status corresponding to the read destination ID from the unread status to the read status ;