JPH11249854A - Charging server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently execute a charging processing as against a printing processing on a network. SOLUTION: A print client 102 transmits a printing request file and a slip file 104 to a charging server 100. The charging server 100 transmits a printing permission file 110 where the permitted quantity of resources such as the number of sheets of available printing paper is described to the printing client 102. The charging server generates charging information based on the quantity of the resources and stores it in a charging information file 108. The printing client 102 transmits the printing permission file 110 to a printer device 112 in advance of the slip file. The printer device 112 executes printing processing only when the printing permission file 110 is transmitted in advance of the slip file 104. Charging information undergoes centralized management and also printing is efficiently controlled.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to accounting for a print service by a print server or a network printer used on a network. In particular, the present invention relates to a print server and a printer that can easily charge for a print service, and an apparatus and a method related thereto.

[0002] The present invention also relates to various apparatuses and methods suitable for performing charging for various services, for example, charging for file transfer.

[0003]

2. Description of the Related Art When printing a form or the like on a network, the print requests are once collected by a print server or the like, and the print server performs a predetermined spooling process or the like, and appropriately sends the request to a printer on the network. Data to be printed was sent out.

As described above, when printing a form or the like,
It is often necessary to charge for each print process. This billing is often performed by a print spooler in the print server. That is, since the print spooler actually holds the file to be printed, the number of prints and the like can be relatively easily known. Therefore, it is preferable that the calculation of the billing amount is also performed by the print spooler. Such a conventional charging operation will be described below with reference to FIG.

FIG. 12 is an explanatory diagram showing a conventional printing process on a network and a charging operation for the printing process.

As shown in FIG. 12, conventionally, a client 10 requesting a print sends a print request to a print server 12. The print server 12 appropriately spools a print request from the client 10 using the print spooler 12a. The print spooler 12a accumulates billing information for each user by counting the number of pages of a form to be billed. This charge information is stored in the charge information file 1 in the print server 12.
4 was stored.

Japanese Patent Laid-Open Publication No. Hei 6-266461 discloses a charging management system for a color printer.

[0008]

In recent years, so-called network printers 16 have become widespread. Therefore, in recent years, requests for printing from the client 10 directly to the network printer 16 have been increasing. As described above, in a system configuration in which each client 10 directly requests the network printer 16 to print a form or the like without passing through the print server 12, unlike the related art, centralized accounting management is performed. It is difficult.

As described above, when a print request is issued directly to the network printer 16 without passing through the print server 12, the network printer 16 itself may be provided with a function of managing charging.

However, in a so-called horizontal distributed system in which a plurality of servers, a plurality of clients, and a plurality of network printers 16 are provided on a single network, the management of such billing becomes complicated. However, there is a problem that expansion such as adding a network printer 16 or adding a client 10 becomes extremely complicated.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a billing server independent of a conventional print server, and to centrally manage billing for print processing by this billing server. It is to be.

Another object of the present invention is to smoothly perform charging processing for charging processing for services other than printing processing.

[0013]

In order to solve the above-mentioned problems, the present invention is based on a print data file to be printed and a print request file indicating a request for printing the print data file. A print permission file generation processing unit that generates a print permission file indicating that printing of the print data file is permitted, and a charging log processing unit that stores charging information of a client that has output the print request file. .

Further, according to the present invention, the print permission file includes print permission information, and the print permission information includes at least one set of a combination of an identifier of each resource used for printing and a permitted use amount of the resource. It is characterized by including.

Further, in the invention, it is preferable that the print permission file generation processing unit creates the print permission information based on a resource amount used for printing described by the client in the print request file. It is assumed that.

Further, according to the present invention, the print permission file generation processing unit stores a correspondence between a predetermined combination of resource amounts used for printing and a print permission class defined for the combination. The print permission file generation processing unit reads the print permission class described by the client in the print request file, and stores the combination of the resource amounts used for printing corresponding to the print permission class. The print permission information is created based on the combination of the resource amounts.

Further, according to the present invention, the print permission file generation processing section stores the generated print permission file,
Further, the print permission file generation processing unit transmits a file name of the generated print permission file.

Further, according to the present invention, the accounting log processing unit comprises:
The accounting information is stored in an accounting information log file for each accounting log record.

Further, the present invention is characterized in that the accounting log record includes a name of a user who has requested printing.

Further, the present invention is characterized in that the billing log record includes a name of a resource used for printing and a permitted use amount of the resource.

According to the present invention, a billing table storing names of resources used for printing, billing amounts per unit amount of the resources, and contents of the billing information log file are read. And a billing information totalizing unit that calculates, for each user, a billing fee to be charged to each user for print processing based on the contents of the billing information log file and the billing amount in the billing table. It is characterized by the following.

Further, the present invention is characterized in that the billing information tallying unit outputs the calculated billing amount to a billing tally file.

Further, the present invention is characterized in that the billing information tallying unit outputs the calculated billing amount to a billing tally form.

[0024] Further, the present invention permits file transfer of the transfer data file based on a transfer data file to be transferred and a transfer request file indicating a request for file transfer of the transfer data file. A transfer permission file generation processing unit that generates a transfer permission file indicating that the transfer is to be performed, and a charging log processing unit that stores charging information of a client that has output the transfer request file.

Further, according to the present invention, the client includes a business program for requesting printing.

Further, in the present invention, the client includes a business program for requesting a file transfer.

[0027]

Preferred embodiments of the present invention will be described below with reference to the drawings.

Embodiment 1 FIG. 1 is a configuration diagram of a network system according to a preferred embodiment of the present invention. As shown in this figure, a feature of the first embodiment is that a billing server 100 independent of the print server is provided.

First, a client program or a batch program (hereinafter, referred to as a print client 102) for printing a form or the like receives the charge server 10 before transmitting a print request to a print server or the like.
For 0, a form file 104 to be printed and accounting information 106 such as the number of printed pages are notified. The transmission of the accounting information 106 and the form file 104 is indicated by (1) in FIG.

Next, billing server 100 stores transmitted billing information 106 in billing information file 108. This accumulation operation is indicated by (2) in FIG.
The billing server 100, together with the storage operation, performs the billing information 1
A print permission file 110 is generated based on the print permission file 06 and the form file 104. The operation of generating the print permission file 110 is indicated by (3) in FIG. Then, the accounting server 100 transmits the print permission file 110 to the print client 102.

This print permission file 110 defines resources that can be used, such as the number of print permitted pages, and includes a form recognition key for uniquely recognizing data of the form file 104 to be printed. It is.

The print client 102 transmits the transmitted print permission file 110 and the form file 104 to be printed to the printer 112 connected to the network. Specifically, when the print client 102 transmits the print permission file 110 to the printer device 112, the print client 102 transmits the form file 104 to the printer device 112 following the transmission. This transmission operation is indicated by (4) in FIG.

The printer device 112 has a function of rejecting a print request when only the form file 104 is transmitted without accompanying the print permission file 110. Further, when the form file 104 is transmitted following the print permission file 110, the printer device 112 first transmits the form file 104 using the form recognition key described in the print permission file 110. The form file 104 is the print permission file 110
Check if the file is allowed by.
More specifically, the form recognition key described in the print permission file 110 is continuously transmitted to the form file 104.
A check is performed to determine whether or not the ID is uniquely recognized.

As a result of this inspection, if the form file 104 can be uniquely recognized and it is confirmed that the printing permission has been obtained, the printer device 112 starts printing the form file 104.

The printer device 112 constantly monitors the number of pages to be printed during the printing process. If printing is performed beyond the number of print-permitted pages described in the print-permitted file 110, the printing is stopped.

As described above, according to the present embodiment, accounting management for form printing can be easily performed even in a distributed system in which a plurality of servers and clients and a network printer are installed. Note that the printer 112 according to the present embodiment has a function as a print server. In the present embodiment,
The printer device 112 has a function as a print server. For example, the print permission file 110 is stored in a local area network board or a printer adapter for connecting the printer device to a local area network.
It is also preferable to provide a check function of As described above, if the local area network board or the printer adapter is provided with the function of checking the print permission file 110, it is possible to use a conventional printer that is not compatible with the network.

Further, according to the present embodiment, the print server (the printer device 112 in the present embodiment), the printer device connected via the printer adapter, and the like need to have a charge management function for each user. Disappears. Further, when the number of users increases, if the addition of the user is set only in the charging server 100, the charging is automatically performed, so that the operation of the system can be facilitated.

Further, the printer 112 in the present embodiment merely checks the print permission file 110 without depending on the user or the system configuration. For this reason, it is possible to easily make settings when adding the printer device 112 to the network system.

The billing method proposed in the present embodiment uses a billing server 100 for billing when printing a form.
Is calculated with However, the aggregation of such charges is
The present invention can be applied not only to print processing but also to all services using resources on a network. For example, a similar server can also be used when performing accounting management for resource amounts such as communication amounts when transferring files. As the communication amount, it is conceivable to charge the file transfer using, for example, the number of bytes of the transmitted data, the time required for the communication, and the like.

Embodiment 2 Embodiment 2 is an embodiment showing a basic idea of the present invention, and an explanatory diagram thereof is shown in FIG.

As shown in FIG. 2, in the present embodiment, the business client X1 and the print server Y
1 and a billing server 100 are connected via a local area network 200. That is, the business client X1, the print server Y1, and the billing server 100 each have an interface for connecting to the local area network 200.

First, the business client X1 that performs printing
Notifies the accounting server 100 of a print request file 202 in which a request for resources required for printing, such as the number of print sheets, is recorded, and a print data file 204. This notification operation is indicated by (1) in FIG.

As described above, the print permission is requested by notifying the print request file 202 and the print data file 204 to the accounting server 100. The contents of the print request file 202 can be various print parameters such as the size of the print data file 204 and the execution time of the print processing, as well as the number of print sheets. still,
In the present embodiment, the case where the business client X1 makes a print request is described, but the same applies to a case where print is requested by a predetermined batch process or the like.

When the print request file 202 and the print data file 204 are transmitted, the billing server 100 recognizes the amount of usable resources such as the number of print sheets recorded in the print request file 202 and the print data recognition. A print permission file 110 including a key is generated. The print permission file 110 is generated by the print permission file generation processing unit 206.

Here, the amount of resources that can be used means parameters such as the number of sheets permitted for printing, and the print data recognition key uniquely identifies the print data file 204 to be printed. The key that can be.

Specifically, the print data identification key is preferably a key determined from the contents of the print data file 204. This key is calculated by performing a predetermined operation on the contents, but more simply, it is preferable to use the address in the print data file 204 and the value at that address as the key. The print data identification key is stored in the print data file 204.
It is also preferable to include the creation date and time.

Further, the print data identification key may include a key specified from the above contents of the print data file 204 and a plurality of types of keys such as a creation date and time. By combining a plurality of types of keys, the print data file 204 can be identified more accurately.

When the print permission file 110 is returned from the accounting server 100 to the business client X1, printing permission is given.

FIG. 3 is an explanatory diagram showing the structure of the print permission file 110. As shown in this figure, the print permission file 110 includes a print data file name and a print data identification key. Further, the print permission file 110 includes a repetition of a pair of a resource ID and a permitted amount used for printing. In the text, this repetition is called print permission information. The resource ID is an ID for identifying a resource, and the resource name is used for simplicity (see FIG. 3).

The accounting server 100 records, in the accounting information log file 208, the amount of usable resources (permitted to be used) such as the number of print sheets for the user who has been permitted to print. That is, charging information for the resource amount permitted to be used is recorded in the charging information log file 208. The recording of the billing information in the billing information log file 208 is indicated by (3) in FIG.

The writing to the accounting information log file 208 is performed in accounting log record units. This writing is performed by the accounting log processing unit 210. In addition, it is preferable that the log record generally includes the name of the user who has requested the printing, in order to clarify the billing target person. Each billing log record includes the name of the resource and the permitted use amount of the resource, and is configured so that the billing amount can be easily calculated. FIG. 6 is an explanatory diagram showing a specific configuration of the accounting log record.
As shown in the figure, the resource log record is a record including a print request user name, a resource name, and a use (permission) amount.

The accounting information is recorded in the accounting server 100
Is performed by the accounting log processing unit 210. The reply of the print permission file 110 to the business client X1 is represented by (2) in FIG.

The business client X1 sends the print data file 20 to be printed to the print server Y1.
4, the print permission file 110 returned from the charging server 100 prior to the file transfer.
Is transmitted to the print server Y1 in advance. The transmission of the print permission file 110 is indicated by (4) in FIG.

Next, following the transmission of the print permission file 110, the business client X1 transmits the print data file 204 to the print server Y1. The transmission of the print data file 204 is indicated by (5) in FIG.

When printing the print data file 204, the print server Y1 refers to the print permission file 110 received immediately before. Then, it is checked whether the print data file 204 is uniquely recognized by the print data recognition key in the print permission file 110. This inspection is performed by the print monitoring unit 212.

When the print monitoring unit 212 in the print server Y1 determines that the print data file 204 cannot be uniquely recognized from the print data recognition key, it notifies the user (the business client X1) of the print failure.
This notification is indicated by (7) in FIG.

Further, when printing is not performed,
It is often convenient for management to provide the same notification to the network administrator as well as the client. Therefore, it is desirable that the print monitoring unit 212 notifies not only the client but also the network administrator of the audit information indicating that the printing has not been performed.

It is preferable that the print data file 204 is recognized using a key, but it is a simple method to simply look up the file name. By simply comparing only the file name, it is checked whether or not the file name described in the print permission file 110 and the file name of the print data file 204 match.

On the other hand, if the print data file 204 transmitted by the print data recognition key can be uniquely recognized, the printing process is started. This printing process is described in FIG.
Is shown by (8). This printing process is performed in the print processing unit 214 in the print server Y1.

At this time, during the execution of the printing process, the consumption of the used resources such as the number of print pages is monitored, and the print permission file 1
Monitoring is performed so as not to exceed the range specified in 10. This monitoring is specifically performed by the print monitoring unit 212.

Then, when the value exceeds the range specified in the print permission file 110, the printing process is interrupted, and this is notified to the user.

FIG. 4 shows an example of the allowable amount of each resource specified in the print permission file 110. Thus, the monitored resource includes, for example, the number of prints (sheets).
And print processing time (minutes), print data amount (byte), print toner amount (gram), and the like (see FIG. 4). The creation of these print permission amounts is performed by the print permission file generation processing unit 2
06.

In the present embodiment, the printing process is stopped when one of the resources specified in the print permission file 110 is used in excess of the permitted amount.

The process of interrupting the printing process is described in FIG.
In (6). Also, when the printing process is interrupted, it is preferable to notify the user of the interruption as described above. This notification is indicated by (7) in FIG.

In the embodiments described above, the permitted amounts of the respective resources are individually set. However, in the actual printing process, it is considered that the same permitted amount is often used repeatedly. Therefore, it is also preferable that a predetermined combination of the permitted amounts of each resource is defined in advance as a class, and the business client designates the permitted amounts of a plurality of resources collectively by using this class.

That is, the business client X1 that requests printing does not specify the amount of each resource whose use is to be permitted, but specifies the class. It is preferred to specify the amount at one time.

FIG. 5 shows an example of the print permission class. As shown in this figure, for example, the print permission class A defines the number of prints as ten, but is a print permission class that does not limit the other print processing time or the like. In the print permission class B, the permitted number of prints is one.
The print permission class is 00 sheets, but there is no restriction on other print processing time and the like. The print permission class C is
The permitted number of prints is 100, the permitted amount of print processing time is 60 minutes, and the permitted amount of print data is 4096.
The print permission class is a byte. The print permission class D is a print permission class in which the number of prints, print processing time, print data amount, and the like are not limited at all.

Specifically, the print permission file generation processing unit 206 of the accounting server 100 stores the contents of a table as shown in FIG. In addition, the storage contents include a predetermined print permission class. Prior to the actual print processing, the data of the print permission class is transferred to the print permission file generation processing unit 206.
Must be stored.

Now, with respect to the accounting server 100 storing the contents of the print permission class, the business client X1
Transmits a print request file 202 describing a print permission class, which is a combination of the permitted amounts of resources to be used. Then, the print permission file generation processing unit 206 in the charging server 100 searches for the print permission class described in the print request file 202 from the contents of the stored table. Then, the requested permission amount of each resource for printing which the found printing permission class means is
They are read from the stored contents. After the required amount of each requested resource has been determined,
The print permission file generation processing unit 206 generates the print permission file 110.

As described above, the billing server 100, which is a characteristic configuration of the present embodiment, receives the print request from the business client X1 and prints the print permission file 110.
Is generated, and billing information is created based on the requested resources used for printing, and recorded in the billing information log file 208.

In the monthly processing or the like, the billing information is compiled for each user or user group from the billing information log file 208 on the billing server 100, and a billing total file 216 and a billing summary form 218 are created. The accounting process and the creation process are performed by the accounting information aggregation processing unit 220 in the accounting server 100. The process of reading the charging information log file by the charging information totalizing unit 220 is indicated by (a) in FIG. The process of creating the accounting summary file 216 by the accounting information aggregation processing unit 220 is shown by (b) in FIG.

The charging information totaling section 220 has a charging table 500 storing resource names and charging amounts per unit amount of resources.

Based on the charging table 500 and the charging information log file 208, the charging information totalizing section 220
Performs monthly tabulation processing and the like. FIG. 7 is an explanatory diagram showing the concept of the operation of the monthly totaling process. As shown in FIG. 7, the charging table 500 stores the charging amount per unit of each resource, and the charging information log file 208 records the amount of resources used by each user. . Based on these two pieces of information, the billing information tallying unit 220 performs monthly tallying processing. As a result, FIG.
As shown in (1), the billing amount is calculated and calculated for each user. In addition, the billing information tally processing unit 2
Reference numeral 20 denotes a charging summary file 216 and a charging summary form 21
8 and outputs the tally result.

The business client X1 is 1 in FIG.
Although only one is shown, this business client X1 can be freely added. When the business client X1 is added, if only the connection from the business client X1 to the charging server 100 is set, the printing request from the new business client X1 is automatically charged. As a result, the plurality of print servers Y1 connected to the local area network 200
It is not necessary to register a new business client X1 for each of the above, and it is possible to easily add the business client X1.

Further, according to the present embodiment, not only the business client X1 but also the print server Y1 can be easily added. When the print server Y1 is newly added to the local area network 200, the new print server Y1 is automatically set simply by setting the accounting server 100 so that the business client X1 can newly access the print server Y1. Can be charged for the print processing performed by the user.

User to be charged (or user group)
May be added to the billing server 100 as desired. This setting of the user group and the like is used only when the accounting information is totaled, and the information only needs to be known by the charging information aggregation processing unit 220. As a result, the business client X1 and the print server Y1 do not need to be changed at all.

In the present embodiment, the accounting server 100 is a single independent server device. However, it is preferable that the accounting server 100 is constituted by a business server on which a business program runs.

Embodiment 3 This embodiment is an embodiment using a print spooler, and its explanatory diagram is shown in FIG.

As shown in FIG. 8, the present embodiment is characterized in that the print server Y1 has a print spooler 221 and, as an actual printer, is directly connected to the print server Y1. Connected printer 222 and local area network 20
0 is directly under the control of the print server Y1. And
The print spooler 221 stores the print permission file 110
Or, the print data file 204 is spooled. The network printer 224 has an interface for connecting to the local area network 200.

Hereinafter, the operation of the present embodiment will be described.

First, the business client X1 transmits the print request file 202 and the print data file 204 to the accounting server 100, and sends the print permission file 110
Get. The transmission of the print request file 202 and the print data file 204 is indicated by (1) in FIG. 8, and the operation is the same as in the second embodiment described with reference to FIG. In addition, the accounting server 100 determines that the print permission file 110
8 is indicated by (2) in FIG. 8, which is the same operation as that of the second embodiment in FIG. The charging server 100 has the same configuration as the charging server 100 of the second embodiment.

The business client X1 sends the print permission file 110 and the print data file 204 to the print server Y1. The print server Y1 supplies the transmitted print permission file 110 and print data file 204 to the print spooler 221.

The print spooler 221 transmits the print permission file 110 and the print data file 204
Are stored in the spool area 226, and the execution of the printing is scheduled. At this time, the print data file 20
If the print permission file 110 has not been transmitted prior to Step 4, the print spooler 221 rejects spooling.

The spool area 226 specifically stores F
A memory area and a disk area which are buffers of the IFO and are under the control of the print spooler 221 are used.
The print spooler 221 schedules print processing for a set of the print permission file 110 and the print data file 204 stored in the spool area 226. This scheduling process itself is a well-known technique.

The print processing unit 22 of the print spooler 221
Reference numeral 8 denotes a print permission file 110 whose print order has been turned.
And checks whether the contents of the print data file 204 are appropriate. That is, the print processing unit 228
The print monitoring unit 212 according to the second embodiment in FIG.
This is a means that also has the function of: Specifically, the print data recognition key in the print permission file 110 is read, and the print data file 204 sent in pairs (sent as a set) is uniquely identified using the print data recognition key. A check is made to see if it can be recognized. As a result of this inspection, if it can be uniquely recognized, it is determined that printing can be performed, and the print processing unit 228 determines the number of available resources such as the number of print papers specified in the print permission file 110. Execute print processing within the limits.

As described above, the print processing unit 228 inspects the print data file in the print spooler 221.

Specifically, the print processing unit 228 sends the print data of the print data file 204 to the directly connected printer 222 directly connected to the print server Y1 or the network printer 224 connected to the local area network.

According to the present embodiment, since the print processing unit 228 is provided in the print spooler, the spool area 22
6, the print data file 204 and the print permission file 11
While 0 is stored, it is possible to check whether the contents of the print data file 204 are valid. As a result, a smooth billing method can be realized by using the conventional network printer 224 connected to the local area network as it is, without providing the printer itself with the means for executing the inspection.

It is also preferable to use a print server adapter device having the functions described in the present embodiment.
When the print server adapter is used, a print data supply unit that supplies the print data file to the printer is provided in the print server adapter only when printing of the print data file 204 is permitted. Will be.

Embodiment 4 In the above embodiment, the inspection such as the number of print sheets recorded in the print permission file 110 is performed by the print monitoring unit 212 or the print processing unit 22.
8 was performed by the monitoring unit.

However, when the program itself operating on the business client X1 sends the print data file 204 to the print server Y1, it refers to the contents of the print permission file 110 to determine whether the print permission is correctly given. It is also preferable that the inspection itself is performed, and that the program itself monitors the printing operation.

In the present embodiment, the print request input program 23 in the business client X1 is
0 shows an example in which printing is monitored.

An explanatory diagram of the fourth embodiment is shown in FIG. As shown in FIG. 9, this system connects a business client X to a local area network 200.
1, the billing server 100, and the print server Y1 are connected. Among them, the billing server 100 and the print server Y1 have the same configuration as the billing server 100 and the print server Y1 in the above-described embodiment. A characteristic configuration of the present embodiment is that the business client X1 includes a print monitoring unit 232 in the print request input program 230.

The business client X1 obtains the print permission file 110 from the accounting server 100 in the same manner as in the above embodiment. Then, printing is performed by transmitting the print permission file 110 and the print data file 204 to the print server Y1. These operations are the same as in the above-described embodiments.

A characteristic feature of this embodiment is that the print request input program 230 for requesting printing has a print monitoring unit 232. by this,
Print permission file 110 sent to print server Y1
The print monitoring unit 232 performs an inspection on the contents of the print data file 204 and the print data. This monitoring operation is indicated by (1) in FIG. As a result of this monitoring, if the contents of the print data file 204 exceed, for example, the number of print sheets in the print permission file 110, the fact is reported to the print request input program 230, and the print request input program 230 To stop. Specifically, a new print data file 2
04 is not transmitted, and the print server Y1 is requested to stop printing.

As described above, since the print monitoring is performed on the side of the business client X1, more advanced print management can be performed while using a conventional printer or a conventional print server.

Embodiment 5 FIG. In each of the above-described embodiments, the print permission file 110 generated by the accounting server 100 has been transmitted to the business client X1. However, the print permission file 110 generated by the accounting server 100 for each request in response to a print request from the business client X1 is likely to be a file having substantially the same contents. The reason is that the print format is often a fixed format and the number of prints is often determined according to the size (number of pages) of the print data file 204.

Therefore, it is not only wasteful to generate the print permission file 110 having substantially the same contents and transmit it to the business client X1 every time a print request is generated, but also increase the traffic on the local area network 200. There is a risk that it will be done. Therefore, the print permission file 110 is generated in the print permission file generation processing unit 206 of the accounting server 100, but the print permission file 110 is
It is also conceivable to send only the file name. In the fifth embodiment, charging server 100 having such an operation is described.
FIG. 10 is an explanatory diagram thereof.

As shown in FIG. 10, the business client X1 first notifies the print request file 202 and the print data file 204 to the accounting server 100, and requests printing permission.

This operation is shown by (1) in FIG. 10 and is the same as in the above-described embodiment.

The accounting server 100 stores the print permission file 1
10 are generated in the same manner as in the above-described embodiment. Then, while the print permission file 110 itself is held inside the accounting server 100, only the file name of the print permission file 110 is transmitted to the business client X1. In the present embodiment, the print permission file generation processing unit 206
Saves the print permission file 110. Then, the print permission file generation processing unit 206 sends the print permission file 110
Only send the file name of.

The operation of transmitting only the file name of the print permission file 110 is described in FIG.
Indicated by

As described above, since only the file name of the print permission file 110 is transmitted to the business client X1 instead of the print permission file 110 itself, the traffic volume on the local area network 200 is reduced.

Next, the business client X1 transmits the file name of the print permission file 110 and the print file 204 to the print server Y1. As a result, the business client X1 requests the print server Y1 to print the print data file 204.

The print server Y1 reads the print permission file 110 held by the charging server 100 from the charging server 100 based on the file name of the print permission file 110 sent from the business client X1. This reading operation is performed by the print monitoring unit 212.

The print monitoring unit 212 prints the print permission file 11
0, it is checked whether or not the printing is permitted. If the printing is permitted, the print processing unit 214 of the print server Y1 sends the print data file 204 transmitted by the business client X1. Start printing. Further, during the printing process, the amount of resources used for printing is monitored. These inspections and monitoring are the same as in the above-described embodiment.

More specifically, when printing is to be performed exceeding the number of printing papers specified in the print permission file 110 during printing, the print monitoring unit 2
12 requests the print processing unit 214 to stop, and the print processing unit 214 stops printing. Such a series of operations are shown in FIG. 10 as (3), (4), (5),
Each is indicated by (6).

When the printing of the print data file 204 is completed, the print monitoring unit 212 of the print server Y1 sends the print permission file 11 stored in the accounting server 100
0 is deleted.

The reason for deleting the print permission file 110 is to prevent the same print permission file 110 from being used more than once. That is, unless the created print permission file 110 is deleted, the business client X1 can issue the same print request to the print server Y1 any number of times by using the print permission file name twice or more. . On the other hand, the accounting process in the accounting server 100 is performed only once. For this reason, in the present embodiment, the print monitoring unit 212 deletes the print permission file 110 every time one print is completed.

It is preferable that the function of the print server Y1 in the present embodiment is provided in the print server adapter device. In this case, in addition to the above-described functions, the print server adapter device transmits the print data file 204 to the printer device when printing of the print data file 204 is permitted.
A print data file supply unit for supplying the print data file 204 needs to be provided.

Embodiment 6 FIG. In each of the embodiments described above, the charging server that charges the print request for the number of sheets required for the printing has been described. However, it is also preferable that the charging server described above is applied to charging other than charging for print processing. For example, in the case of charging the file transfer processing according to the size of the transfer file, the charging server described above can be applied as it is.

In the sixth embodiment, the second embodiment is directly replaced with a charge for the file transfer process, and FIG. 11 is an explanatory diagram thereof. FIG.
As shown in FIG. 1, this system includes a business client X1 connected to a local area network 200, a billing server 300, and a file transfer server Z1.
It is composed of In the sixth embodiment, the billing target is not the number of printing paper sheets, but the number of bytes of a transfer file, the time required for transfer, and the like. The basic operation principle of the billing server 300 is exactly the same. .

First, the business client X1 transmits the transfer request file 302 and the transfer data file 304, which is the file to be transferred, to the charging server 300. This transmission operation is indicated by (1) in FIG.

The transfer permission file generation processing unit 306 in the accounting server 300 generates a transfer permission file 410 based on the two transmitted files. The generated transfer permission file 410 is returned to the business client X1. This reply process is indicated by (2) in FIG.

In the charging server 300, a transfer permission file 410 is generated, and charging information for the transfer processing is stored in a charging information log file 308 in a charging log processing unit 310. This storing operation is indicated by (3) in FIG.

Next, the business client X1 transmits the transfer permission file 410 and the transfer data file 304 to be transferred to the file transfer server Z1. The transfer of the transfer permission file 410 is indicated by (4) in FIG. 11, and the transmission of the transfer file 304 is indicated by (5) in FIG.

The operation of the file transfer server Z1 is different from that of the print server Y1 only in that the transferred file is transferred instead of being printed, and the other processes are basically the same as those of the above-described print server Y1. Transfer processing unit 3
14 transfers the transfer data file 304 to the transfer destination server Z2. Prior to this, the transfer monitoring unit 312 checks whether the file permitted by the transfer permission file 410 matches the transfer data file 304 or not. If they do not match, the transfer is stopped. If the transfer time or the number of transfer bytes permitted by the transfer permission file 410 exceeds during the transfer operation, the transfer monitoring unit 3
In step 12, the transfer is stopped in the same manner as in the second embodiment. In either case where the transfer processing is not performed or the transfer is stopped, the transfer monitoring unit 312 sets the business client X
1 is sent a message to that effect. The process of transmitting this message is indicated by (7) in FIG.

As described above, this embodiment is an example in which the second embodiment is applied to a file transfer process instead of a print operation. In other words, the charging server 300 according to the present invention can be widely applied to various services to be charged. In the above-described second embodiment, the preferable charging server is described in the case where the printing process is charged based on, for example, the number of sheets. In the sixth embodiment, the operation of the accounting server in the case where accounting is performed based on the number of transfer bytes in the file transfer has been described. As described above, the billing server according to the present invention is used for providing services to be widely billed.

[0119]

As described above, according to the present invention, the accounting process of the client can be performed efficiently, and the print permission can be performed intensively and efficiently.

Further, according to the present invention, there is provided a billing server capable of clarifying the permitted amount of resources used for printing.

Further, according to the present invention, since the use permission amount of the resource in the print permission file is determined based on the resource amount requested by the client, a charging server capable of giving necessary and sufficient resources to the printing process is provided. can get.

According to the present invention, a set of a plurality of resource amounts is defined as a “class”, and by specifying this class, a charging server capable of easily specifying the permitted amount of a plurality of resources is provided. can get.

Further, according to the present invention, a billing server capable of reducing network traffic can be obtained.

Further, according to the present invention, since the accounting log record is written to the accounting log file, more efficient accounting information can be accumulated.

Further, according to the present invention, since the charging log record includes the name of the user, more efficient charging information can be stored.

Further, according to the present invention, since the charging log record includes the resource name and the permitted amount, more efficient charging information can be stored.

Further, according to the present invention, since there is provided the table means for storing the charge unit for each resource, the accounting process can be efficiently performed.

Further, according to the present invention, since the tally result is output to the accounting tally file, the tally result can be easily used.

Further, according to the present invention, since the tally result is output to the accounting tally form, the tally result can be obtained in a form that is easy for a human to see.

Further, according to the present invention, a billing server capable of efficiently billing for file transfer can be obtained.

Further, according to the present invention, since a business program is included as a client, a charging server capable of charging a print request from the business program can be obtained.

Further, according to the present invention, since a business program is included as a client, a charging server capable of charging a file transfer request from the business program can be obtained.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a network system according to an embodiment of the present invention.

FIG. 2 is an explanatory diagram of an embodiment of the present invention.

FIG. 3 is an explanatory diagram illustrating a configuration of a print permission file.

FIG. 4 is an explanatory diagram illustrating an example of an allowable amount of each resource specified in a print permission file.

FIG. 5 is an explanatory diagram illustrating an example of a print permission class.

FIG. 6 is an explanatory diagram of a billing log record.

FIG. 7 is an explanatory diagram illustrating an operation of a tallying process.

FIG. 8 is an explanatory diagram of an embodiment using a print spooler of the present invention.

FIG. 9 is an explanatory diagram of an embodiment of the present invention.

FIG. 10 is an explanatory diagram of an embodiment of the present invention.

FIG. 11 is an explanatory diagram of a file transfer system according to an embodiment of the present invention.

FIG. 12 is an explanatory diagram of a conventional technique.

[Explanation of symbols]

10 client, 12 print server, 14 accounting information file, 16 network printer, 100
Billing server, 102 print client, 104
Report file, 106 accounting information, 108 accounting information file, 110 printing permission file, 112 printer, 200 local area network, 202
Print request file, 204 print data file, 20
6 print permission file generation processing unit, 208 accounting information log file, 212 printing monitoring unit, 216 accounting total file, 218 accounting summary form, 220 accounting information aggregation processing unit, 221 print spooler, 222 directly connected printer, 224 network printer, 226 spool Area, 228 print processing unit, 230 print request input program, 232 print monitoring unit, 300 billing server,
302 transfer request file, 304 transfer data file, 306 transfer permission file generation processing unit, 312 transfer monitoring unit, 314 transfer processing unit, 420 transfer permission file, 500 accounting table, X1 business client, Y1 print server, Z1 file transfer server.

────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] April 5, 1999

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] Claim 5

[Correction method] Change

[Correction contents]

[Procedure amendment 2]

[Document name to be amended] Statement

[Correction target item name] 0017

[Correction method] Change

[Correction contents]

Further, according to the present invention, the print permission file generation processing section stores the generated print permission file,
Further, the print permission file generation processing unit transmits a file name of the generated print permission file.

Claims (14)

[Claims] 1. A print permission file indicating that printing of the print data file is permitted based on a print data file to be printed and a print request file indicating a request to print the print data file. And a charging log processing unit that stores charging information of the client that has output the print request file. 2. The print permission file includes print permission information, and the print permission information includes at least one set of a combination of an identifier of each resource used for printing and a use permission amount of the resource. 2. The charging server according to claim 1, wherein: 3. The print permission file generation processing unit, wherein the client describes the print permission file in the print request file.
3. The accounting server according to claim 2, wherein the print permission information is created based on an amount of resources used for printing. 4. The print permission file generation processing unit stores a correspondence relationship between a predetermined combination of resource amounts used for printing and a print permission class defined for the combination. The file generation processing unit reads the print permission class described by the client in the print request file, and stores the combination of the resource amounts used for printing corresponding to the print permission class in the stored correspondence relationship. 3. The charging server according to claim 2, wherein the print permission information is created based on the combination of the resource amounts. 5. The print permission file generation processing unit stores the generated print permission file, and the print permission file generation processing unit transmits a file name of the generated print permission file. 2. The charging server according to claim 1, wherein: 6. The charging server according to claim 1, wherein the charging log processing unit stores the charging information in a charging information log file for each charging log record. . 7. The accounting server according to claim 6, wherein the accounting log record includes a name of a user who has requested printing. 8. The accounting server according to claim 6, wherein the accounting log record includes a name of a resource used for printing and a usage permission amount of the resource. 9. A charging table storing the name of each resource used for printing and a charging amount per unit amount of each resource; reading the contents of the charging information log file; A charging information totalizing unit that calculates, for each user, a billing fee to be charged to each user for print processing based on the contents of a log file and the billing amount of the billing table. 9. The accounting server according to claim 6, 7 or 8, wherein: 10. The accounting server according to claim 9, wherein the accounting information aggregation processing unit outputs the calculated amount of money to be charged to an accounting file. 11. The accounting server according to claim 9, wherein the accounting information aggregation processing section outputs the calculated amount of the invoice to an accounting summary form. 12. Representing that file transfer of the transfer data file is permitted based on a transfer data file to be transferred and a transfer request file indicating a file transfer request of the transfer data file. A charging server, comprising: a transfer permission file generation processing unit that generates a transfer permission file; and a charging log processing unit that stores charging information of a client that has output the transfer request file. 13. The method according to claim 1, wherein the client includes a business program for requesting printing.
The charging server according to 3, 4 or 5. 14. The accounting server according to claim 12, wherein the client includes a business program for requesting a file transfer.