JP2002149614A - Agent-type license management system and component distribution system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an agent-type license management system which is simple in license management in the case of using a license management object and reasonable also for a user and a component distribution system using this agent- type license management system. SOLUTION: In the agent-type license management system for performing license management for using the license management object based on carrying on of an agent object transmitted from a server through communication line, the server is provided with a seed generation means for generating a seed as the agent object required for using the license management object and a license management means for performing license management by transmitting the seed generated by the seed generation means to the license management object. The seed transmitted to the license management object incorporates a logic program to be consumed by using the license management object.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to software software,
An agent-type license management system that uses an agent object to manage license usage by using a license management object such as a component or a network home appliance, and a component distribution system that distributes components using the agent-type license management system About.

[0002]

2. Description of the Related Art Hitherto, as typified by an ASP (application service provider), a service for renting contents, application software, and the like on a network has been provided. In such a service, license management according to the rental period or license management according to the usage amount of content, application software, and the like during the rental period is performed.

[0003]

However, in the case of the license management method according to the rental period, the user must
Even if you do not use software, you have to pay the usage fee, which makes you hesitate to rent because of the overpriced feeling. On the other hand, in the case of the license management method according to the usage amount, the above problem is solved, but the network between the service providing side and the user side has to be constantly connected and monitored, and there is a problem that it is complicated. . from now on,
Temporary use of various services is expected to increase due to the expansion of the ASP business including the distribution of contents using a network, the rental of components used for creating programs, and the spread of network home appliances. However, as described above, there is no efficient and reliable license management mechanism for such a business.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and has an agent type license management system in which license management when using a license management object is simple and satisfactory to a user. It is an object to provide a component distribution system using a license management system.

[0005]

To solve the above-mentioned problems, the following means are provided. Hereinafter, the names and reference numerals in parentheses correspond to the names and reference numerals in the embodiment. The invention according to claim 1 uses the target object based on seed information transmitted and received by an agent object moving between a server (for example, the component distribution device 2) and the license management object via the communication lines 6 and 7. An agent-type license management system 1 that performs license management for the license management system, wherein the server generates a seed required as a unit for using the license management target (for example, a seed generation unit 215).
a), transmission means (for example, a seed supply unit 215c) for enclosing the seed generated by the seed generation means in a mobile agent object and transmitting the license management target, and a server program on the network. A license management unit (for example, a license management unit 216) for monitoring the movement of the agent and performing license management based on the collection of the seed information, wherein the mobile agent is provided between the license management object and the server. Is transferred by including the seed, thereby transmitting and receiving the seed to and from the license management object. The seed is characterized by incorporating a logic program that consumes the seed.

According to the first aspect of the present invention, a seed to be consumed based on using the license management object is generated by the seed generation means, and the license is generated by the license management means based on the transmission and reception of the seed. Since the server is managed, the server only needs to manage the transmission and reception of the seed, and it is not necessary to constantly monitor the use of the license management object, and the license can be more easily managed. On the other hand, the user can manage the use of the license management target by consuming the seed, and thus can use the license management target at a reasonable price. That is, the agent-type license management system of the present invention is an innovative license management system that combines the simplicity of the term lending method when renting software or the like on a network with the ease of use for a user of the pay-as-you-go method. System.

Here, the license management object is, for example, a program or data that can be distributed via a network, such as various kinds of application software, components, music, video and the like, or a network home appliance or a terminal device. However, the present invention is not limited to this, and any device may be used as long as the license can be managed at the time of use. The license management includes not only the management of the seed issuing license but also the charge for license control and usage. The seed is composed of, for example, an object such as C ++ or Java, and has a built-in logic for managing the use of the license management target. The license management by the license management means does not necessarily have to be performed at the timing of transmitting the seed to the component use server, but may be performed collectively on a predetermined date. For settlement of license management, an arbitrary payment method such as transfer, credit card, electronic money, and currency exchange can be used by adjusting and allocating seed units.

According to a second aspect of the present invention, in the agent-type license management system according to the first aspect, when the license management target is used, the license management target is provided for each predetermined use unit. Is characterized in that seed consumption information for consuming the seed is added.

According to the second aspect of the present invention, when a license management target is used, seed consumption information for consuming a given seed is added to the license management target for each predetermined use unit. Since the seed consumption is managed by the program included in the seed consumption information, individual license management for each network rental product can be easily performed. Here, the predetermined unit of use is, for example, a predetermined time unit or a processing unit of software or content, and may be set arbitrarily.

According to a third aspect of the present invention, in the agent type license management system according to the first or second aspect,
The seed is transmitted to the license management target in a unit of a seed bag in which a plurality of seeds are collected, and at least one of the seeds in the seed bag transmitted to the license management target defines a new seed bag. Characterized in that it comprises an acquisition agent generation seed in which a logic program for acquiring at the timing of (1) is incorporated.

According to the third aspect of the present invention, the seed is:
It is sent to the license management object in seedback units,
With the acquisition agent generation seed, a new seed back is acquired when the seed is lost, so that the user who has lost the seed does not need to request the seed each time, which is easy for the user to use.

According to a fourth aspect of the present invention, in the agent-type license management system according to the third aspect, the acquired agent generation seed is programmed to generate an agent at the predetermined timing, and the agent comprises: It is characterized in that it is configured to move to a server that issues a seed on the network, collect the seed from the server, enclose it in a seed bag, and bring it back to the component use server.

According to the fourth aspect of the present invention, the agent dynamically generated based on the back acquisition seed moves to the server which issues the seed via the network in place of the component use server and performs the seed back. Since the license management object is brought back, the seed can be obtained separately from the operation of the license management object, and the seed can be obtained while the license management object is operating. Also,
By moving the agent to the server side, the connection between the server and the component use server becomes almost unnecessary, and the load on the network can be reduced.

According to a fifth aspect of the present invention, in the agent type license management system according to the fourth aspect, the agent operates in a Jini environment, and the agent is connected to a network using the Jini Discovery mechanism. The server is configured to search for a response from the lookup service of the server, and move to the server that has responded.

According to the invention described in claim 5, the agent can find the moving server by searching for the lookup response of the Discovery mechanism.
Agents do not need to move from server to server.

According to a sixth aspect of the present invention, in the agent-type license management system according to any one of the first to fifth aspects, the seed includes information for determining a weight of an object value. Features.

According to the sixth aspect of the present invention, since the seed includes information for determining the weight of the value of the object, the weight can be freely changed, and the usability is good.

According to a seventh aspect of the present invention, in the agent type license management system according to any one of the first to sixth aspects, the seed is set with an encrypted code for authentication by a license issuer. It is characterized by:

According to the invention described in claim 7, the seed is:
Since the encrypted code is set for authentication by the license issuer, forgery of the seed can be prevented.

According to an eighth aspect of the present invention, in the agent type license management system according to any one of the first to seventh aspects, the seed is a class instantiated as an entry object of JavaSpace. .

According to the invention of claim 8, the seed is:
Since the class is instantiated as an entry object of JavaSpace, it can be operated without being influenced by the OS environment of the license management target.

According to a ninth aspect of the present invention, in the agent type license management system according to the eighth aspect, the seed is stored in a shared memory of JavaSpace.

According to the ninth aspect of the invention, it is needless to say that the same effect as that of the eighth aspect of the invention can be obtained. In particular, since the seed is stored in the shared memory of JavaSpace, Information analysis after license use, statistical processing, and the like can be executed in parallel as separate processes. In addition, seeds can be stored on the network.

The invention according to claim 10 is the invention according to claim 8 or 9
In the agent-type license management system according to the above, a seed consumption class including a consumption method for consuming the seed is mounted on the seed, and the seed consumption class is instantiated for each predetermined processing unit, and the seed consumption class is instantiated. It is characterized in that the seed is consumed.

According to the tenth aspect of the present invention, a seed consumption class having a consumption method for consuming a seed is easily implemented and instantiated in the license management target object, and the license management object can be provided in a predetermined time or a predetermined processing unit. Execution of the consumption method ensures that the seed is consumed.

The invention according to claim 11 is the invention according to claims 1 to 10
In the agent-type license management system according to any one of the above, the seed stores predetermined usage history information of the seed, and the usage history information stored in the used seed is a server that issues the seed. It is characterized by being transmitted to.

According to the eleventh aspect, the seed stores predetermined usage history information of the seed, and the usage history information stored in the used seed is transmitted to the server that issues the seed. The marketing history can be analyzed by analyzing the usage history.

According to a twelfth aspect of the present invention, in the agent type license management system according to the eleventh aspect, the used seed is collected by the agent,
The seed is transmitted to a server that issues the seed together with the agent. According to the twelfth aspect, the same effect as that of the eleventh aspect can be obtained.

The invention according to claim 13 is the invention according to claims 8 to 12
In the agent-type license management system according to any one of the above, the agent is generated by being instantiated with a Java dynamic class loader based on the acquired agent generation seed. According to the invention of claim 13,
The same effects as the invention according to any one of claims 8 to 12 can be obtained.

According to a fourteenth aspect of the present invention, there is provided a component distribution system for renting a component from a server to a component use server using the agent-type license management system according to the second aspect, wherein the server stores the component. Means (for example, the component database 211
a), a means for copying the component requested from the component storage means based on one or more component distribution requests from the component use server (for example, the component copy management unit 217), and a copied component (E.g., the component distribution management unit 218) for transmitting the request to the component use server;
Wherein each component is added with seed consumption information for each predetermined use unit of each component, and the use of each component consumes seed based on the seed consumption information. .

According to the fourteenth aspect of the present invention, the license management at the time of component distribution from the server to the component use server is performed based on transmission of a seed required for component use, so that a license according to component use is used. Management can be performed efficiently.

According to a fifteenth aspect of the present invention, in the component distribution system 1 that rents and distributes a component from a server to a component using server using the agent-type license management system according to the third or fourth aspect, the server distributes the component. A component storage unit for storing (for example, the component database 211a) and a copying unit for acquiring and copying one or more components requested from the component storage unit based on a component distribution request from the component use server ( For example, a component copy management unit 217) and a component transmission unit (for example, the component distribution management unit 218) that transmits the copied component to the requested component use server. Each component is provided with seed consumption information for each predetermined use unit of each component, and the use of each component consumes a seed based on the seed consumption information. A seed bag including an acquisition agent-generated seed is issued.

According to the fifteenth aspect of the present invention, since a seed bag including the acquisition agent generation seed is issued for each component, use of the component can be managed individually.

According to a sixteenth aspect of the present invention, in the component distribution system according to the fourteenth or fifteenth aspect, there is provided a compatible module for adapting to a use environment of a component use server that uses the component duplicated by the component duplication means. It is characterized by having a compatible module creating means for creating.

According to the sixteenth aspect of the present invention, the compatible module is created by the compatible module creating means so as to adapt to the use environment of the component using server using the copied component. Can be created.

[0036]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An agent type license management system and a component distribution system according to the present invention will be described below with reference to the drawings. FIG. 1 is a system configuration diagram showing an overall configuration of a component distribution system according to the present invention.

The component distribution system 1 shown in FIG.
Is composed of a component distribution device 2, a component use server 3, a component providing server 4, a financial institution server 5, and the like.
Are connected via a communication line network 6 such as the Internet or a dedicated line 7, respectively.

As shown in FIG. 2, the component distribution device 2 includes an application server 21 and a web server 2
2. It is composed of a database server 23, a communication unit 24, an administrator terminal 25, and the like. The application server 21 includes a storage unit 211 such as a component database 211a for storing Java components such as JavaBean for building application software, a program database 211b in which various programs are recorded, and a Java for executing Java.
a execution environment unit 212 is provided. Further, the application server 21 manages or controls various operations of the security management unit 213, the user authentication management unit 214, the seed management unit 215, the license management management unit 216, the component copy management unit 217, the component distribution management unit 218, and the like. Has functions.

The component database 211a includes, for example, an authentication service component, an image search component, a graph / chart component, a license management service component,
ML-related components, third-party components, and the like are recorded in accordance with JavaBean specifications. The program database 211b stores programs executed by the present system, application programs, and the like. The storage unit 211 is provided with a fixed or detachable recording medium 211 in which programs and data are stored in advance, and stores various data and processing programs. The recording medium is, for example, a magnetic or optical recording medium or a semiconductor memory. The program, data, and the like stored in the recording medium may be partially or wholly received from another server or the like via a transmission medium such as a network line, and may be recorded. You may comprise so that it may transmit via a transmission medium, such as a line, and install these.

The Java execution environment section 212 includes, for example, J
ava2Platform, Enterprise E
configuration (Java2EE), etc.,
Java2EE includes JavaVM (Java Virtual M
achine), EJB (Enterprise JavaBesns), JSP
(JavaServer Pages), servlets, and other features. The security management unit 213 is configured by, for example, a sandbox, and performs class file operations,
Restrictions on application startup, communication partner, etc. are imposed. These are managed by the security manager of JavaVM. The user authentication management unit 214
For example, it is controlled by a CPU, a RAM, and the like (not shown), receives authentication information (for example, an ID and a password) input by the component use server 3, searches the user information database 321 for matching information, and performs user authentication. Perform processing.

The seed management unit 215 is controlled by, for example, a CPU, a RAM (not shown), and the like. As a seed generation unit, a seed generation unit that generates a seed necessary for using a component based on a program stored in the storage unit 211 is provided. Unit 215a and J for storing the generated seed
The system further includes a seed supply unit 215c having an avaSpace 215b and a lookup server (not shown), and managing the supply of the seed to the component use server 3 using the lookup service.

The seed generation unit 215a includes a CP (not shown).
U, RAM, and the like, and according to a predetermined program in the program database 211a, for example, as shown in FIG. 9, generates the seed 101 at a predetermined timing, and generates the generated seed 101 in the JavaSpace 215.
b in the shared memory. Here, the predetermined timing may be a timing at which a fixed amount of the seed 101 has been lost, or may be such that the lost amount is periodically replenished, or may be arbitrarily set. This seed 101
For example, it is composed of a Java class file instantiated as an entry object of JavaSpace 215b, and has a data part and a method part.

The seed 101 stores in the data section usage history information such as the name of the component that has consumed the seed 101 and the usage time. In the class file of the seed 101, for example, as shown in FIG. 3, an approval number (certificate_code), a serial number (serial_numbe)
r), weight (seed), issuer name (issure), and the like. That is, the life amount of each seed 101 is not uniform but can be arbitrarily set by a numerical value of the weight. Also, an encrypted code is set for authentication by the license issuer, so that forgery is prevented.

A seed consumption class having a method for consuming the seed 101 is mounted on the seed 101. The seed consumption class is instantiated for each predetermined processing unit, and is incorporated in, for example, the consumption method shown in FIG. The logic consumes the seed 101. Seed 101
Is consumed means that, for example, when a component is used in a predetermined processing unit (for example, one hour) on the component use server 3 side, the seed capacity is reduced by a preset amount. And used seed 1
01, the usage history information stored in the agent 10
2a (to be described later), and transmitted to the component distribution device 2 together with the agent 102a.

The seed generation unit 215a generates an acquisition agent generation seed 102 for generating an agent 102a that obtains a new seed when the seed 101 in the seed bag 100 runs out. This acquisition agent generation seed 102 is the seed bag 1
When all the seeds 101 in 00 are consumed, they are consumed when the acquisition agent 102a is instantiated with the Java dynamic class loader, and are taken into the agent 102a together with the seed bag 100. The acquisition agent 102a is programmed to perform the following operations.

The agent 102a searches for a server that issues the seed 101 on the network separately from the operation of the component in the component use server 3, and moves to the server when a server that issues the seed is found. Specifically, the agent 102
a runs in the Jini environment and uses Jini's Multi
By using the ast Discovery mechanism, the server 101 connected to the network is searched for an event of a lookup service of the seed supply unit 215c of the server, and the seed 101 for using the license management object is retrieved. Find the server to publish,
Moving.

The agent 102a collects the used seeds 101 together with the seed bag 100 in advance and, when moving to the server, uses the used seeds 101.
Move with. Agent 10 moved to server
2a, the collected seed 101 and the acquisition agent generated seed 102 consumed by itself are all stored in the Java of the server.
Return to aSpace, and renew the number of seeds 1 for the number specified in the seed bag 100 from JavaSpace.
01 and the acquisition agent-generated seed 102 are acquired in the seed bag 100, and the process moves to the component use server 3 that sent the user again. Then, the acquired seed bag 100 is stored in the storage unit 211 and then disappears. The seed supply unit 215c searches for a used seed from the JavaSpace shared memory, acquires history information, and stores the history information in the user information database 231.

The license management unit 215 is connected to the financial institution server 5 via the communication line 7 and manages licenses for users based on the rental of components. Specifically, the amount corresponding to the seed 101 transmitted from the user's financial institution account is withdrawn at the timing when the seed 101 is transmitted to the component use server 3. The component replication management unit 216
The requested component is picked up from the components stored in the component database, and the component is duplicated.

The component copy management unit 216
When the component is used in the component use server 3 to the copied component, seed consumption information in which logic for consuming the seed 101 is programmed is added for each predetermined use unit (for example, one hour). In addition, the component copy management unit 21
6 creates a compatible module in order to consider the compatibility of the server when the copied component is used by the component using server 3. Here, the compatible module will be described. J2E used in component delivery
The E and EJB specifications differ between versions that go from 1.0 to 1.1 and 2.0, and depending on the application server providing vendor that supports them, the environment properties, the acquisition of database resources, the security model, etc. The implementation procedure when developing Bean is different. In this state, it is difficult to distribute components with portability and operate them correctly on each server. Therefore, as a solution for portability of components and smooth distribution, Port
Create ableContext. There is a part where the definition of the context, which is the interface that enables the Enterprise Bean to interact with the EJB container (EJB server) as the execution environment, is inconsistent between the EJB1.0 and the EJB1.1 rules. As a class to encapsulate to solve this compatibility problem
PortableContext is prepared. By using this in the Bean implementation, the components to be delivered are exactly the same, "compatible module" for each application server
The individual execution becomes possible only by exchanging. This patent application is a solution that ensures portability by distributing compatible modules corresponding to the type of application server at the time of component distribution.

The component distribution management unit 217 performs a process of transmitting the component copied by the component copy management unit 216 to the component use server 3 of the user who has requested the component.

The Web server 22 converts a Web page, for example, a page for searching and narrowing down a component, a page for displaying the use status of a component, etc., based on a request from the component using server 3. And the like for providing a Web page or the like.

The database server 23 includes a user information database 231, a content database 232, and the like. The user information database 231 is used to manage information (name, ID, password, etc.) necessary for authenticating a user, and to manage licenses. Required information (e.g. account number), usage history (use components,
This is a database that stores usage dates and times. The content server 232 is, for example, an XML (eXtensive Mar
kup Language), and specifically, a server that stores contents described in CUPML, WAP
Adapter, palm adapter, FAX adapter, PDF
It is possible to provide content corresponding to various hardware via a / PS adapter and an HTML adapter.

The communication device 24 is a modem (MODEM: MO
dulator / DEModulator), terminal adapter (TA:
Terminal Adapter) or a router or the like, and can perform data communication with the component use server 3, the component providing server 4, and the financial institution server 5 via the communication networks 6 and 7. In addition, the communication device 24 has a CO
A server having an RBA server 241 and a communication environment for communicating components provided from the component providing server 4 in various programming languages. The interface structure is dynamically analyzed by using an interface repository function. I do. The administrator terminal 25 is a device that monitors or instructs various processes of the component distribution device 2 and that maintains data and programs. For example, as shown in FIG. 252, a storage unit 253,
The display unit 254 is provided.

The control unit 251 includes, for example, a CPU (Centra
l Processing Unit) and RAM (Random Access Memor)
y) and the like, and executes various operation controls based on inputs from the input unit 252 according to programs and data stored in the storage unit 253.

The input unit 252 includes, for example, a mouse and a keyboard, and can input a control instruction signal of the control unit 271 and the like. The storage unit 253 stores various programs executed by the control unit 251 and data. The display unit 254 includes, for example, a CRT (Cathode Ray Tube), L
It is composed of CD (Liquid Crystal Display), etc.
Various data and the like are displayed on the screen according to the display control by the control unit 251.

Each of the component use servers 3 includes, for example, a personal computer or the like. As shown in FIG. 5, a CPU (not shown) and a RAM
(Not shown), a control unit 31 including a hard disk device (not shown), an input device 32 connected to the control unit 31 via an input / output interface (not shown), a communication device 33, A display device 34 and the like are provided.

The control unit 31 includes, for example, Java2EE. Java2EE is JavaVM, EJ
A Java execution development environment unit 311 having functions such as B, JSP, and servlet is provided. By reading out and starting a Web browser such as Internet Explorer (trade name) or Netscape Navigator (trade name) stored in a hard disk drive (not shown), a Web page can be displayed on the display device 34 and browsed, An applet viewer is incorporated in the browser so that a Java applet can be started. A Java application can be executed by JavaVM.

The input device 32 includes, for example, a mouse, a keyboard, and the like, and can select and specify designation information displayed on the screen of the display device 34, or can input desired designation information.

The communication device 33 is a modem (MODEM: MO
dulator / DEModulator), terminal adapter (TA:
Terminal Adapter), a router, and the like, and can perform data communication with the component distribution device 2 via the communication network 6. The display device 34 is, for example, a CR
It is composed of a T, an LCD, and the like, and displays display data and the like output from the control unit 31 on a screen.

The application providing server 4 provides the component to the component distribution device 2 and a seed 10 for using the component.
1 and has the same function as the application server 21 of the component distribution device 2 inside. Then, a response indicating that seed supply is possible is sent to the agent 102a of the component use server 3 by the lookup service.
1 is supplied.

Hereinafter, the above component distribution system 1
Is described below. First,
The component selection distribution processing by the component distribution system 1 having the above configuration will be described with reference to FIG.
It should be noted that programs for realizing each function in the present system are stored in the program database 211b in the form of a program code readable by a CPU that operates each management unit.

Before starting this processing, the components provided from each component providing server 4 are installed in the component database 211a in advance and stored in the storage unit 211. As described above, when the component selection distribution process is started in a state where a plurality of components are registered, first, the user starts browsing software such as a browser using the component use server 3 and transmits the component distribution device 2 to the component distribution device 2. to access. Then, a component selection page is transmitted from the Web server 21 of the component distribution device 2, and a component selection screen is displayed on the display device 34 (Step S).
1). Then, a list of rentable components is displayed on the component selection screen, and a desired component is selected from these by clicking with a mouse or the like (step S2).

Next, a selection signal based on the click operation is transmitted to the component copy management unit 216 of the component distribution device 2. Then, for example, as illustrated in FIG. 7, the component copy management unit 216 copies the component selected by the user from the components stored in the component database 211a (Step S3). At this time, PortableContext, which is a compatibility module for improving compatibility with the user's application server, is created. Next, the user acquires the seed bag 100 corresponding to the component selected from the JavaSpace 215b (step S4). If a plurality of components are selected, one or more seed bags 100 are acquired for each component, and one acquired agent generation seed 102 is included for each component.

Next, a license management process is performed based on the acquired seed bag 100 (step S).
5). Here, the license management process is performed by deducting an amount obtained by multiplying the acquired seed bag 100 by each unit price from the user's deposit account. Next, it is determined whether the license management process is normal (step S6),
When the user's balance is small (step S6; NO)
Is notified to the user (step S7), and this processing ends. If the license management processing is normally performed (step S6; YES), the copied component and the seed bag 100 are deleted. The data is transmitted to the user terminal 3 (step S8). Next, the component use server 3 stores the transmitted component and the seed bag 100 in the storage unit 211 (step S9), and ends the process.

Next, the component use process will be described with reference to FIG. In the component use process, first, the user uses the transmitted component (step S11). In this state, the seed consumption program built in the component is activated, and the control unit 41 determines whether or not a predetermined unit of use has been exceeded (step S12). Then, when it is determined that the use unit has not been exceeded (step S12; NO), the process returns to step S11 and the use of the component continues, but when it is determined that the use unit has exceeded the predetermined use unit (step S12). In S12; YES), a predetermined seed 101 is consumed (step S13). Here, “to consume the seed 101” refers to, for example, calling and calling the consumption method of the seed 101.

Next, it is determined whether or not there is a predetermined number or more of seeds 101 other than the acquired agent generation seed 102 in the seed bag 100 (step S14). Then, seed 1 other than the acquisition agent generation seed 102
01 is more than a predetermined number (step S14; YES)
Returns to step S11, but if there is not a predetermined number or more of seeds 101 other than the acquisition agent generation seed 102 (step S14; NO), the acquisition agent is generated / instantiated using the Java dynamic class loader. , Acquisition agent generation seed 102
Is acquired from the component based on the program in which the seed bag 100 including the “.” Is stored. At this time, the agent 102a performs consumption agent generation seed consumption processing. For example, as shown in FIG. 9, the agent 102a is generated (step S15). Next, the agent 102a searches for a server (for example, the component distribution device 2, the component providing server 4) that issues the seed bag 100 for use of the component on the network using the Jini lookup service (step S16). ). At this time, on the component use server 3 side, the execution of the component and the execution of the agent 102a are performed separately.

Next, when there is a response from the server that issues the seed bag 100, the agent 102a moves to the server (for example, the component distribution device 2) via the network as shown in FIG. 10, for example. (Step S17). At this time, the agent 102a converts the collected seed 101 and the acquired agent-generated seed 102 consumed by the agent 102a all into Java.
Return to Space 215b. Next, the seed supply unit 21
5 retrieves the used seed from the JavaSpace shared memory, acquires the history information, and stores it in the user information database 231 (step S18). Next, the agent 102a communicates with J
The seed bag 100 is prepared in advance from avaSpace 215c.
A new number of seeds 101 set according to (1) is obtained (step S19). It includes one acquisition agent generation seed 102. The server 2 performs a license management process (step S20) based on the obtained seed bag 100. Also, the seed supply unit 215c
A used seed is searched from the JavaSpace shared memory, history information is acquired, and stored in the user information database. These license management processes can be executed asynchronously as a separate process, and the usage can be calculated from the amount of the unit corresponding to the license management process separately, and the result can be transferred to the billing or payment process. is there.

Next, it is determined whether or not the license management process is normal (step S21). If the user's balance is small (step S21; NO), the user is notified of the fact (step S22), and this process is performed. When the license management process is completed normally (step S21; YES), the agent 102a returns to the component use server via the network together with the seed bag 100 as shown in FIG. Step S23). Next, the component use server stores the seed bag 100 brought back by the agent 102a in the JavaSpace 214b (step S24). Next, the agent 102a
Disappears by itself according to the built-in program (step S25), and ends this processing.

The present invention is not limited to the above embodiment. For example, although the components are exemplified as the license management object, the present invention is also applicable to license management of application software, music software, video software rental, information home appliance service, use of terminal devices, and the like. In addition, as an example of the license management method, automatic bank debit has been described, but any method such as a transfer form by issuing a bill or a settlement by a credit card may be used.

[0070]

According to the first aspect of the present invention, seeds consumed by using the license management object are generated by the seed generation means, and license management is performed based on the transmission of the seeds. Since the license is managed by the means, the server only has to manage the transmission of the seed, and it is not necessary to constantly monitor the use of the license management object, and the server can perform the license management more easily. On the other hand, the user can manage the use of the license management target by consuming the seed, and thus can use the license management target at a reasonable price.

According to the second aspect of the invention, when a license management target is used, seed consumption information for consuming a given seed is added to the license management target for each predetermined use unit. Since the seed consumption is managed by the program included in the seed consumption information, individual license management for each network rental product can be easily performed. Here, the predetermined unit of use is, for example, a predetermined time unit or a processing unit of software or content, and may be set arbitrarily. According to the third aspect of the present invention, the seed is transmitted to the license management target in a unit of seed back, and a new seed back is acquired by the acquisition agent generation seed when the seed is exhausted. This eliminates the need for the user to request the seed each time, which makes the user easy to use.

According to the fourth aspect of the present invention, the agent generated from the back acquisition seed moves to the server that issues the seed via the network instead of the component using server and brings back the seed back.
The seed can be obtained separately from the operation of the license management object, and the seed can be obtained while the license management object is operating. Further, by moving the agent to the server side, the connection between the server and the component using server becomes almost unnecessary, and the load on the network can be reduced.

According to the fifth aspect of the present invention, the agent can find the moving server by searching for the lookup response of the Discovery mechanism.
Agents do not need to move from server to server. According to the invention described in claim 6, since the seed includes information for determining the weight of the value of the object, the weight can be freely changed and the usability is good.

According to the seventh aspect of the present invention, the seed is:
Since the encrypted code is set for authentication by the license issuer, forgery of the seed can be prevented. According to the eighth aspect of the present invention, the seed is a Java
Since the class is instantiated as an aSpace entry object, it can operate without being affected by the OS environment of the license management target.

According to the ninth aspect, the seed is:
Since it is stored in the shared memory of javaSpace, the seed can be stored on the network. According to the invention of claim 10, the seed is implemented with a seed consumption class including a consumption method for consuming the seed,
A seed consumption class is instantiated for each predetermined processing unit, and the seed is reliably consumed by the consumption method.

According to the eleventh aspect, the seed stores predetermined use history information of the seed, and the use history information stored in the used seed is transmitted to the server that issues the seed. The marketing history can be analyzed by analyzing the usage history.

According to the fourteenth aspect of the present invention, the license management at the time of component distribution from the server to the component use server is performed based on transmission of a seed necessary for component use. Management can be performed efficiently.

According to the fifteenth aspect of the present invention, since a seed bag including an acquisition agent generation seed is issued for each component, use of the component can be managed individually. According to the sixteenth aspect of the present invention, since the compatible module for adapting to the use environment of the component using server using the component copied by the compatible module creating means is created, a component having good compatibility can be created. .

[Brief description of the drawings]

FIG. 1 is a block diagram showing a system configuration of a component distribution system according to the present invention.

FIG. 2 is a block diagram illustrating a main configuration of the component distribution device.

FIG. 3 is a diagram showing data logic of a seed, a seed bag, and an acquisition agent generation seed.

FIG. 4 is a block diagram showing data logic of a seed consumption class.

FIG. 5 is a block diagram illustrating a main configuration of a component use server.

FIG. 6 is a flowchart of a component distribution process.

FIG. 7 is a diagram illustrating a component duplication process.

FIG. 8 is a flowchart of a component use process.

FIG. 9 is a diagram illustrating a search for a seed by an agent.

FIG. 10 is a diagram for explaining movement of an agent to a component distribution device.

FIG. 11 is a diagram for explaining movement of an agent to a component use server.

[Explanation of symbols]

 Reference Signs List 1 component distribution system 2 component distribution device 3 component use server 4 component providing server 5 financial institution server 21 application server 22 Web server 23 database server 211 storage unit 211a component database 211b program database 212 Java execution environment unit 215 seed management unit 215a seed generation Unit 215b JavaSpace 215c Seed supply unit 216 License management unit 217 Component duplication unit 231 User information database 232 Content database

Claims (16)

[Claims] 1. An agent-type license management system that performs license management for use of a license management target based on seed information transmitted and received by an agent object that moves between a server and a license management target via a communication line. A server for generating a seed required as a unit for using the license management target; a seed included in the mobile agent object generated by the seed generation unit; A server program on the network for monitoring the movement of the agent and performing license management based on collecting seed information, wherein the mobile agent is a license management target. Object and server By moving the enclosing seed, to send and receive seed for that license management object,
An agent-type license management system characterized in that the seed incorporates a logic program that consumes itself. 2. The agent-type license management system according to claim 1, wherein the license management target uses a seed for every predetermined use unit when the license management target is used. An agent type license management system characterized by adding consumption information. 3. The agent-type license management system according to claim 1, wherein the seed is transmitted to the license management target in a unit of a seed bag in which a plurality of seeds are collected, and is transmitted to the license management target. At least one of the seed bags to be obtained includes an acquisition agent generation seed in which a logic program for acquiring a new seed bag at a predetermined timing is provided. . 4. The agent-type license management system according to claim 3, wherein the acquisition agent generation seed includes a logic program that generates an agent at a predetermined timing, and the agent generates a seed on the network. An agent-type license management program which is programmed to move to a server to issue, collect a predetermined number of seeds from the server, insert the seeds into a seed bag, and bring back the license management object. system. 5. The agent-type license management system according to claim 4, wherein the agent operates in a Jini environment, and the agent is a Discover of the Jini.
An agent type configured to search for a response from a lookup service of the server from among servers connected to the network using a y mechanism, and to move to a server that has responded. License management system. 6. The agent type license management system according to claim 1, wherein the seed includes information for determining a weight of an object value. Management system. 7. The agent type license management system according to claim 1, wherein an encrypted code for authentication by a license issuer is set in the seed. Agent type license management system. 8. The agent-type license management system according to claim 1, wherein the seed is a class that is instantiated as a JavaSpace entry object. 9. The agent-type license management system according to claim 8, wherein the seed is stored in a shared memory of JavaSpace. 10. The agent-type license management system according to claim 8, wherein the seed includes a seed consumption class including a consumption method for consuming the seed, and for each predetermined processing unit,
An agent-type license management system, wherein the seed consumption class is instantiated, and the seed is consumed by the consumption method. 11. The agent-type license management system according to claim 1, wherein the seed is configured to store predetermined use history information of the seed. License management system. 12. The agent-type license management system according to claim 11, wherein the used seed is collected by the agent and transmitted to the server that issues the seed together with the agent. License management system. 13. The agent-type license management system according to claim 8, wherein the agent is generated by instantiating the acquired agent generation seed with a Java dynamic class loader. Agent type license management system characterized by the following. 14. A component distribution system that rents and distributes components from a server to a component use server using the agent-type license management system according to claim 2, wherein: the server comprises: component storage means for storing components; Means for copying the component requested from the component storage means based on one or more component distribution requests from the component using server; and component transmitting means for transmitting the copied component to the requesting component using server. Each component is provided with seed consumption information for each predetermined use unit of each component, and the use of each component consumes seed based on the seed consumption information. Components distribution system characterized in that it is. 15. A component distribution system for renting components from a server to a component use server using the agent-type license management system according to claim 3, wherein the server comprises: component storage means for storing components; Means for copying one or more components requested from the component storage means based on a component distribution request from the component use server, and transmission means for transmitting the copied components to the requested component use server. Each component is provided with seed consumption information for each predetermined use unit of each component, and the use of each component consumes a seed based on the seed consumption information. The component units, component delivery system characterized in that the seed bag is issued including the acquired agent generation seed. 16. The component distribution system according to claim 14, wherein a compatible module for creating a compatible module for adapting to a use environment of a component use server that uses the component copied by the component copy unit is used. A component distribution system comprising: