JP2009104433A - Update program distribution system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an update program distribution system capable of preserving the interests of a vender providing products by distributing an update program only to users under contract with the vender without storing customer information in a database and by preventing the update program from being illegally installed in a plurality of devices. <P>SOLUTION: A server 11 confirms whether or not a serial number transmitted from client software 14 exists in a license information management database 19. When the serial number exists, whether or not the number of times used exceeds the maximum number of times used is judged. When the number of times used does not exceed the maximum number of times used, information indicating success of registration is transmitted to the client software 14. In this case, the client software 14 stores the serial number in a serial number management function. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an update program distribution system for distributing an update program for a software package product or the like to a license holder of the software package product or the like.

  Currently, various software package products used in personal computers are sold. And many update programs based on version upgrade etc. are provided for each of those products. Since an update program may have a dependency, in order to apply a certain update program, it is necessary to apply another update program in advance. For this reason, distributing and applying an update program having such dependency relationship places a heavy burden on the distributor of the software package product and the end user.

  Therefore, the update program and its dependency relationship information are stored in advance in the database of the server and released on the Internet. A service that enables the end user to distribute the latest update program without being aware of the order of application has become widespread by the system grasping the application status of the update program of the end user.

The prior art of such an update program distribution system will be briefly described.
As shown in FIG. 16, the update program distribution system in the prior art includes a server 41 and a client terminal 42. The server 41 and the client terminal 42 are communicably connected to the Internet 43 as a communication network, and a client server system is constructed with the server 41 as a server computer and the client terminal 42 as a client computer.

  The server 41 is provided with a magnetic disk 46 in which an update program database 44 and a customer contract information database 45 are registered. In the update program database 44, an update program 47, an update program detection condition 48, and information 49 related to the update program dependency are registered. Further, customer information 50 and contract information 51 are registered in the customer contract information database 45. The server 41 has a function of transmitting to the client terminal 42 an update program 47, an update program detection condition 48, and information 49 regarding the update program dependency.

Further, client software 52 which is a software package product is installed in the client terminal 42.
The operation of the conventional update program distribution system configured as described above is as follows.
First, an update program request request applicable from the client software 52 executed on the client terminal 42 is transmitted to the server 41 via the Internet 43.

Next, the server 41 specifies the customer information 50 by referring to the customer contract information database 45 using the key data of the customer information 50 transmitted from the client terminal 42. Then, the server 41 specifies the update program 47 that can be downloaded in the contract from the contract information 51 in the customer contract information database 45 associated with the customer information 50.
Next, the server 41 returns an update program detection condition 48 regarding the update program 47 that can be downloaded under contract and information 49 regarding the dependency relationship of the update program to the client terminal 42.

The client software 52 in the client terminal 42 determines the update program 47 to be applied using the update program detection condition 48 and information 49 regarding the update program dependency. Based on the determination result, the client terminal 42 requests the server 41 for the necessary update program 47 and, after downloading the update program 47, applies the update program 47.
Thus, the end user can apply the update program 47 to the client software 52 without being aware of the dependency relationship of the update program 47.
In addition, there exists patent document 1 as a well-known technical document regarding this invention.
Patent Publication 2005-222453

  By the way, in order to determine an update program that can be downloaded based on a contract, it is necessary to store customer information in a customer contract database and determine whether download is possible based on the contents of the contract.

  Further, when the end user makes a contract for a plurality of products, the contract information of the additionally purchased product must be added to the customer contract database. At this time, in order to add contract information, it is necessary to specify the contracted end user. However, many software vendors sell software via a sales company, and it is not easy to grasp end user information. Therefore, even if an end user purchases an additional product, the software vendor does not know which end user should be given permission to download the additional product.

Even if customer information can be obtained, there is a problem in terms of management costs. Furthermore, customer information must be strictly managed so that personal information is not leaked due to the enforcement of the Personal Information Protection Law. For this reason, security requirements for a system for managing personal information are very high, and a major problem arises in that an update program distribution service provider increases operational costs.
An object of the present invention is to provide a mechanism for distributing an update program only to contracted users without storing customer information on a database.

On the other hand, in general, a product to which an update program is applied is permitted to be installed only on a specified number of client terminals, and installation on a plurality of client terminals exceeding the specified number is a license violation. If an end user illegally installs multiple products subject to the update program and installs the client software on multiple client terminals, the update program is also applied to the client terminal that is violating the license. , Which will hinder the profits of vendors who provide products for which updates are applicable.
The second object of the present invention is to protect the profits of vendors who provide products by preventing unauthorized installation of update programs on a plurality of machines.

  In order to achieve the above object, an update program distribution system of the present invention is installed with a server including storage means for storing an update program database and a license information management database, and client software to which the update program is applied. An update program distribution system that is communicably connected to a client terminal via a communication network, wherein the update program database includes an update program installed in the client terminal and an update program for detecting the update program Update program detection conditions and update program dependency data, which is data recording dependency relationships among a plurality of update programs, are stored, and the license information management database identifies the client software. Serial number information for managing serial numbers, ticket number information for managing downloadable update programs and ticket numbers having a downloadable period, and mapping for managing the connection between the serial number information and the ticket number information Information is stored, the server updates the update program database and the license information management database, and the license information management database downloads an update program that can be downloaded in response to a request from the client software. And a search processing unit that searches from the update program database, and a list of update programs that can be downloaded to the client software, and data sent from the client terminal Characterized in that it comprises a receiving section for receiving.

The update program distribution system of the present invention has the following effects.
-Update programs can be distributed only to contracted users without storing customer information on the database.
-By preventing unauthorized installation of update programs on multiple devices, it is possible to protect the profits of vendors who provide products.

Hereinafter, an embodiment of an update program distribution system to which the present invention is applied will be described.
As shown in FIG. 1, the update program distribution system includes a server 11 and a client terminal 12. The server 11 and the client terminal 12 are communicably connected to the Internet 13 as a communication network, and a client server system is constructed with the server 11 as a server computer and the client terminal 12 as a client computer.

Client software 14 that is a software package product is installed in the client terminal 12.
The server 11 includes a database update unit 15, a search processing unit 16, and a transmission / reception unit 17, and a magnetic disk 20 as a storage unit that stores an update program database 18 and a license information management database 19. .
The database update unit 15 has a function of updating the update program database 18 and the license information management database 19.

The search processing unit 16 has a function of searching the license information management database 19 and the update program database 18 for an update program 21 that can be downloaded in response to a request from the client software 14.
The transmission / reception unit 17 receives various data transmitted from the client terminal 12 and transmits list data of downloadable update programs 21 to the client terminal 12.

In the update program database 18, an update program 21, an update program detection condition 22, and update program dependency relationship data 23 are registered.
The update program 21 is installed in the client terminal 12. The update program detection condition 22 has a function of detecting the update program 21. The update program dependency relationship data 23 is data in which dependency relationships between a plurality of update programs 21 are recorded.

In the license information management database 19, serial number information 24, ticket number information 25, and mapping information 26 are registered.
The serial number information 24 is information for managing a serial number for identifying the client software 14. The ticket number information 25 is information for managing a ticket number including information relating to a downloadable update program 21 and a downloadable period. The mapping information 26 is information for managing the connection between the serial number and the ticket number.

Next, an outline of the client software 14 will be described.
As shown in FIG. 2, the client software 14 has a user interface function 27, a transmission / reception function 28, and a data processing function 29. The user interface function 27 has a function of receiving input from the user for managing the ticket number and applying the update program 21. The transmission / reception function 28 has a function of transmitting / receiving data to / from the server 11. The data processing function 29 has functions for managing serial numbers and ticket numbers, determining the applicable update program 21, and applying the update program 21.

Further, the data processing function 29 includes a serial number management function 30, an applicable update program determination function 31, an update program reception function 32, and an update program application function 33.
The serial number management function 30 records the serial number input when the client software 14 is installed in the client terminal 12 and transmits the serial number recorded when communicating to the server 11 from the transmission / reception unit 17.

The applicable update program determination function 31 receives the update program detection condition 22 and the update program dependency relationship data 23 from the server 11, detects the update program 21 actually installed on the client terminal 12, and is still installed. The process which determines the update program 21 which has not been performed is performed.
The update program reception function 32 performs a process of downloading the update program 21 determined to be installable by the applicable update program determination function 31 from the server 11.
The update program application function 33 performs a process of actually installing the update program 21 downloaded by the update program reception function in the client terminal 12.

Next, the table structure of the serial number information 24 stored in the license information management database 19 will be described.
As shown in FIG. 3, the table element of the serial number information 24 stored in the license information management database 19 is composed of a serial number, the number of uses, and the maximum number of uses. The serial number is a number that is unique in the present system and is required when installing the client software 14.

Next, the table structure of the ticket number information 25 stored in the license information management database 19 will be described.
As shown in FIG. 4, the table elements of the ticket number information 25 stored in the license information management database 19 are ticket number, product name, ticket contract start date, contract end date, ticket use count, and maximum use count. It consists of The ticket number is a character string for uniquely identifying the ticket in this system.

Next, the table structure of the mapping information 26 stored in the license information management database 19 will be described.
As shown in FIG. 5, the table element of the mapping information 26 stored in the license information management database 19 is composed of a serial number and a ticket number. The serial number is a serial number stored in the serial number information. The ticket number is a ticket number stored in the ticket number information. A plurality of ticket numbers can be linked to one serial number. This is because, when an end user purchases an additional product, a single client software 14 can download update programs for a plurality of products.

Next, the table structure of the update program detection condition 22 stored in the update program database 18 will be described.
As shown in FIG. 6, the table elements of the update program detection condition 22 stored in the update program database 18 are composed of a correction program name, a product name, a detection condition, and a binary. The correction program name is a name that uniquely indicates the correction program. The product name indicates to which product the modification program name belongs. The detection condition is a condition for detecting that the correction program name is installed. Specifically, the existence of a file, the value of a registry database on the operating system, and the like are described as detection conditions.

Next, the operation of the update program distribution system configured as described above will be described.
First, the server 11 uses the database update unit 15 to create serial number information 24 and ticket number information 25 in the license information management database 19. The issued serial number information 24 is stored in the table shown in FIG. Specifically, the issued serial number is recorded in the serial number, 0 indicating that it is not used is recorded in the number of uses, and the maximum number of use of the serial number is recorded in the maximum number of uses.

The issued ticket number information 25 is stored in the table shown in FIG. Specifically, the issued ticket number is the ticket number, the name indicating the product that can be downloaded with the ticket is the product name, the contract start date is the contract start date, and the contract end date is the contract On the end date, 0 indicating no use is recorded as the number of uses, and the maximum use number of tickets is recorded as the maximum use number.
The serial number and ticket number issued here are handed over from the vendor to the end user, for example, by e-mail or mailing them in writing.

The client software 14 registers a serial number in the server 11 when installed on the client terminal 12.
In the process of registering the serial number in the server 11, as shown in FIG. 7, first, the client software 14 transmits a serial number registration request to the server 11 (step S71). Next, the server 11 executes serial number registration processing (step S72) and returns the processing result as a serial number registration result reply to the client software 14 (step S73).

Next, an outline of the serial number registration process will be described.
As shown in FIG. 8, first, the server 11 checks whether or not the serial number transmitted from the client software 14 exists in the table shown in FIG. 3 (step S81). If not, the server 11 transmits information indicating that registration has failed to the client software 14 (step S82). On the other hand, if it exists, the server 11 determines whether or not the maximum number of uses has been exceeded (step S83).

  If the maximum use count has been reached, the server 11 transmits information indicating that registration has failed to the client software 14 (step S82). If the maximum use count has not been exceeded, the maximum use count is incremented (step S84), and information indicating that the registration has been successful is transmitted to the client software 14 (step S85). When the information indicating that the registration is successful is received, the client software 14 stores the serial number in the serial number management function 30.

The client software 14 has a function of displaying a ticket management screen 34 for adding and deleting tickets shown in FIG. 9 on a display (not shown) of the client terminal 12 as one of the user interface functions 27.
Here, an outline of communication processing that occurs on the ticket management screen 34 will be described.
As shown in FIG. 10, when the ticket management screen 34 is opened by the user, the client software 14 sends a serial number held by the client software 14 to the server 11, thereby requesting a ticket list. Is performed (step S101).

  Next, the server 11 performs ticket list acquisition processing in response to a request from the client software 14 (step S102). Then, the server 11 creates a list of tickets associated with the serial number and returns a ticket list (step S103). Specifically, the server 11 acquires a list of ticket numbers associated with the serial numbers from the table shown in FIG. 5 based on the serial numbers received from the client software 14, and associates the ticket numbers with the ticket numbers from the table shown in FIG. Get the product name, contract start date, contract end date, and return the ticket list to the client software. The client software 14 displays the ticket list returned from the server 11 in the ticket list area of the ticket management screen 34.

When the end user purchases a new product, the ticket number of the corresponding product is registered from the ticket management screen 34 shown in FIG.
When the end user presses the ticket addition button, the ticket number input from the ticket management screen 34 by the ticket registration request process and the serial number of the client software 14 are transmitted to the server 11 (step S104).
The server 11 performs a ticket registration process (step S105), associates the ticket number transmitted by the client software 14 with the serial number, and returns a ticket registration result (step S106).

Here, an outline of the ticket number registration process will be described.
As shown in FIG. 11, the server 11 first searches the table shown in FIG. 4 for the ticket number transmitted from the client software 14, and determines whether the maximum number of uses has been exceeded (step S111). If the maximum use count has been reached, the server 11 transmits information indicating that registration has failed to the client software 14 (step S112).
On the other hand, if the maximum number of uses has not been exceeded, the number of uses is incremented (step S113), and the association between the serial number and the ticket number is recorded in the table shown in FIG. 5 (step S114). Finally, information indicating that the registration is successful is transmitted to the client software 14 (step S115).

Here, the description returns to the communication processing that occurs on the ticket management screen 34 shown in FIG.
When an end user moves a purchased product license to another computer, the used ticket needs to be deleted. When deleting a ticket, the end user presses a ticket deletion button from the ticket management screen 34 shown in FIG. When the ticket deletion button is pressed, a ticket deletion request is transmitted to the server 11 (step S107). Specifically, the ticket number designated to be deleted from the ticket management screen 34 and the serial number of the client software 14 are transmitted to the server 11.

In the server 11, a ticket deletion process is executed (step S108). Then, the server 11 cancels the association between the ticket number and the serial number transmitted by the client software 14, and returns a ticket deletion result reply (step S109).
Here, an outline of the ticket number deletion process will be described.
As shown in FIG. 12, first, the server 11 searches the table shown in FIG. 5 for a combination of the ticket number and serial number transmitted from the client software 14, and cancels the association by deleting the record. (Step S121).

  Next, the server 11 searches the ticket number transmitted from the client software 14 from the table shown in FIG. 4 and decrements the number of uses (step S122). Then, the server 11 returns information related to the deletion success result to the client software 14 (step S123).

Next, processing until the client software 14 requests and applies the list of update programs to the server 11 will be described.
As shown in FIG. 13, the client software 14 sends an update program list acquisition request to the server 11 (step S131). Then, the server 11 executes update program list acquisition request processing (step S132) and returns data related to the update program list to the client software 14 (step S133).

Next, the client software 14 executes update program list screen display processing and displays an update program list screen, which is a list of applicable update programs, on a display (not shown) of the client terminal 12 (step S134).
Next, the client software 14 performs an update program download request in order to download the update program selected by the end user from the update program list screen (step S135).

  In response to the request, the server 11 executes an update program download processing request (step S136). Specifically, when the client software 14 transmits a list of non-installed update programs selected by the end user from the update program list screen, the server 11 acquires binary data of the update program from the table shown in FIG. To the client software 14.

  The server 11 returns an update program to the client software 14 as a result of the download processing request (step S137). The client software 14 executes the downloaded software on the client terminal 12 to perform update program application processing (step S138). Specifically, the client software 14 executes the update program downloaded from the server 11 on the client terminal 12 to install the update program.

  Here, the details of the update program list acquisition request processing in step S132 of FIG. 13 will be described. As shown in FIG. 14, first, a set of the ticket number and serial number sent from the client software 14 is searched from the table shown in FIG. 5 (step S141). Next, the product name associated with the ticket number is searched from the table shown in FIG. 4 (step S142), and the correction program name and detection condition of the correction program with the matching product name are acquired from the table shown in FIG. . Then, the list is returned to the client software 14 (step S143).

Next, details of the update program list screen display process in step S134 of FIG. 13 will be described.
As shown in FIG. 15, first, the client software 14 checks the detection conditions from the list of correction programs for the list obtained from the server 11. Then, it is determined whether or not the correction program on the list is actually installed on the client, and a list of update programs that are not installed is created (step S151). Then, a list of update programs that are not installed is displayed on the update program list screen (step S152).

As described above, according to the update program distribution system of the present embodiment, the following effects are obtained.
-Update programs can be distributed only to contracted users without storing customer information on the database.
-By preventing unauthorized installation of update programs on multiple devices, it is possible to protect the profits of vendors who provide products.

The above embodiment may be modified as follows.
Although the Internet 13 has been described as an example of a communication network, a network such as a LAN (Local Area Network) or a WAN (Wide Area Network) may be used.
Although a system in which one client terminal 12 is connected to the Internet 13 has been described as an example, a plurality of client terminals 12 may be connected to the Internet 13.

1 is a system configuration diagram showing an embodiment of the present invention. The block diagram of client software. The block diagram of the serial number information stored in the database. The block diagram of the ticket number information stored in the database. The block diagram of the mapping information stored in the database. The block diagram of the update program detection conditions stored in the database. The sequence diagram in serial number registration. The flowchart which shows the outline | summary of a serial number registration process. The block diagram of a ticket management screen. The sequence diagram in a ticket addition and deletion process. The flowchart which shows the outline | summary of a ticket number registration process. The flowchart which shows the outline | summary of a ticket number deletion process. The sequence diagram in an update program acquisition and application process. The flowchart which shows the outline | summary of an update program list acquisition request process. The flowchart which shows the outline | summary of an update program list screen display process. The system block diagram which shows the conventional update program delivery system.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 11 ... Server, 12 ... Client terminal, 13 ... Internet as communication network, 14 ... Client software, 15 ... Database update part, 16 ... Search processing part, 17 ... Transmission / reception part, 18 ... Update program database, 19 ... License information management Database: 20 ... Magnetic disk as storage means, 21 ... Update program, 22 ... Update program detection condition, 23 ... Update program dependency data, 24 ... Serial number information, 25 ... Ticket number information, 26 ... Mapping information.

Claims (1)

A server comprising storage means for storing an update program database and a license information management database;
An update program distribution system in which a client terminal to which client software to which an update program is applied is installed is connected to be communicable via a communication network,
The update program database includes update programs installed in the client terminal, update program detection conditions for detecting update programs, and update program dependency relationships that are data recording dependency relationships among a plurality of update programs. Data is stored,
The license information management database includes serial number information for managing a serial number for identifying the client software, ticket number information for managing a downloadable update program and a ticket number having a downloadable period, Mapping information for managing the connection between the serial number information and the ticket number information is stored;
The server
A database update unit for updating the update program database and the license information management database;
A search processing unit that searches the license information management database and the update program database for an update program that can be downloaded in response to a request from the client software;
An update program distribution system comprising: a transmission / reception unit that transmits a list of downloadable update programs to the client software and receives data transmitted from the client terminal.

Images