JP2010049643A - Information processing system, information processing method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing system, an information processing method, and a program which enable a user to easily obtain again a program which is provided to the user in a state of being stored in a rewritable information storage medium. <P>SOLUTION: A control part 20 of a product management server 2 generates program identifiers corresponding to programs stored in a rewritable semiconductor memory. A storage part 21 of the product management server 2 accepts a program identifier from a user and stores program provision data showing that a program corresponding to this program identifier has been provided, in association with an identifier of the user. When the control part 2 of the product management server 2 accepts a request for re-provision of a program from a user, the program is provided again if program provision data showing this program has been provided is stored in the storage part 21 of the product management server 2 in association with an identifier of this user. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information processing system, an information processing method, and a program.

  Various information storage media such as a CD-ROM, a DVD-ROM, and a USB (Universal Service Bus) memory are known. Conventionally, programs such as application software are often stored in a non-rewritable information storage medium such as a CD-ROM and provided to users.

  After the program stored in the information storage medium and provided to the user is installed in a hard disk or the like provided in the personal computer, the program stored in the information storage medium is no longer necessary. Here, when a program is stored in a rewritable information storage medium such as a USB memory, the user can delete the stored program and freely store various data in the storage area in which the program is stored. This information storage medium can be used effectively.

  However, it may be necessary to reinstall the program due to circumstances such as purchasing a personal computer or a hard disk after deleting the program and writing other data. In such a situation, it is desirable that the user can easily obtain the program again.

  In addition, it is conceivable that the user accidentally deletes the program stored in the information storage medium before installing the program. Even in such a situation, it is desirable that the user can easily obtain this program again.

  The present invention has been made in view of the above problems, and an information processing system and an information processing method by which a user can easily re-acquire a program stored in a rewritable information storage medium and provided to the user. And to provide a program.

  In order to solve the above problem, an information processing system according to the present invention includes a program identifier generation unit that generates a program identifier provided to a user together with a semiconductor memory corresponding to a program stored in a rewritable semiconductor memory. Receiving program identifier from the user and storing program provision data indicating that a program corresponding to the program identifier is provided in association with the identifier of the user; When the program provision data indicating that the program is provided is stored in the program provision data storage means in association with the user's identifier when receiving the program re-provision request, the program is re-executed. Provided program re-provision means , Characterized in that it comprises a.

  An information processing method according to the present invention includes a program identifier generation step for generating a program identifier provided to a user together with the semiconductor memory, corresponding to a program stored in the rewritable semiconductor memory, and the program from the user. Receiving the identifier and storing the program provision data indicating that the program corresponding to the program identifier is provided in association with the identifier of the user in the program provision data storage means; and re-providing the program from the user When the program providing data indicating that the program is provided is stored in the program providing data storage means in association with the user identifier when the request is received, the program re-providing program is re-provided. Providing step; Characterized in that it contains.

  The program according to the present invention is a program identifier generating means for generating a program identifier provided to a user together with the semiconductor memory, corresponding to the program stored in the rewritable semiconductor memory, and accepting the program identifier from the user. Means for storing program provision data indicating that the program corresponding to the program identifier is provided in association with the identifier of the user in the program provision data storage means, and accepting a request for re-provision of the program from the user When the program providing data indicating that the program has been provided is stored in the program providing data storage means in association with the user identifier, a program re-providing means for re-providing the program, Computer Characterized in that to ability.

  According to the present invention, a program identifier provided to a user is received together with a rewritable semiconductor memory in which a program is stored, and the program identifier is stored in association with the user identifier so that the program identifier is stored in the rewritable semiconductor memory. It is managed to which user the program is provided. Therefore, when receiving a request for re-provision of a program, it can be easily determined whether or not the program should be provided to the requesting user. In this way, the user can easily reacquire the program stored in the rewritable information storage medium and provided to the user.

  In one aspect of the present invention, the rewritable semiconductor memory is a USB memory.

  In one aspect of the present invention, the rewritable semiconductor memory is provided together with a print medium on which the program identifier is printed and provided to the user.

  In one aspect of the present invention, the program re-providing means transmits the program via a network.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  As illustrated in the network configuration diagram of FIG. 1, the information processing system 1 in this embodiment includes a product management server 2 and a user terminal (client) 3. The product management server 2 and the client 3 are connected to a network 4 such as the Internet, so that the product management server 2 and the client 3 can communicate with each other.

  As illustrated in FIG. 1, the product management server 2 includes, for example, a control unit 20, a storage unit 21, a communication unit 22, a user interface (UI) unit 23, an input / output unit 24, and a print output unit 25. Server. The control unit 20, storage unit 21, communication unit 22, UI unit 23, input / output unit 24, and print output unit 25 are connected via a bus 26. The client 3 is, for example, a personal computer, and includes a control unit 30, a storage unit 31, a communication unit 32, a user interface (UI) unit 33, and an input / output unit 34. The control unit 30, the storage unit 31, the communication unit 32, the UI unit 33, and the input / output unit 34 are connected via a bus 36.

  The control unit 20 of the product management server 2 and the control unit 30 of the client 3 are program control devices such as a CPU, for example. The control unit 20 of the product management server 2 and the control unit 30 of the client 3 operate according to a program installed on the product management server 2 and a program installed on the client 3, respectively.

  The storage unit 21 of the product management server 2 and the storage unit 31 of the client 3 are, for example, a storage element such as a RAM or a hard disk. The storage unit 21 of the product management server 2 and the storage unit 31 of the client 3 store programs executed by the control unit 20 of the product management server 2 and the control unit 30 of the client 3, respectively. The storage unit 21 of the product management server 2 and the storage unit 31 of the client 3 also operate as work memories of the control unit 20 of the product management server 2 and the control unit 30 of the client 3, respectively.

  The communication unit 22 of the product management server 2 and the communication unit 32 of the client 3 are, for example, network interfaces and the like according to instructions input from the control unit 20 of the product management server 2 and the control unit 30 of the client 3, respectively. 4, information is transmitted between the product management server 2 and the client 3. The communication unit 22 of the product management server 2 and the communication unit 32 of the client 3 output information received via the network 4 to the control unit 20 of the product management server 2 and the control unit 30 of the client 3, respectively. To do.

  The UI unit 23 of the product management server 2 and the UI unit 33 of the client 3 are a display, a microphone, a speaker, a button, and the like. The contents of operations performed by the user and the voice input by the user are respectively The data is output to the control unit 20 of the management server 2 and the control unit 30 of the client 3. In addition, the UI unit 23 of the product management server 2 and the UI unit 33 of the client 3 display and output information according to instructions input from the control unit 20 of the product management server 2 and the control unit 30 of the client 3, respectively. To do.

  The input / output unit 24 of the product management server 2 and the input / output unit 34 of the client 3 are each a USB interface, for example, and a rewritable information storage medium (such as a USB memory) to be inserted, and the product management server 2 and the client 3 input / output data.

  The print output unit 25 of the product management server 2 is, for example, a printer, and prints and outputs an image generated by the control unit 20 of the product management server 2 on a print medium such as a paper medium.

  Here, processing performed in the information processing system 1 according to the present embodiment will be described. The processing shown below is realized by executing a program installed in the product management server 2 or the client 3 that is a computer by the control unit 20 such as a CPU included in the product management server 2 or the client 3. The program is supplied to the product management server 2 and the client 3 via a computer-readable information transmission medium such as a CD-ROM or DVD-ROM, or via a communication network such as the Internet.

[Program identifier generation processing]
First, an example of a flow of processing for generating a program identifier performed in the product management server 2 will be described. In this embodiment, a product serial number is generated as a program identifier, but the program identifier is not limited to a number, and may be a character string or a symbol string.

  In the present embodiment, product management data 40 illustrated in FIG. 2A is stored in advance in the storage unit 21 of the product management server 2. In the present embodiment, the storage unit 21 of the product management server 2 also stores account data 42 illustrated in FIG. 2B and program provision data 44 illustrated in FIG. Details of the account data 42 and the program provision data 44 will be described later.

  The product management data 40 includes, for example, a product ID 46, product name data 48, version data 50, and program data 52, as illustrated in FIG. The product ID 46 is an identifier of a product (in this embodiment, for example, a program such as an application program). The product name data 48 indicates the name of the product. The version data 50 indicates, for example, a version number indicating the current latest version of this product. The program data 52 is a program (for example, a program such as an application program) corresponding to the product management data 40, for example. Specifically, for example, the program data 52 is a product (program) indicated by the product management data 40 of the version indicated by the version data 50.

  First, the control unit 20 of the product management server 2 acquires the product ID 46 corresponding to the program for which the product serial number is generated from the storage unit 21 of the product management server 2. Then, the control unit 20 of the product management server 2 generates a product serial number based on the acquired product ID 46. In the present embodiment, the product serial number corresponds to the product ID 46 that is the basis for generating the product serial number, and the control unit 20 of the product management server 2 determines the product serial number based on the generated product serial number. It is possible to specify the product ID 46 that is the basis for generating the product serial number. Specifically, for example, by storing data that associates a product ID 46 with a program identifier such as a product serial number in the storage unit 21 of the product management server 2, the product serial number is generated based on the product serial number. It is possible to specify the product ID 46 that is the basis of the. The control unit 20 of the product management server 2 may generate a product serial number including a character string (numerical string) corresponding to the product ID 46. Further, the control unit 20 of the product management server 2 may generate a product serial number by compressing data corresponding to a program using a known lossless compression algorithm, for example.

  Then, the control unit 20 of the product management server 2 instructs the print output unit 25 of the product management server 2 to print out an image including the generated product serial number. Through the above-described processing, the print medium (in this embodiment, for example, registration sheet) on which the product serial number is printed is output from the print output unit 25 of the product management server 2. In this way, in the present embodiment, a registration sheet on which the product serial number is printed is generated.

  In the present embodiment, a package containing a registration form generated by the above-described processing and a USB memory storing a program corresponding to the product ID 46 on which the product serial number is generated is included in the user package. Provided to.

  In the USB memory provided to the user, the storage area in which the program is stored may not be rewritable. Further, the rewritable / non-rewritable storage area in which the program is stored may be switched by a switch provided in the USB memory. Further, when the USB memory is inserted into the input / output unit 34 of the client 3, the user may not be able to refer to the storage area in which the program is stored. At this time, if the USB memory is formatted, the user may be able to access the storage area in which the program is stored. The program may be compressed and encrypted and stored in the USB memory.

  Note that the control unit 20 of the product management server 2 may generate a program identifier based on the program itself provided to the user.

[Installation process]
Next, an example of a flow of installation processing of a program (for example, an application program) stored in a rewritable semiconductor memory (in this embodiment, a USB memory) provided to the user performed by the client 3 is as follows. This will be described with reference to the flowchart illustrated in FIG. Here, in the present embodiment, a setting file and a program are stored in the USB memory provided to the user.

  When the user inserts the provided USB memory into the input / output unit 34 (in this embodiment, the USB interface) of the client 3 in which the OS is activated in advance, the control unit 30 of the client 3 is stored in the USB memory. The setting file is acquired (S101). This setting file indicates the contents for instructing the installation of the program stored in the USB memory.

  Then, based on the contents of the setting file, the control unit 30 of the client 3 displays and outputs an initial operation selection screen 54 as shown in FIG. 4 on the UI unit 33 such as a display provided in the client 3 (S102). ). The initial operation selection screen 54 illustrated in FIG. 4 includes at least an installer activation button 56 and a folder reference button 58. When the user presses the installer activation button 56, the control unit 30 of the client 3 receives a signal indicating an installer activation instruction, acquires an installer program included in the program stored in the USB memory, and obtains an installer program. Is executed (S103). When the user presses the folder reference button 58, the control unit 30 of the client 3 displays and outputs a list of data stored in the USB memory on the UI unit 33 such as a display provided in the client 3.

  Then, the control unit 30 of the client 3 displays and outputs a processing selection screen 60 as shown in FIG. 5 on the UI unit 33 such as a display provided in the client 3 (S104). As illustrated in FIG. 5, the process selection screen 60 includes an install button 62, a program / setting shift button 64, an uninstall button 66, and an update button 68.

  When the user presses the install button 62, the control unit 30 of the client 3 receives a signal indicating an installation start instruction, and a UI unit such as a display provided in the client 3 with the product serial number input screen 70 illustrated in FIG. Display output to 33 (S105). As illustrated in FIG. 7, the product serial number input screen 70 includes a product serial number input field 72 and an OK button 74.

  Here, when the user inputs the product serial number printed on the registration sheet included in the package together with the USB memory into the product serial number input field 72 and presses the OK button 74, the control of the client 3 is performed. The unit 30 acquires the product serial number (S106). In this embodiment, the control unit 30 of the client 3 confirms whether or not the acquired product serial number satisfies a predetermined condition (S107).

  If it is determined that the predetermined condition is not satisfied (S107: N), the control unit 30 of the client 3 again displays the product serial number input screen 70 on the UI unit 33 such as a display provided in the client 3. The display is output (S105). If it is determined that the predetermined condition is satisfied (S107: Y), the control unit 30 of the client 3 installs the program stored in the USB memory (for example, the data stored in the USB memory). , Copy processing to the storage unit 31 of the client 3) is executed (S108).

  In this way, the program stored in the USB memory is installed in the client 3.

  Note that the control unit 30 of the client 3 may execute an authentication process based on a USB memory inserted in the input / output unit 34 of the client 3 as a pre-process for executing the above-described installation process. Specifically, for example, when the control unit 30 of the client 3 transmits an authentication token stored in the USB memory to a license server (not shown) connected via the network 4, the license server authenticates. Based on the token, installability data indicating whether or not to allow the client 3 to execute the installation process is generated and transmitted to the client 3. The license server outputs a screen for prompting the user to input the user ID 76 to the UI unit 33 such as a display provided in the client 3, receives the input of the user ID input by the user, and receives the received authentication token and the user ID 76. The installability data may be generated based on the above. Then, the control unit 30 of the client 3 may acquire the installability data and determine whether to execute the installation process. Thus, a USB memory may be used as an authentication key.

  In addition, license information (for example, a license counter in which a predetermined numerical value is set) is stored in the USB memory, and the control unit 30 of the client 3 acquires the license information when the above-described installation process is executed. It may be updated (for example, the value of the license counter is decreased by 1). Further, when the program stored in the USB memory is copied to an external storage device (for example, the storage unit 31 such as a hard disk provided in the client 3), the control unit 30 of the client 3 updates the license information (for example, The value of the license counter may be decreased by 1.

[Program provision registration process]
Next, an example of a processing flow in which the information processing system 1 according to the present embodiment registers that a program has been provided to a user will be described with reference to a flowchart illustrated in FIG. As described above, the account data 42 illustrated in FIG. 2B is stored in the storage unit 21 of the product management server 2 in advance. In this embodiment, the account data 42 includes, for example, a user ID 76, password data 78, user name data 80, address data 82, and the like. For example, the control unit 20 of the product management server 2 acquires the account data 42 transmitted from the client 3 and outputs the acquired account data 42 to the storage unit 21 of the product management server 2. The user ID 76 is a user identifier. The password data 78 is a password set for this user. User name data 80 indicates the name of the user. The address data 82 indicates the user's address.

  First, the control unit 30 of the client 3 transmits a data output request indicating a login screen (not shown) to the product management server 2. Then, the control unit 20 of the product management server 2 accepts this output request (S201). Then, the control unit 20 of the product management server 2 displays and outputs a login screen via the Web browser on the UI unit 33 such as a display provided in the client 3 (S202).

  The login screen includes a user ID input field, a password input field, and a login button. Here, when a user whose account data 42 is already stored in the storage unit 21 of the product management server 2 inputs the user ID 76 in the user ID input field and the password in the password input field and presses the login button, the user A combination of the ID 76 and the password is transmitted to the product management server 2. And the control part 20 of the product management server 2 receives the combination of user ID76 and a password (S203).

  Then, the control unit 20 of the product management server 2 determines whether the login is successful based on the combination of the received user ID 76 and the password and the comparison result with the account data 42 stored in the storage unit 21 of the product management server 2. Is confirmed (S204). When it is determined that the login has failed (S204: N), the control unit 20 of the product management server 2 again displays a login screen on the UI unit 33 such as a display provided in the client 3 via the Web browser. The display is output (S202). On the other hand, when it is determined that the login is successful (S204: Y), the control unit 20 of the product management server 2 displays the product serial number input screen 70 similar to the screen illustrated in FIG. A display is output to the UI unit 33 such as a display provided via a Web browser (S205). Here, when the user inputs the product serial number printed on the print medium in the product serial number input field 72 and presses the OK button 74, the product serial number is transmitted to the product management server 2. Then, the control unit 20 of the product management server 2 receives the product serial number (S206).

  Then, the control unit 20 of the product management server 2 identifies the product ID 46 corresponding to the program provided to the user based on the product serial number (S207). As described above, in the present embodiment, the control unit 20 of the product management server 2 can identify the product ID 46 that is the basis for generating the product serial number based on the product serial number. Yes.

  Then, the control unit 20 of the product management server 2 stores the program provision data 44 including the user ID 76 of the logged-in user and the product ID 46 corresponding to the received product serial number, as illustrated in FIG. Generate and output to the storage unit 21 of the product management server 2 (S208).

  In this way, the program provision data 44 in which the product ID 46 corresponding to the program provided to the user and the user ID 76 corresponding to the provided user are associated is stored in the storage unit 21 of the product management server 2. .

[Reinstallation process]
Next, an example of a flow of processing in which the client 3 according to the present embodiment downloads the program from the product management server 2 and reinstalls it after the program provided to the user is once installed in the client 3 is shown in FIG. 8 will be described with reference to the flowchart illustrated in FIG. In this processing example, a reinstallation support program is installed in the client 3 in advance. An icon indicating a reinstallation support program is displayed on the UI unit 33 such as a display provided in the client 3. Note that the reinstallation support program is supplied to the client 3 via a computer-readable information transmission medium such as a CD-ROM or DVD-ROM, or via a communication network such as the Internet. A reinstallation support program may be stored in a USB memory provided to the user.

  In this processing example, a USB memory provided to the user is inserted into the input / output unit 34 of the client 3.

  First, when the user clicks on an icon indicating a reinstallation support program displayed on the UI unit 33 of the client 3, the control unit 30 of the client 3 sends an output request for a login screen (not shown) to the product management server 2. (S301). Then, the control unit 20 of the product management server 2 receives the output request, and displays and outputs the requested login screen on the UI unit 33 such as a display provided in the client 3 (S302). When the user inputs the user ID 76 and the password and presses the login button, the control unit 30 of the client 3 transmits a combination of the user ID 76 and the password to the product management server 2. Then, the control unit 20 of the product management server 2 receives the combination of the user ID 76 and the password (S303). Then, when the control unit 20 of the product management server 2 executes the same login process as described above (S304), and the login fails (S304: N), the display or the like provided in the client 3 with the same screen as the login screen again. Display on the UI unit 33 (S302). When the login is successful (S304: Y), the control unit 20 of the product management server 2 performs the reinstallation illustrated in FIG. 9 based on the above-described program provision data 44 stored in the storage unit 21 of the product management server 2. The support screen 84 is generated and displayed on the UI unit 33 such as a display provided in the client 3 (S305). The reinstallation support screen 84 includes, for example, a radio button 86, a reinstallation target program display unit 88, and a download / install button 90. In the reinstallation target program display unit 88 of the reinstallation support screen 84, a list of program names permitted to be downloaded to the client 3 is displayed in the reinstallation target program display unit 88.

  When the user clicks the radio button 86 arranged on the left side where the name of the program to be downloaded and installed is displayed and presses the download / install button 90, the control unit 30 of the client 3 performs product management. A transmission request for a program to be installed is transmitted to the server 2. And the control part 20 of the product management server 2 receives a transmission request (S306). Then, the control unit 20 of the product management server 2 transmits the requested program to the client 3 (S307). Then, the control unit 30 of the client 3 outputs the program transmitted from the product management server 2 to the USB memory inserted in the client 3 via the input / output unit 34 of the client 3 (S308). And the control part 30 of the client 3 performs the installation process of this program (S309).

  Even if the program stored in the USB memory is deleted by the above processing, the user can download and install the program. In the above processing example, the USB memory inserted in the input / output unit 34 of the client 3 may be different from the USB memory in which the program provided to the user is stored.

  In the re-installation process described above, the latest version of the program corresponding to the program installed by the user may be downloaded and installed.

  Further, in the client 3 different from the client 3 in which the program stored in the USB memory provided to the user is installed, the same process as the above-described reinstallation process is executed, and the program is installed in the client 3 You may do it.

[Program / setting migration process]
Next, processing at the time of migration of programs and settings will be described. In this processing example, processing similar to the processing illustrated in the above-described S101 to S103 is executed in advance, and the processing selection screen 60 is displayed and output on the UI unit 33 such as a display provided in the client 3.

  When the user presses the program / setting shift button 64, the control unit 30 of the client 3 is set after the program stored in the USB memory stored in the storage unit 31 of the client 3 and this program is installed. The setting data indicating the set contents is output to the input / output unit 34 (for example, USB interface) USB memory of the client 3. When the user performs the above-described installation operation on a different client 3, the setting data output to the USB memory after the program is installed on the client 3 in the same flow as the processing described in the above-described installation operation. The setting based on is reflected.

  In this way, the user can easily migrate the program and settings made after the program is installed to another client 3. It should be noted that the restore process may be executed in the case where the data stored in the storage unit 31 of the client 3 is mistakenly erased by the same process flow as described above.

  In the program / setting transfer processing described above, for example, setting data related to confidential information such as personal information may be output to the input / output unit 34 (for example, USB interface) USB memory of the client 3.

[Uninstall process]
When the process selection screen 60 is displayed on the UI unit 33 such as a display provided in the client 3 and the user presses the uninstall button 66, the control unit 30 of the client 3 stores in the storage unit 31 of the client 3. Executes the process of uninstalling the installed program. In this way, the program installed on the client 3 is uninstalled.

[Update process]
When the process selection screen 60 is displayed on the UI unit 33 such as a display provided in the client 3 and the user presses the update button 68, the control unit 30 of the client 3 causes the storage unit 21 of the product management server 2. The product management data 40 corresponding to the program to be installed is acquired. If the version indicated by the version data 50 included in the product management data 40 is newer than the version of the installed program stored in the USB memory, the control unit 30 of the client 3 The program data 52 is acquired from the product management server 2 and the program stored in the USB memory is updated. In this way, the program installed on the client 3 is updated.

  During the installation process described above, the same process as the update process described above is executed in advance, and a newer version of the program stored in the USB memory is stored in the storage unit 21 of the product management server 2. In this case, the program stored in the USB memory may be updated and then installed.

  The present invention is not limited to the above embodiment.

  For example, the program purchased by the user need not be stored in the USB memory. The program purchased by the user may be stored in a rewritable semiconductor memory different from the USB memory, for example.

  Further, the product management server 2 may be configured by a single casing or may be configured by a plurality of casings.

  Further, the division of roles between the product management server 2 and the client 3 and the implementation method of the program installed in the product management server 2 are not limited to the above embodiment. For example, the program installed in the product management server 2 may be a client / server application or the like instead of a Web application.

  In the above embodiment, the screen generated by the product management server 2 is output to the client 3. However, the screen may be output to the product management server 2 itself.

  Further, the product management server 2 receives orders for a plurality of programs from the user, and outputs the plurality of programs that have received the orders to a USB memory inserted in the input / output unit 24 of the product management server 2. Also good. Then, this USB memory may be provided to the user.

  Further, registry information or the like may be included in the program provided to the user. Then, the control unit 30 of the client 3 acquires the program stored in the USB memory via the input / output unit 34 of the client 3 without performing the program installation process, and starts the program. Good.

It is a figure which shows an example of the network structure of the information processing system which concerns on one Embodiment of this invention. It is a figure which shows an example of the data structure of product management data, account data, and program provision data. It is a flowchart which shows an example of the flow of the process performed with the information processing system which concerns on this embodiment. It is a figure which shows an example of an initial stage operation selection screen. It is a figure which shows an example of a process selection screen. It is a figure which shows an example of a product serial number input screen. It is a flowchart which shows an example of the flow of the process performed with the information processing system which concerns on this embodiment. It is a flowchart which shows an example of the flow of the process performed with the information processing system which concerns on this embodiment. It is a figure which shows an example of a reinstallation assistance screen.

Explanation of symbols

  1 Information processing system 2 Product management server 3 User terminal (client) 4 Network 20 Control unit 21 Storage unit 22 Communication unit 23 User interface (UI) unit 24 Input / output unit 25 Print output unit , 26 bus, 30 control unit, 31 storage unit, 32 communication unit, 33 user interface (UI) unit, 34 input / output unit, 36 bus, 40 product management data, 42 account data, 44 program provision data, 46 product ID, 48 product name data, 50 version data, 52 program data, 54 initial operation selection screen, 56 installer start button, 58 folder reference button, 60 process selection screen, 62 install button, 64 program / setting transfer button, 66 uninstall button, 68 Update Button, 70 product serial number input screen, 72 product serial number input field, 74 OK button, 76 user ID, 78 password data, 80 user name data, 82 address data, 84 reinstallation support screen, 86 radio button, 88 reinstall Target program display, 90 download / install buttons.

Claims (6)

Program identifier generation means for generating a program identifier provided to a user together with the semiconductor memory, corresponding to a program stored in the rewritable semiconductor memory;
Program providing data storage means for receiving the program identifier from the user and storing program providing data indicating that the program corresponding to the program identifier is provided in association with the identifier of the user;
When receiving a request for re-provision of the program from the user, when the program provision data indicating that the program is provided is stored in the program provision data storage means in association with the identifier of the user, Program re-providing means for re-providing the program;
An information processing system comprising: The rewritable semiconductor memory is a USB memory;
The information processing system according to claim 1. The rewritable semiconductor memory is provided together with a print medium on which the program identifier is printed and provided to the user.
The information processing system according to claim 1 or 2. The program re-providing means transmits the program via a network;
The information processing system according to any one of claims 1 to 3, wherein: A program identifier generation step for generating a program identifier provided to a user together with the semiconductor memory, corresponding to a program stored in the rewritable semiconductor memory;
Receiving the program identifier from the user and storing the program provision data indicating that the program corresponding to the program identifier is provided in the program provision data storage means in association with the identifier of the user;
When receiving a request for re-provision of the program from the user, when the program provision data indicating that the program is provided is stored in the program provision data storage means in association with the identifier of the user, A program re-providing step for re-providing the program;
An information processing method comprising: Program identifier generating means for generating a program identifier provided to a user together with the semiconductor memory, corresponding to a program stored in the rewritable semiconductor memory;
Means for receiving the program identifier from the user and storing the program provision data indicating that the program corresponding to the program identifier is provided in the program provision data storage means in association with the identifier of the user;
When receiving a request for re-provision of the program from the user, when the program provision data indicating that the program is provided is stored in the program provision data storage means in association with the identifier of the user, Program re-providing means for re-providing the program,
A program characterized by causing a computer to function.

Images