JP2003015758A - Software management apparatus, software management system and software management method using the same - Google Patents

Abstract

(57) [Summary] [Problem] To easily and commonly manage software and a product of the software. SOLUTION: A CPU 210 of a computer 200 comprises:
An activation password is sent to the processor 110 of the software management apparatus 100 via the bus 280. The processor 110 compares the transmitted start password with the start password in the non-disclosure area of the storage device 120, and sends a start permission software start control signal if they match. Subsequently, when the access password for accessing the public area is sent from the computer 200, the processor 110 compares the password with the access password in the non-public area of the storage device 120. Access to public areas of In this way, the software and the software product can be used on the computer 200 under the management of the software management apparatus 100.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software management device, a software management system and a software management method using the software management device, and more particularly to a software management device and a software management device for managing the software by connecting to a computer using predetermined software. The present invention relates to a software management system and a software management method used.

[0002]

2. Description of the Related Art In recent years, with the spread of computer networks such as digital broadcasting and the Internet,
Intangible assets such as programs, electronic data, and digital contents (hereinafter collectively referred to as software)
However, it has become widely distributed through digital broadcasting and networks. Conventionally, as a method for managing such software, for example, Japanese Patent Laid-Open No. 9-160899.
"Information service processing device" described in Japanese Patent Laid-Open No. 10-222427, "Network license management system and storage medium" described in Japanese Patent Laid-Open No. 10-222427, and Japanese Patent Laid-Open No.
As described in "Digital Content Distribution Management Method, Digital Content Playback Method and Device" described in Japanese Patent Laid-Open No. 269289, a server for managing software is provided on a communication network, and when the software is used, the server communicates with the server via the network. Then, there is a method of obtaining usage management information such as billing information and expiration date information and determining whether or not it is available. In addition, for example, Japanese Examined Patent Publication 6-19707
As in the "Software Management Method" described in Japanese Patent Publication, management information peculiar to the software is added together with the paid software stored in a portable medium, and the user-owned I
There has been a method in which the user has a software service system that prevents the software from being used for more than the amount set in the C card.

[0003]

However, the conventional software management system has a problem that the infrastructure for software management needs to be prepared. Further, if the management is simplified by using a portable medium, there is a problem that even the deliverable generated by the software cannot be managed.

[0004] In the conventional method for managing software by providing a server for managing software on a communication network, since communication is used for software management, communication equipment for connecting to infrastructure equipment such as a communication network or the communication network. It is necessary to prepare a computer and a computer, and there is a problem that it cannot be managed easily.

In addition, in the method of managing software using a portable medium, in particular, management of software as a product generated by predetermined software, such as document data created by a document creation program, is managed. Since no consideration is given, there is a problem that the software and the software generated by the software cannot be managed by the same device. Hereinafter, software as an artifact generated by software is particularly referred to as a software artifact.

The present invention has been made in view of the above circumstances, and a software management apparatus capable of easily and commonly managing software and its software products, a software management system using the same, and a software management The purpose is to provide a method.

[0007]

According to the present invention, in order to solve the above-mentioned problems, in a software management device for managing the software by connecting to a computer using predetermined software, the software and the software are generated by the software. Controlling transmission and reception of predetermined information between the storage unit that stores desired data including management information regarding management of software artifacts and the computer, and managing the software and the software artifacts based on the management information Control means for
There is provided a software management device comprising:

In the software management device having such a configuration, desired data including management information related to management of software and software products generated by the software is stored in the storage means. The control means is connected to a computer that performs data processing using predetermined software, transmits and receives predetermined information to and from the computer, and manages predetermined software and software deliverables by the computer according to the management information. Do.

Further, in order to solve the above-mentioned problems, in a software management method for managing the software by connecting to a computer using predetermined software,
Pre-storing management information relating to management of the software and software artifacts generated by the software, connecting with the computer, and obtaining a request for using the software or the software artifact from the computer. And a step of determining whether or not the software or the software product can be used by the computer according to the management information, and a step of notifying the computer of whether or not the software can be used. A software management method is provided.

In the software management method having such a procedure, software and management information relating to management of software products generated by the software are stored in advance. When connecting to a computer that uses this software and obtaining a request to use the software or software deliverable from the computer, it is determined whether the software or software deliverable can be used according to the management information stored in advance. Notify the computer of the judgment result.

In order to solve the above-mentioned problems, a software utilizing device that uses a predetermined software, a software artifact producing device that produces a software artifact using the software, and the software utilizing device or the software. In a software management system including a software management device that manages the software by connecting to a product creation device, storing desired data including management information regarding management of the software and software products generated by the software A software management device comprising: storage means for controlling the transmission and reception of predetermined information between the software utilization device and a control means for managing the software and the software deliverable based on the management information; Storage means for storing the software and the software deliverable, and control means for determining the availability of the software and the software deliverable according to the software management device and using the software and the software deliverable when permitted And a storage means for storing the software, managing the software management apparatus for generating the software deliverable using the software and connecting to the software using apparatus as necessary. There is provided a software management system comprising: a software deliverable creation device including control means for setting information.

In the software management system having such a configuration, the software deliverable creation device stores the predetermined software used in the storage means. The control means of the software management device activates the software and creates a desired software deliverable. Further, when supplying the software deliverable to the software utilizing apparatus, the management information regarding the software deliverable is set in the software managing apparatus connected to the software utilizing apparatus. The software utilization device stores software and software products used in the storage means. When the software and the software deliverable are used in the software utilizing apparatus, the control means inquires of the software managing apparatus to be connected whether or not the software and the software deliverable can be used. The control means of the software management device determines whether or not the predetermined software and the software product can be used by the software using device according to the management information related to the management of the software and the software product generated by the software stored in the storage device. And notify the result. The software using device uses the software and the software deliverable according to the notification result.

In order to solve the above-mentioned problems, a software utilizing apparatus that uses a predetermined software, a software artifact producing apparatus that produces a software artifact using the software, the software utilizing apparatus or the software. In a software management method in a software management system including a software management device that is connected to a product creation device and manages the software, the software product creation device creates a desired software product using the software. Together with the step of generating related information related to the software deliverable and adding the related information to the software deliverable; and, when using the software deliverable in the software utilizing device, the software utilizing device, A step of setting management information relating to management of software deliverables generated by the software in accordance with the related information in a subsequent software management device; connecting the software using device and the software managing device; Determining whether or not the software and the software product can be used by the software using device according to the management information stored in the software, and the software and the software result in the software using device according to the determination result. There is provided a software management method, characterized in that it has a procedure of using an object.

In the software management method of such a procedure, the software deliverable creating apparatus creates the software deliverable and the related information related to the software deliverable by using the software, and adds the related information to the software deliverable. . When the software deliverable is used in the software utilizing device, the software deliverable creating device sets the management information regarding the management of the software deliverable in the software managing device according to the related information. The software utilization device connects the software management device when using the software and the software product, inquires about the availability of the software product, and uses the software product when permitted.

[0015]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. The software management device according to the present invention includes software prepared for generating software artifacts such as programs, data, and libraries,
It is used to manage the software artifacts generated by the software.

As an example of the software management system,
A case of creating data broadcast content will be described. FIG. 1 is a diagram showing a procedure until data broadcast content is created.

Data broadcasting contents are produced using software sold by the software sales company 10. This software includes a program for creating content, data, and the like. In addition, for example, packaged parts made up of image data of buttons displayed on the data broadcast screen and programs related to operations associated with the buttons, and data broadcast of data transmitted by data broadcast such as weather forecast data. The materials for use are produced by the data broadcasting material providing company 20. The data broadcasting material providing company 20 uses the software of the software selling company 10 to create and sell a software product that is a data broadcasting material. The data broadcasting content creation company 30 is a software sales company 1
0 software is used to produce data broadcast contents by using the data broadcast material provided by the data broadcast material providing company 20. The data broadcasting content produced in this way is distributed on the broadcast wave from the broadcasting station 40. The distributed data broadcasting content is sent via the communication satellite 50, received at the home 60, and viewed.

As described above, the data broadcasting material providing company 2
The software product creation apparatus of No. 0 uses the software to create the software product, and therefore the use management of the software is required. Further, the software using device of the data broadcast content creation company 30 uses the software for the production process and the software deliverable as a material to produce the data broadcast content, and therefore, both the software and the software deliverable are produced. Need to manage. The software management device according to the present invention is connected to a software product creation device or a software utilization device to manage these software and software products.

Next, a software management system using this software management device will be described. Figure 2
It is a block diagram of the software management system which is one embodiment of the present invention.

The software management system according to the present invention comprises a software management device 100 for managing software and software artifacts, and a computer 200 for utilizing software or software and software artifacts. Computer 2
00 is software or software management device 1
Depending on 00, it functions as a software deliverable creation device or a software utilization device.

The software management apparatus 100 communicates with the computer 200 and stores the software, or a processor 110 which is a control means for managing the software or software and software artifacts, and desired data including management information for the software and software artifacts. The storage device 120 is a storage unit that stores the data. The software management device 100 is, for example, a portable device such as an IC card, and is connected to the computer 200 when executing predetermined software.

The processor 110 is a computer 200.
It is connected to the internal bus 280 and can communicate with the CPU 210. Communication is performed with the CPU 210 of the computer 200 via the bus 280, and in response to a request from the CPU 210, it is determined whether or not the software and software deliverable can be used and whether or not the information data stored in the storage device 120 can be accessed. Notify the result, C
It manages software and software products such as updating management information in response to a request from the PU 210.

The storage device 120 is a rewritable access storage device such as a flash memory, a magnetic disk, an optical disk, a magneto-optical disk, or the like. Storage device 120
Cannot be read and written from the computer 200, and can be read and written only by the processor 110, and the reading and writing from the processor 110 can also be done by the computer 2.
It is divided into open areas where reading and writing from 00 is possible.

The private area is a first area for identifying whether or not the computer 200 can use the software.
A first storage area that stores a startup password as identification information of the first and a second storage area that stores an access password as second identification information for identifying whether or not the computer 200 can access the public area. It is composed of a storage area. Each password is stored in each storage area.

Management information about software and software deliverables is stored in the open area. The computer 200 can read and write management information as needed.

The computer 200 is, for example, a general-purpose computer such as a personal computer or a workstation, and is a software product creating apparatus that creates software products using software for creating contents, or software for creating contents. Functions as a software utilization device that creates contents using software deliverables. The inside of the device is C
The PU 210, the ROM 220, the RAM 230, the hard disk 240, the display device 250, the keyboard 260, and the mouse 270 are connected via the bus 280. The hard disk 240 is a storage unit that stores content creation software acquired via a recording medium such as an optical disk, a network, or the like, and, if necessary, a software deliverable that is a content creation material. CP
The U 210 makes an inquiry to the software management device 100 via the bus 280 when activating software for content creation or using a software product,
It is a control means that executes only when permitted.

The operation and software management method of the software management apparatus and the content creation apparatus having such a configuration will be described. When activating the content creation software on the computer 200, the user connects the software management device 100 to the computer 200.

The CPU 210 of the computer 200 sends the activation password to the processor 110 of the software management apparatus 100 via the bus 280. When the activation password is sent from the computer 200, the processor 110 compares it with the activation password in the private area of the storage device 120, and returns the result of whether or not they match to the computer 200. That is, if they match, a software activation control signal for permitting activation is sent.
As described above, the software operating on the computer 200 cannot start the software unless it is connected to the software management device 100 and is not authorized.
This can prevent the computer 200 not equipped with the software management device 100 from starting and using the software.

Subsequently, when the processor 110 receives an access password for accessing the public area from the computer 200, the processor 110 compares it with the access password in the non-public area of the storage device 120. Enable access to the public area of the storage device 120. The operation up to this point is the same for both the software deliverable creation device and the software utilization device.

After the computer 200 can access the public area of the software management apparatus 100 in this way, the software utilizing apparatus can start or not activate each software constituting the software according to the information stored in the public area. Or the availability of individual software deliverables, billing processing, etc. Further, the software deliverable creation device determines whether or not each software constituting the software can be started according to the information stored in the open area, and publishes the deliverable management information used for managing the software deliverable created by itself. Set to the specified area of the area.

The configuration of the open area will be described. Figure 3
FIG. 3 is a configuration diagram of a public area of a software management device according to an embodiment of the present invention. The public area 3000 includes software activation information 3100 and a creator management information area used by the software artifact creator who created the software artifact to manage the software artifact. The management information area for creators corresponds to the software artifact seller who creates and sells software artifacts, and the area 3200 for software artifact seller (1)
It is divided into a software product seller (N) area 3400. Area 32 for software artifact sellers
Areas of 00 to 3400 are secured in a number corresponding to the number of sellers.

In the software activation information 3100, software that can be activated by the user of the computer 200 is set among the software components that make up the software. For example, the software supplied from the software sales company is the same for both the software deliverable creation device and the software utilizing device, but the software deliverable creation device is software that sets management information for sale in the public area. However, it is not convenient for the software utilizing device to be able to activate this software. In such a case, in order that only the software deliverable creation apparatus can activate the software for setting the information for sale, the activation possibility of each software corresponding to the software activation information 3100 is registered in advance. For example, software activation information 3
Reference numeral 100 is composed of flags corresponding to each software, and flags corresponding to the software that can be activated are set. The processor 110 or the CPU 210 of the computer 200 uses the software startup information 31.
00, and if the flag is not set, the corresponding software is not started. For example, the software management device 100 connected to the software utilizing device
A flag is set in the software activation information 3100 so that the software for setting the information for sale is not activated. Therefore, the software utilizing apparatus cannot activate the software for setting the information for sale. In this way, the software activation information 3100 makes it possible to restrict the use of software.
Further, in the above description, the software for setting the information about the sale is described, but the restricted software may be any software, for example, the usage of the software for creating the software deliverable as the material is restricted. .

Software Product Seller Area 3200
3400 are provided for each seller who sells the generated software artifacts, and when the area for software artifact seller (1) 3200 is taken as an example, the identification number of the seller (hereinafter referred to as ID) ID 321 which is an area for storing
0 and password 32, which is the area for storing the password
20 and a usage amount 3230, which is an area for storing information about the usage amount.

The ID 3210 is a creator identification information area for storing creator identification information for identifying a software product creator (same as the seller) who created the software product. The software deliverable is accompanied by management information including the creator's ID as related information regarding the software deliverable. The software management device or the software utilization device searches the corresponding area for the software product seller based on the ID attached to the software product. If there is no corresponding area for the software artifact seller, the software artifact cannot be used. On the other hand, the software deliverable creation device sets the ID of the software deliverable creator in the corresponding area of the software management device of the software deliverable user who is permitted to use the software deliverable.

The password 3220 records information for identifying whether or not the software product can be used or whether or not the software product can be written in the management information area for the software product seller corresponding to the software product. For example, the user identification information for identifying whether or not the software utilizing device can use this software product is stored, and the user identification information sent from the software and the stored user identification information are stored. Only when and match, it is possible to allow the use of the software product. Utilization also includes, for example, editing software artifacts. In addition, in order to identify whether the usage amount 3230 or the like provided in the software product seller area can be changed, a password is stored,
Only when the creator identification information sent from the software and the stored password match, the usage amount 323
Allows setting changes such as 0.

The usage amount 3230 is recorded with billing information relating to billing when the software product created by the software creator corresponding to the software utilizing device is used, for example, information regarding available amount that can be used for payment. ing. In the usage amount 3230, information corresponding to the paid amount is set by paying a fee to the software product seller in advance. When the software deliverable is used, the content of the available amount is updated to the value obtained by subtracting the used amount. Also, if necessary, before using the software artifact, check whether the available amount is larger than the usage amount of this software artifact, and permit the use of the software artifact only when the available amount is large. You can also When the available amount is insufficient, the software product user pays the software product seller to update the usage amount 3230. In addition, if the user who uses the software deliverable purchases the right to use the software deliverable, the software deliverable creation device is the corresponding usage amount of the software management device connected to the software use device of the software deliverable user. Change the area of according to the purchase price. Usage amount 32
The use right of the software product 30 can be omitted if the software product can be purchased collectively, that is, if the software product is not charged on a pay-per-use basis.

Since the information in the public area can be read and written by the computer 200 as well, the processing such as determining the availability by using the software deliverable management information,
Computer 200 or software management device 10
It may be performed at either 0.

A specific example of such a public area is shown in FIG. Area 3200a for software product seller (A)
To company A, area 33 for software product seller (B)
00a is assigned to company B, and their IDs are registered. In the password 3220a, a password for using the corresponding software deliverable or a password for permitting setting of the usage amount 3230a is registered. For example, if the user of the software product pays 10,000 yen to the company A, the company A
By inputting the password, the user receives permission to rewrite the usage amount 3230a of the software product seller (A) area 3200a, and sets information indicating that 10000 yen can be used in the usage amount 3230a. Next, a method of managing the software deliverable when the software utilizing device uses the software deliverable by using such a software managing device will be described. FIG. 5 is a flowchart of the software product use processing. The use of the software deliverable is started (S100), and the requested software is activated (S101). When the software deliverable is used (S106), the software reads the management information in the software deliverable (S107), and searches the software management device for an ID included in the read management information (S108). Whether or not there is an ID is determined (S109), and if there is no ID, the software product cannot be used and error processing is executed (S110). If there is an ID, it is determined whether the amount of money corresponding to the ID is larger than the amount of money in the management information (S
111). If the usage amount is not more than the amount (unit price) written in the management information, the software product cannot be used, and the comment written in the management information is displayed (S112). If the amount of usage is more than the amount written in the management information, the unit price is subtracted from the amount of usage of the software management device, and the amount of usage of the software management device is overwritten (S113), and the software deliverable can be used. (S114), a software product is created on the memory of the content creation device (S115), and the process ends (S116). In addition, if necessary, it is possible to confirm how much the amount of software artifacts currently used remains in the software management device of the software artifact user (S102), and when the balance is confirmed (S10).
3) Then, the ID and the usage amount in the management information are read from the software management device and displayed to the user (S104), and the process ends (S105). Also, the public area can be assigned corresponding to the software artifact. FIG. 6 shows a second example of the software management apparatus according to the embodiment of the present invention.
3 is a configuration diagram of a public area of FIG. The same parts as those in FIG. 3 are designated by the same reference numerals and the description thereof will be omitted.

Area 3200 for software product seller
3400 are divided into an ID 3210, a password 3220, a software artifact (1) area 3240 to a software artifact (N) area 4260. Furthermore, the software product area is divided into a software product code 3241 and a usage amount 3242, when the software product (1) area 3240 is taken as an example.

The software product code 3241 is an area for storing identification information for identifying the software product created by the software product creator. The usage amount 3242 is recorded with charging information regarding charging when using the corresponding software deliverable, for example, information regarding available amount that can be used for payment. As a result, it becomes possible to manage each software product, and more detailed management becomes possible.

When the software utilizing apparatus uses the software deliverable, the software utilizing apparatus enables the reading and writing to the public area based on the password, and then uses the creator identification information written in the software deliverable management information. It is searched whether the same ID as a certain ID exists in the software product seller areas 3200 to 3400. If there is a corresponding ID, the software product sellers to which the ID belongs are searched for a software product code written in the software product management information, and the corresponding software product code is found. In that case, the amount set in the software deliverable is subtracted from the amount stored in the corresponding usage amount to overwrite it. If the usage amount becomes less than 0, by disallowing the usage,
It is possible to manage usage not only for software but also software deliverables.

FIG. 7 shows a specific example of such a public area. Area 3200a for software product seller (A)
To company A, area 33 for software product seller (B)
00a is assigned to company B, and their IDs are registered. In the password 3220a, a password for using the corresponding software deliverable or a password for permitting setting of the usage amount 3230a is registered. Area 3240a for software artifact (1) and area 3250 for software artifact (2)
In a, software product codes 3241a and 3251a for identifying the software product and usage amounts 3242a and 325 corresponding to the software product are provided.
2a is registered. For example, the software product (1) area 3240a is weather forecast data, and the available amount of money is 10,000 yen. Further, the software product (2) area 3250a is a button, and the available amount of money is 20000 yen.

Next, a method of managing the software deliverables when the software utilizing device uses the software deliverables by using such a software managing device will be described. FIG. 8 is a flowchart of the second software deliverable use process.

Use of the software deliverable is started (S
200), and activates the requested software (S20)
1). When the software deliverable is used (S206),
The software reads the management information in the software deliverable (S207), and searches the software management device for the ID and the software deliverable code included in the read management information (S208). It is judged whether the ID and the software product code are present (S209), and if I
If there is no D or software product code, the software product cannot be used and error processing is executed (S214). If the ID and the product code are present, it is determined whether the usage amount corresponding to the ID and the product code is larger than the amount in the management information (S210). If the usage amount is not more than the amount (unit price) written in the management information, the software deliverable cannot be used, and the comment written in the management information is displayed (S21).
3). If the usage amount is more than the amount written in the management information, the unit price is subtracted from the usage amount of the software management device, and the usage amount of the software management device is overwritten (S
211) and the software artifacts are available (S
212), a software artifact is created in the memory of the content creation device (S215), and the process ends if no other software artifact is used (S216). When using, the processing from S206 is repeated. In addition, if necessary, it is possible to confirm how much the software product user's software management device currently has the remaining amount of the software product usage amount (S202).
When the balance is confirmed (S203), the ID and usage amount in the management information are read from the software management device and displayed to the user (S204), and the process ends (S205).

Next, the software and software deliverables in the entire software management system using the software management apparatus according to the present invention, and the flow of the management information thereof will be described. FIG. 9 is a configuration diagram of a software management system according to an embodiment of the present invention. 1, 2,
The same parts as those in FIG. 3 are designated by the same reference numerals and the description thereof will be omitted.

The software sales company 10 sells software for generating software deliverables such as data and libraries. For example, the software 510a, 510b, 510c for creating contents is owned by the software utilization apparatus A (201a). The software is sold to the software user A, the software user B who owns the software using device B (201b), and the software product creator. Here, the software 510a, 510
b and 510c are common software. The software user A, the software user B, and the software deliverable creator who purchased the software 510a, 510b, 510c copy the software into the software using device A.
(201a), software using device B (201b),
It is stored in the hard disk or the like of the software deliverable creation apparatus 202. 201a, 201b, and 202 are devices that realize their functions by the computer 200. Further, the software sales company 10 supplies software as well as software management devices 100a, 100b, 100c that manage the software. The software 510a, 510b, 510c cannot be used without the software management apparatuses 100a, 100b, 100c. Software management devices 100a, 100b, 100 supplied from the software sales company 10
In c, information on a non-public area for software management is recorded. The non-disclosure area includes software utilization apparatus A (201a) and software utilization apparatus B (201a).
b), since it cannot be read from the software deliverable creation device 202, even if the software is copied illegally, the software management devices 100a, 100
It is not possible to run this software on a device without b, 100c. In this way, the software management device 1
Software can be managed using 00a, 100b, and 100c.

Next, in response to a request from the software user A, the software deliverable product seller uses the software deliverable product creating device 202 to create the software deliverable product. When the software sales company 10 permits the software product seller to sell the software product (hereinafter referred to as resale), in addition to the purchase price, the usage amount setting program 520, the ID 3210 for identifying the software product seller, A password 3220 is provided. The software deliverable creation device 202 of the software deliverable seller creates the software deliverable 601 based on these pieces of information, and adds the ID 3210 and the like assigned as related information of the software deliverable to the software deliverable. These software artifacts 601 are
It is provided to software user A in exchange for the purchase price. Software user A uses software deliverable 60
1 is stored in the hard disk or the like of the software utilizing apparatus A (201a). Further, the software deliverable seller receives the software management apparatus 100a connected to the software usage apparatus A (201a) and uses the usage amount setting program 520 to use the software management apparatus 10
ID3 assigned to a predetermined creator management information area of 0a
210, password 3220, product code, usage amount, etc. are set. Software deliverables that are allowed to be used 6
The software management apparatus 100a in which the software product management information about 01 is recorded is the software user A.
Then, the software utilization apparatus A (201a) can use the software deliverable 601.

Even if the illegally copied software artifact 602 generated by illegally copying the software artifact 601 passes to the software utilization apparatus B (201b), the software artifact related to the software artifact 601 is stored in the software management apparatus 100b. Since the management information is not set, the software deliverable 601 cannot be used.

Next, the software deliverable creation device 202
Creating software deliverables in.
First, there is a case where the information on the usage amount shown in FIG. 3 is created corresponding to the software product creator. Figure 10
6 is a flowchart of a procedure for creating a software artifact and its software artifact management information according to an embodiment of the present invention.

Production of software deliverables is started (S
For the purpose of (300), when the software is started and the production of the software artifact is started (S301), the software artifact is created in the memory of the computer (S30).
2). It is determined whether or not to use the pay-as-you-go system for managing software products (S303).
304), when the ID, the amount charged for one-time use, and the comment are set to the management information attached to the software artifact (S305), the management information set to the software artifact on the memory is added. (S306). If the pay-as-you-go billing is not performed, the item corresponding to the pay-as-you-go system is deselected on the software (S307).
After that, the contents of the software deliverable are encrypted so that the user cannot see them (S308), the software deliverable is completed (S309), and the production of the software deliverable is finished (S310). The processing up to this point is the processing on software.

Then, the usage amount setting process using the usage amount setting program 520 relating to the charging information setting is performed. FIG. 11 is a flowchart of the usage amount setting process according to the embodiment of the present invention.

The usage amount setting process is started (S400),
It is determined whether or not to charge on a pay-as-you-go basis (S401). If the pay-as-you-go system is not charged, the process ends (S40).
9). In the case of paying on a pay-as-you-go basis, the usage amount setting program is started (S402), and the software management device of the software product user is installed in the computer (S40).
3) Enter the ID, password and usage amount on the usage amount setting program. The usage amount setting program searches the set of ID and password in the public area of the storage device in the software management device and determines whether there is a match (S405). If there is a match, the used amount of money in the public area on the storage device of the software management device is set to the input amount (S406) and written to the software management device (S408). The setting program ends (S409). If there is no match, a warning indicating that they do not match is displayed (S407), and the usage amount setting program is terminated (S409). This completes the production of software deliverables.

Next, there is a case where the information about the usage amount shown in FIG. 6 is created in correspondence with the software result. FIG. 12 is a flowchart of a procedure for creating a software artifact and its second software artifact management information, which is an embodiment of the present invention.

Production of software deliverables is started (S
For the purpose of 500), when the software is started and the production of the software deliverable is started (S501), the software deliverable is created in the memory of the computer (S50).
2). It is determined whether or not to charge on a pay-as-you-go basis for managing software deliverables (S503). If you want to charge by the pay-as-you-go system, select the item corresponding to the pay-as-you-go system on the software (S504), the management information attached to the software deliverable, the ID, the software deliverable code, and the amount charged once used , Set a comment (S505)
Then, the management information set in the software deliverable on the memory is added (S506). If the pay-per-use billing is not to be performed, the item corresponding to the pay-per-use system is deselected on the software (S507). After that, the contents of the software deliverable are encrypted so that they cannot be seen by the user (S508), and the software deliverable is completed (S50).
9), the process ends. The above is the processing on software.

Then, the usage amount setting process using the usage amount setting program 520 relating to the charging information setting is performed. FIG. 13 is a flowchart of a second usage amount setting process which is an embodiment of the present invention.

The usage amount setting process is started (S600),
It is determined whether or not to charge by the pay-as-you-go system (S601). If the pay-as-you-go system is not charged, the process ends (S60).
9). In the case of paying on a pay-as-you-go basis, the usage amount setting program is started (S602) and the software management device of the software deliverable user is installed in the computer (S60).
3) Enter the ID, password, software deliverable code and usage amount on the usage amount setting program (S
604), the usage amount setting program searches the set of ID and password in the public area of the storage device in the software management device, and determines whether there is a match (S6).
05). If there is a match, the used amount of money in the public area on the storage device of the software management device is set to the input amount (S606) and written to the software management device (S608) to set the used amount of money. The program ends (S609). If there is no match, a warning indicating that there is no match is displayed (S60
7), the usage amount setting program ends (S60)
9). This completes the production of software deliverables.

Next, a processing procedure for editing an existing software product will be described. FIG. 14 is a flowchart of a software product editing process according to an embodiment of the present invention.

When the editing of the software artifact is started (S700), the software artifact is designated (S7).
01). First, it is determined whether or not there is management information in the designated software deliverable (S702). If not, the software product can be opened and edited (S708, S709). If there is management information, the ID is read from the management information (S703), and the password corresponding to the ID read from the software management device is read (S704). After that, the user is prompted to input the password (S705), and when the password is input (S70)
6) It is determined whether the input password and the read password match (S707). If they match, the software product can be opened and edited (S708, S709), but if they do not match, the software product cannot be edited without opening (S710). This is to prevent anyone other than the software product seller from editing the management information such as changing the unit price written on the software product.

As described above, according to the present invention, the software management device is configured to store the software start information and the software product utilization information.
Without using large infrastructure such as networks,
It has become possible to reliably manage the use of software and the use of software artifacts at the same time.

Further, instead of managing for each software product, it is possible to use even if the storage capacity of the storage device in the software management device is small, by managing for each software product seller. became. Also, if there are many storage devices in the software management device, by managing each software deliverable,
It became possible to set the usage amount for each software product, and it became possible to manage the use of the software product in more detail.

The processing functions described above can be realized by a computer. In that case, a program describing the processing contents of the function that the software management device should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing content can be recorded in a computer-readable recording medium. As a computer-readable recording medium,
There are magnetic recording devices, optical disks, magneto-optical recording media, semiconductor memories, and the like. The magnetic recording device includes a hard disk device (HDD), a flexible disk (FD), a magnetic tape, and the like. DVD (Digital Ver
satile Disc), DVD-RAM (Random Access Memor)
y), CD-ROM (Compact Disc Read Only Memory),
There are CD-R (Recordable) / RW (ReWritable).
Magneto-optical recording media include MO (Magneto-Optical disk).

When distributing the program, for example, a DVD or a CD-ROM in which the program is recorded.
Portable recording media such as. It is also possible to store the program in the storage device of the server computer and transfer the program from the server computer to another computer via the network.

The computer executing the program stores, for example, the program recorded in the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, the computer can also sequentially execute processing according to the received program each time the program is transferred from the server computer.

[0064]

As described above, the software management apparatus of the present invention stores desired data including management information of software and software deliverables. Then, it connects to a computer that uses software, and manages the use of predetermined software and software products by the computer according to the management information.

By managing the use of software using such a software management device, it is possible to manage software and its software deliverables without using large infrastructure such as a network.

Further, in the software management method of the present invention, management information of software and software artifacts is stored in advance, and when a use request for software or software artifacts is acquired from a connected computer, the management information is returned according to the management information. Determine the availability and notify the result.

As described above, the management information is stored in advance in the device connected to the computer, and the use of the software and the software product in the computer is managed, so that it is possible to securely perform the management without using a large infrastructure such as a network. It is possible to manage the software and its software deliverables.

Further, in the software management system of the present invention, the software product creating device creates software products using software. When the created software deliverable is used by the software utilizing device, the management information of the software managing device connected to the software utilizing device is set. When using software and software deliverables, the software utilizing device inquires of the software managing device whether or not it is available. The software management device determines whether or not the predetermined software and the software product can be used by the software using device according to the management information, and notifies the result.

As described above, the management of the use of the software in the software product creating apparatus and the management of the software and the software product in the software using apparatus are performed by using the software management apparatus, so that a large base such as a network can be obtained. It is possible to manage the software and its software artifacts reliably without using equipment.

Further, in the software management method of the software management system according to the present invention, the software artifact creating device creates the software artifact and related information. When the software utilizing apparatus uses the software deliverable, the software deliverable creating apparatus sets management information regarding management of the software deliverable in the software management apparatus according to the related information. The software utilization device connects the software management device and inquires about the availability, and when permitted, uses the software and the software deliverable.

As described above, the software deliverable creating apparatus that has created the software deliverable sets the management information for managing the software deliverable in the software managing apparatus, so that the software in the software utilizing apparatus is used by using the software managing apparatus. And, it becomes possible to manage software products. By performing management using the software management device, it becomes possible to reliably manage the software and its software deliverables without using a large infrastructure such as a network.

[Brief description of drawings]

FIG. 1 is a diagram showing a procedure until data broadcast content is created.

FIG. 2 is a configuration diagram of a software management system according to an embodiment of the present invention.

FIG. 3 is a configuration diagram of a public area of a software management device according to an embodiment of the present invention.

FIG. 4 is a specific example of a public area of a software management device.

FIG. 5 is a flowchart of a software product utilization process.

FIG. 6 is a configuration diagram of a second public area in the software management device according to the embodiment of the present invention.

FIG. 7 is a specific example of a second public area of the software management device.

FIG. 8 is a flowchart of a second software deliverable use process.

FIG. 9 is a configuration diagram of a software management system according to an embodiment of the present invention.

FIG. 10 is a flowchart of a procedure for creating a software artifact and its software artifact management information according to an embodiment of the present invention.

FIG. 11 is a flowchart of a usage amount setting process according to an embodiment of the present invention.

FIG. 12 is a flowchart of a procedure for creating a software artifact and its second software artifact management information, which is an embodiment of the present invention.

FIG. 13 is a flowchart of a second usage amount setting process which is an embodiment of the present invention.

FIG. 14 is a flowchart of a software product editing process according to an embodiment of the present invention.

[Explanation of symbols]

10 ... Software sales company, 20 ... Data broadcasting material providing company, 30 ... Data broadcasting content creation company,
40 ... Broadcasting station, 50 ... Communication satellite, 60 ... Home, 10
0 ... Software management device, 110 ... Processor, 1
20 ... Storage device, 200 ... Computer, 210 ...
CPU, 220 ... ROM, 230 ... RAM, 240 ...
・ Hard disk, 250 ... Display device, 260 ... Keyboard, 270 ... Mouse, 280 ... Bus

Claims (22)

[Claims] 1. A software management device that manages the software by connecting to a computer that uses predetermined software, and stores desired data including management information regarding management of the software and software deliverables generated by the software. And a control unit that controls transmission and reception of predetermined information with the computer and that controls the software and the software deliverable based on the management information. . 2. The storage means comprises a non-public area that can be controlled only by the control means, and a public area that can be controlled by the control means and the computer connected to the control means. The software management apparatus according to claim 1, wherein the software management apparatus is a software management apparatus. 3. The private area comprises a first storage area for storing first identification information for identifying whether or not the computer can use the software, and the control means comprises the computer. Transmitting a software activation control signal for enabling the software to the computer when the identification information transmitted from the computer and the first identification information stored in the first storage area match. The software management device according to claim 2. 4. The private area comprises a second storage area for storing second identification information for identifying whether or not the public area of the computer can be accessed, and the control means. When the identification information transmitted from the computer and the second identification information stored in the second storage area match, it is possible to access the public area of the storage means. The software management device according to claim 3. 5. The public area includes a boot information area that stores boot information in which the boot availability of a plurality of software is set, and the control means of the computer or the software management device boots each software in the computer. The software management device according to claim 2, wherein the software management device is permitted according to the startup information. 6. The public area is a creator management information area for storing software artifact management information for managing the software artifact corresponding to a software artifact creator who created the software artifact. The control means of the computer or the software management device may search the corresponding creator management information area based on related information about the software artifact associated with the software artifact used by the computer. The software management device according to claim 2, characterized in that 7. The management information area for creators comprises a creator identification information area for storing creator identification information for identifying the software product creator, and the control means of the computer or the software management device, Only when the creator identification information matching the creator identification information of the software artifact creator included in the related information of the software artifact is in the creator identification information area, the use of the software artifact is permitted. The software management device according to claim 6, wherein 8. The management information area for the creator comprises a creator identification information area for storing creator identification information for identifying the software product creator, and the control means of the computer or the software management apparatus, When the creator identification information of the software product creator included in the related information and the creator identification information of the creator identification information area match, the corresponding management information area for creator can be rewritten. 7. The software management device according to claim 6, characterized in that 9. The management information area for the creator further comprises:
A rewritable / unwritable information area storing rewritable / unwritable information for identifying whether or not rewriting of the software deliverable management information area by the computer is permitted, and the control means of the computer or the software management apparatus further includes the computer The rewriting of the creator management information area is permitted when the rewriting availability information transmitted from the user and the rewriting availability information stored in the creator management information area match. 8. The software management device described in 8. 10. The creator management information area further stores a software artifact management information area for storing software artifact management information for managing the software artifact corresponding to each of the software artifacts. The computer or the control means of the software management device, the software in the management information area for the creator corresponding based on the identification information of the software artifact associated with the software artifact used by the computer 7. The software management device according to claim 6, wherein the product management information area is searched. 11. The control means of the computer or the software management device further determines availability of each corresponding software artifact according to the software artifact management information. 10. The software management device according to item 10. 12. The management information area for the creator comprises a charging information area for storing charging information regarding charging for use of the software product, and a control means of the computer or the software management device stores the charging information in the charging information. 7. The software management device according to claim 6, wherein whether or not to use the software product is determined based on the determination, and the charging information is updated according to the use of the software product. 13. The billing information includes a usable amount that can be used by a user who uses the software deliverable, and the control means of the computer or the software management device can use the usable amount. 13. The software management device according to claim 12, wherein the software deliverable is made available when the amount is larger than the usage amount of the software deliverable. 14. A software management method for managing the software by connecting to a computer using predetermined software, in which management information on management of the software and software deliverables generated by the software is stored in advance. A step of connecting to the computer, a step of obtaining a use request of the software or the software deliverable from the computer, and the availability of the software or the software deliverable in the computer according to the management information. And a step of notifying the computer of availability, the software management method comprising: 15. A program for causing a computer to realize a function of managing the software by connecting to a computer using predetermined software, the management information relating to management of the computer and the software deliverable generated by the software. Storage means for storing desired data including: control means for controlling transmission / reception of predetermined information to / from a computer using the predetermined software and managing the software and the software deliverable based on the management information A program characterized by causing it to function as. 16. A software utilization device that uses a predetermined software, a software artifact production device that produces a software artifact using the software, and a connection to the software utilization device or the software artifact production device. In a software management system including a software management device that manages the software, a storage unit that stores desired data including management information regarding management of the software and software deliverables generated by the software; A software management device including control means for controlling transmission and reception of predetermined information to and from the device and managing the software and the software deliverable based on the management information; and the software and the software. Storage means for storing a hardware artifact, and a control means for determining availability of the software and the software artifact according to the software management device and using the software and the software artifact when permitted. A software utilizing device, a storage means for storing the software, the software product is generated using the software, and management information of the software managing device connected to the software utilizing device is set as necessary. A software management system comprising: a software deliverable creation device including control means. 17. The software management system according to claim 16, wherein the control means of the software artifact creating device further comprises means for performing encryption processing on the created software artifact. 18. The control means of the software deliverable creation device generates relevant information about the software deliverable including identification information that enables identification of the software deliverable when creating the software deliverable, and the software deliverable. 17. The method according to claim 16, which is added to an object.
Software management system described. 19. The control means of the software deliverable creation device manages the software deliverable in a storage means of the software management device connected to the software utilizing device according to related information about the software deliverable. 19. The software management system according to claim 18, wherein the software product management information of is set. 20. The control means of the software deliverable creation device discloses the identification information of the software creator included in the related information of the software deliverable and the storage means of the software management device connected to the software utilizing device. 2. The software product management information in the management information area for the creator, which matches the identification information of the software creator provided in the area, is set.
9. The software management system described in 9. 21. The control means of the software deliverable creation device further adds identification information for identifying whether or not to permit editing processing on the software deliverable to the related information on the software deliverable, If editing of the artifact is requested,
19. The software management system according to claim 18, wherein permission of the editing process is given according to the identification information. 22. A software utilization device that uses predetermined software, a software artifact production device that produces a software artifact using the software, and a connection to the software utilization device or the software artifact production device. In a software management method in a software management system including a software management device that manages the software, the software artifact creating device creates a desired software artifact using the software and is related to the software artifact. Generating related information and adding it to the software product, and a software management device for connecting to the software device when the software product is used in the software device Setting management information relating to management of software deliverables generated by the software according to the related information; connecting the software utilization apparatus and the software management apparatus to store the management information stored in the software management apparatus Determining whether or not the software and the software deliverable can be used in the software using device according to information, and using the software and the software deliverable in the software using device according to the determination result, A software management method comprising the steps of: