JP4454787B2 - Printing system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention provides a file created using an application program.printingDoprintingIt is about the system.
[0002]
[Prior art]
  Conventionally, various related technologies for application service providers (hereinafter simply referred to as ASPs) that provide the above-described system have been developed, particularly focusing on billing technologies.
[0003]
  For example, “Operation management system and operation management method” of Japanese Patent Laid-Open No. 10-83298 is a system for managing the operation of an application, and a function for generating data among functions included in an application is weighted for each function. Is attached.
[0004]
  A certain value (battery value) is set in advance in the operation management counter, and the count for the weight value is decremented each time a function for generating data is used, and this count value is set to a predetermined limit. When the value is reached, the operation of the application is limited.
[0005]
  Also, according to “Software Usage Management Method and System” of Japanese Patent Application Laid-Open No. 11-212785, software is downloaded from the network, the usage time is returned to the host at the time of execution, and charging is performed at the host. Alternatively, the usable time is set in advance, subtracted during use, and when it becomes 0, the use is prohibited (Pre-paid method).
[0006]
  In addition, according to “Software Usage Management System” of Japanese Patent Laid-Open No. 11-85502, a fee system that charges according to the usage time, the number of times of use, etc. of each provided content is adopted, and the file format cannot be read. It is a software usage management system for playing back content in a readable format, whereby the content user can pay a fee according to the usage frequency.
[0007]
  Further, according to “Information Processing Device and Software Management Method” of Japanese Patent Laid-Open No. 10-333901, when identification information of a user who uses an application program is input, a program that controls the application receives a ticket, The application can be used only for the time allowed by the ticket.
[0008]
  In addition, according to the “metered charge type program license management system” disclosed in Japanese Patent Laid-Open No. 10-320070, this program unit price, usage time, etc. are stored in a server client model with a metered program license on the server. The client can know the license fee for using the program.
[0009]
  Further, according to “General Application Distribution Method” disclosed in Japanese Patent Application Laid-Open No. 9-305675, when a general-purpose application is required, only necessary functions are purchased, and the purchase is made until necessary. The maintenance and management (version upgrade, etc.) of applications that have not been performed are performed by the vendor, and charging is performed according to the functions actually used by the purchaser.
[0010]
  Japanese Patent Publication No. 6-19707, “Software Management Method” relates to fee management for fee-based software. Each user has user-specific data for recording a software available fee in a prepaid manner. The usage fee is reduced each time the card is used, and if it is insufficient, it cannot be used, but it can be used again by adding an available fee with an IC card.
[0011]
[Problems to be solved by the invention]
  However, in the case of the prior art as described above, the following problems have occurred. When using application services in the conventional ASP system, it is not a visible product,(1)Are you charged for application uptime,(2)You are charged for the number of times you use the application,(3)Or, it has come to be charged on a functional basis.
[0012]
  (1)In this case, it is impossible for the user to determine whether or not the time subject to billing is actually counted as the time used for the benefit of the user, and the user is not compensated for such billing fee. I was not necessarily convinced to pay.
[0013]
  Also(2)In this case, the result desired by the user may not be output during one use, and a certain result may be obtained by multiple use depending on the user's convenience. In particular, the user was not convinced.
[0014]
  further,(3)in the case of,(1)And(2)For the same reason, the user was not convinced.
[0015]
  On the other hand, among the techniques disclosed in the above-mentioned publications, in the “operation management system and operation management method” disclosed in Japanese Patent Laid-Open No. 10-83298, the unit of charge can be interpreted as a function product. If you look at it, you can pay for each function in the app. If the corresponding function is used, the billing amount will increase as much as it is used, and no matter how many times it is used for each app, if the product is not output, no billing will occur.
[0016]
  Further, in “Software Usage Management Method and System” of Japanese Patent Application Laid-Open No. 11-212785, communication between a host and a client (indicated as “terminal” in the specification) includes the Internet, and is downloaded in advance, not downloaded at the time of use. In addition, there is no concept of server sharing, as charging is made according to usage time.
[0017]
  In addition, in the “software use management system” of Japanese Patent Application Laid-Open No. 11-85502, both the charge according to the number of times of use of the content provided by the MO and the charge according to the use time are shown in the embodiment. The point is not solved.
[0018]
  Further, in “Information processing apparatus and software management method” disclosed in Japanese Patent Laid-Open No. 10-333901, charging is performed when a ticket is issued, and execution permission / non-permission of an application is controlled by an application control program. There is no charge according to the case, and a pre-paid method using a ticket is adopted.
[0019]
  In addition, the “pay-as-you-use program license management system” disclosed in Japanese Patent Application Laid-Open No. 10-320070 performs collective management in a management department or the like, and each client can know the usage fee. The license fee is displayed.
[0020]
  In addition, the “general purpose application distribution method” disclosed in Japanese Patent Application Laid-Open No. 9-305675 is for paying per function, not for pay-per-use, and intended for users who want to use only a part of the functions of the integrated package software. It is what.
[0021]
  In addition, the “software management method” disclosed in Japanese Patent Publication No. 6-19707 does not indicate what the charge unit for using the software is, but indicates that it indicates that at least the charge unit is a product. It has not been.
[0022]
  The present invention has been made in view of the above circumstances, and the application·programApplications that users can use·programFor calculating usage chargesprintingThe purpose is to provide a system.
[0023]
[Means for Solving the Problems]
  In order to achieve the above object, a printing system according to the present invention is provided.,
  Receiving means for receiving a print processing request for data created using an application program to be charged;
  Application program used to create the data to be subjected to the requested printing processType ofIdentifying means for identifying
  The requestedDataPrint processing execution means for executing print processing;
  Print log recording means for recording the amount of printed matter obtained by the printing process for each application program based on the identification result of the identification means;
  Calculation means for calculating a usage fee for each application program based on the amount of printed matter recorded in the print log recording means.In the printing system
  Unit price storage means for storing the unit price of the application program for each processing content for data created by the application program;
The calculation means calculates a total amount of usage fees for the application program by summing charges for each processing content calculated based on a unit price for each processing content..
[0027]
  The calculated application·programIt is preferable to provide a notifying means for notifying the usage fee to a billing server that performs billing processing.
[0028]
DETAILED DESCRIPTION OF THE INVENTION
  Exemplary embodiments of the present invention will be described in detail below with reference to the drawings. However, the dimensions, materials, shapes, relative arrangements, and the like of the components described in this embodiment are not intended to limit the scope of the present invention only to those unless otherwise specified. Absent.
[0029]
  Moreover, in the following drawings, the same number is attached | subjected to the member similar to the member described in above-mentioned drawing. Further, in each of the following embodiments, each embodiment of the application / program billing system according to the present invention will be described. However, the description of these embodiments includes an apparatus, a totaling server, a billing management server, an application program, and the like according to the present invention. It also serves as a description of each embodiment of the program charging method, the charging program, and the recording medium on which the charging program is recorded.
[0030]
  (First Embodiment) First, a first embodiment of an application program billing system according to the present invention will be described with reference to the drawings.
[0031]
  In the present embodiment, an application server function and an application / program usage log are held on the MFP, and when printing is performed using an application, the application usage fee is added to the printing and charging is performed.
[0032]
  The usage log of the application program is sent to the charge management server, and the fee is distributed to the application provider. There are applications that are executed on the PC and those that are executed on the MFP, both of which hold the log in the MFP and are sent to the charge management server.
[0033]
  FIG. 1 is a configuration diagram showing the configuration of the system of the present embodiment. The MFP 3 is used in a stand-alone environment (a situation where a PC or server that uses the MFP is connected but is not connected locally). It shows the state being done.
[0034]
  As shown in FIG. 1, this system includes a billing management server (sales company) 1 that manages billing, an application provider (ASP) 2 that provides application programs, and an MFP 3 combined with a copier, a facsimile, and the like. It is composed of a network (Internet) 4 for connecting them.
[0035]
  The network 4 is Internet in the example shown in FIG. 1, but is not limited to such a network, and may be a network of a protocol other than TCP / IP. In addition, this network may be wireless or wired.
[0036]
  Next, another configuration of the present embodiment will be described with reference to FIG. FIG. 2 is a schematic diagram showing another configuration of the present system, and shows a state in which the MFP 3 is used in a LAN or an intranet.
[0037]
  In the system configuration shown in FIG. 2, the MFP 3 is connected to the LAN 5 together with the user terminal 6. The LAN 5 is connected to a network (Internet) 4 by a router 7.
[0038]
  This system may be in the form of FIG. 1 or in the form of FIG. 2 and may not be connected to an external network. However, if it is not externally connected, it is necessary to send accounting information to the sales company by another means such as a modem.
[0039]
  Next, the operation of this embodiment will be described with reference to FIG. FIG. 3 shows a sequence diagram when the application is executed on the user terminal 6 in the system shown in FIG.
[0040]
  As shown in FIG. 3, the user first requests the MFP to download an application using the user terminal (step S1). Based on this request, the MFP performs an authentication process and a file transfer process (step S2). When downloading of the application is completed, the user executes the application program (step S3). In this case, after downloading, the application program server may issue an execution instruction command to the downloaded application program for execution.
[0041]
  Then, the user requests the MFP to print data obtained by executing this application program (step S4).
[0042]
  Upon receiving this request, the MFP identifies the application program requested to print, executes the printing process, and updates the application program usage log (step S5, step S6, step S7).
[0043]
  Thereafter, the MFP calculates a charge amount. That is, the MFP transmits the calculated charging amount to the charging management server (step S8) based on the charging information transmission request from the charging management server (step S9).
[0044]
  Next, the billing management server that has received the billing information transmits a payment amount payment request to the user (step S10). However, in this case, a payment request is issued to the individual user, but it may actually be issued to the organization to which the user belongs.
[0045]
  Then, when remittance is received from the user terminal, the charge management server remits the share of the application / program provider to the application / program provider (step S11).
[0046]
  Next, a billing table used in the present embodiment will be described with reference to FIG. FIG. 4 is a charging table showing a fee charged when the application is used, and the printing fee is determined based on this table. The amount charged for the app includes the normal print.
[0047]
  In the example shown in FIG. 4, for example, the charge amount per normal print is 8 yen, and the charge amount per application A is 15 yen. The same applies to other applications.
[0048]
  FIG. 5 is an application / program usage log stored in the MFP, and stores the relationship between the application and the number of printed sheets. The application program usage log can also serve as application program count information of the present invention. The same applies to the following embodiments. This log is a log within one billing period (for example, one month) and is cleared after the billing process.
[0049]
  In the example shown in FIG. 5, for example, the normal print has 3501 printed sheets, and the application A has 335 printed sheets. The same applies to other examples.
[0050]
  Here, the update operation of the application usage log in the MFP in the present embodiment will be described with reference to FIG. FIG. 6 shows a flowchart of an application usage log update operation in the MFP in the present embodiment.
[0051]
  In the present embodiment, when the application usage log is updated, the MFP first determines whether or not the recording paper on which the image is formed has been discharged (step S201). If it is not discharged (No), it is in a discharge standby state. If it is discharged (Yes), the process proceeds to step S202.
[0052]
  Next, the MFP determines whether the paper discharge is an output from the application (step S202). If the sheet is not discharged from the application (No), the process proceeds to step S204, the number of printed sheets is added to the normal print log, and the operation ends.
[0053]
  If the sheet is discharged from the application (Yes), the application number is stored in N in step S203, the number of applications printed is added to the application usage log (step S205), and the operation ends.
[0054]
  FIG. 7 is a table showing the calculation results of the printing and application usage fees derived from the table of FIG. 4 and the log of FIG. This is derived by multiplying the table of FIG. 4 and the number of printed sheets of FIG. 5 for each row. Here, the sales company refers to a sales company that performs sales, management, maintenance, and the like of the MFP. The normal printing equivalent is distributed to the sales company, and the application usage fee is distributed to the application provider.
[0055]
  For example, in a normal print, the total amount is 28008 yen, the sales company share is 28008 yen, and the provider share is 0 yen. The total amount of application A is 5025 yen, the sales company share is 2680 yen, and the provider share is 2345 yen. Others are the same.
[0056]
  Next, a method for calculating the table shown in FIG. 7 will be described with reference to FIG. FIG. 8 is a flowchart showing a calculation method of the table of FIG.
[0057]
  As shown in FIG. 8, when calculating the charge amount, the total amount is calculated from the application log and the charge table (step S71).
[0058]
  Next, it is determined whether or not printing is normal printing (step S72). If it is normal printing (Yes), the process proceeds to step S75. If it is not normal print (No), the normal print is subtracted from the total amount, the result is added to the app provider, and the normal print is added to the sales company (step S73, step S74, step S75).
[0059]
  Next, it is determined whether or not the processing of all applications has been completed. If it has not been completed (No), the process proceeds to step S71. If it has been completed (Yes), the operation is terminated (step S76).
[0060]
  FIG. 9 is an overview of the application server of this system and the MFP that holds the log. An MFP is a copier that combines functions such as a printer and a FAX, and has hardware capable of mounting functions as a server such as a CPU and a hard disk.
[0061]
  FIG. 10 is a hardware block diagram of the MFP 3 shown in FIG. 2, which has a CPU on the main controller 23, and each function is connected through a system bus 26.
[0062]
  In FIG. 10, the scanner engine 15 drives the scanner together with the scanner controller 16.
[0063]
  The print engine 17 drives the printer together with the print controller 18.
[0064]
  The display screen 19 displays instructions and warnings for the user, the operation panel of the MFP, the operation status, and the like.
[0065]
  The communication unit 20 is a device for the MFP to exchange data with other devices, and performs communication using a predetermined protocol such as TCP / IP.
[0066]
  The input device 21 is a device for inputting data, and examples thereof include a touch panel, a pointing device, a mouse, a reset button, a start key, and a numeric keypad.
[0067]
  The memory 22 is used for storing image data, input contents, an MFP processing program, and the like. This memory 22 can be the first recording means and the second recording means of the present invention.
[0068]
  The main controller 23 is a device for controlling the entire MFP, and the operation of each member is controlled by the main controller 23.
[0069]
  The disk device 24 stores various application programs and the like, and functions as a kind of storage medium.
[0070]
  The log 25 stores the usage status of the application program within a predetermined period so far as an application program usage log, and is used to determine the charge amount of the user. This log 25 can also be the first recording means and the second recording means of the present invention.
[0071]
  FIG. 11 is a software block diagram of an application program stored in the MFP 3 shown in FIG. 2, which is equipped with a normal MFP function, an application server function for realizing the system, a log management function, and the like. Implemented in a state where communication with the outside is possible.
[0072]
  As shown in FIG. 11, the software configuration of the MFP of this system is a configuration in which a scanner driver 32, a printer driver 33, and an application file management 34 are connected to a network interface 31.
[0073]
  The scanner driver 32 is an application program for driving the scanner.
[0074]
  The printer driver 33 is an application program for driving the printer together with the print engine controller 36.
[0075]
  The application file management 34 controls various application programs 37 and manages the application usage log 35.
[0076]
  The application usage log 35 is a file that records the usage status of the application program, and its update and reference are managed by the application file management 34.
[0077]
  There are a plurality of application programs whose update and reference are managed by the application file management 34.
[0078]
  Next, the operation of the MFP 3 of this system shown in FIG. 2 will be described with reference to FIGS. 12 to 17 are schematic diagrams showing a touch panel screen on the operation panel of the MFP.
[0079]
  As shown in FIG. 12, various tabs 41 indicating various functions of the MFP are shown at the top of the screen, and the user selects a function by touching the tab 41 indicating the function to be used with a finger. This figure shows the touch panel screen in a state where the file function is selected.
[0080]
  Further, FIG. 12 shows a configuration of a screen for presenting the application program in the MFP and a list of charges for each of the generated results to the user and selecting an application program desired to be used from the presented application programs. Show.
[0081]
  In this screen, when the output is output as data (file) generated by the application program as a printed product, when it is sent to the outside as an attached file of an e-mail, or when it is sent as image data by facsimile Is shown.
[0082]
  From this screen, the user selects an application program suitable for the purpose of use and budget by touching a virtual button with a finger.
[0083]
  It is assumed that the user has selected an application C that provides an OCR function. As a result, the application C is activated, and the touch panel screen is as shown in FIG.
[0084]
  FIG. 13 is displayed in a screen configuration corresponding to the selected application program. In this figure, the screen is displayed in a screen configuration for using the OCR function of the currently selected application C.
[0085]
  The user selects an image file to be subjected to OCR from a pull-down list of a file list displayed by touching a file list button. Thereby, as shown in FIG. 14, the contents of the designated file are displayed in the input image display field.
[0086]
  When the OCR execution button 42 is touched here, the OCR processing is executed, and the result is displayed in the OCR result display field as shown in FIG.
[0087]
  By the way, in this embodiment, charging is not performed only by performing OCR processing. Therefore, the user can perform OCR processing by respecifying the file as many times as necessary without worrying about the application program usage fee.
[0088]
  Next, when the user touches the print button 43 in FIG. 15, the touch panel screen becomes as shown in FIG. This figure is for instructing to print the result of OCR processing, and displays the name of the application program used and the name of the file to be processed.
[0089]
  The unit price and total charge when the processing result is printed out are displayed. When the user is satisfied with the display, the user touches the print execution button. To stop printing, touch the cancel button to cancel printing and return to the screen of FIG.
[0090]
  On the other hand, when the user touches the storage button 44 in FIG. 15, the touch panel screen is as shown in FIG. This figure is for storing the result of OCR processing as a file, and the name of the application used and the name of the file to be processed are displayed.
[0091]
  Further, in the present embodiment, there is no charge for storage only, so this is displayed. Touch the save execution button to save. If not stored, touch the cancel button to return to the screen of FIG. When the storage execution button is touched, a screen on which various character keys are arranged and characters can be input like a keyboard may be displayed separately so that the user can input a file name or the like.
[0092]
  On the other hand, when the clear button 45 is touched in FIG. 15, the displayed input file name, input image display field display content, and OCR result display field display content are cleared, and the state returns to the state of FIG. If the cancel button is touched in FIG. 15, the screen returns to the screen of FIG. 12 without doing anything.
[0093]
  In FIGS. 13 to 15, to the right of each of the OCR execution button 42, the print button 43, and the storage button 44, a charge amount that will be charged when these instructions are given is the total charge and the unit price. Is displayed.
[0094]
  In the case of the present embodiment, there is a charge only for a print instruction, and since OCR processing itself and the result data storage are free, it is displayed as free from the beginning.
[0095]
  Regarding printing, e-mail transmission, and FAX transmission, the charge amount is not fixed at the stage of FIG. 13, so it is represented by a gray pattern, and is displayed when the charge amount is fixed after the OCR process is completed in FIG. To do.
[0096]
  As described above, in the present embodiment, when the application program is executed and printing is executed (FIG. 16), the user is charged. In other cases, for example, the OCR function is executed and stored without printing (FIG. 17). ) Is not charged.
[0097]
  Therefore, according to the present embodiment, when the application program is only executed, the user is not charged just for executing the application program, such as the operation time of the application program, the number of times of use, and the function unit. Therefore, the user can pay the fee in a state of being satisfied according to the result of the application program.
[0098]
  In the present embodiment, the usage status of the user's application programs compiled by the MFP 3 is transmitted to the billing management server 1 via the network 4, so that no matter where the MFP 3 is installed, The billing management server on the sales company side can manage the usage status of the application program and perform the billing process no matter what time zone the user is using the MFP 3, thereby further improving the billing process efficiency. More can be achieved.
[0099]
  Furthermore, since a printed matter, E-mail, FAX transmission, data output, and the like are prepared as a product obtained by the user, charging using the present embodiment can be applied to a wider range of application programs. The scope of program providers can be expanded.
[0100]
  In the above-described embodiment, the storage means of the present invention is the application server of the application provider shown in FIG. 1 or 2, and the instruction means, execution means, output means, and database are the MFP 3 shown in FIG. In the user terminal 6 shown in FIG. 2, the charging means is the charging management server 1.
[0101]
  (Second Embodiment) Next, a second embodiment of the application / program billing system according to the present invention will be described with reference to the drawings.
[0102]
  In the present embodiment, an application server function is held on a general server machine, and logs are held in a totaling server.
[0103]
  When a product is generated using the application, an application usage fee is charged for the product, and the log on the aggregation server is sent to the charge management server, and the fee is distributed to the application provider. The application is executed on the PC.
[0104]
  FIG. 18 is a system configuration diagram showing the configuration of the second embodiment of the application program billing system according to the present invention, in which the application servers 50 and 51 and the aggregation server 52 are used in the LAN 5 or in the intranet. It is a figure which shows a state.
[0105]
  As shown in FIG. 18, in this embodiment, a billing management server 1, at least one or more application providers 2, and a router 7 are connected to a network (Internet) 4.
[0106]
  The LAN 5 is connected to the network 4 via the router 7. Connected to the LAN 5 are application servers 50 and 51, an aggregation server 52, a user terminal 6, printers 53 and 54, a scanner 55, and a FAX 56.
[0107]
  Further, databases 57 and 58 storing application user data are connected to the application servers 50 and 51, respectively.
[0108]
  Thus, in the present embodiment, the application servers 50 and 51 and the aggregation server 52 are configured to exist separately.
[0109]
  FIG. 19 is an overview diagram of an application server and an aggregation server used in this system. In the present embodiment, the application servers 50 and 51 and the aggregation server 52 are separate devices, but may be in the same device.
[0110]
  Next, the internal configuration of the application servers 50 and 51 shown in FIG. 18 will be described with reference to FIG. FIG. 20 is an internal schematic diagram of the application server.
[0111]
  As shown in FIG. 20, in the application server, a network adapter 61 serving as a connection interface with the LAN, a FAX modem 62 for carrying data on a telephone line, and a video for displaying an image on a monitor 66 A card 63, a disk 65 as storage means for storing data, and a controller 64 for controlling these operations are provided.
[0112]
  As shown in the figure, the disk 65, which is a storage device such as a hard disk, includes a system area 67, an application area 68 that holds applications, and a user area 69 that holds user files.
[0113]
  This division may be logically divided, may be separate disks, or may be divided by directories in the same disk.
[0114]
  Next, the internal configuration of the application servers 50 and 51 shown in FIG. 18 will be described with reference to FIG. FIG. 21 is a software block diagram of the application server shown in FIG. 18 and is divided into an application file management 72 connected to the network interface 71 and a user file management 73 connected to the network interface 71.
[0115]
  Various applications 74 are connected to the application file management 72.
[0116]
  Various user files 75 are connected to the user file management 73.
[0117]
  As described above, the software of the application servers 50 and 51 of the present embodiment is divided into a part for managing application files and a part for managing user files. Both areas are accessed through the network.
[0118]
  Next, the internal configuration of the aggregation server 52 shown in FIG. 18 will be described with reference to FIG. FIG. 22 is a software block diagram of the aggregation server 52 shown in FIG. 18. As seen in the figure, a charging table 82 and an application usage log 83 are connected through a network interface 81. That is, a log when an application on the application server is used is accumulated in the aggregation server, and charging information is calculated based on the charging table 82 and the application usage log 83.
[0119]
  Here, the application usage log update operation of the aggregation server 52 shown in FIG. 18 will be described with reference to FIG. FIG. 23 shows a flowchart of the application usage log update operation of the aggregation server 52 shown in FIG. In FIG. 23, N is a number for distinguishing application programs, K is a number indicating the type of data processing, and D is data held in a log.
[0120]
  First, the aggregation server 52 receives the application number N selected in the user terminal 6, the type of data processing, and the data held in the log (step S222). The type of data processing is FAX transmission, printing, and the data held in the log is the number of transmissions, the number of prints, and the like. Then, the type is stored in K, and the data is stored in D (step S223).
[0121]
  Next, the application number N of the application usage log and the data D are added to the field K indicating the process (step S224), and the operation ends.
[0122]
  Next, a billing table used in the present embodiment will be described. FIG. 24 is a billing table used in the present embodiment, and the charge varies depending on the application, how to extract the product, or the output destination.
[0123]
  In other words, when printing, sending to others by E-mail, sending to others by FAX, the charge differs depending on the case where the finished product is taken out as electronic data (content retrieval), and there are multiple charges for one product. If the application is involved, it will be charged twice.
[0124]
  Here, “retrieving deliverables” refers to a case where a file created using an application is taken out of the application server, and may be a method other than that described here, and may be associated with a billing table.
[0125]
  In addition, it is also possible to make all the extractions other than the unexpected extraction method the same amount as the content extraction.
[0126]
  However, FIG. 24A is a standard billing table, and FIG. 24B is a discount billing table. That is, it is not necessary to fix the billing table to one, and for example, the charge setting may be changed according to various conditions such as the output destination of the deliverable.
[0127]
  For example, the charge of the table shown in FIG. 24B is lower than the table shown in FIG.
[0128]
  Next, an operation when generating output information in the present embodiment will be described with reference to FIG. FIG. 25 shows a flowchart of the operation when the application server generates output information in this embodiment.
[0129]
  When generating output information, first, an output destination drive name is acquired (step S210). Then, it is determined whether or not the output destination drive is a drive on the application server. If it is a drive on the application server (Yes), the operation ends as it is, and if it is not a drive on the application server (No). In step S212, the fact that the file is a file is stored in the output information, and the operation ends.
[0130]
  Next, the application usage log 83 held in the aggregation server 52 shown in FIG. 18 of this embodiment will be described with reference to FIG.
[0131]
  FIG. 26 shows a schematic diagram of an example of the application usage log 83 held in the aggregation server 52. The example shown in FIG. 26 is an application usage log with a user ID. The application program usage log can also serve as application program count information of the present invention.
[0132]
  Although the table shown in FIG. 26 is sorted by user ID, the present invention is not limited to such a case. For example, for application A, the user ID 0001 has a print count of 102, an E-mail transmission of 42 kbytes, a FAX count of 13, and a content takeout count of 2. The same applies to other examples.
[0133]
  Next, the billing amount calculation result calculated by the tabulation server 52 shown in FIG. 18 of this embodiment will be described with reference to FIG. FIG. 27 shows a schematic diagram of an example of a charge amount calculation result with a user ID derived by a charge amount calculation process in the aggregation server 52.
[0134]
  In the example shown in FIG. 27, the number of print processes and the like are stored for each type of application used by the user, and the resulting total amount is stored.
[0135]
  Next, the billing amount calculation operation calculated by the aggregation server 52 shown in FIG. 18 of this embodiment will be described with reference to FIG. FIG. 28 (a) shows a flowchart of the billing amount calculation operation performed by the aggregation server 52 shown in FIG. 18 of the present embodiment.
[0136]
  In the flowchart shown in FIG. 28A, the tabulation server 52 first waits for a processing request (step S81). If file saving is selected (Yes), the process proceeds to step S84. If not selected (No), the process proceeds to step S83 (step S82).
[0137]
  In step S84, it is determined whether or not the file is stored in the application server. If the file is stored in the server (Yes), the operation is terminated. If the file is not stored in the server (No), the process proceeds to step S87. .
[0138]
  In step S83, it is determined whether or not E-mail is selected. If E-mail has been selected (Yes), the process proceeds to step S87, and if not selected, the process proceeds to step S85.
[0139]
  In step S85, it is determined whether or not FAX is selected. When the FAX is selected (Yes), the process proceeds to step S87, and when not selected, the process proceeds to step S86.
[0140]
  In step S86, it is determined whether printing has been selected. If printing is selected (Yes), the process proceeds to step S87, and if not selected, the process proceeds to step S88.
[0141]
  That is, in step S83, step S85, and step S86, it is determined whether or not the user is trying to obtain a product as a result of using the application program.
[0142]
  When a product such as E-mail is obtained, the total information is updated in step S87 and charging is performed. In step S88, other processing is performed to finish the operation.
[0143]
  Next, a second example of the billing amount calculation operation calculated by the tabulation server 52 shown in FIG. 18 of the present embodiment will be described with reference to FIG. FIG. 28B shows a flowchart when the charge amount calculation operation is performed by the aggregation server 52 shown in FIG. 18 of the present embodiment and the charge is different in the output destination domain.
[0144]
  However, since the flowchart shown in FIG. 28B is different from the flowchart shown in FIG. 28A only in step S89, step S90, and step S91, these different operations will be described.
[0145]
  In this operation, whether or not the output destination is the same domain when E-mail is selected in the determination in step S83 (Yes), or in the determination in step S84 that it is not in the server (No). Is determined in step S91.
[0146]
  If they are in the same domain (Yes), the process proceeds to step S90, where the charge table is a discounted charge table, and then the process proceeds to step S87.
[0147]
  On the other hand, if they are not in the same domain (No), the process proceeds to step S89 to set the charging table as a standard table, and the process proceeds to step S87.
[0148]
  Here, the process proceeds to step S89 also when FAX is selected in the determination of step S85 (Yes) and when printing is selected in the determination of step S86 (Yes).
[0149]
  That is, in the operation shown in FIG. 28B, the charging status is changed by changing the charging table depending on whether or not the data output destination is the same domain.
[0150]
  Next, in this embodiment, referring to FIG. 29, an operation for storing data in the application server 50 or the application server 51, an operation for printing the stored data, and a sequence when the data is transmitted by FAX or E-mail. I will explain. FIG. 29 shows an operation for storing data in the application server, an operation for printing the stored data, and a sequence diagram when transmitting the data by FAX or E-mail in this embodiment.
[0151]
  In FIG. 29, the user (terminal) requests the application server to download an application (step S101). Upon receiving this request, the application server performs authentication processing and file transfer (step S102).
[0152]
  Next, the user executes the application and requests data storage by this execution (step S103, step S104). Based on this request, the application server performs a saving process (step S105). In this case, after downloading, the application program server may issue an execution instruction command to the downloaded application program for execution.
[0153]
  Next, the user requests and executes any one or any combination of a print request, a FAX transmission request, and an E-mail transmission request (steps S106, S108, S109, S111, S112, and S114).
[0154]
  Then, the aggregation server updates the application usage log based on each request (steps S107, S110, S113).
[0155]
  Next, with reference to FIG. 30, a sequence of operations in the present embodiment when data is stored outside the application server, when content is extracted, and when charging collection processing is performed will be described. FIG. 30 shows a sequence diagram of operations in the present embodiment when data is stored outside the application server, when content is extracted, and when bill collection processing is performed.
[0156]
  In FIG. 30, the user (terminal) requests the application server to download an application (step S101). Upon receiving this request, the application server performs authentication processing and file transfer (step S102).
[0157]
  Next, the user executes the application and requests data storage by the execution (steps S103 and S104). Based on this request, the application server performs a saving process (step S105). However, this storage is assumed to be outside the application server. In this case, after downloading, the application program server may issue an execution instruction command to the downloaded application program for execution.
[0158]
  The application server that has received the storage request performs a storage process (step S105), requests the aggregation server to update the application usage log, and transmits data (steps S121 and S123). The user receives this data (step S122).
[0159]
  Next, the user requests the application server to retrieve the deliverable (step S124). In response to this request, the application server performs an application retrieval process (step S125), requests the aggregation server to update the application usage log, and transmits data (steps S1261 and S128). The user receives this data (step S127).
[0160]
  Next, the aggregation server 52 calculates a charge amount, and transmits the calculated charge amount to the charge management server 1 in response to a request from the charge management server 1 (steps S129 and S130).
[0161]
  Then, the accounting management server 1 outputs a payment request for the settlement amount based on the received accounting information and remits the share to the application provider (steps S131 and S132).
[0162]
  As described above, the example shown in FIG. 30 shows a case where the product of the application program is extracted as it is in a reusable form (content extraction).
[0163]
  Here, the operation when the billing amount is transmitted from the counting server 52 to the billing management server 1 will be described with reference to FIG. FIG. 31 shows a flowchart of the operation when the billing amount is transmitted from the collection server 52 to the billing management server 1 in this embodiment.
[0164]
  The flowchart shown in FIG. 31A is a flowchart when the calculated amount is transmitted from the aggregation server 52 to the charge management server 1 in this embodiment, and the flowchart shown in FIG. FIG. 6 is a flowchart when making a payment for payment by the accounting management server 1. FIG.
[0165]
  As shown in FIG. 31A, when transmitting the calculated amount from the aggregation server 52 to the accounting management server 1, the aggregation server 52 first calculates the amount from the application usage log and the accounting table, This amount is sent to the charge management server 1 (step S301, step S302).
[0166]
  Further, as shown in FIG. 31 (b), when the billing management server 1 makes a payment request for billing, billing information is acquired, and then a bill is issued (steps S303 and S304).
[0167]
  Next, the billing amount calculation operation performed in the aggregation server 52 of the present embodiment will be described with reference to FIG. FIG. 32 shows a flowchart of the calculation operation of the billing amount performed in the aggregation server 52 of this embodiment. When calculating the charge amount, as shown in FIG. 32, first, the total amount of the charge amount is calculated from the application usage log and the charge table (step S141).
[0168]
  Then, it is determined whether or not all application processes have been completed. If not completed (No), the process proceeds to step S141, and if completed (Yes), the operation ends.
[0169]
  Next, a screen displayed on the user terminal 6 as the client PC in the present embodiment will be described with reference to FIGS. FIG. 33 to FIG. 42 (excluding FIG. 40) show schematic diagrams of screens displayed on the user terminal 6 as the client PC in the present embodiment.
[0170]
  FIG. 33 shows a screen of software for downloading an application operating on the user terminal 6.
[0171]
  With this software, the user can download an application to be used from an arbitrary application server (the application server 50 or the application server 51 in FIG. 18). FIG. 33 also shows a state when an application server is selected with this software.
[0172]
  FIG. 34 is a screen for presenting to the user a list of A applications in the server of the selected application server (Application Server 1) and a fee list when a result is generated by the application.
[0173]
  From this screen, the user selects an application according to the purpose of use and budget. In this example, the second application B is selected.
[0174]
  It is disclosed to the user that this fee is 30 yen for printing, 100 yen for E-mail attachment, 10 yen for Fax, and 2000 yen for content retrieval.
[0175]
  If the user is satisfied with this fee, the user presses the “OK” button in the lower right to indicate the willingness to understand the fee and downloads the application B.
[0176]
  Also, the user ID used is notified to the application server at this timing.
[0177]
  In this embodiment, the information is notified to the application server on a non-description login screen. In addition, a technique that is shared with the OS login screen without using the login screen is also disclosed, and the user ID can be easily obtained on the server side.
[0178]
  Application B self-starts after downloading and presents the initial screen of FIG. Application B is OCR software in this example.
[0179]
  The user selects an image file to be subjected to OCR from “Input” of Menu.
[0180]
  As the input target file, one managed by the file server in the MFP is displayed. In the present embodiment, only items managed by the file server in the MFP are displayed. However, even if a file outside the MFP can be input, the present invention is acceptable.
[0181]
  Next, as shown in FIG. 36, the input image file is displayed in the middle image display section, and OCR is executed by the upper right execution button.
[0182]
  Then, as shown in FIG. 37, the TEXT output as a result of the OCR is displayed on the lower result display section.
[0183]
  Further, as shown in FIG. 38, this TEXT can be output by selecting Print / Fax / E-mail from the menu output. Here, FIG. 38 shows a case where printing is selected.
[0184]
  Then, the charge confirmation dialog shown in FIG. 39 is opened, the user's consent is reconfirmed, and printing is executed by pressing “OK”. The number of prints, the print size, and the like are passed through the application server 50 or the application server 51, and the totaling server 52 Will be notified.
[0185]
  The notification contents are output type (printing, fax, email attachment, content retrieval) and data (printing number, number of transmissions, file size, etc.).
[0186]
  Here, the information transmission operation from the application server 50 or the application server 51 in the present embodiment will be described with reference to FIG. FIG. 40 shows a flowchart of an information transmission operation from the application server 50 or the application server 51 to the aggregation server 51 in the present embodiment.
[0187]
  When sending information, first, an application number is input (step S151). And output information is acquired (step S152).
[0188]
  Next, it is determined whether or not the output is printing. If it is printing (Yes), the process proceeds to step S154. If it is not printing (No), the process proceeds to step S155.
[0189]
  In step S154, printing is stored in the type, and the number of printed sheets is stored in the data. Then, the process proceeds to step S161.
[0190]
  Next, it is determined whether or not the output is FAX. If the output is FAX (Yes), the process proceeds to step S156. If the output is not FAX (No), the process proceeds to step S157.
[0191]
  In step S156, FAX is stored in the type, and the number of FAX transmissions is stored in the data. Then, the process proceeds to step S161.
[0192]
  Next, it is determined whether or not the output is E-mail. If the output is E-mail (Yes), the process proceeds to step S158. If the output is not E-mail (No), the process proceeds to step S159.
[0193]
  In step S158, E-mail is stored in the type, and FileSize is stored in the data. Then, the process proceeds to step S161.
[0194]
  Next, it is determined whether or not the output is a file. If the output is a file (Yes), the process proceeds to step S160. If the output is not a file (No), the operation is finished as it is.
[0195]
  In step S160, content retrieval is stored in the type, and 1 is stored as the file number in the data. Then, the process proceeds to step S161.
[0196]
  In step S161, the application number N and the stored type and data are transmitted to the aggregation server 52.
[0197]
  In this way, the output type (print, fax, email attachment, content retrieval) and data (print number, number of transmissions, file size, etc.) are notified from the application server 50 or the application server 51 to the aggregation server 52.
[0198]
  Also, as shown in FIG. 41, TEXT data can be stored as a file by selecting the menu of application B to be stored.
[0199]
  In other words, the option can be stored inside the server, outside the server, but in the same domain, outside the server and outside this domain.
[0200]
  However, in the case of storage only, as shown in FIG. 42, a dialog indicating that the storage is free is displayed. When the server is selected, the dialog shown in FIG. 42 is displayed. At this time, it can be stored free of charge.
[0201]
  However, there may be a result output for billing such as printing in subsequent file operations. At that time, the result output is made in another application, and in order to prevent the usage fee of this application from becoming zero, information indicating that this application B was used at the time of this file storage is shown in FIG. In the file management information when multiple applications are used.
[0202]
  FIG. 43 shows a conceptual diagram of file management information when a plurality of applications are used in this embodiment. As shown in FIG. 43, in this case, a pointer of each file, application information, and the like are stored in the directory, the file is referred to by the file pointer, and the application information of the file includes the number of used applications, used application information, and the like. Stored.
[0203]
  Next, if you choose the same domain outside the server, you can take it out of the server and print as much as you want, so this is positioned as content retrieval, and taking it out of the server is a high fee setting.
[0204]
  However, as shown in (b) of FIG. 24, the content is extracted in the same domain, and thus it is calculated by applying a discount.
[0205]
  On the other hand, when storage outside the server and outside this domain is selected, this discount is not applied, and the standard accounting table shown in FIG. 24A is applied. The above movement is processed according to the flowchart shown in FIG.
[0206]
  Thus, according to the second embodiment of the application program billing system according to the present invention, the application server 50 or the application server 51 that stores and downloads the application program, and the usage status of the user's application program are determined. Even when the aggregation server 52 to be aggregated is separated, the aggregation contents of the aggregation server 52 are transmitted to the accounting management server via the network 4 and when the user is charged, the user uses an application program. In addition, for example, since charging is performed at the time when a product is obtained by performing data extraction processing such as printing processing and E-mail transmission, the same effect as in the first embodiment can be obtained. Regardless of the number of times the application program is used or the usage time, Can be in the form performs accounting.
[0207]
  In the above embodiment, the storage means of the present invention is the application server 50 or the application server 51 shown in FIG. 18, the instruction means and the execution means are the user terminal 6 shown in FIG. 18, and the output means. Is the printers 53 and 54, the scanner 55 or the FAX 56 shown in FIG. 18, and the charging means is the charging management server 1.
[0208]
  (Third Embodiment) Next, a third embodiment of the application program billing system according to the present invention will be described.
[0209]
  In the present embodiment, an application server function and a log are held on the MFP, and charging is performed when an application is used.
[0210]
  In this embodiment, the processing target is image data read by a scanner, and charging is not generated unless an application is used. Here, the difference from traditional charging for content (such as downloading images and music for a fee) is that the charge for using the app is charged to the deliverable, and it is not charged unless the app is used. Is a point.
[0211]
  The overall configuration of the third embodiment of the application program billing system according to the present invention will be described with reference to FIG. FIG. 44 is a system configuration diagram of the third embodiment of the application program billing system according to the present invention.
[0212]
  In the system configuration shown in FIG. 44, the MFP 3 is connected to the user terminal 6 and the LAN 5. The LAN 5 is connected to a network (Internet) 4 by a router 7. Therefore, the application provider 2 may not exist.
[0213]
  This system may not be connected to an external network. However, if it is not externally connected, it is necessary to send accounting information to the sales company by another means such as a modem.
[0214]
  The appearance of the MFP including the scanner used in the present embodiment is the same as the appearance of the MFP shown in FIG. In addition to those shown in FIG. 9, a server, such as a CPU or HD, is also provided inside and connected to the network.
[0215]
  Next, the operation of the present embodiment will be described with reference to FIG. FIG. 45 shows a sequence diagram of the operation of the present embodiment, and shows a sequence in the case of charging for application use (here, OCR processing is performed on an image).
[0216]
  As shown in FIG. 45, first, the user (terminal) transmits a normal scan request to the MFP (step S171). The MFP performs normal scan processing and transmits scan data to the user (steps S172 and S173). The user receives this scan data (step S174).
[0217]
  Next, the user outputs an OCR scan request to the MFP using OCR software as an application program (step S175). Upon receiving this request, the MFP performs OCR scan processing, updates the application usage log, and transmits the scan data to the user (steps S176, S177, and S178). The user receives this scan data (step S179).
[0218]
  Next, the MFP transmits the application usage log information to the charging management server 1 based on the application usage log information transmission request of the charging management server 1 (steps S180 and S181).
[0219]
  The billing management server 1 calculates a billing amount based on the received application usage log information and transmits a settlement payment request to the user (steps S182 and S183). However, in this embodiment, a payment request is issued to the individual user, but a payment request may be made to the organization to which the user belongs.
[0220]
  Then, the accounting management server 1 calculates the share of the application provider, and remits this share to the application provider (step S184).
[0221]
  Next, FIG. 46 shows a charging table used in the charging management server 1 of the present embodiment. In the billing table shown in FIG. 46, the billing amount for each impression is shown for each type of application. For example, it is 0 yen in normal scanning, but it is 100 yen in OCR.
[0222]
  Next, FIG. 47 shows an application / program usage log used in this embodiment. The log shown in FIG. 47 shows the number of scan impressions for each type of application. For example, it is 335 in the normal scan, but 258 in the OCR. The use log can also serve as application program count information of the present invention.
[0223]
  Next, FIG. 48 shows a billing amount breakdown table used in the present embodiment. The example shown in FIG. 48 is a calculation example of charging, and shows that charging does not occur in normal scanning, but charging occurs when an application is used.
[0224]
  Next, screens displayed on the user terminal 6 as the client PC in the present embodiment will be described with reference to FIGS. 49 to 51. 49 to 51 show schematic diagrams of screens displayed on the user terminal 6 as the client PC in the present embodiment.
[0225]
  FIG. 49 is a screen of application download software that runs on the user terminal 6.
[0226]
  Among these software, there is an application that can output a scanning instruction to the MFP and receive the scanning output on the user terminal 6 that is the user's PC.
[0227]
  FIG. 49 is also a screen for presenting to the user a list of charges when receiving results using an application function that adds value to the scanning of the MFP and its output.
[0228]
  In the present embodiment example, the first normal scan is selected. In this system, simple scanning is positioned as a result output with no added value, and is free of charge.
[0229]
  However, when processing such as OCR is performed, added value is added to the scan output, and a usage fee of 100 yen is charged. In addition, a scanning fee of 30 yen is charged for scanning output when scanning color images.
[0230]
  FIG. 50 is an execution screen for a downloaded simple scanning application. By pressing the Scan execution button, the MFP is scanned.
[0231]
  The data can be received from the menu bar, and can be stored anywhere.
[0232]
  At this timing, a log is left in the aggregation server through the application server in the MFP, and file storage, that is, scanning data reception is passed to the user.
[0233]
  FIG. 51 shows an execution screen for scanning with OCR. The user's operation is not changed except that this data reception is charged.
[0234]
  As described above, in the present embodiment, when scanning is executed in the MFP 5, the charge is charged when a predetermined application program such as color image processing is used. An effect similar to that of the first and second embodiments of the program billing system can be obtained, and the user can be satisfied with the deliverables and pay a fee.
[0235]
  In the embodiment described above, the storage means of the present invention is the application server or MFP 3 of the application provider shown in FIG. 44, and the instruction means, execution means, output means, and database are the user terminal 6 shown in FIG. The billing means is the billing management server 1.
[0236]
  In each of the above embodiments, the accounting management server, application provider (application server), and MFP connected to the network have been described as the main components, but the present invention is not limited to such an embodiment. Various modifications are possible.
[0237]
  For example, instead of using a PC or the like as a billing management server, for example, a clerk may manually calculate a billing amount from an application / program usage log and a billing table. However, this manual work includes work using a calculator such as a calculator or an abacus.
[0238]
  Further, the information transmission medium between the components is not limited to the case where a network is used. For example, mail, courier service, verbal contact, telephone instructions, and the like can be used.
[0239]
  In each of the above-described embodiments, the application server is assumed as a place where the application program is stored. However, the application program is stored in a recording medium such as an FD, a CD-ROM, or an MO. May be. In this case, each application program is recorded on the user terminal from the recording medium.
[0240]
【The invention's effect】
  As described above, according to the present invention, the application·programCreated usingUse of the application program based on the amount of printed matterSince the fee is calculated, the user can be satisfied with the fee, and the effect of smooth charging can be obtained.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram of a first embodiment of an application program billing system according to the present invention.
FIG. 2 is a system configuration diagram of a first embodiment of an application program billing system according to the present invention.
FIG. 3 is a sequence diagram when an application is executed on the user terminal 6 in the system shown in FIG.
FIG. 4 is a charging table used in the first embodiment of the application program charging system according to the present invention.
FIG. 5 is an application program use log stored in the MFP of the first embodiment of the application program billing system according to the present invention;
FIG. 6 is a flowchart of an application usage log update operation in the MFP in the first embodiment of the application program billing system according to the present invention;
7 is a table showing calculation results of printing and application usage charges derived from the table of FIG. 4 and the log of FIG.
FIG. 8 is a flowchart showing a calculation method of the table in FIG.
FIG. 9 is an overview diagram of an application server and an MFP for holding a log in the first embodiment of the application program billing system according to the present invention;
10 is a hardware block diagram of the MFP 3 shown in FIG.
11 is a software block diagram of an application program stored in the MFP 3 shown in FIG.
12 is a schematic diagram showing a touch panel screen on the operation panel of the MFP shown in FIG. 2. FIG.
13 is a schematic diagram showing a touch panel screen on the operation panel of the MFP shown in FIG.
14 is a schematic diagram showing a touch panel screen on the operation panel of the MFP shown in FIG. 2. FIG.
15 is a schematic diagram showing a touch panel screen on an operation panel of the MFP shown in FIG. 2. FIG.
16 is a schematic diagram showing a touch panel screen on the operation panel of the MFP shown in FIG.
17 is a schematic diagram showing a touch panel screen on the operation panel of the MFP shown in FIG.
FIG. 18 is a system configuration diagram of a second embodiment of an application program billing system according to the present invention.
FIG. 19 is an overview of the application server and the aggregation server shown in FIG.
20 is an internal schematic diagram of the application server shown in FIG.
21 is a software block diagram of the application server shown in FIG.
FIG. 22 is a software block diagram of the aggregation server 52 shown in FIG.
23 is a flowchart of an application usage log update operation of the aggregation server 52 shown in FIG.
FIG. 24 is a charging table used in the second embodiment of the application program charging system according to the present invention;
FIG. 25 is an operation flowchart when the application server generates output information in the second embodiment of the application program billing system according to the present invention;
FIG. 26 is a schematic diagram of an example of an application usage log 83 held in the aggregation server 52 shown in FIG.
FIG. 27 is a schematic diagram of an example of a charge amount calculation result with a user ID derived by a charge amount calculation process in the aggregation server 52 shown in FIG.
FIG. 28 is a flowchart of a billing amount calculation operation performed by the aggregation server 52 shown in FIG.
FIG. 29 is a diagram illustrating an operation for storing data in the application server, an operation for printing the stored data, and sending the data by FAX or E-mail in the second embodiment of the application program billing system according to the present invention. FIG.
FIG. 30 is a sequence diagram of operations when data is stored outside the application server, content is extracted, and charge collection processing is performed in the second embodiment of the application program billing system according to the present invention.
FIG. 31 is a flowchart of an operation when a billing amount is transmitted from the collection server 52 to the billing management server 1 in the second embodiment of the application program billing system according to the present invention.
FIG. 32 is a flowchart of a billing amount calculation operation performed in the aggregation server 52 of the present embodiment in the second embodiment of the application program billing system according to the present invention.
FIG. 33 is a schematic diagram of a screen displayed on a user terminal 6 as a client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 34 is a schematic diagram of a screen displayed on a user terminal 6 as a client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 35 is a schematic diagram of a screen displayed on a user terminal 6 as a client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 36 is a schematic diagram of a screen displayed on a user terminal 6 as a client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 37 is a schematic diagram of a screen displayed on a user terminal 6 as a client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 38 is a schematic diagram of a screen displayed on the user terminal 6 as the client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 39 is a schematic diagram of a screen displayed on the user terminal 6 as the client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 40 is a flowchart of an information transmission operation from the application server 50 or the application server 51 to the aggregation server 51 in the second embodiment of the application program billing system according to the present invention.
FIG. 41 is a schematic diagram of a screen displayed on a user terminal 6 as a client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 42 is a schematic diagram of a screen displayed on the user terminal 6 as the client PC in the second embodiment of the application program billing system according to the present invention.
FIG. 43 is a conceptual diagram of file management information when used by a plurality of applications in the second embodiment of the application program billing system according to the present invention;
FIG. 44 is a system configuration diagram of the third embodiment of the application program billing system according to the present invention.
FIG. 45 is a sequence diagram of operations of the third embodiment of the application program billing system according to the present invention.
FIG. 46 is a billing table used in the billing management server 1 of the third embodiment of the application program billing system according to the present invention.
FIG. 47 is an application program usage log used in the third embodiment of the application program billing system according to the present invention;
FIG. 48 is a billing amount breakdown table used in the billing management server 1 of the third embodiment of the application program billing system according to the present invention.
FIG. 49 is a schematic diagram of a screen displayed on the user terminal 6 as the client PC in the third embodiment of the application program billing system according to the present invention.
FIG. 50 is a schematic diagram of a screen displayed on the user terminal 6 as the client PC in the third embodiment of the application program billing system according to the present invention.
FIG. 51 is a schematic diagram of a screen displayed on the user terminal 6 as the client PC in the third embodiment of the application program billing system according to the present invention.
[Explanation of symbols]
1 Billing management server
2 Application provider
3 MFP
4 network
5 LAN
6 User terminal
7 routers
15 Scanner engine
16 Scanner controller
17 Print Engine
18 Printer controller
19 Display screen
20 Communication means
21 Input device
22 memory
23 Main controller
24 disk unit
25 logs
31 Network interface
32 Scanner driver
33 Printer Driver
34 Application file management
35 Application usage log
36 Print Engine Controller
37 applications
41 tabs
42 OCR execution button
43 Print button
44 Storage button
45 Clear button
50,51 application server
52 aggregation server
53, 54 Printer
55 Scanner
56 FAX
57,58 database
61 Network adapter
62 FAX modem
63 Video card
64 controller
65 discs
66 Monitor
67 System area
68 Application Area
69 User area
71 Network interface
72 Application File Management
73 User file management
74 applications
75 User files
81 Network interface
82 Billing table
83 Application usage log

Claims (2)

Receiving means for receiving a print processing request for data created using an application program to be charged;
Identification means for identifying the type of application program used to create the data to be requested for the printing process;
Print processing execution means for executing print processing of the requested data ;
A print log recording means for recording the amount of printed matter obtained by the printing process for each application program based on the identification result of the identification means;
In a printing system comprising: calculation means for calculating a usage fee for each application program based on the amount of printed matter recorded in the print log recording means ;
Unit price storage means for storing the unit price of the application program for each processing content for data created by the application program ,
The printing system according to claim 1, wherein the calculation means calculates the total usage fee of the application program by summing the charges for each processing content calculated based on the unit price for each processing content . The printing system according to claim 1, further comprising a notification unit configured to notify the calculated usage charge of the application program to a charging server for performing a charging process.

Images