JPH11338696A - Charging system of software module - Google Patents

Abstract

PROBLEM TO BE SOLVED: To impose on a user a charge corresponding to the service value of a device and an appropriate charge for a serviced function, and to flexibly cope with changes in a charging method, function extension of a product itself or an individual function correspondence. SOLUTION: In a charging system of a software module which converts software that controls a hardware part mounted on an image input-output device 12 into plural software modules, and allows the software modules to cooperatively operate and control the device 12, each software module has a charging function which accumulates charges in accordance with service value or use situation applied to itself.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a billing system for a software module, and more particularly, to a feeder section for feeding a document to be read and sequentially setting the same in a reading apparatus, a scanner section for executing reading, and storing read image data. Hardware, such as a storage device to be stored, a paper feed tray unit for feeding paper to be printed and setting it in the writing device, a plotter unit for executing writing, and a paper ejection unit for distributing and placing printed paper Software for controlling a hardware module mounted on an OA device such as an image input / output device having a module is divided into a plurality of software modules, and a software module for controlling the OA device by operating the software modules in a coordinated manner. About the system.

[0002]

2. Description of the Related Art A conventional charging system for a software module of this type is disclosed, for example, in Japanese Patent Application Laid-Open No. Hei 8-6660 (Title of Invention: Charging System, Filing Date: June 23, 1994, hereinafter referred to as "prior art"). ).

[0003] That is, in the prior art, in a billing processing method for obtaining the billing information of each user by individually accumulating the usage status of the computer system, the existing software indispensable when creating a newly designed software product is used. This is a billing processing method having a software billing management means for adding the usage value of a module to the billing information.

[0004] The billing system of the computer system includes, specifically, a central processing unit, a user operation terminal for allowing a user to instruct software combination processing, and user-created software for storing software created by the user. Storage device, software module storage device for storing existing software modules used by users, charging information storage device for storing charging information for each user, and after combination in which software products after combination processing are stored Software storage device, operating system for controlling the computer system,
The hardware configuration is centered on a software combination processing unit that executes software combination processing and a charging processing unit that executes processing for updating user billing information.

In the computer system having such a configuration, the software connection request and the user name input from the user operation terminal to the operating system via the signal line are transmitted from the operating system to the software connection processing unit via the signal line. You.

[0006] In response to this, first, the software combination processing unit reads out user-created software (object module) to be subjected to the combination instruction from the user-created software storage device via a signal line. It then analyzes the read user-created software to determine the software modules that are indispensable for creating the intended software product, and all the software that needs to be combined from the software module storage device via signal lines. The module is read with the usage fee specified for the software module.

Next, the software combination processing unit notifies the charging processing unit via a signal line of a value obtained by accumulating all the read usage charges together with the user name received from the operating system via a signal line. The software to be created is combined with necessary software modules, and the created software products are combined via a signal line and stored in the software storage device.

[0008] Finally, the billing processing section reads out the billing information of the user corresponding to the user name notified from the software combining processing from the billing information storage device via the signal line, and accumulates the notified usage fee. The new billing information is stored again in the billing information storage device via the signal line.

[0009]

However, in such a conventional billing method, a billing process is performed when the user-created software created by the user is combined with a necessary existing software module. ,
It is not charged each time a software module is used.

That is, in the conventional accounting processing method, the accounting is performed when the combining process is performed, and the accounting is performed regardless of the use of the software module. Therefore, there is a problem that a difference between the actual use state of the software module and the billing occurs.

Further, in a conventional general copying machine, a fee is charged for a function, and the same fee is charged even though a completely different device is used depending on a function to be used. However, users have to pay a certain fee regardless of the value of the device. For example, whether to use a sorter with a large number of output bins to implement the sort function or to use an electronic sort using memory, the device and software used are different, but the fee is the same. .

Further, since no counter is provided for each hardware module, a usage fee is imposed regardless of whether or not the hardware module is actually used. There was also a problem that the user had to pay a usage fee.

An object of the present invention is to solve such a conventional problem. In particular, the present invention is directed to charging management of software incorporated in OA equipment or the like in units of software modules, thereby achieving device management. The task is to enable users to pay a fee according to the usage value.

[0014] In addition, it is another object of the present invention to allow a user to pay an appropriate usage fee only for a used function.

It is another object of the present invention to flexibly cope with a change in a billing method by replacing or upgrading a software module unit, expanding a function of a product itself, and supporting individual functions.

[0016]

According to the first aspect of the present invention, which has been made to solve the above-mentioned problems, the present invention provides a software for controlling a hardware module mounted on an image input / output device 12 by a plurality of software. In a software module billing system in which components are formed into software modules and the software modules are operated in cooperation with each other to control the image input / output device 12, each of the software modules pays a usage fee according to its use value or usage status. A billing system for a software module, which has a billing function for adding.

According to the first aspect of the present invention, the user pays a fee corresponding to the use value of the device by managing the charge for the software incorporated in the OA equipment or the like in units of software modules. Will be able to

In addition, the user can pay an appropriate usage fee only for the used function.

In addition, it is possible to flexibly cope with a change in the billing method by replacing or upgrading the software module unit, expanding the functions of the product itself, and supporting individual functions.

Specifically, conventionally, since the function is charged for the function, the problem that the same charge is made even when different software modules are used in the same function is solved, and the function to be used is solved. Regardless (copy, fax,
Multifunction devices such as printers have many functions), and accounting can be managed in software module units.

According to a second aspect of the present invention, in the software module billing system according to the first aspect, each of the software modules is a module identifier (hereinafter referred to as a module identifier) registered in advance for each software module. ID) 51, and has a data structure including unit price information 54 which is a charge unit per use of the module, and the specification of the software module based on the module ID 51 and the unit price information 54 included in the data structure. And a charging module for the software module that executes the charging function for the software module based on the module ID 51 and the unit price information 54.

According to the invention of claim 2, according to claim 1,
In addition to the effects described in (1), by using the unit price information 54 or the module ID 51, the charge according to the use value of the device is performed by managing the charge for the software incorporated in the OA device or the like in units of software modules. Will allow users to pay.

In addition, by using the unit price information 54 or the module ID 51, the user can pay an appropriate usage fee only for the used function.

In addition, by replacing or changing the unit price information 54 or the module ID 51, it is possible to flexibly cope with a change in the billing method by replacing or upgrading the software module unit, expanding the functions of the product itself, and supporting individual functions. Will be able to

Specifically, conventionally, since the function is charged for the function, the problem that the same charge is made even when different software modules are used in the same function is solved. If the module ID 51 is the same, regardless of the function used (copy, fax,
Multifunction devices such as printers have many functions), and accounting can be managed in software module units.

According to a third aspect of the present invention, in the billing system for a software module according to the first or second aspect, the user uses the software module for controlling printing or the software module for controlling reading. At the time, the service center 1
The 0 side is a software module billing system that executes a billing process to the user side according to the result of the billing function executed by the software module.

According to the invention described in claim 3, according to claim 1
In addition to the effect described in 2 above, by charging based on the execution status of the software module using the unit price information 54 or the module ID 51, the charge management is performed for the software incorporated in the OA device or the like in units of software modules. By doing so, the user can pay a fee corresponding to the use value of the device.

In addition, by charging based on the execution status of the software module using the unit price information 54 or the module ID 51, the user can pay an appropriate usage fee only for the used function.

In addition, by replacing or changing the unit price information 54 or the module ID 51, it is possible to flexibly cope with a change in the billing method by replacing or upgrading the software module unit, expanding the functions of the product itself, and supporting individual functions. Will be able to

Specifically, conventionally, since the function was charged for the function, the problem that the same charge was made even when different software modules were used in the same function was solved. If the module ID 51 is the same, regardless of the function used (copy, fax,
Multifunction devices such as printers have many functions), and accounting can be managed in software module units.

According to a fourth aspect of the present invention, a hardware module mounted on the image input / output device 12 is associated with the software module.
A billing system for a software module that manages the usage status of the hardware module based on the usage status of the software module corresponding to the hardware module.

According to the fourth aspect of the present invention, since the hardware module is charged by software, a counter for charging is not required. In addition, since software management is used, version upgrades are simplified.

The unit price information 54 or the module ID 5
By executing the charging of the hardware module according to the execution status of the software module using
By performing charge management for software incorporated in OA equipment or the like in units of software modules, a user can pay a fee corresponding to the utility value of the device.

In addition, by charging the hardware module according to the execution status of the software module using the unit price information 54 or the module ID 51, the user can pay an appropriate usage fee only for the used function. become able to.

In addition, by replacing or changing the unit price information 54 or the module ID 51, the charging method is changed by replacing or upgrading the software module unit or the hardware module unit, and the function extension or individual function of the product itself is changed. It becomes possible to respond flexibly to the response.

Specifically, conventionally, since the function is charged for the function, the problem that the same charge is made even when different software modules are used in the same function is solved. If the module ID 51 is the same, regardless of the function used (copy, fax,
Multifunction devices such as printers have many functions), and accounting can be managed in software module units corresponding to hardware modules.

According to a fifth aspect of the present invention, in the software module billing system according to any one of the first to fourth aspects, the billing process of the software module that centrally manages the cumulative processing of the billing at a network destination. System.

According to the invention described in claim 5, according to claim 1,
In addition to the effects described in any one of (1) to (4), by performing cumulative processing management of charging for each user remotely,
It is possible to separate the charging information of the module from the accumulated fee, and it is possible to flexibly cope with the fee form according to the usage situation of the user due to function expansion or version upgrade.

According to a sixth aspect of the present invention, in the billing system for software modules according to any one of the first to fifth aspects, the image processing is performed in response to a usage fee notification request from the service center 10. I / O device 1
2 is a software module billing system for adding usage fees for all the software modules used in the service center 2 and notifying the service center 10 of the sum.

According to the invention of claim 6, according to claim 1,
In addition to the effects described in any one of (1) to (5), the charge information of the module can be separated from the accumulated charge by remotely requesting the notification of the charge for the cumulative processing management of the charge for each user. As a result, it is possible to flexibly cope with a fee form according to a user's use situation by function expansion or version upgrade.

[0041]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is a block diagram for explaining one configuration of a system environment (network environment 14) of a computer system for realizing a billing system applying a billing system for software modules according to the present invention. is there.

In the billing system for software modules according to the present embodiment, the software for controlling the hardware modules mounted on the OA equipment is divided into a plurality of software modules, and the software modules are operated in cooperation with each other to execute the image input / output device 12. Each of the software modules has a charging function for accumulating a usage fee according to the usage value or usage status of the software module.

More specifically, the OA equipment includes a feeder unit for feeding a document to be read and sequentially setting the document in a reading device, a scanner unit for executing reading, a storage device for storing read image data, and printing. A copier (server) including hardware modules such as a paper feed tray unit that feeds paper and sets it in a writing device, a plotter unit that executes writing, and a paper discharge unit that distributes and places printed paper. A) Image input / output device 12 such as 122, fax, printer (server B) 121, scanner 123, etc.
There is. Each device of the image input / output device 12 includes a software module (not shown), and achieves one function by combining the software modules. For example, in the copying machine 122, when electronic sorting is performed, a software module for storing read image information in a memory, a software module for reading from the memory, a software module for editing, a software module for actually forming an image, and the like are combined into one. To achieve the function of one electronic sort copy. Below,
The description will proceed as the image input / output device 12.

Conventionally, the image input / output device 12 such as a copier (server A) 122, facsimile, printer (server B) 121, scanner 123, and personal computer (PC) 124 have been used in a stand-alone one-to-one connection. As shown in FIG. 1, in recent years, usage methods connected to the network environment 14 have been increasing.

In the billing system for software modules according to the present embodiment, the accumulating process of billing is centrally managed at the network destination.

Specifically, in this embodiment, a service center 10 for managing software modules is provided outside of the existing system environment.

That is, the service center 10
As shown in the figure, a storage device 102 for storing a management database for managing software version upgrades, billing, etc., and a personal computer (PC) 101 for managing software modules using the storage device 102 are provided. 14 through remote control via each device 12 (121, 122,
123, 124, etc.).

FIG. 2 is a diagram showing one configuration of hardware of the system environment of FIG. FIG. 2 shows only the copying machine 122 of the image input / output device 12, and the other printers 1
21, the scanner 123 is omitted. In the present embodiment, the service center 10 (see FIG. 1)
Has the role of. This broker 22 may be in each image input / output device 12.

First, the hardware configuration of the image input / output device 12 will be described.

As shown in FIG. 2, a processor (CPU) 201 controls the entire apparatus. Under the control, a ROM 209, a RAM 210, and an NVRAM 21 are controlled.
1, operation panel 202 and panel control unit 205, scan / print engine 203 and engine control unit 206, storage device 204 and disk driver 207, communication control unit 2
08, the modem 212 is connected.

The ROM 209 stores program codes, fonts, and other static data.

The RAM 210 shown in FIG. 2 is used as a temporary storage location.

The NVRAM 211 shown in FIG. 2 stores nonvolatile data.

The operation panel 202 and the panel control unit 205 shown in FIG. 2 control an interface with a user.

Scan / print engine 2 shown in FIG.
03 and the engine control unit 206 execute reading of a paper document and printing on transfer paper as an input / output unit of image data.

The storage device 204 and the disk drive 207 shown in FIG. 2 store a large amount of image data and the like and are used as a storage location of a database.

The communication control unit 208 shown in FIG. 2 is connected to the network environment 14 such as Ethernet, and enables communication with an external device (for example, the broker 22 or the personal computer (PC) 101).

The modem 212 shown in FIG. 2 is connected to a public line (specifically, a telephone line or an ISDN line), and enables communication with an external device.

Next, the hardware configuration of the broker 22 will be described.

As shown in FIG. 2, the broker 22 maintains the function information and management information of the image input / output device connected to the network environment 14, and the client (here, P
C124) and establishes a connection between the server (here, the image input / output device 12).

The broker 22 includes a CPU 223, a ROM 2
24, a RAM 225, a communication control unit 222, and a storage device 102 for storing a management database. The storage device 102 may be located on either the PC 101 or the image input / output device 12.

FIG. 3 shows a copying machine 122 as an example of the image input / output device 12 in the hardware configuration of FIG.
1 shows one configuration of software incorporated in the software.

As shown in FIG. 3, the configuration of software incorporated in the image input / output device 12 is roughly divided into an application layer 30, a kernel layer 32,
It has a four-layer structure of a driver layer 34 and a hardware layer 36.

The application layer 30 shown in FIG. 3 is a layer for forming an application such as a copy / fax / printer / scanner.

The document manager 302 shown in FIG.
Is a functional block that is central to an application that handles documents according to scenarios such as copy, fax, printer, and scanner.

The service manager 303 shown in FIG.
This is a functional block that is required in common when handling documents, and manages and executes various services.

The device manager 304 shown in FIG.
A function block that determines the operation of a physical device such as a scanner, a plotter, and an image bus, and manages and executes various devices.

The operation manager 30 shown in FIG.
A control unit 1 controls an operation panel attached to the apparatus, and displays a button, notifies a button operation, notifies an alert, and the like.

The database manager 305 shown in FIG.
Maintains and manages permanent data such as fonts, fixed forms, fax reception histories, and device usage histories.

The database manager 305 also maintains and manages billing information of each software module. When the device, for example, the copying machine 122 has a function as a broker, the maintenance and management of the accumulated charge can also be performed.

The program factory 306 shown in FIG.
Performs initialization for executing a program from a software module.

That is, the program factory 306
Is to develop a statically existing software module on a RAM (generation of an instance in object-oriented programming) and receive an appropriate message (method call in object-oriented programming) to make it operable.

The kernel layer 32 shown in FIG.
(Operating system) is incorporated as a kernel to abstract various devices,
Execution process 322, file system 323, socket 324, virtual machine 325 (execution management device 325)
1, a mode management device 3252). The kernel layer 32 mediates between the application layer 30 and the driver layer 34.

The application layer 30 shown in FIG. 3 operates by making a system call to the kernel layer 32.

The driver layer 34 shown in FIG. 3 is a group of functional blocks for executing control for driving various hardware, and includes a memory management driver 341, a process management driver 342, a file management driver 343, a network management driver 344, an integrated copy driver 345, a blocking device driver 346, a page device driver 347, and the like.

The hardware layer 36 shown in FIG. 3 is a set of controllable resources existing in the image input / output device 12, and includes a RAM 210, a ROM 209, and a storage device 204.
And NVRAM 211, network interface 208, scanner 203, image bus 203, plotter 2
It is equipped with 03 mag.

FIG. 4 shows the relationship between a carriage operation control software module for image reading incorporated in the image input / output device 12 such as a copying machine or a scanner.

ScannerControl shown in FIG.
The software module 42 controls the Carriage software module 44, that is, gives an instruction to the Carriage software module 44 according to the resolution and the read range.

The Carrier software module 44 shown in FIG. 4 instructs the Motor software module 48 on the moving speed and the like, and instructs the Lamp software module 46 on / off (lighting / off).
A software module for executing and monitoring the carriage operation.

The Motor software module 48 shown in FIG. 4 is a software module for driving a stepping motor and the like.

The Lamp software module 46 shown in FIG. 4 is a software module for turning on and off an exposure lamp and the like.

Next, an embodiment of the data structure of the software module will be described with reference to the drawings.

Each of the software modules of this embodiment has a data structure including a module ID 51 which is a module ID registered in advance for each software module, and a unit price information 54 which is a charging unit per use of the module. doing.

Thus, the billing system for software modules according to the present embodiment manages the specifications of the software modules based on the module ID 51 and the unit price information 54 included in the data structure.
It is characterized in that a charging function for the software module is executed based on the unit information 51 and the unit price information 54.

FIG. 5 shows an example of a data structure for each software module.

In FIG. 5, the module ID 51 is
An arbitrary identifier registered in advance for each software module. Usually, it is a 6-digit numerical value or the like, and is a number that is centrally managed by the vendor that is the device provider.

The vendor manages the specifications of the software module from the module ID 51.

The name information 52 shown in FIG. 5 is the name of the software module. Usually, for example, "Carri
age ”and the like.

The version information 53 shown in FIG. 5 is a version corresponding to the module ID 51. Usually 3
It is a digit number, and is recognized as version 3.01, for example, "301".

The unit price information 54 shown in FIG. 5 is a fee required for charging, which is charged for one use of the software module.

The usage fee information 55 shown in FIG. 5 is the current usage fee, and the unit price is added by one use.

The attribute value information 56 unique to the individual module shown in FIG. 5 is data necessary for each software module.

Next, a fee charging method executed by each of the software modules will be described with reference to the drawings.

In the billing system for software modules according to the present embodiment, when a user uses a software module for controlling printing or a software module for controlling reading, the service center 10 uses the billing function of the billing function executed by the software module. It is characterized in that charging processing is performed on the user side according to the result.

Further, the billing system for software modules according to the present embodiment further associates the hardware modules mounted on the image input / output device 12 with the software modules to further reduce the usage status of the hardware modules. It is characterized in that the management is performed based on the usage status of the software module corresponding to.

The following shows a specific event trace when the usage fee is added.

FIG. 6 shows an event trace when the usage fee is added using the software module having the data structure of FIG. 5 in the charging process of FIG.

More specifically, Mov for controlling the carriage
When the e-method S601 is activated by the ScannerControl software module 42, C
MotorStart method S6 in which the arrange software module 44 controls the carriage motor
Activate 02.

As a result, the AddCharge method S603 is activated, and the accounting process is executed. This Ad
The dCharge method S603 corresponds to an embodiment of the third aspect.

When the Carriage software module 44 activates the ON method S604 for controlling the lamp to turn on, the Lamp software module 46
Activate the ddCharge method S605 to execute the accounting process.

Subsequently, the Motor software module 48 instructs the completion of the control of the carriage motor.
orComplete method S606 is activated, and thereafter, OFF method S607 for turning off the lamp
Is activated, and the Carrier software module 44 instructs MoveCom to instruct the completion of the carriage control.
Activate the plete method S608.

As described above, by charging based on the execution status of the software module using the unit price information 54 and the module ID 51, it is possible to manage the charging of the software incorporated in the OA equipment or the like on a software module basis. In this way, the user can pay a fee according to the usage value of the device.

In addition, by charging based on the execution status of the software module using the unit price information 54 and the module ID 51, the user can pay an appropriate usage fee only for the used function.

Further, by replacing or changing the unit price information 54 or the module ID 51, it is possible to flexibly cope with a change in the billing method by replacing or upgrading the software module unit, expanding the functions of the product itself and supporting individual functions. Will be able to

[0105] Specifically, conventionally, since the function was charged for the function, the problem that the same charge was made even when different software modules were used in the same function was solved. If the module ID 51 is the same, regardless of the function used (copy / fax /
Multifunction devices such as printers have many functions), and accounting can be managed in software module units.

That is, in the data structure of the software module, the Lamp software module 4
6 and a Motor software module 48 corresponding to hardware exist as software modules, and the billing management of such software modules also corresponds to an embodiment of claim 4.

As described above, by charging the hardware module by software, a counter for charging is not required. In addition, since software management is used, version upgrades are simplified.

The unit price information 54 or the module ID 5
By executing the charging of the hardware module according to the execution status of the software module using
By performing charge management for software incorporated in OA equipment or the like in units of software modules, a user can pay a fee corresponding to the utility value of the device.

In addition, by executing the charging of the hardware module according to the execution status of the software module using the unit price information 54 or the module ID 51, the user can pay an appropriate usage fee only for the used function. become able to.

In addition, by replacing or changing the unit price information 54 or the module ID 51, the charging method is changed by replacing or upgrading the software module or the hardware module, and the functions of the product itself are expanded and individual functions are changed. It becomes possible to respond flexibly to the response.

Specifically, conventionally, since the function was charged for the function, the problem that the same charge was made even when different software modules were used in the same function was solved. If the module ID 51 is the same, regardless of the function used (copy / fax /
Multifunction devices such as printers have many functions), and accounting can be managed in software module units corresponding to hardware modules.

FIG. 7 shows an event trace when the usage fee is added using the software module having the data structure of FIG. 5 in the charging process of FIG. This embodiment shows a case where the broker is located in the service center.

The software module charging system according to the present embodiment adds the usage fee for all software modules used in the image input / output device 12 in response to a usage fee notification request from the service center 10. The feature is that notification is made to the service center 10 side.

Hereinafter, a specific operation will be described using an event trace.

When the service center 10 activates the fee inquiry method S701 for requesting the notification of the usage fee, the service manager 303 adds the usage fee of all the software modules in the image input / output device 12 to the GetAllCharge method S702.
Activate.

In response, the Carriage software module 44 executes the SumCharge method S7.
Activate 03 and execute the charge processing of the usage fee of the Carriage software module 44.

[0117] After the completion, the Carriage software module 44 reduces the usage fee of the Carriage software module 44 to GetAllChar.
Add to the charge data in the get method S702 and use the charge data to obtain the GetAllCharge method S70
Activate 4.

In response to this, the Motor software module 48 executes the GetAllCharge method S
In response to the activation of 704, the SumCharge method S705 is activated to execute the charge processing of the usage fee of the Motor software module 48.

After the completion, the Motor software module 48 adds the usage fee of the Motor software module 48 to the fee data in the GetAllCharge method S704, and activates the GetAllCharge method S706 using the fee data.

In response to this, the Lamp software module 46 executes the GetAllChange method S7
06 in response to the activation of the SumCharge method S
Activate 707 to activate the Lamp software module 4
The charge processing of the usage fee of No. 6 is executed.

Waiting for the end, the Lamp software module 46 starts the Lamp software module 4
GetAllCharge method S7
Add to the charge data in 06 and use the charge data to
Activate the tAllCharge method S708.

The same billing process (SumCharge method S70) is performed for other software modules.
9) is executed, and the accumulated usage fee data (charging information) is stored in the AllChargeAdded method S71.
0 is returned to the service manager 303 by activating 0.

The service manager 303 sends an AllCh
The charge method S711 is activated using the added usage fee data (charging information) received from the "argeAdded" method S710, and the service center 10 is notified of the added usage fee data (charging information). In FIG. 7, the same billing process (SumCharge method S709) is executed for each software module.
Charge data may be sent to the mCharge method S709 to perform billing processing.

In the following mechanism, a software module to which a fee is to be added is registered as a billing software module in the broker, and the event is propagated as a chain to all the registered software modules. Is added.

Further, as a method of realizing the fifth and sixth aspects,
In addition, each module ID 51 is managed by the service center 10, and the usage fee can be taken out by specifying the module ID 51. In that case, registration management as a billing software module is performed in the service center 10, and the service center 10 inquires the fee for each software module and adds all the charges.

As described above, since each software module has information on the price and the number of times of use of the software module itself, it is possible to separate the charge information of the module from the charge for the accumulation processing of the charge for each user. This makes it possible to flexibly cope with a fee form according to the user's use situation by function expansion or version upgrade.

As described above, according to the present embodiment, the charge according to the use value of the device can be paid by the user by managing the charge for the software incorporated in the OA equipment or the like on a software module basis. You will be able to pay.

In addition, the user can pay an appropriate usage fee only for the function used.

In addition, it is possible to flexibly cope with a change in the billing method by replacing or upgrading the software module unit, expanding the functions of the product itself, and supporting individual functions.

[0130] Specifically, conventionally, since the function was charged for the function, the problem that the same charge was made even when different software modules were used in the same function was solved, and the function to be used was solved. Regardless (copy fax
Multifunction devices such as printers have many functions), and accounting can be managed in software module units.

[0131]

According to the first or second aspect of the present invention, the charge according to the use value of the device is managed by managing the charge for the software incorporated in the OA equipment or the like in units of software modules. Users will be able to pay.

In addition, the user can pay an appropriate usage fee only for the function used.

In addition, it is possible to flexibly cope with a change in the billing method by replacing or upgrading the software module unit, expanding the functions of the product itself, and supporting individual functions.

[0134] Specifically, in the past, since the function was charged for the function, the problem that the same charge was made even if different software modules were used in the same function was solved. Regardless (copy fax
Multifunction devices such as printers have many functions), and accounting can be managed in software module units.

According to the invention described in claim 3, according to claim 1
In addition to the effects described in 2 above, by charging based on the execution status of the software module using the unit price information or the module ID, the charge management is performed for the software incorporated in the OA device or the like in units of the software module. This allows the user to pay a fee according to the usage value of the device.

In addition, unit price information or module I
By billing according to the execution status of the software module using D, the user can pay an appropriate usage fee only for the used function.

In addition, unit price information or module I
By exchanging or changing D, it becomes possible to flexibly cope with the change of the billing method by exchanging software modules or upgrading the version, and to extend the functions of the product itself or cope with individual functions.

According to the fourth aspect of the invention, the hardware module is charged by software, so that a counter for charging is not required. In addition, since software management is used, version upgrades are simplified.

[0139] In addition, by performing billing of a hardware module according to the execution status of a software module using unit price information or a module ID, billing management can be performed for each software module for software incorporated in an OA device or the like. This allows the user to pay a fee according to the usage value of the device.

In addition, unit price information or module I
By executing billing of the hardware module according to the execution status of the software module using D,
Users will be able to pay appropriate usage fees only for the functions used.

In addition, unit price information or module I
By replacing or changing D, it becomes possible to flexibly respond to a change in the billing method by replacing or upgrading the software module unit or the hardware module unit, and to expand the function of the product itself or support individual functions. .

According to the invention described in claim 5 or 6,
In addition to the effects described in any one of claims 1 to 4,
By remotely managing the cumulative processing of billing for each user, it is possible to separate the billing information of the module from the billing fee. It is possible to respond flexibly.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating one configuration mode of a system environment (network environment) of a computer system that implements a billing processing method to which a billing system for software modules according to the present invention is applied.

FIG. 2 is a block diagram showing a configuration of the system environment shown in FIG.
1 and a hardware configuration including an image input / output device that receives a service provided by a software module.

FIG. 3 shows a configuration of software incorporated in an image input / output device that receives a service provided by a software module in the hardware configuration of FIG. 2;

FIG. 4 shows one form of accounting processing for a software module for controlling carriage operation for image reading incorporated in an image input / output device such as a copying machine or a scanner.

FIG. 5 is an example of a data structure for each software module.

6 shows an event trace on the image input / output device side when a usage fee is added using the software module having the data structure of FIG. 5 in the charging process of FIG. 4;

FIG. 7 shows an event trace on the service center side according to the image input / output device when a usage fee is added using the software module having the data structure of FIG. 5 in the charging process of FIG.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 10 ... Service center (vendor) 12 ... Image input / output device 14 ... Network environment 22 ... Broker 30 ... Application layer 32 ... Kernel layer 34 ... Driver layer 36 ... Hardware layer 42 ... Scanner Control software module 44 ... Carriage software module 46 ... Lamp Software module 48 Motor software module 51 Module identifier (module ID) 52 Name information 53 Version information 54 Unit price information 55 Usage fee information 56 Attribute value information unique to an individual module

Claims (6)

[Claims] 1. A software module for controlling a hardware module mounted on an image input / output device into a plurality of software modules, and operating the software modules in cooperation to control the image input / output device. A charging system for software modules, wherein each of the software modules has a charging function for accumulating a usage fee according to the usage value or usage status of the software module. 2. Each of the software modules comprises:
A module identifier pre-registered for each software module, a data structure including unit price information for identifying a unit price that is a charging unit per use of the module, and a module identifier included in the data structure; The software module according to claim 1, wherein the software module manages specifications of the software module based on the unit price information, and executes the charging function for the software module based on the module identifier and the unit price information. Billing system. 3. When the user uses the software module for controlling printing or the software module for controlling reading, the service center side determines the user in accordance with the result of the accounting function executed by the software module. The billing system for software modules according to claim 1, wherein a billing process is performed on the side. 4. A hardware module mounted on the image input / output device is associated with the software module, and a usage status of the hardware module is changed to a usage status of the software module corresponding to the hardware module. A billing system for a software module, wherein the billing system is managed on the basis of the software module. 5. The charging system for a software module according to claim 1, wherein the accumulating process of the charging is centrally managed at a network destination. 6. The method according to claim 1, further comprising: adding a usage fee for all of the software modules used in the image input / output device in response to a usage fee notification request from the service center, and notifying the service center. The billing system for software modules according to claim 1, wherein: