JP2006285774A - Service generating device, service processing system, processing method, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve license management when providing network service. <P>SOLUTION: A service generating device, or the like comprises a service generation means for generating service from a service source; an installation destination storage means for storing one or a plurality of installation destinations; a license generation means for generating a license corresponding to the installation destination; an installable binary generation means for generating an installable binary from the service and the license; and an installation means for installing the installable binary to the installation destination. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an apparatus and a system for generating and executing a service so as to conform to a license.

Traditionally, when installing software, programs, or services (collectively referred to below as services) on a device or executing a service on a device, the service is installed with a license embedded in the service. There is a technology that determines whether it can be installed on the device or whether a service can be executed and does not permit installation or execution unless it has a proper license.
For example, Patent Documents 1 and 2 are examples of such a technique.

A license may be granted to a person who purchased the service, or may be granted to a device that executes the service.
In the latter case, variations may be made so that the license is unique to the device ID. Simply, the device ID is included in the license. In this way, at the time of installation or execution, it is checked whether the device ID included in the license matches the own device ID, and control is performed such that installation or execution is possible only if they match. Thus, installation or execution prohibition on a device for which a license has not been issued is achieved.
In order to prevent unauthorized copying and falsification of licenses, encryption technology is generally used.

The configuration of the prior art is shown in the block diagram of FIG.
A service is installed from the management PC 103 to the MFP 1 102a and the MFP 2 102b. As for services, a service program 1 302a to be installed on the multifunction peripheral 1 102a and a service program 2 302b to be installed on the multifunction peripheral 2 102b are stored in the CD-ROM 301, which is read and installed by the management PC 103. . The service program 1 302a includes a license 1 303a corresponding to the MFP 1 102a. The service program 2 302b includes a license 2 303b corresponding to the MFP 2 102b.
The two service programs provide the same service.

  When the service program is installed from the management PC 103, the operation is performed as described above, and the installation is performed while checking the license compatibility.

As described above, since the license generation is a key technology for preventing unauthorized use, it is strictly managed. Usually, a license is generated by collecting information on devices to be installed or executed on a service provider site, and a service incorporating the generated license is provided to a customer.
By doing so, safety is ensured.

JP 2004-46606 A JP 2004-135325 A

However, the above conventional techniques have the following problems.
In other words, this is a license granting method when a service is dynamically generated on a device. When a service is dynamically generated on a device, the license does not exist because the service does not exist before the service is generated. The problem is how to license such services.

If the service is to be installed not only on the device itself but also on other devices, the licensing method in this case is also a problem.
Also, once a license is granted, it is meaningless unless the service provider knows it. If a license is created or deleted dynamically, it must leave a trace that it was there. It must be possible for the service provider to know exactly such information as to which device the license is issued to and how much the device is using the service. This is because it is a matter related to billing.
However, even if the service provider's site and the device are connected via a network, it does not mean that the information needs to be sent from the device to the site. It is desired that the user can grasp that the license is properly granted.

In order to broaden the scope of application, it should not be a requirement that the service provider's site and equipment are connected to the network.
In addition, license information and service usage information must be difficult to change by unauthorized means.

If license management is performed centrally at the service provider's site, licenses may be issued for a large number of devices sold to the entire world, increasing the burden on the site. Therefore, it is also desirable to distribute license issuance in order to reduce the burden on the site.
For example, it is preferable that the service provider site manages only the number of licenses issued to each user site, and performs license management so that the device does not exceed the number of licenses at each user site.

  The present invention has been made in view of the above problems. When a service is dynamically generated on a device, a license is dynamically generated even if a license is not generated in advance, and a license authentication mechanism is used. It is an object of the present invention to provide a service generation device, a service processing system, a processing method, a program, and a recording medium that enable a service to be installed or executed.

  The service generation device of the present invention includes a service generation unit that generates a service from a service source, an installation destination storage unit that stores one or more installation destinations, a license generation unit that generates a license according to the installation destination, An installable binary generation unit configured to generate an installable binary from the service and the license; and an installation unit configured to install the installable binary in the installation destination.

  The service processing system of the present invention includes a service generation device that generates a service from a service source, and a service execution device that executes the service, wherein the service generation device generates a service from the service source. Generating means; installation destination storage means for storing one or a plurality of installation destination service execution apparatuses; license generation means for generating a license corresponding to the installation destination; and generating an installable binary from the service and the license An installer for inputting the installerable binary, and an installer for installing the installerable binary in the installation destination. When the license condition determining means for determining whether the license conditions of the installable binary, the license condition of the installerable binary is compatible with the self apparatus, and the license conformity determining means are determined to be suitable for the self apparatus And installation means for installing the installable binary service.

  The service generation device of the present invention includes a service generation unit that generates a service from a service source, an installation destination storage unit that stores one or more installation destinations, a license generation unit that generates a license according to the installation destination, An installable binary generating means for generating an installable binary from the service and the license; an installation means for installing the installable binary in the installation destination; and a service usage status storage for storing a service usage status sent from the installation destination. And information output means for outputting the information stored in the installation destination storage means or the service usage status storage means to the outside.

  The service processing system of the present invention includes a service generation device that generates a service from a service source and a service execution device that executes the service, wherein the service generation device generates a service from the service source. Generating means; installation destination storage means for storing one or a plurality of installation destination service execution apparatuses; license generation means for generating a license corresponding to the installation destination; and generating an installable binary from the service and the license Installerable binary generation means for performing installation, installation means for installing the installerable binary in the installation destination, and service usage status storage means for storing service usage status sent from the installation destination And information output means for outputting the information stored in the installation destination storage means or the service usage status storage means to the outside, and the service execution device includes an installable binary input means for inputting the installable binary A license compatibility determination unit that determines whether or not a license condition of the installerable binary is compatible with the device; and the license compatibility determination unit determines that the license condition is compatible with the device. An installation unit that installs a binary service, and a service usage status transmission unit that transmits a service usage status of the device itself to the service generation device.

  The service generation method of the present invention includes a service generation step of generating a service from a service source, an installation destination storage step of storing one or more installation destinations, a license generation step of generating a license according to the installation destination, An installable binary generation step of generating an installable binary from the service and the license; and an installation step of installing the installable binary in the installation destination.

  The processing method of the service processing system according to the present invention includes a processing method of a service generation device that generates a service from a service source, and a processing method of a service execution device that executes the service. The processing method of the generation apparatus includes a service generation step of generating a service from a service source, an installation destination storage step of storing one or a plurality of installation destination service execution devices, and a license for generating a license corresponding to the installation destination A process for generating the installable binary from the service and the license; and an installation process for installing the installable binary in the installation destination. The method includes an installable binary input step for inputting the installable binary, a license suitability determining step for determining whether a license condition of the installable binary is compatible with a self-apparatus, and the license suitability determining step. And an installation step of installing the installable binary service when it is determined that the license condition is compatible with the device.

  The service generation method of the present invention includes a service generation step of generating a service from a service source, an installation destination storage step of storing one or more installation destinations, a license generation step of generating a license according to the installation destination, An installable binary generation step of generating an installable binary from the service and the license; an installation step of installing the installable binary in the installation destination; and a service usage status storage for storing a service usage status sent from the installation destination And an information output step of outputting the information stored in the installation destination storage step or the service usage status storage step to the outside.

  The processing method of the service processing system according to the present invention includes a processing method of a service generation device that generates a service from a service source, and a processing method of a service execution device that executes the service. The processing method of the generation apparatus includes a service generation step of generating a service from a service source, an installation destination storage step of storing one or a plurality of installation destination service execution devices, and a license for generating a license corresponding to the installation destination Sent from the installation destination, a creation step, an installerable binary generation step of generating an installable binary from the service and the license, an installation step of installing the installerable binary in the installation destination, and A service usage status storage step for storing service usage status; and an information output step for outputting information stored in the installation destination storage step or the service usage status storage step to the outside. An installable binary input step for inputting the installable binary, a license suitability determining step for determining whether a license condition of the installable binary is compatible with the device, and the license suitability determining step. When it is determined that the condition is compatible with the own device, an installation step of installing the installable binary service and a service usage status transmission step of transmitting the service usage status of the own device to the service generation device are provided.

By providing the above means, the present invention has the following effects.
That is, when the service is dynamically generated on the device, the license can be dynamically generated even if the license is not generated in advance, and the service can be installed or executed using the license authentication mechanism.
By doing so, the same license authentication mechanism as that used when installing a static service in the device can be used.

Also, a license can be generated not only for the device itself but also for other devices, and the service can be installed or executed.
Further, the service provider or the user can know the license information generated dynamically and the usage status information of the service installed or executed using the license accurately and safely.
The acquisition of the information can be realized even if the service provider site and the device are not connected to the network.

Further, it is difficult to change license information and service usage status information by unauthorized means.
In addition, license management is not performed centrally at the service provider site, but license management is performed on the device, thereby achieving distributed license management and reducing the burden on the service provider site.

Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a configuration of a service processing system according to the present invention. In FIG. 1, 101 is a center multifunction peripheral, 102 is a multifunction peripheral, and 103 is a management PC, which are connected to each other via a network.

  The center multifunction peripheral 101 plays a central role in the configuration of the present invention, which generates services and licenses and manages licenses. A service is installed in the MFP 102 and the service is executed. The service usage status in the MFP 102 is reported to the center MFP 101.

The management PC 103 installs a service source to the center multifunction peripheral 101, designates an installation destination of a dynamically generated service, or creates a statically constructed service as the center multifunction peripheral 101 or the multifunction peripheral 102. Or install against.
The internal configuration of the center multifunction machine 101 or the multifunction machine 102 will be described with reference to the block diagram of FIG.

  In the figure, a center multifunction machine 101 or a multifunction machine 102 includes a central processing unit (hereinafter referred to as CPU) 201 that controls the entire device, a ROM 202 that stores various operation programs in a readable manner, and a temporary program operation. RAM 203 used for storing various values, timer 204 for measuring various times, display 205 for displaying various setting menus and images, scanner 206, printer 207, various operation buttons 208, and non-volatile for storing various setting data files A flash ROM 209 which is a volatile memory, a network I / F 210 which is an interface for connecting to the outside of the device, a hard disk (hereinafter referred to as HD) 211 for storing service sources and binaries, various operation programs, and various setting data files Become

  The source, binary, and license information of the service described in the present invention do not have to be included in some of the above-mentioned recording media, but are stored in the HD 211 in this embodiment. Shall.

Next, the hierarchy of software operating on the center multifunction peripheral 101 will be described with reference to FIG.
First, hardware 1301 exists in the lowest layer. In addition, an operating system (hereinafter referred to as OS) 1302 for controlling the hardware 1301 exists. Various programs operating on the OS 1302 exist on the OS 1302.
For example, a Java (registered trademark) virtual machine (Java (registered trademark) is a trademark or registered trademark of Sun Microsystems Inc. in the United States and other countries, hereinafter referred to as Java (registered trademark) VM) 1303. Exists.

The Java (registered trademark) VM 1303 can execute a Java (registered trademark) bytecode which is a kind of intermediate code format. Since Java (registered trademark) bytecode is an intermediate code, the degree of device dependency is low, and it is suitable to be sent to another device and executed there.
A service 1320 described in the present embodiment is realized by a Java (registered trademark) bytecode, and operates on the Java (registered trademark) VM 1303.

Furthermore, there are various compilers and tools that run on the OS 1302, and these will be described with reference to FIG.
Next, the flow of generating a service will be described with reference to the block diagram of FIG.
Here, a Java (registered trademark) source 410 and a WSDL source 411 are cited as service sources.

  WSDL is an abbreviation for Web Services Description Language, and is a service description language of a Web service protocol stack. This is described in XML (extensible Markup Language) and is platform independent. The WSDL source 411 describes a public interface of a certain web service. If the WSDL source 411 is interpreted, compiled, and put into a form that can operate on the device, a program incorporating the form can access the Web service. Such a mechanism can increase the flexibility of the means for accessing the Web service. In the present embodiment, the WSDL source 411 is finally compiled into the Java (registered trademark) class 412, but the present invention is not limited to this, and may be another execution format.

The Java (registered trademark) source 410 stored in the HD 211 is compiled into a Java (registered trademark) class file 412 by the Java (registered trademark) compiler 401. The Java (registered trademark) class file 412 is described in Java (registered trademark) bytecode, and the Java (registered trademark) VM 1303 can execute this.
Note that the CPU 201 is the main operating element of software such as the Java (registered trademark) compiler 401 and the Java (registered trademark) VM 1303. In the following, the same case will not be explained.

There are two routes to which the WSDL source 411 stored in the HD 211 is converted.
First, after the WSDL2Java (registered trademark) tool 402 converts the WSDL source 411 into the Java (registered trademark) source 410, the Java (registered trademark) compiler 401 converts the Java (registered trademark) source 410 into the same manner as described above. This is a route for conversion into a Java (registered trademark) class file 412.

The other is a route in which the WSDL compiler 403 directly converts the WSDL source 411 into a Java (registered trademark) class file 412. There is no need to have both routes, as long as either one is supported. This shows the variety of transformations.
Finally, both the Java (registered trademark) source 410 and the WSDL source 411 are converted into a Java (registered trademark) class file 412.

Next, the archiver 404 generates a Jar file 417 by combining the Java (registered trademark) class file 412, the resource file 415 and the manifest file 416. The Jar file 417 is a file in a format that can be executed by the Java (registered trademark) VM 1303.
Here, the resource file 415 or the manifest file 416 may be statically given from the beginning or may be dynamically created. When a service is created in the Java (registered trademark) language, these files can be made a part of the function of the service.

Next, a license file is generated and stored in the HD 211 according to the device to which the service is installed.
Finally, the archiver 404 collects the Jar file 417 and the license file 413 to create an installable binary 414.

  The generation of the Jar file 417 is not essential. This is because the Java (registered trademark) VM 1303 can execute the service even if it is not put together in the format of the Jar file 417. The Java (registered trademark) class file 412, the resource file 415, the manifest file 416, and the license file 413 may be collected by the archiver 404 to create the installable binary 404.

  Hereinafter, the term “service” means a Jar file 417 or a combination of a Java (registered trademark) class file 412, a resource file 415, and a manifest file 416 in terms of an executable format unit. In the meaning of the unit, the installerable binary 414 is indicated.

  The service source indicates a Java (registered trademark) source 410, a WSDL source 411, a resource file 415, or a manifest file 416. However, since the Java (registered trademark) source 410 and the WSDL source 411 are important as the role of the service source in the present invention, these are mainly handled as the service source.

Next, the operation of the service processing system will be described using a flowchart.
The flowchart of FIG. 5 is a diagram showing a service installation procedure of the service processing system.
In the figure, first, a Java (registered trademark) source 410 and a WSDL source 411 are installed in the center multifunction peripheral 101 from the management PC 103 (step S501). The storage location is HD211. You don't have to install both, and in principle, you can create a service with one source, but here you install both.

Next, a service is generated from the source installed above (step S502).
Details of the service generation procedure step S502 are shown in the flowchart of FIG. First, the Java (registered trademark) compiler 401 of the center multifunction peripheral 101 compiles the Java (registered trademark) source 410 on the HD 211 to generate the Java (registered trademark) class file 412 (step S601).
Next, the WSDL compiler 403 of the center multifunction peripheral 101 compiles the WSDL source 411 on the HD 211 to generate a Java (registered trademark) class file 412 (step S602).

Finally, the archiver 404 of the center multifunction peripheral 101 generates a Jar file 417 by combining the Java (registered trademark) class file 412, the resource file 415, and the manifest file 416 (step S603).
As a procedure subsequent to step S502, address information of the multifunction device 102 is input in order to specify the multifunction device 102 that is the installation destination of the service (step S503). The installation destination may be itself, that is, the center multifunction peripheral 101, but here, it can be installed in another multifunction peripheral 102.

One or more installation destinations can be specified.
The designation of the installation destination may be performed on the center multifunction peripheral 101 using the display 205 and the operation button 208 of the center multifunction peripheral 101, or may be performed from the management PC 103 using a means such as a Web browser.

Upon receiving the designation of the installation destination, the center multifunction peripheral 101 repeats the following processing for all the designated installation destinations.
First, it is determined whether or not all installations have been completed (step S513). If completed, the sequence of FIG. 5 is terminated.
If not completed, the center multifunction device 101 selects one multifunction device 102 that has not been installed, and acquires its ID (step S504). This is, for example, the serial number of the MFP 102. Will get. If the address information can be used as an ID as it is, it can also be used.

  Next, the license file 413 is generated based on the ID obtained in the previous step (step S505). The license file 413 includes the ID. Alternatively, in order to improve security, the included ID portion or the entire license file 413 is encrypted, making it difficult to impersonate and tamper.

  Although not shown, the license file 413 is normally deleted after the installation procedure. This is because it cannot be abused. However, if the license file 413 itself can be prevented from being misused by using an encryption technique or the like, the license file 413 may be left in preparation for the installation of the next service. In this way, the trouble of acquiring the ID and generating the license file 413 can be saved.

Next, the archiver 404 of the center multifunction peripheral 101 generates an installable binary 414 by combining the Jar file 417 and the license file 413 (step S506).
Then, the center multifunction peripheral 101 installs the generated installable binary 414 in the multifunction peripheral 102 (step S507).
The multifunction peripheral 102 that is the installation destination receives the installable binary 414 sent for installation through the network, extracts the license file 413 from the installerable binary 414, and includes the ID included in the license file 413. The license is confirmed by checking whether the ID matches the user ID (step S508).

If the IDs match, that is, the license is valid, the Jar file 417, which is a service included in the installable binary 414, is extracted and installed in the HD 211 (step S510).
Finally, the installed service is started (step S511), and the process returns to step S513.
If it is determined in step S509 that the license is not valid, error processing is performed (step S512), and the process returns to step S513.

  Through the above procedure, one service can be installed in one or a plurality of multifunction peripherals 102. Although not shown in the figure, it is assumed that the center multifunction device 101 manages data indicating which service is installed in which multifunction device 102 or which service is installed in which multifunction device 102.

  It is also possible to install additional services. Even after the service installation is completed, the center multifunction peripheral 101 does not immediately delete the service source or the Jar file 417 from the HD 211. It remains until the user gives an explicit deletion instruction (not shown). When the user gives an instruction to install the remaining service to the non-installed multifunction peripheral 102, the installation can be performed by following the procedure from step S503.

Next, acquisition and output of service usage status will be described with reference to FIGS.
The service usage status will be described. The multifunction machine 102 counts the number of times the scanner 206 and printer 207 are used. Billing for service use is performed based on this count information. The counter of the number of times of use is protected by strict security, for example, so that the counter cannot be decremented illegally. This is an advantage of a proprietary device compared to a general-purpose PC whose specification is open. Further, when it is inconvenient to determine the usage status of the service by the usage count of the scanner 206 or the printer 207, other elements may be added to the usage status. For example, it may be possible to include the number of operating days of the service in the usage status.

  This is shown in the table of FIG. In the figure, for each service, items indicating a service usage status such as a scan counter 901, a print counter 902, and a working day 903 are prepared, and the item data is updated each time the service is used. .

The data shown in the table of FIG. 9 is stored in the HD 211 or the Flash ROM 209.
The item indicating the service usage status is not limited to these, and an item unique to a certain service may be added.
Each time a new service is installed, the line is incremented and a count for the new service is started.

  In FIG. 9, data items are provided for each service. However, the data items may be further subdivided and the data of each service may be divided according to the MFP 102 of the installation destination (not shown). In this case, the table in FIG. 9 also indicates in which MFP 102 each service is installed.

Accordingly, the service usage status, that is, the license grant status can be managed for each MFP 102.
Of course, it is obvious to those skilled in the art that this can be realized in a format other than the format shown in FIG.

Next, the procedure for acquiring the service usage status will be described with reference to FIG.
The center multifunction peripheral 101 aggregates the service usage status from the multifunction peripheral 102 that has installed the service (step S701). The aggregation method may be a method in which the center multifunction device 101 makes an inquiry to the multifunction device 102 and the multifunction device 102 responds, or each time the multifunction device 102 uses the service or every predetermined time, the center multifunction device 102 It is also possible to report to the machine.

  Next, the center multifunction peripheral 101 determines whether there is a service usage status output request from the user (step S702). When there is a service usage status output request, for example, when the user performs an operation for requesting a service usage status output from the management PC 103, the data shown in the table of FIG. Is output (step S703), and the process ends. If there is no service usage status output request, the process ends without doing anything.

Next, the procedure for uninstalling the service will be described with reference to the flowchart of FIG.
It is assumed that the user gives an instruction to uninstall a service from the management PC 103 (step S801).
At that time, the user designates one or more MFPs 102 to be uninstalled (step S802).
The center multifunction peripheral 101 repeats the following procedure for all multifunction peripherals 102 that have been instructed to be uninstalled.

That is, first, it is determined whether or not uninstallation has been completed for all the MFPs 102 that have been instructed to be uninstalled (step S803).
If there are still MFPs 102 to be uninstalled, one MFP 102 is selected from them, and if the service is operating, the MFP 102 is stopped (step S804).

Next, the service is uninstalled from the HD 211 (step S805). Specifically, the service Jar file 417 is deleted from a predetermined location of the HD 211.
If there is service usage status data that has not yet been sent from the MFP 102 to the center MFP 101 (if there is service usage after the last service usage status report, such data exists. ), The center multifunction peripheral 101 tabulates the data (step S806). Then, the process returns to step S803.

If it is determined in step S803 that all uninstallation has been completed, the center multifunction peripheral 101 determines whether or not to delete the service source from an option (not shown) specified by the user during uninstallation (step S807). ).
If the user has turned on the option “Delete service source when uninstalling”, the service source is deleted from the HD 211 (step S808). And it ends.

Next, the procedure for installing the service will be described with reference to the flowchart of FIG.
In the figure, first, a Java (registered trademark) source 410 and a WSDL source 411 are installed in the center multifunction peripheral 101 from the management PC 103 (step S1001). The storage location is HD211. You don't have to install both, and in principle, you can create a service with one source, but here you install both.

Next, a service is generated from the source installed above (step S1002).
Details of the service generation procedure step S1002 are shown in the flowchart of FIG.
Next, the address information of the multifunction device 102 is input to designate the multifunction device 102 that is the installation destination of the service (step S1003). The installation destination may be itself, that is, the center multifunction peripheral 101, but here, it can be installed in another multifunction peripheral 102.

One or more installation destinations can be specified.
The designation of the installation destination may be performed on the center multifunction peripheral 101 using the display 205 and the operation button 208 of the center multifunction peripheral 101, or may be performed from the management PC 103 using a means such as a Web browser.

Upon receiving the designation of the installation destination, the center multifunction peripheral 101 repeats the following processing for all the designated installation destinations.
First, it is determined whether or not all installations have been completed (step S1004). If completed, the sequence of FIG. 10 is terminated.
If not completed, the center multifunction device 101 selects one multifunction device 102 that has not been installed, and inquires of the multifunction device 102 about the ID (step S1005).

When the MFP 102 receives the ID inquiry (step S1051), it returns its own ID (step S1052).
The center multifunction peripheral 101 acquires the returned ID (step S1006).
Next, a license file 413 is generated based on the ID obtained in the previous step (step S1007). The license file 413 includes the ID. Alternatively, in order to improve security, the included ID portion or the entire license file 413 is encrypted, making it difficult to impersonate and tamper.

Next, the archiver 404 of the center multifunction peripheral 101 generates an installable binary 414 by combining the Jar file 417 and the license file 413 (step S1008).
Then, the center multifunction peripheral 101 installs the generated installable binary 414 in the multifunction peripheral 102 (step S1009).

The multi-function peripheral 102 that is the installation destination receives the installable binary 414 sent for installation via the network (step S1061).
Next, the license file 413 and the Jar file 417 are extracted from the installable binary 414 (step S1062).

Then, after acquiring the ID included in the license file 413 (step S1063), it is checked whether it matches the own ID (step S1064).
If the IDs match, that is, if the license is valid, the Jar file 417 is installed in the HD 211 (step S1065).

Next, the installed service is started (step S1066).
Finally, success is notified to the center multifunction peripheral 101 (step S1068), and the process ends.
If it is determined in step S1064 that the license is not valid, an error notification is sent to the center multifunction peripheral 101 (step S1067), and the process ends.

  On the other hand, the center multifunction peripheral 101 waits for an error notification in step S1067 or a success notification in step S1068 (step S1010). If an error is notified, an error indicating that the installation has failed is displayed on the MFP 102 being processed (step S1011), and the process returns to step S1004. If there is a success notification, no error is displayed and the process returns to step S1004. If ID notification and license file generation are performed correctly, a normal error cannot occur unless it is a program bug.

Next, another embodiment of the procedure for acquiring the service usage status will be described with reference to FIG.
The center multifunction peripheral 101 monitors whether the service usage status is notified from the multifunction peripheral 102 (step S1101).
When notified, the usage status is totaled (step S1102). For example, for the service 1 904 in FIG. 9, when the scan counter 901 reports from the multifunction device 1 102a that the increment is 3, the data of the corresponding item is incremented by +3.

  In FIG. 9, data is aggregated for each service, but it may be further subdivided that the data is aggregated for each MFP 102 at the installation destination. At that time, the use of the service 1 904 in the MFP 2 102b is incremented as different data.

Next, the center multifunction peripheral 101 monitors whether there is a service usage status output request from the management PC 103 (step S1103).
If there is a request, the data in FIG. 9 is output as the service usage status (step S1104).

Next, the center multifunction peripheral 101 monitors whether or not there is a service usage status data clear request from the management PC 103 (step S1105).
When the service usage status is aggregated for each predetermined period and billing is performed, it is easy to understand that after the aggregation, the service usage status is cleared and restarted from zero. In order to do this, the service usage status data can be cleared from the management PC 103.
If there is a service usage status clear request, the usage status of the requested service is cleared (step S1106). For example, when there is a clear request for service 1 904, the data in the row of service 1 904 in FIG. 9 is cleared.
And it returns to step S1101 and continues monitoring.

Next, the procedure for uninstalling the service will be described with reference to the flowchart of FIG.
It is assumed that the user gives an instruction to uninstall a service from the management PC 103 (step S1201).
At that time, the user designates one or more multifunction peripherals 102 to be uninstalled (step S1202).

The center multifunction peripheral 101 repeats the following procedure for all multifunction peripherals 102 that have been instructed to be uninstalled.
That is, first, it is determined whether or not uninstallation has been completed for all the MFPs 102 that have been instructed to be uninstalled (step S1203).
If there is still a multifunction device 102 to be uninstalled, one of the multifunction devices 102 is selected, and a service uninstall request is made to the multifunction device 102 (step S1204).

The MFP 102 that has received the service uninstall request stops if the service is operating (step S1251).
Next, the service is uninstalled from the HD 211 (step S1252). Specifically, the service Jar file 417 is deleted from a predetermined location of the HD 211.
If there is still service usage status data not yet notified from the MFP 102 to the center MFP 101 (if there is service usage after the last service usage status report, such data exists. ) And notify (step S1253).
The center multifunction peripheral 101 receives the usage status data and tabulates it (step S1205).

When the uninstallation is completed, the multifunction device 102 sends an uninstallation completion notification to the center multifunction device 101 (step S1254).
The center multifunction peripheral 101 waits until an uninstallation completion notification is received (step S1206). When the notification is received, the process returns to step S1203.
If it is determined in step S1203 that all uninstallation has been completed, the center multifunction peripheral 101 determines whether or not to delete the service source from an option (not shown) specified by the user during uninstallation (step S1207). ).
If the user has turned on the option “Delete service source when uninstalling”, the service source is deleted from the HD 211 (step S1208). And it ends.

In the above embodiment, as an example of a service, a Java (registered trademark) source 410 or a WSDL source 411 is compiled into a Java (registered trademark) class file 412 and is operated on the Java (registered trademark) VM 1303. As explained, the form of service is not limited to this.
Those skilled in the art will readily understand that the service is language independent and that the present invention can be achieved with program description languages other than Java (registered trademark).

  Further, although the embodiment using the WSDL source 411 has been described, it is obvious that the present invention is not limited to this, and other source formats may be used as long as the service format is finally executable. is there.

Further, in the above-described embodiment, it has been described that the service installation source device of the service processing system described so far is the center multifunction device 101 and the service installation destination device is the multifunction device 102.
In a device such as the center multifunction peripheral 101, the means for externally accessing an internal recording medium such as the HD 211 is limited, and it is difficult to illegally rewrite information existing on the internal recording medium as compared to a general computer. . Also, unlike general computers, it can incorporate its own specifications, so various measures can be taken to improve security. In that sense, the security of license management is higher.

However, they do not have to be a multifunction machine to implement the present invention. Both may be general computers.
However, if the service processing system is composed of a general-purpose OS and a general-purpose CPU, the possibility that the license management information is tampered with increases. Therefore, when a general computer is used for the service processing system, it may be possible to make unauthorized access difficult by further using an encryption technique for the license management information.

  Although the present invention has been described above, the present invention can be realized by a program that operates on each device, although hardware is required. Accordingly, the above-described functions can be realized by reading a software program that realizes the functions of the above-described embodiment and a recording medium storing the program codes and executing them by a computer.

It is a block diagram which shows the structure of the service processing system which concerns on this invention. 2 is a block diagram illustrating an internal configuration of the center multifunction peripheral or the multifunction peripheral. FIG. It is a block diagram which shows the conventional structure. It is the figure which showed the flow in which a service is produced | generated. It is the flowchart which showed the service installation procedure. It is the flowchart which showed the service production | generation procedure. It is the flowchart which showed the service utilization condition acquisition procedure. It is the flowchart which showed the service uninstallation procedure. It is a figure which shows the table | surface which showed the structure of the service utilization status data. It is the flowchart which showed the service installation procedure. It is the flowchart which showed the service utilization condition acquisition procedure. It is the flowchart which showed the service uninstallation procedure. It is the figure which showed the software hierarchy of the service generation apparatus.

Explanation of symbols

101 ... Center MFP 102 ... MFP 103 ... Management PC
201 ... CPU
211 ... Hard disk 401 ... Java (registered trademark) compiler 403 ... WSDL compiler 404 ... Archiver 410 ... Java (registered trademark) source 411 ... WSDL source 412 ... Java (registered trademark) class file 413 ... License file 414 ... Installable binary 417 ... Jar file 1303 ... Java (registered trademark) VM

Claims (12)

Service generation means for generating a service from a service source;
Installation destination storage means for storing one or more installation destinations;
License generation means for generating a license according to the installation destination;
Installable binary generation means for generating an installable binary from the service and the license;
An apparatus for installing the installable binary in the installation destination. In a service processing system including a service generation device that generates a service from a service source and a service execution device that executes the service,
The service generation device includes:
Service generation means for generating a service from a service source;
Installation destination storage means for storing service execution devices as one or more installation destinations;
License generation means for generating a license according to the installation destination;
Installable binary generation means for generating an installable binary from the service and the license;
Installation means for installing the installable binary in the installation destination;
The service execution device includes:
Installerable binary input means for inputting the installerable binary;
A license conformity determination means for determining whether a license condition of the installable binary is compatible with the device;
A service processing system comprising: an installation unit that installs the installable binary service when the license compatibility determination unit determines that the license condition is compatible with the device itself. Service generation means for generating a service from a service source;
Installation destination storage means for storing one or more installation destinations;
License generation means for generating a license according to the installation destination;
Installable binary generation means for generating an installable binary from the service and the license;
Installation means for installing the installable binary in the installation destination;
Service usage status storage means for storing the service usage status sent from the installation destination;
An information output unit that outputs information stored in the installation destination storage unit or the service usage status storage unit to the outside. In a service processing system including a service generation device that generates a service from a service source and a service execution device that executes the service,
The service generation device includes:
Service generation means for generating a service from a service source;
Installation destination storage means for storing service execution devices as one or more installation destinations;
License generation means for generating a license according to the installation destination;
Installable binary generation means for generating an installable binary from the service and the license;
Installation means for installing the installable binary in the installation destination;
Service usage status storage means for storing the service usage status sent from the installation destination;
Information output means for outputting information stored in the installation destination storage means or the service usage status storage means to the outside,
The service execution device includes:
Installerable binary input means for inputting the installerable binary;
A license conformity determination means for determining whether a license condition of the installable binary is compatible with the device;
An installation unit that installs the installable binary service when the license compatibility determination unit determines that the license condition is compatible with the device;
A service processing system comprising: service usage status transmission means for transmitting the service usage status of the device itself to the service generation device. A service generation process for generating a service from a service source;
An installation location storage step for storing one or more installation locations;
A license generation step of generating a license according to the installation destination;
An installable binary generation step of generating an installable binary from the service and the license;
An installation process for installing the installable binary in the installation destination. In a processing method of a service processing system including a processing method of a service generation device that generates a service from a service source and a processing method of a service execution device that executes the service,
The processing method of the service generation device is:
A service generation process for generating a service from a service source;
An installation destination storage step for storing a service execution apparatus as one or more installation destinations;
A license generation step of generating a license according to the installation destination;
An installable binary generation step of generating an installable binary from the service and the license;
An installation step of installing the installable binary in the installation destination,
The processing method of the service execution device is:
An installerable binary input step for inputting the installerable binary;
A license conformity determination step for determining whether a license condition of the installable binary is compatible with the device;
A processing method of a service processing system comprising: an installation step of installing the installable binary service when the license suitability determination step determines that a license condition is compatible with the device itself. A service generation process for generating a service from a service source;
An installation location storage step for storing one or more installation locations;
A license generation step of generating a license according to the installation destination;
An installable binary generation step of generating an installable binary from the service and the license;
An installation step of installing the installable binary in the installation destination;
A service usage status storage step for storing a service usage status sent from the installation destination;
An information output step of outputting the information stored in the installation destination storage step or the service usage status storage step to the outside. In a processing method of a service processing system including a processing method of a service generation device that generates a service from a service source and a processing method of a service execution device that executes the service,
The processing method of the service generation device is:
A service generation process for generating a service from a service source;
An installation destination storage step for storing a service execution apparatus as one or more installation destinations;
A license generation step of generating a license according to the installation destination;
An installable binary generation step of generating an installable binary from the service and the license;
An installation step of installing the installable binary in the installation destination;
A service usage status storage step for storing a service usage status sent from the installation destination;
An information output step of outputting the information stored in the installation destination storage step or the service usage status storage step to the outside,
The processing method of the service execution device is:
An installerable binary input step for inputting the installerable binary;
A license conformity determination step for determining whether a license condition of the installable binary is compatible with the device;
An installation step of installing the installable binary service when the license suitability determination step determines that the license condition is compatible with the device;
A service processing system processing method comprising: a service usage status transmission step of transmitting a service usage status in the device itself to the service generation device.   A program for causing a computer to execute the service generation method according to claim 5 or 7.   A computer-readable recording medium on which the program according to claim 9 is recorded.   A program for causing a computer to execute the processing method of the service processing system according to claim 6 or 8.   A computer-readable recording medium on which the program according to claim 11 is recorded.

Images