Patent Description:
There are cases where the status of a document to be managed changes from moment to moment. For real-time ascertaining of the current status of a document, there is known a technology of changing the current status of an unread document from unread to read in response to an operation of reading all pages of the document, and changing the current status of the document from unread to hold in response to an operation of reading a part of the pages of the unread document (for example, <CIT>).

For example, a facsimile document received from a sender facsimile machine is accumulated in a receiver facsimile machine. When the received document is read using the receiver facsimile machine, the status of the received document is changed from an unread status to a read status. In recent years, there is a system for accumulating received facsimile documents in a cloud or the like so that the received documents can be viewed from a device other than the receiver facsimile machine.

Additionally, there are systems in which a received document is viewable from an apparatus or device other than the receiver apparatus. In such a system, if a received document viewed from a device other than the receiver apparatus is unconditionally changed from an unread status to a read status, a user who should view the received document may overlook the received document. The information processing system disclosed by <CIT> does not address the above inconvenience. <CIT> discloses an information coordination system and <CIT> proposes a displayable information management system.

In view of the foregoing, an object of the present disclosure is to control a change of read/unread status of a document that is transmitted from a sender apparatus and viewed from an apparatus or device other than a receiver apparatus. A server for controlling a status of a document transmitted by facsimile is provided in accordance with claim <NUM>. Further aspects and preferred embodiments are set out in claim <NUM> et seq.

In order to achieve the above-described object, there are provided a server for controlling a status of a document transmitted by facsimile from a sender apparatus to a receiver apparatus as described in appended claims. Advantageous embodiments are defined by the dependent claims.

Accordingly, the read/unread status of the received document viewed from an apparatus or device other than the receiver apparatus is properly controlled.

However, the disclosure of this specification is not intended to be limited to the specific terminology so selected and it is to be understood that each specific element includes all technical equivalents that have a similar function, operate in a similar manner, and achieve a similar result falling within the scope of the appended claims.

Referring to the drawings, embodiments of the present disclosure are described. In the present disclosure, the "site" is a place serving as a home (or platform) of an activity or a foothold for the activity, and is, for example, a place, a department, a business, or the like.

<FIG> is a schematic diagram illustrating an example of a configuration of a management system according to the present embodiment. <FIG> illustrates a management system <NUM> in which a facsimile reception server <NUM>, apparatuses 12A to 12D such as facsimile machines, and a device <NUM> such as a smart device are connected via a network <NUM>. The network <NUM> is, for example, a telephone network, the Internet, or a local area network (LAN) for data communication. Any one of the apparatuses 12A to 12D may be simply referred to as the apparatus <NUM>.

The apparatus <NUM> performs facsimile transmission and reception. The apparatus <NUM> is, for example, a facsimile machine, a multifunction peripheral (MFP), or the like. The term "MFP" also represents a multifunction product and a multifunction printer. The apparatus <NUM> accesses the facsimile reception server <NUM> via the network <NUM>. When transmitting a facsimile document, the apparatus <NUM> that is the sender apparatus transmits the facsimile document to the facsimile reception server <NUM>, designating a facsimile number (receiver number) of a receiver apparatus. The apparatus <NUM> that is the receiver apparatus receives the facsimile document from the facsimile reception server <NUM>.

The facsimile reception server <NUM> is implemented by one or more information processing apparatuses. Alternatively, the facsimile reception server <NUM> may be implemented using a cloud. The facsimile reception server <NUM> receives and stores facsimile documents (received document) addressed to the apparatus <NUM> of, for example, an organization such as a company having a plurality of sites.

The device <NUM> is, for example, a smart device of a user belonging to the organization. Examples of the device <NUM> includes a head up display (HUD) device, an industrial machine, a network home appliance, a mobile phone, a smartphone, a tablet terminal, a game console, and a personal digital assistant (PDA).

The received document stored in the facsimile reception server <NUM> can be acquired by, not limited to the receiver apparatus <NUM>, any of the apparatuses <NUM> and the device <NUM> that are accessible to the facsimile reception server <NUM> via the network <NUM>. In such a system, if a received document viewed from a device other than the receiver apparatus is unconditionally changed from an unread status to a read status, a user who should view the received document may overlook the received document. In view of the foregoing, the facsimile reception server <NUM> manages (controls) the read/unread status of the stored received documents as described later.

The notification of facsimile reception to the receiver apparatus <NUM> may be push notification in which the facsimile reception server <NUM> notifies the receiver apparatus <NUM> of the facsimile reception, or may be pull notification in which the receiver apparatus <NUM> makes an inquiry to the facsimile reception server <NUM>.

The configuration of the management system <NUM> illustrated in <FIG> is one example. For example, at least a part of functions of the apparatuses <NUM> and the device <NUM> may be implemented by the facsimile reception server <NUM>. At least a part of the functions of the facsimile reception server <NUM> may be implemented by another server such as a management server other than the facsimile reception server <NUM>, or may be implemented by the apparatus <NUM> or the device <NUM>.

The facsimile reception server <NUM> illustrated in <FIG> is implemented by, for example, a computer <NUM> (information processing apparatus) having a hardware configuration as illustrated in <FIG>. The device <NUM> illustrated in <FIG> may be implemented by the computer <NUM> having a hardware configuration as illustrated in <FIG> is a block diagram illustrating an example of a hardware configuration of a computer according to the present embodiment.

The computer <NUM> includes a central processing unit (CPU) <NUM>, a read only memory (ROM) <NUM>, a random access memory (RAM) <NUM>, a hard disk (HD) <NUM>, a hard disk drive (HDD) controller <NUM>, a display <NUM>, an external device interface (I/F) <NUM>, a network I/F <NUM>, a data bus <NUM>, a keyboard <NUM>, a pointing device <NUM>, a digital versatile disk rewritable (DVD-RW) drive <NUM>, and a media I/F <NUM>.

The CPU <NUM> controls entire operation of the computer <NUM> according to a program. The ROM <NUM> stores a program such as an initial program loader (IPL) used for driving the CPU <NUM>. The RAM <NUM> is used as a work area for the CPU <NUM>. The HD <NUM> stores various data such as a program. The HDD controller <NUM> controls reading and writing of various data from and to the HD <NUM> under control of the CPU <NUM>.

The display <NUM> displays various information such as a cursor, a menu, a window, a character, and an image. The external device I/F <NUM> is an interface for connecting various external devices. The external device in this case is, for example, a universal serial bus (USB) memory. The network I/F <NUM> is an interface for data communication using the network <NUM>. Examples of the data bus <NUM> include, but not limited to, an address bus and a data bus that electrically connect the components, such as the CPU <NUM>, with one another.

The keyboard <NUM> is one example of an input device provided with a plurality of keys for allowing a user to input characters, numerals, or various instructions. The pointing device <NUM> is an example of an input device that allows a user to select or execute a specific instruction, select an item to be processed, or move a cursor being displayed. The DVD-RW drive <NUM> reads and writes various data from and to a DVD-RW <NUM>, which is an example of a removable recording medium. The removable storage medium is not limited to the DVD-RW and may be a DVD-recordable (DVD-R) or the like. The media I/F <NUM> controls reading and writing (storing) of data from and to a recording medium <NUM> such as a flash memory.

The apparatus <NUM> illustrated in <FIG> may be implemented by an MFP <NUM> having a hardware configuration as illustrated in <FIG> is a block diagram illustrating an example of the hardware configuration of the MFP <NUM> according to the present embodiment.

The MFP <NUM> illustrated in <FIG> includes a controller <NUM>, a short-range communication circuit <NUM>, an engine controller <NUM>, a control panel <NUM>, and a network I/F <NUM>. The controller <NUM> includes a CPU <NUM> as a main processor of a computer, a system memory <NUM>, a north bridge (NB) <NUM>, a south bridge (SB) <NUM>, an application specific integrated circuit (ASIC) <NUM>, a local memory <NUM> as a storage area, a hard disk drive (HDD) controller <NUM>, and a hard disk (HD) <NUM> as a storage area. The NB <NUM> and the ASIC <NUM> are connected via an accelerated graphics port (AGP) bus <NUM>.

The CPU <NUM> is a controller that controls the entire operation of the MFP <NUM>. The NB <NUM> is a bridge that connects the CPU <NUM> to the system memory <NUM>, the SB <NUM>, and the AGP bus <NUM>. The NB <NUM> includes a memory controller that controls reading and writing from and to the system memory <NUM>, a peripheral component interconnect (PCI) master, and an AGP target.

The system memory <NUM> includes a ROM 902a and a RAM 902b. The ROM 902a stores data and program for implementing various functions of the controller <NUM>. The RAM 902b is used to load the program and the data. The RAM 902b is also used as a drawing memory to store drawing data for printing. The program stored in the RAM 902b may be stored in any computer-readable storage (recording) medium, such as a compact disc-read only memory (CD-ROM), compact disc-recordable (CD-R), or digital versatile disc (DVD), in a file format installable or executable by the computer, for distribution.

The SB <NUM> is a bridge that connects the NB <NUM> with a PCI device or a peripheral device. The ASIC <NUM> is an integrated circuit (IC) dedicated to an image processing use and includes a hardware element for image processing. The ASIC <NUM> is a bridge that connects the AGP bus <NUM>, a PCI bus <NUM>, the HDD controller <NUM>, and the local memory <NUM> with each other.

The ASIC <NUM> includes a PCI target, an AGP master, an arbiter (ARB) as a central processor of the ASIC <NUM>, a memory controller to control the local memory <NUM>, a plurality of direct memory access controllers (DMACs) to rotate image data, and a PCI unit. By converting coordinates of the image data with a hardware logic, image data are rotated. The PCI unit transfers data between a scanner unit <NUM> and a printer unit <NUM> via the PCI bus <NUM>. The ASIC <NUM> may be connected to a USB interface, or the Institute of Electrical and Electronics Engineers <NUM> (IEEE1394) interface.

The local memory <NUM> is used as a buffer for image data to be copied or coding. The HD <NUM> is a storage (memory) that stores various image data, font data for printing, and form data. The HDD controller <NUM> reads and writes various data from and to the HD <NUM> under control of the CPU <NUM>. The AGP bus <NUM> is a bus interface for a graphics accelerator card, which is proposed to accelerate graphics processing. Through directly accessing the system memory <NUM> by high-throughput, speed of the graphics accelerator card is improved.

Further, the short-range communication circuit <NUM> is provided with a short-range communication antenna 920a. The short-range communication circuit <NUM> is a communication circuit in compliance with the near field communication (NFC), BLUETOOTH, and the like.

The engine controller <NUM> includes the scanner unit <NUM> and the printer unit <NUM>. The control panel <NUM> includes a panel display 940a and an operation device 940b. The panel display 940a is, e.g., a touch panel that displays current settings or a selection screen and receives a user input. The operation device 940b includes, e.g., a numeric keypad and a start key. The numeric keypad receives assigned values of image forming parameters such as an image density parameter. The start key receives an instruction to start copying.

The controller <NUM> controls entire operation of the MFP <NUM>. For example, the controller <NUM> controls drawing, communication, or user inputs to the control panel <NUM>. The scanner unit <NUM> or the printer unit <NUM> includes an image processing unit for, for example, error diffusion and gamma conversion.

Note that, in response to an instruction to select a specific application through the control panel <NUM> by an application switch key, the MFP <NUM> sequentially selects document server, coping, printing, and facsimile transmission functions. The MFP <NUM> enters a document server mode to store document data with selection of the document server function and enters a copy mode with selection of the copy function. Further, the MFP <NUM> enters a printer mode with selection of the printing function and enters a facsimile mode with selection of the facsimile function.

The network I/F <NUM> is an interface for data communication using the network <NUM>. The short-range communication circuit <NUM> and the network I/F <NUM> are electrically connected to the ASIC <NUM> through the PCI bus <NUM>.

To enable authentication, by an IC card, of a user to use the MFP <NUM>, the MFP <NUM> includes a built-in IC card reader. Alternatively, the IC card reader is attached to the MFP <NUM>. The MFP <NUM> reads identification information unique to the IC card from a radio frequency (RF) tag embedded in the IC card by wireless communication. In another example, the IC card is included in a smart device such as a smartphone. In still another example, the MFP <NUM> uses any suitable device other than the IC card reader, such as a biometric authentication device (that recognizes fingerprint, palm print, iris, face, etc.) or a barcode reading device.

The management system <NUM> according to the present embodiment has, for example, a functional configuration as illustrated in <FIG> is a schematic diagram illustrating an example of the functional configuration of the management system according to the present embodiment. In the description of the functional configuration of <FIG>, descriptions of components unnecessary for the description of the present embodiment may be omitted.

The apparatus <NUM> illustrated in <FIG> includes a facsimile communication control unit <NUM>, a received document acquisition request unit <NUM>, an authentication control unit <NUM>, and a display control unit <NUM>. The apparatus <NUM> (in particular, the CPU <NUM> illustrated in <FIG> when the apparatus <NUM> is implemented by the MFP <NUM>) executes a program to implement, for example, the functional units illustrated in <FIG>.

The facsimile communication control unit <NUM> transmits and receives a facsimile document using a facsimile communication protocol. The received document acquisition request unit <NUM> requests acquisition of a received document or a list of received documents stored in the facsimile reception server <NUM> from the facsimile reception server <NUM>. Thus, the received document acquisition request unit <NUM> acquires the received document or the received document list (an example of received document list information) from the facsimile reception server <NUM>. The authentication control unit <NUM> controls processing relating to authentication. The display control unit <NUM> displays the received document list or the received document on the control panel <NUM>.

The device <NUM> illustrated in <FIG> includes a received document acquisition request unit <NUM>, an authentication control unit <NUM>, and a display control unit <NUM>. The device <NUM> (in particular, the CPU <NUM> illustrated in <FIG> when the device <NUM> is implemented by the computer <NUM>) executes a program to implement, for example, the functional units illustrated in <FIG>.

The received document acquisition request unit <NUM> requests acquisition of a received document or a list of received documents stored in the facsimile reception server <NUM> from the facsimile reception server <NUM>. Thus, the received document acquisition request unit <NUM> acquires the received document or the received document list from the facsimile reception server <NUM>. The authentication control unit <NUM> controls processing relating to authentication. The display control unit <NUM> displays the received document list or the received document on the display <NUM>.

As described above, in the example of the management system <NUM> illustrates in <FIG>, the apparatus <NUM> or the device <NUM> acquires the received document or the list of received documents stored in the facsimile reception server <NUM> and displays or prints the received document or the received document list, to allow the user to view the received document. The management system <NUM> may allow either one of the apparatuses <NUM> and the device <NUM> to view the received document stored in the facsimile reception server <NUM>.

The facsimile reception server <NUM> illustrated in <FIG> includes a received document management unit <NUM>, a read/unread management unit <NUM>, a received document list providing unit <NUM>, an information update control unit <NUM>, a management information memory <NUM>, and a received document memory <NUM>. The facsimile reception server <NUM> (in particular, the CPU <NUM> illustrated in <FIG> when the facsimile reception server <NUM> is implemented by the computer <NUM>) executes a program to implement, for example, the functional units illustrated in <FIG>.

The received document management unit <NUM> receives, from the sender apparatus <NUM>, a facsimile document addressed to the apparatus <NUM> of an organization, and stores the facsimile document (received document). The read/unread management unit <NUM> manages (controls) read/unread status of the received document stored in the facsimile reception server <NUM> as described later. The received document list providing unit <NUM> transmits, to the request source, the received document list or the received document based on the request of acquisition thereof from the apparatus <NUM> or the device <NUM>. The information update control unit <NUM> updates management information stored in the management information memory <NUM>. The management information memory <NUM> stores various information used for processing performed by the facsimile reception server <NUM>. The received document memory <NUM> stores a received document that is faxed from the sender apparatus <NUM> to the receiver apparatus <NUM> (e.g., the apparatus <NUM> owned by an organization). When the facsimile reception server <NUM> is implemented by the computer <NUM> illustrated in <FIG>, the management information memory <NUM> and the received document memory <NUM> are implemented by, for example, the ROM <NUM> illustrated in <FIG>.

A description is given of facsimile transmission and reception by the management system <NUM> according to the present embodiment. <FIG> is a diagram illustrating an example of facsimile transmission and reception in the management system <NUM> according to the present embodiment. <FIG> illustrates an example in which the apparatus 12A is a sender (sender apparatus) of a facsimile document and the apparatus 12B is a receiver (receiver apparatus) of the facsimile document.

To transmit a facsimile document to the receiver apparatus 12B, the sender apparatus 12B transmits the facsimile document to the facsimile reception server <NUM>, designating the facsimile number "<NUM>" of the receiver apparatus 12B as the receiver number. The receiver apparatus 12B of the facsimile document can access the facsimile reception server <NUM> and acquire the facsimile document (received document) from the facsimile reception server <NUM>.

In the management system <NUM> according to the present embodiment, in addition to the receiver apparatus 12B, any of the apparatuses 12C and 12D and the device <NUM> accessible (permitted to access) to the facsimile reception server <NUM> can acquire (download) the received documents stored in the facsimile reception server <NUM> for the user to view the documents. Note that, hereinafter the "received document" may be simply referred to as a "document" for simplicity.

The facsimile reception server <NUM> stores the document received from the sender apparatus 12A in the received document memory <NUM>, and manages read/unread status of the received document using, for example, a received document table (received document list in a table format) as illustrated in <FIG> illustrates an example of the received document table according to the present embodiment. The received document table of <FIG> is stored in, for example, the management information memory <NUM>.

The received document table illustrated in <FIG> includes a document identifier (ID), a read flag, a reception date and time, a sender, and a receiver as data items. The document ID is an example of identification information of the received document. The read flag is an example of information indicating an unread status or a read status of the received document. In <FIG>, "<NUM>" represents an unread status, and "<NUM>" represents a read status.

The sender is represented by the facsimile number of the sender of the received document. The receiver is represented by the facsimile number of the receiver of the received document. The read/unread management unit <NUM> of the facsimile reception server <NUM> manages read/unread status of the stored received document, using the received document table of <FIG>.

For example, when the receiver apparatus 12B having the facsimile number "<NUM>" acquires the received document list of <FIG> from the facsimile reception server <NUM>, the control panel <NUM> (illustrated in <FIG>) displays a screen <NUM> illustrated in <FIG> illustrate an example of screen transition on the control panel <NUM> (illustrated in <FIG>) of the receiver apparatus.

On the screen <NUM>, based on the received document table of <FIG>, the data item "unread" of the second, fourth, and fifth documents (assigned with document IDs "<NUM>," "<NUM>," and "<NUM>") from the top are marked with black solid circles representing an unread status. On the screen <NUM>, no black solid circles (representing the unread status) are in the data item "unread" of the first and third documents from the top (assigned with the document IDs "<NUM>" and "<NUM>"). The blank data item "unread" represents the read status.

The screen <NUM> includes a display document button <NUM>, a print document button <NUM>, and a delete document button <NUM>. When the user operating the receiver apparatus 12B selects, from the received document list, a received document to be viewed and presses a display document button <NUM>, the selected document is acquired from the facsimile reception server <NUM> and displayed on the control panel <NUM>.

When the user operating the receiver apparatus 12B selects, from the received document list, a received document to be viewed and presses the print document button <NUM>, the selected document is acquired from the facsimile reception server <NUM> and is printed. When the user operating the receiver apparatus 12B selects, from the received document list, a received document and presses the delete document button <NUM>, the selected document is deleted from the facsimile reception server <NUM>.

Referring to <FIG>, a description is given below of an examples in which the user operating the receiver apparatus 12B selects, from the received document list, the document having the document ID "<NUM>" and presses the display document button <NUM> on the screen <NUM>. The receiver apparatus 12B requests acquisition of the document having the document ID "<NUM>" from the facsimile reception server <NUM>, and acquires the document having the document ID "<NUM>. " The receiver apparatus 12B displays, for example, a screen <NUM> illustrated in <FIG> on the control panel <NUM>.

The screen <NUM> is an example in which an image of the document having the document ID "<NUM>" selected by the user is displayed. The screen <NUM> includes an exit button <NUM> for ending the display of the selected document. The user operating the receiver apparatus 12B presses the exit button <NUM> to end the display of the image of the selected document. Since the receiver number of the document having the document ID "<NUM>" displayed on the screen <NUM> is "<NUM>," the receiver is the apparatus 12B.

Therefore, the read/unread management unit <NUM> of the facsimile reception server <NUM> determines that the document having the document ID "<NUM>" has been viewed on the receiver apparatus 12B. Then, regarding the document ID "<NUM>" in <FIG>, the read/unread management unit <NUM> switches the data item "read flag" from "<NUM>" representing unread to "<NUM>" representing read. In addition, on the screen <NUM> of <FIG> changed from the screen <NUM>, the data item "unread" of the second document from the top (the document having the document ID "<NUM>") is changed from the solid circle representing the unread status to blank representing the read status.

For example, when the apparatus <NUM> other than the receiver apparatus 12B having the facsimile number "<NUM>" acquires the received document list illustrated in <FIG> from the facsimile reception server <NUM>, the control panel <NUM> displays the screen <NUM> illustrated in <FIG>, which is the same as the screen <NUM> illustrated in <FIG>. <FIG>, <FIG>, and <FIG> illustrate an example of screen transition on the control panel <NUM> (illustrated in <FIG>) of the receiver apparatus.

On the screen <NUM>, based on the received document table of <FIG>, the data item "unread" of the second, fourth, and fifth documents (assigned with document IDs "<NUM>," "<NUM>," and "<NUM>") from the top are marked with black solid circles representing an unread status.

Referring to <FIG>, a description is given below of an examples in which the user operating the apparatus <NUM> other than the receiver apparatus 12B selects the document having the document ID "<NUM>" from the received document list and presses the display document button <NUM> on the screen <NUM>. The apparatus <NUM> other than the receiver apparatus 12B requests acquisition of the document having the document ID "<NUM>" from the facsimile reception server <NUM>, and acquires the document having the document ID "<NUM>. " The apparatus <NUM> other than the receiver apparatus 12B displays, for example, the screen <NUM> as illustrated in <FIG> on the control panel <NUM>.

The screen <NUM> is an example in which an image of the document having the document ID "<NUM>" selected by the user is displayed. The user operating the apparatus <NUM> other than the receiver apparatus 12B presses the exit button <NUM> to end the display of the image of the selected document. Since the receiver number of the document having the document ID "<NUM>" displayed on the screen <NUM> is "<NUM>," the receiver is the apparatus 12B.

Therefore, the read/unread management unit <NUM> of the facsimile reception server <NUM> determines that the document having the document ID "<NUM>" is viewed not on the receiver apparatus 12B but on the apparatus <NUM> other than the receiver apparatus 12B. Then, the read/unread management unit <NUM> maintains "<NUM>" representing unread in the data item "read flag" of the document ID "<NUM>" in <FIG>. In addition, on the screen <NUM> of <FIG> changed from the screen <NUM>, the data item "unread" of the second document from the top (the document having the document ID "<NUM>") remains the solid circle indicating the unread status.

Although <FIG> illustrates an example of screen transition when the apparatus <NUM> other than the receiver apparatus 12B acquires the received document list of <FIG> from the facsimile reception server <NUM>, the same applies to the device <NUM> except for the screen layout.

<FIG> is a flowchart illustrating an example of operation performed by the facsimile reception server that has received a facsimile document according to the present embodiment. In step S10, the received document management unit <NUM> of the facsimile reception server <NUM> assigns a document ID to the received facsimile document. In step S12, the received document management unit <NUM> records (stores) the facsimile document assigned with the document ID as a received document in the received document memory <NUM> (a memory). Note that, the received document memory <NUM> may be provided in another server with which the facsimile reception server <NUM> performs data communication.

In step S14, the received document management unit <NUM> adds a record of information (document ID, reception date and time, sender, and receiver) of the received document stored in step S12 to the received document table as illustrated in <FIG>. In step S16, the received document management unit <NUM> sets the read flag to "<NUM>" representing unread in the record (received document information) added in step S14.

As illustrated in <FIG>, when adding a record of a received document to the received document table illustrated in <FIG>, the facsimile reception server <NUM> that has received the facsimile document sets the read flag of the record to "<NUM>" representing unread.

<FIG> is a sequence diagram illustrating an example of a process in which a user acquires, with the apparatus (e.g., a facsimile machine), a received document stored in the facsimile reception server and views the document. <FIG> illustrates an example in which the user operating the apparatus <NUM> views the received document by displaying or printing the received document.

In step S20, for example, the received document acquisition request unit <NUM> of the apparatus <NUM> that has received the operation, by the user, of displaying the received document list screen <NUM> requests the received document list, such as the received document table illustrated <FIG>, from the facsimile reception server <NUM>. The received document list providing unit <NUM> of the facsimile reception server <NUM> proceeds to step S22 and transmits, to the apparatus <NUM> of the request source, a received document list (received document list information) based on the received document list request from the apparatus <NUM>. The display control unit <NUM> of the apparatus <NUM> displays, for example, the screen <NUM> illustrated in <FIG> on the control panel <NUM> based on the received document list thus received.

For example, the user operating the apparatus <NUM> selects a received document to be viewed from the received document list of <FIG> and presses the display document button <NUM>. With this operation, the user requests download of the received document from the facsimile reception server <NUM>, specifying the document ID of the selected document and the facsimile number of the apparatus <NUM> as the request source. The user operating the apparatus <NUM> selects a received document to be viewed from the received document list of <FIG> and presses the print document button <NUM>. Thus, the user requests printing of the received document from the facsimile reception server <NUM>, specifying the document ID of the selected document and the facsimile number of the apparatus <NUM> as the request source.

In step S26, the received document list providing unit <NUM> of the facsimile reception server <NUM> transmits, to the apparatus <NUM> that has made the download request, the document having the specified document ID, based on the download request of the document from the apparatus <NUM> made in step S24. The read/unread management unit <NUM> of the facsimile reception server <NUM> controls the read/unread status of the received document thus sent.

More specifically, the read/unread management unit <NUM> determines whether the facsimile number of the request source apparatus <NUM> specified in step S24 matches the facsimile number of the receiver of the document sent in step S26. Determining that the request source facsimile number matches the receiver facsimile number, the read/unread management unit <NUM> determines that the user who should view the received document has viewed the received document, and switches the data item "read flag" to "<NUM>" representing read in the corresponding record in the received document list in <FIG>.

By contrast, determining that the facsimile number of the request source apparatus <NUM> specified in step S24 does not match the facsimile number of the receiver of the document sent in step S26, the read/unread management unit <NUM> determines that the received document has not been viewed by the user who should view the received document, and maintains "<NUM>" representing unread in the data item "read flag" of the corresponding record in the received document list in <FIG>.

The read/unread management unit <NUM> executes the read management, for example, in the procedure illustrated in <FIG> is a flowchart illustrating an example of operation performed by the facsimile reception server that has received a download request of a received document, according to the present embodiment. In the description with reference to the flowchart of <FIG>, the request source apparatus <NUM> is given a facsimile number "XXXXX," and the received document requested to be downloaded is given a document ID "Id.

In step S40, the received document list providing unit <NUM> of the facsimile reception server <NUM> searches the received document table illustrated in <FIG> for a record (received document information) including the document ID "Id" of the requested document. In step S42, the read/unread management unit <NUM> determines whether or not the facsimile number (receiver facsimile number) set in the data item "receiver" of the received document information retrieved in step S40 matches the number "XXXXX.

Based on the determination of match, the read/unread management unit <NUM> proceeds to step S44, and switches the data item "read flag" to "<NUM>" representing read in the record (received document information) including the document ID "Id" retrieved in step S40. By contrast, based on the determination of not match, the read/unread management unit <NUM> skips the process of step S44 and does not switch the data item "read flag" of the record (received document information) of the document ID "Id" retrieved in step S40 to "<NUM>" representing read.

In step S46, the received document list providing unit <NUM> retrieves the document having the document ID "Id" from the received document memory <NUM>, and transmits the document to the download request source apparatus <NUM>. As a result, in the management system <NUM> according to the present embodiment, when the received document marked as unread is viewed by the apparatus <NUM> other than the receiver apparatus <NUM>, the received document is kept in the unread status.

Returning to <FIG>, for example, when the exit button <NUM> on the screen <NUM> of <FIG> is pressed by the user, in step S28, the received document acquisition request unit <NUM> of the apparatus <NUM> requests the received document list from the facsimile reception server <NUM>.

The received document list providing unit <NUM> of the facsimile reception server <NUM> proceeds to step S30, and transmits, to the apparatus <NUM> of the request source, the received document list information based on the received document list request from the apparatus <NUM>. Based on the received document list information thus received, the display control unit <NUM> of the apparatus <NUM> displays, on the control panel <NUM>, the screen <NUM> in <FIG> presenting the received document list in which the unread status has been changed to the read status in response to, for example, transmission of the document in step S26.

<FIG> is a sequence diagram illustrating an example of a process in which a user acquires, with the device <NUM> (e.g., a smart device), a received document stored in the facsimile reception server <NUM> and views the document. <FIG> illustrates an example in which the user operating the device <NUM> views the received document by displaying the document.

In step S60, for example, the received document acquisition request unit <NUM> of the device <NUM> that has received the operation, by the user, of displaying the received document list screen <NUM> requests the received document list, such as the received document table illustrated <FIG>, from the facsimile reception server <NUM>. The received document list providing unit <NUM> of the facsimile reception server <NUM> proceeds to step S62, and transmits, to the device <NUM> of the request source, the received document list information based on the received document list request from the device <NUM>. The display control unit <NUM> of the device <NUM> displays a screen including the received document list on the display <NUM> based on the received document list information thus received.

For example, the user operating the device <NUM> selects a received document to be viewed from the received document list and performs an operation of downloading the document. With this operation, the user requests download of the received document from the facsimile reception server <NUM>, specifying the document ID of the selected document and the user account of the user who is operating the device <NUM>. That is, the download request (i.e., acquisition request) includes the document ID and user information that is the user account, in this example.

In step S66, the received document list providing unit <NUM> of the facsimile reception server <NUM> transmits, to the device <NUM> that has made the download request, the document having the specified document ID, based on the download request of the document from the device <NUM> made in step S64. The read/unread management unit <NUM> of the facsimile reception server <NUM> controls the read/unread status of the received document thus sent.

More specifically, the user account is associated with the facsimile number of the apparatus <NUM> in a user management table (association information) such as that illustrated in <FIG>. The read/unread management unit <NUM> determines whether the facsimile number associated with the user account specified in step S64 matches the facsimile number of the receiver of the document sent in step S66. Determining that the facsimile number associated with the user account matches the receiver facsimile number, the read/unread management unit <NUM> determines that the user who should view the received document has viewed the received document. The read/unread management unit <NUM> switches the data item "read flag" (data item) to "<NUM>" representing read in the record corresponding to the document transmit in S66, in the received document list in <FIG>.

<FIG> illustrates an example of the user management table. The user management table illustrated in <FIG> includes, as data items, the user account, and the facsimile number of the apparatus. The user account is an example of identification information identifying a user. The facsimile number of the apparatus is an example of identification information identifying the apparatus <NUM> associated with the user identified by the user account. The user management table of <FIG> may be stored in the management information memory <NUM> of the facsimile reception server <NUM> or may be stored in the device <NUM>. When the received document is stored in the device <NUM>, the information designated by the download request of the received document in the step S64 is the same as that in the step S24 in <FIG>. Accordingly, the process after step S64 is the same as the process after step S24 in <FIG>.

Determining that the facsimile number of the apparatus <NUM> associated with the user account (in the user management table illustrated in <FIG>) specified in step S64 does not match the facsimile number of the receiver of the document sent in step S66, the read/unread management unit <NUM> determines that the user who should view the received document has not yet viewed the received document. The read/unread management unit <NUM> does not switch the value of the data item "read flag" (data item) in the record corresponding to the document transmit in S66, in the received document list illustrated in <FIG>.

The read/unread management unit <NUM> executes the read management, for example, in the procedure illustrated in <FIG> is a flowchart illustrating an example of operation performed by the facsimile reception server that has received a download request of a received document, according to the present embodiment. In the description referring to the flowchart of <FIG>, "UserX" represents the user account of the user who is performing the request operation on the apparatus <NUM> (the user of the request source), and "Id" represents the document ID of the received document requested to be downloaded.

In step S80, the received document list providing unit <NUM> of the facsimile reception server <NUM> searches the received document table illustrated in <FIG> for a record (received document information) including the document ID "Id" of the requested document. In step S82, the received document list providing unit <NUM> searches the user management table such as that illustrated in <FIG> for the facsimile number of the apparatus <NUM> associated with the user account "UserX.

In step S84, the read/unread management unit <NUM> determines whether or not the facsimile number (receiver facsimile number) set in the data item "receiver" of the received document information retrieved in step S80 matches the facsimile number of the apparatus <NUM> associated with the user account "UserX" retrieved in step S82.

Based on the determination of match, the read/unread management unit <NUM> proceeds to step S86, and switches the data item "read flag" to "<NUM>" representing read in the record (received document information) including the document ID "Id" retrieved in step S80. By contrast, based on the determination of not match, the read/unread management unit <NUM> skips the process of step S86 and does not switch the data item "read flag" of the record (received document information) of the document ID "Id" retrieved in step S80 to "<NUM>" representing read.

In step S88, the received document list providing unit <NUM> retrieves the document having the document ID "Id" from the received document memory <NUM>, and transmits the document to the download request source device <NUM>. As a result, in the management system <NUM> according to the present embodiment, when the received document marked as unread is viewed by the device <NUM> (e.g., a smart device) other than the receiver apparatus <NUM>, the received document is kept in the unread status.

Returning to <FIG>, when the user performs an operation of ending the display of the received document, in step S68, the received document acquisition request unit <NUM> of the device <NUM> requests the received document list from the facsimile reception server <NUM>.

The received document list providing unit <NUM> of the facsimile reception server <NUM> proceeds to step S70, and transmits, to the request source device <NUM>, the received document list based on the received document list request from the device <NUM>. Based on the received document list information thus received, the display control unit <NUM> of the device <NUM> displays, on the display <NUM>, a document list screen presenting the received document information. On the document list screen, the unread status has been changed to the read status in response to, for example, transmission of the document in step S66.

The user management table illustrated in <FIG> may be automatically updated by the procedure illustrated in <FIG> and <FIG>, for example. <FIG> is a diagram illustrating an example of a process of updating the user management table, performed by the facsimile reception server <NUM>.

For example, (<NUM>) when the user has successfully logged in, (<NUM>) the authentication control unit <NUM> of the apparatus <NUM> having the facsimile number "<NUM>" makes an update request for the user management table, specifying the user account of the logged-in user and the facsimile number "<NUM>" of the apparatus <NUM>.

Receiving the update request for the user management table, the information update control unit <NUM> of the facsimile reception server <NUM> registers the user account and the facsimile number (specified by the update request from the apparatus <NUM>) in association with each other in the user management table illustrated in <FIG>, for example, according to the procedure illustrated in <FIG>.

<FIG> illustrates an example of a process of updating the user management table, performed by the facsimile reception server <NUM>. In the description referring to the flowchart illustrated in <FIG>, the logged-in user is given the user account "UserX," and the apparatus <NUM> in which the user "UserX" logs in is given the facsimile number "XXXXX.

In step S100, the information update control unit <NUM> of the facsimile reception server <NUM> searches the user management table for the facsimile number of the apparatus <NUM> corresponding to the user account "UserX.

In response to retrieval of the facsimile number of the apparatus <NUM> corresponding to user account "UserX" in the search (Yes in S102), in S104, the information update control unit <NUM> updates the value of the data item "facsimile number of apparatus" corresponding to the user account "UserX" to the number "XXXXX.

When the facsimile number of the apparatus <NUM> corresponding to user account "UserX" is not retrieved in the search (No in S102), in S106, the information update control unit <NUM> adds a record in which the user account "UserX" is associated with the number "XXXXX" to the user management table.

Referring back to <FIG>, after the user logs in to the apparatus <NUM> having the facsimile number "<NUM>," the facsimile reception server <NUM> stores the user account of the logged-in user in association with the apparatus <NUM> in which the user has logged in the user management table. Assume that the user views the received document stored in the facsimile reception server <NUM> from the device <NUM> such as the smart device, specifying the user account. In this case, when the receiver of the document is the apparatus <NUM> having the facsimile number "<NUM>," the facsimile reception server <NUM> changes the status of the document from unread to read based on the user management table illustrated in <FIG>.

Alternatively, the read/unread management unit <NUM> of the facsimile reception server <NUM> may control the read/unread status of the document as described with reference to <FIG>. <FIG> is an example of facsimile transmission and reception in the management system according to the present embodiment. <FIG> illustrates an example of a site management table. <FIG> is a flowchart illustrating an example of process performed by the facsimile reception server that has received a download request for a received document.

In the example illustrated in <FIG>, the apparatus 12B having the facsimile number "<NUM>" and the apparatus 12C having the facsimile number "<NUM>" belong to the same site (Tokyo). The apparatus 12D having the facsimile number "<NUM>" and an apparatus 12E having the facsimile number "<NUM>" belong to the same site (Osaka).

The sender apparatus 12A transmits the facsimile document to the facsimile reception server <NUM>, specifying the facsimile number "<NUM>" of the apparatus 12B as a receiver number. The receiver apparatus 12B of the facsimile document can access the facsimile reception server <NUM> and acquire the facsimile document (received document) from the facsimile reception server <NUM>.

It is assumed that each of the apparatuses 12B to 12E in <FIG> has access to the facsimile reception server <NUM>. In the case illustrated in <FIG>, the status of the document addressed to the facsimile number "<NUM>," stored in the facsimile reception server <NUM>, is changed to read when the document is downloaded to the receiver apparatus 12B having the facsimile number "<NUM>.

In the case illustrated in <FIG>, the status of the document addressed to the facsimile number "<NUM>," stored in the facsimile reception server <NUM>, is also changed to read when the document is downloaded to the apparatus 12C on the same site to which the apparatus 12B having the facsimile number "<NUM>" belongs.

On the other hand, in the case illustrated in <FIG>, the status of the document addressed to the facsimile number "<NUM>," stored in the facsimile reception server <NUM>, is not changed to read when the document is downloaded to the apparatus 12D or 12E not belonging to the same site where the apparatus 12B having the facsimile number "<NUM>" belongs.

Using the site management table illustrated in <FIG>, the read/unread management unit <NUM> determines whether or not the site of the receiver of the document to be downloaded matches the site to which the apparatus <NUM> that downloads the document belongs. The site management table illustrated in <FIG> is an example in which the facsimile number is used as the information identifying the apparatus <NUM>. The information identifying the apparatus <NUM> is not limited thereto but may be any information, such as an internet protocol (IP) address or an identifier (ID) unique to the apparatus <NUM>.

The read management process by the read/unread management unit <NUM> is executed, for example, in the procedure s illustrated in <FIG>. In the description with reference to the flowchart of <FIG>, the request source apparatus <NUM> is given the facsimile number "XXXXX," and the received document requested to be downloaded is given the document ID "Id.

In step S120, the received document list providing unit <NUM> of the facsimile reception server <NUM> searches the received document table (e.g., illustrated in <FIG>) for a record (received document information) including the document ID "Id". In step S122, the read/unread management unit <NUM> determines whether or not the facsimile number (receiver facsimile number) in the data item "receiver" of the received document information retrieved in step S120 matches the number "XXXXX.

Based on the determination of match, the read/unread management unit <NUM> proceeds to step S130, and sets the data item "read flag" to "<NUM>" representing read in the record (received document information) including the document ID "Id" retrieved in step S120.

By contrast, based on the determination of not match, the read/unread management unit <NUM> proceeds to step S124, and searches for a site corresponding to the receiver in the received document information retrieved in step S120 using the site management table illustrated in <FIG>. The site corresponding to the receiver is referred to as "Site <NUM>".

In step S126, the read/unread management unit <NUM> searches for a site corresponding to the number "XXXXX" using the site management table illustrated in <FIG>. The site corresponding to the number "XXXXX" is referred to as "Site <NUM>. " In step S218, the read/unread management unit <NUM> determines whether Site <NUM> matches Site <NUM>.

Based on the determination of match, the read/unread management unit <NUM> proceeds to step S130, and sets the data item "read flag" to "<NUM>" representing read in the record (received document information) including the document ID "Id" retrieved in step S120. By contrast, based on the determination of not match, the read/unread management unit <NUM> skips the process of step S130 and does not sets the data item "read flag" of the received document information of the document ID "Id" retrieved in step S120 to "<NUM>" representing read.

In step S132, the received document list providing unit <NUM> reads out the document having the document ID "Id" from the received document memory <NUM>, and transmits the document to the download request source apparatus <NUM>. As a result, in the management system <NUM> according to the present embodiment, the status of the received document marked as unread is changed to read also when the document is viewed by the apparatus <NUM> that is not the receiver apparatus <NUM> but belongs to the same sate to which receiver apparatus <NUM> belongs.

As described above, according to the present embodiment, the management system <NUM> permits a device other than the receiver apparatus <NUM> to view (acquire) the received document and appropriately manages the read/unread status of the document.

A description is given of a second embodiment. In the second embodiment, in a case where a user who should view a received document (stored in the facsimile reception server <NUM>) has viewed the document by the apparatus <NUM> other than the receiver apparatus <NUM>, the facsimile reception server <NUM> changes the read/unread states of the document to read. In the description of the second embodiment below, descriptions of the configuration same as that of the first embodiment are omitted.

<FIG> is an example of facsimile transmission and reception in the management system according to the present embodiment. <FIG> illustrates, as examples of the apparatus and the device that can acquire the received document, the apparatus 12B having the facsimile number "<NUM>," the apparatus 12C having the facsimile number "<NUM>," and the apparatus 12D having the facsimile number "<NUM>.

In addition, the apparatuses 12C and 12D in <FIG> can access the facsimile reception server <NUM> and acquire the document addressed to the facsimile number "<NUM>" from the facsimile reception server <NUM>.

In the case of <FIG>, the facsimile reception server <NUM> determines whether to change the read/unread status of the document addressed to the facsimile number "<NUM>" from the unread status to the read status based on the facsimile number of the apparatus <NUM> accessing the facsimile reception server <NUM>, the organization to which the accessing user belongs, and the owner organization to which the accessing apparatus <NUM> belongs.

<FIG> illustrates an example of a management table associating a user, an organization (e.g., department), an owner organization of the accessing apparatus <NUM>, and a facsimile number with each other. The management table illustrated in <FIG> includes, as data items, a user ID, a department an organization owning the apparatus <NUM>, and a facsimile number.

The user ID is an example of identification information identifying a user. The department (department name) is an example of identification information identifying an organization or group to which the user belongs. The organization (department name) owning the apparatus is an example of identification information identifying the organization owning the apparatus <NUM>. The facsimile number is an example of identification information identifying the apparatus <NUM>.

For example, in the case of the management table illustrated in <FIG>, the site to which the apparatus 12B (Omori <NUM>) illustrated in <FIG> belongs is "Omori," and the owner organization is "design A". The site to which the apparatus 12C (Ginze <NUM>) belongs is "Ginza," and the apparatus 12C is shared by the organizations "design A" and "design B. " The site to which the apparatus 12D (Ebina <NUM>) belongs is "Ebina," and the apparatus 12D is owned by "design B.

For example, when a received document stored in the facsimile reception server <NUM> is viewed from the apparatus <NUM>, the organization owning the accessing apparatus <NUM> is determined based on the organization owning the apparatus <NUM> associated with the user ID of the accessing user in the management table illustrated in <FIG>.

In the example illustrated in <FIG>, assume that a user A accesses the document addressed to the apparatus 12B (Omori <NUM>) installed in the site "Omori" from the apparatus 12D (Ebina <NUM>) installed in the site "Ebina. " In this case, the owner organization "design A" owning the apparatus 12B matches "design A" to which the user A belongs. Accordingly, the document is set to the read status.

In the example illustrated in <FIG>, assume that a user B accesses the document addressed to the apparatus 12B (Omori <NUM>) installed in the site "Omori" from the apparatus 12D (Ebina <NUM>) installed in the site "Ebina. " In this case, the owner organization "design A" owning the apparatus 12B does not match "design B" to which the user B belongs. Accordingly, the document is kept in the unread status.

In the example illustrated in <FIG>, assume that the user A accesses the document addressed to the apparatus 12C (Ginza <NUM>) installed in the site "Ginza" from the apparatus 12D (Ebina <NUM>) installed in the site "Ebina. " In this case, the apparatus 12C is shared by "design A" and "design B," that is, the owner organizations include "design A" to which the user A belongs. Accordingly, the document is set to the read status.

A description is given below of a modification of the above-described embodiments.

In the above-described embodiments, descriptions are given of examples in which the facsimile reception server <NUM> stores the received facsimile data and transmits the received facsimile data based on the request from the apparatus <NUM> or the device <NUM>. Alternatively, aspects of the present disclosure are applicable to a system in which the apparatus <NUM> transfers a received document to a management apparatus and performs read/unread management. In such a system, the management apparatus may cause the apparatus <NUM> or the device <NUM> to download the received document and execute read/unread management of the received document.

Claim 1:
A server (<NUM>) for controlling a status of a document transmitted by facsimile from a sender apparatus (<NUM>) to a receiver apparatus (<NUM>) that performs facsimile transmission and reception, the server comprising:
a document providing unit (<NUM>) configured to provide, to a request source apparatus (<NUM>; <NUM>), the document in response to receiving an acquisition request specifying the document, transmitted from the request source apparatus, wherein the request source apparatus is one of the receiver apparatus (<NUM>), to which the document is addressed by the sender apparatus, or a different apparatus (<NUM>; <NUM>) from the receiver apparatus (<NUM>); and
a read management unit (<NUM>) configured to control a status change, from unread to read, of the document specified by the acquisition request based on information on the request source apparatus and information on the receiver apparatus (<NUM>) of the document;
wherein the document providing unit (<NUM>) provides the request source apparatus with list information on the document, the list information including information indicating whether the document is in the read status or in the unread status, such that the request source apparatus can display the list information to a user,
and wherein: the read management unit (<NUM>) sets, to the read status, the document specified by the acquisition request based on a determination that the information on the request source apparatus matches the information on the receiver apparatus (<NUM>) of the document specified by the acquisition request;
and the read management unit (<NUM>) maintains, in the unread status, the document specified by the acquisition request based on a determination that the information on the request source apparatus does not match the information on the receiver apparatus (<NUM>) of the document specified by the acquisition request.