Image processing device, image processing system, and method for managing facsimile data

The image processing device addresses memory inefficiency and data integrity issues by authenticating and securely transferring fax data to a cloud service for deletion, enhancing memory efficiency and data security.

JP7894770B2Active Publication Date: 2026-07-24SHARP KK
View PDF 3 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
SHARP KK
Filing Date
2022-09-08
Publication Date
2026-07-24

AI Technical Summary

Technical Problem

Conventional multifunction printers with facsimile functions face issues of reduced memory efficiency due to unresolved fax data storage and the inability to verify the integrity of transferred fax data, leading to potential tampering and unwanted paper output.

Method used

An image processing device with a storage unit, verification unit, and control unit that confirms the authenticity of fax data, allowing secure transmission to a cloud service and subsequent deletion from the device.

Benefits of technology

Ensures efficient memory usage by deleting fax data after verification and secure transfer to a cloud service, preventing unauthorized printing and proving data integrity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007894770000001
    Figure 0007894770000001
  • Figure 0007894770000002
    Figure 0007894770000002
  • Figure 0007894770000003
    Figure 0007894770000003
Patent Text Reader

Abstract

To provide an image processing device etc. which suitably transmit facsimile data to another service and thereafter delete the data.SOLUTION: The image processing device comprises: a storage unit which stores received facsimile data; a verification unit which verifies authenticity of the facsimile data; and a control unit which when the authenticity of the facsimile data is verified, performs control to transmit the facsimile data to a service and delete the facsimile data from the storage unit.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to an image processing apparatus and the like.

Background Art

[0002] Conventionally, image processing apparatuses such as multifunction printers equipped with a facsimile function have been used. Also, with regard to multifunction printers equipped with a facsimile function, techniques for transmitting (transferring) received facsimile data to an external device or service have been proposed.

[0003] For example, when there is no caller number in the number information list or when an identification signal is received without receiving the caller number, facsimile data is sequentially stored, and every time a predetermined unit of the facsimile data is stored, a predetermined unit of the facsimile data is transmitted to a cloud server and the predetermined unit of the facsimile data is deleted (see, for example, Patent Document 1). Also, a technique for verifying the integrity of transferred image data by comparing a first hash value generated from image data with a second hash value generated from the image data transferred to the cloud side has been proposed (see, for example, Patent Document 2).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] Generally, fax documents have evidentiary value, so unless a process to delete the fax document data (linked data) after transfer is explicitly specified, the linked data remains on the multifunction printer and is not deleted. In other words, even if the multifunction printer is configured to link with a cloud service and the fax document data is linked (transferred) to the cloud service, the fax document data continues to be stored until the fax document is printed (paper output) on paper such as record paper. This resulted in a problem of reduced memory usage efficiency of the multifunction printer. Furthermore, even when paper output of the fax data was not desired, the continued storage of the fax data resulted in the problem of the fax data being printed on paper.

[0006] For example, generally, when receiving fax data, the available processing methods include forwarding, printing, deleting, forwarding and printing, forwarding and deleting, or doing nothing (storing only). In this case, even if "forwarding" is selected as the processing method, the fax data is not deleted from the multifunction printer simply by completing the transfer. Furthermore, when "forwarding and deleting" is selected as the processing method for fax data, it is unclear whether the fax data has been transferred without being tampered with, and there is a problem in that it is not possible to prove the existence or non-tampering of the transferred fax data.

[0007] Regarding this issue, conventional technologies have not been able to prove that fax data sent to a cloud service has not been tampered with. For example, the technology described in Patent Document 1 does not consider how to prove that fax data has not been tampered with. Furthermore, the technology described in Patent Document 2 is based on the premise that image data is downloaded from the cloud service, and therefore, it is not possible to verify that fax data has not been tampered with when image data is not downloaded.

[0008] In light of the aforementioned issues, this disclosure aims to provide an image processing device, etc., that appropriately transmits facsimile data to other services and then deletes it. [Means for solving the problem]

[0009] The image processing apparatus of the present disclosure is characterized by comprising: a storage unit for storing received facsimile data; a verification unit for verifying the authenticity of the facsimile data; and a control unit that, when the authenticity of the facsimile data has been confirmed, transmits the facsimile data to a service and controls the deletion of the facsimile data from the storage unit.

[0010] Furthermore, the image processing system disclosed herein includes an image processing device and a server, wherein the image processing device comprises a storage unit for storing facsimile data, a verification unit for verifying the authenticity of the facsimile data, and a control unit that, when the authenticity of the facsimile data has been confirmed, transmits the facsimile data to the server and controls the deletion of the facsimile data from the storage unit, and the server comprises a transmission unit for transmitting the facsimile data to a service.

[0011] Furthermore, the facsimile data management method of this disclosure is a facsimile data management method characterized by including the steps of: storing received facsimile data in a storage device; verifying the authenticity of the facsimile data; and, when the authenticity of the facsimile data has been confirmed, transmitting the facsimile data to a service and deleting the facsimile data from the storage device. [Effects of the Invention]

[0012] This disclosure makes it possible to provide an image processing device, etc., that appropriately transmits facsimile data to other services and then deletes it. [Brief explanation of the drawing]

[0013] [Figure 1] This is an overall system configuration diagram of the first embodiment. [Figure 2] This is a functional configuration diagram of the multifunction device in the first embodiment. [Figure 3] It is a functional configuration diagram of the authentication server in the first embodiment. [Figure 4] It is a functional configuration diagram of the cloud server in the first embodiment. [Figure 5] It is a sequence diagram showing the processing flow in the first embodiment. [Figure 6] It is a flowchart of the main processing of the multifunction device in the first embodiment. [Figure 7] It is a flowchart of the main processing of the authentication server in the first embodiment. [Figure 8] It is a flowchart of the main processing of the cloud server in the first embodiment. [Figure 9] It is a diagram showing an operation example in the first embodiment. [Figure 10] It is a functional configuration diagram of the multifunction device in the second embodiment. [Figure 11] It is a diagram showing an example of the data structure of the storage destination information in the second embodiment. [Figure 12] It is a flowchart of the main processing of the multifunction device in the second embodiment. [Figure 13] It is a functional configuration diagram of the multifunction device in the third embodiment. [Figure 14] It is a diagram showing an example of the data structure of the cloud service information in the third embodiment. [Figure 15] It is a flowchart of the main processing of the multifunction device in the third embodiment. [Figure 16] It is an overall configuration diagram of the system in the fourth embodiment. [Figure 17] It is a functional configuration diagram of the multifunction device in the fourth embodiment. [Figure 18] It is a functional configuration diagram of the intermediate server in the fourth embodiment. [Figure 19] It is a sequence diagram showing the processing flow in the fourth embodiment. [Figure 20] It is a flowchart of the main processing of the multifunction device in the fourth embodiment. [Figure 21] It is a flowchart of the main processing of the intermediate server in the fourth embodiment. [Modes for carrying out the invention]

[0014] An embodiment for implementing this disclosure will be described below with reference to the drawings. Note that the following embodiment is merely an example for illustrating this disclosure, and the technical scope of the invention as described in the claims is not limited to the following description.

[0015] [1. First Embodiment] [1.1 Overall Structure] Figure 1 shows the overall configuration of System 1, which includes a multifunction printer 10 to which the image processing apparatus of the present disclosure is applied. As shown in Figure 1, System 1 of this embodiment is configured by connecting the multifunction printer 10, the authentication server 20, and the cloud server 30 via a network NW. The network NW is described as an external network such as the Internet (WAN (Wide Area Network)), but it may be a network other than the Internet (for example, a LAN (Local Area Network)) as long as each device can exchange information with each other.

[0016] The multifunction device 10 is an image processing device that has copying, scanning, printing, and faxing functions, and is also called an MFP (Multi-Function Printer / Peripheral).

[0017] The authentication server 20 and the cloud server 30 are information processing devices that provide predetermined services. The authentication server 20 and the cloud server 30 are composed of computers such as servers, for example. The authentication server 20 and the cloud server 30 may be composed of multiple devices, or they may be composed of virtual servers implemented on any information processing device.

[0018] The authentication server 20 provides functions and services used to verify the authenticity of data. In this embodiment, the services provided by the authentication server 20 are referred to as authentication services. Authentication services are generally provided by a third-party organization (external organization).

[0019] The authentication server 20 provides, for example, a timestamping service as an authentication service. The timestamping service is a service that adds a timestamp token to data (for example, a file) sent to the authentication server 20. A timestamp token is data that includes a hash value calculated from the data to which the timestamp token is to be added, and time information indicating the time when the hash value was calculated. The hash value is the return value of a hash function that generates a fixed-length bit string calculated from a bit string of arbitrary length by a predetermined operation. The timestamp token makes it possible to verify the existence of the data and that the data has not been tampered with. Specifically, it is proven that the data from which the hash value was calculated existed at the time indicated by the time information contained in the timestamp token. Furthermore, if the hash value contained in the timestamp token matches the hash value calculated from the data to which the timestamp is to be added, it is proven that the data has not been changed (tampered with) since the time the timestamp was added. In this embodiment, the timestamp token is also referred to as a timestamp. In this embodiment, the service provided by the authentication server 20 is described as a timestamping service.

[0020] The cloud server 30 provides a service for storing data transmitted from other devices. The cloud server 30 may be a server that provides online storage (cloud storage) services, or a mail server that provides mail services. In this specification, the services provided by the cloud server 30 are referred to as cloud services.

[0021] Furthermore, the multifunction printer 10 will have a function to link with cloud services. This function allows the multifunction printer 10 to send data it manages to a cloud service, thereby storing the data in the cloud service. In particular, the multifunction printer 10 of this embodiment will be described as being able to store (link) received fax data (facsimile data; also called received fax data) in a cloud service as part of its cloud service linkage function.

[0022] System 1 may include multiple different cloud services. In this case, a cloud server 30 is connected to the network NW for each cloud service. The multifunction printer 10 also has a function to cooperate with each individual cloud service.

[0023] [1.2 Functional Configuration] [1.2.1 Multifunction device] Figure 2 shows the functional configuration of the multifunction device 10 in this embodiment. The multifunction device 10 comprises a control unit 100, an image input unit 120, an image forming unit 130, a display unit 140, an operation unit 150, a storage unit 160, a line communication unit 180, and a network communication unit 190.

[0024] The control unit 100 is a functional unit for controlling the entire multifunction device 10. The control unit 100 realizes various functions by reading and executing various programs stored in the memory unit 160, and is composed of, for example, one or more arithmetic units (CPU (Central Processing Unit)). The control unit 100 may also be configured as a SoC (System on a Chip) having multiple functions among those described below.

[0025] The control unit 100 functions as an image processing unit 102 and a verification unit 104 by executing a program stored in the storage unit 160.

[0026] The image processing unit 102 performs various image-related processing. For example, the image processing unit 102 performs sharpening and grayscale conversion processing on images input via the image input unit 120, the line communication unit 180, and the network communication unit 190.

[0027] The verification unit 104 verifies the authenticity of the data. Authenticity is the property that indicates that the data has not been tampered with, modified, deleted, or replaced. One method of verifying authenticity is to determine whether a hash value calculated from the data at one point in time matches a hash value calculated from the data at another point in time. A hash value is a value uniquely determined from the data by calculation using a predetermined algorithm (hash function). For example, a hash function such as SHA-2 can be used. In this case, if the two hash values ​​match, it can be proven that the two data are identical and have not been tampered with, modified, deleted, or replaced. On the other hand, if the two hash values ​​do not match, there is a possibility that the data has been tampered with, modified, deleted, or replaced.

[0028] For example, the verification unit 104 sends the data to be verified for authenticity to the timestamp service and executes a process to obtain a timestamp token for the data from the timestamp service. Furthermore, the verification unit 104 calculates the hash value of the data to be verified for authenticity. The hash calculation method (hash function) used by the verification unit 104 is the same as the hash calculation method (hash function) used by the timestamp service. In this case, if the hash value contained in the timestamp token obtained from the timestamp service matches the hash value calculated by the verification unit 104, then the data sent to the timestamp service and the data that the verification unit 104 used for hash value calculation match. If the hash values ​​are the same, it can be presumed that the data used for hash value calculation has not been tampered with, and the authenticity of the data can be confirmed (verified). Thus, the hash value is identification information that can be used to identify the identity of data. The processes executed by the verification unit 104 will be described later.

[0029] The image input unit 120 inputs images to the multifunction printer 10. The image input unit 120 is composed of, for example, a scanner device that reads a document placed on the document glass. The scanner device is a device that converts an image into an electrical signal using an image sensor such as a CCD (Charge Coupled Device) or CIS (Contact Image Sensor), and then quantizes and encodes the electrical signal. The image input unit 120 is also composed of an interface (terminal) for reading images stored in a USB (Universal Serial Bus) memory, and images may be input by reading from the USB memory. Alternatively, the image input unit 120 may also input images by receiving them from other devices via the network communication unit 190.

[0030] The image forming unit 130 forms (prints) an image on a recording medium such as recording paper. The image forming unit 130 is composed of a printing device such as a laser printer using an electrophotographic method. For example, the image forming unit 130 feeds recording paper from a paper tray provided in the multifunction printer 10, forms an image on the surface of the recording paper, and ejects the recording paper from an output tray provided in the multifunction printer 10.

[0031] The display unit 140 displays various information. The display unit 140 is composed of a display device such as an LCD (Liquid Crystal Display), an organic EL (Organic Electro-Luminescence) display, or a micro-LED (Micro Light Emitting Diode) display.

[0032] The operation unit 150 receives operation instructions from the user of the multifunction printer 10. The operation unit 150 is composed of input devices such as key switches (hard keys) and touch sensors. The method for detecting input by contact (touch) in the touch sensor can be any common detection method, such as resistive, infrared, electromagnetic induction, or capacitive touch. The multifunction printer 10 may also be equipped with a touch panel in which the display unit 140 and the operation unit 150 are integrally formed.

[0033] The storage unit 160 stores various programs and data necessary for the operation of the multifunction printer 10. The storage unit 160 is composed of storage devices such as a semiconductor memory SSD (Solid State Drive) or an HDD (Hard Disk Drive).

[0034] The memory unit 160 reserves a FAX data storage area 162 as a storage area and stores authentication service usage information 164 and cloud service usage information 166.

[0035] The FAX data storage area 162 stores FAX data. FAX data is data transmitted and received via facsimile communication, and is image data representing text and images such as FAX documents and FAX images. Facsimile communication can be performed using, for example, a facsimile line that supports the G3 / G4 standard, or by using Internet FAX via the Internet network.

[0036] Furthermore, information related to the fax data may be stored within the fax data itself. For example, the fax data may include attribute information such as the date and time the fax data was received, and sender information (TSI, Transmitting Subscriber Identification).

[0037] Sender information is information that indicates the source (sender) of the fax data. For example, it may be the telephone number (fax number) of the sender of the fax data, or the name (sender name) corresponding to that telephone number (fax number) may be used. The information indicating the sender may be the sender name (RTI) or sender fax number (CSI) included in the sender information (TSI). Alternatively, an address book may be stored in the storage unit 160 in advance, and the names etc. stored in the address book may be used as sender information.

[0038] Authentication service usage information 164 is information used to use the authentication service. For example, authentication service usage information 164 includes information about the connection destination of the authentication server 20 (e.g., URL (Uniform Resource Locator) or IP (Internet Protocol) address) and authentication information used when using the authentication service (e.g., username and password).

[0039] Cloud service usage information 166 is information used to use cloud services. For example, cloud service usage information 166 includes information about the connection destination of the cloud server 30 (e.g., URL or IP address) and authentication information used when using the cloud service (e.g., username or password).

[0040] The communication unit 180 communicates with external devices via a public network (for example, a regular telephone line). The communication unit 180 is composed of, for example, terminals into which a cable that can be connected to a public network can be inserted.

[0041] The network communication unit 190 communicates with other devices and equipment, such as the authentication server 20, via a network such as a LAN or WAN. The network communication unit 190 is composed of communication devices and communication modules, such as a NIC (Network Interface Card) used in wired / wireless LANs. The network communication unit 190 may also have an interface (network I / F) that can connect to a network.

[0042] [1.2.2 Authentication Server] Figure 3 shows the functional configuration of the authentication server 20 in this embodiment. The authentication server 20 comprises a control unit 200, a storage unit 260, and a network communication unit 290.

[0043] The control unit 200 is a functional unit for controlling the entire authentication server 20. The control unit 200 realizes various functions by reading and executing various programs stored in the storage unit 260, and is composed of, for example, one or more arithmetic units (CPUs). The control unit 200 may also be configured as an SoC having multiple functions among those described below.

[0044] The control unit 200 functions as an authentication service provision unit 202 and a time management unit 204 by executing a program stored in the storage unit 260.

[0045] The authentication service provider unit 202 provides authentication services. For example, the authentication service provider unit 202 provides a timestamping service. In this case, the authentication service provider unit 202 calculates a hash value for data received from another device using a function such as SHA-2. The authentication service provider unit 202 also attaches a timestamp token, which includes the calculated hash value and the time the hash value was calculated, to the data for which the hash value was calculated. The hash function used by the authentication service provider unit 202 is specified in advance by the service administrator or the like. The processing performed by the authentication service provider unit 202 will be described later.

[0046] The time management unit 204 manages the time on the authentication server 20. For example, in parallel with the authentication service provision unit 202's processing of timestamp assignment services, the time management unit 204 periodically synchronizes the time on the authentication server 20 with the time on the NTP (Network Time Protocol) server. In this way, the time management unit 204 periodically adjusts the time on the authentication server 20.

[0047] The storage unit 260 stores various programs and data necessary for the operation of the authentication server 20. The storage unit 260 is composed of storage devices such as a semiconductor memory SSD or HDD. The storage unit 260 also reserves a received data storage area 262 as a storage area for storing data received from other devices.

[0048] The network communication unit 290 communicates with other devices and equipment, such as the multifunction printer 10, via a network such as a LAN or WAN. The network communication unit 290 is composed of communication devices and communication modules, such as NICs used in wired / wireless LANs. The network communication unit 290 may also have an interface (network I / F) that can connect to a network.

[0049] [1.2.3 Cloud Server] Figure 4 shows the functional configuration of the cloud server 30 in this embodiment. The cloud server 30 is composed of a control unit 300, a storage unit 360, and a network communication unit 390.

[0050] The control unit 300 is a functional unit for controlling the entire cloud server 30. The control unit 300 realizes various functions by reading and executing various programs stored in the memory unit 360, and is composed of, for example, one or more arithmetic units (CPUs). The control unit 300 may also be configured as an SoC having multiple functions from among the functions described below.

[0051] The control unit 300 functions as a service provider 302 by executing a program stored in the storage unit 360. The service provider 302 provides a service for storing data received from external devices. For example, the service provider 302 provides online storage (cloud storage) services and email services. The processes performed by the service provider 302 will be described later.

[0052] The storage unit 360 stores various programs and data necessary for the operation of the cloud server 30. The storage unit 360 is composed of storage devices such as a semiconductor memory SSD or HDD. The storage unit 360 also reserves a received data storage area 362 as a storage area for storing data received from other devices.

[0053] The network communication unit 390 communicates with other devices and equipment, such as the multifunction printer 10, via a network such as a LAN or WAN. The network communication unit 390 is composed of communication devices and communication modules, such as NICs used in wired / wireless LANs. The network communication unit 390 may also have an interface (network I / F) that can connect to a network.

[0054] [1.3 Processing Flow] [1.3.1 Overall Flow] Figure 5 is a sequence diagram showing the processing flow executed by the devices included in System 1. In this embodiment, when the multifunction printer 10 receives FAX data (D100 in Figure 5) (S1000), it stores the FAX data in the FAX data storage area 162 (S1002). Furthermore, the multifunction printer 10 sends a request to the timestamp service to add a timestamp token to the FAX data received in S1000 (timestamp request) (S1004). At this time, the multifunction printer 10 sends the FAX data received in S1000 to the timestamp service.

[0055] When the authentication server 20 receives a timestamp request from the multifunction printer 10, it issues a timestamp token for the FAX data sent from the multifunction printer 10 and associates it with the FAX data. The timestamp token may be managed separately from the FAX data or attached to the FAX data, but in this embodiment, it will be described as the timestamp token being attached to the FAX data. The timestamp service also stores the data with the timestamp token attached to the FAX data (D102 in Figure 5). Furthermore, the timestamp service sends a response to the multifunction printer 10, which is the source of the timestamp request (S1006).

[0056] When the multifunction printer 10 receives a response from the timestamp service, it sends a request to the timestamp service to download the fax data with the timestamp token (download request) (S1008). When the timestamp service receives the download request from the multifunction printer 10, it sends the requested data back to the multifunction printer 10 as a response (S1010). As a result, the multifunction printer 10 obtains the fax data with the timestamp token (D104 in Figure 5).

[0057] Next, the multifunction printer 10 calculates a hash value from the FAX data stored in step S1002 (S1012). Then, the multifunction printer 10 compares the hash value calculated in step S1012 with the hash value contained in the timestamp token.

[0058] If the hash values ​​do not match, the multifunction printer 10 issues an alert (step S1014). On the other hand, if the hash values ​​do match, the multifunction printer 10 sends a request to the cloud service to upload the FAX data with the timestamp token attached (upload request) (S1016).

[0059] When the cloud server 30 receives an upload request from the multifunction printer 10, it stores the fax data with a timestamp token attached that was sent from the multifunction printer 10 (D106 in Figure 5) and sends a response to the multifunction printer 10 (S1018).

[0060] When the multifunction printer 10 receives a response from the cloud service, it deletes the FAX data corresponding to the uploaded data (the FAX data stored in step S1002) from the FAX data storage area 162 (S1020). This deletes the FAX data uploaded to the cloud service from the multifunction printer 10. The processes performed by each device included in System 1 are described below.

[0061] [1.3.2 Processing Flow of a Multifunction Printer] Figure 6 is a flowchart showing the flow of the main processing performed by the multifunction printer 10. The processing shown in Figure 6 is performed when the control unit 100 reads a program stored in the memory unit 160, and is particularly executed when the multifunction printer 10 receives fax data.

[0062] First, the control unit 100 determines whether or not a fax has been received (step S100). Here, receiving a fax means that the multifunction printer 10 receives fax data sent from an external device via the line communication unit 180 or the network communication unit 190. If the control unit 100 does not receive a fax, it repeats step S100 (step S100; No).

[0063] On the other hand, when the control unit 100 receives a fax, it stores the received fax data in the fax data storage area 162 (step S100; Yes → step S102). At this time, the control unit 100 may store sender information as attribute information of the fax data.

[0064] Next, the control unit 100 (verification unit 104) sends a timestamp assignment request to the authentication server 20 via the network communication unit 190 (step S104). At this time, the control unit 100 sends the FAX data received in step S102 to the authentication server 20 in association with the timestamp assignment request as the data to which a timestamp token will be assigned. Note that step S104 may be executed immediately after the FAX data is stored, or it may be executed when the user performs an operation to store the FAX data in the cloud service.

[0065] Next, the control unit 100 (verification unit 104) determines whether or not it has received a response from the authentication server 20 via the network communication unit 190 (step S106). In step S106, the response received from the authentication server 20 is a response indicating that a timestamp token has been attached to the data sent to the authentication server 20. If the authentication server 20 does not respond, the control unit 100 repeats step S106 (step S106; No).

[0066] When the control unit 100 (verification unit 104) receives a response from the authentication server 20, it sends a download request to the authentication server 20 via the network communication unit 190 (step S106; Yes → step S108). At this time, the control unit 100 sends information indicating that the target of the download request is the FAX data sent in step S104 to which a timestamp token has been added, in association with the download request.

[0067] Next, the control unit 100 (verification unit 104) starts downloading the data requested in step S108 via the network communication unit 190 and determines whether the download of the data has been completed (step S110). If the download is not completed, the control unit 100 repeats step S110 (step S110; No). As a result, the verification unit 104 can obtain a timestamp token including the hash value from the timestamp assignment service.

[0068] If the download is complete, the control unit 100 (verification unit 104) calculates a hash value from the FAX data stored in step S102 (step S110; Yes → step S112).

[0069] Next, the control unit 100 (verification unit 104) compares the hash value calculated in step S112 with the hash value contained in the data downloaded in step S110, and determines whether the two compared hash values ​​match (step S114). If the two compared hash values ​​match, the verification unit 104 can confirm (verify) that the FAX data stored in step S102 matches the FAX data contained in the data downloaded in step S110, and that the authenticity of the FAX data stored in step S102 is confirmed.

[0070] If the two hash values ​​compared in step S112 match, that is, if the authenticity of the FAX data stored in step S102 is confirmed, the control unit 100 sends an upload request to the cloud server 30 via the network communication unit 190 (step S114; Yes → step S116). At this time, the control unit 100 sends the data downloaded in step S110 (FAX data with a timestamp token) to the cloud server 30 as the data to be uploaded, in association with the upload request.

[0071] Next, the control unit 100 determines whether or not it has received a response from the cloud server 30 via the network communication unit 190 (step S118). The response received from the cloud server 30 at this time is a response that includes information (response information) indicating that the data sent to the cloud server 30 has been stored (linked) in the cloud server 30. If the control unit 100 does not receive a response from the cloud server 30, it repeats step S118 (step S118; No).

[0072] When the control unit 100 receives a response from the cloud server 30, it deletes the FAX data stored in step S102 from the FAX data storage area 162 (step S118; Yes → step S120). This allows the control unit 100 to confirm that the FAX data has been stored (linked) to the cloud service and then delete the FAX data from the FAX data storage area 162. In other words, the FAX data is stored on the cloud server 30 and is not stored on the multifunction printer 10.

[0073] Furthermore, in step S114, if the control unit 100 determines that the two hash values ​​compared in step S112 do not match, it issues an alert (step S114; No → step S122). For example, the control unit 100 displays on the display unit 140 a message indicating that there is an abnormality in the FAX data or a message indicating that the FAX data was not stored in the cloud server 30. However, if the FAX data is received and an alert is issued while the user is operating the multifunction printer 10, it may interfere with the user's operation. Therefore, as a method of notifying the alert, the control unit 100 may display an icon for displaying a message containing the content of the alert in a predetermined area of ​​the display unit 140, and when the icon is selected, the message is displayed on the display unit 140.

[0074] The control unit 100 may also send an email containing a message indicating that an abnormality has occurred in the fax data to the user operating the multifunction printer 10 or the administrator of the multifunction printer 10 as a method of notifying alerts. Alternatively, the control unit 100 may notify the multifunction printer 10 or other devices of the alert by emitting a sound or illuminating an indicator.

[0075] If the two hash values ​​compared in step S114 do not match, an alert is issued, and the FAX data stored in step S102 is not deleted but remains stored in the FAX data storage area 162. In this case, the user can check the contents of the alert and print an image based on the FAX data stored in the FAX data storage area 162 onto recording paper (paper output), or manually transfer the FAX data to another device.

[0076] Furthermore, the control unit 100 may display a message indicating that the fax data has been uploaded to the cloud service if it has been successfully uploaded. Additionally, if the control unit 100 receives multiple fax data, it may display a message or screen indicating the number of fax data files that were successfully uploaded to the cloud service, as well as the number of fax data files that could not be uploaded.

[0077] [1.3.3 Processing Flow of the Authentication Server] Figure 7 is a flowchart showing the flow of the main processing performed by the authentication server 20. The processing shown in Figure 7 is performed by the control unit 200 reading a program stored in the storage unit 260, and is repeatedly performed while the timestamp assignment service is being provided.

[0078] First, the control unit 200 (authentication service provision unit 202) determines whether or not it has received a timestamp assignment request from another device via the network communication unit 290 (step S140).

[0079] When the control unit 200 (authentication service provider unit 202) receives a timestamp assignment request, it calculates the hash value of the received data as the data to which a timestamp token will be assigned (step S140; Yes → step S142). The data to which a timestamp token will be assigned is, for example, transmitted from another device in association with the timestamp assignment request received in step S140.

[0080] Next, the control unit 200 (authentication service provision unit 202) adds a timestamp token to the data received as data to which a timestamp token is to be added (step S144).

[0081] Next, the control unit 200 (authentication service provider unit 202) stores the data to which the timestamp token was added in step S144 in the received data storage area 362 (step S146). Furthermore, the control unit 200 (authentication service provider unit 202) sends a response to the device that sent the timestamp request via the network communication unit 290 indicating that the data to which the timestamp token was added has been stored (step S148).

[0082] Furthermore, if the control unit 200 (authentication service provision unit 202) determines in step S140 that no other device has requested timestamp assignment, it omits the processing from steps S142 to S148 (step S140; No).

[0083] Next, the control unit 200 (authentication service provider unit 202) determines whether or not it has received a download request from another device via the network communication unit 290 (step S150). If the control unit 200 (authentication service provider unit 202) has received a download request, it sends the data that is the subject of the download request to the device that sent the download request (step S150; Yes → step S152). If the control unit 200 (authentication service provider unit 202) determines in step S150 that it has not received a download request, it omits the processing in step S152 (step S150; No).

[0084] [1.3.4 Cloud Server Processing Flow] Figure 8 is a flowchart showing the flow of the main processing performed by the cloud server 30. The processing shown in Figure 8 is performed by the control unit 300 reading a program stored in the memory unit 360, and is executed repeatedly while the cloud service is being provided.

[0085] The control unit 300 (service provision unit 302) determines whether or not it has received an upload request from another device via the network communication unit 390 (step S180). If the control unit 300 (service provision unit 302) does not receive an upload request, it repeats step S180 (step S180; No).

[0086] When the control unit 300 (service provision unit 302) receives an upload request, it stores the data received as data to be uploaded in the received data storage area 362 (step S180; Yes → step S182). The data to be uploaded is transmitted from another device, for example, in association with the upload request received in step S180. Furthermore, the control unit 300 (service provision unit 302) sends a response to the device that sent the upload request via the network communication unit 390 indicating that the upload has been completed (step S184).

[0087] Furthermore, even if the steps are not as described above, the order of the steps may be changed or some steps omitted, as long as it is not inconsistent. For example, if the response (S1006 in Figure 5) to the timestamp assignment request (S1004 in Figure 5) of the multifunction printer 10 is an error response, the multifunction printer 10 may resend the timestamp assignment request (S1004 in Figure 5). Alternatively, steps S1006 and S1008 in Figure 5 may be omitted, and the authentication server 20 may send data with a timestamp token attached as a response to the timestamp assignment request (S1004 in Figure 5) (S1008 in Figure 5).

[0088] [1.4 Example of Operation] Figure 9 is a diagram showing an example of operation in this embodiment, and is a diagram showing the display screen displayed on the display unit 140 of the multifunction device 10.

[0089] The screen W100 shown in Figure 9(a) is an example of a screen that includes a button B100 indicating that the fax data could not be stored in the cloud service. Button B100 contains text such as "Fax data linkage error". By checking button B100, the user can be informed that the fax data could not be linked (an alert). Screen W100 is displayed in step S122 of Figure 6.

[0090] The screen W110 shown in Figure 9(b) is an example of a screen displayed when button B100 in Figure 9(a) is selected. The message M110, indicating that the FAX data was not stored in the cloud service, is displayed as an alert on screen W110. Note that if the FAX data could not be stored in the cloud service, the multifunction printer 10 may display screen W110 without displaying screen W100, which includes button B100.

[0091] Furthermore, a notification may also be issued when the fax data is stored in the cloud service. For example, when the fax data is stored in the cloud service, screen W120 shown in Figure 9(c) may be displayed. Screen W120 includes message M120 indicating that the fax data has been stored in the cloud service and deleted from the multifunction printer 10. By checking message M120, the user can be informed that the fax data has been stored in the cloud service and deleted from the multifunction printer 10.

[0092] In the above explanation, it was stated that when FAX data with a timestamp token is downloaded from the timestamp service, the hash value contained in the timestamp token is compared with the hash value calculated from the FAX data stored in the storage unit 160. However, the timing of the hash value comparison may be when the FAX data with the timestamp token is uploaded to the cloud service. In this case, the multifunction printer 10 links the FAX data with the timestamp token to the cloud service, which is the linked service, based on the authentication information and the FAX data (FAX information). The cloud service, on the other hand, sends response information to the multifunction printer 10 indicating that the link has been made. The response information will include the hash value of the FAX data. If the hash value included in the response information matches the hash value calculated from the FAX data received from the external device, the multifunction printer 10 deletes the FAX data from the multifunction printer 10; otherwise, it sends an alert. Even in this manner, the multifunction printer 10 can determine whether the fax data transferred to the cloud service matches the received fax data, and if they match, it can prove that the fax data transferred to the cloud service has not been tampered with. However, if the user has set the device to delete faxes without determining (confirming) whether the hash values ​​match, the multifunction printer 10 may omit the determination of whether the hash values ​​match and the notification of an alert, and delete the received fax data.

[0093] Furthermore, the above explanation described comparing the hash value contained in the timestamp token with the hash value calculated from the FAX data (local FAX information) stored by the multifunction printer 10. Since the timestamp token contains time information, it is possible to prove the existence of the FAX data at the time indicated by that time information.

[0094] Furthermore, the above explanation described the use of a timestamp token, assuming that authenticity clarifies two things: that the data has not been tampered with and that the FAX data existed at the time indicated by the time information. However, authenticity may be confirmed by other methods. For example, if authenticity only requires confirmation (verification) that the FAX data has not been tampered with, an electronic signature may be used instead of a timestamp token. In this case, the multifunction printer 10 sends the FAX data to a service that adds electronic signatures to data, and receives the FAX data with an electronic signature (hash value) from that service. The multifunction printer 10 then compares the electronic signature (hash value) with the hash value calculated from the FAX data stored in the multifunction printer 10 (local FAX information). If the two hash values ​​match, the multifunction printer 10 can determine that the FAX data has not been tampered with and can confirm its authenticity. The multifunction printer 10 can then transfer the verified FAX data to a cloud service and delete the FAX data from the multifunction printer 10. Furthermore, as a measure of authenticity, it may be necessary to verify whether or not the sender of the fax data is legitimate.

[0095] Thus, the multifunction printer of this embodiment can prevent the printing of images based on fax data by transferring (linking) the received fax data to a cloud service and then deleting the fax data. Furthermore, the multifunction printer of this embodiment deletes the fax data from the printer after transferring (linking) the received fax data to a cloud service. In other words, the multifunction printer of this embodiment does not need to retain the fax data after transferring it to a cloud service until the image based on the fax data is printed on paper. As a result, the multifunction printer of this embodiment can improve the efficiency of its memory usage and receive and process more fax data.

[0096] Furthermore, the multifunction printer of this embodiment can prove that data uploaded to a cloud service has not been tampered with (proof of non-tampering) using identification information that indicates the identity of the data, such as a hash value. In this case, when fax data with a timestamp token is uploaded, it becomes possible to prove the existence of the fax data at the time indicated by the time information contained in the timestamp token.

[0097] [2. Second Embodiment] Next, a second embodiment will be described. The second embodiment is an embodiment in which, in the process described in the first embodiment, when fax data is stored in the cloud service, the storage destination is sorted according to the fax sender. In this embodiment, Figure 2 of the first embodiment is replaced with Figure 10, and Figure 6 of the first embodiment is replaced with Figure 12. The same reference numerals are used for the same functional parts and processes, and their descriptions are omitted.

[0098] [2.1 Functional Configuration] Figure 10 shows the functional configuration of the multifunction device 12 in this embodiment. The multifunction device 12 differs from the multifunction device 10 of the first embodiment in that the storage unit 160 is further equipped with a storage destination information storage area 168.

[0099] The storage location information storage area 168 stores information about the storage location of the FAX data (storage location information). As shown in Figure 11, the storage location information includes, for example, sender information that identifies the sender (e.g., "03-3000-AAAA") and a folder name that indicates the storage location (storage area) of the FAX data sent by that sender (e.g., [User A] folder).

[0100] Sender information can identify the sender who sent the fax data, and may include, for example, a telephone number (fax number) or the sender's or source's email address. Sender information may also include the sender's name or company name, or information indicating the type of line from which the fax data was sent.

[0101] [2.2 Processing Flow] [2.2.1 Multifunction device] Figure 12 is a flowchart showing the main processing flow of the multifunction printer 12 in this embodiment. In this embodiment, if the two hash values ​​compared in step S112 match, the control unit 100 obtains the folder name where the FAX data is stored (step S114; Yes → step S200).

[0102] For example, in step S200, the control unit 100 performs two processes: (1) a process to acquire sender information, and (2) a process to read storage destination information containing the acquired sender information and acquire the folder name included in the read storage destination information.

[0103] For example, the control unit 100 retrieves sender information stored as attribute information of the FAX data, or retrieves sender information from the FAX data received in step S100. The control unit 100 also reads the storage destination information, including the retrieved sender information, from the storage destination information storage area 168, and retrieves the storage destination folder name included in the retrieved storage destination information.

[0104] Next, the control unit 100 specifies the folder name obtained in step S200 as the destination folder name and sends an upload request to the cloud server 30 (step S202). In this way, the control unit 100 can cause the cloud service to store the FAX data in the storage area (folder) corresponding to the sender, according to the sender information, which is the information of the sender of the FAX data.

[0105] In addition, the control unit 100 may not be able to obtain the name of the folder where the FAX data will be stored in step S200, for example, when it receives FAX data from a user who has not specified a storage folder. In such cases, the control unit 100 may send an upload request to the cloud server 30 without specifying a folder name.

[0106] [2.2.2 Cloud Server] The cloud server 30 executes the process shown in Figure 8. It is assumed that a folder has already been added to the received data storage area 362.

[0107] In step S180, the control unit 300 (service provision unit 302) may receive an upload request in which the name of the destination folder is specified. In this case, as processing in step S182, the control unit 300 (service provision unit 302) executes a process to store the received data as data to be uploaded in the folder with the name of the destination folder specified.

[0108] Furthermore, if the control unit 300 (service provision unit 302) receives an upload request in step S180 in which the destination folder name is not specified, it should execute a process to store the received data in a predetermined folder.

[0109] As a result of the process described above, the multifunction printer 12 sends an upload request to the cloud server 30, specifying a folder name corresponding to the sender of the fax data. The cloud server 30 then stores the fax data to be uploaded in the specified folder (storage area). For example, fax data sent from phone number A is stored in the phone number A folder of the cloud service, and fax data sent from phone number B is stored in the phone number B folder of the cloud service.

[0110] Thus, when fax data is stored on the cloud server 30, the multifunction printer of this embodiment can achieve folder sorting of the stored fax data by switching the storage location of the fax data according to the sender of the fax data.

[0111] [3. Third Embodiment] Next, a third embodiment will be described. The third embodiment is an embodiment in which the cloud service used is switched according to the sender of the fax in the process described in the first embodiment. In this embodiment, Figure 2 of the first embodiment is replaced with Figure 13, and Figure 6 of the first embodiment is replaced with Figure 15. The same reference numerals are used for the same functional parts and processes, and their descriptions are omitted.

[0112] Furthermore, in this embodiment, the multifunction printer 14, which will be described later, is capable of using multiple cloud services. Specifically, multiple cloud servers 30 are connected to system 1. The multifunction printer 14 can also connect to multiple cloud servers 30.

[0113] [3.1 Functional Configuration] Figure 13 shows the functional configuration of the multifunction printer 14 in this embodiment. Unlike the multifunction printer 10 of the first embodiment, the multifunction printer 14 differs in that, instead of storing cloud service usage information 166 in the storage unit 160, it further includes a cloud service information storage area 170.

[0114] The cloud service information storage area 170 stores information about the cloud service that will be used to store the FAX data (cloud service information). As shown in Figure 14, the cloud service information includes, for example, the service name of the cloud service (e.g., "AAA Drive"), the access destination indicating the communication destination for using the cloud service (e.g., "https: / / aaadrive.com / upload"), the authentication information used for authentication when using the cloud service (e.g., "ID: a-sha, PW: abc123"), and the sender information of the FAX data (e.g., "03-3000-XXXX, userA@example.com").

[0115] Thus, the multifunction printer 14 of this embodiment supports the registration of multiple cloud services and can switch between cloud services according to the sender information. In the example in Figure 14, fax data sent by a user with the phone number "03-3000-AAAA" is stored in "AAA Drive," and fax data sent by a user with the phone number "03-3000-BBBB" is stored in "BBB Drive."

[0116] Furthermore, as shown in D300 and D302 of Figure 14, two or more cloud services may be associated with a single user. In the example in Figure 14, fax data sent by a user with the email address "userC@exmpale.com" is stored in "AAA Drive" and "CCC Service". Fax data sent by a user with the email address "userD@exmpale.com" is stored in "BBB Drive" and also sent to the email service "DDD Mail".

[0117] Furthermore, as shown in D304 of Figure 14, the cloud service information storage area 170 may store information about the cloud service used when receiving fax data that includes sender information other than that of a specific sender.

[0118] [3.2 Processing Flow] Figure 15 is a flowchart showing the main processing flow of the multifunction printer 14 in this embodiment. In this embodiment, if the two hash values ​​compared in step S112 match, the control unit 100 identifies the cloud service corresponding to the sender of the FAX data (step S114; Yes → step S300). For example, the control unit 100 retrieves the sender information of the FAX data stored in step S102. Furthermore, the control unit 100 reads the cloud service information, including the retrieved sender information, from the cloud service information storage area 170. As a result, the control unit 100 can identify the cloud service corresponding to the sender of the FAX data and retrieve information about that cloud service.

[0119] Next, the control unit 100 sends an upload request to the cloud service identified in step S300 (step S302). For example, the control unit 100 connects to the cloud service using the access destination information and authentication information contained in the cloud service information read in step S300, and sends an upload request to the cloud service for the FAX data with a timestamp token. In this way, the control unit 100 can cause the cloud service to store the FAX data in the cloud service corresponding to the sender, according to the sender information, which is the information of the sender of the FAX data. Furthermore, if two or more cloud services are associated with one sender information, the FAX data can be stored in two or more of the multiple cloud services, according to the sender information, which is the information of the sender of the FAX data.

[0120] Furthermore, each cloud server 30 that communicates with the multifunction printer 14 provides the service by executing the process shown in Figure 8. As a result, each cloud server 30 stores the FAX data received from the multifunction printer 14 in response to upload requests from the multifunction printer 14.

[0121] Thus, the multifunction printer of this embodiment can switch the cloud service to which the fax data is transferred, depending on the sender of the fax.

[0122] [4. Fourth Embodiment] Next, the fourth embodiment will be described. Unlike the first embodiment, the fourth embodiment is an embodiment in which the multifunction printer uploads fax data to a cloud service via an intermediate server. In this embodiment, Figure 1 of the first embodiment is replaced with Figure 16, Figure 2 of the first embodiment with Figure 17, Figure 5 of the first embodiment with Figure 19, and Figure 6 of the first embodiment with Figure 20. The same reference numerals are used for the same functional parts and processes, and their descriptions are omitted.

[0123] [4.1 Overall Structure] Figure 16 shows the overall configuration of System 2 in this embodiment. System 2 differs from System 1 shown in Figure 1 in that a multifunction printer 16 is connected to the network NW instead of the multifunction printer 10, and an intermediate server 40 is also connected.

[0124] The intermediate server 40 is a server that transmits data received from the multifunction printer 16 to the cloud service. The intermediate server 40 is composed of computers such as servers. The intermediate server 40 may be composed of multiple devices, or it may be composed of virtual servers implemented on any information processing device.

[0125] Furthermore, the multifunction printer 16 of this embodiment has a function to cooperate with an intermediate server 40. The function to cooperate with the intermediate server 40 is to send fax data to the intermediate server 40 when fax data is received.

[0126] [4.2 Functional Configuration] [4.2.1 Multifunction device] Figure 17 shows the functional configuration of the multifunction printer 16 in this embodiment. Unlike the multifunction printer 10 of the first embodiment, the multifunction printer 16 differs in that, instead of storing cloud service usage information 166 in the storage unit 160, intermediate server information 172 is stored.

[0127] Intermediate server information 172 is information about intermediate server 40. Intermediate server information 172 is information used to connect to intermediate server 40. For example, intermediate server information 172 includes information about the connection destination of intermediate server 40 (e.g., URL or IP address).

[0128] [4.2.2 Intermediate Server] Figure 18 shows the functional configuration of the intermediate server 40 in this embodiment. The intermediate server 40 is comprised of a control unit 400, a storage unit 460, and a network communication unit 490.

[0129] The control unit 400 is a functional unit for controlling the entire intermediate server 40. The control unit 400 realizes various functions by reading and executing various programs stored in the storage unit 460, and is composed of, for example, one or more arithmetic units (CPUs). The control unit 400 may also be configured as an SoC having multiple functions among those described below.

[0130] The storage unit 460 stores various programs and data necessary for the operation of the intermediate server 40. The storage unit 460 is composed of storage devices such as a semiconductor memory SSD or HDD.

[0131] The memory unit 460 reserves a received data storage area 462 as a storage area and stores cloud service usage information 464 therein.

[0132] The received data storage area 462 stores data received from the multifunction printer 16. The cloud service usage information 464 is information used to access cloud services. The cloud service usage information 464 is the same as the cloud service usage information 166 in the first embodiment.

[0133] The network communication unit 490 communicates with other devices and equipment, such as the multifunction printer 16, via a network such as a LAN or WAN. The network communication unit 490 is composed of communication devices or communication modules, such as a NIC (Network Interface Card) used in wired / wireless LANs. The network communication unit 490 may also have an interface (network I / F) that can connect to a network.

[0134] [4.3 Processing Flow] [4.3.1 Overall Flow] Figure 19 is a sequence diagram showing the processing flow executed by the devices included in System 2. In this embodiment, if the hash value calculated from the FAX data matches the hash value contained in the timestamp token attached to the FAX data, the multifunction printer 16 sends an upload request to the intermediate server 40 (S4000). At this time, the multifunction printer 16 sends the data to be uploaded (FAX data with a timestamp token attached) to the intermediate server 40, associating it with the upload request. As a result, the intermediate server 40 obtains the upload request and the FAX data with a timestamp token attached (D400 in Figure 19) from the multifunction printer 16.

[0135] When the intermediate server 40 receives an upload request from the multifunction printer 16, it sends an upload request to the cloud service, treating the data sent from the multifunction printer 16 as the data to be uploaded (S4002). At this time, the intermediate server 40 sends the data to be uploaded (FAX data with a timestamp token) to the cloud service, associating it with the upload request.

[0136] When the cloud server 30 receives an upload request from the intermediate server 40, it stores the fax data with a timestamp token attached that was sent from the intermediate server 40 (D402 in Figure 19) and sends a response to the intermediate server 40 (S4004).

[0137] When the intermediate server 40 receives a response from the cloud service, it sends a response to the multifunction printer 16 (S4006). When the multifunction printer 16 receives a response from the intermediate server 40, it deletes the FAX data corresponding to the data uploaded to the intermediate server 40 (the FAX data stored in step S1002) from the FAX data storage area 162.

[0138] [4.3.2 Multifunction device] Figure 20 is a flowchart showing the main processing flow of the multifunction device 16 in this embodiment. In this embodiment, if the two hash values ​​compared in step S112 match, an upload request is sent to the intermediate server 40 (step S114; Yes → step S400).

[0139] Next, the control unit 100 determines whether or not it has received a response from the intermediate server 40 via the network communication unit 190 (step S402). The response received from the intermediate server 40 at this time is a response indicating that the data sent to the intermediate server 40 has been stored (linked) in the cloud server 30. If the intermediate server 40 does not respond, the control unit 100 repeats step S402 (step S402; No).

[0140] When the control unit 100 receives a response from the intermediate server 40, it deletes the FAX data stored in step S102 from the FAX data storage area 162 (step S402; Yes → step S120).

[0141] [4.3.3 Intermediate Server] Figure 21 is a flowchart showing the main processing flow of the intermediate server 40 in this embodiment. The processing shown in Figure 21 is executed by the control unit 400 reading a program stored in the storage unit 460, and is executed repeatedly.

[0142] First, the control unit 400 determines whether or not it has received an upload request from the multifunction printer 16 (step S440). If the control unit 400 does not receive an upload request from the multifunction printer 16, it repeats step S440 (step S440; No).

[0143] When the control unit 400 receives an upload request from the multifunction printer 16, it stores the data received from the multifunction printer 16 in the received data storage area 462 (step S440; Yes → step S442).

[0144] Next, the control unit 400 sends an upload request to the cloud server 30 via the network communication unit 490 (step S444). At this time, the control unit 400 sends the data received in step S440 (FAX data with a timestamp token) to the cloud server 30 as the data to be uploaded, in association with the upload request.

[0145] Next, the control unit 400 determines whether or not it has received a response from the cloud server 30 via the network communication unit 490 (step S446). The response received from the cloud server 30 at this time is a response indicating that the data sent to the cloud server 30 has been stored in the cloud server 30. If the cloud server 30 does not respond, the control unit 400 repeats step S446 (step S446; No).

[0146] When the control unit 400 receives a response from the cloud server 30, it deletes the FAX data stored in step S442 from the received data storage area 462 (step S446; Yes → step S448).

[0147] Next, the control unit 400 sends a response via the network communication unit 490 to the multifunction printer 16 that sent the upload request, indicating that the data sent to the intermediate server 40 has been stored (linked) in the cloud server 30 (step S450).

[0148] [4.3.4 Cloud Server] The cloud server 30 executes the process shown in Figure 8. In this embodiment, the upload request is sent from the intermediate server 40. Therefore, in step S180, the control unit 300 (service provision unit 302) receives the upload request from the intermediate server 40, and in step S184, sends a response to the intermediate server 40.

[0149] Thus, in this embodiment, the system has a function for coordinating with an intermediate server, and the intermediate server has a function for coordinating with individual cloud services. Therefore, even if the number of cloud services that the multifunction printer connects with increases, it is only necessary to modify the intermediate server, and the main functions of the multifunction printer are not affected.

[0150] The system of this embodiment may include multiple multifunction printers. In this case, each multifunction printer can communicate with an intermediate server and send fax data to a cloud service via the intermediate server. Since the intermediate server holds the cloud service information (cloud service usage information), if the number of cloud services communicating with the multifunction printers increases or changes, users such as system administrators only need to modify the cloud service usage information held by the intermediate server. This eliminates the need to change the settings of individual multifunction printers even if the number of cloud services communicating with the multifunction printers increases or changes, thereby reducing the costs and operations associated with changing settings.

[0151] [5. Variant] The present invention is not limited to the embodiments described above, and various modifications are possible. That is, embodiments obtained by combining technical means that are appropriately modified without departing from the spirit of the present invention are also included in the technical scope of the present invention.

[0152] Furthermore, although the embodiments described above are explained separately for the sake of explanation, they can, of course, be combined and implemented to the extent that is technically possible. For example, the second and third embodiments may be combined. In this case, the multifunction printer can switch between the cloud service and the storage location (storage area) within that cloud service depending on the sender. Also, the second or third embodiment may be combined with the fourth embodiment. In this case, the intermediate server switches the storage location of the fax data and the cloud service to be used based on the sender information contained in the fax data received from the multifunction printer.

[0153] Furthermore, in the embodiments, the programs that run in each device are programs that control the CPU and the like (programs that make the computer function) in order to realize the functions of the embodiments described above. The information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) during processing, and then stored in storage devices such as various ROMs (Read Only Memory) and HDDs, and read, modified, and written by the CPU as needed.

[0154] Here, the recording medium for storing the program may be any of the following: semiconductor media (e.g., ROM or non-volatile memory card), optical recording medium / magneto-optical recording medium (e.g., DVD (Digital Versatile Disc), MO (Magneto Optical Disc), MD (Mini Disc), CD (Compact Disc), BD (Blu-ray® Disc), etc.), magnetic recording medium (e.g., magnetic tape, flexible disk, etc.). Furthermore, in addition to realizing the functions of the above-described embodiment by executing the loaded program, the functions of the present invention may also be realized by processing in cooperation with the operating system or other application programs based on the instructions of the program.

[0155] Furthermore, when distributing the program to the market, it 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, also included in the present invention.

[0156] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuit may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of this disclosure may use new integrated circuits based on such technologies. [Explanation of symbols]

[0157] 1, 2 Systems 10, 12, 14, 16 multifunction device 100 Control Unit 102 Image Processing Unit 104 Verification Department 120 Image Input Section 130 Image forming unit 140 Display section 150 Operation section 160 Storage section 162 FAX data storage area 164 Authentication Service Usage Information 166 Cloud Service Usage Information 168 Storage destination information storage area 170 Cloud service information storage 172 Intermediate Server Information 180 Communication Section 190 Network Communications Department 20 Authentication Server 200 Control Unit 202 Authentication Service Provider 204 Time Management Department 260 Storage section 262 Received data storage area 290 Network Communications Department 30 Cloud Servers 300 Control Unit 302 Service Provision Department 360 storage section 362 Received data storage area 390 Network Communications Department 40 Intermediate Servers 400 Control Unit 460 Storage section 462 Received data storage area 464 Cloud Service Usage Information 490 Network Communications Department

Claims

1. A storage unit that stores the received facsimile data, A verification unit for verifying the authenticity of the facsimile data, When the authenticity of the facsimile data is confirmed, the control unit performs control to transmit the facsimile data to the service and delete only the facsimile data whose authenticity has been confirmed from the storage unit. Equipped with an image processing device.

2. The verification unit, The timestamp token assigned to the aforementioned facsimile data is obtained from the authentication service. The authenticity of the facsimile data is verified based on the aforementioned timestamp token. The image processing apparatus according to claim 1.

3. The aforementioned timestamp token includes a hash value, The verification unit verifies the authenticity of the facsimile data stored in the storage unit by determining whether the hash value generated from the facsimile data stored in the storage unit matches the hash value contained in the timestamp token. The image processing apparatus according to claim 2.

4. The aforementioned timestamp token includes time information assigned by the authentication service. The image processing apparatus according to claim 3.

5. Based on the fact that the control unit has received response information from the service indicating that the facsimile data has been linked to the service, it deletes only the facsimile data whose authenticity has been confirmed from the storage unit. The image processing apparatus according to claim 1.

6. The control unit, in accordance with the information of the sender who transmitted the facsimile data, causes the service to store the facsimile data in the storage area corresponding to the sender. The image processing apparatus according to claim 1.

7. The aforementioned service includes multiple services, The control unit transmits the facsimile data to the service corresponding to the sender, according to the information of the sender who sent the facsimile data. The image processing apparatus according to claim 1.

8. The control unit transmits the facsimile data to two or more of the services from among the multiple services, according to the information of the sender who sent the facsimile data. The image processing apparatus according to claim 7.

9. Including an image processing device and a server, The aforementioned image processing device is A memory unit for storing facsimile data, A verification unit for verifying the authenticity of the facsimile data, When the authenticity of the facsimile data is confirmed, the control unit performs control to send the confirmed authentic facsimile data to the server and delete only the confirmed authentic facsimile data from the storage unit. Equipped with, The aforementioned server, The transmission unit transmits the facsimile data whose authenticity has been verified to the service. An image processing system equipped with the following features.

10. A method for managing facsimile data, The steps include storing the received facsimile data in a storage device, The steps include verifying the authenticity of the facsimile data, When the authenticity of the facsimile data is confirmed, the facsimile data is sent to the service and only the facsimile data whose authenticity has been confirmed is deleted from the storage device. A method for managing facsimile data, including [specific data].

11. The method for managing facsimile data according to claim 10, wherein when the facsimile data is transmitted to the service, it is transmitted to a server device capable of communication, and the server device transmits the authentic facsimile data to the service.

Citation Information

Patent Citations

  • JP2004147019A

  • JP2013186613A

  • JP2016192644A