JP2002041174A - Information managing device, information management system and storage medium stored with information management software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To control the use of software variously by providing various control information for limiting the use of the software in order to create the environment where a user can more easily utilize the software. SOLUTION: This information managing device is provided with a storage part for controlling the use limit of software having a storage area in which kind information showing the kind of the use limit of software is stored and a storage area in which information showing the use limit is stored, a software storage part in which software corresponding to the storage part is stored, and a means for changing the contents of the storage part based on the use of the software corresponding to the storage part.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus and a method for controlling the use of software or a medium storing the same.

[0002]

2. Description of the Related Art Conventionally, software attached to a magazine appendix has been used for a limited period (for example, 60 days).

[0003]

[Problems to be solved by the invention] Special registration 2810033
However, since the battery is supplied by the FD, there is a risk that the battery FD may be illegally copied. In addition, it takes time (time lag) to mail the FD, and there is a possibility that the business will be interrupted. Furthermore, there is a risk of loss or breakage of the FD.

Next, Japanese Patent Publication No. Hei 7-89305 has the following problems.

[0005] There is a problem in the use termination process (when the host machine performs the process, if a communication device such as a modem fails, the use termination process is not performed and the user is charged for the time not in use. When processing by the user machine, if there is a power failure, etc., the usage termination processing will not be executed on the user machine side, and it will be impossible to calculate the usage time or if the system date is manipulated when restarting after a power failure However, even if it can be detected, the change of the system date during the operation of the application may be performed for system management and management reasons even if it is not a fraud (an emergency in the year 2000). Date 199 as correspondence
Return to 9/12/30). It is inconvenient if the app can no longer be used in such a case.

[0006] Therefore, the calculation of the usage fee is carried out by From To.
There are limits to what you can do.

[0007] Since the fee is the same in the case of referencing only and in the case of frequent use of input, there is a feeling of being overpriced in the case of referencing only (cannot charge according to the usage).

On the other hand, according to the present invention, it is possible to charge the battery in real time. There is little risk of duplication. It is also possible to charge the battery automatically when the remaining battery capacity is less than a certain level. Operation of the system date is meaningless because it will be used. Even if the application suddenly drops due to a power outage, etc., there is no disruption to the billing process.-The battery is prepaid, so there is no time lag until the billing, and the financing of the provider is easy. On the other hand, users can avoid overuse (over budget) without their knowledge.

[0009]

In order to achieve the above object, the present invention provides a storage medium storing software and management software for managing the software, wherein the management software includes the software. Restoring and changing the management state of the storage medium.

According to the present invention, there is provided an information processing apparatus provided with a storage unit for storing management software for managing software to realize the above-mentioned object, wherein the management software restores the management state of the software. An information processing apparatus comprising: means for changing; and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means.

The present invention has been made in order to realize the above-mentioned object.
An information processing apparatus comprising: means for restoring and changing the management state of management software for managing software; and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means. Features.

The present invention has been made in order to achieve the above-mentioned object.
An information processing apparatus comprising: means for restoring and changing the management state of management software for managing software; and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means. Features.

The present invention has been made in order to achieve the above-mentioned object.
An information processing apparatus comprising: means for restoring and changing the management state of management software for managing software; and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means. Features.

The present invention provides means for restoring and changing the management state of management software for managing software, and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means. Means for transmitting information for restoring the management state of the management software in response to a request from the information processing apparatus, in a host device for restoring the management state of the management software by communicating with an information processing apparatus having A host device provided with

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will be described below with reference to the drawings.

In FIG. 1, on a user machine PC on which a “software battery management system” exists, a “site access tool” charges a battery from a host machine HM in cooperation with the system.

* The "site access tool" stores information on the host machine HM to be connected to, for example, a readable storage medium CD,
It is provided to the user by being incorporated in advance in an MD, FDD, semiconductor memory, or the like. When software is provided by communication, it may be received via a communication medium together with the software.

A "battery supply module" is incorporated in the host machine HM, and supplies a battery selected by the user to a predetermined location in a designated amount. The predetermined location is provided on the user machine PC or provided on a server.

FIG. 1 is a block diagram of the present invention. In FIG. 1, a PC is a user's computer, which is downloaded from a removable storage medium CD and set up. Operating software for controlling the expiration date is at least stored.

The storage medium CD stores applications and operating software. More specifically, the operating software includes an access tool and a battery data structure list. A predetermined value is set as an initial value in the battery data structure list, and the application can be restarted by rewriting the value of the data later. The operating software includes a software battery management system and a site access tool.

HM is a host machine, a computer PC
To extend the validity of the above application software, communicate with the host machine HM,
The validity period can be extended by rewriting the above value.

In the host machine HM, a user's log record LL, an expiration date update module, an application list AL, and a supply list SL are stored in a memory.

The above-mentioned application list AL, battery list BL and battery supply history list BH are shown in FIG.
It is as shown in FIG. With this list, it is possible to set the matching of the application and the unit price of the battery for each application. Here, the battery means information for controlling the use of the application software (for example, controlling the time and the number of times).

Startup procedure (1) The "site access tool" of the user machine is the address information of the information host machine that the user has, and in the case of the Internet, it is the IP address or URL. A connection is made to the host machine HM according to the information. (2) The “battery supply module” of the host machine provides information on a list of batteries that can be provided. Such information is listed and displayed on the screen of the display device of the user machine. (3) The "site access tool" that receives the battery list information inquires of the "software battery management system" whether or not each battery is already managed, and classifies the managed battery and the non-managed battery to the user. indicate. (4) The user moves the cursor to the desired battery and the amount thereof from the displayed batteries, and selects a desired battery. A numerical value may be input from the input device without moving the cursor. (5) The “site access tool” sends the battery and amount selected by the user to the “battery supply module”. (6) The “battery supply module” creates additional battery information based on the received battery and amount, and sends it to the “site access tool”. The information at this time is recorded as a log. (7) The “site access tool” that has received the additional information of the battery transfers the information to the “software battery management system” and confirms that the battery has been charged. (8) The “site access tool” sends the confirmation information to the “battery supply module”. (9) In the “battery supply module”, this confirmation information is also recorded in addition to the previous log. (10) When a series of communication ends, the “site access tool” ends communication with the host machine.

Of course, after the battery is supplied, the value decreases each time the application is used on the user machine, and the application cannot be used.

The above-described process will be further described with reference to the sequence flow of FIG. 5 and the control flow shown in FIG. This control flow is control performed on the user machine PC. A program according to the control flow is stored in the memory, and the program is executed by the processing unit to perform control. The following steps are executed by the processing unit.

In step 301, an IP address or a URL
To the host machine HM according to the following. When the connection is established, a battery list and a key 1 list are received from the host machine HM in step 302. Next, in step 303, the presence / absence of the battery and the remaining amount are confirmed in the software battery management system, and the battery list is rearranged. Next step
The battery list rearranged in 304 is displayed on the display screen of the computer PC. Next, in step 305, the user operates the mouse to move the cursor on the battery and the battery amount from the battery list displayed on the display screen to select the battery and the battery amount. Next, it is determined in step 306 whether to cancel. If it is to be continued, in step 307, the battery issue request and the key are
Send to In the next step 308, battery additional information is received from the host machine HM. In step 309, the additional battery information is sent to the software battery management system to be charged. At step 310, charge confirmation information is received from the software battery management system. In step 311, charge confirmation information is transmitted to the host machine HM together with the key 1. In step 312, the key 3 is received from the host machine HM.

In step 313, charge confirmation information and key 1
And key 3 are combined and displayed for user confirmation.
In step 314, the connection with the host machine HM is terminated.

Next, the battery supply module will be described based on FIG. 4 with reference to the sequence of FIG. This control flow is control performed on the host machine HM. A program according to the control flow is stored in the memory, and the program is executed by the processing unit to perform control. The following steps are executed by the processing unit.

In step 401, a connection from the user machine PC is waited. In step 402, a key as a session number is generated, and the battery list and key 1 are transmitted to the user machine PC. In step 403, the battery amount, key 1, and key 2 from the user machine PC are received. Step 40
4. Determine if timeout. If it is not time-out, it is determined in step 405 whether or not key 1 and key 2 correspond to each other. If yes, in step 406, additional battery information is generated, transmitted to the user machine PC, and recorded in a log. In step 407, charge confirmation information and key 1 are received from the user machine PC. It is determined in step 408 whether or not a timeout has occurred. If not, a key 3 is generated from the charge confirmation information in step 409 and added to the log. Step 410
Transmits the key 3 to the user machine PC.

Next, in step 411, the connection with the user machine PC is terminated.

After charging the battery with such a connection,
Move on to running the application. By executing the application, recharging is performed again in the process described above,
Run the application again.

Next, another embodiment of the battery used in the above embodiment will be described.

As members for controlling the use of software,
The information for controlling the use of software is stored in a memory using, for example, a floppy (registered trademark) and is referred to as a battery because it controls the use of software. The configuration of the battery is, as shown in FIG.
Area to be stored. Also, an area where a floppy identification information file FIF is stored. This stores information on whether the floppy disk is regular or illegal (for example, to determine whether the floppy disk is illegally generated). Further, an area for storing a floppy battery program is provided. This battery program is a program having a function of communicating with a battery manager in a user machine at the time of battery replenishment / removal, and selectively handling a battery for an application which is a start source. When this program is called, a battery ID and an operation mode (either replenishment or removal) are designated as parameters at the time of startup.

Finally, an area for storing the battery file BF is provided. It stores an encrypted file consisting of a combination of battery capacity as well as information for checking the integrity of this data. There can be more than one of this file.

FIG. 7 is a flowchart showing the above-described battery program, which is stored in the user machine and executed by the processing unit on the user machine PC shown in FIG.

The operation will be described below according to a flow.

In step 71, the battery ID is arbitrarily assigned from the parameters at the start of acquisition and written in the area for storing the battery program. Next, in step 72, the operation mode is obtained. Next, in step 73, the data in the storage area corresponding to the validity of the floppy is read, and the content is confirmed by the processing unit. Next, the routine proceeds to step 74, where a battery file name is generated. Next, the process proceeds to step 75, where it is determined whether the operation mode is the replenishment mode.
Move to step 76. Check that the battery file exists on the floppy. If there is, the process proceeds to step 77 to check the battery information. When that is completed, check whether the battery can be replenished, and go to step 79. The battery amount is transferred to the battery manager of the user machine PC. Delete the floppy file. Next, the identification information of the floppy disk is updated, and the process ends. If the operation mode is the retrieval mode, the information is retrieved from the floppy and checked for the existence of the battery file. If it does not exist, check whether a battery file can be created, and if so, create a battery file and move the battery amount from the battery manager.
Next, the identification information of the floppy is updated.

By storing the identification information in the above-described configuration, it is possible to prevent the illegal copying of the floppy disk.

Further, by storing a program in a floppy disk, a self-check of the format information of the floppy disk becomes possible.

Further, the self-inspection of the consistency of the battery information can be performed.

By communicating with the battery manager of the user machine, the battery can be selectively handled.

The confidentiality of the floppy battery information can be enhanced by upgrading the version of the program.

A plurality of battery files can be created on one floppy.

Next, another embodiment of the battery will be described.

FIG. 8 is an explanatory diagram for making the types of batteries.

FIG. 1 shows an example in which a floppy is used exclusively for a battery. In the figure, BP indicates an area where a battery program is stored. The CDF is an area where a management data file is stored. BDA indicates an area where battery data is stored. Here, battery data A is stored, and data for controlling the application program A and data for executing for a predetermined time are stored. Here, it is usually called a battery.

The BDB stores battery data B and is data for controlling the application program B, and stores data that allows the application B to be used without limitation. Here, it is called an unlimited battery.

The format of the management data file is
As shown in FIG. 8, the area for storing the serial number of the floppy, the area for storing the date and time information of the last operation, the area for storing the ID of the last operated battery, and the area for storing the summary of the last operated battery are provided. Provided. The battery data format includes an area for storing identification information of a battery type (here, trial, normal, and unlimited three types of batteries are provided, so that information for identifying the three types is allocated), an area for storing battery capacity, An area for storing a charge enable / disable identification flag, an area for storing a detachable / impossible identification flag, and a spare value for the remaining use time / number of times are provided. Next, the use of the above-described battery will be described.

FIG. 9 shows a display example when a battery is used. In the drawing, is an explanatory diagram showing a state in which an unlimited battery or a normal battery having a full capacity is mounted on a device. FIG. 5 is an explanatory diagram showing an example in which a state in which one normal battery that has consumed about 55% is mounted is displayed.
FIG. 4 is an explanatory diagram showing a display example in a state where one trial battery is mounted on a device. FIG. 4 is an explanatory diagram showing a state where two batteries, a normal battery and a trial battery, are mounted. In this case, the battery is usually consumed. Is a text display for explaining a battery mounting state, and displays a status of a battery mounted by an application in use. It is configured to indicate which battery is consumed. FIG. 7 is a diagram for explaining a display example for enabling a display format of a battery to be selected from a graphic display and a text display.

FIG. 10 is a diagram showing a control flow for controlling the display of the battery described above.

The display control will be described with reference to FIG.

In step 101, a battery ID is obtained. Next, the operation mode is obtained. Next, at step 103, it is determined whether or not a graphic display is to be performed. If the graphic display has been selected, a process of displaying the battery mounting state is performed, and display data as shown in the previous figure is created and displayed on the display. In step 103, if no, it is determined whether or not it is in text format, and if so, step 10
The display data of the mounting status is created in step 6, and the display shown in is performed.

If NO in step 105, the process is terminated without controlling the display of the mounting status.

Next, the use prediction of the battery mounted on the device will be described.

FIG. 11 shows a display screen for battery use prediction. Shows one of the prediction screens, and shows another example of the prediction screen.

For prediction, the data format of the battery is configured as shown in the figure.

The area for storing the battery type identification information, the area for storing the battery capacity, the chargeable / impossible identification flag area, the detachable / impossible identification flag area, and the area for storing the calculation result of the remaining use time / number of times. Configure the data format. The usage history information stored in the system includes battery ID, usage start date and time,
An area for storing the software use end date and time, use time, and number of units used is provided. In addition, an area for storing the battery ID, the cumulative use time, and the cumulative number of units used is provided as a total data file.

Next, the process of estimating the usable time / number from the control flow shown in FIG. 12 will be described. In step 1201, a battery ID is obtained, and in step 1202, an operation mode is obtained. The process proceeds to next step 1203, where it is determined whether the target function is used. If yes, step 12
Moving to 04, it is determined whether or not the battery has been used for the first time after the startup. If yes, the use start date and time is recorded in the history file in the machine in step 1205. The next step is to count the number of units used in the history file in the machine. It is determined in step 1206 whether or not the vehicle has passed the notification point. If the vehicle has passed, the process proceeds to step 1208 to display a remaining amount warning and display the warning on the display. Next, it is determined in step 1209 whether the use of the target software has been completed. If no, the process returns to step 1203 to repeat the above processing. If completed, the process moves to step 1210, where the use end date and time are recorded in the history file in the machine, and the process ends.

Next, the process of charging the battery will be described with reference to the drawings.

FIG. 13 is a diagram showing a charging flow. Explanation will be given according to the figure.

In step 1301, it is determined whether the battery to be charged is an unlimited battery. With unlimited batteries,
The charging process ends. If not, step 13
The process proceeds to 02, where the remaining amount is checked. If the available capacity is large, the charging process is performed in step 1303. If the charging is performed, the charging process ends. In step 1304, it is determined whether or not to permit the partial charging. If yes, the charging process is performed in step 1305, and if the charging is completed, the charging process ends. Next, a case where an unlimited battery is charged will be described with reference to FIG.

At step 1402, it is determined whether an unlimited battery is mounted. If so, a notice to that effect is output on the display screen as shown in the figure, and the process ends. If there is no unlimited battery in step 1401, a battery is generated, a message as shown in the figure is displayed, and a message indicating completion of mounting is displayed.

Next, the case where the trial battery is charged will be described with reference to FIG.

In step 1501, it is determined whether the trial battery of the sub key is mounted. If so, a message as shown in the figure is displayed and the process ends. Steps
If no at 1501, generate a trial battery for the subkey with the specified capacity. At this time, during the installation of the message being generated as shown in the figure and when the charging is completed, a message indicating the completion of the mounting is displayed as shown in the figure, indicating the completion of the power reception.

FIG. 16 shows a control flow of the battery use restriction and the process of reproducing the restriction when the restriction is reached.

A description will be given with reference to the drawings. First step 1601
To obtain the battery ID. Next, in step 1602, the operation mode is acquired. In the next step 1603, the current date and the expiration date are compared, and if yes, the battery is usable, and the process of checking whether the battery is usable ends. If no at step 1603, step
At 1605, the current date and the expiration date are further checked. If yes, in step 1606, warning display data is created and displayed on the display. Next, if "Purchase Now" is operated, the process proceeds to the battery purchase routine. If no, the battery is still usable, so that the process of enabling the battery is performed in step 1608, and this process ends. If a negative result is obtained in step 1605, data for a warning display is created in step 1609, and the data is displayed on the display and displayed in step 16
In 10 it is checked whether the screen was clicked next,
A process is performed as to whether to go to the purchase routine or to proceed to the operation of the device for the time being, and when the process is completed, this process ends.

FIG. 18 shows a flow for checking whether the battery is purchased or used continuously when the battery is of a limited time type.

In the same figure, at step 1801, the battery I
D is acquired, and then the operation mode is acquired in step 1802. After that, in step 1803, the current date + X use start date + expiration date is compared. If yes, it means that the battery can be used, and the processing is performed in step 1804, and the processing ends. If no at step 1803,
In step 1805, the current date is compared with the use start date + expiration date. If yes, a warning is displayed in step 1806 as shown in FIG. 19, and an instruction to purchase the battery now or later is made. And if it is a purchase right now, the process proceeds to a purchase process; otherwise, a process for enabling the battery is performed in step 1808, and this process ends. If no in step 1805, a warning is displayed in step 1809, and FIG.
As shown in FIG. 9, the process shifts to a process of waiting for an instruction, the process is performed in accordance with the instruction as described above, and the process ends.

Next, with reference to FIG. 20, a description will be given of a process of controlling whether to use the battery or to subscribe to the battery of the unused period trigger type.

In the figure, at step 2001, the battery I
D is obtained, and then in step 2002, the operation mode is obtained. Thereafter, in step 2003, the current date + X is compared with the latest use date + unused period. If yes, it means that the battery can be used, and the processing is performed in step 2004, and the processing ends. If “No” in step 2003, the current date and the latest use date + unused period are compared in step 2005, and if yes, a warning is displayed in step 2006 as shown in FIG. In 2007, the battery is enabled, and the process ends. Steps
If "No" in 2005, a warning is displayed in step 2008, and the process proceeds to the waiting for instruction as shown in FIG. 19, and it is determined whether or not to purchase immediately. If the battery is purchased, the process proceeds to a purchase routine, and the process is terminated.

FIG. 22 is a diagram showing a flow of the battery purchase processing. The processing will be described with reference to this figure. In the same figure, in step 2201 S. in the client machine
A search is made to see if AT is present, and the result is returned to step 22.
If it is determined in 02, if there is, a purchase screen is created in step 2203 and displayed, for example, as shown in FIG. Steps
At step 2204, the process waits for a purchase battery selection operation, and at step 2205, a payment screen display process is performed and displayed.

If "NO" in step 2202, a SAT download request screen is created in step 2207, and the display is displayed as shown in FIG. 23. If a click operation is performed, the SAT is displayed. Downloaded from the site.

Next, a case where there are a plurality of battery purchase sites will be described.

FIG. 24 shows a case where a plurality of items are stored in a user's machine.
If SAT (site access tool) exists, all S
Example of searching for the battery you want to purchase with AT and displaying the result.

By installing this function, the user can compare prices of other sites and purchase them.

At step 2401, a parameter is set for the number of download sites, and at step 2402 the number of site access tools on the client machine is searched.
If there is a site access tool in step 2403, the number of site access tools is put into n in step 2404. Next, in step 2405, M = M + 1 is executed.
In step 6, the M-th site access tool is used to connect to the battery sales site, search for A (battery name), and obtain the sales information. For example, battery name, type and price.

It is determined whether or not M ≧ N, and if “yes”, a battery purchase screen is displayed as shown in FIG. Next, the user operates the screen to select a purchased battery in step 2410. Next, a payment screen is displayed in step 2410, and a payment method is selected and payment information is input in step 2412.

If “No” is obtained in step 2403,
In step 2413, a download request screen of the site access tool is created and displayed on the screen as shown in FIG.

Next, the handling when the battery is invalid will be described.

When the battery is invalid, charging of the battery is performed in the following manner. With prepay, the user
Refund [unused amount-predetermined cancellation fee]. Unused parts are calculated from [Battery level].

Note that the amount of money is calculated after the battery distributor collects the invalid battery from the user, and then calculates and notifies the user. Charging when the battery is invalid enables adaptation to normal / unlimited batteries.

Next, description will be made with reference to FIG. In step 2601, a battery ID is obtained. Then in step 2602,
Get the operation mode. In step 2603, a display indicating that the battery is invalid is created, and a display to that effect is displayed on the screen as shown in FIG. Next, when the icon "purchase battery now" is operated, step 220 in FIG.
Move to 1.

If "NO", the battery information of the user is taken out, sent to the purchaser, and the purchaser checks the contents of the battery, and checks in step 2607 whether the battery is accepted. If it is “no”, it is displayed as shown in FIG.

If “yes” in the step 2607, a refund amount is calculated after calculating the actual use amount of the purchaser battery, and then the refund is notified to the purchaser user, and the process is terminated.

Next, a description will be given with reference to FIG. In step 2801, a battery ID is obtained. Then in step 2802,
Get the operation mode. In step 2803, a display indicating that the battery is invalid is created, and a display to that effect is displayed on the screen as shown in FIG. Next, when the icon "purchase battery now" is operated, step 220 in FIG.
Move to 1.

If “NO”, the battery information of the user is extracted and sent to the purchaser, and the purchaser checks the contents of the battery, and checks in step 2807 whether the battery is accepted. If "No", display is made as shown in FIG.

If “yes” in the step 2807, the actual charge of the purchaser battery is calculated, the charge is calculated, and then the charge is notified to the purchaser user, and the process ends.

Next, an example in which the FD of the battery can be generated by, for example, a device installed in a convenience store will be described.

The operation will be described.

First, the user specifies the type of software and the payment method from the convenience store device.

Next, when the battery is requested, the FD is set in the terminal, the FD is read from the FD, and the terminal sends a serial number unique to the terminal to the server. The serial NO generates encrypted data, and the server sends the encrypted battery source data to the terminal.

Thereafter, the terminal side decrypts the encryption, checks the matching between the transmitted serial number and the terminal-specific serial number, and then generates battery data.

Further, user registration can be performed at a convenience store terminal. In addition, if a prepaid card is used to generate a battery in the floppy disk, anonymity can be maintained.

Further, an FD in which only key data is written at a convenience store is sold, and the FD can be used to change from a trial version to a product version offline or upgrade a paid version using the FD.

[0096]

According to the present invention, * information for charging a battery is not transmitted as a file, and communication via a program is always performed.
It is difficult to copy files by simple operations such as copying files. * Among the provided batteries, the battery that the user has already used and the one that is not can be distinguished, so that the user is not confused when operating. * Confirmation information at the time of charging the battery is recorded in the log of the host machine, so that it is possible to provide a means for assuring that the user machine is properly charged.

Since the battery type is provided, software management can be centrally managed. Since the type of the battery is provided, the control of the restoration can be controlled according to the type of the battery, so that it is possible to provide a system which is easy for the user to use.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an overall outline of the present invention.

FIG. 2 is a diagram showing a data structure in a battery supply module.

FIG. 3 is a flowchart illustrating an embodiment of the present invention.

FIG. 4 is a diagram showing a flowchart of a battery supply module.

FIG. 5 is a diagram showing a protocol between a user machine and a host machine.

FIG. 6 is a view for explaining a floppy file structure;

FIG. 7 is a diagram illustrating a flow of a battery program.

FIG. 8 illustrates a configuration of a battery floppy.

FIG. 9 illustrates a display example of a battery.

FIG. 10 is a diagram illustrating a flow of controlling display of a battery.

FIG. 11 is a diagram illustrating a display of a battery.

FIG. 12 is a diagram for explaining a flow of estimating a usable time / number of times from a battery remaining amount

FIG. 13 is a diagram illustrating a flow for controlling charging of a normal battery.

FIG. 14 is a diagram illustrating a flow for controlling charging of an unlimited battery.

FIG. 15 is a diagram illustrating a flow for controlling charging of a trial battery.

FIG. 16 is a diagram illustrating a control flow of battery use restriction and regeneration.

FIG. 17 is a view for explaining display during battery use restriction and reproduction control.

FIG. 18 is a diagram illustrating a flow of controlling whether to purchase a battery or to use the current battery.

FIG. 19 is a diagram showing a display screen when a battery is purchased.

FIG. 20 is a flowchart for controlling whether to purchase a battery or use the current battery.

FIG. 21 is an explanatory diagram of a display screen showing purchase of a battery.

FIG. 22 is a diagram illustrating a control flow of battery online purchase.

FIG. 23 is a view for explaining a screen display at the time of controlling battery online purchase.

FIG. 24 is a diagram illustrating a control flow of battery online purchase.

FIG. 25 is an explanatory diagram of a display screen showing purchase of a battery.

FIG. 26 is a flowchart of charging control when the battery is invalid.

FIG. 27 is an explanatory diagram of a display screen at the time of charging control when the battery is invalid.

FIG. 28 is a flowchart of charging control when the battery is invalid.

FIG. 29 is an explanatory diagram of a display screen at the time of charging control when the battery is invalid.

[Explanation of symbols]

 CD storage medium PC user machine HM host machine

(72) Inventor Yoshiaki Kurasawa 3-11-28 Mita, Minato-ku, Tokyo Canon Sales Inc. (72) Inventor Kyoichi Hoshino 3-1-128 Mita, Minato-ku, Tokyo Canon Sales Inside (72) Inventor Yoshiko Furuyama 3-11-28 Mita, Minato-ku, Tokyo Canon Sales Inc. (72) Inventor Toshihiko Wada 3-11-28 Mita, Minato-ku, Tokyo Canon Sales Co., Ltd. F-term (reference) 5B076 FB18 FC10

Claims (19)

[Claims] 1. A storage medium storing software and management software for managing the software, the storage software comprising a step of restoring and changing the management state of the software. 2. The storage medium according to claim 1, wherein the storage medium stores a predetermined address for restoration and change, and is connected to the address. 3. An information processing apparatus comprising storage means for storing management software for managing software, wherein the management software restores and changes the management state of the software, and Means for connecting to a predetermined site in order to restore the management state of the management software. 4. The information processing apparatus according to claim 3, further comprising means for receiving information from a predetermined site and storing the information in the storage means. 5. A means for restoring and changing the management state of management software for managing software, and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means. Information processing equipment. 6. The information processing apparatus according to claim 5, further comprising a selecting unit for restoring a management state by said restoring and changing unit. 7. A means for restoring and changing the management state of management software for managing software, and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means. A host device that communicates with the information processing apparatus and restores the management state of the management software, comprising: a unit that transmits information for restoring the management state of the management software in response to a request from the information processing apparatus. Host device. 8. The host device according to claim 7, wherein said host device includes means for storing information for restoring a management state for a plurality of management software. 9. A storage medium for controlling software usage restriction, comprising a storage area for storing type information indicating the type of software usage restriction and a storage area for storing information indicating the usage restriction. 10. The storage medium according to claim 9, wherein any one of information indicating trial, normal, or unlimited is stored as the type information. 11. The storage medium according to claim 9, wherein said storage medium further comprises an area for storing management data. 12. A storage unit for controlling a software use restriction, comprising: a storage area for storing type information indicating a type of software use restriction; and a storage area for storing information indicating the use restriction. Means for changing the contents of the storage unit based on use of software corresponding to the storage unit. 13. The storage device according to claim 1, wherein a plurality of storage units are arranged.
3. The management device according to claim 2. 14. The information processing apparatus according to claim 12, further comprising a storage unit in which software corresponding to the storage unit is arranged. 15. A storage unit for controlling software usage restriction, comprising: a storage area for storing type information indicating a type of software usage restriction; and a storage area for storing information indicating usage restriction. A management device comprising: a software storage unit that stores software corresponding to a storage unit; and a unit that changes contents of the storage unit based on use of the software corresponding to the storage unit. 16. The storage medium according to claim 9, wherein said storage medium has a storage area for storing a plurality of types of information. 17. A means for restoring and changing the management state of management software for managing software, means for connecting to a predetermined site to restore the management state of the management software by the restoration means, and An information processing apparatus comprising: control means for displaying a message about a software restoration change sent from the site. 18. A means for restoring and changing the management state of management software for managing software, and means for connecting to a predetermined site for restoring the management state of the management software by the restoration means. A host device that communicates with the information processing device and restores the management state of the management software. A host device including a unit for transmitting information to be restored. 19. The host device according to claim 18, wherein the control unit has a function of attaching the information indicating the supply source of the information to be restored when transmitting the message.