Senior Fitness - Exercise and Nutrition for Aging Men and Women
FREE Article Feed for your website.
Home Ownership Magazine
Party Planning Information
Article Marketing Resources
Bio-Medical Research Article Database
Informative Articles on Life, Love and Happiness
Tutorials on Business to Writing
Famous Quotes from Famous People
Song Lyric Information
New US Patent Information
Comprehensive List of Content by Category
Online Auctions and Shopping Related Articles
Article Search
Most Recent Articles
Title: Mass flowmeter and method for correcting the measurement signal of a mass flowmeter
Patent Number: 6,889,561 Issued on 05/10/2005 to Hussain,   et al.

Title: Method and device for generating an air stream in a duplicating machine
Patent Number: 6,889,609 Issued on 05/10/2005 to Braun,   et al.

Title: Low operating pressure gas scrubber
Patent Number: 6,893,484 Issued on 05/17/2005 to Thomas

Title: Process for the production of grain oriented electrical steel strips
Patent Number: 6,893,510 Issued on 05/17/2005 to Fortunati,   et al.

Title: Nucleic acids encoding a cytokine receptor complex
Patent Number: 6,890,734 Issued on 05/10/2005 to Reche-Gallardo,   et al.

Title: Actuator provided with grounding terminal
Patent Number: 7,151,333 Issued on 12/19/2006 to Suzuki,   et al.

Title: Optical polarity modules and systems
Patent Number: 7,147,383 Issued on 12/12/2006 to Sullivan

Title: Light-receiving module having a light-receiving device on a die-capacitor
Patent Number: 6,949,731 Issued on 09/27/2005 to Ito

Title: Antidepressant drugs and methods
Patent Number: 6,759,435 Issued on 07/06/2004 to Chen

Title: Main cylinder with integrated transportation lock
Patent Number: 7,152,405 Issued on 12/26/2006 to Friedsam,   et al.

Title: Intrusion detection accelerator
Patent Number: 7,146,643 Issued on 12/05/2006 to Dapp,   et al.

Title: Bandaging system
Patent Number: 6,759,566 Issued on 07/06/2004 to Court,   et al.

Title: Expandable, no-shrink shirt collar
Patent Number: 7,146,647 Issued on 12/12/2006 to Krause,   et al.

Title: Automatic tone correction apparatus, automatic tone correction method, and automatic tone correction program storage mediums
Patent Number: 7,142,712 Issued on 11/28/2006 to Maruoka,   et al.

Title: Semiconductor device and manufacturing method thereof
Patent Number: 7,151,035 Issued on 12/19/2006 to Koshimizu,   et al.

Title: Integrated memory cell and method of fabrication
Patent Number: 6,943,071 Issued on 09/13/2005 to Fazio,   et al.

Title: Recording medium and a recording system for the recording medium
Patent Number: 6,952,393 Issued on 10/04/2005 to Muramatsu,   et al.

Title: Ornamentation for apparel article
Patent Number: 7,146,649 Issued on 12/12/2006 to Kronenbeger

Title: Patient classification
Patent Number: 6,763,307 Issued on 07/13/2004 to Berg,   et al.

Title: Reinforced undergarment
Patent Number: 7,143,453 Issued on 12/05/2006 to Duran

Title: Laser guides for X-ray device
Patent Number: 7,147,371 Issued on 12/12/2006 to Hecker

Title: Image reading-out apparatus, copying machine and facsimile device utilizing the same, and method of reading out image
Patent Number: 6,961,151 Issued on 11/01/2005 to Nara

Title: Mobile communication device having extendable display
Patent Number: 7,149,557 Issued on 12/12/2006 to Chadha

Title: Thermal management systems and methods
Patent Number: 7,147,071 Issued on 12/12/2006 to Gering,   et al.

Title: Method for decoding data sequence encoded with aid of binary convolution code
Patent Number: 7,143,334 Issued on 11/28/2006 to Finn,   et al.

Title: Cathode ray tube having specific radius of curvatures for inner and outer surface of the panel
Patent Number: 6,765,344 Issued on 07/20/2004 to Yoshida,   et al.

Title: Dual access cargo system for outerwear
Patent Number: 7,143,450 Issued on 12/05/2006 to Green, III

Title: Hat including active ventilation
Patent Number: 7,143,451 Issued on 12/05/2006 to Lundgren

Title: Method of manufacturing a semiconductor device with self-aligned contacts
Patent Number: 7,151,025 Issued on 12/19/2006 to Itabashi,   et al.

Title: Method and apparatus for adjusting power control setpoint in a wireless communication system
Patent Number: 6,763,244 Issued on 07/13/2004 to Chen,   et al.

Title: LNG production in cryogenic natural gas processing plants
Patent Number: 6,889,523 Issued on 05/10/2005 to Wilkinson,   et al.

Title: Semiconductor device having an integral resistance element
Patent Number: 7,151,038 Issued on 12/19/2006 to Ueda

Title: Finger ring bottle opener
Patent Number: 7,143,666 Issued on 12/05/2006 to Gutierrez

Title: Game calling device
Patent Number: 7,145,067 Issued on 12/05/2006 to Pfortmiller,   et al.

Title: Fiber optic connector and method
Patent Number: 7,147,385 Issued on 12/12/2006 to Zimmel,   et al.

Title: Pyrazolo[1,5-a]pyridine derivatives and their use as neurotransmitter modulators
Patent Number: 7,151,109 Issued on 12/19/2006 to Fu

Title: System and method of adaptively reconfiguring buffers
Patent Number: 7,143,263 Issued on 11/28/2006 to Anand,   et al.

Title: Semiconductor device and method for manufacturing the same
Patent Number: 7,151,034 Issued on 12/19/2006 to Lee,   et al.

Title: Laser assisted magnetic recording apparatus and method
Patent Number: 6,762,977 Issued on 07/13/2004 to Gage,   et al.

Title: Method of mixing by intermittent centrifugal force
Patent Number: 7,147,362 Issued on 12/12/2006 to Caren,   et al.

Title: Disposal of cement waste from chute
Patent Number: 7,147,360 Issued on 12/12/2006 to Elefsrud

Title: Semiconductor memory device having a circuit for fast operation
Patent Number: 6,762,967 Issued on 07/13/2004 to Tanizaki,   et al.

Title: Child-resistant piezoelectric lighter
Patent Number: 6,765,338 Issued on 07/20/2004 to Orazietti

Title: Method of manufacturing semiconductor device
Patent Number: 7,151,017 Issued on 12/19/2006 to Ohnuma

Title: Semiconductor wafer test system
Patent Number: 7,151,003 Issued on 12/19/2006 to Oishi

Title: Patient support pad with repositionable pressure source
Patent Number: 7,146,660 Issued on 12/12/2006 to Heimbrock

Title: Method to prevent damage to probe card
Patent Number: 7,143,500 Issued on 12/05/2006 to Byrd

Title: Digital broadcast receiving device
Patent Number: 7,146,633 Issued on 12/05/2006 to Yamaguchi,   et al.

Title: Transfer of hot feed materials from a preprocessing plant to an electric smelting or melting furnace
Patent Number: 6,953,337 Issued on 10/11/2005 to McCaffrey

Title: Multi-site cardiac stimulation device and method for detecting retrograde conduction
Patent Number: 7,146,215 Issued on 12/05/2006 to Mo

Title: Funnel in cathode ray tube
Patent Number: 6,765,343 Issued on 07/20/2004 to Kim

Title: Booster circuit for non-volatile semiconductor memory device
Patent Number: 6,762,960 Issued on 07/13/2004 to Natori

Title: Linear guide
Patent Number: 7,147,375 Issued on 12/12/2006 to Zernickel,   et al.

Title: Open hydraulic circuit including a relief valve device
Patent Number: 7,150,150 Issued on 12/19/2006 to Bigo,   et al.

Title: System for and method of toner flow control
Patent Number: 6,760,555 Issued on 07/06/2004 to Dougherty,   et al.

Title: Cardiovascular anchoring device and method of deploying same
Patent Number: 7,149,587 Issued on 12/12/2006 to Wardle,   et al.

Title: Semiconductor filter circuit and method
Patent Number: 6,953,980 Issued on 10/11/2005 to Escoffier,   et al.

Title: Humidifier with parallel gas flow paths
Patent Number: 7,146,979 Issued on 12/12/2006 to Seakins,   et al.

Title: Gas turbine engine
Patent Number: 7,153,091 Issued on 12/26/2006 to Stephenson,   et al.

Title: Glutamate receptor antagonists
Patent Number: 7,151,098 Issued on 12/19/2006 to Adam,   et al.

Title: Method for manufacturing a surface acoustic wave device with a piezoelectric substrate
Patent Number: 7,146,695 Issued on 12/12/2006 to Nakagawara,   et al.

Title: Modular air conditioner for a bus
Patent Number: 6,761,038 Issued on 07/13/2004 to Bushnell,   et al.

Title: Alarm activated acoustic measuring signals for patient monitoring
Patent Number: 7,149,570 Issued on 12/12/2006 to Ellscheid,   et al.

Title: Method for fabricating electrical connection structure of circuit board
Patent Number: 7,151,050 Issued on 12/19/2006 to Hsu,   et al.

Title: Water heater having self-powered low NOx burner/fuel-air delivery system
Patent Number: 6,761,134 Issued on 07/13/2004 to Trant

Title: Satellite broadcast receiving converter with lower power consumption
Patent Number: 7,136,618 Issued on 11/14/2006 to Kato,   et al.

Title: Apparatus and method for managing power of a battery
Patent Number: 6,765,369 Issued on 07/20/2004 to Rhee,   et al.

Title: Paint bucket
Patent Number: 6,945,440 Issued on 09/20/2005 to Ford

Title: Data communications synchronization using GPS receiver
Patent Number: 6,763,241 Issued on 07/13/2004 to Gous,   et al.

Title: Truncated aggrecanase molecules
Patent Number: 7,150,983 Issued on 12/19/2006 to Georgiadis,   et al.

Title: Pneumatic surgical prone head support and system
Patent Number: 7,146,664 Issued on 12/12/2006 to Grosvenor

Title: Magnetic pipette
Patent Number: 6,763,734 Issued on 07/20/2004 to Shukla,   et al.

Title: Methods and apparatus for efficient and accurate coarse timing synchronization in burst demodulators
Patent Number: 7,154,967 Issued on 12/26/2006 to Boutros,   et al.

Title: Use of downhole high pressure gas in a gas-lift well and associated methods
Patent Number: 7,147,059 Issued on 12/12/2006 to Hirsch,   et al.

Title: Semiconductor device with flexible redundancy system
Patent Number: 6,762,964 Issued on 07/13/2004 to Takase

Application charging system, information processing apparatus, and control method therefor and memory medium storing program therefor Number:7,154,616 from the United States Patent and Trademark Office (PTO) owispatent

Home    Author Login    Submit Article    Article Search    Add Your Link    Edit Your Link    Contact Us    Advertising    Disclaimer

   

 
Web LinkGrinder.com

Top Breaking News
     Greek, Cypriot Leaders Resume Unification Talks in Nicosia by Nathan Morley
     Indonesia Tobacco Sales Grow, Raising Health Fears
     South Korea Allows Top Defector to Travel Overseas by VOA News

Title: Application charging system, information processing apparatus, and control method therefor and memory medium storing program therefor

Abstract: In case a file is prepared by executing an application, the fee for the use of the application is charged according to whether such file is subjected to an output process. Thus the user of the application need not pay the fee for the use of the application for the mere preparation of the file by using the application.

Patent Number: 7,154,616 Issued on 12/26/2006 to Watanabe,   et al.


Inventors: Watanabe; Yoshihiko (Yokohama, JP), Kojima; Jiro (Kawasaki, JP), Yoshida; Masayuki (Yokohama, JP), Kurumida; Tsuneaki (Kawasaki, JP), Negishi; Tsutomu (Tokyo, JP), Yamasawa; Yuichiro (Kawasaki, JP), Kimura; Yoshio (Kawasaki, JP), Kanamoto; Yoshiji (Tokyo, JP)
Assignee: Canon Kabushiki Kaisha (Tokyo, JP)
Appl. No.: 09/840,157
Filed: April 24, 2001


Foreign Application Priority Data

Apr 27, 2000 [JP] 2000-127885
Oct 03, 2000 [JP] 2000-304066
Oct 06, 2000 [JP] 2000-308110
Oct 11, 2000 [JP] 2000-311020
Oct 13, 2000 [JP] 2000-314318
Oct 18, 2000 [JP] 2000-318364
Oct 23, 2000 [JP] 2000-322992
Oct 27, 2000 [JP] 2000-328833

Current U.S. Class: 358/1.13 ; 358/1.15; 705/52; 705/54; 705/59
Current International Class: G06Q 99/00 (20060101)
Field of Search: 705/39,26,14,52,54,59 395/186,701 358/1.15,1.13


References Cited [Referenced By]

U.S. Patent Documents
5771289 June 1998 Kuzma
5771354 June 1998 Crawford
5819092 October 1998 Ferguson et al.
5943650 August 1999 Kanno
6401243 June 2002 Suzuki
6615183 September 2003 Kolls
Primary Examiner: Poon; King Y.
Attorney, Agent or Firm: Fitzpatrick, Cella, Harper & Scinto

Claims



What is claimed is:

1. A print apparatus for holding an application program provided from an application service provider apparatus, comprising: downloading means for downloading the application program to a user terminal apparatus; receiving means for receiving, from said user terminal apparatus, a file produced when said user terminal apparatus executes the application program, and a print request of the produced file; discriminating means for discriminating a type of the application program used to produce the file; print processing means for executing print processing of the received file; recording means for recording, in a log, a print amount caused by the print processing, in correspondence with the type of the application program; calculating means for calculating a charge on the basis of a cost for use of the log and a cost for use of the application program; and notifying means for notifying an accounting management server of the calculated charge, wherein said accounting management server effects processing for sending money to said application service provider apparatus, on the basis of the calculated charge.

2. An apparatus according to claim 1, wherein said receiving means receives a user ID for uniquely identifying said user terminal apparatus, wherein said recording means records the print amount in correspondence with the user ID, and wherein said calculating means calculates the charge for every user ID.

3. An apparatus according to claim 1, further comprising erasing means for erasing the log when said accounting management server completes the accounting processing.

4. An apparatus according to claim 1, wherein said downloading means downloads a plurality of application programs to said user terminal apparatus, wherein said receiving means receives a file produced when said user terminal apparatus executes the plurality of application programs, and wherein said calculating means calculates the charge on the basis of the cost for use of the log and the cost for use of each of combinations of the plurality of application programs.

5. A control method for a print apparatus for holding an application program provided from an application service provider apparatus, comprising: a downloading step of downloading the application program to a user terminal apparatus; a receiving step of receiving, from said user terminal apparatus, a file produced when said user terminal apparatus executes the application program, and a print request of the produced file; a discriminating step of discriminating a type of the application program used to produce the file; a print processing step of executing print processing of the received file; a recording step of recording, in a log, a print amount caused by the print processing, in correspondence with the type of the application program; a calculating step of calculating a charge on the basis of a cost for use of the log and a cost for use of the application program; and a notifying step of notifying art accounting management server of the calculated charge, wherein said accounting management server effects processing for sending money to said application service provider apparatus, on the basis of the calculated charge.

6. A computer-readable storage medium on which is stored a computer-executable program for causing a computer to execute a control method for a print apparatus for holding an application program provided from a application service provider apparatus, said control method comprising: a downloading step of downloading the application program to a user terminal apparatus; a receiving step of receiving, from said user terminal apparatus, a file produced when said user terminal apparatus executes the application program, and a print request of the produced file; a discriminating step of discriminating a type of the application program used to produce the file; a print processing step of executing print processing of the received file; a recording step of recording, in a log, a print amount caused by the print processing, in correspondence with the type of the application program; a calculating step of calculating a charge on the basis of a cost for use of the log and a cost for use of the application program; and a notifying step of notifying an accounting management server of the calculated charge, wherein said accounting management server effects processing for sending money to said application service provider apparatus, on the basis of the calculated charge.
Description



BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an application charging system adapted for use in a system for providing the user with an application and charging a fee for the use of the application to the user, an information processing apparatus therefor, a control method therefor and a memory medium storing a program therefor.

2. Related Background Art

There have conventionally been developed various technologies for enabling, in the system of the above-described type, the application service provider (hereinafter represented as ASP), who provides the application, to charge the fee for using the application to the user.

For example the U.S. Pat. No. 5,943,650 discloses a system capable of assigning a weight to each of the functions contained in the application, calculating a fee for using the application based on a count of the weights of the used functions, and charging such fee to the user. Thus the fee for using the application is calculated in the unit of each function in the application and increases as such functions are used more.

There is also known a system capable of calculating a fee only for a function actually used by the user among plural functions contained in the application and charging such fee to the user.

There is further known a system in which a user terminal informs an ASP terminal of the time of use at the execution of the application and the ASP terminal calculates a fee for using the application based on the time of use informed from the user terminal and charges such fee to the user.

There is further known a system in which the user acquires a ticket bearing a time permitting the use to use the application, and which thereby enables the use of the application for the time recorded on the ticket. Thus, such system calculates the fee for using the application according to the time of use of the application and charges such fee to the user.

There is further known a system capable of calculating a fee for the use of the application according to the number of uses thereof and charging such fee to the user.

Thus, in the conventional technologies described in the foregoing, the fee for using the application, to be charged to the user, is calculated (1) in the unit of the function used in the application, (2) according to the time of use of the application, or (3) according to the number of uses of the application.

In the case (1), for example if plural functions of the application are used for preparing a single file, the fee becomes higher because the fee has to be paid for such plural functions. Also the fee becomes higher than in a case of preparing two files utilizing a single function.

In the case (2), the user cannot be satisfied with the charged fee because the user cannot judge whether the time actually required by the user in the preparation of a file is correctly measured as the time of use. Also in case the user is not accustomed to the use of the application, there may be encountered a situation where the time of use becomes exceptionally long or the desired file cannot be prepared even after a long time of use, so that the user is dissatisfied with the charging system.

In the case (3), the fee becomes exceptionally high in case the desired file cannot be prepared after a single use of the application but can only be prepared after the use of the application plural times.

SUMMARY OF THE INVENTION

The present invention is to realize charging for the use of an application with a fee satisfactory to the user, and is featured by calculating a fee for the use of the application based on the output result (result product) of a file prepared utilizing the application and charging such fee to the user.

Other objects and features of the present invention will become fully apparent from the following detailed description to be taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 are views showing the configuration of an application charging system of the present invention;

FIG. 3 is a view showing the operation sequence of the application charging system of the present invention;

FIG. 4 is a view showing a charge table to be used in the application charging system of the present invention;

FIG. 5 is a view showing an application use log to be used in the application charging system of the present invention;

FIG. 6 is a flow chart showing a renewing operation for the application use log to be used in the the application charging system of the present invention;

FIG. 7 is a table representing the application use fee calculated from the charge table shown in FIG. 4 and the application use log shown in FIG. 5;

FIG. 8 is a flow chart showing the calculating method for the table shown in FIG. 7;

FIG. 9 is a schematic view of an MFP in the application charging system of the present invention;

FIG. 10 is a hardware block diagram of the MFP to be used in the application charging system of the present invention;

FIG. 11 is a software block diagram of the MFP to be used in the application charging system of the present invention;

FIGS. 12, 13, 14, 15, 16 and 17 are schematic views showing a touch panel image displayed on an operation panel of the MFP to be used in the application charging system of the present invention;

FIG. 18 is a view showing the system configuration of an application charging system of the present invention;

FIG. 19 is a schematic view of an application server and an add-up server to be used in the application charging system of the present invention;

FIG. 20 is a schematic view showing the internal configuration of the application server to be used in the application charging system of the present invention;

FIG. 21 is a software block diagram of the application server to be used in the application charging system of the present invention;

FIG. 22 is a software block diagram of the add-up server to ve used in the application charging system of the present invention;

FIG. 23 is a flow chart of a renewing operation for the application use log to be used in the application charging system of the present invention;

FIGS. 24A and 24B are views showing a charge table to be used in the application charging system of the present invention;

FIG. 25 is a flow chart showing a procedure for generating output processing information in the application charging system of the present invention;

FIG. 26 is a schematic view of the application use log to be used in the application charging system of the present invention;

FIG. 27 is a view showing a table indicating the result of calculation of the fee for using the application, derived in the application charging system of the present invention;

FIGS. 28A and 28B are flow charts showing a procedure for calculating the application use fee in the application charging system of the present invention;

FIGS. 29 and 30 are views showing the operation sequence of the application charging system of the present invention;

FIGS. 31A and 31B are flow charts showing a fee charging operation in the application charging system of the present invention;

FIG. 32 is a flow chart showing a procedure for calculating the application use fee in the application charging system of the present invention;

FIGS. 33, 34, 35, 36, 37, 38 and 39 are schematic views showing a UI image displayed on a user terminal to be used in the application charging system of the present invention;

FIG. 40 is a flow chart showing an operation of transmitting output process information from the application server to the add-up server in the application charging system of the present invention;

FIGS. 41 and 42 are schematic view showing a UI image displayed on a user terminal to be used in the application charging system of the present invention;

FIG. 43 is a view showing the concept of file management information in a file prepared in the application charging system of the present invention;

FIG. 44 is a view showing the system configuration of an application charging system of the present invention;

FIG. 45 is a view showing the operation sequence of the application charging system of the present invention;

FIG. 46 is a view showing a charge table to be used in the application charging system of the present invention;

FIG. 47 is a view showing an application use log to be used in the application charging system of the present invention;

FIG. 48 is a view showing a charge breakdown table to be used in the application charging system of the present invention;

FIGS. 49, 50 and 51 are schematic views showing a UI image displayed on a user terminal to be used in the application charging system of the present invention;

FIG. 52 is a view showing a charge table to be used in the application charging system of the present invention;

FIGS. 53, 54, 55 and 56 are schematic views showing a touch panel image displayed on an operation panel of an MFP to be used in the application charging system of the present invention;

FIG. 57 is a view showing a charge breakdown table to be used in the application charging system of the present invention;

FIGS. 58A and 58B are views showing a charge table to be used in the application charging system of the present invention;

FIG. 59 is a view showing an application use log to be used in the application charging system of the present invention;

FIG. 60 is a view showing a charge table to be used in the application charging system of the present invention;

FIG. 61 is a view showing an application use log to be used in the application charging system of the present invention;

FIG. 62 is a table showing the application use fees calculated by the application charging system of the present invention;

FIG. 63 is a view showing the system configuration of an application charging system of the present invention;

FIG. 64 is a schematic view showing a touch panel image displayed on an operation panel of an MFP to be used in the application charging system of the present invention;

FIG. 65 is a flow chart showing an operation for calculating the application use fee in the application charging system of the present invention;

FIGS. 66A and 66B are views showing discount rates of the application use fee by date and time in the application charging system of the present invention;

FIG. 67 is a view showing a fee selecting image displayed to the user in the application charging system of the present invention;

FIG. 68 is a view showing a charge table to be used in the application charging system of the present invention;

FIG. 69 is a view showing an application use log in the application charging system of the present invention;

FIG. 70 is a flow chart showing an operation for renewing the application use log to be used in the application charging system of the present invention;

FIG. 71 is a view showing a charge table to be used in the application charging system of the present invention;

FIGS. 72 and 73 are views showing a table to be used in the application charging system of the present invention;

FIG. 74 is a view showing a fee breakdown table to be used in the application charging system of the present invention;

FIG. 75 is a flow chart showing an operation for calculating the application use fee in the application charging system of the present invention;

FIG. 76 is a view showing the system configuration of an application charging system of the present invention;

FIGS. 77 and 78 are views showing the operation sequence of the application charging system of the present invention;

FIGS. 79 and 80 are views showing a UI image displayed on a user terminal to be used in the application charging system of the present invention;

FIG. 81 is a view showing a charge table to be used in the application charging system of the present invention;

FIG. 82 is a view showing an application use log to be used in the application charging system of the present invention;

FIG. 83 is a flow chart showing an operation for renewing the application use log to be used in the application charging system of the present invention;

FIGS. 84, 85 and 86 are schematic views showing a touch panel image displayed on an operation panel of an MFP to be used in the application charging system of the present invention;

FIG. 87 is a view showing a charge table to be used in the application charging system of the present invention;

FIG. 88 is a view showing an application use log to be used in the application charging system of the present invention;

FIG. 89 is a flow chart showing an operation for renewing the application use log to be used in the application charging system of the present invention; and

FIG. 90 is a view showing a charge table to be used in the application charging system of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Now the present invention will be clarified in detail by preferred embodiments thereof, with reference to the accompanying drawings. However, the dimension, material, shape etc. of the components and the relative position thereof, described in such embodiments are not to limit the range of the present invention, unless stated otherwise.

In the accompanying drawings, components similar to those appearing in the preceding drawings are represented by same numbers. In the following there will be explained embodiments of the application charging system of the present invention.

[First Embodiment] [Application Server and Add-up Serving Being Realized by a Same Device]

At first there will be explained a first embodiment of the application charging system of the present invention, with reference to the accompanying drawings.

A first configuration of the system of the present embodiment will be explained with reference to FIG. 1.

There are shown a charge management server 1 of a distribution company for managing the charge information relating to the use fee of the application, an application service provider (ASP) 2 providing the applicationl, and a multi function peripheral (MFP) 3 having functions of plural output devices such as a copying apparatus, a facsimile apparatus and a printer, for outputting a file prepared with the application. The MFP 3 also manages the application provided by the ASP 2. There is also shown a network 4 connecting the charge management server 1, the ASP 2 and the MFP 3. In FIG. 1, the network 4 is composed of the internet, but it may also be composed of a network utilizing a protocol other than TCP/IP. Also the network may be a wireless one or a wired one.

In the configuration shown in FIG. 1, the MFP 3 is connected with the network 4 but is used in a standalone environment not locally connected with a personal computer or a server utilizing the MFP 3.

In the following there will be explained a second configuration of the system of the present embodiment, with reference to FIG. 2.

Referring to FIG. 2, there are shown a local area network (LAN) 5, a user terminal 6 for preparing a file utilizing the application provided from the ASP 2, and a router 7.

In the configuration shown in FIG. 2, the MFP 3 is connected together with the user terminal 6 to the LAN 5, which is connected by the router 7 to the network 4. Thus, in the second configuration, different from the stand-alone environment in first configuration, the MFP 3 is locally connected to the user terminal 6 and is used within the LAN 5 or the intranet.

The system of the present embodiment may assume the configuration shown in FIG. 1 or that shown in FIG. 2.

Also the MFP need not be connected to the network 4. However, in case not connected with the network 4, the MFP 3 has to inform the distribution company of the charge information for example through a telephone line through a modem or the like.

In the following there will be explained, with reference to a sequence chart shown in FIG. 3, the function of the system of the present embodiment. FIG. 3 shows a case, in the second configuration shown in FIG. 2, of executing the application on the user terminal 6 to prepare a file and obtaining, as a product, a print of the file.

At first the user terminal 6 requests the downloading of the application to the MFP 3 (S1). In this operation, the user terminal 6 informs the MFP 3 of a user ID for identifying the user utilizing the application.

In response to the request from the user terminal 6 in the step S1, the MFP 3 executes an authentication process based on the user ID and an application transfer process to the user terminal 6 (S2).

Upon receiving the application transferred from the MFP 3 in the step S2 and completing the downloading of the application, the user terminal 6 executes the application thereby preparing a file (S3). In this operation, after the downloading of the application by the user terminal 6, the application may be executed after the MFP 3 issues an execution instructing command to such application.

Then the user terminal 6 requests (S4), to the MFP 3, a printing process for a file prepared by executing the application in the step S3. At this point, the user terminal 6 informs the MFP 3 of the user ID.

Upon receiving the request for the printing process from the user terminal 6 in the step S4, the MFP 3 identifies the type of the application used for preparing the file and the user ID of the user who requests the printing process (S5). Then it executes the printing process of the file (S6) and renews the application use log to be explained later (S7).

At a predetermined time, the charge management server 1 transmits a request for the transmission of charge information, to the MFP 3 (S9).

Upon receiving the request for transmitting the charge information from the charge management server 1 in the step S9, the MFP 3 calculates the application use fee for each user ID, based on the application use log renewed in the step S7, and transmits the information on thus calculated application use fee, as the charge information, to the charge management server 1 (S8).

Based on the charge information transmitted from the MFP 3 in the step S8 and on the user ID, the charge management server 1 transmits, to the user terminal 6, a request for payment of the application use fee (S10). In the step S8, the application use fee may be calculated not for each user (user ID) but for an organization to which plural users belong, and the request for payment in the step S9 may be made to such organization.

When the application use fee is sent from the user terminal 6, the charge management server 1 sends, to the application provider 2, a sum after the deduction of a printing process fee for the file from the sent application use fee (S11).

FIG. 4 shows a charge table showing, for each application, the fee required for the output process of the file prepared utilizing the application. FIG. 4 only shows the fees for the printing process as the output process, but the table also contains the fees for other output processes such as e-mail transmission or facsimile transmission. The MFP 3 calculates the application use fee in the step S8 shown in FIG. 3, based on such charge table. The fee for each application includes also the fee of the output process for the file.

According to FIG. 4, the fee for "normal print" is 8 Yen per sheet, while the fee of the printing process for the file prepared utilizing the "application A" is 15 Yen per sheet. Therefore, the fee for using the application A is "7 Yen" per sheet in case of printing the file prepared utilizing the application A.

FIG. 5 shows an application use log held by the MFP 3. Upon executing the printing process of the file in the step S6 shown in FIG. 3, the MFP 3 renews the application use log in the step S7. The application use log records the user ID of the user requesting the printing process of the file, the type of the application used for preparing the file, the number of printed sheets etc., and stores the information of a predetermined period (for example 1 month). The information having completed the charging process in the steps S9, S10 and S11 in FIG. 3 is erared from the application use log.

An example shown in FIG. 5 indicates that the "normal print" has 3501 print sheets and the file prepared utilizing the "application A" has 335 print sheets.

Now reference is made to a flow chart shown in FIG. 6, for explaining an operation of the MFP 3 for renewing the application use log shown in FIG. 5 in the step S7 in FIG. 3.

At first, in a step S201, the MFP 3 discriminates whether a recording sheet bearing an image has been discharged. If not discharged (No), it enters a state for awaiting the sheet discharge, but, if discharged (Yes), the sequence proceeds to a step S202.

In a step S202, the MFP 3 discriminates whether the discharged sheet is an output from the application.

If the step S202 identifies that the sheet discharge is not an output from the application (No), the MFP 3 in a step S204 renews the "print number" of the "normal print" in the application use log (FIG. 5), whereupon the sequence is terminated.

On the other hand, if the step S202 identifies that the sheet discharge is an output from the application (Yes), the MFP 3 in a step S203 acquires, from the application, an application number N for identifying the type of the application. Then, in a step S205, the MFP 3 renews, in the application use log (FIG. 5), the "print number" of an "application type" corresponding to the application number N acquired in the step 203, whereupon the sequence is terminated.

FIG. 7 is a table showing the application use fee calculated by the MFP 3 in the step S8 in FIG. 3, based on the charge table (FIG. 4) and the application use log (FIG. 5). The application use fee is calculated, based on the "application type", by multiplying the charge amount per sheet in the charge table (FIG. 4) with the number of prints in the application use log (FIG. 5) for each field. Referring to FIG. 7, the "distribution company's share" is a charge for the normal printing process to be paid to the distribution company in charge of the sales, management and maintenance of the MFP 3, while the "provider's share" is a charge to be paid to the ASP 2 after the deduction of the distribution company's share from the application use fee.

In FIG. 7, the "normal print", not utilizing the application, does not include the application use fee to be paid to the ASP 2. Therefore, the total sum 28008 Yen is divided into the distribution company's share of 28008 Yen and the provider's share of 0 Yen. For the "application A", the total sum 5025 Yen is divided into the distribution company's share of 2680 Yen and the provider's share of 2345 Yen.

In the following there will be explained, with reference to a flow chart shown in FIG. 8, an operation of the MFP 8 for calculating the table (FIG. 7) of the application use fee.

At first, in a step S71, the MFP 3 calculates the application use fee, based on the "application type", by multiplying the charge per sheet in the charge table (FIG. 4) with the number of prints in the application use log (FIG. 5) for each field.

In a step S72, the MFP 3 discriminates whether the print process is for a file prepared not using the application (normal print).

If the step S72 identifies a normal print (Yes), the sequence proceeds to a step S75.

If the step S72 identifies that the print process is not a normal print (No), the MFP 3 in a step S73 subtracts the normal print fee from the application use fee calculated in the step S71.

Then, the MFP 3 in a step S74 adds the result of subtraction in the step S73 to the application provider's share, and, in a step S75, adds the normal print fee to the distribution company's share.

Then a step S76 discriminates whether the calculation of the application use fee has been completed for all the applications. If not completed (No), the sequence proceeds to the step S71, but, if completed (Yes), the sequence is terminated.

FIG. 9 is a schematic view showing the MFP 3. In the present embodiment, the MFP 3 functions as an application server for managing the application provided from the ASP 2, and also as an add-up server for holding the charge table (FIG. 4) and the application use log (FIG. 5) and calculating the application use fee based thereon.

The MFP 3 is a composite apparatus having the plural output functions such as a printer, a facsimile apparatus, a copying apparatus etc., and is provided therein with hardware configuration including a central processing unit (CPU) and a hard disk required for the functions of the application server and the add-up server.

FIG. 10 is a hardware block diagram showing the internal configuration of the MFP 3.

A scanner engine 15 drives a scanner in cooperation with a scanner controller 16, and a print engine 17 drives a printer in cooperation with a print controller 18.

A display 19 displays instructions and warnings to the user, an operation panel for operating the MFP 3, and the operation status thereof.

Communication means 20 is provided for data exchange between the MFP 3 and other devices, and executes communication by a predetermined protocol such as ICP/IP.

An input device 21, for entering data, can be composed for example of a touch panel, a pointing device, a mouse, a reset button, a start key and numeral keys.

A memory 22 is provided for storing image data, content of the input, a processing program of the MFP 3 etc.

A main controller 23, for controlling the entire MFP 3, is provided with a CPU and controls the functions of the various components.

A disk device 24 functions as a memory medium, storing for example various applications provided from the ASP 2.

A log 25 stores the status of use of the application within a predetermined period as the application use log (FIG. 5), and is used for determining the charge amount to the user.

A system bus 26 connects the various functions of the system.

FIG. 11 is a software block diagram showing the internal configuration of the MFP 3. The software of the MFP 3 incorporates, for example, the function of an ordinary composite apparatus, that of the application server, and that of the add-up server for managing the application use log. These functions are incorporated in a state capable of communication with the exterior through the network.

The software configuration of the MFP 3 in the system of the present embodiment is composed, as shown in FIG. 11, by connecting a scanner driver 32, a printer driver 33 and an application file management 34 to a network interface 31.

The scanner driver 32 is an application for driving the scanner, and the printer driver 33 is an application for driving the printer in cooperation with a print engine controller 36.

The application file management 34 executes control of various applications 37 provided from the ASP 2, and management of an application use log 35. The application use log 35 is a file recording the use status of the application, and the renewal of and reference to such log are managed by the application file management 34, which manages the renewal of and reference to plural applications.

In the following there will be explained the operation of the MFP 3 of the system of the present embodiment, with reference to FIGS. 12 to 17 schematically showing a touch panel image displayed on the operation panel of the MFP 3.

As shown in FIG. 12, tabs 41 representing output process functions of the MFP 3 are displayed in an upper part of the touch panel image, and the user can select the output process function by touching a tab 41 of a desired output process function with a finger. As an example, FIG. 12 shows the touch panel image in a state where a "file" function is selected.

Also FIG. 12 shows, to the user, a list of the fee for each type of the application managed by the application file management 34 of the MFP 3 and each output product of a file prepared using the application, where by the user can select an application to be used from the list of the fees of the applications.

The list of the fees shown in FIG. 12 also shows the fees in case the product file prepared using various applications is printed as a print, e-mail transmitted as an attachment to an e-mail and facsimile transmitted as image data by the facsimile function. The fee list shown in FIG. 12 is based on the charge table shown in FIG. 4.

On the touch panel image, the user selects an application to be used by touching a virtually displayed button with a finger.

In the following there will be explained a case where the user selects an application C on the image shown in FIG. 12, wherein the application C executes an OCR function.

In response to the selection of the application C on FIG. 12, the application C is activated whereby the touch panel image is shifted to a state shown in FIG. 13. The touch panel image is shifted to a configuration corresponding to the selected application, and FIG. 13 shows an image configuration optimum for executing the OCR function of the application C selected by the user.

Then the user designates an image file to be subjected to the OCR process. More specifically, the user selects and designates an image file in a pull-down file list displayed by touching a file listg button. In response to the selection of an image file in FIG. 13, the name of the designated file is displayed in a file name field and the content of such file is displayed in an input image display field, as shown in FIG. 14.

When the user touches an "OCR execution" button 42 in the touch panel image shown in FIG. 14, the OCR process is executed on the designated image file and the result of such execution is displayed in an OCR result field, as shown in FIG. 15.

In the present embodiment, the execution of the OCR process alone on the designated image file does not require an application use fee, so that no fee is charged to the user. Therefore the user can freely repeat the designation of the image file or the OCR process on the image file until a satisfactory OCR result can be obtained, without paying attention to the application use fee.

In the following there will be explained a case where the user is satisfied with the result of the OCR process of the image file, displayed on the OCR result field shown in FIG. 15 and executes an output process on the file obtained as the OCR result. In particular there will be explained a case where the user wishes a "print" process as the output process for the file.

When the user touches a "print" button 43 in FIG. 15, the touch panel image is shifted to a state shown in FIG. 16.

FIG. 16 shows an image for designating printing for the file obtained as the result of the OCR process. In FIG. 16 there are displayed "application C" as the name of the used application and "image file 2" as the name of the image file subjected to such application. There are also displayed a unit fee and a total fee in case the file obtained as the result of the OCR process is printed. If satisfied with these displays, the user touches a "print" button. If the printing is canceled, the user touches a "cancel" button whereupon the print process is interrupted and the display returns to the state shown in FIG. 15. On the other hand, if the user touches a "store" button 44 in FIG. 15, the touch panel image is shifted to a state shown in FIG. 17.

FIG. 17 shows an image for storing the file obtained as the result of the OCR process in memory means such as the memory 22 or the disk device 24 in the MFP 3. In FIG. 17, there are displayed the name of the used application and the name of the image file processed by the application.

In the present embodiment, the file storage alone does not require an application use fee, and there is displayed a message indicating that the file storage is charge free. For storing the file, the user touches a "store" button. It is also possible, when the "store" button is touched, to display an array of various character keys such as a keyboard thereby enabling the user to enter a file name and to store the file with an altered name. In case the file storage is to be canceled, the user touches a "cancel" button whereupon the touch panel image returns to a state shown in FIG. 15.

On the other hand, if the user touches a "clear" button 45 in the touch panel image shown in FIG. 15, the displays in the file name field, input image field and OCR result field are erased whereby the touch panel image returns to the state shown in FIG. 13. Also if the user touches a "cancel" button in the touch panel image shown in FIG. 15, the touch panel image returns to the state shown in FIG. 12.

In the touch panel images shown in FIGS. 13 to 15, to the right of the "OCR execution" button 42, "print" button 43 or "store" button 44, the application use fee for such process are displayed in the unit fee and the total fee.

In the present embodiment, the application use fee is charged only on the "printing", "e-mail transmission" and "facsimile transmittion" but not on the "OCR" process or the storage of the file obtained as the product of the process, so that the latter ones are displayed as charge free.

Also the fee for the "printing", "e-mail transmission" or "fax transmission" is displayed in a gray pattern in the touch panel image shown in FIG. 13 as such fee is not yet fixed in the strage of FIG. 13, and is displayed in a fixed manner when the fee for the various process is fixed after the OCR process on the touch panel image shown in FIG. 15.

In the present embodiment, as explained in the foregoing, the user prepares a file using the application, and then executes an output process of the file and the fee is charged when the user obtains the product of such output process. Stated differently, no fee is charged for the preparation only of the file utilizing the application.

Consequently, according to the present embodiment, the charge payable by the user corresponds to the product of the use of the application by the user and is reasonable for the use of the application.

Also in the present embodiment, the output process device for outputting the file has the function of an add-up server and the information on the application use fee is transmitted from the output devices to the charge management server through the network. Therefore the charge management server can execute the charging process on the application use fee regardless of the actual locations of the output devices or regardless of the time zone in which the user utilizes the output devices, whereby the charging process can be made more efficient.

Also the system of the present embodiment can be applied to the application of a wide range, thereby expanding the business range of the ASP.

[Second Embodiment] [Application Server and Add-up Server Being Realized by Different Devices]

In the following there will be explained, with reference to the accompanying drawings, a second embodiment of the application charging system of the present invention. In the present embodiment, different from the foregoing first embodiment, the functions of the application server, the add-up server and the output processes are provided separately.

FIG. 18 shows the system configuration of the present embodiment, wherein provided are application servers 50, 51 which hold applications provided from the ASP 2 and whihc are respectively connected to data bases 57, 58 for storing the user files which user prepares using the application.

An add-up server 52 manages the use status of the applications held in the application servers 50, 51. Printers 53, 54, a scanner 55 and a facsimile device 56 execute output process for the user file prepared using the application. A user terminal 6, the application servers 50, 51, the add-up server 52, the printers 53, 54, the scanner 55 and the FAX 56 are connected to a LAN 5 and are used therein or in an intranet environment. The LAN 5 is connected by a router 7 to a network 4. A charge management server 1 of the distribution company, at least an application provider 2 and the router 7 are connected to the network 4.

FIG. 19 is a schematic view of the application servers 50, 51 and the add-up server 52 used in the present system. In the present embodiment, the application servers 50, 51 and the add-up server 52 are assumed to be realized by separate devices, but they may also be incorporated within a same device.

In the following there will be explained the internal configuration of the application server 50, with reference to a schematic view shown in FIG. 20. The application server 51 has a similar internal configuration. The application server 50 is provided therein with a network adapter 61 constituting a connection interface with the LAN 5, a FAX modem 62 for data transmission on a telephone line, a video card 63 for image display on a monitor 66, a disk 65 constituting data memory means, and a controller 64 for controlling these components. The disk 65 is a memory device such as a hard disk, and includes a system area 67, an application area 68 for holding the application provided from the ASP 2, and a user area 69 for holding the user file which the user prepares using the application. These areas only need to be logically separated and may be composed of different disks 65 or may be separated by directories within a same disk 65.

In the following there will be explained the internal software configuration of the application server 50 with reference to a software block diagram shown in FIG. 21. Also the application server 51 has a similar software configuration.

An application file management 72 and a user file management 73 are connected to a network interface 71, through which an external access is made possible. The application file management 72 is connected to the various applications 74 provided from the ASP 2. Also the user file management 73 is connected to a user file 75 which the user prepares using the application file.

In the following there will be explained the internal configuration of the add-up server 52 with reference to a software block diagram shown in FIG. 22.

A charge table 82 stores tables as shown in FIGS. 24A and 24B and as will be explained later, and an application use log 83 accumulates logs recording the uses of the applications held in the application servers 50, 51.

The charge table 82 and the application use log 83 are connected through a network interface 81, and the application use fee is calculated on the information stored in the charge table 82 and the application use log 83.

In the following there will be explained, with reference to a flow chart shown in FIG. 23, an operation of the add-up server 52 for renewing the application use log 83.

Referring to FIG. 23, N is an application number of identifying the application type uses for preparing the user file, while K is a process number indicating the type of the output process for the user file, used for obtaining the product, and D is log information acumulated in the appllication use log 83. The types of the output process for the user file include, for example, printing, FAX transmission, e-mail transmission and OCR process. Also the log information accumulated inn the application use log 83 includes, for example, the number of prints, number of FAX transmissions and size of e-mail.

At first, in a step S222, the add-up server 52 receives, from the user terminal 6, the application number N of the application used in the user terminal 6, the type of the output process for the prepared user file, the log information, and the user ID of the user of the user terminal 6.

In a step S223, the add-up server 52 obtains the process number K and the log information D based on the type of the output process and the log information, received from the user terminal 6 in the step S222.

In a step S224, the add-up server 52 stores the "user ID" received in the step S222 and the "application name" corresponding to the application number N in the respective fields of the application use log shown in FIG. 26 and to be explained later. It also stores the use log derived from the process number K obtained in the step S223 and the log information D in the field of each output process, whereupon the sequence is terminated.

In the following there will be explained, with reference to FIGS. 24A and 24B, a charge table 82 used for calculating the application use fee in the present embodiment.

In FIGS. 24A and 24B, the fee is different depending on the type of the application and the content of the output process for the user file prepared using the application. More specifically, the fee is variable depending not only on tht type of the used application but also on the output process, for example whether the user file prepared using the application is printed, or it is transmitted by e-mail to another destination, or it is transmitted by facsimile or it is taken out as the electronic data (hereinafter called contents retrieval). Also in case plural applications are used for preparing a user file, fees are charged in overlapping manner. There may also be adopted other output processes other than those cited above, and such processes are also set in the charge table, together with the corresponding fees. Also the fee for an output process not listed in the charge table may be selected same as that for the file retrieval.

Furthermore, the fee may be made variable depending on the destination of output of the user file.

The charge table includes a standard charge table shown in FIG. 24A and a discount charge table shown in FIG. 24B, in which the fees in the latter are lower than those in the former. The add-up server 52 may hold a plurality of such charge tables and may select a charge table to be used according to the condition such as the destination of the output of the user file, whereby the charge setting can be easily altered.

In the following there will be explained, with reference to a flow chart shown in FIG. 25, an operation of the user terminal 6 for generating output information for outputting the user file prepared using the application.

At first, in a step S210, the user terminal 6 obtains the drive name at the destination of output.

In a step S211, the user terminal 6 discriminates, from the drive name of the destination of the output obtained in the step S210, whether the drive at the output destination is a drive on the application server 50. If the step S211 identifies that the drive is on the application server 50 (Yes), the sequence is terminated. If the step S211 identifies that the drive is not on the application server 50 (No), a step S212 stores that the output information is a file, whereupon the sequence is terminated.

In the following there will be explained an application use log 83 held by the add-up server 52, with reference to a schematic view shown in FIG. 26.

As shown in FIG. 26, there are provided an "application type" field for storing the type of the used application, a "user ID" for storing the ID of the user who has used the application, and a field for storing the log information for each kind of the output process for the product. In FIG. 26, the output processes for the product include "print process", "e-mail transmission", "facsimile transmission" and "file retrieval". FIG. 26 indicates that, for the user file prepared with the "application A", the "user ID 0001" has executed "print process" for 102 sheets, "e-mail transmission" for 42 kbytes, "FAX transmission" for 13 sheets, and "contents retrieval" for two times. There are other similar products. In FIG. 26, the application use log is sorted according to the "user ID", but such example is not restrictive.

In the following there will be explained, with reference to a schematic view shown in FIG. 27, the result of calculation of the application use fee in the add-up server 52.

In FIG. 27, there are stored, for each user file prepared with the application, the type of the use application, the user ID, the log information of the output process (number of printed sheets, number of bytes transmitted by e-mail etc.) for the user file, and the application use fee calculated according thereto.

In the following there will be explained the operation of the add-up server 52 for calculating the application use fee, with reference to FIGS. 28A and 28B.

At first reference is made to a flow chart in FIG. 28A.

In a step S81, the add-up server 52 awaits a request for process (S81).

In a step S82, the add-up server 52 discriminates whether the request is for storage of the user file. If the result of discrimination is affirmative (Yes), the sequence proceeds to a step S84, but, if negative (No), the sequence proceeds to a step S83.

Then a step S84 discriminates whether the destination of storage of the user file is within the application server 50. If the result of discrimination is affirmative (Yes), the sequence is terminated, but, if negative (No), the sequence proceeds to a step S87.

Also in a step S83, the add-up server 52 discriminates whether the request is for the e-mail transmission. If the result of discrimination is affirmative (Yes), the sequence proceeds to a step S87, but, if negative (No), the sequence proceeds to a step S85.

Also in a step S85, the add-up server 52 discriminates whether the request is for the FAX transmission. If the result of discrimination is affirmative (Yes), the sequence proceeds to a step S87, but, if negative (No), the sequence proceeds to a step S86.

Also in a step S86, the add-up server 52 discriminates whether the print process is selected. If the print process is selected (Yes), the sequence proceeds to a step S87, but, if not selected (No), the sequence proceeds to a step S88.

Thus the steps S83, S85 and S86 discriminate the output process to be applied to the user file, prepared using the application, for obtaining the product.

In case the product is obtained outside the application server 50 by an output process such as "printing", "e-mail transmission" or "FAX transmission", the step S87 renews the application use log information in order to charge the application use fee to the user.

In the following reference is made to a flow chart of FIG. 28B, showing a case where the application use fee is different depending on the domain of the destination of output of the product. In the flow chart of FIG. 28B, the steps of the numbers same as those in the flow chart of FIG. 28A are equivalent in function, so that the following explanation will only be made on steps S89, S90 and S91 which are different in function from the flow chart FIG. 28A.

In case the step S83 discriminates that the request is for the e-mail transmission (Yes), or the step S84 discriminates that the destination of storage of the user file is not within the application server 50 (No), the sequence proceeds to a step S91, which discriminates whether the destination of output of the user file is within a domain same as that of the application server 50. If the step S91 identifies that the destination of output of the user file is within a domain same as that of the application server 50 (Yes), the step S90 selects the discount charge table in FIG. 24B for calculating the application use fee, and the sequence then proceeds to the step S87. On the other hand, if the step S91 identifies that the destination of output of the user file is not within a domain same as that of the application server 50 (No), a step S89 selects the standard charge table in FIG. 26A for calculating the application use fee, and the sequence then proceeds to the step S87.

In case the step S85 identifies the FAX transmission (Yes) or the step S87 identifies the printing (Yes), the application use fee is not related with the destination of output of the user file, so that the step S89 selects the standard charge table in FIG. 24A for calculating the application use fee.

Thus, in the flow chart in FIG. 28B, the charge table to be used for calculating the fee to be charged is selected according to whether the destination of output of the product of the output process by the user is within a domain same as that of the application server 50, whereby the application use fee can be easily calculated with different charge systems.

In the following there will be explained, with reference to a sequence chart shown in FIG. 29, an operation of storing the user file prepared with the application in the application server 50 or 51, an operation of printing the stored user file and an operation of FAX transmission or e-mail transmission of the user file. The following description will be made on the application server 50, but the operation will be the same for the application server 51.

Referring to FIG. 29, the user terminal 6 requests downloading of the appllication to the application server 50 and informs the user ID (S101). Based on the download request and the user ID transmitted from the user terminal 6 in the step S101, the application server 50 executes authentication of the user terminal 6 and application transfer to the user terminal 6 (S102).

Then the user terminal 6 downloads the application transmitted from the application server 50 in the step S102 and executes the application to prepare the user file (S103). In this operation, after the downloading of the application by the user terminal 6, the application server 50 may issue an execution instructing command to achieve execution of the application.

Then the user terminal 6 requests the storage of the user file prepared in the step S103 to the application server 50 (S104). Based on the request for storage of the user file from the user terminal 6 in the step S104, the application server 50 executes storage of the user file (S105).

Then the user terminal 6 arbitrarily combines one or plural of printing (S106, S108), FAX transmission (S109, S111) and e-mail transmission (S112, S114) and executes such process or processes on the prepared user file.

Then the add-up server 52 renews the application use log (S107, S110, S113), based on the requests for the above-mentioned output processes (S106, S109, S112) from the user terminal 6.

In the following there will be explained, with reference to a sequence chart shown in FIG. 30, an operation of storing the file outside the application server 50 or 51, retrieving the file, outputting the product and recovering the charge therefor, in contrast to the sequence shown in FIG. 29 in which the file is stored in the application server 50. As the steps S101 to S104 in FIG. 30 are same as those in FIG. 29, these steps will no longer be explained and the following explanation will be given only to steps S120 to S132 representing operations different from those in FIG. 29. The following description will be given on the application server 50, but the operations are same also for the application server 51.

In a step S105, based on the request for file storage from the user terminal 6 in the step S104, the application server 50 executes storage of the file and requests the renewal of the application use log to the add-up server 52. The destination of storage of the file is assumed to be outside the application server 50.

In a step S121, based on the request from the application server 50 in the step S120, the add-up server 52 renews the application use log.

In a step S123, the application server 50 transmits the file to the user terminal 6.

In a step S122, the user terminal 6 receives the file transmitted from the application server 50 in the step S123.

Then, in a step S124, the user terminal 6 request file output (product retrieval) to the application server 50. It is assumed that there is requested a process of retriving, as the product of the file, the file in a form reusable as electronic data (contents retrieval).

In a step S125, based on the request from the user terminal 6 in the step S124, the application server 50 executes output process of the file (product retrieval) and request the renewal of the application use log to the add-up server 52.

In a step S126, based on the request from the application server 50 in the step S125, the add-up server 52 renews the application use log 83.

In a step S128, the application server 50 transmits the file to the user terminal 6.

In a step S127, the user terminal 6 receives the file transmitted from the application server in the step S128.

In a step S129, the add-up server 52 calculates the application use fee based on the application use log renewed in the step S126.

In a step S130, the charge management server 1 request the transmission of the charge information to the add-up server 52.

In a step S129, the add-up server transmits, to the charge management server 1, the charge information


Free Web Sudoku Puzzles.
Solve with your browser.
  8 1 2       3 6
            4 8  
      5         1
  7   8         5
    4       8    
1         3   6  
4         2      
  1 2            
7 5       9 3 2  
What is it?



Add Your Site · Terms Of Service · Privacy Policy


DISCLAIMER
Linkgrinder is a free service that searches the Internet and indexes all files found so that you may search quickly and easily for shared files. These files are created and made available individually by users whose identity we are not aware of and who we have no control over. In essence we function like a search engine tool; these files ARE NOT STORED OR SERVED BY OUR NETWORK. We are not responsible for any materials obtained by using our service. We do not monitor any of the contents of these files. These files may contain viruses, illegal materials, materials inappropriate for minors, offensive files and the like. BY USING OUR SERVICE, YOU ASSUME FULL RESPONSIBILITY FOR DOWNLOADING THESE MATERIALS AND WILL INDEMNIFY US FOR ANY DAMAGES THAT MAY BE INCURRED.

For More Specific Information VIEW OUR TERMS OF SERVICE.

Thank you and Enjoy!