Image communication device, control method for image communication device, communication system, and control method for communication system
The system addresses the lack of clear reply confirmation in image communication by displaying thumbnail images with identification information, facilitating efficient management and tracking of image operations through a timeline UI.
Patent Information
- Application Number
- JP2024114182
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-07-17
- Publication Date
- 2025-09-05
- Estimated Expiration
- 2040-07-17
AI Technical Summary
Existing image communication systems, such as facsimile devices, do not provide clear confirmation that a reply has been sent to a received image.
A system comprising an image communication device, a server device, and a terminal device that acquires and displays a thumbnail image along with identification information to explicitly show that a reply has been sent, using a server to manage and update the status of received images and their operations.
Enables explicit display of a sent reply, allowing users to track and manage image communication operations efficiently through a timeline-style UI, preventing duplicate replies and ensuring timely updates across a group.
Smart Images

Figure 0007734802000001 
Figure 0007734802000002 
Figure 0007734802000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to an image communication device and the like. [Background technology]
[0002] 2. Description of the Related Art Conventionally, there has been known an invention for notifying a user of a facsimile, which is one type of image communication apparatus, of the reception of a facsimile.
[0003] For example, a technology has been proposed for an image forming device that creates a notification message notifying that a facsimile has been received and sends it to the notification destination, where the notification message includes a URL (Uniform Resource Locator) for displaying a preview of the facsimile data and a form that allows the user to specify processing for the facsimile data (see, for example, Patent Document 1). [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent Publication No. 2008-160531 Summary of the Invention [Problem to be solved by the invention]
[0005] However, the technique described in Patent Document 1 has a problem in that it is not possible to explicitly confirm that a reply has been sent.
[0006] In view of the above-mentioned problems, the present application has an object to provide a terminal device or the like that clearly displays that a reply has been sent to an image received by an image communication device. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems, the first embodiment of the present disclosure includes: an acquisition unit that acquires a received image received by an image communication device that transmits and receives an image and information that can identify the received image that has been returned; a display control unit that controls displaying a thumbnail image based on the received image and displaying identification information together with the thumbnail image based on the returned received image; The terminal device is characterized by comprising:
[0008] A second embodiment of the present disclosure comprises: A system including an image communication device that transmits and receives images, a server device that can communicate with the image communication device, and a terminal device that can communicate with the server device, The server device a management section for managing received images received by the image communication device and information capable of identifying the received images that have been returned; Equipped with The terminal device an acquisition unit that acquires information that can identify the received image and the returned image from the server device; a display control unit that controls displaying a thumbnail image based on the received image and displaying identification information together with the thumbnail image based on the returned received image; The system is characterized by comprising:
[0009] A third embodiment of the present disclosure comprises: acquiring a received image received by an image communication device that transmits and receives an image and information that can identify the received image that has been returned; a step of controlling to display a thumbnail image based on the received image and to display identification information together with the thumbnail image based on the returned received image; The display method is characterized by comprising:
[0010] A fourth embodiment of the present disclosure is On the computer, a function of acquiring a received image received by an image communication device that transmits and receives images and information that can identify the received image that has been returned; a function of controlling display of a thumbnail image based on the received image and displaying identification information together with the thumbnail image based on the returned received image; It is a program characterized by realizing the above. [Effects of the Invention]
[0011] According to the present disclosure, as one example, it is possible to explicitly display that a reply has been sent to a received image. [Brief explanation of the drawings]
[0012] [Figure 1] FIG. 1 is a diagram for explaining the overall configuration of a system in a first embodiment. [Figure 2] FIG. 1 is a diagram illustrating an overview of a system according to a first embodiment. [Figure 3] FIG. 2 is a diagram illustrating the functional configuration of an image communication apparatus according to the first embodiment. [Figure 4] FIG. 2 is a diagram illustrating a functional configuration of a server device according to the first embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of a data configuration of timeline data in the first embodiment. [Figure 6] FIG. 3 is a diagram illustrating an example of a data configuration of group information in the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating the functional configuration of a terminal device according to the first embodiment. [Figure 8] FIG. 4 is a diagram for explaining processing of a terminal device in the first embodiment. [Figure 9] FIG. 4 is a diagram for explaining a timeline display process in the first embodiment. [Figure 10] FIG. 4 is a diagram for explaining processing of the server device in the first embodiment. [Figure 11] FIG. 2 is a diagram for explaining an example of operation in the first embodiment. [Figure 12] FIG. 2 is a diagram for explaining an example of operation in the first embodiment. [Figure 13] FIG. 2 is a diagram for explaining an example of operation in the first embodiment. [Figure 14] FIG. 2 is a diagram for explaining an example of operation in the first embodiment. [Figure 15] FIG. 2 is a diagram for explaining an example of operation in the first embodiment. [Figure 16] FIG. 2 is a diagram for explaining an example of operation in the first embodiment. [Figure 17] FIG. 10 is a diagram for explaining processing of a server device in the second embodiment. [Figure 18] FIG. 10 is a diagram for explaining an example of operation in the second embodiment. [Figure 19] FIG. 11 is a diagram for explaining processing of a terminal device in the third embodiment. [Figure 20] FIG. 10 is a diagram for explaining an operation example in the third embodiment. [Figure 21] FIG. 10 is a diagram for explaining an operation example in the third embodiment. [Figure 22] FIG. 10 is a diagram for explaining an operation example in the third embodiment. [Figure 23] FIG. 10 is a diagram for explaining an example of operation in the fourth embodiment. [Figure 24] FIG. 13 is a diagram for explaining an example of operation in the fifth embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the embodiments, a system including a terminal device to which the present invention is applied will be described as an example.
[0014] [1. First embodiment] [1.1 Overall Description] [1.1.1 Overall Structure] 1 is a diagram illustrating the entire system 1. In the system 1, an image communication device 10, a server device 20, and a terminal device 30 are connected via a network NW1.
[0015] The image communication apparatus 10 is an apparatus having at least a facsimile (FAX / facsimile) function. The image communication apparatus 10 may be installed in an image forming apparatus such as a digital multifunction peripheral / printer (MFP), or may be a standalone apparatus. The image communication apparatus 10 can also be connected to a telephone line network NW2, such as an analog line or a digital line (ISDN).
[0016] The server device 20 is a device that provides a predetermined service (for example, an IoT platform), and is installed, for example, on a cloud. In this embodiment, the server device 20 manages a group made up of the image communication device 10 and one or more users who use the image communication device, and provides a service that allows information about images received by the image communication device 10 to be shared among the users belonging to the group.
[0017] The terminal device 30 is a device used by a user, and is, for example, an information processing device configured by a mobile terminal such as a smartphone or a tablet, or a personal computer (PC).
[0018] The network NW1 is a network that connects the various devices and is realized by, for example, a local area network (LAN) or a wide area network (WAN). Alternatively, the network NW1 may be configured by combining these networks.
[0019] In this specification, "receiving a fax," "receiving a fax," and "fax reception" refer to receiving an image based on a standard using facsimile communication. "sending a fax," "sending a fax," and "sending a fax" refer to sending an image based on a standard using facsimile communication. Facsimile communication is an electrical communication method for sending and receiving images that include text and graphics, and the transmission path used for facsimile communication is called a facsimile communication network.
[0020] [1.1.2 System Operation Overview] Next, an overview of the operation of the system 1 will be described with reference to Fig. 2. In Fig. 2, user A is a user who sends a fax to the image communication device 10 using a device with a facsimile function. A device that sends a fax to the image communication device 10 is called a sending device. Also in Fig. 2, user B is a user of a service provided by the server device 20, and is a user who belongs to the same group as the group to which the image communication device 10 belongs.
[0021] First, with reference to Fig. 2(a), a case where the image communication device 10 receives a FAX will be described. User A uses a transmission source device to send a FAX to the image communication device 10. As a result, an image is sent from the transmission source device to the image communication device 10.
[0022] The image communication apparatus 10 receives an image from a transmission source apparatus. In this embodiment, an image (FAX data) received by the image communication apparatus 10 from a transmission source apparatus is referred to as a "received image."
[0023] The image communication device 10 transmits received data including the received image and information about the received image to the server device 20. The information about the received image is, for example, information about the transmission source device extracted from the received image (for example, the FAX number of the transmission source device, etc.).
[0024] The server device 20 authenticates the image communication device 10 and receives received data from the image communication device 10. The server device 20 manages (stores) the received images so that the received images can be acquired by a device used by user B (for example, terminal device 30).
[0025] The terminal device 30 acquires the received image from the server device 20, displays a notification (reception notification) indicating that the image communication device 10 has received a FAX, and displays the received image. This allows user B to check the received image without printing it, or to download it to the terminal device 30. In this way, the received image is transferred (transmitted) to the server device 20 by the image communication device 10, and is acquired by the terminal device 30 via the server device 20. Therefore, by connecting the terminal device 30 to the server device 20, user B can timely check the receipt of the received image regardless of his or her location, such as at his or her desk or while out and about.
[0026] User B may download the received images from server device 20 to a device other than terminal device 30 (for example, a mobile terminal or a personal computer). User B may also check data such as the received images and print only the necessary images from the received images using a device such as a printer. The printer may obtain the received images from server device 20, or may obtain them from the device that downloaded the received images (for example, terminal device 30).
[0027] Furthermore, the server device 20 manages (stores) information indicating the operation (action) performed on the received image and the status of the received image (for example, status information such as whether a reply has been sent) in association with the received image, and makes the information available to the terminal device 30. The terminal device 30 displays the information associated with the received image, thereby making it possible to share the operation performed on the received image and the status of the received image with users (multiple users) in the group to which the image communication device 10 belongs. Therefore, a user who wishes to obtain information about the image communication device 10 only needs to belong to the same group to which the image communication device 10 belongs in the service provided by the server device 20.
[0028] In this embodiment, as an operation on a received image, an operation of sending a predetermined image corresponding to the received image (for example, an image indicating that a FAX has been received) to the device that sent the received image is called a "reply." Also, in this embodiment, an image sent to the device that sent the received image by the reply operation is called a "reply image."
[0029] The server device 20 may manage the received images for a certain period of time, thereby enabling the user to check past data (received images) and perform operations on the past data (received images).
[0030] Furthermore, the terminal device 30 displays the received images and the operations performed on the received images as a timeline-style UI (User Interface), and enables the user to operate the received images from the timeline-style UI. This allows the user to check the received images and operate the received images with simple operations by operating the timeline-style UI.
[0031] Next, referring to Figure 2(b), we will explain the case where a user sends a reply. After User B checks the received image, he or she can immediately send a reply FAX to the sending device (the destination for User B) to inform that the FAX has been received.
[0032] User B selects a received image to be returned and transmits a request for a return to server device 20. When server device 20 receives the request for a return, it authenticates the user who sent the request and then generates return data including at least the return image and information about the device that transmitted the received image. The information about the device that transmitted the received image is the destination of the return image when the return is made.
[0033] For example, the server device 20 generates a reply image based on a preset template. The server device 20 also sets information about the destination (sender device) of the reply image based on the information about the sender device transmitted from the image communication device 10 together with the received image.
[0034] User B can edit the reply data. For example, User B can edit the information of the sending device, or select or input an original comment (comment of the reply data) to be added to the reply image. Furthermore, when User B is ready to send a reply image to User A, User B transmits a request to server device 20 to execute the reply.
[0035] When user B requests that a reply be made, server device 20 transmits reply data to image communication device 10. Image communication device 10 transmits the reply image contained in the reply data by fax to the sender device based on the sender device information contained in the reply data. As a result, the sender device of the received image that is the target of the reply receives the fax from image communication device 10 and outputs the reply image. User A can check the reply image.
[0036] When the server device 20 has successfully transmitted the reply image to the transmission source device, it updates the status of the received image that was the subject of the reply to "Replied." This allows users who belong to the same group as the user who sent the reply to share information about the received image that is in the replied state.
[0037] Furthermore, when replying again to a received image whose status is "replied", the terminal device 30 checks the message to prevent duplicate reply operations.
[0038] [1.2 Functional Configuration] [1.2.1 Image communication equipment] The functional configuration of the image communication device 10 will be described with reference to Fig. 3. As shown in Fig. 3, the image communication device 10 is configured to include a control unit 100, an image reading unit 120, an image forming unit 130, a display unit 140, an input unit 150, a storage unit 160, a line communication unit 170, and a NW communication unit 180.
[0039] The control unit 100 is a functional unit for controlling the entire image communication device 10. The control unit 100 realizes various functions by reading and executing various programs stored in the storage unit 160, and is configured by one or more arithmetic units (e.g., CPUs (Central Processing Units)).
[0040] The control unit 100 executes a program to function as a FAX control unit 102, an image processing unit 104, a receiving processing unit 106, and a transmitting processing unit 108.
[0041] The FAX control unit 102 transmits and receives FAXes. For example, the FAX control unit 102 transmits an image of a document read by the image reading unit 120 to another device via a telephone line from the line communication unit 170. In addition, in the case of Internet FAX, the FAX control unit 102 transmits the image to another device via the Internet from the NW communication unit 180.
[0042] That is, the FAX control unit 102 transmits and receives images to and from other devices by performing facsimile communication using the normal G3 / G4 standard or the like, or by performing facsimile communication using InternetFAX. The FAX control unit 102 may perform facsimile communication using any known standard or protocol.
[0043] Furthermore, the FAX control unit 102 receives an image based on a facsimile communication signal via the line communication unit 170 or the NW communication unit 180. The FAX control unit 102 stores the received image, which is the image data that has been received, in the image data storage area 162 as image data.
[0044] The image data is, for example, a Portable Document Format (PDF) file. Note that the image data may also be a file in a Tagged Image File Format (TIFF) format, a Joint Photographic Experts Group (JPEG) format, or the like. When receiving multiple images at once, the FAX control unit 102 may store the received images on different pages, and store the image data consisting of multiple pages in the image data storage area 162.
[0045] The image processing unit 104 performs various image-related processes, such as sharpening and tone conversion processes on the image read from the image reading unit 120.
[0046] When a FAX is received by the FAX control unit 102, the reception processing unit 106 generates received data including image data in which the received image is stored and information about the received image. The reception processing unit 106 transmits the received data and the authentication information stored as authentication information 164 to the server device 20 via the NW communication unit 180.
[0047] The information relating to the received image is, for example, the following information: Note that all or any of the following information may be included. Received date and time Number of received pages Image data capacity - Information about the source device
[0048] The information about the sending device is information included in the protocol for facsimile communication, a telephone number notified by a sending telephone number notification service, information set in the sending device, etc. For example, in the case of the G3 protocol, the receiving processor 106 acquires a transmitting subscriber identification (TSI) and uses it as information about the sending device. Note that the receiving processor 106 may extract information about the sending device from the received image by recognizing the received image.
[0049] The transmission processing unit 108 receives reply data from the server device 20 via the NW communication unit 180. Furthermore, when the transmission processing unit 108 receives the reply data, it controls the FAX control unit 102 to transmit a reply image included in the reply data to the sending device based on the information about the sending device included in the reply data.
[0050] The image reading unit 120 reads an original document and outputs image data. For example, the image reading unit 120 uses a CCD scanner to read an original document placed on a table of the image communication device 10 and outputs the image. The image reading unit 120 stores the image in the storage unit 160. The image reading unit 120 is configured by, for example, a scanner device, but may also read images stored in, for example, a USB memory.
[0051] The image forming unit 130 forms an image on, for example, a recording sheet. That is, an image is printed on the recording sheet by the image forming unit 130. The image forming unit 130 is configured by, for example, a laser printer unit or the like.
[0052] The display unit 140 is a functional unit for displaying various types of information and is configured, for example, by an LCD (Liquid Crystal Display). The input unit 150 is a functional unit for receiving operations from a user of the image communication device 10. The input unit 150 is configured, for example, by a touch panel. The method for detecting input on the touch panel may be any common detection method, such as a resistive film method, an infrared method, an electromagnetic induction method, or a capacitive method. The input unit 150 may be a hardware key, or may be configured by a touch panel and a hardware key.
[0053] The storage unit 160 is a functional unit that stores various programs and various data required for the operation of the image communication apparatus 10. The storage unit 160 is configured by, for example, a semiconductor memory such as an SSD (Solid State Drive) or an HDD (Hard Disk Drive).
[0054] The storage unit 160 secures an image data storage area 162 and stores authentication information 164. The authentication information 164 stores a device ID, a password, and the like required for authentication when using a service provided by the server device 20. The device ID is an ID for identifying a device that uses a service provided by the server device 20.
[0055] The line communication unit 170 is a functional unit that can communicate with a telephone line and communicates with other devices via the telephone line.
[0056] The NW communication unit 180 is a functional unit that connects to, for example, a LAN (Local Area Network) and transmits and receives information and images to and from other devices. The NW communication unit 180 uses a LAN, which is Ethernet (registered trademark), or a communication method such as LTE (Long Term Evolution), 4G, or 5G.
[0057] [1.2.2 Server device] The functional configuration of the server device 20 will be described with reference to Fig. 4. The server device 20 includes a control unit 200, a NW communication unit 210, and a storage unit 220, as shown in Fig. 4.
[0058] The control unit 200 is a functional unit for controlling the entire server device 20. The control unit 200 realizes various functions by reading and executing various programs stored in the storage unit 220, and is configured by one or more arithmetic units (e.g., CPUs).
[0059] The control unit 200 executes a program to function as a timeline data processing unit 202, a received data processing unit 204, and an authentication processing unit 206.
[0060] The timeline data processing unit 202 performs processing related to timeline data. Timeline data refers to data for displaying information about received images, such as received images and the details of operations performed on the received images, in a timeline format. The timeline data processing unit 202 performs processing for transmitting and storing the timeline data.
[0061] When the timeline data processing unit 202 receives a request to acquire timeline data from the terminal device 30, it transmits the timeline data stored in the timeline data storage area 222 to the terminal device 30 that sent the request. For example, the timeline data processing unit 202 transmits timeline data in which the group ID of a group to which a user authenticated by the authentication processing unit 206 belongs is specified as the posting destination to the terminal device 30 that sent the request to acquire timeline data. The timeline data processing unit 202 acquires the group ID of the group to which the user belongs by reading, from the group information storage area 232, group information in which the user ID is stored, and reading the group ID stored in the read group information. Furthermore, when the timeline data processing unit 202 receives a request to acquire image data from the terminal device 30, it reads the corresponding image data from the image data storage area 354 and transmits the image data to the terminal device 30.
[0062] The timeline data processing unit 202 may notify the terminal device 30 when timeline data is generated or updated, and prompt the terminal device 30 to acquire the timeline data. The timeline data processing unit 202 may also transmit the timeline data by a push method. In this way, the terminal device 30 can acquire the latest timeline data in real time.
[0063] When the timeline data processing unit 202 receives a request from the terminal device 30 to post a message in response to a received image, the timeline data processing unit 202 stores timeline data based on information included in the request to post in the timeline data storage area 222. For example, the timeline data processing unit 202 stores timeline data in which predetermined information such as date and time is added to the information included in the request to post (e.g., message, title, poster user ID, destination group ID, image ID), and the message type is set to "user message." Note that "posting" refers to a user sending a message to the server device 20 via the terminal device 30. Also, a "message" refers to specific content (e.g., text data) to be displayed on the terminal device 30.
[0064] The received data processing unit 204 receives received data from the image communication device 10 and generates timeline data relating to the received image.
[0065] Specifically, the received data processing unit 204 executes the following processing to generate timeline data. (1) Image data storage The received data processing unit 204 stores the image data included in the received data in the image data storage area 224 .
[0066] (2) Image ID generation The received data processing unit 204 generates an image ID that uniquely identifies the received image (image data). The image ID may be a sequential number, a code in a predetermined format, a hash value of the image data, a UUID (Universally Unique Identifier), or the like.
[0067] (3) Acquisition of the group ID to which the image communication device 10 belongs The received data processing unit 204 acquires the group ID of the group to which the image communication device 10 that transmitted the received image belongs. For example, the received data processing unit 204 reads out group information in which the device ID included in the authentication information transmitted from the image communication device 10 is stored from the group information storage area 232. The received data processing unit 204 sets the group ID stored in the read group information as the group ID to which the image communication device 10 belongs.
[0068] (4) Generating timeline data The received data processing unit 204 generates timeline data related to the received image and stores it in the timeline data storage area 222. For example, the received data processing unit 204 generates timeline data by including information about the received image in a message, setting the date and time of receiving the received data from the image communication device 10 or the date and time of receiving the received image as the date and time, and using information about the sending device as the sender. Here, the received data processing unit 204 includes in the timeline data the file name of the image data stored in (1), the image ID generated in (2), and the group ID acquired in (3). Furthermore, the received data processing unit 204 sets the poster user ID to be included in the timeline data as the ID indicating the server device 20, the message type as "received message," and the reply status as "no reply."
[0069] The authentication processing unit 206 authenticates users and devices that use services provided by the server device 20. For example, when the authentication processing unit 206 receives a request to acquire or post timeline data from the terminal device 30, it authenticates the user based on authentication information transmitted along with the request. If the authentication processing unit 206 can authenticate the image communication device 10, it permits the timeline data processing unit 202 to execute a predetermined process. Similarly, the authentication processing unit 206 authenticates the image communication device 10 based on authentication information transmitted along with received data from the image communication device 10. If the authentication processing unit 206 can authenticate the image communication device 10, it permits the received data processing unit 204 to execute generation of timeline data.
[0070] The authentication processing unit 206 searches the authentication information storage area 226 for authentication information that stores the same information as the authentication information transmitted from the terminal device 30 or the image communication device 10. If the authentication information is found, the authentication processing unit 206 authenticates the terminal device 30 or the image communication device 10.
[0071] The NW communication unit 210 is a functional unit that connects to, for example, a LAN (Local Area Network) and transmits and receives information to and from other devices. The NW communication unit 210 uses a LAN such as Ethernet (registered trademark) or a communication method such as LTE (Long Term Evolution) / 4G / 5G.
[0072] The storage unit 220 is a functional unit that stores various programs and various data required for the operation of the server device 20. The storage unit 350 is configured by, for example, an SSD or HDD, which is a semiconductor memory.
[0073] In the storage unit 220, a timeline data storage area 222, an image data storage area 224, an authentication information storage area 226, a user information storage area 228, a device information storage area 230, and a group information storage area 232 are secured.
[0074] The timeline data storage area 222 is an area for storing timeline data. As shown in FIG. 5, the timeline data may include, for example, a poster user ID (e.g., “faxreceived”) indicating the user who posted the message, a destination group ID (e.g., “grp1”) indicating the group to which the message was posted, the date and time of the message (e.g., “November 6, 2019, 9:17:39”), the message title (e.g., “A new fax has been received”), the message (e.g., “Fax number 091434···”), the image ID (e.g., “1”), the image data in which the received image is stored (e.g., “FAX_201911060917_091434.pdf”), the sender of the received image (e.g., “091434”), the user ID indicating the user who will be replying, the message type (e.g., “Received message”), a reply status (e.g., “Replied”) indicating whether a reply image corresponding to the received image has been sent, and an edit status (e.g., “Edited”) indicating whether the message has been edited.
[0075] When a message is posted by a user, the user ID of the user who posted the message is stored as the poster user ID. When timeline data is generated by server device 20, a predetermined ID (e.g., "faxreceived") indicating server device 20 is stored as the poster user ID.
[0076] The date and time is information on the date and time that serves as a reference when sorting the timeline data in chronological order. The date and time may be, for example, the date and time when a request to post a message was sent or the date and time when the message was created.
[0077] The sender stores the sender's fax number, etc. The image data stores information (for example, a file name) that identifies the image data stored in the image data storage area 224. Note that the image data may be included in the timeline data.
[0078] The message type is information indicating the type of message content. For example, the following information is stored as the message type: Received messages A message indicating that a fax has been received. The message may include, for example, the fax number of the sending device, the date and time of reception, the number of received pages, and the file name of the image data. The message may also include content that explicitly indicates that a fax has been received (for example, text data such as "A fax has been received") or content that prompts the user to reply (for example, text data such as "Do you want to reply to the received fax?"). The content that explicitly indicates that a fax has been received may be included in the title of the timeline data. Reply working message A reply operation message that indicates inquiries about the reply data to the user performing the reply operation. The message includes content that prompts the user to confirm or edit the reply data. Specifically, the message includes content that prompts the user to enter a comment to be added to the reply image, and content that prompts the user to confirm or edit information about the sender device of the received image that is the target of the reply (the destination to which the reply image is sent). System Messages A message generated by the server device 20 to notify the user of the status of the reply operation. The message includes the status of the operation on the received image and the result of the reply operation. User messages Messages posted by users. Messages contain content posted by users.
[0079] In addition, the user ID of the user who performs the reply operation is stored in the timeline data whose message type is a reply operation message.
[0080] The reply status is stored in the timeline data whose message type is "received message." If no reply has been made to the image data (received image) stored in the timeline data, "no reply" is stored as the reply status, and if a reply has been made, "reply completed" is stored.
[0081] In this way, in the timeline data whose message type is "received message," a received image is associated with whether or not the received image has been replied to. A device (e.g., terminal device 30) that has acquired the timeline data can determine whether or not a received image has been replied to, based on the timeline data whose message type is "received message."
[0082] The authentication information storage area 226 stores information (authentication information) required to authenticate users and devices that use services provided by the server device 20. The authentication information stores a user ID that uniquely identifies a user or a device ID that uniquely identifies a device, and a password in association with each other.
[0083] The user information storage area 228 stores information (user information) about users who use the services provided by the server device 20. The user information stores a user ID, a user name, an icon representing the user, and the like that can uniquely identify the user.
[0084] The device information storage area 230 stores information (device information) about devices (e.g., the image communication device 10) that use the services provided by the server device 20. The device information stores a device ID that can uniquely identify the device, a device name, an icon that indicates the device, and the like.
[0085] The group information storage area 232 stores information (group information) about groups managed by the server device 20. As shown in Fig. 6, the group information stores a group ID (e.g., "grp1") that uniquely identifies a group, a device ID (e.g., "MFP1") that indicates a device belonging to the group, and a user ID (e.g., "yokomitsu, hiroaki") that indicates a user belonging to the group.
[0086] 1.2.3 Terminal Devices The functional configuration of the terminal device 30 will be described with reference to Fig. 7. The terminal device 30 includes a control unit 300, a display unit 320, an input unit 330, a NW communication unit 340, and a storage unit 350, as shown in Fig. 7.
[0087] The control unit 300 is a functional unit for controlling the entire terminal device 30. The control unit 300 realizes various functions by reading and executing various programs stored in the storage unit 350, and is configured by one or more arithmetic units (e.g., CPUs).
[0088] The control unit 300 executes a program to function as a timeline data acquisition unit 302, a posting processing unit 304, and a notification display control unit 306.
[0089] The timeline data acquisition unit 302 acquires timeline data by transmitting a request to acquire timeline data to the server device 20 together with the authentication information stored as authentication information 356. The timeline data acquisition unit 302 also stores the acquired timeline data in the timeline data storage area 352. If the timeline data includes image data, the timeline data acquisition unit 302 transmits a request to acquire the image data to the server device 20. When the timeline data acquisition unit 302 acquires image data from the server device 20, it stores the image data in the image data storage area 354.
[0090] The posting processor 304 posts a message by transmitting to the server device 20 a request to post a message for the received image together with the authentication information stored as the authentication information 356. In this embodiment, the message to be posted is a message related to a specific received image, and the posting processor 304 prompts the user to select a received image related to the message. The posting processor 304 reads timeline data in which image data corresponding to the received image selected by the user is stored from the timeline data storage area 352, and acquires a destination group ID and an image ID. The posting processor 304 includes in the posting request the message and title entered by the user, the user ID of the user (poster) using the terminal device 30, the group ID (destination group ID) and image ID acquired from the timeline data, and the like. As a result, the posting processor 304 can transmit to the server device 20 a request to post a message to users in the group to which the image communication device 10 that received the received image belongs.
[0091] The notification display control unit 306 displays a pop-up screen or a toast containing predetermined notification content on the display unit 320.
[0092] The display unit 320 is a functional unit for displaying various types of information and is configured, for example, by an LCD. The input unit 330 is a functional unit for receiving operations from a user of the terminal device 30. The input unit 330 is configured, for example, by a touch panel. The method for detecting input on the touch panel may be any common detection method, such as a resistive film method, an infrared method, an electromagnetic induction method, or a capacitive method. The input unit 330 may be a hardware key, or may be configured by a touch panel and a hardware key.
[0093] The NW communication unit 340 is a functional unit that connects to, for example, a LAN and transmits and receives information to and from other devices.
[0094] The storage unit 350 is a functional unit that stores various programs and various data required for the operation of the terminal device 30. The storage unit 350 is configured, for example, by an SSD or the like, which is a semiconductor memory.
[0095] The storage unit 350 has a timeline data storage area 352 for storing timeline data, an image data storage area 354 for storing image data, and authentication information 356 stored therein.
[0096] The authentication information 356 stores a user ID, a password, etc., which are required for authentication when using a service provided by the server device 20. The user ID is an ID for identifying a user who uses a service provided by the server device 20.
[0097] [1.3 Processing flow] The main processing flow of this embodiment will be described. First, the processing of the terminal device 30 will be described with reference to Fig. 8. Note that when the terminal device 30 transmits a request or information to the server device 20, the authentication information stored as the authentication information 356 is also transmitted, and authentication is performed by the server device 20. In the description of the processing flow, for simplicity, a description of authentication will be omitted.
[0098] 1.3.1 Terminal Devices The processing of the terminal device 30 will be described with reference to Fig. 8. First, the control unit 300 (timeline data acquisition unit 302) acquires timeline data from the server device 20 (step S102).
[0099] Next, when a new fax is received, the control unit 300 (notification display control unit 306) displays a notification of new arrivals (reception notification) of the received data (received image) (step S104). For example, the control unit 300 determines that a new fax has been received when the latest timeline data acquired in step S102 includes timeline data whose message type is "received message." At this time, as a notification of new arrivals (reception notification) of the received data, the control unit 300 (notification display control unit 306) displays a toast or a pop-up screen indicating that a fax has been received. Note that the control unit 300 may notify the user that a fax has been received by displaying a badge on an icon selected by the user to display the timeline.
[0100] Next, the control unit 300 executes a timeline display process (step S106). The timeline display process is a process for displaying a timeline based on timeline data. The timeline display process will be described with reference to FIG.
[0101] The control unit 300 reads the timeline data stored in the timeline data storage area 352 (step S132).
[0102] Next, the control unit 300 arranges the read timeline data in chronological order and displays the messages stored in the timeline data for each piece of timeline data, thereby displaying the timeline on the display unit 320 (step S134). The control unit 300 may also display information included in the timeline data along with the messages. For example, the control unit 300 may display the poster's user ID, date and time, title, etc., or, if the editing status is "edited," may display the words "edited." Furthermore, the control unit 300 may obtain user information (user name and icon indicating the user) corresponding to the user ID from the server device 20 and display the user name and icon indicating the user.
[0103] Furthermore, for timeline data whose message type is "received message," the control unit 300 displays information to be displayed on the timeline in addition to the message displayed in step S134. The additional information to be displayed is a thumbnail image of the received image, a stamp indicating that a reply has been made, and a reply button for accepting a request for a reply. This will be explained below.
[0104] The control unit 300 displays thumbnail images of received images stored in the timeline data whose message type is "received message" on the display unit 320 (step S136). The thumbnail image is an image generated based on the received image, and is, for example, an image obtained by reducing one page of the received image (for example, the first page). The thumbnail image may be generated by the terminal device 30 or the server device 20.
[0105] When a thumbnail image is generated by the terminal device 30, the control unit 300 acquires a received image based on image data stored in the timeline data. For example, the control unit 300 reads image data corresponding to the image data stored in the timeline data from the image data storage area 354. The control unit 300 generates a thumbnail image by reducing an image of one page from the received image included in the read image data. Note that when a thumbnail image is generated by the server device 20, the control unit 300 requests the thumbnail image from the server device 20 along with information based on the timeline data (for example, the file name and image ID of the image data). The control unit 300 acquires the thumbnail image sent from the server device 20 in response to the request for the thumbnail image.
[0106] Then, the control unit 300 displays the generated or acquired thumbnail image near the location where the corresponding message is displayed.
[0107] Next, if the reply status stored in the timeline data for which the message type is "received message" is "replied," the control unit 300 superimposes a stamp (identification information) on the thumbnail image displayed in step S136 (step S138). If the reply status is "not replied," the control unit 300 displays the thumbnail image without superimposing a stamp (identification information). In this embodiment, the identification information is information indicating that a received image to which a reply has been made has been sent. The identification information is displayed superimposed on the received image or a thumbnail image of the received image, or displayed around the received image or a thumbnail image of the received image. The identification information may be any information that allows the user to recognize that the received image has been replied to. The identification information may be, for example, a predetermined image such as a stamp or an icon, an animation, a video, text, or a symbol. The identification information may also be a border or the like displayed around the received image or a thumbnail image of the received image.
[0108] Next, the control unit 300 displays a reply button near the location where the message stored in the timeline data whose message type is "received message" is displayed (step S140).
[0109] Furthermore, the control unit 300 performs processing to omit and display messages stored in timeline data whose message type is a "message for replying" on the timelines of users other than the user who is performing the replying work.
[0110] First, the control unit 300 identifies a message displayed based on timeline data whose message type is "message for reply work" from among the messages displayed in step S134 (step S142).
[0111] Next, for each identified message, the control unit 300 determines whether the work user ID stored in the timeline data corresponding to the message matches the user ID of the user using the terminal device 30. The control unit 300 acquires the user ID of the user using the terminal device 30, for example, by reading the user ID stored in the authentication information 356. If the work user ID stored in the timeline data does not match the user ID of the user using the terminal device 30, the control unit 300 omits (reduced) the message stored in the timeline data on the timeline (step S144). The omitted display is a display method in which the control unit 300 omits and displays a part or the entire message (a display method in which the entire message is not expanded). Note that, when a message that has been omitted is selected by the user, the control unit 300 may expand the message so that the entire message is displayed. Alternatively, instead of omitting and displaying the message, the control unit 300 may hide the message. In this way, the control unit 300 can omit or hide messages related to reply operations on the timelines of users who do not perform reply operations.
[0112] Through the above-described processing, the control unit 300 displays a timeline on the display unit 320 based on the timeline data. Here, the control unit 300 displays messages related to the reply operation (for example, reply settings such as a comment to be added to the reply image, or edited contents of the destination of the sender device) only on the screen (display unit 320) of the user who is performing the reply operation. The control unit 300 omits and displays messages related to reply operations by other users on the screen (display unit 320) of users who are not performing the reply operation (displaying the messages without expanding them entirely). In this way, the control unit 300 does not display the operations by other users as common information, and displays only the results of the interaction between the user who performed the reply operation and the system (server device 20), such as the operation status and results. This allows the control unit 300 to prevent the display of information unnecessary for the user, thereby improving user operability.
[0113] Returning to FIG. 8 , when a thumbnail image displayed together with a message displayed when a received image is received is selected by, for example, a user clicking or tapping (step S108; Yes), the control unit 300 displays a preview image of the received image corresponding to the selected thumbnail image (step S110). The control unit 300 displays the preview image, for example, as an image larger than the thumbnail image on a screen separate from the screen displaying the timeline. In this way, the control unit 300 enables the user to check detailed information about the image data of the received image. Note that, as described in step S138, the image data merely has a stamp superimposed thereon, and no changes have been made to the image data itself. Therefore, even when a thumbnail image with a stamp superimposed thereon is selected, a preview image of the received image itself is displayed. Identification information such as a stamp is not displayed on the preview image.
[0114] Next, the control unit 300 determines whether or not the reply button has been selected (step S112). If the reply button has been selected, the control unit 300 determines whether or not the reply status of the timeline data corresponding to the reply button is "replied" (step S112; Yes → step S114). If the reply status is "replied", the control unit 300 displays a confirmation message (warning) indicating that a reply has already been made on the display unit 320 (step S114; Yes → step S116).
[0115] By displaying the warning, for example, if a user performs an operation (in this embodiment, a reply operation) and then the same user attempts to perform the same operation again, or if another user attempts to perform the same operation, the warning is displayed. In this way, it is possible to prevent erroneous operations such as duplicate operations being performed by multiple users. In addition to displaying the warning, the control unit 300 may also inquire of the user as to whether or not to continue the reply operation. If the user selects not to continue the reply operation, the control unit 300 omits the processes of steps S118 to S126.
[0116] The control unit 300 also reads out timeline data in which an image ID similar to the image ID of the timeline data corresponding to the reply button is stored and the message type is "message for reply work." Furthermore, the control unit 300 determines whether the work user ID stored in the read timeline data matches the user ID of the user using the terminal device 30. If they match, no warning is displayed, and if they do not match, a warning indicating that another user has replied may be displayed. In this case, if the user using the terminal device 30 performs a reply operation twice, the control unit 300 does not display a warning.
[0117] By the above-described processing, when a user other than the user who performed the reply operation presses (e.g., clicks or taps) the reply button for a received image whose reply status is "replied", the control unit 300 can display a warning (confirmation message) such as "Another user has already replied, do you want to reply?". Also, when a user who performed the reply operation presses (e.g., clicks or taps) the reply button for a received image whose reply status is "replied", the control unit 300 can display a warning (confirmation message) such as "You have already replied, do you want to reply?".
[0118] Next, the control unit 300 transmits a reply work request including the image ID stored in the timeline data corresponding to the reply button and the user ID of the user who uses the terminal device 30 to the server device 20 (step S118). By including the image ID in the reply work request, the server device 20 can identify the received image to be replied to.
[0119] When the timeline data acquisition unit 302 acquires timeline data whose message type is "reply message," the control unit 300 displays the message included in the acquired timeline data on the timeline (step S120). If the timeline data includes image data (e.g., a reply image), the control unit 300 displays a thumbnail image of the image data.
[0120] The control unit 300 accepts a user's operation on the reply message and edits the reply data by transmitting the confirmation result of the reply data content and the edited content to the server device 20 (step S122). Furthermore, when the user instructs the execution of a reply, the control unit 300 transmits a request for executing a reply (reply execution request) to the server device 20 (step S124).
[0121] Next, when the reply is completed, the control unit 300 superimposes a stamp on the thumbnail image of the received image that was the subject of the reply (step S126).
[0122] For example, the control unit 300 receives from the server device 20 an execution result including an image ID corresponding to the received image that was the subject of the reply and information indicating that the reply has been completed, as information that can identify the received image that has been replied to. Next, the control unit 300 identifies timeline data in which the image ID received from the server device 20 is stored and whose message type is "received message." The control unit 300 superimposes a stamp on the thumbnail image corresponding to the image data stored in the identified timeline data, among the thumbnail images displayed on the timeline.
[0123] In this way, the control unit 300 immediately adds (reflects) new information indicating that a reply has been made to the received image to the thumbnail image (previous display content) already displayed on the timeline. As a result, it is possible to prevent inconsistencies between the display content of the timeline and the content of the operation performed by the user.
[0124] [1.3.2 Server device] Next, the processing of the server device 20 will be described with reference to Fig. 10. First, the control unit 200 determines whether or not a reply work request has been received from the terminal device 30 (step S152).
[0125] When a reply work request is received, the control unit 200 generates reply data (step S152; Yes → step S154). For example, the control unit 200 reads out from the timeline data storage area 222 timeline data in which the image ID included in the reply work request is stored and the message type is "received message" (timeline data in which a message to be displayed when a received image is received is stored). The control unit 200 acquires the sender stored in the read timeline data and generates a reply image based on the image data. The control unit 200 generates reply data including the acquired sender and the generated reply image.
[0126] Next, the control unit 200 generates timeline data with the message type set to "reply work message" and stores it in the timeline data storage area 222 (step S156). Specifically, the control unit 200 generates timeline data with the poster user ID set to an ID indicating the server device 20 and the destination group ID set to the destination group ID stored in the timeline data read out in step S154. Furthermore, the control unit 200 includes in the timeline data the image ID included in the reply work request as the image ID, the user ID included in the reply work request as the work user ID, and a message inquiring of the user who will be working on the reply.
[0127] The content of the message may be a prompt to input a comment to be added to the reply image, or a prompt to confirm information about the sender of the received image that is the subject of the reply. The timeline data generated in step S156 is transmitted to the terminal device 30 by the timeline data processing unit 202 based on a request to acquire timeline data from the terminal device 30.
[0128] When the control unit 200 receives edited contents of the reply data from the terminal device 30, it reflects the edited contents in the reply data (step S158; Yes → step S160). For example, when the control unit 200 receives a comment to be added to the reply image from the terminal device 30, it adds the comment to the reply image. Furthermore, when the control unit 200 receives sender information from the terminal device 30, it updates the sender information included in the reply data to the information received from the terminal device 30.
[0129] Next, when the control unit 200 receives a reply execution request from the terminal device 30, it transmits reply data to the image communication device 10 (step S162; Yes→step S164).
[0130] Next, the control unit 200 receives from the image communication device 10 a result of the image transmission based on the reply data, and updates the reply status of the received image that was the reply target. For example, when the control unit 200 receives from the image communication device 10 a result indicating that the image transmission was successful, the control unit 200 updates the reply status of the timeline data read in step S154 to "reply completed" (step S166). Furthermore, the control unit 200 adds a comment indicating that a reply has been completed (for example, text data such as "hiroaki has replied") to the message stored in the timeline data read in step S154, and updates the editing status to "edited" (step S168). Note that the control unit 200 acquires the user who sent the reply from, for example, the operation user ID stored in the timeline data in which the image ID corresponding to the received image to which the reply was sent is stored.
[0131] In this way, after completing the reply operation, the control unit 200 updates the reply status and adds a comment indicating that the reply has been completed to the timeline data at the time when the received image that was the subject of the reply was received. This allows new information to be added to the timeline data corresponding to the previously displayed content. Furthermore, by displaying a timeline based on the added timeline data, the terminal device 30 can display in the message displayed when the received image is received that the received image displayed as a thumbnail image in the message has been replied to.
[0132] Furthermore, the control unit 200 transmits an execution result including the image ID of the received image that was the target of the reply and information indicating that the reply has been completed to the terminal device 30 that transmitted the reply execution request (step S170).
[0133] If no reply is received (for example, if a result indicating that the reply image transmission failed is received from the image communication device 10), the control unit 200 may omit the processes of steps S166 to S170. Alternatively, the control unit 200 may update the reply status of the timeline data read out in step S154 to "transmission failed."
[0134] Furthermore, the server device 20 may generate timeline data including a message indicating the status of the reply operation as appropriate, such as when editing the reply data, when sending the reply data, or when receiving a reply data sending result from the image communication device 10. In this case, the control unit 200 generates timeline data in which the poster user ID is set to an ID indicating the server device 20, the destination group ID is set to the destination group ID stored in the timeline data read in step S154, the image ID is set to the image ID included in the reply operation request, the message type is set to "system message," and the message includes the content of the status of the reply operation, and stores the generated timeline data in the timeline data storage area 222.
[0135] [1.4 Example of operation] An example of operation of this embodiment will be described with reference to the drawings. In the description of the example of operation, identical messages among messages displayed on the timeline will be assigned the same reference numerals. In the following description, a message displayed based on timeline data whose message type is "received message" will be simply referred to as a "received message." Similarly, a message displayed based on timeline data whose message type is "reply message" or "system message" will be simply referred to as a "reply message" or "system message."
[0136] 11 shows an example of a screen display when a notification (reception notification) indicating that a new fax has been received by the image communication device 10 is displayed on the display unit 320. For example, when a so-called standby screen W100 is displayed as in FIG. 11(a) or when a so-called home screen W102 is displayed as in FIG. 11(b), a toast message is displayed to indicate that a fax has been received (that a new fax has been received). Note that when the toast message is selected, the display may switch to a screen that displays timeline data in a timeline format.
[0137] Furthermore, on screen W104 of a dedicated app for using a service provided by server device 20, a badge may be displayed as a notification indicating that a fax has been received (that a new fax has been received) on an icon selected by the user to display a timeline, as in area B104. By looking at the toast display or badge display displayed on display unit 320, the user can confirm that a new fax has been received, i.e., that the image communication device 10 has received a fax.
[0138] 12 and 13 are examples of a display screen when a timeline is displayed on the display unit 320. On a mobile terminal, a timeline is generally displayed starting with the most recent information, and older information is displayed by scrolling upward. FIG. 12(a) is an example of a display screen W130 when a timeline is displayed on the display unit 320 and a received message C100 is displayed on the display unit 320 by the user scrolling upward. The received message C100 includes information E100 about the received image (e.g., fax number, date and time of reception, number of pages, file name). A thumbnail image F100 of the received image is also displayed.
[0139] Fig. 12(b) is an example of the display screen W140 when the timeline displayed in Fig. 12(a) is scrolled downward. A reply button B100 is displayed in the received message C100. Note that a button B102 for printing the received image may also be displayed in the received message C100.
[0140] When the reply button B100 is selected, a reply work message C110 is displayed on the timeline as the latest message. FIG. 12(b) is an example of a display screen W140 in which a message prompting confirmation of the fax number of the sender of the received image (the destination of the reply image) is displayed as the reply work message C110. The reply work message C110 displays a button B110 indicating that the sender's fax number is correct and a button B112 for correcting the fax number. By selecting button B110 or button B112, the user can indicate to the server device 20 that the fax number is correct or that correction is required. When button B112 is selected, for example, a reply work message for inputting a fax number is displayed on the timeline.
[0141] 13(a) is an example of a display screen W150 when, after the FAX number has been confirmed, a reply message C120 prompting the user to enter a comment to be added to the reply image is displayed on the timeline. The user enters the number of a pre-prepared template or a free comment in the input field T120 and selects button B120 to transmit the selected number or entered comment information as a comment to be included in the reply image to the server device 20. In this way, the user can edit and check the reply data by operating the reply message.
[0142] 13(b) is an example of a display screen W160 in which a reply operation message C130 prompting the user to check the reply image is displayed on the timeline after information about a comment to be added to the reply image has been sent. The reply operation message C130 displays a thumbnail image F130 of the reply image, and further displays a button B130 for sending a reply execution request. By selecting button B130, the user can send the reply image to the sender of the received image.
[0143] The reply message C130 may display an area E130 including buttons for modifying the addressee, telephone number (fax number), and text (comments to be added to the reply image). When the user selects a button included in E130, a reply message for modifying the reply data is displayed on the timeline.
[0144] 13(c) is an example of the display screen W170 when system messages C140 and C150 are displayed on the timeline after button B130 is selected. For example, system message C140 is a message indicating that a fax transmission is about to begin based on a reply operation. System message C150 is a message indicating that the fax transmission has been completed.
[0145] As shown in FIGS. 12(a) to 13(c), the latest messages are displayed one after another on the timeline, and the received message C100 is a past message (past display content). Therefore, by scrolling the display screen W170 shown in FIG. 13(c) upward, the received message C100 is displayed on the display unit 320. FIG. 13(d) shows an example of the display screen W180 when the display screen W170 shown in FIG. 13(c) is scrolled upward to display the received message C100 including a thumbnail image F100 of the received image to be replied to. The received message C100 is an older display content than the system message C150, but when the reply is completed, a stamp (completed stamp) is superimposed on the thumbnail image F100 of the received image to be replied to, which is included in the received message C100, which is past display content. In this way, even if the display content is past, information about the reply operation is added (reflected) as shown in the thumbnail image F100 shown in FIG. 13(d).
[0146] 14A and 14B are diagrams showing examples of timeline displays. Fig. 14A shows a timeline L100 displayed on the terminal device 30 used by the user who performed the reply operation. L100 displays a received message C100, reply operation messages C110, C120, and C130, and system messages C140 and C150.
[0147] 14(b) and 14(c) are examples of timelines L110 and L120 displayed on a terminal device 30 used by another user who belongs to the same group as the user who sent the reply, i.e., a user who is not performing the reply operation. The terminal device 30 of a user who is not performing the reply operation may display a timeline, such as timeline L110, that does not display the reply operation messages C110, C120, and C130. Alternatively, the terminal device 30 of a user who is not performing the reply operation may display a timeline, such as timeline L120, that omits the reply operation messages C110, C120, and C130. By displaying such a timeline, a user who is not performing the reply operation can know only that a fax has been received and the status and results of the operations of other users, making it easier to understand the status of the received image.
[0148] 15 shows an example of a display screen W190 in which a warning W192 is displayed when the reply button is selected for a received image to which a reply has already been sent. By checking the warning W192, the user can avoid sending a reply twice.
[0149] 15, a button B192 indicating to perform a reply operation and a button B194 indicating to cancel the reply operation may be displayed together with the warning W192. If the user selects B192, a reply operation message is displayed on the timeline. At this time, if a reply operation is performed in accordance with the user's operation on the reply operation message, information indicating the number of times the reply operation has been performed and information about the user who performed the reply operation may be displayed on the received image to which the reply has been made, along with identification information such as a stamp (done stamp). If the user selects B194, the reply is canceled, and therefore the reply operation message is not displayed on the timeline.
[0150] 16 is a diagram showing another example of the display of a received message including a received image to which a reply has been made. FIG. 16(a) is an example of a timeline L130 including a received message C102 including a received image to which a reply has been made. The received message C102 may include a comment E102 indicating that a reply has been made (for example, "Hiroaki has replied"). Note that when the reply is completed, the message is edited to add a comment indicating that a reply has been made, and therefore, the words "edited" are displayed together with the message, as shown in A102.
[0151] 16(b) is an example of a timeline L140 including a received message C104 that includes a received image for which a reply has been made. Instead of superimposing a stamp (Done stamp) on the received image for which a reply has been made, as in the received message C104, a thumbnail image F104 of the reply image (reply data) may be displayed. The thumbnail image of the reply image may be displayed based on image data stored in timeline data whose message type is "message for reply work."
[0152] As described above, according to this embodiment, the user can confirm that a fax has been received and can operate on the received image using a timeline-style UI. In addition, a stamp (identification information) is superimposed on the received image to which a reply has been sent, so the user can easily check whether or not a reply has been sent.
[0153] In addition, the embodiment may be modified in a manner other than that described above, as long as there is no contradiction.
[0154] For example, in this embodiment, a timeline (working user screen) displaying messages exchanged one-to-one between the server device 20 and users in chronological order may be displayed, separate from the timeline (shared screen) viewed by all users belonging to the group. In this case, the terminal device 30 may display the reply message on the working user screen but not on the shared screen. As a result, the reply message is not displayed on the shared screen, and users who have not performed a reply operation can only know the results of the interaction between the user who performed the reply operation and the system (server device 20), such as the receipt of a fax and the status and results of operations by other users. Because unnecessary information is not displayed for users who do not perform a reply operation, the terminal device 30 can improve user operability.
[0155] Furthermore, in the present embodiment, the image communication device 10 is described as being equipped with the reception processing unit 106 and the transmission processing unit 108. However, the processing performed by these functional units may be implemented in an information processing device (edge terminal) different from the image communication device 10. The edge terminal cooperates with the image communication device 10 (MFP cooperation) to implement the functions of the image communication device 10 in this embodiment. In this case, the image communication device 10 transmits received images and information related to the received images to the edge terminal. The edge terminal transmits received data, including the received images and information related to the received images received from the image communication device 10, to the server device 20 along with authentication information stored in the edge terminal. Furthermore, when the edge terminal receives transmission data from the server device 20, it controls the image communication device 10 to transmit a reply image to the transmission source device. Note that the edge terminal may also implement the functions of the image communication device 10. For example, the edge terminal may have the function of the FAX control unit 102, thereby enabling the edge terminal to receive and transmit FAXes from and to the transmission source device.
[0156] Furthermore, in the timeline display process, instead of displaying messages related to all received images, only messages related to received images received only from a transmission source device (destination) preset by the user may be displayed. For example, in step S132, the control unit 300 extracts timeline data in which the FAX number of the transmission source device specified by the user is stored and the message type is "received message" from the timeline data storage area 222. The control unit 300 then reads out from the timeline data storage area 222 timeline data in which the same image ID as the image ID stored in the extracted timeline data is stored. Thereafter, the control unit 300 executes the processes from step S134 onward. In this way, instead of displaying messages related to all received images, only messages related to received images received from a transmission source device preset are displayed, making it easier for the user to check the received images.
[0157] Furthermore, in the timeline display process, when the reply status stored in timeline data whose message type is "received message" is "replied," a stamp (identification information) is superimposed on the thumbnail image. However, other processing may be performed. For example, the control unit 300 may display the message in a predetermined text color, or the background of the message in a predetermined color. The control unit 300 may also color the message or thumbnail image by superimposing a semi-transparent color on it, or may display predetermined identification information (e.g., an icon) superimposed on or around the thumbnail image. That is, the control unit 300 may display identification information visually indicating that a reply has been made for a message or thumbnail image based on timeline data whose reply status is "replied."
[0158] Also, in step S104, the notification display control unit 306 has been described as displaying a notification of a new fax based on the timeline data, but the notification of a new fax may be performed by other methods. For example, after generating the timeline data, the received data processing unit 204 transmits information indicating that a new fax has been received to a terminal device 30 used by a user who belongs to the same group as the image communication device 10 that received the received image. The notification display control unit 306 displays a notification of a new fax when it receives information indicating that a new fax has been received.
[0159] Furthermore, when the control unit 200 updates the timeline data, such as by adding an entry, the control unit 200 may transmit information indicating that the timeline data has been updated to the terminal devices 30 used by users who belong to a group identified by the destination group ID stored in the timeline data. Upon receiving the information indicating that the timeline data has been updated, the terminal devices 30 reacquire the timeline data updated by the server device 20 and reflect the updated data on the timeline. In this way, the timeline can be kept up to date.
[0160] In addition, even if it is not the case that the above-described explanation is not applicable, the order of the steps may be changed or some steps may be omitted within a range that does not cause inconsistencies. For example, in the timeline display process, the control unit 300 may display a reply button (step S140) and then execute the display of thumbnail images and superimposed display of stamps (steps S136 and S138).
[0161] According to this embodiment, the terminal device 30 displays a timeline based on timeline data acquired from the server device. Because a group is specified as the posting destination, the timeline data is acquired by the terminal device 30 used by the users belonging to the group, enabling information sharing. Furthermore, when a reply operation is performed on a received image, information indicating that a reply operation has been performed is added (reflected) on the timeline. Therefore, as long as the user is connected to the server device, the user can share the images received by the image communication device and the details of the operation via the terminal device, regardless of location.
[0162] Furthermore, in this embodiment, when a reply operation is performed, the content of the operation performed on the received image is added to the display content of the timeline on the terminal device 30 where the reply operation was performed. This allows the content of the user's operation to be displayed in real time, and further prevents inconsistencies between the content of the timeline display already displayed and the content of the operation performed by the user. The server device also adds (updates) information to the timeline data storing the received image to which the reply is made. For example, the server device updates the reply status to "replied" or adds a comment indicating that the message has been replied to. The user can prevent inconsistencies between the content displayed on the timeline and the content of the operation performed by the user by re-acquiring and displaying the timeline data. In this way, it is possible to perform operations on the display content (received image) without deteriorating operability, while maintaining the convenience of a service that displays messages input between multiple user terminals in real time in chronological order. By joining a group, users can obtain information about image communication devices and receive reception notifications via their terminal devices. This prevents a situation where reception notifications are only sent to pre-defined users. When you confirm a reception notification and want to reply to the received data (received image), you can simply reply by selecting the reply button displayed on the timeline. In addition, by sharing timeline data with multiple users, multiple users can share the status of their response to the received image.
[0163] Furthermore, when a user selects a notification (reception notification) that a new fax has been received and checks the timeline, the user first searches for a thumbnail image of the received data (received image) on the timeline and checks the received image. However, when a timeline is shared with other users, the timing at which the user checks the received image generally differs from that of the other users. Because the actions (operations) performed by other users up until the user checks the received image are displayed on the timeline, it may be difficult for the user to understand the sequence of events. As a result, it may be difficult for the user to understand whether a reply operation has been performed on the received image. In contrast, in this embodiment, identification information such as a stamp is displayed on thumbnail images corresponding to received images to which a reply has been made, or a comment indicating that a reply has been made is added to the message, so that the user can easily identify received images to which a reply has been made at a glance.
[0164] Furthermore, according to this embodiment, the terminal device displays messages based on timeline data whose message type is a "reply message" to users who perform a reply operation, but omits the display for users who do not perform a reply operation. By omitting and displaying information that is unnecessary for users who do not perform a reply operation, the terminal device can improve user operability.
[0165] Furthermore, according to this embodiment, if a reply operation is performed on a received image to which a reply has already been sent, a warning is displayed, thereby preventing the user from making a mistaken reply, such as sending a duplicate reply.
[0166] [2. Second Embodiment] Next, a second embodiment will be described. In the second embodiment, in addition to adding a comment indicating that a reply has been completed as described in the first embodiment, a comment indicating that a reply is currently being made (operation is in progress) is added and displayed on the terminal device. In the second embodiment, FIG. 10 of the first embodiment is replaced with FIG. 17, and the same functional units and processes are assigned the same reference numerals and descriptions thereof will be omitted.
[0167] The flow of processing in the server device 20 of this embodiment will be described with reference to Fig. 17. In this embodiment, after the processing of step S156, the control unit 200 adds a comment indicating that a reply operation is being performed (for example, text data such as "yokomitsu is replying") to the message stored in the timeline data read in step S154 (step S252). At this time, the control unit 200 updates the editing status of the timeline data read in step S154 to "edited".
[0168] After the process of step S168, the control unit 200 deletes the comment added in step S252 (step S254).
[0169] By the above-described process, a comment indicating that a reply is in progress is added to the message of the timeline data storing the received image to be replied to, from the time when the reply work request is received until the time when the reply execution request is received, i.e., until the reply work is completed. The terminal device 30 acquires and displays the timeline data to which the comment has been added, thereby indicating that a reply operation is in progress.
[0170] In this embodiment, in step S114, the control unit 300 of the terminal device 30 also determines whether or not a comment indicating that a reply is being made to the message is included in the timeline data corresponding to the reply button. If a comment indicating that a reply is being made to the message is included, the control unit 300 displays a confirmation message (warning) indicating that a reply is being made on the display unit 320.
[0171] At this time, the control unit 300 may determine whether or not a reply operation has been performed by another user based on the timeline data, similarly to the first embodiment, and switch whether or not to display a warning.
[0172] Furthermore, in step S134, if the message includes a comment indicating that a reply is being made, the control unit 300 may highlight the comment by making the character size of the comment larger than the character size of the message, by using a different color for the character of the comment from the color of the character of a normal message, by drawing a line around the comment, by changing the background color of the comment, or the like.
[0173] An example of the operation of this embodiment will be described with reference to Fig. 18. Fig. 18(a) is an example of a timeline L200 displayed on the display unit 320 in this embodiment. A received message C200 is displayed on the timeline L200.
[0174] A thumbnail image F200 of the received image corresponding to the received message C200 is displayed in the received message C200. If a reply operation is being performed on the received image corresponding to the received message C200, a comment indicating that a reply is being made is displayed, as shown in area E200. Furthermore, since the editing status of the timeline data corresponding to the received message C200 is "edited," a display indicating that the timeline data has been edited is displayed, as shown in area A200.
[0175] Fig. 18(b) is an example of a display screen W200 that is displayed on the display unit 320 when the reply button B200 displayed on the received message C200 shown in Fig. 18(a) is selected. In this embodiment, if an attempt is made to perform a reply operation on a received image that has already been operated on for replying, a warning W202 is displayed. The user can select whether or not to continue the reply operation.
[0176] According to this embodiment, when a user is working on a reply, the terminal device 30 displays a message indicating that the reply is being worked on. Depending on the content of the reply, it may take some time to work on the reply, but even in this case, the user working on the reply can prevent another user from accidentally working on the same message.
[0177] 3. Third Embodiment The third embodiment is an embodiment in which timeline data is linked to image data and then a timeline is displayed. In the third embodiment, Fig. 8 of the first embodiment is replaced with Fig. 19, and the same functional units and processes are assigned the same reference numerals and descriptions thereof are omitted.
[0178] The processing flow of the terminal device 30 in this embodiment will be described with reference to Fig. 19. In this embodiment, after the processing of step S106, the control unit 300 selects one piece of timeline data from the timeline data displayed as a timeline, and extracts timeline data having the same image ID as the selected timeline data (step S302). In this way, the timeline data corresponding to one received image is linked.
[0179] Next, the control unit 300 displays the same identification mark for the message corresponding to the timeline data extracted in step S302 (step S304). The identification mark is, for example, a strip-shaped rectangle with a predetermined width that is displayed next to the message. In this case, the control unit 300 displays a strip-shaped rectangle with the same background color as the same identification mark next to the message corresponding to the extracted timeline data. In this way, the control unit 300 associates the message with one received image and displays it in the same color.
[0180] When the control unit 300 repeatedly executes the process of step S304, it displays an identification display that is different from the identification display that has already been displayed. For example, when the control unit 300 executes step S304 for the first time, it displays a strip-shaped rectangle with a red background. When the control unit 300 executes step S304 for the second time, it displays a strip-shaped rectangle with a green background. In this way, the same identification display is displayed for messages based on timeline data in which the same image ID is stored, but different identification displays are displayed for messages based on timeline data in which different image IDs are stored.
[0181] The distinguishing mark does not have to be a strip-shaped rectangle, but may be the background color of the message, the text color of the message, an icon added to the message, or the like.
[0182] Next, the control unit 300 displays in full only the messages based on timeline data whose message type is "received message" (messages displayed when the received image is received) and the messages based on timeline data with the most recent date and time (latest messages) from among the extracted timeline data, and omits (reduced) the display of other messages (step S306). By doing this, the control unit 300 omits and displays, for each received image, all messages for the same received image (one piece of data) other than the message at the time the received image was received (display at the time of reception) and the latest message.
[0183] Next, the control unit 300 displays (places) a message display switching button for switching the display to the previous or next message for each message corresponding to the extracted timeline data (step S308). The message previous to a given message is, among messages with the same identification, a message whose date and time precedes and is closest to the date and time of the given message. Similarly, the message next to a given message is, among messages with the same identification, a message whose date and time follows and is closest to the date and time of the given message. In other words, the message display switching button is a button for switching the display to the next or previous message in chronological order among messages related to the same received image.
[0184] Next, the control unit 300 determines whether all the timeline data displayed as a timeline has been extracted (step S310). If all the timeline data has not been extracted, the control unit 300 returns to step S302 and executes the processes of steps S302 to S308 on the unextracted timeline data (step S310; No→step S302).
[0185] Furthermore, when a message display switching button is selected, the control unit 300 switches the display to the corresponding message (step S312; Yes → step S314). The control unit 300 switches the message display by, for example, displaying the previous or next corresponding message at the position where the message display switching button selected by the user is displayed.
[0186] The control unit 300 may execute either step S306 or step S308, or may not execute both steps.
[0187] An example of operation in this embodiment will be described with reference to the drawings. In the description of the example of operation, the same messages displayed on the timeline are denoted by the same reference numerals.
[0188] 20 shows an example of a timeline L300 in which identification marks are displayed for messages based on timeline data. Here, it is assumed that the same image ID is stored in the timeline data corresponding to message C300, message C320, message C340, message C350, and message C360. In this case, strip-shaped rectangles R300, R320, R340, R350, and R360, each with the same background color, are displayed next to these messages.
[0189] Meanwhile, the same image ID is stored in the timeline data corresponding to message C310 and message C330. However, the image IDs corresponding to message C310 and message C330 are different from the image ID corresponding to message C300. In this case, strip-shaped rectangles R310 and R330 with the same background color are displayed next to message C310 and message C330. However, the background colors of rectangles R310 and R330 are different from that of rectangle R300.
[0190] Furthermore, the image ID corresponding to message C370 is different from that of message C300 and message C310. In this case, message C370 is displayed as a strip-shaped rectangle R370 with a background color different from that of rectangle R300 and rectangle R310.
[0191] In this way, messages corresponding to the same image ID are displayed with the same identification mark, and messages corresponding to different image IDs are displayed with different identification marks. Therefore, even when scrolling the timeline, the user can easily check the series of operations and statuses performed on the same received image.
[0192] Figure 21 is an example of a timeline L310 in which, among messages with the same identification display, messages other than messages based on timeline data with a message type of "received message" and messages based on timeline data with the latest date and time are displayed in an abbreviated manner.
[0193] For example, message C300, message C320, message C340, message C350, and message C360 are displayed with the same identification. Of these, messages C320, C340, and C350 other than message C300 based on timeline data whose message type is "received message" and message C360 based on timeline data with the latest date and time are displayed in an abbreviated form. Similarly, of messages C310 and C330 with the same identification, message C310 other than message C330 based on timeline data with the latest date and time is displayed in an abbreviated form. Furthermore, message C370 whose message type is "received message" is displayed without abbreviation.
[0194] In this way, all messages other than the message indicating the reception of a FAX and the message indicating the latest status of the received image are displayed in a simplified manner, so the user can easily grasp the latest status of each received image.
[0195] 22(a) is an example of a timeline L320 when message display switching buttons are displayed. For example, message C300 displays a button B300 for switching the display to the previous message and a button B302 for switching the display to the next message. Note that if there is no previous message or no next message, the message display switching buttons may be made unselectable or hidden. For example, like button B300 in FIG. 22(a), if there is no previous message, button B300 may be made unselectable.
[0196] Fig. 22(b) is an example of the timeline L330 when button B302 in Fig. 22(a) is selected. In this case, message C320, which is the next message, is displayed in the position where message C300 was displayed. Message C320 also displays button B320 for switching the display to the previous message and button B322 for switching the display to the next message. When button B320 is selected, message C300, which is the previous message, is displayed in the position where message C320 was displayed. When button B322 is selected, the next message (e.g., message C340) is displayed in the position where message C320 was displayed.
[0197] In this way, the user can switch between messages with the same identification, i.e., messages related to the same received image, and as a result, the user can easily grasp the status of each received image.
[0198] According to this embodiment, the timeline is displayed after linking the timeline data linked to the same received image, so that the user can easily grasp the situation regarding the same received image.
[0199] Generally, the display area on a mobile device screen is limited, and messages are displayed in chronological order, making it difficult to understand the sequence of messages for the same information. For example, as shown in Figure 20, messages related to operations on different received images may be displayed in chronological order. Furthermore, for example, when a user checks message C350 in Figure 20, the user can see that reply data is being created (edited), but it is difficult to identify which of the multiple fax data (received images) the message is related to.
[0200] According to this embodiment, messages related to the same received image are marked with the same identification, so that the user can easily check the series of tasks (operations) and status of the data (received image) even when scrolling the display on the screen of the mobile terminal (terminal device). Furthermore, among the messages marked with the same identification, messages other than the message when the received image was received and the message based on the latest timeline data are omitted, so that the user can easily check the status of one piece of data (received image). Furthermore, by selecting a button to switch the display to the previous or next message, the user can switch the display to messages that are chronologically related, and can easily see the connection between the previous and next messages in the information related to the received image.
[0201] [4. Fourth Embodiment] The fourth embodiment is an embodiment in which a contact (notification) is made when there is a received image for which a reply operation has not been performed and for which a reply has not yet been made.
[0202] In this embodiment, for example, the notification display control unit 306 periodically extracts timeline data whose date and time fall within a predetermined period (e.g., one week) and whose reply status is "no reply" from the timeline data stored in the timeline data storage area 352. The timeline data extracted in this manner is timeline data that includes received images for which no reply operation has been performed within the predetermined period. When one or more pieces of timeline data are extracted, the notification display control unit 306 displays a notification indicating that there are received images for which no reply operation has been performed. Note that the notification display control unit 306 may also display a message stored in the extracted timeline data.
[0203] Fig. 23 is a diagram showing an example of operation in this embodiment. Fig. 23 is an example of a display screen W400 when a notification W402 indicating that there is a received image for which a reply operation has not been performed is displayed on the display unit 320. The notification W402 includes, for example, the contents of the message stored in the timeline data extracted by the notification display control unit 306 (for example, information related to the received image, such as the fax number and the date and time of reception).
[0204] According to this embodiment, even if the unreplied data (received images) is left unattended, the user will receive a message (notification) from the system (e.g., terminal device 30) in the form of a toast display, etc., and by checking the notification, the user can prevent missing out on responding to the unreplied received images.
[0205] [5. Fifth Embodiment] The fifth embodiment is an embodiment in which the status of received images is displayed by a method other than the timeline.
[0206] In this embodiment, in step S106, the terminal device 30 performs the following process instead of the timeline display process.
[0207] The control unit 300 reads out only the timeline data whose message type is "received message" and displays the message in a table format on the display unit 320. Next, the control unit 300 displays thumbnail images based on the image data of the read timeline data. If the reply status of the read timeline data is "replied," the control unit 300 superimposes a stamp on the thumbnail image. The control unit 300 also displays a reply button.
[0208] When the reply button is selected, the control unit 300 displays a warning if the reply status of the timeline data corresponding to the reply button is "Replied." When a reply operation is performed, for example, the control unit 300 may display a reply operation message on the display unit 320 and accept an operation to edit the reply data or a reply execution request.
[0209] Fig. 24 is a diagram showing an example of operation in this embodiment. Fig. 24 is an example of a display screen W500 when timeline data is displayed in a table format on the display unit 320. A message E500 and a thumbnail image F500 of a received image are displayed on the display screen W500. Note that a stamp is superimposed on a thumbnail image F502 of a received image corresponding to timeline data whose reply status is "replied."
[0210] Also displayed on the display screen W500 is a button B500 for replying to the received image. When the user selects the button B500, a screen for accepting an operation to reply to the corresponding received image is displayed on the display unit 320.
[0211] In this embodiment, the timeline data is displayed in a table format, but it may be displayed in a format other than a table. Also, it may be possible to switch between a screen that displays the timeline data in a timeline format and a screen that displays the timeline data in a table format.
[0212] According to this embodiment, the received image and the situation regarding the received image can be summarized and displayed, so that even if a large amount of timeline data is displayed on the terminal device and the displayed timeline is long, the user can easily grasp the received image and the situation regarding the received image.
[0213] [6. Modifications] The present invention is not limited to the above-described embodiments, and various modifications are possible. In other words, embodiments obtained by combining technical means that are appropriately modified within the scope of the gist of the present invention are also included in the technical scope of the present invention.
[0214] Although the above-described embodiments are described separately for convenience of explanation, they may be combined within the scope of technical feasibility. For example, the third embodiment and the fifth embodiment may be combined. In this way, the user can check messages related to each received image in a timeline format and can check an overview of the status of each received image in a table format.
[0215] In addition, the programs that run on each device in the embodiments are programs that control the CPU, etc. (programs that make a computer function) so as to realize the functions of the above-described embodiments. Information handled by these devices is temporarily stored in a temporary storage device (e.g., RAM) during processing, and then stored in various storage devices such as ROMs (Read Only Memories) and HDDs, and is read, modified, and written by the CPU as needed.
[0216] Here, the recording medium for storing the program may be any of semiconductor media (e.g., ROM, non-volatile memory card, etc.), optical recording media / magneto-optical recording media (e.g., DVD (Digital Versatile Disc), MO (Magneto Optical Disc), MD (Mini Disc), CD (Compact Disc), BD (Blu-ray Disc), etc.), magnetic recording media (e.g., magnetic tape, flexible disk, etc.), etc. Furthermore, not only are the functions of the above-described embodiments realized by executing the loaded program, but the functions of the present invention may also be realized by processing in cooperation with an operating system or other application programs, etc., based on instructions from the program.
[0217] Furthermore, when distributing the program on the market, the program can be stored on a portable recording medium and distributed, or transferred to a server computer connected via a network such as the Internet. In this case, the storage device of the server computer is of course included in the present invention. [Explanation of symbols]
[0218] 1 System 10 Image communication equipment 100 control section 102 FAX control section 104 Image processing section 106 Receiving processing unit 108 Transmission processing unit 120 Image reading unit 130 Image forming unit 140 Display section 150 Input section 160 Storage section 162 Image data storage area 164 Authentication Information 170 Line Communication Unit 180 Network Communications Department 20 Server device 200 control section 202 Timeline data processing section 204 Received data processing unit 206 Authentication processing section 210 Network Communications Department 220 Storage section 222 Timeline Data Storage Area 224 Image data storage area 226 Authentication information storage area 228 User information storage area 230 Device information storage area 232 Group information storage area 30 Terminal Equipment 300 control section 302 Timeline Data Acquisition Unit 304 Posting Processing Unit 306 Notification information control section 320 Display 330 Input section 340 Network Communications Department 350 Storage section 352 Timeline Data Storage Unit 354 Image data storage area 356 Credentials
Claims
1. An image communication apparatus capable of communicating with a terminal apparatus via a server apparatus that provides a service for managing a group made up of an image communication apparatus and one or more users who use the image communication apparatus, a control unit for transmitting and receiving images to and from other devices by performing facsimile communication; The control unit When the image is received from the other device, the server device transmits received data including the image and information about the image to the server device; In response to receiving reply data in response to the received data from the server device, transmitting a reply image included in the reply data to the other device; transmitting a transmission result of the reply image to the server device so that a reply status based on the transmission result of the reply image can be displayed on the terminal device so as to be shareable among one or more users belonging to the group; Image communication equipment.
2. the reply data is transmitted from the server device when the server device receives a reply request for the received data from the terminal device.
2. The image communication device according to claim 1.
3. The transmission result is used by the server device to update the reply status.
3. The image communication apparatus according to claim 1.
4. If the transmission result indicates that the reply image has been successfully transmitted, the transmission result is used by the server device to update the reply status to "returned." 4. The image communication apparatus according to claim 3.
5. If the transmission result indicates that the transmission of the reply image has failed, the transmission result is used by the server device to update the reply status to "transmission failed." 4. The image communication apparatus according to claim 3.
6. 1. A method for controlling an image communication apparatus capable of communicating with a terminal device via an image communication apparatus that transmits and receives images to and from other apparatuses by performing facsimile communication, and a server apparatus that provides a service for managing a group made up of one or more users who use the image communication apparatus, comprising: When the image is received from the other device, the server device transmits received data including the image and information about the image to the server device; In response to receiving reply data in response to the received data from the server device, transmitting a reply image included in the reply data to the other device; transmitting a transmission result of the reply image to the server device so that a reply status based on the transmission result of the reply image can be displayed on the terminal device so as to be shareable among one or more users belonging to the group; A method for controlling an image communication device.
7. An image communication device that transmits and receives images to and from other devices by performing facsimile communication; a server device that provides a service for managing a group made up of one or more users who use the image communication device; a terminal device capable of communicating with the image communication device via the server device; A communication system comprising: The image communication device When the image is received from the other device, the server device transmits received data including the image and information about the image to the server device; In response to receiving reply data in response to the received data from the server device, transmitting a reply image included in the reply data to the other device; transmitting a transmission result of the reply image to the server device so that a reply status based on the transmission result of the reply image can be displayed on the terminal device in a manner that can be shared among one or more users belonging to the group; The terminal device In response to receiving from the server device a transmission result of the reply image for which execution of a reply has been requested by another user belonging to the same group as the user using the terminal device, a reply status based on the transmission result is displayed. Communication system.
8. An image communication device that transmits and receives images to and from other devices by performing facsimile communication; A control method for a communication system including a server device that provides a service for managing a group made up of one or more users who use the image communication device, and a terminal device that can communicate with the image communication device via the server device, The image communication device When the image is received from the other device, the server device transmits received data including the image and information about the image to the server device; In response to receiving reply data in response to the received data from the server device, transmitting a reply image included in the reply data to the other device; transmitting a transmission result of the reply image to the server device so that a reply status based on the transmission result of the reply image can be displayed on the terminal device in a manner that can be shared among one or more users belonging to the group; The terminal device In response to receiving from the server device a transmission result of the reply image for which execution of a reply has been requested by another user belonging to the same group as the user using the terminal device, a reply status based on the transmission result is displayed. A method for controlling a communication system.
Citation Information
Patent Citations
Data processing unit and its control method
JP2001103232A
Image forming apparatus, and facsimile notifying method and program
JP2008160531A
Fax browsing system and server
JP2010061225A
Image processing apparatus, image processing method and program
JP2016086397A