JP2009252120A - Program accounting management device and capsule execution processing device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program accounting management device capable of providing an accounting mechanism of not static data such as digital contents but a process of a program such as executable form file. <P>SOLUTION: The program accounting management device 20 includes: a first control means 22 for creating a capsule file part with a body program storing means for storing the body program part and the number-of-executions storing means for storing information of the number of executions by counting the number of executions of the body program part encapsulated; and a second control means 23 for outputting a clearance money amount of the body program part by checking the capsule file part at the request of a clearance information acquiring, and by the information of the number of executions stored in the number-of-executions storing means and the preliminarily registered utilized unit price information of the body program part. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a program charging management apparatus, a program charging system, a capsule execution processing apparatus, a program charging method, a capsule execution processing method, a charging management program, and a capsule execution processing program, and in particular, digital rights management (DRM). The present invention relates to a technology for charging a charged program using the above mechanism.

When selling paid programs such as application software, the paid programs are sold in units of packages.
In recent years, as a method for charging only the amount of content used, for example, ASP (Application Service Provider), SaaS (Software as a Service), and the like can be cited.

  In this ASP or SaaS, a Web server is started, a request from a user computer is received through the Internet, a process for the request is performed, and a processing result is returned to the user computer through the Internet. It is a mechanism to charge for. These are suitable for charging for static data such as contents.

  On the other hand, digital rights management (DRM) can be cited as a mechanism for protecting static data that can have high value.

DRM encrypts content data using encryption technology and adds (encapsulates) information about usage browsing conditions to control the execution of capsules, that is, usage browsing conditions for content, and illegal use of content This is a technology to prevent this.
DRM originally began to spread as a mechanism for charging paid content such as video content and music content by billing, but this is also applied to the management of electronic documents of companies.

  Specific examples of such DRM include, for example, Microsoft RMS (Rights Management Services, http://www.microsoft.com/japan/windowsserver2003/technologies/rightsmtmt/development). //Www.adobe.com/jp/products/livecycle/).

For example, it demonstrates concretely in the example of RMS. A general DRM mechanism is shown in FIG.
In the DRM system 1000, when a new electronic document F is generated, the creator computer 1001 uses one of the DRM management servers for license information that defines attribute information such as the usage method and distribution authority of the electronic document F. It is transmitted to the ticket server 1002. The ticket server 1002 adds the attribute information defined in the license transmitted to the electronic document F, performs encryption, and generates a capsule CP. This is called electronic document encapsulation. Further, the ticket server 1002 transmits authentication information related to encryption to the authentication server 1003 for registration.

  A user who wishes to use a capsule CP, which is an encapsulated electronic document, transmits a request for sending a license ticket L necessary for using the capsule CP to the ticket server 1002 using the user computer 1004.

  When the ticket server 1002 permits the application for sending the license ticket L, the ticket server 1002 transmits the license ticket L describing various distribution-related attributes such as the number of times of use and whether or not to permit copying to the user computer 1004 of the user who wants to use the license ticket. To do. Only the person holding the license ticket L can open the capsule CP of the encapsulated electronic document and refer to or edit the electronic document in the capsule CP.

  In the user computer 1005, those who wish to use the capsule CP who does not have the license ticket L cannot open the capsule CP. Furthermore, the license ticket L cannot be copied without permission and the electronic document cannot be used illegally.

In some cases, the license ticket is not permitted to be distributed, and the use permission is applied to the DRM server every time the license ticket is used. In this way, by managing and encapsulating an electronic document with DRM, even if the information of the encapsulated electronic document is leaked, access to the DRM server at the leakage destination to obtain authentication permission, or a license ticket As long as you don't get, you don't have to worry about the contents being decrypted
In addition, by providing a mechanism for charging each time a license ticket is issued, it is possible to charge for each data usage.

  In DRM, the target data is static data, and application software that processes the data needs to incorporate a mechanism closely linked to DRM. For example, in RMS of Microsoft Corporation, it is possible to encapsulate a data file created by the company's Office program, specifically, spreadsheet software or word processor software using each application software.

In this case, application software such as spreadsheet software and word processing software has a built-in mechanism for RMS encapsulation and decapsulation.
For this reason, DRM can be used only in an environment in which application software that supports RMS, such as the company's Office program or a third-party application, is installed.

  Furthermore, as a related technology of this type of system, for example, those described in Patent Document 1 and Patent Document 2 shown below can be cited.

In the digital rights management (DRM) system of Patent Document 1, an authoring tool 18 encrypts digital content 12 according to an encryption / decryption key and instructions and / or rules associated with digital content 12. 12p is generated (paragraph number 0031 of Patent Document 1).
The digital content package 12p distributed by the content server 22 includes the following. Digital content 12 encrypted using an encryption / decryption key (KD) (ie, (KD (CONTENT))), content ID (or package ID) of digital content 12 (or package 12p), encryption Key ID of deregistration key (KD). License acquisition information in unencrypted form. The key KD for encrypting the content server 22 public key (PU-CS) signed with the content server 22 private key (PR-CS) (ie, (KD (PU-CS) S (PR-CS))) (patent Reference 1, paragraph number 0051).
The user's computing device does not render the digital content unless it complies with the license rules associated with the digital content and implemented with the license acquired by the user (paragraph number 0062 of Patent Document 1).
Assuming that the encrypted digital content 12 is distributed and received by the user and placed on the computing device 14 in the form of a file stored by the user, the user performs some variation of the rendering command. To attempt to render the digital content 12.
The rendering command can be implemented as a request to “play” or “open” digital content. This playback command or open command is as simple as “clicking” on an icon representing digital content.
The rendering command is executed when the user instructs to open a file having digital content (paragraph number 0069 of Patent Document 1).

In the digital work distribution system disclosed in Patent Document 2, when a user wants to use a digital work based on a use contract, the user pays some consideration and obtains a program and differential data for restoring distribution data to original data. . These are encapsulated as a restoration object together with usage conditions that are conditions for use, and are sent to the user as encrypted data. Here, the encrypted data sent to the user is not data obtained by encrypting the original data itself, but differential data created by taking the difference between the original data and the distribution data, and embedding it in the distribution data into the original data. The program to be restored is encrypted (paragraph number 0035 of Patent Document 2).
In Patent Document 2, the restoration object includes a usage condition based on a usage contract, and the user device interprets this and determines the availability and the usage authority (paragraph number 0036 of Patent Document 2).
The user decapsulates the encapsulated restoration object and reproduces the original data by the function of each unit of the data reproduction unit of the user device.
JP 2003-330560 A Japanese Patent No. 3173352

However, in the related digital rights management (DRM) system, the object of encapsulation is static data, and the program itself such as application software is not the object of encapsulation.
That is, there are ASP and SaaS as a billing mechanism for static data such as content, but for processing corresponding to one program unit, for example, an execution format file (for example, * .exe format file). There is a problem that such an ASP or SaaS mechanism cannot be introduced.

  Further, in Patent Document 1, there is a problem that even if digital content can be protected, the program itself such as various software cannot be protected or charged.

  Further, in Patent Document 2, since a release program for restoring original data is encapsulated, the original data can be protected, but the program itself, such as various application software, can be used by the user. There is a problem that it is not possible to use the system or charge according to the usage.

  An object of the present invention is to solve the above-described problems of the related art, and to realize a charging mechanism for processing of a program such as an executable file instead of static data such as digital content. It is an object of the present invention to provide a program billing management apparatus capable of performing the above.

  In order to achieve the above object, a program charge management apparatus according to the present invention is a program charge management apparatus for managing charges according to the use of an execution form of a main body program part, and a main body program storage means storing the main body program part. A first control unit that encapsulates the execution number storage unit that counts the number of executions of the main body program unit and stores information on the number of executions, and a payment information acquisition request regarding the main body program unit The main body program of the capsule file portion is checked based on the information on the number of executions stored in the execution number storage means and the usage unit price information of the main body program portion registered in advance. And a second control means for outputting the settlement amount of the part.

  The program billing system of the present invention generates a capsule file part that encapsulates a main body program part in an executable format, and manages a billing control according to the use of the capsule file part, and the program billing management A first communication device that is formed so as to be communicable with a device and used by a capsule user who uses the capsule file unit, and the program charge management device includes a main body program storage unit storing the main body program unit; A first control unit that generates a capsule file unit encapsulating an execution number storage unit that counts the number of executions of the main body program unit and stores information on the number of executions; and a settlement information acquisition request for the main body program unit In response, the capsule file portion is examined and the execution number stored in the execution number storage means Second control means for outputting a settlement amount of the main body program part of the capsule file part based on number information and usage unit price information of the main body program part registered in advance, and the first communication In response to a process execution request for the capsule file unit, the capsule file unit used in the device releases the encapsulation and starts the main body program unit, counts the number of times of execution, and counts the number of times of execution. Capsule control means for storing information in the execution count storage means and performing re-encapsulation after the execution of the main body program unit is included.

  The capsule execution processing apparatus of the present invention encapsulates a main body program storing means for storing a main program section in an execution format, and an execution count storage means for counting the number of executions of the main body program section and storing information on the number of executions. A capsule execution processing device for executing the capsule file portion, and in response to a processing execution request for the capsule file portion, in a state where the encapsulation is released, The main body program part stored in the main body program storage means is taken out and stored in the independent file generation means for generating an independent file in a storage area managed by the file system to which the capsule file section belongs, and in the execution frequency storage means. Execution number counting means for performing a counting process for incrementing the execution number information by one , A child task activation processing means for performing a process for activating the main body program part as a child task, and an independent file deletion for performing a process for deleting the independent file on the file system upon receiving a task end notification from the child task A processing unit; and a re-encapsulation unit configured to re-encapsulate the capsule file portion when the independent file is deleted.

  The program billing method of the present invention is a program billing method in which a computer charges according to the use of a main program part in an execution format, and the main program storage means in which the computer stores the main program part and the main program A first control processing step for generating a capsule file portion encapsulating an execution number storage means for counting the number of executions of the unit and storing information on the number of executions, and the computer provides the capsule file portion to the user The providing step, and the computer investigates the capsule file part in response to a payment information acquisition request relating to the main body program part, and information on the number of executions stored in the execution number storage means and the main body program registered in advance The main body program of the capsule file unit based on the unit price information of the unit It is characterized in that it comprises a second control processing step of outputting the adjusted amount of arm portion.

  The capsule execution processing method of the present invention includes a main body program storing means in which a computer stores a main program section in an execution format, and an execution count storage means for counting the number of executions of the main body program section and storing information on the number of executions. A capsule execution processing method for executing a capsule file portion encapsulating a capsule file, wherein the computer releases the encapsulation in response to a process execution request to the capsule file portion, and the computer An independent file generation step of taking out the main body program part stored in the main body program storage means in a state where the encapsulation is released, and generating an independent file in another storage area on the file system to which the capsule file part belongs; The computer stores the number of execution times in the storage unit. An execution number counting step for performing a counting process for incrementing the information on the number of execution times, a child task starting process step for performing processing for starting the main body program unit as a child task, and a computer Upon receiving a task end notification from a task, an independent file deletion processing step for performing processing for deleting the independent file on the file system, and when the independent file is deleted, the computer re-capsules the capsule file portion. And a re-encapsulation step for performing a process of converting to a re-encapsulation step.

  An accounting management program of the present invention is an accounting management program for causing a computer to execute accounting processing in accordance with the use of an execution-format main body program unit, wherein the main body program storing means storing the main body program unit and the main body program unit A first control function for generating a capsule file part encapsulating an execution number storage means for counting the number of executions and storing information on the number of executions, and in response to a settlement information acquisition request for the main body program part, the capsule Investigate the file part, and output the settlement amount of the main body program part of the capsule file part based on the information on the number of executions stored in the execution number storage means and the usage unit price information of the main body program part registered in advance And a second control function for causing the computer to execute a function including the second control function.

  The capsule execution processing program of the present invention encapsulates a main body program storage means that stores an execution-format main body program section and an execution count storage means that counts the number of executions of the main body program section and stores information on the number of executions. A capsule execution processing program for causing a computer to execute the execution processing of the capsule file portion, wherein the encapsulation is released in response to a processing execution request to the capsule file portion, and the encapsulation is released. In the state, the main body program part stored in the main body program storage means is taken out, an independent file generation function for generating an independent file in another storage area on the file system to which the capsule file part belongs, and the execution frequency storage The information on the number of executions stored in the means is increased by one. When an execution count function that performs a counting process, a child task activation process function that activates the main body program unit as a child task, and a task end notification from the child task, the independent file on the file system is received. A function that includes an independent file deletion processing function that performs processing for deleting a file and a recapsulation function that performs processing for recapsulating the capsule file portion when the independent file is deleted. It is characterized by causing a computer to execute a function including it.

  According to the present invention, it is possible to provide an excellent program billing management apparatus that does not have related technology that can measure the number of uses for billing in units of programs.

[Basic configuration of program charge management device]
First, the basic configuration of the program charge management apparatus will be described. The program billing management apparatus of the present invention is a program billing management device that manages billing according to the use of a main program unit in an execution format, and includes a main body program storage means storing the main body program unit and execution of the main body program unit 1st control means (for example, the code | symbol 22 etc. shown in FIG. 1) which encapsulates the execution frequency storage means which counts the frequency | count, and memorize | stores the information of execution frequency, and the adjustment regarding the said main body program part In response to the information acquisition request, the capsule file portion is examined, and the capsule file portion is stored based on the information on the number of executions stored in the execution number storage means and the unit price information of the main body program portion registered in advance. 2nd control means (for example, the code | symbol 23 etc. shown in FIG. 1) which outputs the adjustment amount of the said main body program part. It is set to.

  According to such a program billing management apparatus, it is possible to measure the number of uses for billing in a small program unit, and it is not necessary to presuppose mounting a specific DRM base, so that distribution is easy.

  Hereinafter, an example of a preferred embodiment in which the “program charge management apparatus” of the present invention is applied to a “program charge system” will be specifically described with reference to the drawings.

[First Embodiment]
(Overall configuration of program billing system)
First, the specific configuration of the program billing system of the present embodiment will be described from the overall configuration, and then the detailed configuration of each unit will be described. FIG. 1 is a block diagram showing an example of an overall schematic configuration of a program billing management apparatus in the program billing system according to the first embodiment of the present invention. FIG. 2 is a block diagram showing an example of the overall configuration of the program billing system according to the first embodiment of the present invention.

  As shown in FIG. 1, the program billing system 1 of the present embodiment has, as a schematic configuration, an execution form main body program unit 12 that executes a specific process registered by a program creator, and the main body program unit 12. A capsule file unit 13 that encapsulates the file, a program file management unit 20 that generates the capsule file unit 13 so that the capsule file unit 13 can be provided to a user, and performs charge management control according to the use of the capsule file unit 13; It is comprised including.

Here, as a specific hardware configuration of the program billing system 1 that realizes the schematic configuration as described above, for example, a configuration as shown in FIG.
That is, the program billing system 1 includes a program billing management device 20 in which the main body program unit 12 is registered and encapsulated, and a registered user who is configured to be able to communicate with the program billing management device 20 and registers the main body program unit 12. The first communication device 10a used by the capsule user who uses the capsule file unit 13 and is formed so as to be communicable with the third billing management device 10c and the program billing management device 20, and the capsule file used And a second communication device 10b used by a payment information user who desires to use the payment information of the unit 13.

The first communication device 10 a can also be referred to as a capsule execution processing device in which the capsule user executes the capsule file unit 13.
In addition, the first communication device 10a, the second communication device 10b, the third communication device 10c, and the program billing management device 20 are each operated by program control and have network-related functions. For example, any computer such as a desktop computer, a laptop computer, an information device having a wireless / wired communication function, or a similar computer may be used.

  Furthermore, each hardware configuration of the first communication device 10a, the second communication device 10b, the third communication device 10c, and the program billing management device 20 includes display means (screen) for displaying various information and the like. ), Operation input means (for example, a keyboard / mouse) for operating and inputting data on the display screen (various input fields, etc.) of the display means, and transmission / reception means (communication means) for transmitting / receiving various signals / data. Further, it may have storage means (for example, memory, hard disk, etc.) for storing various programs and various data, and control means (for example, CPU, etc.) for controlling these.

  Each part of the program billing management apparatus 20 in FIG. 1 will be described on the assumption that the communication infrastructure as described above is formed.

  The main body program unit 12 is provided from the third communication device 10c and the like and registered in the program billing management device 20, and is an executable program to be billed. For example, in the case of Windows, *. Programs with an extension of exe are targeted.

(Data structure of capsule file)
The capsule file unit 13 is generated by the program billing management device 20 and provided to a user such as the first communication device 10a. The capsule file unit 13 counts the number of executions and records the number of executions. In response to a process execution request to the capsule file unit 13 and a main body program storage unit 15 that stores the main program unit 12 in an executable format, the encapsulation program is released and the main body program unit 12 is started, and the number of executions And a capsule control unit 16 for controlling the execution number storage unit 14 to store the execution number information in the execution number storage unit 14 and performing re-encapsulation after the execution of the main body program unit 12 is completed.

  Here, as an implementation method of the capsule, there is an implementation method in the form of an archive file. In terms of Windows, the archive file is typically a ZIP format or an LZH format, and a plurality of files are collected into a single compressed file and stored in one file.

To extract an internal file from an archive format file, it can be extracted by performing a “decompression” process. In addition, when an archive file is called, it can be decompressed in a “self-extracting” manner, and a startup program can be automatically activated at the time of self-extracting.
Therefore, in the case of the capsule file unit 13, the capsule file unit 13 may be a self-extracting archive file, and the processing of the capsule file unit 13 may be described as a startup program.

Also, the capsule control unit 16 takes out the main body program part stored in the main body program storage means in response to a processing execution request from the first communication device 10a by the capsule user, and the file to which the capsule file part belongs Independent files can be created in other storage areas on the system.
Further, the capsule control unit 16 increases the count of the execution number storage means by one, starts the file of the main body program unit as a child task, and receives a task end notification from the child task. The independent file can be deleted and terminated.

(Configuration of program billing management device)
The program billing management apparatus 20 includes a program billing information storage unit 21 that stores the unit price information of the main body program unit and the program identification information for identifying the main body program unit 12 in association with each other, In response to a registration request for registering the main body program part (from the communication device 10c), the usage program unit information of the main body program part and the program identification information for identifying the main body program part are associated with each other as the charge object In response to a settlement information acquisition request (from the settlement information user's second communication device 10b), a program billing registration section 22 that performs control to register and generate the capsule file section is examined. The main body program unit based on information on the number of executions of the execution number storage means and registered usage unit price information Configured to include a program use the accounting settlement unit 23 performs control for outputting a levy, the.

  Here, the program billing management apparatus 20 of the present embodiment can use a multitasking operating system. Multitasking can use functions included in various operating systems such as Unix (registered trademark), Linux, and Windows (registered trademark).

  The program billing correspondence information storage unit 21 has a program billing correspondence table composed of a set of pairs of program names and usage unit prices. This is achieved with a normal array structure.

When the program billing registration unit 22 receives from the third communication device 10c of the registered user an instruction (main body program unit registration request) for registering as a billing target using a certain target program and its usage unit price as arguments, The target program and the unit price are additionally registered in the program billing correspondence table of the information storage unit 21 (registration function), the target program is stored in the main body program storage unit 15, and zero is stored in the execution count storage unit 14. The stored capsule file unit 13 is generated (capsule generation function).
The program billing registration unit 22 may be realized by a normal execution program (* .exe format in the case of Windows).

  Further, when generating the capsule file unit 13, the program billing registration unit 22 performs a process of performing encryption, compression encoding, or a combination thereof one or more times on the main body program storage unit 15 and the execution count storage unit 14. Can be encapsulated.

  When the program usage billing settlement unit 23 receives an instruction (settlement information acquisition request) for settlement of usage billing from the second communication device 10b of the settlement information user using a capsule file unit 13 as an argument, The program stored in the main body program storage unit is retrieved, the program billing correspondence table of the program billing correspondence information storage unit 21 is referred to, and the usage unit price of the retrieved program is checked from the registered information. Information on the number of executions (for example, an execution number value) in the execution number storage unit 14 in the capsule file unit 13 is extracted, and the total number of charges is output by adding the execution number value to the usage unit price.

  At this time, when the program usage charge settlement unit 23 acquires information on the number of executions from the execution number storage unit 14 of the capsule file unit 13, the program usage fee settlement unit 23 temporarily cancels the encapsulation of the capsule file unit 13. Can be obtained and re-encapsulated.

(Function of capsule control unit: configuration of capsule execution processing device)
When the capsule file unit 13 is executed by the first communication device 10a, it functions as a capsule execution processing device as shown in FIG.
In this case, the capsule control unit 16 of the capsule execution processing device, as shown in FIG. 4, in response to a process execution request to the capsule file unit 13, the decapsulation means 17a for releasing the encapsulation, and the encapsulation In the state in which is released, the main body program part stored in the main body program storage part 15 is taken out, and an independent file generating means 17b for generating an independent file in another storage area on the file system to which the capsule file part 13 belongs. And can be included.

  Further, the capsule controller 16 of the capsule execution processing device includes an execution number counting unit 17c that performs a counting process for incrementing the information on the number of executions in the execution number storage unit 14, and the main body program unit 12 as a child task. A child task activation processing unit 17d that performs processing to be activated, an independent file deletion processing unit 17e that performs processing to delete the independent file on the file system upon receiving a task end notification from the child task, and the independent file Is deleted, recapsulation means 17f for performing a process for recapsulating the capsule file portion may be included.

Here, the correspondence between the configuration requirements of the present embodiment and the configuration requirements of the present invention will be described.
The program charge registration unit 22 of the present embodiment can constitute the “first control means” referred to in the present invention. Further, the program use charge settlement section 23 can constitute the “second control means” in the present invention.
Furthermore, the “capsule control means” according to the present invention can be configured by the capsule control unit 16 of the present embodiment. Further, the “execution count storage means” according to the present invention can be configured by the execution count storage section 14 of the present embodiment. Furthermore, the “main program storing means” according to the present invention can be configured by the main program storage 15 of the present embodiment.

(Outline of program billing system)
The program billing system 1 having the above-described configuration generally operates as follows.
First, based on the operation input of the registered user, the third communication device 10 c transmits a main body program part registration request including the main body program part 12, a usage unit price, a program name, and the like to the program billing management apparatus 20.
The program billing management apparatus 20 gives an instruction (main body program part registration request) to register the billing target using the main body program unit 12 as a certain target program and its usage unit price as arguments from the third communication device 10c of the registered user. Upon receipt, the program billing registration unit 22 of the program billing management apparatus 20 additionally registers the target program and usage unit price in the program billing correspondence table of the program billing correspondence information storage unit 21.

  Further, the program billing registration unit 22 of the program billing management apparatus 20 stores the main body program unit 12 in the main body program storage unit 15, and generates a capsule file unit 13 storing zero in the execution count storage unit 14.

  In addition, the generated capsule file unit 13 is processed by the program billing management apparatus 20 so as to be provided to the capsule user by downloading or the like.

  The first communication device 10a of the capsule user acquires the capsule file unit 13 by downloading or the like from the program charge management device 20, and the first communication device 10a is instructed to execute a specific process on the capsule file unit 13. First, the capsule control unit 16 of the capsule file unit 13 takes out the program stored in the main body program storage unit 15 and creates it as an independent file on the file system provided in the first communication device 10a.

  Next, in the first communication device 10a, the capsule control unit 16 of the capsule file unit 13 increments the count of the execution count storage unit 14, and further starts the created main program file as a child task. Wait until the child task is finished.

  Subsequently, when the capsule control unit 16 of the capsule file unit 13 receives the task end notification from the child task in the first communication device 10a, the capsule file unit 13 deletes the independent file created on the file system and ends the process.

  On the other hand, when the second communication device 10b of the settlement information user obtains information related to the settlement of the usage fee, the second communication device 10b determines that the program billing management device is based on the operation input of the settlement information user. An instruction (settlement information acquisition request) for settlement of usage charges is transmitted to 20.

  The program usage charge settlement unit 23 of the program billing management apparatus 20 issues an instruction (payment information acquisition request) for settlement of usage bills from the second communication device 10b of the settlement information user using a capsule file unit 13 as an argument. When received, the program use charge settlement unit 23 of the program charge management apparatus 20 takes out the program stored in the main body program storage unit in the capsule.

  Further, the program usage charge settlement unit 23 refers to the program charge correspondence table in the program charge correspondence information storage unit 21 to check the usage unit price of the extracted program.

  Then, the program usage charge settlement unit 23 takes out information on the number of executions (for example, an execution number value) in the execution number storage unit 14 in the capsule file unit 13, and adds the execution number value to the usage unit price to calculate the total charge. Output the amount so that the user can refer to it.

In such a configuration, as shown in FIG. 3, when the program main body program is encapsulated in the program billing management apparatus 20, and the capsule is executed in the first communication apparatus 10a, the startup program is a self-decompression type. Starts execution, immediately starts execution of the main body program, deletes the main body program from the file system after completion of execution, and writes the one added with the number of times of decompression to the original capsule.
By doing so, the number of times this encapsulated program has been used is stored as the number of times of decompression, so that the registered user can charge a usage fee according to the number of times of decompression.

(About processing procedure)
Next, various processing procedures in the program billing system having the above-described configuration will be described in detail with reference to FIGS. FIG. 5 is a network sequence diagram showing an example of the entire processing procedure in the program billing system according to the first embodiment of the present invention.

The program billing method according to the present embodiment is intended for a method in which a computer included in the program billing management apparatus 20 performs billing according to the use of an execution form main body program unit that executes specific processing. .
In this program billing method, as a basic configuration, the computer included in the program billing management apparatus 20 has program identification information for identifying the main body program unit and the main body program unit in response to a registration request for registering the main body program unit. And encapsulating a main body program storage means for storing the main body program part and an execution number storage means for counting the number of executions of the main body program part and storing information on the number of executions. It is possible to include a first control processing step (for example, step S12 shown in FIG. 5) for performing control to generate the capsule file portion.
In this program billing method, the computer included in the program billing management apparatus 20 can include a providing step (for example, step S13 shown in FIG. 5) for providing the capsule file portion to the user.
Furthermore, in this program billing method, the computer included in the program billing management apparatus 20 investigates the capsule file portion used in response to the payment information acquisition request regarding the main body program portion, and executes the execution count storage means. Including a second control processing step (for example, step S18 shown in FIG. 5) for performing control to output the settlement amount of the main body program portion of the capsule file portion based on the number of times information and the registered usage unit price information. Can do.

(Overall processing)
More specifically, as shown in FIG. 5, first, the registered user registers the main body program unit in the program management device 20 using the third communication device 10 c.

  That is, when the registered user inputs the program name, which is an example of the program identification information for identifying the main body program part, the main body program part, and the usage unit price information on the third communication apparatus 10c, the third communication apparatus 10c. Transmits a main body program part registration request including these pieces of information to program charge management apparatus 20 (step S11) <main body program part registration request transmission step or main body program part registration request transmission function (hereinafter referred to as the name of the function) Abbreviation)>.

  Next, when receiving the main body program part registration request from the third communication apparatus 10c, the program billing management apparatus 20 (the computer provided therein) performs the first control process in response to the main body program part registration request. (Step S12) <First control processing step>.

In this first control process, in response to the main body program part registration request, the program billing management apparatus 20 associates the program name with the unit price information and stores it in the program correspondence table information storage unit 21 to register the program. Process to perform.
Further, in the first control process, the program charge management apparatus 20 performs a process of encapsulating the main body program part and generating the capsule file part 13 in response to the main body program part registration request.

  When the capsule file unit 13 is generated, the computer included in the program billing management apparatus 20 stores a main body program unit storage unit 15 storing the main body program unit and information on the number of executions of the main body program unit. An execution number storage unit 14 and a capsule control unit 16 that controls to release encapsulation and execute the main body program unit based on a processing instruction to the capsule file unit 13, count the number of executions, and reencapsulate. To configure.

  Next, the program billing management apparatus 20 performs a process for making the generated capsule file portion available to the capsule user by downloading or the like (step S13) <providing step>.

  Then, the first communication device 10a performs a process of transmitting a capsule file part acquisition request to the program billing management apparatus 20 based on the operation input by the capsule user (step S14) <capsule file part acquisition request Send step>.

  When the program charging management apparatus 20 receives this capsule file part acquisition request, the program charging management apparatus 20 transmits a capsule file part to the first communication apparatus 10a in response to the capsule file part acquisition request. (Step S15) <capsule file part transmission step>.

  Further, the first communication device 10a performs processing for receiving the capsule file portion from the program billing management device 20 <capsule file portion receiving step>. Thereafter, when a processing instruction for the capsule file unit is issued in the first communication device 10a according to the operation instruction of the capsule user, the capsule control unit 16 of the capsule file unit performs the capsule control processing in the first communication device 10a. Perform (step S16) <capsule control processing step>.

  In this capsule control processing step, in response to a process execution request to the capsule file unit, the encapsulation is released and the main body program unit is started, the execution count is counted, and the execution count information is stored in the execution count storage And re-encapsulation after the execution of the main body program unit.

  On the other hand, based on the operation input by the settlement information user, the second communication device 10b performs a process of transmitting a settlement amount information acquisition request to the program billing management device 20 (step S17) <the settlement amount information acquisition request. Send step>.

  When receiving the settlement amount information acquisition request from the second communication device 10b, the program billing management apparatus 20 performs the second control process in response to the settlement amount information acquisition request (step S18) <second control process Step>.

  In this second control process, in response to the request for payment amount information acquisition, the capsule file portion is investigated and a process for calculating the payment amount is performed.

  Specifically, in the second control process, in order to acquire information in the capsule file part of the first communication device 10a (information on the number of executions of the execution number storage unit 14), the program charge management device 20 In response to the information acquisition request, a process of transmitting an execution frequency information acquisition request to the first communication device 10a is performed (step S18a) <execution frequency information acquisition request transmission step>.

  Subsequently, in the second control process, the first communication device 10a receives the execution frequency information acquisition request from the program billing management device 20, and when the capsule file unit receives the execution frequency information acquisition request, the capsule file unit In response to this execution frequency information acquisition request, the capsule control unit of the capsule controller releases the encapsulation, extracts the execution frequency information of the execution frequency storage unit 14 in the capsule file unit, The program is extracted, the execution count information and the main body program section are transmitted to the program billing management apparatus 20, and a control process for recapsulation is performed (step S18b) <execution count information transmission control step>.

  Next, in the second control process, the program billing management apparatus 20 receives the execution frequency information and the main body program unit from the first communication apparatus 10a.

  Further, in the second control process, the program billing management apparatus 20 refers to the program correspondence table information storage unit 21 based on the main body program unit, and acquires usage unit price information corresponding to the program name of the main body program unit. .

  In the second control process, the program billing management apparatus 20 calculates a settlement amount that is a billing total amount based on the usage unit price information and the execution frequency information.

  Subsequently, the program billing management apparatus 20 performs processing for transmitting the calculated settlement amount information to the second communication device 10b (step S19) <settlement amount information transmission step>.

  The second communication device 10b receives the settlement amount information from the program billing management device 20, and the settlement information user can refer to the settlement amount information.

  Details of the capsule control processing step, the first control processing step, and the second control processing step will be described below.

(Detailed processing of capsule control processing step)
First, detailed processing of the capsule control processing step of step S16 shown in FIG. 5 will be described in detail with reference to the flowchart of FIG. FIG. 6 is a flowchart showing an example of a processing procedure related to the capsule file unit in the program billing system according to the first embodiment of the present invention. It can also be said that this capsule control processing step is each function that the capsule control unit 16 (capsule execution processing program) performs processing when the capsule file unit 13 is executed.

  Here, in the capsule execution processing method of the present embodiment, the main body program storage in which the computer included in the first communication device 10a (capsule execution processing device) stores the main program section of the execution format for executing specific processing. It is intended to execute a capsule file part that encapsulates the means and an execution number storage means that counts the number of executions of the main body program part and stores information on the number of executions.

  In this capsule execution processing method, as a basic configuration, the computer included in the first communication device 10a (capsule execution processing device) is encapsulated to release the encapsulation in response to a processing execution request for the capsule file unit. A cancellation step (for example, step S101a shown in FIG. 5) and a computer included in the first communication device 10a (capsule execution processing device) are stored in the main body program storage unit in a state where the encapsulation is released. And an independent file generation step (for example, step S102 shown in FIG. 5) for generating an independent file in another storage area on the file system to which the capsule file portion belongs.

  Further, in this capsule execution processing method, the computer provided in the first communication device 10a (capsule execution processing device) performs the execution count counting in which the execution count storage unit increments the execution count information by one. Step (for example, step S105 shown in FIG. 5) and a child task activation processing step in which the computer provided in the first communication device 10a (capsule execution processing device) performs processing for activating the main body program unit as a child task ( For example, step S106 shown in FIG.

  Furthermore, in this capsule execution processing method, when the computer included in the first communication device 10a (capsule execution processing device) receives a task end notification from the child task, the independent file on the file system is deleted. When the independent file deletion processing step (for example, step S108 shown in FIG. 5) that performs processing and the computer included in the first communication device 10a (capsule execution processing device) deletes the independent file, the capsule file A re-encapsulation step (for example, step S110 shown in FIG. 5).

  More specifically, first, the computer included in the first communication device 10a (capsule execution processing device) performs processing for receiving a processing execution instruction (processing execution request) based on the operation input of the capsule user (processing execution request) ( Step S101) <Processing execution request receiving step>.

  And the computer with which the 1st communication apparatus 10a was equipped performs the process which cancels | releases encapsulation of a capsule file part (step S101a) <encapsulation release step>.

  Next, the computer provided in the first communication device 10a takes out the execution program (main program part) stored in the main program storage unit 15 and creates it as an independent file on the file system (step). S102) <Independent file generation step>.

  Further, the computer provided in the first communication device 10a performs a process of storing the execution file name of the execution program (main program part) in the variable X (step S103) <execution file name storage step>.

  Next, the computer included in the first communication device 10a performs processing for storing the value (first execution count information) stored in the execution count storage unit 14 in the variable Y (step S104) <first execution. Number information storage step>.

Subsequently, the computer included in the first communication device 10a performs a calculation of Y = Y + 1 (step S105) <execution count counting step>.
For example, if the value Y stored in the execution count storage unit 14 is 0 (first execution count information), the new Y value is 1 (second execution count information).

  Further, the computer included in the first communication device 10a performs a process of starting a child task using the execution file name stored in the variable X as an argument (step S106) <child task activation process step>.

  Then, the computer included in the first communication device 10a performs a process of waiting until a task end notification is received from the child task (step S107) <task end notification waiting step>.

  Thereafter, when the computer included in the first communication device 10a receives the task end notification in the standby state, it starts again, deletes the executable file stored in the variable X, and deletes the independent file on the file system. Processing is performed (step S108) <independent file deletion processing step>.

  And the computer with which the 1st communication apparatus 10a was equipped performs the process which stores the value of the variable Y in the execution frequency memory | storage part 14 (step S109) <2nd execution frequency information storage step>.

  Further, the computer included in the first communication device 10a performs re-encapsulation processing, and performs processing for generating a capsule file portion with the number of executions (step S110) <re-encapsulation step>.

  Here, depending on the operating system, the child task may be provided with a similar function under the name of a process or a thread instead of a task.

  The execution program stored in the main program storage unit 15 is generated on the file system as an independent file. In this case, if the execution program is generated as a normal file, the execution program is not deleted until the file is deleted. Duplicates may be created elsewhere by the user.

  Therefore, instead of generating as a normal file, you can set the attributes of a hidden file so that it is not displayed by file list software (Explorer.exe in Windows), or you can easily find it in the hierarchy of the file system By creating it in a difficult place, it is possible to add a device that prevents the user from easily copying. In another operating system, it is possible to add an attribute that prohibits copying. In that case, the attribute may be added.

(Detailed processing of the first control processing step)
Next, detailed processing of the first control processing step of step S12 shown in FIG. 5 will be described in detail with reference to the flowchart of FIG. FIG. 7 is a flowchart showing an example of a processing procedure related to the program billing registration unit in the program billing system according to the first embodiment of the present invention. It can also be said that the first control processing step is each function performed by the program charging registration unit 22 when the program charging registration unit 22 is executed.

  First, the program billing management apparatus 20 (the computer provided therein) instructs the registered user's third communication device 10c to register an execution program (main program part) as a target to be charged (main program part registration). Request) is performed (step S111) <main body program part registration request receiving step>. At this time, the computer performs a process of receiving the target execution program (main program part) and its usage unit price as arguments.

  Next, the computer included in the program billing management apparatus 20 performs a process of making the variable X refer to the execution program (main program part) received as an argument (step S112) <main program part reference step>.

  Subsequently, the computer included in the program billing management apparatus 20 performs a process of storing the usage unit price received as an argument in the variable Y (step S113) <Usage unit price information storage step>.

  Further, the computer included in the program billing management apparatus 20 performs a process of additionally registering the combination of the execution program (main program unit) referenced by the variable X and the variable Y in the program billing correspondence table of the program billing correspondence information storage unit 21. Perform (step S114) <program billing correspondence information registration processing step>.

  In addition, the computer included in the program billing management apparatus 20 performs a process of creating a new capsule file part (capsule). The computer included in the program billing management apparatus 20 performs a process for the variable Z to refer to the new capsule file part (step S115) <capsule file part body generation step>.

  Next, the computer included in the program billing management apparatus 20 performs a process of storing the execution program (main body program part) referred to by the variable X in the main body program storage part in the capsule file part referred to by the variable Z (step S116). <Main Program Program Capsule Storage Step>

  Further, the computer included in the program billing management apparatus 20 performs an initial setting process for storing 0 (zero) in the execution count storage section 14 in the capsule file section referred to by the variable Z (step S117) <execution count information. Initial setting step>.

  Furthermore, the computer included in the program billing management apparatus 20 performs processing for returning the value referred to by the variable Z to the user as the reference value of the newly created capsule file part (step S118) <capsule file part completion step> .

(Detailed processing of the second control processing step)
Next, detailed processing of the second control processing step of step S18 shown in FIG. 5 will be described in detail with reference to the flowchart of FIG. FIG. 8 is a flowchart showing an example of a processing procedure related to the program use charge settlement unit in the program charge system according to the first embodiment of the present invention. It can also be said that the second control processing step is a function that the program usage fee settlement unit 23 performs processing when the program usage fee settlement unit 23 is executed.

  First, the program billing management device 20 (the computer with which the billing management device 20 is provided) performs processing for receiving an instruction (settlement amount information acquisition request) for settlement of usage bills for an execution program from the second communication device 10b of the settlement information user. Perform (Step S121) <Settlement Amount Information Acquisition Request Accepting Step> At this time, the computer included in the program billing management apparatus 20 performs a process of receiving a capsule containing the target execution program as an argument.

  Next, the computer included in the program billing management apparatus 20 performs processing for referring to the capsule file part (capsule) received as an argument for the variable X (step S122) <capsule file part reference step>.

  Then, the computer included in the program billing management apparatus 20 performs a process of temporarily decapsulating the capsule file part in order to obtain information necessary for billing settlement (step S122a) <Encapsulation Temporary Release Step> .

  Next, the computer included in the program billing management apparatus 20 takes out the program stored in the main body program storage unit 14 in the capsule file section referred to by the variable X in order to obtain information necessary for billing settlement, and sets the variable Y (Step S123) <Billing settlement main body program part acquisition step>

  Subsequently, the computer included in the program billing management apparatus 20 refers to the program billing correspondence table in the program billing correspondence information storage unit 21, and matches the program whose variable Y refers to the program item in the program billing correspondence table. (Step S124) <Program item search step>.

  Here, if there is no corresponding program item in step S124, the computer included in program billing management apparatus 20 performs notification processing that explains to the user that there is no registered program, and ends (step S125). <Program non-registration notification step>.

  On the other hand, if there is a corresponding program item in step S124, the computer included in program billing management apparatus 20 extracts the value (usage unit price information) of the corresponding usage unit price item of the same set and stores it in variable Z. Processing is performed (step S126) <use unit price information acquisition step>.

  Further, the computer included in the program billing management apparatus 20 extracts the value (execution count information) of the execution count storage section 14 in the capsule file section referred to by the variable X, and performs a process of storing it in the variable U (step S127). <Capsule execution count information acquisition step>.

  Next, the computer included in the program billing management apparatus 20 calculates the value of (variable Z × variable U) and performs a process of outputting the billing total amount (step S128) <billing total amount calculation step>.

  Further, the computer included in the program billing management apparatus 20 performs recapsulation processing after billing settlement is completed, and performs processing for generating a capsule file portion at the number of executions (step S129) <settlement termination recapsulation. Step>.

  As described above, according to this embodiment, there is an effect that it is possible to measure the number of times of use for charging in a small program unit. Moreover, since it is not necessary to presuppose mounting of a specific DRM base as the mechanism, there is an effect that distribution is easy.

  Actually, in the case of a completely different operating system (for example, Linux, Windows, Mac), the capsule corresponding to the file system of each operating system must be generated or released. This can be solved by preparing multiple capsule creation and release mechanisms for each unit.

Here, a part of each block in the block diagrams shown in FIG. 1 and FIG. 4 is a software module that shows a state functionalized by the program when the computer executes various programs stored in an appropriate memory. It may be a configuration.
That is, the physical configuration is, for example, a computer or the like including one or a plurality of CPUs (or one or a plurality of CPUs and one or a plurality of memories), but the software configuration by each unit (means) is a CPU ( A plurality of functions exhibited by a computer are expressed as components by a plurality of units (means).
When a dynamic state (state in which each procedure constituting the program is executed) being executed by the program is functionally expressed, each unit (means) is configured in the CPU (computer). Become. In a static state in which the program is not executed, the entire program (or each program part included in the configuration of each unit) that realizes the configuration of each unit is stored in a storage area such as a memory.
The description of each part (means) described above can be interpreted as a computer functionalized by a program together with the function of the program, or a plurality of functions permanently functioning by specific hardware. Naturally, it can be interpreted that the device comprising the electronic circuit block is described. Therefore, these functional blocks can be realized in various forms by hardware only, software only, or a combination thereof, and is not limited to any one.

[Second Embodiment]
Next, a second embodiment according to the present invention will be described with reference to FIG. In the following, description of the substantially similar configuration of the first embodiment will be omitted, and only different parts will be described. FIG. 9 is a block diagram showing an example of the second embodiment of the program billing system of the present invention.

  In the present embodiment, a capsule file unit with authentication, a program billing registration unit with authentication, and a user billing settlement unit with authentication are configured.

(Overall configuration of program billing system)
Specifically, as shown in FIG. 9, the program billing system 100 according to the present embodiment includes a main body program unit 112 having an execution format for executing a specific process registered by a program creator, and the main body program unit. 112 is a capsule file portion with authentication 113 that has been encapsulated with authentication, and the capsule file portion with authentication 113 is generated so as to be provided to the user, according to the use of the capsule file portion with authentication 113 And a program billing management device 120 that performs billing management control.

  Here, the program billing system 100 of the present embodiment can also form the same communication infrastructure as that of the first embodiment shown in FIG. However, the first communication device is denoted by reference numeral 110a, the second communication device is denoted by reference numeral 110b, and the third communication device is denoted by reference numeral 110c (for example, FIG. 12).

  The main body program unit 112 is an executable program to be charged.

(Data structure of the capsule file with authentication)
The capsule file unit with authentication 113 uses the execution number storage unit 114 that is a counter that counts and records the number of executions, a main body program storage unit 115 that stores the main body program unit 112 in an execution format, and the main body program unit 112. A user authentication unit 116 (stored and recorded with a set (first authentication information) of a user name (first user identification information) and a password (first user authentication information) of the capsule user is stored and recorded. A first authentication information storage means), a creator name (second user identification information) and a password (second user) relating to the creator as an example of a settlement information user who can use the billing settlement information A creator authentication unit 117 (second authentication information storage unit) in which a set of authentication information) pairs (second authentication information) is stored and recorded, and the capsule file unit with authentication 113 In response to a physical execution request, the encapsulation is released and the main body program unit 112 is started, the number of executions is counted, and information on the number of executions is stored in the execution number storage unit 114, and the main body program unit And a capsule control unit 118 that performs re-encapsulation after the execution of 112 is completed.

  The capsule control unit 118 releases the encapsulation in response to a process execution request for the capsule file unit, prompts the capsule user to input first authentication information, and uses the capsule when using the capsule file unit. When the first authentication is performed based on the first input authentication information inputted by the user and the first authentication information of the first authentication information storage means, and the first authentication is permitted, the main body program The part can be activated.

(Configuration of program billing management device)
The program billing management apparatus 120 includes a program billing information storage unit 121 that stores the unit price information of the main body program unit and the program identification information for identifying the main body program unit 112 in association with each other, In response to a registration request for registering the main body program part (from the communication device 110c), the usage program unit information of the main body program part and the program identification information for identifying the main body program part are associated with each other as the charge object In response to the payment information acquisition request (from the payment information user's second communication device 110b) and the program billing registration unit 122 that registers and controls to generate the capsule file part, the capsule file part is examined. The main body based on the information on the number of executions of the execution number storage means and the registered unit price information A program use the accounting settlement unit 123 performs control to output the charge amount of the program portion configured to include a.

  The program billing correspondence information storage unit 121 has a program billing correspondence table composed of a set of a program name and a usage unit price.

  The authenticated program billing registration unit 122, from the third communication device 110c of the registered user, a set of a main program unit 112 as a certain target program and its usage unit price, and a user name that can use the main program unit 112. When receiving an instruction (main body program part registration request) for registering as a billing object using as arguments the name of the user and the set of passwords and the user name that can use the charge information and the set of passwords, the program charge corresponding information storage unit In the program billing correspondence table 121, the main body program unit 112 and the usage unit price are additionally registered.

  Further, the authenticated program billing registration unit 122 stores the main body program unit 112 in the main body program storage unit 115, and generates an authenticated capsule file unit 113 storing zero in the execution count storage unit 114. A combination of a user name that can be used by the unit 112 and its password is stored in the user authentication unit 116, and a combination of a user name that can use the billing information and its password is stored in the creator authentication unit 117 It is.

  Further, when generating the authenticated capsule file unit 113, the authenticated program billing registration unit 122 encrypts the main body program storage unit 115, the execution count storage unit 114, the user authentication unit 116, and the creator authentication unit 117. , Compression encoding, or a combination of these can be performed one or more times to perform encapsulation.

  Upon receipt of an instruction (settlement information acquisition request) for settlement of usage bills by using a certain authenticated capsule file unit 113 as an argument from the second communication device 110b of the settlement information user, the authenticated program use bill settlement unit 123 If it is specified that the user name and password are input to the settlement information user, and the set is not included in the creator authentication unit 117, the user is notified that the user does not have authority to use, and ends. .

  Further, if the set is included in the creator authenticating unit 117, the authenticated program use charge settlement unit 123 retrieves the program stored in the main body program storage unit 115 in the authenticated capsule file unit 113. Then, referring to the program billing correspondence table of the program billing correspondence information storage unit 121, the usage unit price of the retrieved program is checked, and the value of the number of executions of the execution number storage unit 114 in the authenticated capsule file unit 113 is extracted. Then, the value of the number of executions is added to the usage unit price to output the total charge amount.

That is, the program-use billing settlement unit 123 with authentication prompts the settlement information user to input second authentication information, and the second input authentication information input by the settlement information user when the billing settlement information is used. And the second authentication information stored in the second authentication information storage means (creator authentication unit 117), and when the second authentication is permitted, the number of times the capsule file unit is executed. Information on the number of executions can be acquired from the storage unit 114, and the settlement amount can be output.
Thereby, only the creator of the main body program part can confirm the information of the settlement amount.

  Further, when the authentication program use charge settlement unit 123 obtains the second authentication information of the second authentication information storage means (creator authentication unit 117), the capsule file unit with authentication 113 is temporarily released from the encapsulation. If the second authentication information is acquired and the second authentication is not permitted, re-encapsulation can be performed.

(Function of capsule control unit: configuration of capsule execution processing device)
Furthermore, the first communication device 110a in which the capsule file unit with authentication 113 is executed can constitute a capsule execution processing device as shown in FIG.
In this case, as shown in FIG. 11, the capsule controller 118 of the capsule execution processing device has the same configuration as that of the first embodiment, the decapsulation unit 119c, the independent file generation unit 119d, and the execution frequency count. In addition to the means 119e, the child task activation processing means 119f, the independent file deletion processing means 119g, and the reencapsulation means 119h, a first authentication control means 119a and a second authentication information provision control means 119b can be configured.

  The first authentication control means 119a prompts the capsule user to input the first authentication information in response to a process execution request for the capsule file portion, and inputs from the capsule user when using the capsule file portion. The first authentication is performed based on the first input authentication information to be performed and the first authentication information stored in the first authentication information storage means. When the first authentication is permitted, the encapsulation is released. Control can be performed.

  In response to a second authentication information acquisition request for acquiring the second authentication information, the second authentication information provision control unit 119b temporarily releases the encapsulation, and the second authentication information storage unit stores the second authentication information. The authentication information is taken out, and the second authentication information can be provided to the second authentication means for performing the second authentication performed when the billing settlement information is used, and re-encapsulation can be performed.

Here, the correspondence between the configuration requirements of the present embodiment and the configuration requirements of the present invention will be described.
The program charge registration unit with authentication 122 according to the present embodiment can constitute the “first control unit” according to the present invention. Further, the “programmed charge settlement unit 23 with authentication” can constitute the “second control means” in the present invention.
Furthermore, the “capsule control means” referred to in the present invention can be configured by the capsule control unit 118 of the present embodiment. Further, the “execution count storage means” according to the present invention can be configured by the execution count storage section 114 of the present embodiment. Furthermore, the “main program storage means” according to the present invention can be configured by the main program storage unit 115 of the present embodiment.
Furthermore, the “first authentication information storage unit” according to the present invention can be configured by the user authentication unit 116 of the present embodiment. The creator authentication unit 118 according to the present embodiment can constitute the “second authentication information storage unit” according to the present invention.

(Outline of program billing system)
The program billing system 100 configured as described above generally operates as follows.
First, the program billing management apparatus 120 receives a set of a main program unit 112 and a unit price for use as a target program from the third communication apparatus 110c of the registered user, and a user name that can use the main program unit 112. And an instruction (main body program part registration request) for registering it as an object of charging with an argument of a set of passwords and a user name that can use charging information and a set of passwords.
Then, the program charge registration unit 122 with authentication of the program charge management apparatus 120 uses the program name of the main body program unit 112 and the usage in the program charge correspondence table of the program charge correspondence information storage unit 121 according to the main body program part registration request. Register additional unit prices.

  Next, the program billing registration unit 122 with authentication of the program billing management device 120 stores the main body program unit 112 in the main body program storage unit, and the execution count storage unit 114 stores an authenticated capsule file unit 113 storing zero. Generate.

  Further, the program billing registration unit 122 with authentication of the program billing management apparatus 120 stores a set of user names and passwords that can be used by the main body program unit 112 in the user authentication unit 116, so that billing information can be used. A pair of possible user names and their passwords is stored in the creator authentication unit 117, and the capsule file unit with authentication 113 is generated.

  The program billing management apparatus 120 processes the generated capsule file unit with authentication 113 so that it can be provided to the capsule user by downloading or the like.

  When the capsule user's first communication device 110a obtains the authenticated capsule file unit 113 from the program billing management device 120 by downloading or the like, and instructs the authenticated capsule file unit 113 to execute a specific process, first, authentication is performed. The capsule control unit 118 of the capsule file unit 113 instructs the user to input a user name and password. If the set is not included in the user authentication unit 116, the capsule control unit 118 has authority to use. Notify and exit.

  On the other hand, if the set is included in the user authentication unit 116, the capsule control unit 118 of the capsule file unit with authentication 113 proceeds to the next and extracts the program stored in the main body program storage unit 115. Thus, it is created on the file system of the first communication device 110a as an independent file.

  Next, the capsule control unit 118 of the capsule file unit with authentication 113 increments the count of the execution count storage unit 114 by one, starts the created main body program as a child task, and waits until the child task ends. .

  Subsequently, when the capsule control unit 118 of the capsule file unit with authentication 113 receives a task end notification from the child task, the capsule control unit 118 deletes the independent file created on the file system and ends.

  On the other hand, when the second communication device 110b of the settlement information user obtains information related to the settlement of the usage fee, the second communication device 110b instructs the program billing management device 120 to settle the usage fee ( (Settlement information acquisition request) is transmitted.

The program usage charge settlement unit 123 with authentication of the program billing management device 120 instructs the settlement information user's second communication device 110b to settle the usage fee with a certain capsule file unit with authentication 113 as an argument (accounting information). When the acquisition request is received, it is specified that the user name and password are input to the second communication device 110b of the settlement information user.
Here, the program usage charge settlement unit 123 with authentication of the program billing management apparatus 120 uses the combination of the user name and password input at the second communication device 110b as the capsule file with authentication of the first communication device 110a. If it is not included in the creator authentication unit 117 of the unit 113, the second communication device 110b is notified that there is no authority to use, and the process ends.

  On the other hand, the program use billing settlement unit 123 with authentication of the program billing management device 120 is configured such that the input user name and password combination is included in the creator authentication unit 117 of the capsule file unit with authentication 113 of the first communication device 110a. Included in the main body program storage unit 115 in the capsule file unit with authentication 113 of the first communication device 110a.

  Then, the program usage charge settlement unit 123 with authentication refers to the program billing correspondence table of the program billing correspondence information storage unit 121 and checks the usage unit price of the extracted program.

  Further, the program usage charge settlement unit 123 with authentication of the program billing management apparatus 120 extracts the value of the number of executions of the execution number storage unit 114 in the capsule file unit with authentication 113 of the first communication apparatus 110a, and performs program billing management. The total number of executions is output by adding the value of the number of executions to the usage unit price in the device 120.

In such a configuration, as shown in FIG. 9, in addition to the configuration of the first embodiment, a program for performing authentication is incorporated in the capsule, and the capsule file is executed by the first communication device 110a. Then, the startup program starts executing in a self-extracting type. First, the authentication program is executed. After the authentication, the main body program is immediately started to be executed. On the other hand, the one to which the number of times of thawing is added is written in the original capsule.
Also, in the case of billing settlement, by authenticating with the authentication program, only authorized persons can see the billing process information, thereby improving the reliability.

(About processing procedure)
Next, various processing procedures in the program billing system having the above-described configuration will be described in detail with reference to FIGS. FIG. 12 is a network sequence diagram showing an example of the entire processing procedure in the program billing system according to the first embodiment of the present invention.

The program billing method according to the present embodiment is intended for a method in which a computer included in the program billing management apparatus 120 performs billing according to the use of an execution form main body program unit that executes specific processing. .
In this program billing method, as a basic configuration, the computer included in the program billing management apparatus 120 counts the number of executions of the main body program storage means storing the main body program portion and the main body program portion, and obtains information on the number of executions. A first control processing step (for example, step S22 shown in FIG. 12) for generating a capsule file portion encapsulating the execution frequency storage means to be stored, and a computer provided with the program billing management apparatus 120 include the capsule file portion. Providing the user with a providing step (for example, step S23 shown in FIG. 12), and the computer included in the program billing management apparatus 120 examines the capsule file portion in response to the payment information acquisition request regarding the main body program portion. And the execution stored in the execution number storage means Second control processing step (for example, step S28 shown in FIG. 12, etc.) for outputting the settlement amount of the main body program part of the capsule file part based on the number information and the usage unit price information of the main body program part registered in advance ) And.

  Here, in the first control processing step, program identification information for identifying the main body program unit and the main body program unit in response to a registration request for registering the main body program unit by the computer included in the program charge management apparatus 120 Can be registered in association with the usage unit price information.

  Further, in this program billing method, a computer included in the program billing management apparatus 120 releases the encapsulation and starts the main body program unit in response to a process execution request for the capsule file unit, and determines the number of executions. A capsule control processing step (for example, step S26 shown in FIG. 12) for counting and storing the execution count information in the execution count storage unit and performing re-encapsulation after the execution of the main body program unit is further performed. Can have.

  The capsule file unit includes first authentication information storage means for storing first authentication information related to a capsule user who uses the main body program unit. In this case, in the capsule control processing step in the program billing method, the capsule user is prompted to input first authentication information, and the first input authentication information input by the capsule user when the capsule file unit is used. And the first authentication information stored in the first authentication information storage means. When the first authentication is permitted, the main body program unit can be activated.

  Furthermore, the capsule file unit may include a second authentication information storage unit that stores second authentication information related to a payment information user who can use the billing payment information. In this case, in the second control processing step, the second authentication information is urged to be input to the settlement information user by the second settlement information user and input by the settlement information user when the billing settlement information is used. And second authentication information based on the second authentication information storage means, and when the second authentication is permitted, the execution count storage means of the capsule file portion stores the execution count. Information can be obtained, and the settlement amount can be output.

(Overall processing)
A more specific overall process including these steps is as shown in FIG. As shown in the figure, first, the registered user registers the main body program unit with respect to the program billing management apparatus 120 using the third communication apparatus 110c.

Specifically, the registered user is a main body program part, a program name that is an example of program identification information for identifying the main body program part, usage unit price information, and a user name that can use the authenticated capsule file part 113 (first number). 1 user identification information) and its password (first user authentication information) pair (first authentication information), the name of the creator of the main program part or the user name of the settlement information user (second use) User identification information) and a password (second user authentication information) pair (second authentication information) are input by the third communication device 110c.
These pieces of information are transmitted as a body program part registration request from the third communication device 110c to the program management apparatus (step S21) <body program part registration request transmission step>.

  Next, when receiving the main body program part registration request from the third communication apparatus 110c, the program billing management apparatus 120 performs the first control process in response to the main body program part registration request (step S22) <first 1 control processing step>.

In the first control process, in response to the main body program part registration request, the program name and the unit price information are associated with each other and stored in the program correspondence table information storage unit 121 to perform program registration.
Further, in the first control process, in response to a main body program part registration request, a process of encapsulating the main body program part to generate a capsule file part with authentication 113 is performed.

  When generating the capsule file unit with authentication 113, a main body program unit storage unit 115 storing the main body program unit, an execution number storage unit 114 for storing information on the number of executions of the main body program unit, a first The main body program unit is decapsulated based on a processing instruction to the user authentication unit 116 that stores the authentication information, the creator authentication unit 117 that stores the second authentication information, and the capsule file unit with authentication 113. And a capsule control unit 118 that performs control for counting the number of executions and re-encapsulation.

Here, in the first control process, in response to the main body program part registration request, the user authentication part 116 is provided with a user name (first user identification information) that can use the capsule file part with authentication 113. Processing for storing the pair (first authentication information) of the password (first user authentication information) is performed.
Further, in the first control process, in response to the main body program part registration request, the creator authenticating part 117 is informed of the creator name of the main body program part or the user name of the settlement information user (second user identification information). And a password (second user authentication information) pair (second authentication information) is stored.

  Next, the program billing management apparatus 120 performs a process of making the generated capsule file part with authentication available to the user by downloading or the like (step S23) <providing step>.

  Then, the first communication device 110a performs a process of transmitting an authenticated capsule file part acquisition request to the program billing management device 120 based on an operation input by the capsule user (step S24) <capsule file with authentication Copy acquisition request transmission step>.

  When the program charging management apparatus 120 receives the authenticated capsule file part acquisition request from the first communication apparatus 110a, the program charging management apparatus 120 determines that the authenticated capsule file part is in response to the authenticated capsule file part acquisition request. Is transmitted to the first communication device 110a (step S25) <authenticated capsule file portion transmission step>.

  Further, the first communication device 110a performs processing for receiving the capsule file portion with authentication from the program billing management device 120. Thereafter, when a processing instruction is issued to the capsule file with authentication according to an operation instruction of the capsule user, a capsule control process is performed (step S26) <capsule control process step>.

  In this capsule control process, the capsule user is prompted to input the first authentication information, and the first input authentication information input from the capsule user when using the capsule file portion and the first authentication information storage means Based on the first authentication information, the first authentication may be performed, and when the first authentication is permitted, a first authentication control step of starting the main body program unit may be included.

  On the other hand, the second communication device 110b of the settlement information user transmits a settlement amount information acquisition request to the program billing management device 120 based on the operation input of the settlement information user (step S27) <the settlement amount information. Acquisition request transmission step>.

  When receiving the settlement amount information acquisition request from the second communication device 110b, the program billing management apparatus 120 performs the second control process in response to the settlement amount information acquisition request (step S28) <second control process Step>.

  In the second control process, the capsule file portion is investigated and the settlement amount is calculated in response to the settlement amount information acquisition request.

Specifically, in the second control process, a second authentication process is performed.
In the second authentication process, first, in response to the payment amount information acquisition request, the program billing management apparatus 120 performs a process of transmitting the second authentication information acquisition request to the first communication apparatus 110a (step S28a). <Second authentication information acquisition request transmission step>

  In the second authentication process, when the first communication device 110a receives the second authentication information acquisition request from the program billing management device 120, the capsule file portion with authentication of the first communication device 110a And the pair of the second user identification information and the second user authentication information, which is the second authentication information, is extracted from the creator authentication unit 117, and the second authentication is performed with respect to the program billing management apparatus 120. A control process for transmitting and re-encapsulating information is performed (step S28b) <second authentication information provision control step>.

  In the second authentication process, program billing management apparatus 120 also transmits a second authentication information input request to second communication apparatus 110b (step S28c) <second authentication information input request transmission step> . When the second communication device 110b receives the second authentication information input request, the settlement information user can input the second authentication information from the second communication device 110b.

  In the second authentication process, the second input authentication information (second input user identification information and second input user authentication information) input from the second communication device 110b by the settlement information user is further obtained. Then, the second communication device 110b performs processing to transmit to the program billing management device 120 (step S28d) <second input authentication information transmission step>.

In the second authentication process, next, the program billing management apparatus 120 includes the second authentication information (second user identification information and second user authentication information) from the first communication apparatus 110a, The second input authentication information is based on the second input authentication information (second input user identification information and second input user authentication information) from the second communication device 110b. Determine if it is inside.
As a result of this determination, when it is determined that the second input authentication information is included in the second authentication information, the subsequent processing is continued.
On the other hand, as a result of this determination, if it is determined that the second input authentication information is not included in the second authentication information, the program billing management apparatus 120 notifies the settlement information user of the second communication apparatus 110b. On the other hand, the user is notified that he / she does not have the authority to acquire the settlement information, and ends the process.

  In addition, in the second control process, in order to obtain information in the capsule file part of the first communication device 110a (information on the number of executions of the execution number storage unit 114), the program billing management apparatus 120 obtains the payment amount information. In response to the request, processing for transmitting an execution frequency information acquisition request to the first communication apparatus 110a is performed (step S28e) <execution frequency information acquisition request transmission step>.

  Subsequently, in the second control process, the first communication device 110a receives the execution frequency information acquisition request from the program billing management device 120, and when the capsule file unit receives the execution frequency information acquisition request, the capsule file unit In response to this execution frequency information acquisition request, the capsule control unit of the capsule controller releases the encapsulation, extracts the execution frequency information of the execution frequency storage unit 114 in the capsule file unit, and also stores the main body program in the main body program unit storage unit 115 The program is extracted, the execution count information and the main body program section are transmitted to the program billing management apparatus 120, and a control process for recapsulation is performed (step S28f) <execution count information transmission control step>

  Next, in the second control process, the program billing management apparatus 120 receives the execution frequency information and the main body program part from the first communication apparatus 110a.

  Further, in the second control process, the program billing management apparatus 120 refers to the program correspondence table information storage unit 121 based on the main body program unit, and acquires usage unit price information corresponding to the program name of the main body program unit. .

  In the second control process, the program billing management apparatus 120 calculates a settlement amount that is a billing total amount based on the usage unit price information and the execution frequency information.

  Subsequently, the program billing management apparatus 120 performs processing for transmitting the calculated settlement amount information to the second communication device 10b (step S29) <settlement amount information transmission step>.

  The second communication device 110b receives the settlement amount information from the program billing management device 120, and the settlement information user can refer to the settlement amount information.

  Details of the capsule control processing step, the first control processing step, and the second control processing step will be described below.

(Detailed processing of capsule control processing step)
First, detailed processing of the capsule control processing step of step S26 shown in FIG. 12 will be described in detail with reference to the flowchart of FIG. FIG. 13: is a flowchart which shows an example of the process sequence relevant to the capsule file part with authentication in the program billing system by the 2nd Embodiment of this invention. It can also be said that this capsule control processing step is each function that the capsule control unit 118 (capsule execution processing program) performs processing when the authenticated capsule file unit 113 is executed.

  Here, in the capsule execution processing method according to the present embodiment, the main body program in which the computer included in the first communication device 110a (capsule execution processing device) stores the main program section in an execution format for executing specific processing. The object is to execute a capsule file part that encapsulates storage means and execution number storage means for counting the number of executions of the main body program part and storing information on the number of executions.

  In this capsule execution processing method, as a basic configuration, the computer included in the first communication device 110a (capsule execution processing device) is encapsulated to release the encapsulation in response to a processing execution request for the capsule file unit. A cancellation step (for example, step S201a shown in FIG. 13) and a computer included in the first communication device 110a (capsule execution processing device) are stored in the main body program storage unit in a state where the encapsulation is released. And an independent file generation step (for example, step S206 shown in FIG. 13) for generating an independent file in another storage area on the file system to which the capsule file portion belongs.

  Further, in this capsule execution processing method, the computer included in the first communication device 110a (capsule execution processing device) performs the execution count counting in which the execution count information in the execution count storage means is incremented by one. Step (for example, step S209 shown in FIG. 13) and a child task activation processing step in which a computer provided in the first communication device 110a (capsule execution processing device) performs processing for activating the main body program unit as a child task ( For example, step S210 shown in FIG.

  Furthermore, in this capsule execution processing method, when the computer included in the first communication device 110a (capsule execution processing device) receives a task end notification from the child task, the independent file on the file system is deleted. When the independent file deletion processing step (for example, step S212 shown in FIG. 13) that performs processing and the computer included in the first communication device 110a (capsule execution processing device) deletes the independent file, the capsule file A re-encapsulation step (for example, step S214 shown in FIG. 13).

In addition, the capsule file unit may include a first authentication information storage unit that stores first authentication information related to a capsule user who uses the main body program unit.
In this case, in this capsule execution processing method, the computer included in the first communication device 110a (capsule execution processing device) makes a first response to the capsule user in response to a processing execution request for the capsule file unit. Prompt the input of authentication information, and perform the first authentication based on the first input authentication information input by the capsule user when using the capsule file portion and the first authentication information of the first authentication information storage means. And when the first authentication is permitted, a first authentication control step (for example, a step including step S202 to step S204 shown in FIG. 13) for performing the control for releasing the encapsulation can be included.

Furthermore, the capsule file unit may include a second authentication information storage unit that stores second authentication information related to a payment information user who can use the billing payment information.
In this case, the capsule execution processing method temporarily cancels the encapsulation in response to a second authentication information acquisition request for acquiring the second authentication information, and the second authentication information storage unit executes the second authentication information storage unit. A second authentication information provision control step of taking out the authentication information, providing the second authentication information to a second authentication means for performing second authentication performed when using the billing settlement information, and performing reencapsulation (For example, step S28b shown in FIG. 12 and the like).

  Specifically, as shown in FIG. 13, first, a computer provided in the first communication device 110a (capsule execution processing device) performs processing for receiving a processing execution instruction (processing execution request) from a user. (Step S201) <Processing execution request receiving step>.

  Next, the computer included in the first communication device 110a performs a process of releasing the encapsulation of the capsule file portion (step S201a) <encapsulation release step>.

  Subsequently, the computer included in the first communication device 110a performs processing for prompting the user to input a user name and a password (first authentication information) (step S202) <first authentication information. Input support step>.

  Then, when the capsule user inputs the user name and password, the computer included in the first communication device 110a performs a process of receiving the input information (first input authentication information) (step S203). <First input authentication information acquisition step>.

  Next, the computer included in the first communication device 110a has a set (a set of input user name and password: first input authentication information) registered in the user authentication unit 116. Processing for checking whether or not it exists (step S204) <first input authentication information checking step>.

  Here, in the process of step S204, when it is determined that the computer included in the first communication device 110a does not exist, the computer included in the first communication device 110a notifies that the computer does not have authority to use. (Step S205) <first authentication non-permission notification step>, the process proceeds to step S214 and ends.

  On the other hand, if it is determined in step S204 that the computer included in the first communication device 110a is included in the user authentication unit 116, the computer included in the first communication device 110a is An execution program (main program part) stored in the main program storage unit 115 is taken out and created on the file system as an independent file (step S206) <independent file generation step>.

  Next, the computer included in the first communication device 110a performs a process of storing the execution file name of the execution program (main program part) in the variable X (step S207) <execution file name storage step>.

  Further, the computer included in the first communication device 110a performs processing for storing the value (first execution count information) stored in the execution count storage unit 114 in the variable Y (step S208) <first execution count. Information storage step>.

  Subsequently, the computer included in the first communication device 110a performs a process of adding 1 to the variable Y (Y = Y + 1) (step S209) <execution count counting step>. For example, if the value Y stored in the execution count storage unit 114 is 0 (first execution count information), the new Y value is 1 (second execution count information).

  In addition, the computer included in the first communication device 110a performs a process of starting a child task using the execution file name stored in the variable X as an argument (step S210) <child task activation process step>.

  Next, the computer included in the first communication device 110a performs a process of waiting until a task end notification is received from the child task (step S211) <task end notification waiting step>.

  In addition, when the computer included in the first communication device 110a receives a task end notification in the standby state, it starts again, deletes the executable file stored in the variable X, and deletes the independent file on the file system. Processing is performed (step S212) <independent file deletion processing step>.

  Furthermore, the computer included in the first communication device 110a performs a process of storing the value of the variable Y in the execution count storage unit 114 (step S213) <second execution count information storage step>.

  Further, the computer included in the first communication device 110a performs re-encapsulation processing, and performs processing for generating a capsule file portion with the number of executions (step S214) <re-encapsulation step>.

  Here, the above steps S202 to S204 can be referred to as a “first authentication control step”.

(Detailed processing of the first control processing step)
Next, detailed processing of the first control processing step of step S22 shown in FIG. 12 will be described in detail with reference to the flowchart of FIG. FIG. 14 is a flowchart showing an example of a processing procedure related to the authenticated program billing registration unit in the program billing system according to the second embodiment of the present invention. It can also be said that the first control processing step is a function performed by the authenticated program charge registration unit 122 when the authenticated program charge registration unit 122 is executed.

First, an instruction for registering an execution program (main program part) as a target to be charged from the third communication device 110c of the registered user by the computer included in the program charge management apparatus 120 (main program part registration request). A process of accepting is performed (step S221) <main body program part registration request receiving step>.
At this time, the computer included in the program billing management apparatus 120 can use the target execution program and its usage unit price, the set of the user name and password that can use the program, and the billing information. Process to receive a pair of user name and password as an argument.

  Next, the computer included in the program billing management apparatus 120 performs processing for referring to the variable X1 the execution program (main program part) received as an argument (step S222) <main program part reference step>.

  Subsequently, the computer included in the program billing management apparatus 120 performs processing for storing the usage unit price received as an argument in the variable X2 (step S223) <Usage unit price information storage step>.

  Further, the computer included in the program billing management apparatus 120 performs a process of storing, in the variable U1, a user name (first user identification information) that can use the program received as an argument (step S224) < First user identification information storing step>.

  Next, the computer included in the program billing management apparatus 120 performs processing for storing a password (first user authentication information) of a user name that can use the program received as an argument in the variable U2 (step S225). <First user authentication information storage step>.

  Further, the computer included in the program billing management apparatus 120 performs processing for storing, in the variable V1, a user name (second user identification information) that can use the billing information received as an argument (step S226). <Second user identification information storing step>.

  In addition, the computer included in the program billing management apparatus 120 performs a process of storing a password (second user authentication information) of a user name that can use the billing information received as an argument in the variable V2 (second user authentication information). Step S227) <Second user authentication information storing step>.

  Further, the computer included in the program billing management apparatus 120 performs a process of additionally registering the combination of the execution program (main program unit) referenced by the variable X1 and the variable X2 in the program billing correspondence table of the program billing correspondence information storage unit 121. Perform (step S228) <Program billing correspondence information registration processing step>.

  Next, the computer included in the program billing management apparatus 120 creates a new capsule file part (capsule). The computer performs processing for the variable Z to refer to the new capsule file part (step S229) <capsule file part body generation step>.

  Subsequently, the computer included in the program billing management apparatus 120 performs a process of storing the execution program (main body program part) referred to by the variable X1 in the main body program storage part 115 in the capsule file part referred to by the variable Z (step). S230) <Main Program Program Unit Capsule Storage Step>.

  Further, the computer included in the program billing management apparatus 120 performs an initial setting process for storing 0 (zero) in the execution count storage unit 114 in the capsule file unit referred to by the variable Z (step S231) <execution count information. Initial setting step>.

  In addition, the computer included in the program billing management apparatus 120 performs a setting control process for storing the set of the variables U1 and U2 (first authentication information) in the user authentication unit 116 (step S232) <first Authentication information setting control step>.

  Further, the computer included in program billing management apparatus 120 performs setting control processing for storing a set of variable V1 and variable V2 (second authentication information) in creator authentication unit 117 (step S233) <second authentication. Information setting control step>.

  Further, the computer included in program billing management apparatus 120 performs a process of returning the value referred to by variable Z to the user as a reference value of the newly created capsule file part (step S234) <capsule file part completion step>.

(Detailed processing of the second control processing step)
Next, detailed processing of the second control processing step of step S28 shown in FIG. 12 will be described in detail with reference to the flowchart of FIG. FIG. 15 is a flowchart showing an example of a processing procedure related to the authenticated program use billing settlement unit in the program billing system according to the second embodiment of the present invention. It can also be said that the second control processing step is a function performed by the authenticated program usage fee settlement unit 123 when the authenticated program usage fee settlement unit 123 is executed.

  First, the computer included in the program billing management device 120 issues an instruction (payment amount information acquisition request) for the settlement of the usage bill for a certain execution program (main program unit) from the second communication device 110b of the settlement information user. Processing for accepting is performed (step S241) <accounting amount information acquisition request accepting step>. At this time, the computer performs processing for receiving a capsule containing the target execution program as an argument.

  Next, the computer included in the program billing management apparatus 120 performs a process of making the variable X refer to the capsule file part (capsule) received as an argument (step S242) <capsule file part reference step>.

  Subsequently, the computer included in the program billing management apparatus 120 performs a process for prompting the second communication apparatus 110b of the settlement information user to input the user name and password (second authentication information) (step). S243) <Second authentication information input support step>.

  In addition, when the payment information user inputs the user name and password in the second communication apparatus 110b, the computer included in the program billing management apparatus 120 receives the input information (second input authentication information). A process of accepting (receiving) from the second communication device 110b is performed (step S244) <second input authentication information acquisition step>.

  Then, the computer included in the program billing management apparatus 120 makes an inquiry to the capsule file part of the first communication device 110a, and temporarily cancels the encapsulation of the capsule file part in order to acquire information necessary for billing settlement. (Step S244a) <Encapsulation temporary release step>.

  Next, the computer included in the program billing management apparatus 120 uses the set (input user name and password set: second input authentication information) as the authentication of the creator of the capsule file section referenced by the variable X. Processing for checking whether or not it exists in the part 116 is performed (step S245) <second input authentication information checking step>.

  Here, in the process of step 245, when it is determined that the computer included in the program charge management apparatus 120 does not exist in the creator authentication unit 117, the computer included in the program charge management apparatus 120 uses the computer. Processing to notify that there is no authority is performed (step S246) <second authentication non-permission notification step>, and the process proceeds to step S253 and ends.

  On the other hand, if it is determined in step S245 that the computer included in the program charge management apparatus 120 is included in the creator authentication unit 117, the computer included in the program charge management apparatus 120 The main body program part stored in the main body program storage part in the capsule file part referred to by X is extracted and stored in the variable Y (step S247) <charging settlement main body program part acquisition step>.

  Next, the computer included in the program billing management apparatus 120 refers to the program billing correspondence table in the program billing correspondence information storage unit 121 and matches the program referenced by the variable Y in the program item in the program billing correspondence table. (Step S248) <Program item search step>.

  If it is determined in step S248 that there is no corresponding item, the computer included in the program billing management apparatus 120 performs notification processing that explains to the user that there is no registered program (step S249). ) <Program non-registration notification step>, the process proceeds to step S253 and ends.

  When it is determined in step S248 that there is a corresponding one, the computer included in the program billing management apparatus 120 extracts the value (usage unit price information) of the corresponding usage unit price item of the same set, and the variable Z (Step S250) <Usage unit price information acquisition step>.

  Next, the computer included in the program billing management apparatus 120 retrieves the value (execution count information) of the execution count storage section 114 in the capsule file section referred to by the variable X and performs a process of storing it in the variable U (step S251). <Capsule execution count information acquisition step>.

  Subsequently, the computer included in the program billing management apparatus 120 calculates the value of (variable Z × variable U) and outputs a billing total amount (step S252) <billing total amount calculation step>.

  Further, the computer included in the program billing management apparatus 120 performs re-encapsulation processing, and performs processing for generating a capsule file portion with the number of executions (step S253).

As described above, according to the present embodiment, there is an effect that an information leakage countermeasure can be taken in a small program unit while exhibiting the same operational effects as the first embodiment.
In other words, the data file is usually a problem due to information leakage, but the program file is also a valuable intellectual property. By providing this protection mechanism, even if the encapsulated file is leaked or leaked, only the authorized person can execute the program in this encapsulated file. This has the effect of protecting the leak.

  Other configurations, other steps or functions, and the operation and effects thereof are the same as those in the first embodiment described above. In the above description, the operation content of each step described above and the components of each unit may be programmed and executed by a computer.

[Third Embodiment]
Next, a third embodiment according to the present invention will be described with reference to FIGS. In the following, description of the substantially similar configuration of the above-described embodiment will be omitted, and only different parts will be described. FIG. 16 is a block diagram showing an example of the third embodiment of the program billing system of the present invention.

  In each of the above-described embodiments, the registered user inputs registration of a program through the first communication device, the capsule user uses the capsule file unit through the second communication device, and the settlement is performed by the third communication device. An example of a configuration of a program billing system in which an information user obtains settlement information and performs various control processes by the program billing management device, but in this embodiment, when the registered user and the settlement information user are the same, The example of a structure in the case of inputting the registration of a program and acquisition of payment information with a 2nd communication apparatus is shown.

  Specifically, as shown in FIG. 16, the program billing system 200 of the present embodiment is a first communication device 210a used by a capsule user and a registered user as well as a settlement information user. A second communication device 210b used by the user and a program charge management device 220 are included.

  As shown in FIG. 17, the program billing system 200 operates in steps S22 to S22 in the second embodiment other than step S321 in which a main body program part registration request is transmitted from the second communication device 210b. Similar to S29, steps S322 to S329 are performed.

  Other configurations, other steps or functions, and the effects thereof are the same as those in the above-described embodiment. In the above description, the operation content of each step described above and the components of each unit may be programmed and executed by a computer.

[Fourth Embodiment]
Next, a fourth embodiment according to the present invention will be described with reference to FIGS. In the following, description of the substantially similar configuration of the first embodiment will be omitted, and only different parts will be described. FIG. 18 is a block diagram showing an example of the fourth embodiment of the program billing system of the present invention.

  In this embodiment, when the capsule user and the adjustment information user are the same, a configuration example is shown in which the adjustment information is acquired by using the capsule file portion in the first communication device.

  Specifically, as shown in FIG. 18, the program billing system 300 according to the present embodiment includes a first communication device 310a used by a user who is a capsule user and a settlement information user, and a registration. A second communication device 310b used by the user and a program charge management device 320 are included.

In the operation of this program billing system 300, as shown in FIG. 19, after performing steps S421 to S426 as in the second embodiment, the first communication device 310a makes a settlement amount information acquisition request. Transmit (step S427).
In the second control processing step S428, the program billing management apparatus 320 performs a process of transmitting a second authentication information input request to the first communication apparatus 310a (step S428a).
When the first communication device 310a receives the second authentication information input request, the settlement information user who is the capsule user can input the second authentication information from the first communication device 310a. .

The first communication device 310a transmits the input second input authentication information (second input user identification information and second input user authentication information) to the program billing management device 320. (Step S428b).
The program billing management apparatus 320 holds second input authentication information (second input user identification information and second input user authentication information).

Next, the program billing management apparatus 320 performs a process of transmitting a second authentication information acquisition request to the first communication apparatus 310a (step S428c).
When the first communication device 310a receives the second authentication information acquisition request from the program billing management device 320, the capsule file unit with authentication of the first communication device 310a releases the encapsulation, and the second authentication information And the second authentication information is transmitted to the program billing management apparatus 320, and control processing for re-encapsulation is performed (step S428d).

  Further, the program billing management apparatus 320 includes the second authentication information (second user identification information and second user authentication information) from the first communication apparatus 310a and the first authentication information from the first communication apparatus 310a. Whether or not the second input authentication information is in the second authentication information is determined based on the second input authentication information (second input user identification information and second input user authentication information). To do.

  The program billing management apparatus 320 performs authentication in this way, calculates settlement information as in the second embodiment, and transmits the settlement information to the first communication apparatus 310a (step S429).

  Other configurations, other steps or functions, and the effects thereof are the same as those in the above-described embodiment. In the above description, the operation content of each step described above and the components of each unit may be programmed and executed by a computer.

[Fifth Embodiment]
Next, a fifth embodiment according to the present invention will be described with reference to FIGS. In the following, description of the substantially similar configuration of the above-described embodiment will be omitted, and only different parts will be described. FIG. 20 is a block diagram showing an example of the fifth embodiment of the program billing system of the present invention.

  In the present embodiment, a configuration example is shown in which the registered user and the settlement information user are the same, and the program billing management apparatus inputs the registration of the program and acquires the settlement information.

  Specifically, as shown in FIG. 20, the program billing system 400 according to the present embodiment is a first communication device 410a used by a capsule user and a payment information user as well as a registered user. And a program billing management apparatus 420 used by the user.

  In the operation of the program billing system 400, as shown in FIG. 21, <main body program part registration request transmission step> required in the second embodiment before the first control processing step S522. Is no longer necessary.

Further, the <payment amount information acquisition request transmission step> required in the second embodiment is not required before the second control processing step S528.
Furthermore, in the second control processing step S528, the <second authentication information input request transmission step> and the <second input authentication information transmission step> required in the second embodiment are unnecessary. Become.
Furthermore, the <settlement amount information transmission step> after the second control processing step S528 is not necessary.

  Other configurations, other steps or functions, and the effects thereof are the same as those in the above-described embodiment. In the above description, the operation content of each step described above and the components of each unit may be programmed and executed by a computer.

[Sixth Embodiment]
Next, a sixth embodiment according to the present invention will be described with reference to FIGS. In the following, description of the substantially similar configuration of the above-described embodiment will be omitted, and only different parts will be described. FIG. 22 is a block diagram showing an example of the sixth embodiment of the program billing system of the present invention.

  In the present embodiment, when the capsule user and the settlement information user are the same, the first communication device uses the capsule file portion to acquire the settlement information, and the registered user pays the program charge. An example of the configuration when registration is performed by the management apparatus is shown.

  Specifically, as shown in FIG. 22, the program billing system 500 according to the present embodiment includes a first communication device 510a used by a user who is a capsule user and a settlement information user, and a registration. And a program charge management device 520 used by the user.

In the operation of the program billing system 500, as shown in FIG. 23, <main body program part registration request transmission step> required in the fourth embodiment before the first control processing step S622. Is no longer necessary.
Subsequent steps S622 to S629 of each process are performed in the same manner as steps S422 to S429 of the fourth embodiment.

  Other configurations, other steps or functions, and the effects thereof are the same as those in the above-described embodiment. In the above description, the operation content of each step described above and the components of each unit may be programmed and executed by a computer.

[Seventh Embodiment]
Next, a seventh embodiment according to the present invention will be described with reference to FIG. In the following, description of the substantially similar configuration of the above-described embodiment will be omitted, and only different parts will be described. FIG. 24 is a network sequence diagram showing an example of the seventh embodiment of the program billing system of the present invention.

In the present embodiment, a configuration example in the case where the second authentication process performed in the second control processing step of the fifth embodiment is performed not on the program billing management apparatus side but on the first communication apparatus side. Show.
In this case, the capsule control means of the capsule file section needs to include the second authentication processing means.

In the operation of such a program billing system, as shown in FIG. 24, the first communication device 510a performs the second authentication process in step S727a. In the second authentication process, the authentication process is performed based on the second input authentication information and the second authentication information in the capsule file portion.
As a result of the second authentication process, if the authentication is permitted, the first communication device 510a performs a process of transmitting the second authentication permission information to the program billing management apparatus 520 (step S727b).
Thereafter, the second control processing step S729 is performed as in the fifth embodiment.

  Other configurations, other steps or functions, and the effects thereof are the same as those in the above-described embodiment. In the above description, the operation content of each step described above and the components of each unit may be programmed and executed by a computer.

[Eighth Embodiment]
Next, an eighth embodiment according to the present invention will be described with reference to FIG. In the following, description of the substantially similar configuration of the above-described embodiment will be omitted, and only different parts will be described. FIG. 25 is a flowchart showing an example of the eighth embodiment of the program billing system of the present invention.

  The processing of each unit in the program billing system having the configuration as in each of the above-described embodiments can be realized as a method, and various processing procedures as the program billing method will be described with reference to FIG.

  In particular, it is assumed that each process is performed by a single computer. As shown in FIG. 25, the program billing method of the present embodiment is such that the computer performs billing according to the use of the main program unit in the execution format for executing a specific process. (Step S801), a capsule control processing step (step S802), and a second control processing step (step S803).

  In the first control processing step, in response to a registration request for registering the main body program part, the computer registers program identification information for identifying the main body program part and usage unit price information of the main body program part in association with each other. In addition, control is performed to generate a capsule file part that encapsulates the main body program storage means storing the main body program part and the execution number storage means for counting the number of executions of the main body program part and storing information on the number of executions. .

  In the capsule control processing step, in response to a process execution request to the capsule file unit, the computer releases the encapsulation and starts the main body program unit, counts the number of executions, and obtains the information on the number of executions. The program is stored in the execution count storage unit, and re-encapsulation is controlled after the execution of the main program unit.

  In the second control processing step, the computer investigates the capsule file part used in response to the payment information acquisition request regarding the main body program part, and registers the usage number information registered in the execution number storage means. Based on the unit price information, control is performed to output the settlement amount of the main body program part of the capsule file part.

  Other configurations, other steps or functions, and the effects thereof are the same as those in the above-described embodiment. In the above description, the operation content of each step described above and the components of each unit may be programmed and executed by a computer.

[Other variations]
Also, although the apparatus and method according to the present invention have been described according to some specific embodiments thereof, the embodiments described in the text of the present invention can be used without departing from the spirit and scope of the present invention. Various modifications are possible.

For example, the number, position, shape, and the like of the constituent members are not limited to the above-described embodiment, and can be set to a suitable number, position, shape, and the like in practicing the present invention.
That is, in the above-described embodiment, there is a case in which one capsule file part has one main body program part, one execution number storage part, one user authentication part, and one creator authentication part. Although shown, the present invention does not limit the number thereof, and a plurality of main body program units 714-1 to 714 -n, a plurality of units are included in one capsule file unit as in the capsule file unit 713 shown in FIG. A configuration example in which the execution number storage units 715-1 to 715-n are configured.

  Furthermore, the capsule file unit may have a structure in which a plurality of subcapsule file units 813-1 to 813-n are multiplexed by the multiplexed capsule control unit 820 as in the capsule file unit 810 illustrated in FIG. 27. In this case, the subcapsule file units 813-1 to 813-n can have the same structure as the capsule file unit of the second embodiment. Further, the multiplexed capsule control unit 820 can include the function of the capsule control unit of the second embodiment.

  Furthermore, the capsule file part may be multiplexed in a nested configuration example.

  Further, the capsule file unit is not limited to the main body program unit, the execution frequency storage unit, the user authentication unit, and the creator authentication unit, but may include other additional information and other units. For example, usage unit price information may be included as other incidental information, and a billing settlement unit may be included as each other unit. That is, a configuration in which charging can be calculated on the capsule side may be used.

  Furthermore, the information on the number of executions may be obtained when the program billing management apparatus acquires it from the capsule file part, or may be transmitted spontaneously from the capsule file part side. In this case, the capsule file unit may include an execution frequency information transmission unit.

  Further, the billing settlement calculation function (means) of the main body program unit may be provided in the capsule control unit of the capsule file unit.

  Further, the capsule file unit may be provided with usage time information storage means for counting usage time information and storing usage time information and other usage related information in addition to the execution frequency information. In this case, the capsule control means may be provided with usage time information counting means for counting the usage time information of the main body program unit. Further, the second control means may perform billing settlement based on both the usage count and usage time. The program billing correspondence information storage unit (means) may store usage time unit price information (regardless of time unit such as day, hour, minute, second) corresponding to the main body program unit.

  Furthermore, the configuration is not limited to the Web-accessible configuration in the client / server system, but may be a configuration that can be used in P2P and a configuration that includes one PC.

(program)
Further, the software program of the present invention that realizes the functions of the above-described embodiments is a program corresponding to the processing unit (processing means), functions, etc. shown in the various block diagrams in each of the above-described embodiments, Each processing program processed in a program corresponding to a processing procedure, processing means, function, etc. shown in a flowchart, a sequence diagram, etc., a method (step) generally described in the present specification, a process described, The whole or each part of data (for example, a program billing correspondence table of the program billing correspondence information storage unit) is included.

Specifically, the billing management program of the present invention causes the computer to execute billing processing according to the use of the main program unit in the execution format.
The billing management program generates a capsule file unit that encapsulates a main body program storage unit that stores the main body program unit and an execution number storage unit that counts the number of executions of the main body program unit and stores information on the number of executions. In response to a first control function (for example, a function such as reference numeral 22 shown in FIG. 1) and a payment information acquisition request related to the main body program part, the capsule file part is examined and stored in the execution number storage means A second control function for outputting the settlement amount of the main body program part of the capsule file part based on the information on the number of executions and the usage unit price information of the main body program part registered in advance (for example, reference numeral 23 shown in FIG. 1) Etc.) can be executed by the computer.

  Here, in the first control function, in response to a registration request for registering the main body program portion, program identification information for identifying the main body program portion and usage unit price information of the main body program portion are registered in association with each other. You can also.

The capsule execution processing program of the present invention stores main program storing means for storing a main program part of an execution format for executing a specific process, and stores information on the number of executions by counting the number of executions of the main program part. The computer executes the execution process of the capsule file portion encapsulating the execution frequency storage means.
In response to a process execution request for the capsule file unit, the capsule execution processing program releases the encapsulation (for example, a function such as reference numeral 17a shown in FIG. 4) and the encapsulation is released. In the state, the main body program part stored in the main body program storage means is taken out, and an independent file generation function (for example, the code shown in FIG. 4) for generating an independent file in another storage area on the file system to which the capsule file part belongs. 17b etc.) can be executed by the computer.

  The capsule execution processing program includes an execution number counting function (for example, a function such as reference numeral 17c shown in FIG. 4) for performing a counting process for incrementing the execution number information of the execution number storage means by one, and the main body program. Upon receiving a child task activation processing function (for example, a function such as reference numeral 17d shown in FIG. 4) that performs a process of starting a part as a child task and a task end notification from the child task, the independent file on the file system is An independent file deletion processing function (for example, a function such as reference numeral 17e shown in FIG. 4) that performs a deletion process, and a reencapsulation function that performs a process for recapsulating the capsule file portion when the independent file is deleted ( For example, it is possible to cause the computer to execute a function including a function such as a reference numeral 17f illustrated in FIG.

  A program such as an accounting management program may be in any form such as an object code, a program executed by an interpreter, script data supplied to the OS, and the like. The program can be implemented in a high level procedural or object oriented programming language, or in assembly or machine language as required. In either case, the language may be a compiler or interpreted language.

As a method of supplying the program, it is also possible to provide the program from an external device that is communicably connected to the computer via an electric communication line (whether wired or wireless).
For example, the program can be supplied by connecting to a homepage on the Internet using a browser on a computer and downloading the program itself or a compressed file including an automatic installation function from the homepage to a recording medium such as a hard disk.
It can also be realized by dividing the program into a plurality of files and downloading each file from a different home page.

  According to the program of the present invention, the program (CPU) is read from a storage medium such as a ROM storing the program and executed, or the program is downloaded to the computer via communication means. If executed after that, the above-described apparatus according to the present invention can be realized relatively easily. When the software of the apparatus is embodied as an embodiment of the idea of the invention, it naturally exists and is used on a storage medium storing such software.

Moreover, the program is the same without any question about the copying stage of the primary copy product, the secondary copy product, etc. If the program is supplied using a communication line, the communication line becomes a transmission medium and the present invention is used.
Furthermore, the dependent claims in the apparatus may be configured to correspond to the dependent claims in the method and the program.

  Moreover, the structure which recorded the above-mentioned program on the information recording medium may be sufficient. The information recording medium stores an application program including the above-described program, and the computer can read the application program from the information recording medium and install the application program on the hard disk. Thus, the program can be provided by being recorded on an information recording medium such as a magnetic recording medium, an optical recording medium, or a ROM. Use of an information recording medium in which such a program is recorded in a computer constitutes a convenient information processing apparatus.

  Furthermore, the “information recording medium” is a medium that dynamically holds a program for a short time (transmission medium), such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. Or a transmission wave), a volatile memory inside a computer system serving as a server or a client in that case, and those holding a program for a certain period of time.

  In addition, when an OS running on a computer, an RTOS on a terminal (for example, a mobile phone) performs part or all of the processing, the same functions as those in the above embodiment can be realized and An effect can be obtained.

  Further, the above embodiment is not limited to the client server system, but may be a system based on peer-to-peer (Peer To Peer) communication in which terminals form a network without using a server and transmit and receive data to and from each other. At this time, the program charge management apparatus may be a master terminal in the peer-to-peer system.

  In addition, the “system” in the above embodiments refers to a logical collection of a plurality of devices, and it does not matter whether the devices of each configuration are in the same housing. For this reason, this invention may be applied to the system comprised from a some apparatus, and may be applied to the apparatus which consists of one apparatus. The “system” may include hardware such as an OS and peripheral devices.

  Furthermore, as an information processing apparatus on which the above-described program is mounted, the management apparatus is not limited to a personal computer, for example, but is an apparatus composed of various servers, an EWS (engineering workstation), a medium-sized computer, a mainframe, or a combination thereof. Groups and so on. In addition to the above examples, the communication device and the capsule execution processing device include a portable information terminal, various mobile terminals, a PDA, a mobile phone, a wearable information terminal, various televisions, DVD recorders, and various audio devices (such as a portable device). In addition, a configuration that can be used also from a remote controller with a display function thereof, a home appliance equipped with various information communication functions, a game machine having a network function (communication function), or the like may be used.

  Further, in the present specification, the steps shown in the flowchart include processes that are executed in parallel or individually even if they are not necessarily processed in time series, as well as processes that are executed in time series according to the described procedure. It is a waste.

  Furthermore, the functions of the program such as each means of the apparatus, each function, and the procedure function of each step may be achieved by dedicated hardware (for example, a dedicated semiconductor circuit). Some of these functions may be processed by hardware, and other functions among all functions may be processed by software. In the case of dedicated hardware, each unit may be formed by an integrated circuit such as an LSI. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them. The LSI may include other functional blocks. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. Further, if integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology.

  Further, in “communication”, wireless communication and wired communication as well as communication in which wireless communication and wired communication are mixed, that is, wireless communication is performed in a certain section and wired communication is performed in another section. There may be. Further, communication from one device to another device may be performed by wired communication, and communication from another device to one device may be performed by wireless communication.

  This communication includes a communication network. As a network constituting the communication network, for example, a cellular phone network (including base stations and switching systems), a public phone network, an IP phone network, an ISDN network, etc. Any hardware configuration such as communication mode using IP protocol), intranet, LAN (including Ethernet: registered trademark, gigabit Ethernet, etc.), WAN, optical fiber communication network, power line communication network, and various dedicated line networks compatible with broadband But you can. In addition to the TCP / IP protocol, the network may be any communication protocol such as a network using various communication protocols, a virtual network constructed in software, or a network including all similar networks. The network is not limited to a wired network, but includes a wireless (including satellite communication, various high-frequency communication means, etc.) network (for example, a single carrier communication system such as a simple telephone system or a cellular phone, W-CDMA, or IEEE 802.11b) Network including a spread spectrum communication system such as a wireless LAN, a multi-carrier communication system such as IEEE802.11a and HiperLAN / 2, etc., or a combination of these may be used. It may be a system connected to a network. Further, the network may take any form such as point-to-point, point-to-multipoint, multipoint-to-multipoint.

  In addition, in the communication structure between the management apparatus and other communication apparatuses, the types of interfaces formed on one or both of them are, for example, a parallel interface, a USB interface, IEEE 1394, a network such as a LAN or WAN, and the like. Any interface that is similar or that will be developed in the future may be used.

  Further, the method of encapsulating the main body program part and providing it to the user and charging according to the use is not necessarily limited to an actual apparatus, and it can be easily understood that this method also functions. For this reason, the invention relating to the method is not necessarily limited to a substantial apparatus, and there is no difference that the method is also effective. In this case, a program charge management apparatus, a capsule execution processing apparatus, a program charge system, and the like can be included as an example for realizing the method.

  By the way, such an apparatus may exist alone, or may be used in a state of being incorporated in a certain device (for example, an electronic device). Including embodiments. Therefore, it can be changed as appropriate, such as software or hardware. When the software of the apparatus is embodied as an embodiment of the idea of the invention, it naturally exists on the storage medium storing the software and is used.

  Furthermore, it may be a case where a part is software and a part is realized by hardware, and a part is stored on a storage medium and is read as needed. It may be as a thing. When the present invention is implemented by software, a configuration using hardware or an operating system may be used.

The scope of the invention is not limited to the illustrated example.
Further, the above embodiments include various stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. That is, examples include combinations of the above-described embodiments, or any of them and any of the modifications.
In addition, an embodiment based on a configuration in which some of the configuration requirements are deleted from all the configuration requirements shown in the embodiment, and a technical scope based on the configuration may be an invention.

In addition, the description so far including each of the embodiments and the modifications thereof is intended to facilitate the understanding of the present invention. The embodiments of the invention are merely shown as examples of implementation, are illustrative, not limiting, and can be modified and / or modified as appropriate.
The present invention can be implemented in various forms based on its technical idea or its main features, and the technical scope of the present invention should not be construed in a limited manner by each embodiment and its modifications. It will not be.
Therefore, each element disclosed above is intended to include all design changes and equivalents belonging to the technical scope of the present invention.

  The present invention can be used in all computers.

It is a block diagram which shows an example of the schematic structure of the whole program billing management apparatus in the program billing system by the 1st Embodiment of this invention. It is a block diagram which shows an example of the whole structure of the program billing system by the 1st Embodiment of this invention. It is explanatory drawing for demonstrating the principle of the program accounting system shown in FIG. It is a block diagram which shows an example of schematic structure of the capsule execution processing apparatus which performs a capsule file part shown in FIG. It is a network sequence diagram which shows an example of the whole process sequence in the program billing system by the 1st Embodiment of this invention. It is a flowchart which shows an example of the process sequence relevant to the capsule file part in the program billing system by the 1st Embodiment of this invention. It is a flowchart which shows an example of the process sequence relevant to the program charge registration part in the program charge system by the 1st Embodiment of this invention. It is a flowchart which shows an example of the process procedure relevant to the program use charge adjustment part in the program charge system by the 1st Embodiment of this invention. It is a block diagram which shows an example of schematic structure of the whole program billing management apparatus in the program billing system by the 2nd Embodiment of this invention. It is explanatory drawing for demonstrating the principle of the program accounting system shown in FIG. It is a block diagram which shows an example of schematic structure of the capsule execution processing apparatus which performs the capsule file part with authentication shown in FIG. It is a network sequence diagram which shows an example of the whole process sequence in the program billing system by the 1st Embodiment of this invention. It is a flowchart which shows an example of the process sequence relevant to the capsule file part with authentication in the program billing system by the 2nd Embodiment of this invention. It is a flowchart which shows an example of the process procedure relevant to the program charge registration part with authentication in the program charge system by the 2nd Embodiment of this invention. It is a flowchart which shows an example of the process procedure relevant to the program use charge settlement part with authentication in the program charge system by the 2nd Embodiment of this invention. It is a block diagram which shows an example of schematic structure of the whole program billing management apparatus in the program billing system by the 3rd Embodiment of this invention. It is a network sequence diagram which shows an example of the whole process sequence in the program billing system by the 3rd Embodiment of this invention. It is a block diagram which shows an example of the schematic structure of the whole program billing management apparatus in the program billing system by the 4th Embodiment of this invention. It is a network sequence diagram which shows an example of the whole process sequence in the program billing system by the 4th Embodiment of this invention. It is a block diagram which shows an example of the schematic structure of the whole program billing management apparatus in the program billing system by the 5th Embodiment of this invention. It is a network sequence diagram which shows an example of the whole process sequence in the program billing system by the 5th Embodiment of this invention. It is a block diagram which shows an example of the schematic structure of the whole program billing management apparatus in the program billing system by the 6th Embodiment of this invention. It is a network sequence diagram which shows an example of the whole process sequence in the program billing system by the 6th Embodiment of this invention. It is a network sequence diagram which shows an example of the whole process sequence in the program billing system by the 7th Embodiment of this invention. It is a flowchart which shows an example of the whole process sequence in the program billing system by the 8th Embodiment of this invention. It is explanatory drawing which shows an example of schematic structure of the capsule file part in the program billing system by other embodiment of this invention. It is explanatory drawing which shows an example of schematic structure of the capsule file part in the program billing system by other embodiment of this invention. It is explanatory drawing for demonstrating the mechanism of DRM of related technology.

Explanation of symbols

1 Program billing system 10a First communication device (capsule execution processing device)
10b Second communication device 10c Third communication device
12 Main body program part 13 Capsule file part
14 Execution count storage unit (execution count storage means)
15 Main program storage (main program storage means)
16 Capsule control unit (capsule control means)
17a Decapsulation means 17b Independent file generation means 17c Execution count counting means 17e Child task activation means 17f Recapsulation means 20 Program charge management device 21 Program charge corresponding information storage section 22 Program charge registration section (first control means)
23 Program usage charge settlement section (second control means)

100 program billing system 110a first communication device (capsule execution processing device)
119a First authentication control means
119b Second authentication information provision control means

112 Main body program part 113 Capsule file part with authentication 114 Execution number storage part (execution number storage means)
115 Main program storage (main program storage means)
116 User authentication unit (first authentication information storage means)
117 Creator authentication unit (second authentication information storage means)
118 Capsule control unit (capsule control means)
DESCRIPTION OF SYMBOLS 120 Program charge management apparatus 121 Program charge corresponding | compatible information storage part 122 Program charge registration part with authentication (1st control means)
123 Program-use charge settlement section with authentication (second control means)

Claims (25)

A program billing management apparatus that manages billing according to the use of an execution form main body program part,
First control means for generating a capsule file part that encapsulates a main body program storage means for storing the main body program part and an execution number storage means for counting the number of executions of the main body program part and storing information on the number of executions. When,
In response to the payment information acquisition request related to the main body program part, the capsule file part is examined, and based on the information on the number of executions stored in the execution number storage means and the usage unit price information of the main body program part registered in advance. Second control means for outputting the settlement amount of the main body program part of the capsule file part,
A program charge management device comprising: In the program billing management apparatus according to claim 1,
The capsule file part
In response to a process execution request for the capsule file part, the encapsulation is released and the main body program part is started, the execution count is counted, and the execution count information is stored in the execution count storage means. A program charge management apparatus comprising capsule control means for performing re-encapsulation after completion of execution of a main body program unit. In the program billing management apparatus according to claim 2,
The capsule file part
A first authentication information storing means for storing first authentication information relating to the capsule user who uses the main body program unit;
The capsule control means includes
In response to a processing execution request for the capsule file part, the encapsulation is released, the capsule user is prompted to input the first authentication information, and the capsule user is input when using the capsule file part. When the first authentication is performed based on the first input authentication information to be performed and the first authentication information stored in the first authentication information storage unit, and the first authentication is permitted, A program charge management apparatus for starting up the main body program unit. In the program billing management apparatus according to claim 3,
The capsule file part
A second authentication information storage means for storing second authentication information relating to a payment information user capable of using the billing payment information;
The second control means includes
The second authentication information is urged to be input to the settlement information user, the second input authentication information input by the settlement information user when the billing settlement information is used, and the second authentication information storage means 2nd authentication is performed based on the second authentication information stored in the file, and when the second authentication is permitted, information on the number of executions is obtained from the execution number storage means of the capsule file unit. A program billing management apparatus for obtaining and outputting the settlement amount. In the program billing management apparatus according to claim 4,
The second control means includes
When acquiring the second authentication information stored in the second authentication information storage means, the capsule file part is released, the second authentication information is acquired, and the second authentication information is acquired. A program charge management apparatus characterized by re-encapsulation in a case where permission is not permitted. In the program billing management apparatus according to claim 5,
The second control means includes
When acquiring the execution count information from the execution count storage means of the capsule file section, the capsule file section is released, the execution count information is acquired, and re-encapsulated. Program charge management device. In the program billing management apparatus according to claim 2,
The capsule control means includes
In response to a processing execution request from the capsule user, the main body program part stored in the main body program storage means is extracted, and an independent file is generated in another storage area on the file system to which the capsule file part belongs. , Increasing the count of the execution count storage means by one, starting the file of the main body program part as a child task, and receiving the task end notification from the child task, deleting the independent file on the file system A program charge management apparatus characterized in that the program charge management apparatus is terminated. In the program billing management apparatus according to claim 1,
The second control means includes
The main body program part in the capsule file part is taken out, the usage unit price information of the taken out main body program part is checked from the registered information, and the information on the number of executions in the execution number storage means in the capsule file part is taken out. The program billing management apparatus characterized in that the information on the number of executions is added to the usage unit price information to output a settlement amount. In the program billing management apparatus according to claim 1,
The first control means includes
A program charge management apparatus characterized in that encapsulation is performed by a process of performing encryption, compression encoding, or a combination thereof one or more times. A program charge management device that generates a capsule file part that encapsulates a main body program part in an executable format, and manages charge control in accordance with the use of the capsule file part;
A first communication device that is formed to be communicable with the program charge management device and used by a capsule user who uses the capsule file unit;
Including
The program charge management device comprises:
First control means for generating a capsule file part that encapsulates a main body program storage means for storing the main body program part and an execution number storage means for counting the number of executions of the main body program part and storing information on the number of executions. When,
In response to the payment information acquisition request related to the main body program part, the capsule file part is examined, and based on the information on the number of executions stored in the execution number storage means and the usage unit price information of the main body program part registered in advance. Second control means for outputting the settlement amount of the main body program part of the capsule file part,
Including
The capsule file unit used in the first communication device is:
In response to a process execution request for the capsule file part, the encapsulation is released and the main body program part is started, the execution count is counted, and the execution count information is stored in the execution count storage means. A program billing system comprising capsule control means for performing re-encapsulation after completion of execution of a main body program unit. The program billing system according to claim 10, wherein
The capsule file part
A first authentication information storing means for storing first authentication information relating to the capsule user who uses the main body program unit;
The capsule control means in the first communication device is
In response to a processing execution request for the capsule file part, the encapsulation is released, the capsule user is prompted to input the first authentication information, and the capsule user is input when using the capsule file part. When the first authentication is performed based on the first input authentication information to be performed and the first authentication information stored in the first authentication information storage unit, and the first authentication is permitted, A program billing system for starting up the main body program unit. The program billing system according to claim 11, wherein
A second communication device capable of communicating with the program billing management device used by a billing information user who can use billing billing information;
The capsule file unit used in the first communication device is:
A second authentication information storage means for storing second authentication information relating to a payment information user capable of using the billing payment information;
The second control means of the program billing management apparatus includes:
The second authentication information is urged to be input to the second communication device, and the second input authentication information inputted by the adjustment information user when the billing adjustment information is used, and the second authentication information storage When the second authentication is performed based on the second authentication information stored in the means and the second authentication is permitted, the execution count information from the execution count storage means of the capsule file portion And paying the settlement amount to the second communication device. The program billing system according to claim 12,
A third communication device capable of communicating with the program charge management device used by a registered user who registers the main body program unit;
The first control means of the program billing management apparatus includes:
Capsules with authentication by storing the first authentication information and the second authentication information inputted from the third communication device in the first authentication information storage means and the second authentication information storage means, respectively. A program charging system characterized by generating a file part. Capsule for executing a capsule file section encapsulating a main body program storing means for storing a main body program section in an execution format and an execution count storage means for counting the number of executions of the main body program section and storing information on the number of executions An execution processing device,
In response to a process execution request for the capsule file portion, decapsulation means for decapsulating the encapsulation;
Independent file generating means for taking out the main body program part stored in the main body program storage means and generating an independent file in a storage area managed by the file system to which the capsule file part belongs in the state where the encapsulation is released ,
Execution number counting means for performing a counting process for increasing the information on the number of executions stored in the execution number storage means by one;
Child task activation processing means for performing processing for activating the main body program part as a child task;
Upon receiving a task end notification from the child task, independent file deletion processing means for performing processing for deleting the independent file on the file system;
When the independent file is deleted, re-encapsulation means for performing a process of re-encapsulating the capsule file part;
A capsule execution processing device comprising: The capsule execution processing device according to claim 14,
The capsule file unit further includes first authentication information storage means for storing first authentication information related to a capsule user who uses the main body program unit,
When the encapsulation is released, the capsule user is prompted to input the first authentication information, and the first input authentication information input by the capsule user when using the capsule file part, The first authentication is performed based on the first authentication information stored in the first authentication information storage means, and generates the independent file when the first authentication is permitted. A capsule execution processing apparatus further comprising a control unit. The capsule execution processing device according to claim 15,
The capsule file unit further includes second authentication information storage means for storing second authentication information related to a payment information user who can use the billing payment information,
In response to a second authentication information acquisition request for acquiring the second authentication information, the encapsulation is temporarily released, and the second authentication information stored in the second authentication information storage unit is extracted. , Further comprising second authentication information provision control means for providing the second authentication information to a second authentication means for performing second authentication performed when the billing settlement information is used, and for performing reencapsulation. A capsule execution processing device characterized by the above. A program billing method in which a computer performs billing according to the use of an execution form main body program part,
A computer generates a capsule file part that encapsulates a main body program storage means storing the main body program part and an execution number storage means for counting the number of executions of the main body program part and storing information on the number of executions. Control processing steps of
A providing step in which the computer provides the capsule file part to a user;
In response to a payment information acquisition request related to the main body program unit, the computer investigates the capsule file unit, information on the number of executions stored in the execution number storage means, and usage unit price information of the main body program unit registered in advance A second control processing step for outputting a settlement amount of the main body program part of the capsule file part based on
A program billing method comprising: The program billing method according to claim 17,
In response to a processing execution request for the capsule file unit, the computer releases the encapsulation and starts the main body program unit, counts the number of executions, and stores the information on the number of executions in the execution number storage unit. A program billing method further comprising a capsule control processing step of performing re-encapsulation after the execution of the main body program unit. The program billing method according to claim 18,
The capsule file unit further includes first authentication information storage means for storing first authentication information related to a capsule user who uses the main body program unit,
In the capsule control processing step,
In response to a processing execution request for the capsule file part, the encapsulation is released, the capsule user is prompted to input the first authentication information, and the capsule user is input when using the capsule file part. When the first authentication is performed based on the first input authentication information to be performed and the first authentication information stored in the first authentication information storage unit, and the first authentication is permitted, A program charge management method, wherein the main body program unit is activated. The program charge management method according to claim 19,
The capsule file unit further includes second authentication information storage means for storing second authentication information related to a payment information user who can use the billing payment information,
In the second control processing step,
The second authentication information is urged to be input to the settlement information user, the second input authentication information input by the settlement information user when the billing settlement information is used, and the second authentication information storage means 2nd authentication is performed based on the second authentication information stored in the file, and when the second authentication is permitted, information on the number of executions is obtained from the execution number storage means of the capsule file unit. A program billing management method comprising: obtaining and outputting the settlement amount. The computer executes a capsule file unit that encapsulates a main body program storage unit that stores a main body program unit in an executable format and an execution number storage unit that counts the number of executions of the main body program unit and stores information on the number of executions. A capsule execution processing method to process,
A decapsulation step in which the computer releases the encapsulation in response to a process execution request for the capsule file unit;
The computer retrieves the main body program part stored in the main body program storage means in the state where the encapsulation is released, and generates an independent file in another storage area on the file system to which the capsule file part belongs. A file generation step;
An execution frequency counting step in which the computer performs a counting process for incrementing the information of the execution frequency stored in the execution frequency storage means by one;
A child task activation processing step in which the computer performs a process of activating the main body program part as a child task;
When the computer receives a task end notification from the child task, an independent file deletion processing step for performing processing for deleting the independent file on the file system;
When the computer deletes the independent file, a re-encapsulation step of performing a process of re-encapsulating the capsule file portion;
A capsule execution processing method comprising: The capsule execution processing method according to claim 21, wherein
The capsule file unit further includes first authentication information storage means for storing first authentication information related to a capsule user who uses the main body program unit,
When the encapsulation is released, the computer prompts the capsule user to input the first authentication information, and the first input authentication information input by the capsule user when the capsule file unit is used And a first authentication based on the first authentication information stored in the first authentication information storage means, and when the first authentication is permitted, the independent file is generated. A capsule execution processing method, further comprising an authentication control step. The capsule execution processing method according to claim 22,
The capsule file unit further includes second authentication information storage means for storing second authentication information related to a payment information user who can use the billing payment information,
In response to a second authentication information acquisition request for acquiring the second authentication information, the encapsulation is temporarily released, and the second authentication information stored in the second authentication information storage unit is extracted. And a second authentication information provision control step of providing the second authentication information to a second authentication means for performing second authentication performed at the time of using the billing settlement information and performing reencapsulation. A capsule execution processing method characterized by the above. A billing management program for causing a computer to execute billing processing in accordance with the use of an execution form main body program part,
A first control function for generating a capsule file unit that encapsulates a main body program storage unit that stores the main body program unit and an execution number storage unit that counts the number of executions of the main body program unit and stores information on the number of executions When,
In response to the payment information acquisition request related to the main body program part, the capsule file part is examined, and based on the information on the number of executions stored in the execution number storage means and the usage unit price information of the main body program part registered in advance. A second control function for outputting the settlement amount of the main body program part of the capsule file part,
An accounting management program for causing a computer to execute a function including An execution process of a capsule file portion encapsulating a main body program storing means for storing a main body program portion in an execution format and an execution number storage means for counting the number of executions of the main body program portion and storing the number of execution times. A capsule execution processing program to be executed by
In response to a process execution request for the capsule file part, a decapsulation function for releasing the encapsulation;
Independent file generation function for taking out the main body program part stored in the main body program storage means in the released state and generating an independent file in another storage area on the file system to which the capsule file part belongs When,
An execution number counting function for performing a counting process for incrementing the information of the execution number stored in the execution number storage means by one;
A child task start processing function for performing processing for starting the main body program part as a child task;
Upon receiving a task end notification from the child task, an independent file deletion processing function for performing processing to delete the independent file on the file system;
When the independent file is deleted, a re-encapsulation function for performing a process of re-encapsulating the capsule file part;
A capsule execution processing program for causing a computer to execute a function including

Images