JP2010072923A - License authentication system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable a license for an application in a client terminal to be authenticated on another mobile terminal if a mobile terminal is lost or when a client PC is newly purchased. <P>SOLUTION: In this license authentication system, another mobile terminal taking the place of a mobile terminal whose identifier is registered in a server has a means for obtaining a recovery password for an application from a user of the application, obtaining an identifier of the user of the application from the client terminal, and sending the identifier together with the identifier of the other mobile terminal to the server. The server has a means for comparing the recovery password received from the other mobile terminal with a previously registered recovery password and, if they are identical, replacing the identifier of the mobile terminal corresponding to the identifier of the application user in a second correspondence table with the identifier received from the other mobile terminal. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a license authentication system that limits the use of an application of a client terminal to only users who have been given a use right in advance.

Conventionally, the right to use an application installed on a client PC (client terminal) is issued by the license granter by issuing a serial number for each user, and entering the serial number issued at the time of application installation or application startup. Has been granted by being authenticated. At this time, the application incorporates logic for confirming that the input serial number has been issued by the license granter, thereby preventing unauthorized use of the application.
In this case, the granting of the right to use the serial number has the problem that the same serial number is reused and a plurality of applications are used, or an unauthorized person steals the serial number and uses it.

Therefore, a method for confirming the usage status of an application using the Internet is used. This is based on the premise that the user's client PC and the licensee's server can communicate via the Internet. In this method, an application that can be used with a serial number periodically transmits user information, a serial number, and usage environment information (OS, IP address, device configuration information, etc.) to the server. The server manages the number of usage rights for each user. By checking the consistency with usage information sent periodically, it is possible to detect unauthorized use of the application and stop using it. .
However, with this method, unauthorized users cannot be stopped unless they are found by a legitimate user and take appropriate measures.
Therefore, as shown in Patent Document 1 below, a usage right and usage status confirmation method using a mobile terminal such as a mobile phone has been proposed. In the method proposed in Patent Document 1, the right to use can be given by connecting the user's portable terminal like a repeater to a server in order to identify a legitimate user. Yes.

JP 2006-309720 A

  However, the method proposed in Patent Document 1 has a problem that the license cannot be acquired or granted when the hardware of the mobile terminal is destroyed or lost due to misplacement or the like. . In addition, there is a problem that the application cannot be migrated when the client PC is replaced with a new one.

  An object of the present invention is to provide a license authentication system capable of authenticating an application license of a client terminal when a mobile terminal is lost or a client PC is newly purchased.

In order to achieve the above object, a license authentication system according to the present invention includes a first correspondence table between a right to use an application of a client terminal and an identifier of the user of the application, and a mobile phone held by the user of the application. A second correspondence table between an identifier of the terminal and an identifier of the user of the application, a server in which a recovery password registered by the user of the application is registered, and a client terminal holding the identifier of the user of the application A password acquisition function from the user of the application, and a portable terminal that holds the identifier of the terminal, and the user of the client terminal passes between the client terminal and the server via the terminal. Activate the application you are using A license authentication system,
Other mobile terminals replacing the mobile terminal whose identifier is registered in the server,
Obtaining a recovery password of the application from a user of the application, obtaining an identifier of the user of the application from the client terminal, and transmitting the information to the server together with an identifier of the other portable terminal,
The server is
The recovery password received from the other portable terminal is compared with the recovery password registered in advance, and if they are the same, the identifier of the portable terminal corresponding to the identifier of the application user in the second correspondence table is set to the other Means for changing to an identifier received from another mobile terminal, and the license authentication of the application can be carried out by the other mobile terminal.

  According to the present invention, when a mobile terminal is lost or a client PC is newly purchased, the license authentication of the application of the client terminal can be performed using the new mobile terminal.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram showing the carrying of the embodiment of the present invention.
In FIG. 1, a client PC 101 is an information processing device such as a desktop PC or a notebook PC used by a user.
The mobile terminal 102 is an information terminal held by the user of the client PC 101 such as a mobile phone or PHS.
The server 103 is an information processing device such as a desktop PC or a blade PC.
The client PC 101, the portable terminal 102, and the server 103 can perform data communication via the Internet 104 configured by a public line network or a wireless communication network. A plurality of devices similar to the client PC 101, the mobile terminal 102, and the server 103 are connected to the Internet 104.

FIG. 2 is a functional block diagram showing a detailed configuration of the client PC 101.
The client PC 101 includes a CPU 201 that executes programs, a memory 202 that loads programs and data, a communication unit 203 that exchanges data with other information processing devices, an input unit 204 that inputs commands and data, a system An output unit 205 that outputs the status of the application, and a storage unit 207 that stores an application type 208, an application ID 209, and an application program 206 (hereinafter abbreviated as an application) that holds a user ID 211 are connected via a bus 210.
The communication unit 203 has a function of performing direct data communication with the mobile terminal 102 using wireless LAN, Bluetooth, infrared, NFC, proximity wireless communication, or the like. In addition, a function of connecting to the Internet 104 using a wired LAN, a wireless LAN, or the like is provided.
The input unit 204 includes input means such as a keyboard, a mouse, a pen input, a voice input, a button, a jog dial, and a cross key.
The output unit 205 includes output means such as a display and sound.
The application 206 is a program to which a license is given from the server 103.
The application type 208, application ID 209, and user ID 211 are data held by the application 206 in the course of processing.

FIG. 3 is a functional block diagram illustrating a detailed configuration of the mobile terminal 102.
The mobile terminal 102 includes a CPU 301 that executes programs, a memory 302 that loads programs and data, a communication unit 303 that exchanges data with other information processing devices, an input unit 304 that inputs commands and data, An output unit 305 that outputs a system state and the like are connected to a storage unit 310 that stores a license management program 306, a license acquisition program 307, a license recovery program 312, a terminal ID 308, and a user ID 309 via a bus 311.
The communication unit 303 has a function of performing direct data communication with the client PC 101 using wireless LAN, Bluetooth, infrared, NFC, proximity wireless communication, or the like. In addition, a function of connecting to the Internet 104 using a wired LAN, a wireless LAN, or the like is provided.
The input unit 304 includes input means such as a keyboard, a mouse, a pen input, a voice input, a button, a jog dial, and a cross key.
The output unit 305 includes output means such as a display and sound.
The license management program 306 is a program that mediates license authentication of the application of the client PC 101 to the server 103.
The license acquisition program 307 is a program for acquiring license authentication information of applications that can be installed on the client PC 101 from the server 103.
The license recovery program 312 is a program for losing the mobile terminal 102 that has already acquired a license and transferring the license acquired so far to a new mobile terminal 102.
The terminal ID 308 is an identifier assigned in advance that can uniquely identify the mobile terminal 102.
The user ID 309 is an identifier that uniquely identifies the user of the mobile terminal 102.

FIG. 4 is a functional block diagram showing a detailed configuration of the server 103.
The server 103 includes a CPU 401 that executes programs, a memory 402 that loads programs and data, a communication unit 403 that exchanges data with other information processing devices, an input unit 404 that inputs commands and data, and a system The output unit 405 that outputs the status of the license, and the storage unit 411 in which the license issuance program 406, the license registration program 407, the license restoration program 413, the application list 408, the license management table 409, and the terminal ID table 410 are stored are the bus 412. Connected with.
The communication unit 403 has a function of performing data communication with the client 101 via the Internet 104 using wired, wireless LAN, Bluetooth, or the like.

The license issuance program 406 is a program that provides license authentication information of an application program managed by the server 103 to the client PC 101.
The license registration program 407 is a program for performing license authentication of an application installed on the client PC 101 and registration of a license installation status.
The license restoration program 413 is a program for registering and changing the registration information of the license that has been given to the existing mobile terminal 102 to the grant to the new mobile terminal 102.
The application list 408 stores the types of applications that can be license-authenticated by the server 103.

  FIG. 5 shows an example of the application list 408, and the item number 501 is an identifier that uniquely identifies a record in the list. The application type 502 is an identifier that identifies the type of application for which license authentication is possible.

The license management table 409 stores information such as licensed users, applications, and license authentication status.
FIG. 6 shows an example of the license management table 409, and the item number 601 is an identifier for uniquely specifying a record in the table. The user ID 602 is an identifier of a licensed user. The license application 603 is a type of application to be licensed. The application ID 604 is an identifier that uniquely identifies the licensed application.

The terminal ID table 410 manages the terminal ID of the mobile terminal 102 that receives a license grant or license authentication request.
FIG. 7 shows an example of the terminal ID table 410, and the item number 701 is an identifier for uniquely identifying a record in the list. The terminal ID 702 is an identifier that uniquely identifies the mobile terminal. The user ID 703 is an identifier that identifies the user of the mobile terminal. The recovery password 704 is a password used when granting a license to a new mobile terminal.

Hereinafter, the large operation of the entire system will be described with reference to the flowchart of FIG.
First, the user starts the license acquisition program 307 on the mobile terminal 102 (hereinafter referred to as the mobile terminal A), and acquires the license information of the necessary application from the server 103 (step 801).
Next, the user activates the application of the client PC 101 and performs license authentication using the mobile terminal A (step 802).
Next, assuming that the user has lost the portable terminal A (step 803), the license information of the application authenticated by the portable terminal A to the new portable terminal 102 (hereinafter referred to as portable terminal B). (Step 804).

Next, operations of the license acquisition program 307 of the portable terminal A and the license issuance program 406 of the server 103 will be described with reference to the flowchart of FIG.
The license acquisition program 307 transmits an application list request to the license issuance program 406 (step 901).
The license issuance program 406 receives the application list request in step 901 and returns all items of the application type 502 in the application list 408 (step 902).
The license acquisition program 307 receives the item of the application type 502 returned in step 902 and displays it on the output unit 305 (step 903).
The license acquisition program 307 acquires the application type specified by the user (step 904).

The license acquisition program 307 confirms whether data is registered in the user ID 309 (step 905). If registered, the process proceeds to step 906. If not, go to Step 911.
The application type acquired in step 904, the recovery password acquired in step 913, the user ID 309, and the terminal ID 308 are transmitted to the license issuing program 406 as a license acquisition request (step 906).

The license issuance program 406 creates a new record in the license management table 409, and registers the application type and user ID of the received license acquisition request in the items of the user ID 602 and license application 603 of the created record (step 907).
The license issuing program 406 confirms whether or not the received terminal ID is registered in the terminal ID table 410 (step 908).
If registered, the process proceeds to step 909. Otherwise, go to step 912.
A license registration completion notification is transmitted to the client PC (step 909).
Next, a notification of completion of license registration is received, and it is confirmed whether there is a license to be added (step 910). If there is no additional license, the process ends. Otherwise, the process returns to step 903.

The license issuance program 406 generates a user ID. Here, the user ID is generated using date and time, information unique to the mobile terminal 102, and the like (step 911).
The license issuance program 406 obtains a recovery password from the user when the mobile terminal 102 is lost (step 913). Then, the process proceeds to step 906.
A new record is created in the terminal ID table 410, and the received terminal ID, user ID, and recovery password are registered (step 912). Then, the process proceeds to step 909.

Next, operations of the application program 206 of the client PC 101, the license management program 306 of the portable terminal A, the license restoration program 312 of the new portable terminal B, the license registration program 407 of the server 103, and the license restoration program 413 will be described with reference to the flowchart of FIG. .
First, the application program 206 is activated by the user (step 1001).
The application program 206 generates an application ID and stores it in the application ID 209 (step 1002). Here, the application ID is generated using the date and time or information unique to the client PC 101.
Next, the application program 206 transmits the application ID 209 saved in Step 1002 and the application type 208 registered in advance to the client management program 306 (Step 1003).

The client management program 306 of the portable terminal A receives the application ID and the application type from the client PC 101 (step 1004).
The application ID and application type received in step 1004, the terminal ID 308 held by the portable terminal A, and the user ID 309 are transmitted to the license registration program 407 as a license registration request (step 1005).

The license registration program 407 checks whether the terminal ID of the received license registration request is already registered in the terminal ID list 410 (step 1006). If already registered, the process proceeds to step 1007. If not, the process ends.
The license registration program 407 selects from the license management table 409 a record in which the user ID 602 and license application 603 items are the same as the user ID and application type of the received license registration request, and sets the received application ID in the application ID 604 item. (Step 1007).

Next, the application program 206 transmits the application ID 209 as a license authentication request to the license registration program 407 (step 1008).
The license registration program 407 checks whether the received application ID of the license authentication request is registered in the license management table 409 (step 1009).

The license registration program 407 generates a license authentication key permitting the use of the application program 206 and returns it as license authentication data together with the user ID 703 of the record in the lines management table 409 confirmed in step 1009 (step 1010).
The license authentication key is, for example, a digital signature of the server 103 that can be confirmed by the application program 206 using a public key certificate issued by the server 103.
Next, the license authentication key is extracted from the received license authentication data, and the license authentication of the application on the client PC 101 is performed. The received user ID is stored in the user ID 211 of the client PC 101 (step 1011).

Here, the portable terminal A may be lost due to failure or theft. Therefore, the mobile terminal B can be used for license authentication as the new mobile terminal 102.
First, using the application program 206 authenticated by the mobile terminal A, the user ID 211 is transmitted to the mobile terminal B as a mobile terminal recovery request (step 1012).
Next, the license recovery program 312 of the mobile terminal B receives the mobile terminal recovery request from the client PC 101, and acquires the recovery password by input from the user (step 1013).
Next, the license recovery program 312 of the mobile terminal B transmits the received mobile terminal recovery request, the acquired recovery password, and the terminal ID 308 of the mobile terminal B to the license recovery program 413 of the server 103 (step 1014).

Next, the license recovery program 413 of the server 103 searches for the same record as the user ID received from the terminal ID table 410, and confirms that the recovery password 704 item in the record and the received recovery password are the same (step 1015).
Then, the terminal ID 702 item in the record of the terminal ID list 410 searched in step 1015 is rewritten to the terminal ID received in step 1015, and the process is terminated (step 1016).

FIG. 2 is a system configuration diagram showing the implementation of the license authentication system according to the present invention. It is a functional block diagram which shows the structure of client PC. It is a functional block diagram which shows the structure of a portable terminal. It is a functional block diagram which shows the structure of a server. It is a figure which shows the example of an application list. It is a figure which shows the example of a license management table. It is a figure which shows the example of a terminal ID list. It is a flowchart explaining operation | movement of the whole system. It is a flowchart explaining the operation | movement of a license acquisition process. It is a flowchart explaining the operation | movement of a license authentication process.

Explanation of symbols

101 Client PC
DESCRIPTION OF SYMBOLS 102 Mobile terminal 103 Server 104 Internet 206 Application program 306 License management program 406 License issue program 407 License registration program 409 License management table 410 Terminal ID table 413 License recovery program

Claims (1)

A first correspondence table between the usage right of the application of the client terminal and the identifier of the user of the application, and a second correspondence of the identifier of the portable terminal held by the user of the application and the identifier of the user of the application A table, a server in which a recovery password registered by the user of the application is registered, a client terminal holding an identifier of the user of the application, and a function for acquiring a password from the user of the application, and the own terminal A license authentication system for performing license authentication of an application used by a user of the client terminal via the terminal between the client terminal and a server,
Other mobile terminals replacing the mobile terminal whose identifier is registered in the server,
Obtaining a recovery password of the application from a user of the application, obtaining an identifier of the user of the application from the client terminal, and transmitting the information to the server together with an identifier of the other portable terminal,
The server is
The recovery password received from the other portable terminal is compared with the recovery password registered in advance, and if they are the same, the identifier of the portable terminal corresponding to the identifier of the application user in the second correspondence table is set to the other A license authentication system comprising means for changing to an identifier received from a portable terminal, wherein the license authentication of the application can be performed by the other portable terminal.

Images