JP6083297B2 - Scanner and communication system - Google Patents

Description

  The present specification discloses a technique for storing scan data generated by a scanner in a server.

  A technique for storing (that is, uploading) scan data generated by a scanner in a server is known.

JP2008-236702 JP2003-32425A JP2011-192116A

  The present specification discloses a novel technique for storing scan data generated by a scanner in a server.

  The scanner disclosed in the present specification includes a scan execution unit, an account information reception unit, a login unit, an instruction reception unit, a scan control unit, a scan data transmission unit, and an account information transmission unit. The account information receiving unit executes both the first account information for logging in to the first server and the second account information for logging in to the second server at a time executed by the user. It receives from a portable terminal using one wireless communication according to operation. The first server mediates transmission of scan data from the scanner to the second server. The second server stores scan data. The login unit logs in to the first server using the first account information. The instruction receiving unit receives a scan instruction from the first server after logging in to the first server. When a scan instruction is received from the first server, the scan control unit causes the scan execution unit to scan a document and generates specific scan data. The scan data transmission unit transmits specific scan data to the first server. The account information transmission unit transmits the second account information to the first server in a state where the first account information and the second account information are associated with each other by the first server. As a result, the first server logs in to the second server using the second account information, and transmits specific scan data to the second server.

  According to the above configuration, the scanner can receive both the first and second account information from the portable terminal using one wireless communication corresponding to one operation performed by the user. . For this purpose, the scanner can perform the following operations. That is, the scanner uses the first account information to log in to the first server, and then receives a scan instruction from the first server. In this case, the scanner generates specific scan data and transmits the specific scan data to the first server. The scanner transmits the second account information to the first server in a state where the first and second account information are associated with each other at the first server. Accordingly, the first server can associate the first account information used for the login of the scanner with the second account information for logging in to the second server, and as a result, Specific scan data can be transmitted to the second server by logging into the second server using the second account information. According to this technology, the user can cause the scanner to generate specific scan data only by causing the mobile terminal to execute one wireless communication corresponding to one operation, and via the first server. The specific scan data can be stored in the second server.

  The present specification also discloses a communication system including a scanner and a first server. The first server receives the login request including the first account information from the scanner, and after the login of the scanner to the first server and the login control unit that allows the scanner to log in to the first server. , An instruction transmission unit that transmits a scan instruction to the scanner, a scan data reception unit that receives specific scan data from the scanner, and the second account information from the scanner in a state in which the first account information and the second account information are associated with each other. A second account information receiving unit for receiving the account information and a second scan data for logging in to the second server using the second account information and transmitting specific scan data to the second server A transmission unit. According to this technology, the user can cause the scanner to generate specific scan data only by causing the mobile terminal to execute one wireless communication corresponding to one operation, and via the first server. The specific scan data can be stored in the second server.

  A control method, a computer program, and a computer-readable storage medium storing the computer program for realizing any of the above devices (that is, the scanner or the first server) are also novel and useful.

1 shows a configuration of a communication system. The sequence diagram of each process performed by each device is shown. The flowchart of a scan data transmission process is shown. The flowchart of an upload preparation process is shown. The flowchart of an upload process is shown. The sequence diagram of the case where upload succeeds is shown. A sequence diagram of a case where a document jam occurs is shown. Each screen displayed on a portable terminal is shown.

(Example)
(System configuration)
As shown in FIG. 1, the communication system 2 includes a scanner 10, a mediation server 50, a storage server 100, and a mobile terminal 150. Each device 10, 50, 100, 150 can communicate with each other via the Internet. Further, the scanner 10 and the portable terminal 150 can communicate with each other by using wireless communication in accordance with an NFC (Near Field Communication) method described later.

  The scanner 10 scans an original and stores scan data in the scanner 10 or scans a PC (abbreviation of personal computer) connected to the same LAN (abbreviation of local area network) as the scanner 10. Or send data. In particular, in this embodiment, the scanner 10 scans a document by executing wireless communication with the mobile terminal 150 according to the NFC method, and uploads scan data to the storage server 100 via the mediation server 50. can do. In order to realize this upload, each device 10 or the like has the following configuration.

(Configuration of the scanner 10)
The scanner 10 is a peripheral device such as a PC (not shown). The scanner 10 includes an operation unit 12, a display unit 14, an NFC interface 16, a scan execution unit 20, a network interface 22, and a control unit 30. Hereinafter, the interface is described as “I / F”.

  The operation unit 12 includes a plurality of keys. The user can input various instructions to the scanner 10 by operating the operation unit 12. The display unit 14 is a display for displaying various information. The scan execution unit 20 includes a scan mechanism such as a CCD system or a CIS system.

  The NFC I / F 16 is an I / F for executing NFC wireless communication (hereinafter referred to as “NFC communication”). The NFC method is a wireless communication method for so-called short-range wireless communication, for example, a wireless communication method based on the international standard of ISO / IEC21481 or 18092. The network I / F 22 is an I / F for connecting to a LAN (not shown) constructed in the environment where the scanner 10 is installed, and may be an I / F for wired communication or wireless communication I / F may be used. The scanner 10 is connected to the Internet via a network I / F 22 and a LAN (not shown).

  The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the program stored in the memory 34.

(Configuration of Mediation Server 50)
The mediation server 50 is a server installed on the Internet by the vendor of the scanner 10. The mediation server 50 receives the scan data from the scanner 10 and transmits the scan data to the storage server 100. That is, the mediation server 50 mediates transmission of scan data from the scanner 10 to the storage server 100. The mediation server 50 includes a network I / F 60 and a control unit 70.

  The network I / F 60 is an I / F for connecting to the Internet. The control unit 70 includes a CPU 72 and a memory 74. The CPU 72 executes various processes according to the program stored in the memory 74.

(Configuration of storage server 100)
The storage server 100 is a server installed on the Internet by a specific service provider company different from the vendor of the scanner 10. The storage server 100 can store various data (that is, files) such as image data and document data. The storage server 100 is a known server such as “FTOPIA”, “Evernote (registered trademark)”, “Google (registered trademark) Docs”, “PICASA (registered trademark)”, “FACEBOOK (registered trademark)”, or the like. May be.

  Although not shown, on the Internet, there are various storage servers provided by various other service providers as well as the storage server 100 installed by the specific service provider. That is, a plurality of storage servers operated by a plurality of service providing companies exist on the Internet.

  The vendor of the scanner 10 publishes an API (Application Program Interface) for executing communication with the mediation server 50. Each of the plurality of service providers operates each storage server 100 or the like according to the program including the API. Accordingly, the storage server 100 and the like can execute various communications (for example, communication of scan data 300 in FIG. 6 described later) with the mediation server 50.

(Configuration of mobile terminal 150)
The mobile terminal 150 is, for example, a portable terminal device such as a mobile phone (for example, a smartphone), a PDA (abbreviation of Personal Digital Assistance), a notebook PC, a tablet PC, a portable music playback device, and a portable video playback device. The portable terminal 150 includes an NFC I / F 156, a CPU 162, and a memory 164. The portable terminal 150 includes various hardware (not shown) (for example, an operation unit, a display unit, etc.).

  The NFC I / F 156 is an I / F for executing NFC communication. The CPU 162 executes various processes according to the program stored in the memory 164. The memory 164 further stores an application (hereinafter referred to as a “scanner application”) for causing the scanner 10 to execute various processes related to uploading scan data from the scanner 10 to the storage server 100 or the like. . For example, the mobile terminal 150 downloads the scanner application from a server (that is, a server different from the mediation server 50) installed on the Internet by the vendor of the scanner 10. The following processes executed by the CPU 162 are executed according to the scanner application.

(Preparation; Fig. 2)
The contents of each process executed by each device 10, 50, 100, 150 will be described with reference to FIG. First, the user of the mobile terminal 150 performs the following advance preparation. In the mobile terminal 150, a scanner application is activated by the user. Next, an operation for accessing the mediation server 50 is executed. In the scanner application, the URL (abbreviation of Uniform Resource Locator) of the mediation server 50 is described in advance. The CPU 162 of the portable terminal 150 accesses the mediation server 50 using the URL of the mediation server 50 and receives screen information representing an account registration screen from the mediation server 50. Thereby, CPU162 displays an account registration screen on a display part (illustration omitted). While viewing the account registration screen, the user operates the mobile terminal 150 to input various information such as a user ID and a password to the mobile terminal 150. CPU162 will transmit the account request 200 containing said various information to the mediation server 50, if said various information is input by the user.

  When receiving the account request 200 from the mobile terminal 150, the CPU 72 of the mediation server 50 registers the account information AC1 including the various information included in the account request 200 in the memory 74 (that is, stores it in the memory 74). Then, the CPU 72 transmits the registered account information AC1 to the mobile terminal 150.

  When receiving the account information AC1 from the mediation server 50, the CPU 162 of the portable terminal 150 stores the account information AC1. As a result, account information AC <b> 1 for logging in to the mediation server 50 is stored in the mobile terminal 150.

  In the scanner application, server names and URLs of a plurality of storage servers are described in advance. In this embodiment, the user selects a storage server 100 from among a plurality of storage servers, and executes an operation for accessing the storage server 100. In this case, the CPU 162 of the mobile terminal 150 receives the screen information representing the account registration screen from the storage server 100 using the URL of the storage server 100 as in the case of the mediation server 50. The user inputs various information such as a user ID and a password to the mobile terminal 150. In this case, the CPU 162 of the mobile terminal 150 transmits an account request 204 including the above-described various information input by the user to the storage server 100.

  When the storage server 100 receives the account request 204 from the mobile terminal 150, the storage server 100 registers the account information AC <b> 2 including the various information included in the account request 204. Then, the storage server 100 transmits the registered account information AC2 to the mobile terminal 150.

  When receiving the account information AC2 from the storage server 100, the CPU 162 of the portable terminal 150 stores the account information AC2. As a result, account information AC <b> 2 for logging in to the storage server 100 is stored in the mobile terminal 150.

  Note that the mobile terminal 150 can also store account information for logging in to a storage server different from the storage server 100 in accordance with a user instruction. That is, the mobile terminal 150 stores one or more account information for logging in to one or more storage servers.

(Process for uploading scan data)
The user can cause the mediation server 50 to upload the scan data to the storage server 100 after performing the above-described preparation and storing the two pieces of account information AC1 and AC2 in the portable terminal 150. When the user desires to execute the upload of scan data, the user activates the scanner application stored in the portable terminal 150. Thereby, the standby screen SC1 (see FIG. 8) is displayed on the portable terminal 150.

  As shown in FIG. 8, standby screen SC1 includes an area for selecting a server name. In this embodiment, the user selects the server name of one storage server for storing scan data from the server names of one or more storage servers whose account information is stored in the mobile terminal 150 (this embodiment). In the example, the server name “xxx”) of the storage server 100 is selected.

  The standby screen SC1 further includes an area for selecting a scan condition (that is, the size of a document to be scanned, the scan type, and the file type). The user selects one size from a plurality of document sizes such as A3, A4, and B4. Further, the user selects one scan type from a plurality of scan types such as color scan and monochrome scan. In addition, the user selects one file format (that is, a file format of scan data) from a plurality of file formats such as PDF and JPEG.

  Next, the user brings the portable terminal 150 closer to the scanner 10 in order to establish an NFC connection between the scanner 10 and the portable terminal 150. As a result, the distance between the NFC I / F 16 of the scanner 10 and the NFC I / F 156 of the portable terminal 150 is the maximum distance that each I / F 16, 156 can communicate with (i.e., the distance at which NFC communication can be performed; for example, 10 cm). The state shifts from a state larger than the maximum distance to a state equal to or smaller than the maximum distance. In this case, as shown in FIG. 2, an NFC connection is established between the NFC I / F 16 of the scanner 10 and the NFC I / F 156 of the portable terminal 150.

  The CPU 162 of the portable terminal 150 transmits the NFC information 208 to the scanner 10 using the NFC connection (that is, via the NFC I / F 156). The NFC information 208 includes account information AC1 for logging in to the mediation server 50, account information AC2 for logging in to the storage server 100 selected by the user, condition information indicating the scanning conditions selected by the user, and the user And the server name selected by.

  The CPU 32 of the scanner 10 receives the NFC information 208 from the portable terminal 150 using the NFC connection (that is, via the NFC I / F 16). In this case, the CPU 32 transmits a login request 210 including the account information AC1 in the NFC information 208 to the mediation server 50 using the URL of the mediation server 50 via the network I / F 22. The URL of the mediation server 50 may be stored in advance in the memory 34 of the scanner 10 or may be described in the NFC information 208 received from the mobile terminal 150.

  The CPU 72 of the mediation server 50 receives the login request 210 from the scanner 10 via the network I / F 60. Note that the network I / F 60 is always used for communication executed in the mediation server 50, and therefore the term “via the network I / F 60” is omitted in the following description. The CPU 72 determines whether the account information AC <b> 1 included in the login request 210 is registered in the memory 74. When the CPU 72 determines that the account information AC1 is not registered in the memory 74, the CPU 72 transmits a login failure notification to the scanner 10 (not shown).

  On the other hand, when determining that the account information AC1 is registered in the memory 74, the CPU 72 generates a token (that is, authentication information) 214 that is a unique character string. Then, the CPU 72 stores the token 214 in the memory 74 in association with the account information AC1. Next, the CPU 72 transmits a login success notification 212 including the token 214 to the scanner 10.

  The CPU 32 of the scanner 10 receives the login success notification 212 from the mediation server 50 via the network I / F 22. In this case, the CPU 32 stores the token 214 included in the login success notification 212 in the memory 34. Next, the CPU 32 transmits a connection request including the token 214 to the mediation server 50 via the network I / F 22. The connection request is a request for establishing an XMPP (Extensible Messaging and Presence Protocol) connection between the scanner 10 and the mediation server 50.

  When receiving the connection request from the scanner 10, the CPU 72 of the mediation server 50 determines whether or not the token 214 included in the connection request is stored in the memory 74. When the CPU 72 determines that the token 214 is stored in the memory 74, the CPU 72 transmits a predetermined response to the scanner 10. Thereby, an XMPP connection is established between the scanner 10 and the mediation server 50. As a result, since the intermediary server 50 can use the XMPP connection, it can appropriately transmit a scan instruction 220 described later to the scanner 10 without being interrupted by a router (not shown) or the like (that is, the intermediary server 50). Communication from the Internet side to the LAN side can be executed).

  When the XMPP connection is established, the CPU 72 of the mediation server 50 generates a connection ID for identifying the XMPP connection, and stores the connection ID in the memory 74 in association with the account information AC1. As a result, in the memory 74, the token 214, the connection ID, and the account information AC1 are associated with each other.

  Next, the CPU 32 of the scanner 10 uses the token 214 to generate a process ID 216 for identifying a process related to uploading scan data. In the present embodiment, the process ID (for example, YYY20130315) is generated by combining a character string (for example, YYY) indicated by the token 214 and information (for example, 20130315) indicating the current date and time. As will be described in detail later, the process ID 216 is used by the mobile terminal 150 and the storage server 100 in order for the user of the mobile terminal 150 to check the status of processing related to uploading of scan data.

  The CPU 32 of the scanner 10 transmits a scan acceptance notification 218 including the process ID 216 to the portable terminal 150 using the NFC connection (that is, via the NFC I / F 16).

  The CPU 162 of the portable terminal 150 receives the scan acceptance notification 218 from the scanner 10 using the NFC connection (that is, via the NFC I / F 156). In this case, the reception screen SC2 (see FIG. 8) is displayed on the mobile terminal 150. The reception screen SC2 includes a message indicating that a scan request has been received, and a process ID 216 included in the scan reception notification 218.

  The user can know that the portable terminal 150 may be moved away from the scanner 10 by looking at the reception screen SC2. When the mobile terminal 150 is separated from the scanner 10, the distance between the NFC I / F 16 of the scanner 10 and the NFC I / F 156 of the mobile terminal 150 is less than the maximum distance at which each of the I / Fs 16 and 156 can communicate. The state returns to a state larger than the distance. In this case, the NFC connection is disconnected. Hereinafter, NFC communication performed between the scanner 10 and the portable terminal 150 after the NFC connection is established and before the NFC connection is disconnected (that is, communication of the NFC information 208, and The communication of the scan acceptance notification 218) is referred to as “one NFC communication”.

  As described above, in this embodiment, if the user performs one operation for bringing the mobile terminal 150 close to the scanner 10, the NFC from the mobile terminal 150 to the scanner 10 is performed using one NFC communication. Transmission of information 208 and transmission of scan acceptance notification 218 from scanner 10 to portable terminal 150 are executed. That is, communication of all three pieces of information of account information AC1, account information AC2, and process ID 216 is executed using one NFC communication. Compared with a configuration in which the user has to execute an operation for bringing the mobile terminal 150 close to the scanner 10 a plurality of times for the communication of the above three pieces of information, the convenience for the user is improved.

  As described above, the scanner 10 has received the account information AC2 for logging in to the storage server 100 and the server name of the storage server 100 from the portable terminal 150 (see NFC information 208). The CPU 32 of the scanner 10 uses the above-described XMPP connection (that is, via the network I / F 22) to transfer these pieces of information to the mediation server 50 in a state where the process ID 216, the account information AC2, and the server name are associated with each other. Send to. That is, the CPU 32 transmits these pieces of information to the mediation server 50 simultaneously.

  The CPU 72 of the mediation server 50 simultaneously receives the account information AC2, the process ID 216, and the server name of the storage server 100 from the scanner 10 using the XMPP connection.

  As described above, the process ID 216 is generated using the token 214. In the memory 74 of the mediation server 50, the account information AC1 and the token 214 are associated with each other. Therefore, when receiving the account information AC2 and the token 214 included in the process ID 216 at the same time, the CPU 72 refers to the memory 74 and specifies the account information AC1 associated with the token 214. it can. That is, the CPU 72 can associate the account information AC1 and the account information AC2 via the token 214. Then, the CPU 72 stores the account information AC2 and the process ID 216 in the memory 74. As a result, in the memory 74, the token 214, connection ID, account information AC1, account information AC2, and process ID 216 are associated with each other.

  In the modification, the CPU 72 of the mediation server 50 may associate the two pieces of account information AC1 and AC2 as follows. As described above, the CPU 72 receives the account information AC2 and the process ID 216 from the scanner 10 using the XMPP connection. In the memory 74, a connection ID for identifying the XMPP connection and account information AC1 are associated. Therefore, when receiving the account information AC2 and the process ID 216 using the XMPP connection, the CPU 72 can specify the account information AC1 associated with the connection ID of the XMPP connection with reference to the memory 74. As a result, two pieces of account information AC1 and AC2 can be associated with each other. That is, the CPU 72 can associate the two pieces of account information AC1 and AC2 via the connection ID of the XMPP connection. The XMPP connection is a connection established using the token 214. Therefore, it can be said that also in this modification, two pieces of account information AC1 and AC2 are associated through the token 214.

  Next, the CPU 72 of the mediation server 50 stores the status information in the memory 74 in association with the process ID 216. As a result, in the memory 74, the token 214, connection ID, account information AC1, account information AC2, process ID 216, and status information are associated with each other. At this time, the status information indicates “scan preparation”. As will be described in detail later, the mediation server 50 can supply status information to the portable terminal 150 (see status request 308, status notification 310, etc. in FIG. 6 described later). That is, the user can know the current status of processing related to uploading scan data by accessing the status information using the mobile terminal 150.

  Next, the CPU 72 transmits a scan instruction 220 to the scanner 10 using the above XMPP connection. Since the CPU 72 uses the XMPP connection, the scan instruction 220 can be appropriately transmitted to the scanner 10 existing on the LAN side. When the CPU 72 transmits the scan instruction 220 to the scanner 10, the CPU 72 starts an upload preparation process (see FIG. 4).

  In the modification, the CPU 72 may transmit the scan instruction 220 to the scanner 10 without using the XMPP connection. For example, when receiving the process ID 216 and the account information AC2 from the scanner 10, the CPU 72 may transmit a scan instruction 220 to the scanner 10 as a return value of the information. Even in the configuration of this modification, the CPU 72 can appropriately transmit the scan instruction 220 to the scanner 10 existing on the LAN side without being interrupted by a router or the like.

  The CPU 32 of the scanner 10 receives the scan instruction 220 from the mediation server 50 using the above XMPP connection (that is, via the network I / F 22). In this case, in S2, the CPU 32 starts a scan data transmission process (see FIG. 3).

(Scan data transmission processing; FIG. 3)
The contents of the scan data transmission process (S2 in FIG. 2) executed by the CPU 32 of the scanner 10 will be described with reference to FIG.

  As described above, the CPU 32 of the scanner 10 has already received the condition information indicating the scan condition from the portable terminal 150 (see NFC information 208 in FIG. 2). In S10, the CPU 32 transmits a command to the scan execution unit 20 so that the document is scanned according to the document size (for example, A4) and the scan type (for example, color) indicated by the received condition information. . As a result, the scan execution unit 20 scans the document and generates image data.

  In S12, the CPU 32 determines whether or not scanning for all pages of the document to be scanned has been completed. When receiving a signal indicating that scanning of all pages has been completed from the scan execution unit 20, the CPU 32 determines YES in S12, and uses the image data acquired from the scan execution unit 20, A file having a file format (for example, PDF) indicated by the received condition information is generated. Hereinafter, the file generated here is referred to as “scan data”. Then, the CPU 32 proceeds to S14. On the other hand, if the CPU 32 does not receive the above signal from the scan execution unit 20, the CPU 32 determines NO in S12 and proceeds to S30.

  In S <b> 14, the CPU 32 transmits the token 214 and the scan data to the mediation server 50 simultaneously via the network I / F 22. Thus, the CPU 32 can transmit the token 214 and the scan data to the mediation server 50 in a state where the token 214 and the scan data are associated with each other.

  In S <b> 14, the CPU 32 transmits the token 214 and the scan data to the mediation server 50 without using the XMPP connection established between the scanner 10 and the mediation server 50. As will be described in detail later, since the intermediary server 50 receives the token 214 together with the scan data, it knows that the scan data has been received from the scanner 10 having a login state according to the account information AC1 associated with the token 214. (YES in S50 of FIG. 4 described later).

  However, in a modified example, in S14, the CPU 32 may transmit the scan data to the mediation server 50 using an XMPP connection. In this case, the CPU 32 does not have to transmit the token 214 to the mediation server 50. The mediation server 50 can specify the account information AC1 associated with the connection ID of the XMPP connection, and as a result, knows that the scan data has been received from the scanner 10 having a login state according to the account information AC1. be able to.

  Next, in S <b> 18, the CPU 32 transmits a signal for disconnecting the XMPP connection to the mediation server 50 via the network I / F 22. Thereby, the XMPP connection between the scanner 10 and the mediation server 50 is disconnected. As a result, the state where the scanner 10 is logged in to the mediation server 50 according to the account information AC1 ends.

  Subsequently, in S <b> 20, the CPU 32 deletes the token 214 from the memory 34. When S20 ends, the scan data transmission process ends.

  On the other hand, in S <b> 30, the CPU 32 jams a document in the ADF when a document to be scanned is conveyed by an automatic document feeder (not shown) (hereinafter referred to as “ADF (Automatic Document Feeder)”). It is determined whether or not this has occurred. If the CPU 32 receives a signal indicating the occurrence of a document jam from the ADF, the CPU 32 determines YES in S30 and proceeds to S32. On the other hand, when the CPU 32 does not receive the above signal from the ADF, the CPU 32 determines NO in S30 and returns to S12.

  In S <b> 32, the CPU 32 transmits an error notification indicating the token 214 and document jam to the mediation server 50 via the network I / F 22. As a result, the mediation server 50 receives the token 214 together with the error notification, so that the scanner 10 having the login state according to the account information AC1 associated with the token 214 knows that a document jam has occurred. Yes (YES in S70 of FIG. 4 described later).

  Next, in S <b> 34, the CPU 32 determines whether or not a predetermined time has elapsed since the error notification is transmitted to the mediation server 50 in a state where the jammed document is not cleared. If the predetermined time has elapsed, the CPU 32 determines YES in S34 and proceeds to S18. In this case, the XMPP connection between the scanner 10 and the mediation server 50 is disconnected (S18), and the token 214 is deleted from the memory 34 (S20). Then, transmission of scan data from the scanner 10 to the mediation server 50 is not executed, and as a result, upload of scan data to the storage server 100 is not executed. On the other hand, if the predetermined time has not elapsed, the CPU 32 determines NO in S34 and proceeds to S36.

  In S <b> 36, the CPU 32 determines whether the document jam has been resolved. When the user executes a procedure for clearing a document jam, the CPU 32 receives a signal indicating that the document jam has been cleared from the ADF. In this case, the CPU 32 determines YES in S36 and returns to S12. Thereby, CPU32 can transmit scan data to the mediation server 50 (it is YES at S12, S14). On the other hand, if the CPU 32 does not receive the above signal from the ADF, the CPU 32 determines NO in S36 and returns to S34.

(Upload preparation process; Fig. 4)
The contents of the upload preparation process (S4 in FIG. 2) executed by the CPU 72 of the mediation server 50 will be described with reference to FIG. At the stage where the upload preparation process is started, the memory 74 of the mediation server 50 stores status information indicating “scan preparation” in association with the account information AC1 and the like in the login state.

  In S <b> 50, the CPU 72 of the mediation server 50 determines whether scan data has been received from the scanner 10 having a login state according to the account information AC <b> 1 associated with the token 214. When the CPU 72 receives the token 214 and the scan data simultaneously (see S14 in FIG. 3), the CPU 72 determines that the scan data has been received from the scanner 10 (YES in S50), and proceeds to S52. When receiving scan data from the scanner 10, the CPU 72 stores the scan data in the memory 74 in association with the account information AC1, account information AC2, and the like. On the other hand, if the CPU 72 does not receive scan data from the scanner 10, it determines NO in S50 and proceeds to S70.

  In S52, the CPU 72 changes the status information in the memory 74 associated with the account information AC1 (that is, status information associated with the process ID 216) from “scan preparation” to “upload preparation”. If the user accesses the mediation server 50 using the mobile terminal 150 in this state, the user can know that the current status is being prepared for uploading.

  Next, in S58, the CPU 72 receives a signal (see S18 in FIG. 3) for disconnecting the XMPP connection from the scanner 10. Thereby, the XMPP connection between the scanner 10 and the mediation server 50 is disconnected.

  Next, in S <b> 60, the CPU 72 deletes the token 214 and the connection ID from the memory 74. As a result, in the memory 74, the account information AC1, account information AC2, server name, process ID 216, status information (ie, “upload preparation”), and scan data are associated with each other. When ending S60, the CPU 72 starts an upload process (see FIG. 5) described later (S62), and ends the upload preparation process.

  On the other hand, in S <b> 70, the CPU 72 determines whether an error notification has been received from the scanner 10 having a login state according to the account information AC <b> 1 associated with the token 214. When the CPU 72 receives the token 214 and the error notification simultaneously (see S32 in FIG. 3), the CPU 72 determines that the error notification has been received from the scanner 10 (YES in S70), and proceeds to S72. On the other hand, if no error notification is received from the scanner 10, the CPU 72 determines NO in S70 and returns to S50.

  In S72, the CPU 72 changes the status information in the memory 74 associated with the account information AC1 (that is, status information associated with the process ID 216) from “scan preparation” to “document jam”. If the user accesses the mediation server 50 using the mobile terminal 150 in this state, the user can know that the document is jammed in the scanner 10, and the document is jammed. Actions to resolve can be performed.

  Next, in S <b> 74, the CPU 72 determines whether scan data has been received from the scanner 10. The process of S74 is the same as the process of S50. When the document jam is resolved in the scanner 10 (YES in S36 of FIG. 3, YES in S12, S14), the CPU 72 receives the scan data from the scanner 10, determines YES in S74, Proceed to S52. On the other hand, if the CPU 72 does not receive scan data from the scanner 10, the CPU 72 determines NO in S74 and proceeds to S76.

  In S76, the CPU 72 determines whether or not the XMPP connection between the scanner 10 and the mediation server 50 has been disconnected. If the scanner 10 does not clear the jammed document and the fixed time elapses (YES in S34 of FIG. 3, refer to S18), the CPU 72 receives a signal for disconnecting the XMPP connection from the scanner 10. In this case, the CPU 72 determines YES in S76, and proceeds to S78. On the other hand, if the CPU 72 does not receive the above signal from the scanner 10, it determines NO in S76 and returns to S74.

  In S <b> 78, the CPU 72 deletes the token 214, connection ID, account information AC <b> 2, process ID 216, and status information from the memory 74. As a result, in the memory 74, no information is associated with the account information AC1. After completing S78, the CPU 72 ends the upload preparation process without starting the later-described upload process (see FIG. 5) (that is, without executing S62).

(Upload processing; Fig. 5)
With reference to FIG. 5, the contents of the upload process started in S62 of FIG. 4 will be described. At the stage where the upload process is started, status information indicating “preparation for upload” is stored in the memory 74 of the mediation server 50 in association with the account information AC2 or the like (see S52 in FIG. 4).

  In S90, the CPU 72 selects the storage server 100 from a plurality of storage servers on the Internet according to the server name (see FIG. 2) received from the scanner 10 together with the process ID 216 and the account information AC2. Then, the CPU 72 transmits a login request including the account information AC2 to the selected storage server 100. The memory 74 stores the URL of the storage server 100 in advance. The CPU 72 transmits a login request to the storage server 100 using the URL of the storage server 100.

  When receiving the login request from the mediation server 50, the storage server 100 determines whether the account information AC2 included in the login request is registered in the storage server 100. If the storage server 100 determines that the account information AC2 is registered, the storage server 100 transmits a login success notification to the mediation server 50. If the storage server 100 determines that the account information AC2 is not registered, the storage server 100 issues a login failure notification. It transmits to the mediation server 50. For example, if the account information AC2 has expired, the account information AC2 can be deleted from the storage server 100, so it can be determined that the account information AC2 is not registered.

  In S <b> 92, the CPU 72 determines whether a login success notification has been received from the storage server 100. When the CPU 72 receives a login success notification from the storage server 100, the CPU 72 determines YES in S92 and proceeds to S94. In this case, the mediation server 50 is logged in to the storage server 100 according to the account information AC2. On the other hand, when receiving a login failure notification from the storage server 100, the CPU 72 determines NO in S92 and proceeds to S96.

  In S96, the CPU 72 changes the status information in the memory 74 associated with the account information AC2 (that is, status information associated with the process ID 216) from “upload preparation” to “login failure”. If the user accesses the mediation server 50 using the mobile terminal 150 in this state, the user knows that the scan data upload is not executed as a result of the login to the storage server 100 having failed. be able to. When S96 ends, the upload process ends. Note that the account information AC2, the process ID 216, the status information, and the scan data are deleted from the memory 74 after a predetermined time has elapsed since the execution of S96.

  On the other hand, in S94, the CPU 72 changes the status information in the memory 74 associated with the account information AC2 (that is, status information associated with the process ID 216) from “upload preparation” to “uploading”. To do. If the user accesses the mediation server 50 using the mobile terminal 150 in this state, the user can know that the current status is uploading scan data to the storage server 100. .

  Next, in S98, the CPU 72 transmits the scan data in the memory 74 associated with the account information AC2 to the storage server 100. In particular, the CPU 72 transmits scan data to the storage server 100 using a login state according to the account information AC2. Note that, for example, one of the following first and second methods can be employed as the above-described aspect of “using the login state according to the account information AC2”.

  In the first method, when the login according to the account information AC <b> 2 is successful, a specific token is generated by the storage server 100 and the specific token is transmitted to the mediation server 50. In the storage server 100, a specific token and account information AC2 are associated. In this case, the CPU 72 of the mediation server 50 transmits a specific token and scan data to the storage server 100 simultaneously. Thereby, the storage server 100 can associate the account information AC2 and the scan data via the specific token.

  In the second method, when login according to the account information AC2 is successful, a connection (for example, XMPP connection) is established between the mediation server 50 and the storage server 100. In the storage server 100, the connection ID for identifying the connection and the account information AC2 are associated. In this case, the CPU 72 of the mediation server 50 transmits the scan data to the storage server 100 using the above connection. Accordingly, the storage server 100 can associate the account information AC2 and the scan data via the connection ID.

  As described above, when the storage server 100 receives the scan data from the mediation server 50, the storage server 100 can associate the account information AC2 with the scan data. Therefore, the storage server 100 can store the scan data in a location corresponding to the account information AC2. That is, the scan data is uploaded to a location corresponding to the account information AC2. As described above, when uploading of scan data is successful, the storage server 100 transmits an upload success notification to the mediation server 50.

  On the other hand, for example, assume that the storage server 100 has a predetermined maximum data size that can be stored in a location corresponding to the account information AC2. In this case, the storage server 100 determines that the sum of the data size of the data already stored in the location corresponding to the account information AC2 and the data size of the scan data received from the mediation server 50 is the maximum data described above. If the size is exceeded, the scan data cannot be newly stored in the location corresponding to the account information AC2. In this case, the storage server 100 transmits an upload failure notification to the mediation server 50.

  In S <b> 100, the CPU 72 determines whether an upload success notification has been received from the storage server 100. When receiving a successful upload notification from the storage server 100, the CPU 72 determines YES in S100 and proceeds to S102. On the other hand, when receiving the upload failure notification from the storage server 100, the CPU 72 determines NO in S100 and proceeds to S104.

  In S102, the CPU 72 changes the status information in the memory 74 associated with the account information AC2 (that is, status information associated with the process ID 216) from “Uploading” to “Upload successful”. In this state, if the user accesses the mediation server 50 using the mobile terminal 150, the user can know that the scan data has been successfully uploaded to the storage server 100. When S102 ends, the upload process ends.

  On the other hand, in S104, the CPU 72 changes the status information in the memory 74 associated with the account information AC2 (that is, status information associated with the process ID 216) from “Uploading” to “Upload failure”. To do. In this state, if the user accesses the mediation server 50 using the mobile terminal 150, the user can know that the scan data upload to the storage server 100 has failed. When S104 ends, the upload process ends.

  When S102 or S104 is executed, the account information AC2, process ID 216, status information, and scan data are deleted from the memory 74 after a predetermined time has elapsed.

(Case where upload is successful; Fig. 6)
With reference to FIG. 6, a case where the upload of scan data to the storage server 100 is successful will be described. This case is a continuation sequence of FIG. 2, and is realized by each process of FIGS.

  When the scanner 10 receives a scan instruction 220 (see FIG. 2) from the mediation server 50, the scanner 10 scans the document and generates scan data 300 (YES in S10 and S12 of FIG. 3). Then, the scanner 10 transmits the token 214 and the scan data 300 to the mediation server 50 (S14).

  When receiving the scan data 300 from the scanner 10 (YES in S50 of FIG. 4), the mediation server 50 changes the status information from “scan preparation” to “upload preparation” (S52).

  Next, the XMPP connection between the scanner 10 and the mediation server 50 is disconnected, and the state where the scanner 10 is logged in to the mediation server 50 according to the account information AC1 ends (S18 in FIG. 3 and S58 in FIG. 4). Then, the token 214 is deleted in the scanner 10 (S20 in FIG. 3), and the token 214 is deleted in the mediation server 50 (S60 in FIG. 4).

  The user operates the mobile terminal 150 to input an instruction for status confirmation to the mobile terminal 150. In this case, the CPU 162 of the mobile terminal 150 transmits a login request 304 including the account information AC <b> 1 to the mediation server 50 and receives a login success notification 306 from the mediation server 50. That is, the mobile terminal 150 is logged in to the mediation server 50 according to the account information AC1.

  As described above, the CPU 162 of the portable terminal 150 has received the process ID 216 from the scanner 10 (see the scan acceptance notification 218 in FIG. 2). When the CPU 162 logs in to the mediation server 50, the CPU 162 transmits a status request 308 including the process ID 216 to the mediation server 50.

  When receiving the status request 308 from the mobile terminal 150, the mediation server 50 (that is, the CPU 72) acquires status information associated with the process ID 216 included in the status request 308 from the memory 74. Then, the mediation server 50 transmits a status notification 310 including the acquired status information to the mobile terminal 150.

  The CPU 162 of the mobile terminal 150 receives the status notification 310 from the mediation server 50. As a result, the status screen SC3 is displayed on the portable terminal 150 (see FIG. 8). Status screen SC3 includes a message “preparation for upload” indicated by the status information included in status notification 310. This allows the user to know that the current status is being prepared for uploading scan data.

  Next, as shown in FIG. 6, the mediation server 50 transmits a login request 314 including the account information AC2 to the storage server 100 (S90 in FIG. 5), and receives a login success notification 316 from the storage server 100 ( YES in S92). In other words, the mediation server 50 is logged in to the storage server 100 according to the account information AC2. Then, the mediation server 50 changes the status information from “uploading preparation” to “uploading” (S94). Next, the mediation server 50 transmits the scan data 300 to the storage server 100 (S98).

  When the storage server 100 receives the scan data from the mediation server 50, the storage server 100 stores the scan data 300 in a location corresponding to the account information AC2. As a result, the scan data 300 is uploaded to the storage server 100. When saving the scan data 300, the saving server 100 transmits an upload success notification 318 to the mediation server 50.

  When receiving the upload success notification 318 from the storage server 100 (YES in S100), the mediation server 50 changes the status information from “Uploading” to “Upload successful” (S102).

  Similar to the status request 308, the CPU 162 of the portable terminal 150 transmits a status request 320 including the process ID 216 to the mediation server 50 and receives a status notification 322 from the mediation server 50 in accordance with a user instruction. As a result, the status screen SC4 is displayed on the portable terminal 150 (see FIG. 8). The status screen SC4 includes a message “upload successful” indicated by the status information included in the status notification 322. Thereby, the user can know that the upload of the scan data to the storage server 100 is successful.

(Case where document jam occurs; Fig. 7)
With reference to FIG. 7, a case where a document jam occurs will be described. This case is also a continuation sequence of FIG. 2, and is realized by each process of FIGS.

  In the scanner 10, a document jam occurs in the process of scanning the document. In this case, the scanner 10 transmits the token 214 and the error notification 402 to the mediation server 50 (S32 in FIG. 3).

  Upon receiving the error notification 402 from the scanner 10, the mediation server 50 changes the status information from “scan preparation” to “document jam” (S72).

  Communication of each information 404, 406, 408, 410 executed between the portable terminal 150 and the mediation server 50 is the same as the communication of each information 304, 306, 308, 310 in FIG. However, in this case, the status notification 410 includes status information indicating “document jam”.

  The mobile terminal 150 receives the status notification 410 from the mediation server 50. As a result, the status screen SC5 is displayed on the portable terminal 150 (see FIG. 8). Status screen SC5 includes a message indicating “document jam” indicated by the status information included in status notification 410. As a result, the user can know that the document is jammed in the scanner 10 and can execute a measure for clearing the document jam.

  When the document jam is eliminated (YES in S36 of FIG. 3), the scanner 10 scans the document and transmits the token 214 and the scan data 300 to the mediation server 50 (S14). The subsequent processes are the same as in the case of FIG.

(Effect of Example)
According to the present embodiment, as shown in FIG. 2, if the user performs a single operation for the user to bring the mobile terminal 150 closer to the scanner 10 (that is, if a so-called one-touch operation is performed), Both of the two pieces of account information AC1 and AC2 can be received from the mobile terminal 150 using one NFC communication. Therefore, compared with the configuration in which the user has to execute the operation for bringing the portable terminal 150 close to the scanner 10 twice for the communication of the two pieces of account information AC1 and AC2, the convenience of the user is improved. improves.

  Since the scanner 10 receives the account information AC1 from the portable terminal 150, the scanner 10 can log in to the mediation server 50 using the account information AC1. Thereafter, the scanner 10 receives a scan instruction 220 from the mediation server 50. In this case, as illustrated in FIG. 6, the scanner 10 generates the scan data 300 and transmits the token 214 and the scan data 300 to the mediation server 50.

  Further, as shown in FIG. 2, the scanner 10 receives the account information AC2 from the portable terminal 150, so that the account information AC2 can be transmitted to the mediation server 50. Here, the scanner 10 transmits the account information AC2 and the process ID 216 to the mediation server 50 in a state where the account information AC2 and the process ID 216 are associated with each other. As a result, the mediation server 50 can associate the account information AC1 and the account information AC2 via the token 214 included in the process ID 216.

  As shown in FIG. 6, the mediation server 50 can log in to the storage server 100 using the account information AC2. Further, since the mediation server 50 can associate the account information AC1 and the account information AC2, the scan data 300 received from the scanner 10 having the login state according to the account information AC1 is stored in the login state according to the account information AC2. Can be transmitted to the storage server 100. As a result, the storage server 100 can store (that is, upload) the scan data 300 in a location corresponding to the account information AC2.

  As described above, according to this embodiment, the user can easily save (that is, upload) the scan data 300 generated by the scanner 10 to the storage server 100 via the mediation server 50 using the portable terminal 150. ).

  In the present embodiment, even when a mobile terminal different from the mobile terminal 150 is used, the scan data can be uploaded to the storage server 100 as in the case of the mobile terminal 150. That is, when each user brings each portable terminal close to the scanner 10, the mediation server 50 can upload scan data to each location corresponding to each account information corresponding to each user (that is, a different location). According to the present embodiment, each user of each portable terminal can upload scan data to each location corresponding to each account information of each user using the same scanner 10.

  In particular, according to the present embodiment, as shown in FIG. 6, when the transmission of the scan data 300 from the scanner 10 to the mediation server 50 is completed, the XMPP connection between the scanner 10 and the mediation server 50, i.e., account information. The XMPP connection according to AC1 is automatically disconnected (see S18 in FIG. 3 and S58 in FIG. 4). If the XMPP connection is maintained even after the transmission of the scan data 300 is completed, the user of another mobile terminal may use the XMPP connection when the user wishes to upload the scan data. Must be cut off. For example, a user of another mobile terminal must disconnect the XMPP connection by turning off the power of the scanner 10 or causing the scanner 10 to perform a predetermined operation on the operation unit 12. On the other hand, according to the present embodiment, when the transmission of the scan data 300 is completed, the XMPP connection is automatically disconnected. Therefore, the user of another mobile terminal must execute an operation for disconnecting the XMPP connection. You do n’t have to. This improves user convenience.

(Correspondence)
The mediation server 50 and the storage server 100 are examples of “first server” and “second server”, respectively. The token 214 is an example of “first data”. The process ID 216 is an example of “second data” and “process identification information”. The NFC I / F 16 and the network I / F 22 are examples of “first interface” and “second interface”, respectively.

  Each process executed by the scanner 10 has the following correspondence. In FIG. 2, the process of receiving the NFC information 208 from the portable terminal 150, the process of transmitting the login request 210 to the mediation server 50, the process of receiving the login success notification 212 from the mediation server 50, the process of generating the process ID 216, the mediation server 50, the process of receiving the scan instruction 220 from the process 50, and the process of transmitting the account information AC2 and the process ID 216 to the mediation server 50 are “account information receiving unit (first account information receiving unit)”, “login unit”, “ It is an example of processing executed by a “data reception unit”, “generation unit”, “instruction reception unit”, and “account information transmission unit”. Further, the process of transmitting the scan acceptance notification 218 to the portable terminal 150 and the process of transmitting the process ID 216 to the mediation server 50 are examples of processes executed by the “identification information transmitting unit”. The processes in S10 and S14 in FIG. 3 are examples of processes executed by the “scan control unit” and the “scan data transmission unit (first scan data transmission unit)”, respectively.

  Each process executed by the mediation server 50 has the following correspondence. In FIG. 2, a process of receiving a login request 210 from the scanner 10 and transmitting a login success notification 212 to the scanner 10, a process of transmitting a scan instruction 220 to the scanner 10, and a process of receiving account information AC2 from the scanner 10, respectively. , “Login control unit”, “instruction transmission unit”, and “second account information reception unit”. In FIG. 4, the process of receiving scan data from the scanner 10 in S <b> 50 is an example of a process executed by the “scan data receiving unit”. In FIG. 5, the processing of S90 and S98 is an example of processing executed by the “second scan data transmission unit”. In FIG. 6, the process of transmitting the status notification 310 to the portable terminal 150 is an example of the process executed by the “situation information transmission unit”.

  Specific examples of the present invention have been described in detail above, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. The modifications of the above embodiment are listed below.

(Modification 1) In the above embodiment, as shown in FIG. 2, the scanner 10 uses NFC communication, but instead of this, the standard differs from NFC such as infrared communication, Transfer Jet, etc. You may use the near field communication which followed. Also in this modified example, the scanner 10 uses the wireless communication of one time corresponding to one operation for bringing the mobile terminal 150 close to the scanner 10, and both of the two account information AC <b> 1 and AC <b> 2 from the mobile terminal 150. Can be received. In the present modification, wireless communication such as infrared or transfer jet is an example of “one wireless communication”.

(Modification 2) In the above embodiment, as shown in FIG. 2, the scanner 10 transmits the account information AC <b> 2 to the mediation server 50 before receiving the scan instruction 220 from the mediation server 50. Alternatively, the scanner 10 may transmit the account information AC2 to the mediation server 50 after receiving the scan instruction 220 from the mediation server 50. For example, after the scanning of the document is completed (that is, after YES in S12 in FIG. 3), the scanner 10 before the scan data 300 is transmitted to the mediation server 50 (that is, before S14 in FIG. 3). The account information AC2 may be transmitted to the mediation server 50. Further, for example, the scanner 10 transmits the scan data 300 to the mediation server 50 (that is, after S14 in FIG. 3) and before disconnecting the XMPP connection (that is, before S18 in FIG. 3). The information AC2 may be transmitted to the mediation server 50. Generally speaking, the account information transmission unit may transmit the second account information to the first server or the scan from the first server before the scan instruction is received from the first server. After the instruction is received, the second account information may be transmitted to the first server.

(Modification 3) In the above embodiment, as shown in FIG. 2, the scanner 10 transmits the process ID 216 and the account information AC2 to the mediation server 50 in a state where the process ID 216 and the account information AC2 are associated ( That is, the process ID 216 and the account information AC2 are transmitted simultaneously). As a result, the mediation server 50 can associate the account information AC1 and the account information AC2 via the token 214 included in the process ID 216. Instead of this, any of the following methods (1) to (3) may be adopted.

(1) The scanner 10 may transmit the token 214 and the account information AC2 to the mediation server 50 in a state where the token 214 and the account information AC2 are associated without generating the process ID 216. Also in this modification, the mediation server 50 can associate two pieces of account information AC1 and AC2 via the token 214. In the present modification, the token 214 is an example of “first data” and “second data”, and “first data” and “second data” match.

(2) After generating the token 214, the mediation server 50 may further generate a unique ID without using the token 214, and store the ID and account information AC1 in association with each other. Then, the mediation server 50 may transmit a login success notification 212 including the token 214 and the above ID to the scanner 10. The scanner 10 may transmit the ID and account information AC2 to the mediation server 50 in a state where the ID and account information AC2 are associated with each other. In this modification, the mediation server 50 can associate the two pieces of account information AC1 and AC2 via the above ID. In the present modification, the ID is an example of “first data” and “second data”, and “first data” and “second data” match.

(3) In the above embodiment and the above modification examples (1) and (2), the scanner 10 has some data (for example, process ID 216) for associating the two account information AC1 and AC2 together with the account information AC2. , Token 214, ID) to the mediation server 50. Instead of this, the scanner 10 may not transmit the data together with the account information AC2, and may transmit the account information AC2 to the mediation server 50 using the XMPP connection. As described in the above embodiment, in the mediation server 50, the connection ID for identifying the XMPP connection and the account information AC1 are associated. Therefore, the mediation server 50 can associate the two pieces of account information AC1 and AC2 via the connection ID of the XMPP connection used for receiving the account information AC2. This modification is also an example of a configuration of “transmitting the second account information to the first server in a state where the first account information and the second account information are associated with each other”.

(Modification 4) In the above embodiment, as shown in FIG. 6, after receiving the scan data 300 from the scanner 10, the mediation server 50 logs in to the storage server 100 using the account information AC2. Instead, the mediation server 50 may attempt to log in to the storage server 100 using the account information AC2 before transmitting the scan instruction 220 (FIG. 2) to the scanner 10. The mediation server 50 does not need to transmit the scan instruction 220 to the scanner 10 when the login is successful, and does not transmit the scan instruction 220 to the scanner 10 when the login is not successful. According to this modification, the scanner 10 does not need to generate scan data when it cannot upload due to the inability to log in to the storage server 100.

(Modification 5) The “scanner” includes any device including a scan execution unit (for example, a multi-function device capable of executing a multi-function including a scan function and a print function, a FAX apparatus, etc.). For example, the transmission-side FAX apparatus (that is, an example of “scanner”) performs FAX transmission by uploading FAX data (that is, an example of “scan data”) to the storage server 100 via the mediation server 50. Also good. As a result, the reception-side FAX apparatus can execute FAX reception by receiving FAX data from the mediation server 50.

(Modification 6) In each of the above-described embodiments, the CPUs 32 and 72 of the scanner 10 and the mediation server 50 execute the programs (that is, software) in the memories 34 and 74, thereby realizing the processes shown in FIGS. Is done. Alternatively, at least one of the processes may be realized by hardware such as a logic circuit.

  2: communication system, 10: scanner, 12: operation unit, 14: display unit, 16: NFC I / F, 20: scan execution unit, 22: network I / F, 30: control unit, 32: CPU, 34: memory 50: Mediation server, 60: Network I / F, 70: Control unit, 72: CPU, 74: Memory, 100: Storage server, 150: Portable terminal, 156: NFC I / F

Claims (10)

A scanner,
A scan execution unit;
Both the first account information for logging in to the first server and the second account information for logging in to the second server are set once according to one operation executed by the user. An account information receiving unit that receives from the portable terminal using wireless communication of the first, wherein the first server mediates transmission of scan data from the scanner to the second server, and The server stores the scan data, the account information receiving unit,
A login unit for logging in to the first server using the first account information;
An instruction receiving unit that receives a scan instruction from the first server after the login to the first server;
A scan control unit that, when the scan instruction is received from the first server, causes the scan execution unit to scan a document and generates specific scan data;
A scan data transmission unit for transmitting the specific scan data to the first server;
An account information transmitting unit configured to transmit the second account information to the first server in a state in which the first account information and the second account information are associated with each other in the first server; As a result, the first server logs in to the second server using the second account information and transmits the specific scan data to the second server; ,
Comprising a scanner.   The scanner according to claim 1, wherein the account information transmission unit transmits the second account information to the first server before the scan instruction is received from the first server. The scanner further includes
A data receiving unit configured to receive, from the first server, first data associated with the first account information in the first server;
The scanner according to claim 1, wherein the account information transmission unit associates the second data based on the first data and the second account information and transmits the second data to the first server. . The scanner further includes
A generation unit that generates process identification information for identifying a process to be executed based on the scan instruction;
An identification information transmitting unit for transmitting the processing identification information to the portable terminal and the first server;
The scanner according to claim 1, comprising:   The scanner according to claim 4, wherein the identification information transmission unit transmits the processing identification information to the mobile terminal using the one-time wireless communication.   The scanner according to any one of claims 1 to 5, wherein the one-time wireless communication is wireless communication according to NFC (Near Field Communication) standard. The scanner further includes
A first interface for performing wireless communication;
The one-time operation executed by the user causes the portable terminal to be placed on the scanner so that a device-to-device distance that is a distance between the first interface and the portable terminal is equal to or less than a specific distance. Is an operation to bring it closer,
The one-time wireless communication is a second state in which the inter-device distance is less than or equal to the specific distance from the first state that is greater than the specific distance due to the one operation performed by the user. Wireless communication executed in a period between a first timing of transition to a state and a second timing of returning from the second state to the first state;
The account information receiving unit receives both the first account information and the second account information from the mobile terminal using the one-time wireless communication via the first interface. Item 7. The scanner according to any one of Items 1 to 6. The scanner further includes
A second interface different from the first interface;
The login unit logs in to the first server using the first account information via the second interface,
The instruction receiving unit receives the scan instruction from the first server via the second interface;
The scan data transmission unit transmits the specific scan data to the first server via the second interface;
The scanner according to claim 7, wherein the account information transmission unit transmits the second account information to the first server via the second interface. A communication system,
A scanner,
A first server that mediates transmission of scan data from the scanner to a second server, wherein the second server includes the first server that stores the scan data;
The scanner is
A scan execution unit;
Both the first account information for logging in to the first server and the second account information for logging in to the second server are in accordance with a single operation executed by the user. A first account information receiving unit that receives from the mobile terminal using one wireless communication;
A login unit that transmits a login request including the first account information to the first server, and logs in to the first server;
An instruction receiving unit that receives a scan instruction from the first server after the login to the first server;
A scan control unit that, when the scan instruction is received from the first server, causes the scan execution unit to scan a document and generates specific scan data;
A first scan data transmission unit for transmitting the specific scan data to the first server;
An account information transmitting unit configured to transmit the second account information to the first server in a state in which the first account information and the second account information are associated with each other in the first server;
The first server is
A login control unit that receives the login request including the first account information from the scanner and allows the login of the scanner to the first server;
An instruction transmission unit for transmitting the scan instruction to the scanner after the login of the scanner to the first server;
A scan data receiving unit for receiving the specific scan data from the scanner;
A second account information receiving unit for receiving the second account information from the scanner in a state in which the first account information and the second account information are associated;
A communication system comprising: a second scan data transmission unit that logs in to the second server using the second account information and transmits the specific scan data to the second server. The scanner further includes
A generation unit that generates process identification information for identifying a process to be executed based on the scan instruction;
An identification information transmitting unit that transmits the processing identification information to the portable terminal and the first server;
The first server further includes:
The situation information transmission part which transmits the situation information which shows the situation of the process identified by the process identification information to the portable terminal when the process identification information is received from the portable terminal. Communication system.

Images