JP2012194856A - Data communication system, server, and data communication method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide data communication technique for suitably charging for communication when the communication is restarted after a data communication error occurs.SOLUTION: Data responding to a transmission request RQ1a for the data is transmitted from a server 90 to an MFP 1. Based upon a communication amount (data size SZ1) of data received by the MFP 1 up to the point of time of interruption of communication due to error, charge PR1 for data communication based upon the transmission request RQ1a is calculated first (step SP14). A retransmission request RQ1b having the same contents with the transmission request RQ1a is transmitted thereafter from the MFP 1 to the server 90 together with the data size SZ1 (step SP21), and data based upon the retransmission request RQ1b is transmitted to the MFP 1 (step SP22). Charge PR2 for the data communication based upon the retransmission request RQ1b is calculated based upon not only data size SZ2 as the communication amount of the data based upon the retransmission request RQ1b, but also the data size SZ1.

Description

  The present invention relates to a data communication system and a technology related thereto, and more particularly to a billing technology in data communication.

  There are technologies for providing various services by communicating a data communication apparatus such as an MFP with a cloud-side apparatus (server).

  In such services, a pay-per-use system may be adopted.

  For example, Patent Document 1 describes that a charge amount for an image data processing service is calculated based on a transmission data amount.

JP 2003-177878 A

  By the way, the data communication as described above is interrupted due to an error during communication or the like, and after the error is resolved, the data communication may be resumed based on a user operation or the like. Specifically, a certain amount of data communication may be performed until an error occurs based on a data transmission request, and after the error is resolved, the same data transmission request may be made and the data communication may be resumed. In addition, the data communication after the restart is often started again from the first part of the data.

  In such a situation, when a pay-as-you-go billing system as described above is adopted, the total of the communication volume related to the transmitted data up to the time of the error occurrence and the communication volume related to the retransmitted data after the error is resolved Charges are made according to the amount of communication. For example, a case is assumed in which communication relating to 80% of all data ends when an error occurs, and then communication is resumed to complete data communication. In this case, a charge corresponding to the communication amount (100%) of all data in the second data communication after the error is eliminated is further added to the charge related to the 80% data transmission before the error occurs. Is done. That is, a charge corresponding to 180% of data in total is charged.

  However, from the viewpoint of the service user, such a charging process is not always appropriate.

  Accordingly, an object of the present invention is to provide a data communication technique capable of performing appropriate charging when communication is resumed after occurrence of a data communication error.

  In order to solve the above-mentioned problem, the invention of claim 1 is a data communication system, comprising a server and a data communication device connected to the server via a communication network, wherein the data communication device is a data communication device. The first communication control means for transmitting the transmission request to the server and receiving the data based on the transmission request from the server, and the data communication based on the transmission request, the data communication amount based on the transmission request An acquisition means for acquiring a first data size that is a communication amount of data transmitted from the server to the data communication device up to a communication interruption time point due to occurrence of an error in the data communication device; The first communication control means of the first communication control means, after an error occurs during data communication based on the transmission request, the same data as the data specification condition included in the transmission request. A retransmission request having a specified condition is transmitted to the server together with data indicating the first data size, and the server transmits data based on the transmission request to the data communication device in response to the transmission request. , Second communication control means for transmitting data based on the retransmission request to the data communication apparatus in response to the retransmission request, and a first fee related to data communication based on the transmission request. Charging means for calculating based on the size, wherein the charging means of the server is based not only on the second data size which is the amount of data communication based on the retransmission request but also on the first data size And calculating a second charge for data communication based on the retransmission request.

  According to a second aspect of the present invention, in the data communication system according to the first aspect of the present invention, the billing unit is configured such that, when the second data size is larger than the first data size, the second data size. The second fee is calculated by subtracting the fee corresponding to the first data size from the fee corresponding to.

  According to a third aspect of the present invention, in the data communication system according to the first or second aspect of the present invention, the charging means is configured such that when the second data size is smaller than the first data size, It is characterized in that the charge of 2 is calculated as zero.

  According to a fourth aspect of the present invention, in the data communication system according to the first or second aspect of the present invention, when the second data size is smaller than the first data size, the billing means A fee obtained by subtracting a fee corresponding to the second data size from a fee corresponding to one data size is determined as a refund amount, and the refund amount is subtracted from the first fee.

  According to a fifth aspect of the present invention, in the data communication system according to any one of the first to fourth aspects of the present invention, the first communication control means has the job data relating to the data transmission request remaining in an unprocessed state. On the condition that the data communication based on the transmission request is resumed, it is determined that the resumption instruction is given, and the retransmission request is sent to the server together with the data indicating the first data size. It is characterized by transmitting.

  A sixth aspect of the present invention is the data communication system according to any one of the first to fifth aspects, wherein the data communication apparatus has the same data designation condition as the data designation condition included in the transmission request. Means for recording the number of times the transmission request has been sent, and the first communication control means, when an error occurs during data communication, when the number of times has reached a predetermined value, A new transmission request is transmitted to the server instead of a transmission request, and the billing unit performs data transmission based on the new transmission request based on a third data size that is a data communication amount based on the new transmission request. A third fee related to communication is calculated, and the third fee is additionally charged.

  According to a seventh aspect of the present invention, in the data communication system according to any one of the first to fifth aspects, the data communication device is configured to checksum the previous transmission target data based on the transmission request or the retransmission request. Means for comparing the data with the checksum data of the current transmission target data and determining the identity of the data, the first communication control means, after an error has occurred during data communication, When the number of mismatch determinations regarding data identity has reached a predetermined value, a new transmission request is transmitted to the server instead of the re-transmission request, and the billing means transmits the data based on the new transmission request. Based on the third data size, which is a communication amount, a third fee for data communication based on the new transmission request is calculated, and the third fee is additionally calculated. Characterized in that it charged.

  The invention according to claim 8 is a server connected to a data communication device via a communication network, the communication control means for transmitting data based on a transmission request from the data communication device to the data communication device, and the transmission A first data size that is a communication amount of data based on the request and is a communication amount of data transmitted to the data communication device by a communication interruption time point due to an error occurrence during data communication based on the transmission request Charging means for calculating a charge related to data communication based on the transmission request, and the communication control means from the data communication device after an error occurs during data communication based on the transmission request Based on a re-transmission request that is transmitted and has the same data specification condition as the data specification condition included in the transmission request , The designated data is transmitted to the data communication device, and the charging means is based not only on the second data size which is a data communication amount based on the retransmission request but also on the first data size, A charge for data communication based on the retransmission request is calculated.

  The invention according to claim 9 is a data communication method, wherein a) a transmission request which is a data transmission request is transmitted from the data communication device to the server, and b) data based on the transmission request is transmitted from the server to the data. Transmitting to the communication device; and c) the amount of data communication based on the transmission request received by the data communication device by the time of communication interruption due to the occurrence of an error during data communication based on the transmission request. Calculating a first fee for data communication based on the transmission request based on a first data size that is a communication amount of the received data; and d) an error has occurred during data communication based on the transmission request Later, a re-transmission request having the same data specification condition as the data specification condition included in the transmission request is sent as data related to the first data size. Both transmitting from the data communication device to the server, e) transmitting data based on the retransmission request from the server to the data communication device, and f) communicating data based on the retransmission request. Calculating a second fee related to data communication based on the retransmission request based on not only the second data size as a quantity but also the first data size.

  According to the first to ninth aspects of the invention, the second fee for data communication based on the re-transmission request is calculated based on not only the second data size but also the first data size. Appropriate charging can be performed when communication is resumed after the occurrence of a data communication error.

  In particular, according to the inventions described in claims 6 and 7, unauthorized use can be prevented.

It is the schematic which shows the structure of a data communication system. 1 is a schematic diagram illustrating a configuration of an MFP. It is the schematic which shows the structure of a server. It is a figure which shows the operation | movement in a download printing service. FIG. 6 is a diagram showing a menu screen displayed on the MFP. It is a figure which shows a file designation | designated screen. It is a figure which shows the confirmation screen regarding a resending request. It is a figure which shows a communication management table.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<1. Configuration>
<Overall configuration>
FIG. 1 is a schematic diagram showing the configuration of the data communication system 100. As shown in FIG. 1, the data communication system 100 includes a plurality of server computers (also simply referred to as “servers”) 90 and a multi function peripheral (also abbreviated as “MFP”) 1. MFP 1 is also expressed as a data communication device.

  The MFP 1 and each server 90 are connected to each other via a communication network NW, and data can be transmitted and received between the MFP 1 and each server 90 via the communication network NW. The network NW includes various networks such as a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet.

  In the data communication system 100, communication between the MFP 1 and the cloud side device (server 90) is performed, and various services are provided to the user of the MFP 1.

<Configuration of MFP>
The MFP 1 is a device (also referred to as a multi function device) having a scanner function, a printer function, a copy function, a facsimile communication function, and the like. The MFP 1 is also referred to as an image processing apparatus or an image forming apparatus.

  As shown in the functional block diagram of FIG. 2, the MFP 1 includes an image reading unit 2, a print output unit 3, a communication unit 4, a storage unit 5, an input / output unit 6, a controller 9, and the like. Various functions can be realized by operating them in an automated manner.

  The image reading unit 2 is a processing unit that optically reads a document placed at a predetermined position of the MFP 1 and generates (forms) image data (also referred to as a document image) of the document.

  The print output unit 3 is an output unit that prints out (forms) an image on various media such as paper based on image data related to the target image.

  The communication unit 4 is a processing unit capable of performing facsimile communication via a public line or the like. Furthermore, the communication unit 4 can perform network communication via the communication network NW. In this network communication, various protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol) and FTP (File Transfer Protocol) are used. By using the network communication, the MFP 1 can communicate with a desired destination. Various data can be exchanged between them.

  The storage unit 5 includes a storage device such as a hard disk drive (HDD) and a nonvolatile memory. The storage unit 5 stores a document image (image data) generated by the image reading unit 2 or the like.

  The input / output unit 6 includes an operation input unit 6a that receives input to the MFP 1 and a display unit 6b that displays and outputs various types of information. Specifically, the MFP 1 is provided with an operation panel 6c (see FIG. 1). The operation panel (touch screen) 6c is configured by embedding a piezoelectric sensor or the like in a liquid crystal display panel, and functions as a part of the display unit 6b and also functions as a part of the operation input unit 6a.

  The overall control unit 9 is a control device that is built in the MFP 1 and controls the MFP 1 in an integrated manner. The overall control unit 9 is configured as a computer system including a CPU and various semiconductor memories (such as RAM and ROM). The overall control unit 9 implements various processing units by executing a predetermined software program (hereinafter also simply referred to as a program) PG1 stored in a ROM (for example, an EEPROM) in the CPU. The program PG1 may be downloaded via the network NW and installed in the MFP 1. The program PG1 may be recorded on various portable recording media (USB memory or the like), read from the recording medium, and installed in the MFP 1.

  Specifically, the controller 9 performs various processing units including an authentication control unit 31, a data communication control unit 32, a data size acquisition unit 33, a display control unit 34, and an unauthorized use detection unit 35 as the program PG1 is executed. Is realized.

  The authentication control unit 31 is a processing unit that performs user authentication processing.

  The data communication control unit 32 is a processing unit that controls the data transmission / reception operation with the communication partner (for example, the server 90) in cooperation with the communication unit 4. The data communication control unit 32 performs a process of transmitting a data transmission request RQ (RQ1a, RQ1b, etc.) (described later) to the server 90 and receiving the transmission target data D1 based on the transmission request RQ from the server 90.

  The data size acquisition unit 33 is a processing unit that acquires the data size of the reception amount (communication amount) of data transmitted from the communication partner and received by the MFP 1.

  The display control unit 34 is a processing unit that controls the display operation in the display unit 6b.

  The unauthorized use detection unit 35 is a processing unit that detects unauthorized use (described later) in an application service or the like.

<Server configuration>
The server 90 is configured as a computer system including a CPU and various semiconductor memories (such as RAM and ROM). The overall control unit 9 implements various processing units by executing a predetermined software program (hereinafter also simply referred to as a program) PG2 stored in a ROM (for example, an EEPROM) in the CPU. The program PG2 may be downloaded via the network NW and installed in the server 90. The program PG may be recorded on various portable recording media (CD-ROM, USB memory, etc.), read from the recording medium, and installed in the server 90.

  Specifically, the server 90 implements various processing units including an authentication control unit 81, a data communication control unit 82, and a charging processing unit 83 in accordance with the execution of the program PG2 (see FIG. 3).

  The authentication control unit 81 is a processing unit that performs user authentication processing.

  The data communication control unit 82 is a processing unit that controls data transmission / reception operations with a communication partner (for example, MFP 1) in cooperation with the communication unit 94. The data communication control unit 82 receives a data transmission request RQ (RQ1a, RQ1b, etc.) from the MFP 1 and performs processing for transmitting data to be transmitted based on the transmission request RQ to the MFP 1.

  The billing processing unit 83 is a processing unit that performs billing processing with an application service provided by the server 90. The billing processing unit 83 calculates a charge for data communication according to the communication amount (communication data size) with the MFP 1 and performs a billing process for the application service based on the charge or the like.

  The storage unit 95 of the server 90 records various data used in the application service, billing processing information, and the like.

<2. Operation>
Here, a case where the download print service is executed using the MFP 1 will be described as an example of the cloud service.

  FIG. 4 is a diagram illustrating an operation in the download print service. Here, it is assumed that an error occurs during the download of the print target file, the download is temporarily interrupted, and then the print target file is downloaded again.

  After the user authentication operation is performed, the user UA of the MFP 1 operates the menu screen GA1 (see FIG. 5) displayed on the touch screen 6c to correspond to a desired menu item (here, “download printing”). The button BN14 to be selected is selected and pressed. In response to the pressing operation of the button BN14, the MFP 1 displays the file designation screen GA2 (see FIG. 6) on the touch screen 6c. The screen GA2 is a screen showing a list of files stored in the server 90.

  The user UA selects a desired option (for example, “file FL1”) from among a plurality of options in the screen GA2, and presses an OK button BN1.

  In response to the pressing operation of the OK button BN1, the MFP 1 (specifically, the communication control unit 32 or the like) transmits a data transmission request RQ1 (RQ1a) to the server 90 (step SP11). The transmission request RQ1a is command data for requesting the counterpart apparatus (server 90) to transmit the download target file FL1 to the MFP 1. The transmission request RQ1a is also expressed as command data including a search command in which a search condition (file name = “file FL1”) regarding the download target data file is specified. The transmission request RQ1a is also expressed as command data including a data specification condition for specifying a download target data file.

  Upon receiving the transmission request RQ1a, the server 90 specifies transmission target data D1 based on the transmission request RQ1a, and starts a transmission operation for transmitting the transmission target data D1 (here, “file FL1”) to the MFP 1. (Step SP12). On the other hand, the MFP 1 starts an operation of receiving the data D1 transmitted from the server 90 (step SP13). This communication operation is executed by dividing the transmission target data D1 into a plurality of packets according to a predetermined protocol.

  At this time, the billing processing unit 83 of the server 90 performs billing processing as needed according to the communication amount (transmission data size) of the data to be transmitted (data specified by the data specification condition of the transmission request RQ) based on the transmission request RQ1a. Execute (step SP14). The accounting processing unit 83 calculates a charge for data transmission (data communication) based on the transmission request RQ1a based on the data size SZ1 indicating the transmission amount of the transmission target data D1 (which is also the reception amount at the MFP 1). Here, each time a unit information amount (for example, 1 kilobyte) is transmitted, a fee (unit price) per unit information amount is added to calculate the fee. For example, when 1 yen is charged for each 1 KB (kilobyte), when transmission of all 1000 Kbytes of data ends normally, 1000 yen, which is a charge for 1000 Kbytes, is charged.

  Here, in this embodiment, it is assumed that a communication error occurs for some reason before the transmission of all the transmission target data D1 is completed during data communication. Due to the occurrence of this communication error, the communication operation based on the transmission request RQ1a is interrupted at a certain time point TP (step SP15).

  The billing process by the billing processing unit 83 is executed based on the data communication amount (data size SZ1) received by the MFP 1 up to the communication interruption time point TP.

  At the time of this error occurrence (communication interruption time) TP, transmission of 80% of data (800 Kbytes) has been completed out of all data (1000 Kbytes), and the remaining 20% (200 Kbytes) has not been transmitted. Assume it is complete. At this time, for example, when 1 yen is charged for each 1 KB (kilobyte), 800 yen, which is a charge for 800 KB (kilobyte), is already charged at the time of error interruption.

  Thereafter, the cause of the communication error is removed, the network communication is returned to the normal state, and the MFP 1 and the server 90 are returned to a state where communication is possible.

  The user UA of the MFP 1 operates the MFP 1 to display the menu screen GA1 on the touch screen 6c again, and presses the button BN14 (FIG. 5) in the screen GA1 again. Here, when the MFP 1 determines that the data of the job (for example, download print job) regarding the incomplete transmission request RQ1a still remains in the communication management table TB1 (FIG. 8), the communication regarding the communication job is interrupted. Judge that he was doing.

  Here, the communication management table TB1 (see FIG. 8) is a data table for managing a transmission request RQ that has ended abnormally (specifically, job data relating to the transmission request RQ). The communication management table TB1 is stored in the storage unit 5 of the MFP1. Job data related to a certain transmission request RQ is recorded (registered) in the communication management table TB1 at the start of communication related to the transmission request RQ, and is deleted when communication related to the transmission request RQ is normally completed. In other words, if communication related to a certain transmission request RQ is not normally completed, the communication job data related to the transmission request RQ remains in the communication management table TB1. In other words, the communication job data related to the transmission request RQ1a in the unprocessed state (incomplete state) remains in the communication management table TB1.

  When it is determined that communication related to the “download print” job has been interrupted, the MFP 1 skips the screen GA2 (displayed following the screen GA1 during normal operation), and instead of the screen GA2, A screen GA3 (see FIG. 7) is displayed on the touch screen 6c. The MFP 1 specifies “file FL1” as the transmission target data D1 based on the communication job data related to the transmission request RQ1a remaining in the table TB1, and determines whether or not to restart the download printing operation of the file FL1. Query user UA.

  When the “NO” button BN4 is pressed by the user UA, the MFP 1 deletes the communication job data related to the transmission request RQ1a from the communication management table TB1, and executes data communication based on the new transmission request RQ3. Specifically, the MFP 1 displays the screen GA2 (FIG. 6) again to accept the target file designation operation, and transmits a new transmission request RQ3 based on the file designation result using the screen GA2 to the server 90.

  On the other hand, when the “YES” button BN3 is pressed by the user UA, the MFP 1 determines that the resumption instruction (resumption instruction for the interruption operation) that the data communication based on the transmission request RQ1a should be resumed is given.

  Then, the MFP 1 acquires the communication amount (data size SZ1) of the data received by the MFP 1 up to the communication interruption time point TP (step SP16). The data size SZ1 is the total value of the received data at the time of interruption with respect to the data D1, and is acquired based on the size of the data file D1 being received. The data size SZ1 is also recorded in the communication management table TB1.

  The MFP 1 transmits a retransmission request RQ1b to the server 90 together with data indicating the data size SZ1 (step SP21). Here, the transmission request target data name ("file FL1") in the retransmission request RQ1b is the same as the transmission request target data name in the transmission request RQ1a. That is, the retransmission request RQ1b has the same contents as the transmission request RQ1a. In other words, the retransmission request RQ1b and the transmission request RQ1a have the same search condition (data specification condition) regarding the download target file.

  Upon receiving the retransmission request RQ1b, the server 90 starts a transmission operation for transmitting the transmission target data D1 to the MFP 1 in response to the retransmission request RQ1b (step SP22). On the other hand, the MFP 1 starts a re-receiving operation of the data D1 transmitted from the server 90 (step SP23). This communication operation is executed by dividing the transmission target data D1 into a plurality of packets according to a predetermined protocol, as in the first communication of the data D1.

  In this way, after an error has occurred during data communication based on the transmission request RQ1a, the MFP 1 makes a retransmission request on the condition that the communication job data related to the transmission request RQ remains in the communication management table TB1. An operation execution confirmation screen GA3 is displayed on the touch screen 6c. Then, in response to the operator's operation input (pressing operation of the button BN3) using the screen GA3, the MFP 1 restarts the data communication based on the transmission request, in other words, the retransmission request. An operation execution instruction is accepted. Then, in response to the instruction given by the user, the MFP 1 transmits a retransmission request RQ1b to the server 90. Thereby, the data communication regarding the data D1 is resumed.

  Here, the server 90 transmits the entire transmission target data D1 (for example, 1000 Kbytes) from the beginning. Note that it is possible to transmit only the scheduled transmission data after the interruption time point TP (untransmitted data at the interruption time point TP) at the time of error recovery. If this is changed, data inconsistency may occur. In particular, when the transmission target data D1 stored in the cloud is a shared file or the like, partial data change or the like by other users may occur, and thus data inconsistency is likely to occur. On the other hand, if all the transmission target data D1 is transmitted again, it is possible to avoid such inconvenience.

  In addition, the accounting processing unit 83 of the server 90 not only transmits the transmission amount of the transmission target data D1 based on the retransmission request RQ1b (also referred to as transmission data size SZ2), but also the interruption time point TP of the transmission target data D1 based on the transmission request RQ1a. Based on the transmission amount up to (the above data size SZ1), the charging process is executed as needed (step SP24).

  Thereafter, in step SP29, all communication operations of the transmission target data D1 based on the retransmission request RQ1b are completed. Then, a print output operation based on the transmission target data D1 is started, and a printed matter based on the transmission target data D1 is output. Here, the case where the print output operation based on the transmission target data D1 is started after the completion of all the communication operations of the transmission target data D1 is illustrated, but the present invention is not limited to this. For example, the print output operation based on the transmission target data D1 may be executed at any time with the reception operation of the transmission target data D1. More specifically, each time the data of each page is received, the print output operation for each page may be executed.

  In step SP24, first, a fee PR2 corresponding to the data size SZ2 is calculated. Specifically, each time a unit information amount (for example, 1 kilobyte) is transmitted, a fee (unit price) per unit information amount is added to calculate a fee PR2. For example, when 1 yen is charged for every 1 KB (kilobyte), when transmission of all data (transmission data size SZ2 = 1000 (KB)) is normally completed, 1000 yen, which is a charge for 1000 KB (kilobyte), Calculated as a fee PR2 corresponding to the data size SZ2.

  However, in step SP24, the billing processing unit 83 calculates a fee for data communication based on the retransmission request RQ1b based on not only the fee corresponding to the data size SZ2 but also the data size SZ1.

  For example, when the data size SZ2 (1000 KB (kilobytes)) is larger than the data size SZ1 (800 KB), the charge PR2 (1000 yen) corresponding to the data size SZ2 to the charge PR1 (800 yen) corresponding to the data size SZ1. The amount PR3 (= PR2−PR1 = 200 yen) obtained by subtracting is calculated as a charge PR20 related to data communication based on the retransmission request RQ1b. This fee PR3 (200 yen) is additionally charged separately from the charging fee PR1 (800 yen) at the time of transmission of the first transmission request RQ1a. That is, the total fee (1000 yen) of the charging fee PR1 (800 yen) at the time of transmission of the first transmission request RQ1a and the charging fee PR3 (200 yen) at the time of transmission of the retransmission request RQ1b is charged.

  According to this, it is possible to avoid double charging for a portion corresponding to the transmission data amount (for example, 800 KB) for the first transmission request RQ1a. Specifically, in addition to the charging fee PR1 (800 yen) at the time of transmission of the first transmission request RQ1a, a charging fee PR2 (1000 yen) based only on the data size SZ2 at the time of transmission of the retransmission request RQ1b is further charged. You can avoid that. That is, it is possible to avoid charging the total fee PR9 (= PR1 + PR2 = 1800 yen). Therefore, it is possible to realize a more appropriate billing process.

  In addition, as described above, the content of the transmission target data D1 stored in the server 90 may be changed after communication interruption due to an error. The data size of the transmission target data D1 after the change may be smaller than the data size of the transmission target data D1 before the change.

  For example, as the transmission target data D1 is changed, the total data size SZ2b (700 KB (kilobytes)) of the transmission target data D1 after the change may be smaller than the already communicated data size SZ1 (800 KB). .

  If the charge PR2b (700 yen) corresponding to the data size SZ2b is smaller than the data size SZ1, the charging processing unit 83 calculates the charge PR20 related to data communication based on the retransmission request RQ1b as “zero” (yen). Then, a charging process is performed in which the charge PR20 related to data communication based on the retransmission request RQ1b is not added.

  According to this, it is possible to avoid double charging for the portion corresponding to the transmission data amount for the first transmission request RQ1a, and to realize more appropriate charging processing.

  Alternatively, the present invention is not limited to this, and when the data size SZ2b is smaller than the data size SZ1, the billing processing unit 83 changes the fee PR1b corresponding to the data size SZ1 from the fee PR2b (700 yen) corresponding to the data size SZ2b. An amount PR4 (= PR2b−PR1 = −100 yen) obtained by subtracting 800 yen may be calculated as a charge PR20 related to data communication based on the retransmission request RQ1b. The fee PR4 (−100 yen) is added to the charging fee PR1 (800 yen) at the time of transmission of the first transmission request RQ1a, and 700 in total for the data communication related to the transmission request RQ1a and the data communication related to the retransmission request RQ1b. A yen (= 800 + (− 100)) may be charged. Here, the fee PR4 is a negative value, and it is also expressed that the absolute value of the fee PR4 is determined as a refund amount. Therefore, in such an aspect, when the data size SZ2b is smaller than the data size SZ1, the re-transmission request is made by subtracting (subtracting) the return amount (absolute value of the fee PR4) from the original fee PR1. It is also expressed that the billing process of data communication based on RQ1b is performed.

  In the above-described embodiment, it has been described that job data related to a transmission request RQ is deleted from the communication management table TB1 when communication related to a transmission request RQ is normally completed. The job data related to the transmission request RQ may be deleted from the communication management table TB1 in the following cases other than the case where the data communication related to the job is normally completed. Specifically, when a new search condition (data specification condition) is input and / or when the user intentionally interrupts the job (by pressing the reset key or the like), it is deleted. Also good. Also in such an aspect, it is only necessary to determine that the communication job data related to the transmission request RQ remaining in the communication management table TB1 is interrupted due to an error. Then, on the condition that the communication job data related to the transmission request RQ remains in the communication management table TB1, it is determined that a restart instruction for resuming data communication based on the transmission request RQ is given. The retransmission request RQ1b may be issued.

<3. Countermeasures against unauthorized use>
By the way, when the above operation is executed, there is a possibility that the following illegal use or the like is performed. Specifically, there is a possibility that an error is intentionally generated when data updated at a relatively high frequency is downloaded, and download printing is performed a plurality of times at a download printing fee of one time.

  Specifically, in a download print job that downloads target data D1 including a plurality of pages (for example, 10 pages), data necessary for only the first page is arranged, and the remaining pages (for example, the remaining 9 pages) are dummy. Data is placed. A communication error is intentionally generated by an unauthorized user when the data communication and printing of the first page is completed.

  Thereafter, after the target data D1 is updated, the second download printing is performed. At this time, a retransmission request RQ1b is transmitted from the MFP 1 to the server 90, and a communication error is intentionally generated by an unauthorized user when the data communication and printing of the first page is completed. According to the operation according to the above embodiment, the received data size SZ2 in the second download print job (data communication based on the retransmission request RQ1b) is equal to or smaller than the received data size SZ1 in the first download print job. Will not be charged for the second download print job. Therefore, it is possible to execute the second download print job substantially free of charge.

  By repeating the same operation, it is possible to execute a plurality of download print jobs at a charge of one download print job (specifically, a download print job related to only the first page). is there.

  Therefore, here, the following illegal use prevention measures are exemplified. Note that the following fraud prevention operation is realized by cooperation of the unauthorized use detection unit 35 and the data communication control unit 32.

  Specifically, as shown in FIG. 8, the MFP 1 also records the number of errors (number of occurrences of errors) NE in the communication management table TB1.

  When the error number NE reaches a predetermined threshold value TH, the MFP 1 does not issue a retransmission request RQ1b. For example, when the error number NE in the download print job related to the file FL1 of the user UA reaches a predetermined threshold value TH (for example, 5 times), the MFP 1 transmits the communication job data (download print job) related to the transmission request RQ1a to the communication management table TB1. And re-transmission request RQ1b is not issued. The number of errors NE is the same as the number of times NR (or a number “1” larger than the number of times NR) when the retransmission request RQ1b having the same content as the transmission request RQ1a is sent, and can be converted into the number of times NR. is there. Therefore, the error number NE reaching the predetermined threshold value TH is equivalent to the number of times the transmission request RQ1b is transmitted reaching the predetermined threshold value THb.

  Then, the MFP 1 transmits a new transmission request RQ2 to the server 90 instead of the “retransmission request RQ1b”. The new transmission request RQ2 specifies the same file (file with the same name) as the transmission request RQ1a as a transmission target file. In other words, the new transmission request RQ2 has the same data specification condition as the data specification condition of the transmission request RQ1a. However, the new transmission request RQ2 is not a retransmission request and does not accompany the notification of the transmitted data size SZ1. The charging processing unit 83 calculates a fee PR30 (for example, 500 yen) related to data communication based on the new transmission request RQ2 based on the data size SZ3 that is the data communication amount based on the new transmission request RQ2, and calculates the fee PR30. A separate fee is charged separately from the fee PR1 and the like. As described above, the charging process for the data communication related to the new transmission request RQ2 is executed independently of the charging process for the data communication related to the original transmission request RQ1.

  In this way, after an error has occurred during data communication, unauthorized use can be avoided by not allowing retransmission requests more frequently than a predetermined level.

<4. Modified example>
Although the embodiments of the present invention have been described above, the present invention is not limited to the contents described above.

  For example, in the above embodiment, the case where the above idea is applied to a download print job is illustrated, but the present invention is not limited to this. Specifically, the MFP 1 downloads the address book (address book data and the like) from the server 90, and applies the above-described concept in the address book download service that displays the address book on the touch screen 63 based on the downloaded data. May be. Alternatively, the above idea may be applied to other jobs.

  In the above embodiment, after an error has occurred during data communication based on a transmission request, a restart instruction indicating that data communication based on the transmission request should be resumed is given by an operator input, and the operation input However, the present invention is not limited to this. For example, a restart instruction indicating that data communication based on a transmission request should be resumed on the condition that job data relating to the transmission request RQ remains in the communication management table TB1 when a predetermined time has elapsed since the occurrence of the error. The MFP 1 may automatically determine that the transmission request has been made, and a transmission request having the same content as the transmission request RQ may be issued. In short, data communication may be resumed after an error occurs by automatic retry using a timer or the like.

  Moreover, in the said embodiment, although the unauthorized use prevention measure based on the error frequency NE was illustrated, it is not limited to this. For example, the following illegal use prevention measures may be taken using a checksum in data communication.

  Here, the checksum is originally used as follows.

  Prior to data communication, a checksum (regular value) CS relating to transmission target data is first transmitted from the server 90 (transmission source apparatus) to the MFP 1 (transmission destination apparatus). The MFP 1 stores the received checksum (regular value) CS.

  Next, when the transmission target data is transmitted from the server 90 to the MFP 1 and the data communication of the transmission target data is completed, the MFP 1 calculates a checksum (calculated value) CK based on the received transmission target data (reception data). To do. Then, the MFP 1 compares the checksum (regular value) CS received in advance with the checksum (calculated value) CK calculated based on the received data. If both CS and CK match, it is determined that the data has been received normally, and if both CS and CK do not match, the presence of a data error is detected.

  However, in the following countermeasure against unauthorized use, the value CS relating to a plurality of communication data, which is the former value CS of the two types of checksum values CS and CK, is used. In this countermeasure against unauthorized use, the comparison process between the value CS and the value CK may not be performed.

  Here, the regular checksum CSa transmitted prior to data transmission of the first transmission target data and the regular checksum CSb transmitted prior to data transmission of the second transmission target data (retransmission target data). Can be received by the MFP 1 even when a communication error occurs midway. If the first transmission target data and the second transmission target data are completely the same, the checksum CS transmitted from the MFP 1 side is unchanged. That is, the checksum (normal value) CS1a for the first transmission target data and the checksum (normal value) CS1b for the second transmission target data are the same.

  Using such characteristics, the first transmission target data D1 (D1a) and the second transmission target data are based on the identity of the checksum (regular value) CS transmitted from the server side to the MFP 1. The identity with D1 (D1b) is determined.

  Specifically, prior to the first data communication, checksum communication regarding the transmission target data D1a is performed, and after the MFP 1 receives the checksum CSa (regular value) regarding the transmission target data D1a, the transmission target data D1a Start receiving.

  An error occurs during communication of the transmission target data D1 (specifically, D1a). Then, after the error is resolved, the second data communication regarding the transmission target data D1 (D1b) is performed in response to the retransmission request RQ1b.

  However, prior to the second data communication, communication for transmitting the checksum CSb related to the transmission target data D1b is performed.

  The MFP 1 compares both the checksum CSa related to the first transmission target data D1a and the checksum CSb related to the second transmission target data D1b. When both CSa and CSb are the same, it is determined that the transmission target data D1a and the transmission target data D1b are the same. On the other hand, when both CSa and CSb are not the same, it is determined that the transmission target data D1a and the transmission target data D1b are not the same.

  When the retransmission request for the data file with the same name is repeatedly executed, the MFP 1 performs the same determination operation as the identity determination operation based on the values CSa and CSb (identity determination operation based on the values CSp and CSq). Repeatedly. Specifically, the checksum data CSp of the previous (i-1) th transmission target data (data based on a transmission request or a retransmission request) and the current transmission target data (based on the i-th retransmission request). Data) is compared with the checksum data CSq, and the identity of the data is determined.

  In this modified example, when the number of times that the previous transmission target data (D1a, etc.) and the current transmission target data (D1b, etc.) are determined not to be the same (the number of times of mismatch determination regarding identity) reaches a predetermined value, As in the case of the unauthorized use prevention measure, the retransmission request RQ1b is not issued. Note that, until the number of times reaches a predetermined value, the retransmission request RQ1b is issued as in the above embodiment.

  Specifically, when an error occurs during data communication based on transmission request RQ1a (or transmission request RQ1b), the number of times of data mismatch determination (the number of times determined to be mismatch) reaches a predetermined value. The MFP 1 transmits “new transmission request RQ2” to the server 90 instead of the re-transmission request RQ1b. The new transmission request RQ2 designates the same file (file with the same name) as the transmission request RQ1a as a transmission target file, but is not accompanied by a notification of the transmitted data size SZ1, and is distinguished from a retransmission request.

  In addition, the accounting processing unit 83 calculates a fee PR30 related to data communication based on the new transmission request RQ2 based on the data size SZ3 which is a data communication amount based on the new transmission request RQ2, and calculates the fee PR30 as the fee PR1. In addition to charging separately. The charging process for the data communication related to the new transmission request RQ2 is executed independently of the charging process for the data communication related to the transmission request RQ1. In this way, unauthorized use can be avoided by not accepting re-transmission requests with a frequency higher than a predetermined level.

1 MFP
90 server 100 data communication system RQ1a transmission request RQ1b retransmission request RQ2 (another) transmission request SZ1 (first) data size SZ2 (second) data size TP interruption point

Claims (9)

A data communication system,
Server,
A data communication device connected to the server via a communication network;
With
The data communication device includes:
First communication control means for transmitting a data transmission request to the server and receiving data based on the transmission request from the server;
The amount of data communication based on the transmission request, which is the amount of data transmitted from the server to the data communication device up to the point of communication interruption due to the occurrence of an error in data communication based on the transmission request Obtaining means for obtaining a first data size;
Have
The first communication control means of the data communication device includes:
After an error occurs during data communication based on the transmission request, a re-transmission request having the same data specification condition as the data specification condition included in the transmission request is sent to the server together with data indicating the first data size. Send
The server
Second communication control for transmitting data based on the transmission request to the data communication device in response to the transmission request, and transmitting data based on the retransmission request to the data communication device in response to the retransmission request Means,
Charging means for calculating a first charge for data communication based on the transmission request based on the first data size;
With
The billing means of the server is
A second fee for data communication based on the retransmission request is calculated based on not only the second data size, which is a data communication amount based on the retransmission request, but also the first data size. A data communication system. The data communication system according to claim 1, wherein
When the second data size is larger than the first data size, the charging unit subtracts a charge corresponding to the first data size from a charge corresponding to the second data size, A data communication system, wherein the second fee is calculated. The data communication system according to claim 1 or 2,
The billing means calculates the second fee as zero when the second data size is smaller than the first data size. The data communication system according to claim 1 or 2,
If the second data size is smaller than the first data size, the billing unit subtracts the charge corresponding to the second data size from the charge corresponding to the first data size. Is determined as a refund amount, and the refund amount is subtracted from the first fee. The data communication system according to any one of claims 1 to 4,
The first communication control means is provided with a restart instruction indicating that data communication based on the transmission request should be resumed on condition that job data relating to the data transmission request remains unprocessed. A data communication system characterized by determining that the request has been received and transmitting the retransmission request together with data indicating the first data size to the server. The data communication system according to any one of claims 1 to 5,
The data communication device includes:
Means for recording the number of times the retransmission request having the same data specification condition as the data specification condition included in the transmission request is sent;
Further comprising
The first communication control unit transmits a new transmission request to the server instead of the retransmission request when the number of times has reached a predetermined value after an error has occurred during data communication.
The charging unit calculates a third fee related to the data communication based on the new transmission request based on a third data size which is a data communication amount based on the new transmission request, and the third fee A data communication system, which is charged additionally. The data communication system according to any one of claims 1 to 5,
The data communication device includes:
Means for comparing the checksum data of the previous transmission target data based on the transmission request or the retransmission request with the checksum data of the current transmission target data and determining the identity of the data;
Further comprising
The first communication control means sends a new transmission request instead of the retransmission request when the number of inconsistency determinations regarding data identity has reached a predetermined value after an error has occurred during data communication. Send to the server,
The charging unit calculates a third fee related to data communication based on the new transmission request based on a third data size that is a communication amount of data based on the new transmission request, and the third fee A data communication system, which is charged additionally. A server connected to a data communication device via a communication network,
Communication control means for transmitting data based on a transmission request from the data communication device to the data communication device;
A data communication amount based on the transmission request, which is a communication amount of data transmitted to the data communication device up to a communication interruption time point due to an error occurrence during data communication based on the transmission request. Billing means for calculating a charge for data communication based on the transmission request based on a data size;
With
The communication control means is a re-transmission request transmitted from the data communication device after an error has occurred during data communication based on the transmission request, and the same data as the data specification condition included in the transmission request Based on the retransmission request having the specified condition, the specified data is transmitted to the data communication device,
The charging means calculates a charge for data communication based on the retransmission request based on the first data size as well as the second data size which is a data communication amount based on the retransmission request;
A server characterized by that. A data communication method comprising:
a) transmitting a transmission request, which is a data transmission request, from the data communication apparatus to the server;
b) transmitting data based on the transmission request from the server to the data communication device;
c) The amount of data communication based on the transmission request, which is the amount of data received by the data communication device up to the point of communication interruption due to the occurrence of an error in data communication based on the transmission request. Calculating a first charge for data communication based on the transmission request based on the data size of
d) After an error has occurred during data communication based on the transmission request, a re-transmission request having the same data specification condition as the data specification condition included in the transmission request is sent together with the data related to the first data size. Transmitting from the communication device to the server;
e) transmitting data based on the retransmission request from the server to the data communication device;
f) calculating a second fee for data communication based on the retransmission request based on not only the second data size that is the amount of data communication based on the retransmission request but also the first data size When,
A data communication method characterized by comprising:

Images