JP5569428B2 - Mobile terminal license authentication system and license authentication method - Google Patents

Description

  The present invention relates to a license authentication system and a license authentication method for a mobile terminal that manages execution of an application on a mobile terminal that moves by being mounted on a vehicle, for example, by license authentication.

  As is well known, in a so-called mobile terminal such as an in-vehicle device or a mobile phone, the execution of an application installed therein indicates a license key distributed with the application as indicating the execution authority of the application. Management is performed based on determination of validity, that is, license authentication. According to such license authentication, for example, management such that a billable application can be executed based on registration of a license key issued when a fee is paid is realized.

  Conventionally, a technique described in Patent Document 1 is known as an example of such a license authentication system. In the license authentication system described in Patent Document 1, a content server that provides an application (learning content), a license server that creates and distributes a license key for the application, and a terminal means of a user who uses the application are connected to the Internet. Are interconnected through. The user terminal means can use the application based on the registration of the license key by receiving the license key from the license server via the Internet prior to using the application. That is, even an application that can be downloaded or copied cannot be used unless a license key is distributed from the license server by paying a fee.

JP 2002-92188 A

  By the way, in the license authentication system described in Patent Document 1, since the license key needs to be distributed prior to the execution of the application, the terminal means that cannot communicate with the license server when trying to execute the application is licensed. You can't receive the key, and you can't even run the application. And, such communication failure is especially the case for the above-mentioned mobile terminal that uses wireless communication for communication, is mounted on a mobile body such as a vehicle, or is carried around by a user and the usage environment changes. It is also an inevitable phenomenon that occurs more or less. However, even though a valid license key can be issued by a license server or the like, if a mobile terminal cannot obtain a valid license key just because communication is interrupted, it is going to be executed, for example. When the application is used for guidance of a destination or the like, its convenience is significantly impaired.

  The present invention has been made in view of such a situation, and an object of the present invention is to provide a mobile terminal capable of managing the execution of an application based on license conditions and maintaining its convenience even when communication is interrupted. A license authentication system and a license authentication method are provided.

Hereinafter, means for solving the above-described problems and the effects thereof will be described.
In order to solve the above problem, the invention according to claim 1 is directed to a mobile device in which execution of an application installed in a mobile terminal is managed based on a license key given by communication with a center provided outside. In the terminal license authentication system, the mobile terminal includes a holding unit that holds the license key, authenticates the license key held in the holding unit, and is mounted on the mobile terminal based on the authentication result. that is intended to manage the execution of the application, the has a holding portion for holding a provisional license key previously imparted from the center, performs authentication based on the license key that is held by the holding unit, the result of the authentication, When it is determined that the license key is not valid, the validity of the provisional license key held in the holding unit is determined. There, the gist that you allow execution of the application based on the determination of the provisional license key is valid.

  According to such a configuration, when the license key is not valid, the application can be executed based on the temporary license key. As a result, the application can be used on the mobile terminal even if it is not possible to acquire a valid license key due to the lack of communication between the mobile terminal and the center. The convenience is improved.

  The invention described in claim 2 is summarized in that in the mobile terminal license authentication system according to claim 1, communication between the mobile terminal and the center is performed by wireless communication.

  According to such a configuration, even when the mobile terminal cannot acquire a valid license key by wireless communication in which communication has been interrupted due to the surrounding environment such as a tunnel, underground, or mountainous area, the use of the application on the mobile terminal Therefore, it is possible to improve the convenience of the user for using the application.

  According to a third aspect of the present invention, in the mobile terminal license authentication system according to the first or second aspect, the validity of the provisional license key is determined when communication with the center is interrupted. Is the gist.

  According to such a configuration, when the license key is not valid and communication with the center is interrupted, the application can be executed based on the temporary license key. It will be done properly. For example, if communication with the center is possible, whether or not the license key is valid is managed based on the latest information, so it is unnecessary to execute the application with the temporary license key. It is possible to prevent the license key from being used.

  According to a fourth aspect of the present invention, in the license authentication system for a mobile terminal according to any one of the first to third aspects, the temporary license key is given from the center when the communication is normal. The gist is that it is given together with the license key.

  According to such a configuration, the provisional license key is acquired by the mobile terminal at the same time as the license key, so that the effort for distributing the provisional license key can be reduced. Further, managing the temporary license key together with the distribution status of the license key makes it easy to manage the temporary license key.

  According to a fifth aspect of the present invention, in the mobile terminal license authentication system according to any one of the first to fourth aspects, an application permitted to be executed based on the temporary license key is subject to a predetermined restriction. The main point is that

As in this configuration, by limiting the application executed based on the temporary license key, it is possible to achieve proper use only by the temporary license key.

  According to a sixth aspect of the present invention, in the mobile terminal license authentication system according to the fifth aspect, the restricted function of the application is variably configured in accordance with the license content of the provisional license key. Is the gist.

  According to such a configuration, since the function of the application is limited, the user can be recognized that the application is being executed with the temporary license key, and the temporary license key can be used appropriately. Will be able to.

  The invention according to claim 7 is the license authentication system for a mobile terminal according to claim 5, wherein the restriction by the temporary license key is the number of executions of the application.

  According to such a configuration, since the number of executions of the application is limited, it is possible to appropriately use the provisional license key while maintaining the convenience of the application.

  According to an eighth aspect of the present invention, in the license authentication system for a mobile terminal according to any one of the first to seventh aspects, the determination that the temporary license key is valid is performed once for each temporary license key. The main point is that

  According to such a configuration, the temporary license key that is determined to be valid and has executed the application is erased or changed, and cannot be reused. This also makes it possible to achieve proper use unique to the provisional license key.

  The invention according to claim 9 is the license authentication system for the mobile terminal according to any one of claims 1 to 8, wherein the mobile terminal further includes an input unit to which an authentication code given separately is input. And determining the validity of the provisional license key based on verification with the input authentication code.

  According to such a configuration, the validity of the temporary license key is determined based on the authentication code, so that the application based on the temporary license key is more appropriately executed.

  According to a tenth aspect of the present invention, in the license authentication system for a mobile terminal according to the ninth aspect, the authentication code is given to a portable terminal that can communicate with the center. The gist is that an authentication code given to the portable terminal is input to the input unit.

  According to such a configuration, since the authentication code necessary for determining the validity of the provisional license key is held in the mobile terminal, the use of the authentication code when the provisional license key has to be used is prevented. make it easier. Thereby, the convenience for the user is also improved.

  According to an eleventh aspect of the present invention, in the license authentication system for a mobile terminal according to the ninth aspect, the authentication code is issued as character information from the center, and characters capable of character input are input to the input unit. The gist is that an input device is provided, and the authentication code is input as character information via the character input device.

  According to such a configuration, since the authentication code is issued as character information, the management is facilitated, and the authentication code can be easily provided when it is necessary for determining the validity of the provisional license key. This also improves user convenience.

  According to a twelfth aspect of the present invention, in the mobile terminal license authentication system according to any one of the first to eleventh aspects, the application includes one or more license keys including the provisional license key. The summary is that the account can be registered.

  According to such a configuration, since execution of an application, for example, provision of a function can be controlled according to an account, an application used by a plurality of users can be controlled based on an account. Provide functions suitable for users. This further increases the utility value of such a license authentication system.

  The invention according to claim 13 is the mobile terminal license authentication system according to claim 12, wherein the one or more accounts are provided with functional restrictions separately for the accounts, and the mobile terminal. Has a storage unit that holds restriction information given to each account under communication with the center, and when permitting execution of the application for a certain account, the account information and the The gist of the present invention is to determine a function provided by the application based on collation with restriction information held in a storage unit.

  According to such a configuration, the functions provided by the application can be managed separately for each account based on the restriction information that is a restriction on the account as well as restrictions on the functions provided by the account. Can be suitably managed.

  According to a fourteenth aspect of the present invention, in the license authentication system for a mobile terminal according to the thirteenth aspect, the restriction information includes valid period information or valid count information for each account, and the mobile terminal Each time is executed, the usage status of the account that executed the application is stored in the storage unit, and when it is determined that the validity period or number of validity of the account has been exceeded based on the restriction information, The gist is to permit execution of the application by the account on condition that there is an execution history of the application.

  According to such a configuration, even if the account is invalidated, the application is executed with the same restrictions as when the application was previously executed with the account, so that the convenience of the user is improved. Be able to. In addition, for example, when a user ID is associated with an account, an account of an application executed last time can be acquired based on the user ID.

  According to a fifteenth aspect of the present invention, in the mobile terminal license authentication system according to the fourteenth aspect, the mobile terminal permits the execution of an account that is determined to have exceeded the valid period or the number of valid times. The gist is to raise the application function limit to the maximum level.

  According to such a configuration, even if the account is invalidated, the minimum functions are provided from the application, so that the convenience of the user can be improved.

  According to a sixteenth aspect of the present invention, in the mobile terminal license authentication system according to any one of the thirteenth to fifteenth aspects, the acquisition of the account held in the storage unit is interrupted from communication with the center. The gist of what is done when

  According to such a configuration, the application can be executed by an appropriate account even when it is difficult to update the account because the account is invalid and communication is interrupted. Application execution management and user convenience can be improved.

  According to a seventeenth aspect of the present invention, in the mobile terminal license authentication system according to any one of the twelfth to sixteenth aspects, the mobile terminal further includes an input unit for inputting the account identification code and password. And determining the validity of the account based on the collation with the input identification code and password.

  According to such a configuration, even when the account is invalid, the user can be identified by the identification code of the invalid account, and the application can be executed by an appropriate account for the identified user. As a result, application execution management and user convenience are improved.

  The invention according to claim 18 is the license authentication system for a mobile terminal according to any one of claims 1 to 17, wherein the mobile terminal is an in-vehicle information terminal mounted on a vehicle. .

  According to such a configuration, even if the vehicle has a high moving speed and the communication environment is highly likely to change significantly, particularly in wireless communication, the license key is valid for in-vehicle information terminals such as navigation systems. It is possible to maintain the convenience of the application by executing an application that is not a temporary license key.

In order to solve the above-described problem, the invention according to claim 19 is directed to a mobile terminal that manages execution of an application installed in the mobile terminal based on a license key given by communication with a center provided outside. In the license authentication method, the license key is held in the mobile terminal, a step of holding a temporary license key previously given from the center to the mobile terminal, and the license key in the mobile terminal A step of authenticating a license on the basis of the authentication, a step of determining the validity of the temporary license key held in the mobile terminal when the license key is not valid as a result of the authentication, and the temporary license key this and a step of permitting the execution of the application based on the determination that it is effective The the gist.

  According to such a method, the application can be executed based on the temporary license key even when communication with the center is not possible and a valid license key cannot be acquired. As a result, even when acquisition of a valid license key is impossible due to the state of communication between the mobile terminal and the center, the application can be used on the mobile terminal. Improvement comes to be achieved.

The invention according to claim 20 is the license authentication method for a mobile terminal according to claim 19, wherein communication between the mobile terminal and the center is performed by wireless communication.
According to such a method, even if the mobile terminal cannot acquire a valid license key through wireless communication in which communication has become unstable due to the surrounding environment such as a tunnel, underground, or mountainous area, the application in the mobile terminal Since it can be used, the convenience of the application can be improved.

  According to a twenty-first aspect of the invention, in the license authentication method for a mobile terminal according to the nineteenth or twentieth aspect, the step of determining the validity of the provisional license key is that communication with the center is interrupted. The gist is to be done under conditions.

  According to such a method, when the license key is not valid and communication with the center is interrupted, the application can be executed based on the temporary license key. It will be done properly. For example, when communication with the center is possible, whether or not the license key is valid is managed based on the latest information, so it is unnecessary to execute the application with the temporary license key. The key can be prevented from being used.

  According to a twenty-second aspect of the present invention, in the mobile terminal license authentication method according to any one of the nineteenth to twenty-first aspects, the application includes one or more license keys including the provisional license key. The main point is to make it possible to register an account.

  According to such a method, since execution of an application, for example, provision of a function can be controlled according to an account, an application used by a plurality of users can be controlled based on an account. Provide functions suitable for users. This further increases the utility value of such a license authentication method.

  According to a twenty-third aspect of the present invention, in the mobile terminal license authentication method according to the twenty-second aspect, the one or more accounts are given functional restrictions separately for the accounts, and the mobile terminal Stores the restriction information given to each account under communication with the center in the storage unit, and holds the account information and the storage unit when permitting execution of the application for a certain account. The gist of the present invention is to determine a function provided by the application based on collation with restriction information.

  According to such a method, the functions provided by the application can be managed separately for each account based on the restriction information that is a restriction on the account as well as restrictions on the functions provided by the account. Can be suitably managed.

  According to a twenty-fourth aspect of the present invention, in the license authentication method for a mobile terminal according to the twenty-third aspect, the restriction information includes valid period information or valid count information for each account, and the mobile terminal Each time is executed, the usage status of the account that executed the application is stored in the storage unit, and when it is determined that the validity period or the number of validity of the account has been exceeded based on the restriction information, The gist is to permit execution of the application by the account on the condition that there is an application execution history.

  According to such a method, even if the account is invalidated, the application is executed with the same restrictions as when the application was previously executed by the account, so that the convenience of the user is improved. Be able to. In addition, for example, when a user ID is associated with an account, an account of an application executed last time can be acquired based on the user ID.

The block diagram which shows the schematic structure about 1st Embodiment which actualized the license authentication system of the mobile terminal which concerns on this invention. The flowchart which shows the process process about the authentication process including the process etc. which perform an application based on a temporary license about the mobile terminal. The block diagram which shows the schematic structure about 2nd Embodiment which actualized the license authentication system of the mobile terminal which concerns on this invention. The flowchart which shows the process process about the authentication process including the process etc. which perform an application based on a temporary license about the mobile terminal. The flowchart which shows the process process about the process including the process etc. which determine the function which an application provides based on account information about the mobile terminal.

(First embodiment)
A first embodiment embodying a license authentication system for a mobile terminal according to the present invention will be described with reference to FIGS.

First, an outline of the license authentication system of this embodiment will be described.
The license authentication system includes an in-vehicle terminal 10 as a mobile terminal mounted on the vehicle 10 </ b> A and an authentication center 20 capable of wireless communication with the in-vehicle terminal 10. The in-vehicle terminal 10 is equipped with a distribution application 153 that requires license authentication for execution.

  The authentication center 20 issues a license key 100 required for the authentication of the license of the application according to the execution authority for the application given to the user based on the purchase of the application, and the issued license key. 100 is distributed to the in-vehicle terminal 10 owned by the user. Accordingly, the in-vehicle terminal 10 authenticates the license based on the license key 100 issued by the authentication center 20 for the distribution application 153 to be executed, and the distribution application 153 in response to the license being authenticated. Is allowed to run.

  In the present embodiment, the license authentication system is issued from the mobile phone 30 as a mobile terminal capable of communicating information with each other between the in-vehicle terminal 10 and the authentication center 20 and the authentication center 20. Authentication code card 31 is included. However, the present invention is not limited to this, and the license authentication system only needs to include at least one of the mobile phone 30 and the authentication code card 31.

Next, the configuration of the license authentication system of this embodiment will be described.
The authentication center 20 is provided outside the vehicle 10A. The authentication center 20 is provided with a wireless communication device (not shown) that can transmit various data to the vehicle 10A by wireless communication, or a communication device (not shown) connected to such a wireless communication device. Further, the authentication center 20 generates a license key 100 used for authenticating the license for the distribution application 153 that is installed in the in-vehicle terminal 10 and whose execution authority is managed by the license. Manage and distribute. Therefore, the authentication center 20 is provided with a license key management unit 21 that creates a license key 100 including the authority to execute the distribution application 153, maintains and manages the license key 100, and assigns (distributes) the license key 100 to each in-vehicle terminal 10. It has been. The authentication center 20 includes a provisional license key 101 that can be used for license authentication instead of the license key 100 under a predetermined condition, and an authentication code 102 used for verification for rights confirmation when the provisional license key 101 is used. And a temporary license key management unit 22 for maintaining and distributing.

  The license key management unit 21 generates a license key 100 that permits execution of the distribution application 153 in the in-vehicle terminal 10 based on a license granted to the user when the distribution application 153 is purchased. The license key 100 is created on the basis of a predetermined algorithm as a code including information such as a license validity period and a license validity count as contents licensed by the user, together with an identification number of the corresponding distribution application 153.

  The temporary license key management unit 22 generates a temporary license key 101 used for license authentication of the distribution application 153 under a predetermined condition and an authentication code 102 corresponding to the temporary license key 101. The predetermined condition is, for example, when the license key 100 is no longer valid in the in-vehicle terminal 10 and the license key 100 cannot be updated due to a temporary reason, and the corresponding application cannot be executed. The case is envisaged. Such a situation occurs when the in-vehicle terminal 10 that uses wireless communication for updating the license key 100 is in an environment where the in-vehicle terminal 10 cannot perform wireless communication. Such a situation occurs more or less when wireless communication is used to update the license key 100, and it is difficult to avoid the occurrence.

  The temporary license key 101 is generated by a predetermined algorithm as a code including information such as restriction contents given to the temporary license key 101 together with the identification number of the corresponding distribution application 153. The restriction content includes, for example, one or more restrictions such as the number of executions that can be executed by the restricted distribution application 153 and the functions restricted by the distribution application 153. Further, the temporary license key 101 may include one or more other information included in the license key 100 besides the application identification number. In the present embodiment, the temporary license key 101 is generated as a code that can be displayed as character information.

  The authentication code 102 is a code generated so that it can be determined by a predetermined collation process that it corresponds to the provisional license key 101 that is generated together. The provisional license key management unit 22 generates the provisional license key 101. Along with this, a code having a predetermined relevance to the provisional license key 101 is generated based on a predetermined algorithm. The predetermined relevance includes, for example, a relevance such that the authentication code 102 generates a predetermined key that is predetermined in combination with the temporary license key 101. In the present embodiment, the character information Is generated as a code that can be displayed as the same character information as the provisional license key 101 generated as a code that can be displayed. As a result, when the temporary license key 101 is used, the verification is performed by checking whether the code consisting of the character information constituting the temporary license key 101 matches the code consisting of the character information constituting the authentication code 102. Whether the authentication code 102 corresponds to the provisional license key 101 verified can be determined.

  The temporary license key management unit 22 transmits the created temporary license key 101 to the license key management unit 21 so as to be included in the license key 100 of the corresponding distribution application 153. Further, the license key management unit 21 includes the temporary license key 101 received from the temporary license key management unit 22 in the license key 100 of the distribution application 153 to which the license key management unit 21 corresponds. That is, in the authentication center 20, the license key 100 including the temporary license key 101 is created for the distribution application 153.

The mobile phone 30 is owned by a user who has a license for the distribution application 153, and can perform data communication with the authentication center 20 by wireless communication or wired communication using a connection cable or the like. . The mobile phone 30 is distributed (provided) with the authentication code 102 from the temporary license key management unit 22 through data communication with the authentication center 20. In addition, the mobile phone 30 temporarily holds the distributed authentication code 102 as authentication code character information 32 in a storage medium such as an internal memory.

  The authentication code card 31 is a card issued to the user who owns the license of the distribution application 153 from the authentication center 20, and the authentication code 102 created by the temporary license key management unit 22 is authenticated on a recording medium such as paper. Coded character information 32 is described.

  The in-vehicle terminal 10 is a navigation system as an in-vehicle information terminal, for example. That is, the in-vehicle terminal 10 detects the current position of the vehicle 10 </ b> A using a global positioning system (GPS) or the like (not shown). Then, by referring to the map information stored in advance based on the detected current position, the driver is guided on the travel route of the vehicle 10A to the travel destination. The in-vehicle terminal 10 includes a CPU that executes various arithmetic processes, a ROM that stores various control programs, a RAM that is used as a work area for data storage and program execution, and a memory (a storage device including a nonvolatile memory). A microcomputer (not shown) having the above is provided. That is, various types of information processing related to the navigation system are performed using this microcomputer.

  The in-vehicle terminal 10 is provided with an application execution module 15 that provides various functions required for the navigation system through execution of each application software 150 corresponding to these functions in the microcomputer.

  Each application software 150 stored in the storage device of the microcomputer is indispensable for the navigation system, and therefore is installed in the in-vehicle terminal 10 from the beginning, and is similarly installed from the beginning. A plurality of attached applications 152 are provided that provide attached functions to the system. In the present embodiment, each application software 150 includes a plurality of distribution applications 153 that are not originally installed in the in-vehicle terminal 10. That is, the distribution application 153 is an application that can be additionally installed in the in-vehicle terminal 10 by being selected by a user from a distribution center (not shown) and receiving distribution. Each distribution application 153 is distributed from a distribution center holding the distribution application 153 via wireless communication, or given (distributed) from a device holding the distribution application 153 via wired communication, so It is mounted on the terminal 10.

Since such a distribution application 153 has a high degree of freedom in distribution and a high necessity for managing the use authority of the user, the execution authority is managed by the license key 100 corresponding thereto. For this reason, the application execution module 15 confirms that the license key 100 corresponding to the distribution application 153 is valid prior to the execution of the distribution application 153, that is, receives the license authentication. That is, when the license execution is received, the application execution module 15 determines that the distribution application 153 has execution authority and causes the distribution application 153 to execute. On the other hand, when the license execution cannot be received, the application execution module 15 determines that the distribution application 153 has no execution authority and prevents the distribution application 153 from being executed. In addition, when receiving a license with a restriction, the application execution module 15 determines that the execution authority of the distribution application 153 has the restriction (condition) and causes the distribution application 153 to execute under the restriction. To. As a result, the distribution application 153 is restricted from using a part of its functions. In such a case, since the distribution application 153 is provided with functions necessary for function restriction in advance, the license key 100 corresponding to the distribution application 153 restricts the functions provided in the distribution application 153. Settings are made to use functions. Further, a plurality of types of restriction may be provided so that the function for restricting such a function can be changed according to the restriction by the license. On the other hand, when the number of executions is limited, the application execution module 15 only determines whether or not to execute the distribution application 153 depending on whether or not the license is authenticated. There may be no function for limiting the number of executions.

  The in-vehicle terminal 10 is provided with an operation button 161 for allowing the application execution module 15 to input user operation information and the like, and a touch panel 162, and character information and image information output from the application execution module 15 are displayed on the screen. A display screen 171 to be displayed and a speaker 172 that outputs audio information as sound are provided. As a result, the application execution module 15 causes an operation from the user to be input to each application software 150 to be input via the operation button 161 or the touch panel 162. On the other hand, the application execution module 15 can output characters and images output from each application software 150 to the user via the display screen 171 and sound via the speaker 172, respectively.

  Further, the in-vehicle terminal 10 is provided with a license management module 11 that performs license authentication based on the license key, and a storage module 12 that serves as a holding unit that holds the license key 100. Further, the in-vehicle terminal 10 is provided with a wireless communication module 13 that can wirelessly communicate with the authentication center 20 and an authentication code input module 14 as an input unit that allows the license management module 11 to input the authentication code 102. It has been.

  The storage module 12 is a device that includes a known recording device capable of recording various data, and can be read and written by the license management module 11. Accordingly, the storage module 12 holds the license key 100 received from the license management module 11 or transmits the held license key 100 to the license management module 11.

  The authentication code input module 14 acquires the authentication code 102 held in the mobile phone 30 or the authentication code card 31 and causes the license management module 11 to input it. The authentication code input module 14 has a character input device, and acquires the authentication code character information 32 input from this character input device. The authentication code input module 14 is provided with a short-range wireless device, and the authentication code input module 14 automatically searches for the authentication code 102 held in the device having the short-range wireless device using the short-range wireless device, The retrieved authentication code 102 may be automatically acquired.

  The license management module 11 is connected to the application execution module 15, the storage module 12, and the wireless communication module 13 so that they can communicate with each other, and the authentication code 102 input to the authentication code input module 14 is input. Are connected to the authentication code input module 14.

In response to a request from the application execution module 15, the license management module 11 performs processing for authenticating a license for the distribution application 153 designated by the application execution module 15. That is, when the license management module 11 is requested by the application execution module 15 to authenticate the license for the distribution application 153 prior to the execution of the distribution application 153, the license management module 11 performs the distribution application based on the license key 100 corresponding to the distribution application 153. 153 license authentication is performed. When it is determined that the license key 100 is valid, the license management module 11 indicates that the license is authenticated, and when it is determined that the license key 100 is not valid, the license management module 11 indicates that the license is not authenticated. This is transmitted to the execution module 15. For example, the license management module 11 refers to the validity period 122 included in the license key 100 and determines whether or not the current date and time is within the validity period 122. When the current date and time is within the valid period 122, it is determined that the license key is valid and the license is authenticated. On the other hand, when the current date and time is not within the valid period 122, it is determined that the license key is not valid. Is not authenticated. Further, for example, the license management module 11 refers to the valid count 123 included in the license key 100 and determines whether or not the current execution is equal to or smaller than the valid count. When the current execution is less than the valid count 123, it is determined that the license key is valid and the license is authenticated. On the other hand, when the current execution exceeds the valid count 123, it is determined that the license key is not valid. Do not authenticate. When there is no license key 100 corresponding to the distribution application 153, it is determined that the license key 100 is not valid and the license is not authenticated.

  The license management module 11 stores the license key 100 received from the authentication center 20. That is, the license management module 11 receives the license key 100 transmitted from the authentication center 20 to the wireless communication module 13 and stores the received license key 100 in the storage module 12.

  The license management module 11 requests the authentication center 20 to update the license key 100. That is, the license management module 11 requests the authentication center 20 to update the license key 100 when the license key 100 is not valid. If the license key 100 corresponding to the distribution application 153 requested to authenticate the license is not stored in the storage module 12, the authentication center 20 is requested to issue the license key 100 for the distribution application 153. Then, the license management module 11 receives a valid license key 100 for the distribution application 153 or receives a notification that the license key 100 cannot be issued. Normally, the authentication center 20 does not issue the license key 100 if the authority to use the distribution application 153 is not set even if the distribution application 153 is requested to be issued.

Further, the license management module 11 tries to authenticate the license based on the temporary license key 101 under a predetermined condition. The predetermined condition is when the license management module 11 is requested to authenticate the license of the distribution application 153. In addition to this, the license key 100 of the storage module 12 is not valid, and the wireless communication is not possible (discontinued), so the authentication center 20 cannot request to update the license key 100, and is not valid. The condition is such that the license key 100 includes the provisional license key 101. That is, the license management module 11 receives the authentication code 102 stored as the authentication code character information 32 in the mobile phone 30 or the authentication code card 31 via the authentication code input module 14 and the authentication code 102 is not valid. The temporary license key 101 included in the license key 100 is verified. In this embodiment, the provisional license key 101 is character information, and the authentication code 102 corresponding to the provisional license key 101 is also the same character information as the provisional license key 101. It is determined whether the code 102 is the same. When it is determined that the temporary license key 101 and the authentication code 102 are the same, it is determined that the temporary license key 101 is valid, and the license based on the temporary license key 101 is authenticated. On the other hand, if it is determined that the temporary license key 101 and the authentication code 102 are not the same, it is determined that the temporary license key 101 is not valid and the license based on the temporary license key 101 is not authenticated.

  Further, when the license based on the provisional license key 101 is authenticated, the license management module 11 authenticates the license with restrictions and sets the function when the function restriction for the distribution application 153 is set in the provisional license key 101. Information about the restriction is transmitted to the application execution module 15. As a result, in the application execution module 15, the distribution application 153 is executed under the function restriction set in the provisional license key 101.

  Further, the license management module 11 determines that the temporary license key 101 is valid only once for each temporary license key 101. That is, the license management module 11 invalidates the provisional license key 101 once determined to be invalid so that it cannot be reused. As the invalidation process, a process of deleting the temporary license key 101 from the license key 100 is performed. However, the present invention is not limited to this, and if the temporary license key 101 cannot be reused, the contents of the temporary license key 101 are rewritten. For example, processing for correcting the contents may be performed. As a result, the license is authenticated based on the temporary license key 101, while the temporary license key 101 is invalidated and cannot be reused after the license is once authenticated. When the restriction item included in the provisional license key 101 is the execution number restriction, the license management module 11 manages the number of license authentications based on the provisional license key 101, that is, the cumulative number of executions permitted. Then, after the cumulative number of executions managed reaches the execution number limit included in the provisional license key 101, the provisional license key 101 is invalidated.

  Further, the license management module 11 acquires a new temporary license key 101 after the temporary license key 101 is invalidated. That is, when the wireless communication is restored, the license management module 11 requests the authentication center 20 to issue a new temporary license key 101 that replaces the invalidated temporary license key 101. Then, the license key 100 including the new temporary license key 101 is received from the authentication center 20 and replaced with the existing license key 100. At this time, the authentication center 20 that issues a new authentication code 102 corresponding to the issuance of a new provisional license key 101 notifies the user's mobile phone 30 of the newly issued authentication code 102, It is written on the authentication code card 31 and sent to the user.

Next, a license authentication process performed by the license management module 11 will be described with reference to FIG.
First, prior to the distribution application 153 being executed by the application execution module 15, the application execution module 15 requests the license management module 11 to authenticate the license of the distribution application 153. As a result, the license management module 11 performs a license authentication process for the distribution application 153 designated by the application execution module 15.

As shown in FIG. 2, when the license authentication process is started, the license management module 11 searches the storage module 12 for the license key 100 corresponding to the distribution application 153 that is the target of license authentication. It is determined whether or not the corresponding license key 100 found in this step is valid (step S10 in FIG. 2). If it is determined that the found corresponding license key 100 is valid (YES in step S10 in FIG. 2), the license management module 11 authenticates the license of the distribution application 153, that is, the distribution application 153 Execution in the normal mode with no function restrictions is permitted (step S11 in FIG. 2). As a result, the distribution application 153 whose license has been authenticated is normally executed by the application execution module 15.

  On the other hand, when it is determined that the corresponding license key 100 is not valid (NO in step S10 in FIG. 2), the license management module 11 determines whether or not wireless communication with the authentication center 20 is available. (Step S12 in FIG. 2). If it is determined that wireless communication with the authentication center 20 is available (YES in step S12 in FIG. 2), the license management module 11 updates the license key 100 to the authentication center 20 via wireless communication. Is requested (step S13 in FIG. 2). In response to the result, the license management module 11 determines whether or not the license key 100 has been updated (step S14 in FIG. 2). At this time, when the updated license key 100 is received from the authentication center 20 (YES in step S14 in FIG. 2), the license management module 11 returns to step S10 and, based on the updated license key 100, the license The validity of the key 100 is determined. On the other hand, when it is received from the authentication center 20 that the license key 100 cannot be updated (NO in step S14 in FIG. 2), the license management module 11 determines that the license key 100 is not valid and does not authenticate the license. That is, the distribution application 153 cannot be activated (step S20 in FIG. 2). As a result, the distribution application 153 whose license is not authenticated is not executed by the application execution module 15. Then, the license authentication process in the license management module 11 ends.

  On the other hand, if it is determined that wireless communication with the authentication center 20 cannot be used (NO in step S12 in FIG. 2), the license management module 11 determines whether or not the temporary license key 101 is included in the license key 100. (Step S15 in FIG. 2). If it is determined that the temporary license key 101 is not included (NO in step S15 in FIG. 2), the license management module 11 determines that the license key 100 is not valid, and does not authenticate the license and distributes it. The application 153 cannot be activated (step S20 in FIG. 2). Then, the license authentication process in the license management module 11 ends.

  On the other hand, if it is determined that the temporary license key 101 is included in the license key 100 (YES in step S15 in FIG. 2), the license management module 11 receives the authentication code 102 via the authentication code input module 14 (FIG. 2 step S16). At this time, the fact that the authentication code 102 has been accepted is notified to the user by character information displayed on the display screen 171 or voice information output from the speaker 172. Then, the validity of the temporary license key 101 is determined through verification of the accepted authentication code 102 and the temporary license key 101 (step S17 in FIG. 2). If it is determined that the temporary license key 101 is not valid (NO in step S17 in FIG. 2), the license management module 11 determines that the license key 100 is not valid, does not authenticate the license, and distributes the license. The application 153 cannot be activated (step S20 in FIG. 2). Thus, the license authentication process for the license management module 11 is completed.

On the other hand, if it is determined that the temporary license key 101 is valid (YES in step S17 in FIG. 2), the license management module 11 invalidates the temporary license key 101 so that it cannot be reused (step in FIG. 2). S18). Further, the license management module 11 authenticates the license for the distribution application 153 based on the provisional license key 101, that is, can execute the distribution application 153 in the emergency mode under the restrictions given to the provisional license key 101. (Step S19 in FIG. 2). If the temporary license key 101 is invalidated (step S18 in FIG. 2) until the license authentication processing by the license management module 11 is completed, it may be performed after step S19. Then, the process of authenticating the license by the license management module 11 is finished.

The operation of the license authentication system configured as described above will be described below.
First, the distribution application 153 is introduced into the in-vehicle terminal 10 at an arbitrary timing according to selection by a user or the like. With the introduction of the distribution application 153, the license key 100 corresponding to the distribution application 153 is distributed (given) from the authentication center 20 and stored in the storage module 12. The license key 100 may be distributed along with the introduction of the distribution application 153, may be distributed at the first execution of the distribution application 153 introduced, or the distribution application 153 introduced. You may make it distribute every time of execution.

  Then, when the execution of the distribution application 153 is instructed from the operation button 161 or the touch panel 162 by the user's operation, the application execution module 15 performs license management of the license of the distribution application 153 prior to the execution of the distribution application 153. Request to module 11. Then, in response to the request for license authentication, the license management module 11 authenticates the license of the target distribution application 153 based on the license key 100 and transmits to the application execution module 15 whether or not the license has been authenticated. The application execution module 15 executes the distribution application 153 when the license is authenticated, and does not execute the distribution application 153 when the license is not authenticated. As a result, the execution of the distribution application 153 is managed by the result of the license authentication.

  By the way, when the license management module 11 is requested to authenticate the license of the distribution application 153, the license may not be successfully authenticated due to the communication state. That is, the license key 100 of the storage module 12 is not valid, and wireless communication is not possible due to the surrounding environment such as a tunnel, underground, mountainous area, etc., so that the authentication center 20 cannot be requested to update the license key 100. At this time, when the temporary license key 101 is included in the license key 100 that is not valid, the license management module 11 executes the distribution application 153 using the temporary license key 101 via the display screen 171 or the speaker 172. To the user or the like. Then, the license management module 11 waits for the authentication code 102 to be input via the authentication code input module 14 during a predetermined standby period. Note that when there is no input during the standby period, for example, it is treated that there is no input character. When the authentication code 102 is input via the authentication code input module 14 or when the waiting period has passed, the authentication code 102 is compared with the temporary license key 101 to verify that the authentication code 102 is the temporary license key. It is determined whether or not it is generated together with 101. For example, in this embodiment, it is verified whether the character information as the authentication code 102 matches the character information as the temporary license key 101. If it is determined as a result of the verification that the authentication code 102 corresponds to the temporary license key 101, the license is authenticated based on the temporary license key 101, and the distribution application 153 is executed by the application execution module 15. Become so. On the other hand, if it is determined as a result of the verification that the authentication code 102 does not correspond to the temporary license key 101, the license is not authenticated based on the temporary license key 101, and the distribution application 153 is not executed in the application execution module 15.

  At this time, when the function restriction is set in the provisional license key 101, the application execution module 15 causes the distribution application 153 to be executed under the function restriction, and the in-vehicle terminal 10 provides a service with the restricted function. It becomes like this. When the execution license limit is set in the provisional license key 101, the distribution application 153 is executed by the application execution module 15 until the predetermined execution count is exceeded. It should be noted that both the function restriction by the provisional license key 101 and the execution frequency restriction may be set.

As described above, according to the license authentication system for a mobile terminal of this embodiment, the effects listed below can be obtained.
(1) When the license key 100 is not valid, the distribution application 153 can be executed based on the temporary license key 101. As a result, the distribution application 153 can be used in the in-vehicle terminal 10 even when a valid license key 100 cannot be acquired because the communication between the in-vehicle terminal 10 and the authentication center 20 is interrupted. It becomes like this. For this reason, the convenience of the distribution application 153 is improved.

  (2) Even if the in-vehicle terminal 10 cannot acquire a valid license key 100 through wireless communication in which communication is interrupted due to the surrounding environment such as a tunnel, underground, or mountainous area, the use of the distribution application 153 in the in-vehicle terminal Therefore, the convenience of the distribution application 153 can be improved.

  (3) Since the distribution application 153 can be executed based on the temporary license key 101 when the license key 100 is not valid and communication with the authentication center 20 is interrupted, the temporary license key 101 is used. Will be made more appropriate. For example, when communication with the authentication center 20 is possible, whether or not the license key 100 is valid is managed based on the latest information, and therefore it is unnecessary to execute the distribution application 153 with the temporary license key 101. In such a case, the temporary license key 101 can be prevented from being used.

  (4) Since the provisional license key 101 is acquired by the in-vehicle terminal 10 at the same time as the license key 100, the effort for distributing the provisional license key 101 can be reduced. Further, by managing the temporary license key 101 in accordance with the distribution state of the license key 100, the management becomes easy.

  (5) By restricting the distribution application 153 executed based on the provisional license key 101, for example, by making the restricted function variable, proper use unique to the provisional license key 101 can be achieved. .

  (6) When restricting the function of the distribution application 153, the user can be made aware that the distribution application 153 is executed by the provisional license key 101, and the provisional license key 101 can be used appropriately. become able to.

  (7) When the number of executions of the distribution application 153 is limited, the provisional license key 101 can be properly used while maintaining the convenience of the distribution application 153.

(8) After the validity is determined and the distribution application 153 is executed, the provisional license key 101 cannot be reused because it is deleted or changed. This also makes it possible to achieve proper use unique to the provisional license key 101.

  (9) Since the validity of the provisional license key 101 is determined based on the authentication code 102, the distribution application 153 based on the provisional license key 101 is more appropriately executed.

  (10) Since the mobile phone 30 (mobile terminal) holds the authentication code 102 necessary for determining the validity of the provisional license key 101, authentication when the provisional license key 101 must be used is performed. Use of the code 102 is facilitated. Thereby, the convenience for the user is also improved.

  (11) Since the authentication code 102 is issued as character information, the management is facilitated, and the authentication code 102 can be easily provided when it is necessary to determine the validity of the provisional license key 101. This also improves user convenience.

  (12) The vehicle 10 </ b> A has a high moving speed, and there is a high possibility that the communication environment will change greatly, especially if it is wireless communication. However, even in such a vehicle 10A, for example, the in-vehicle terminal 10 (in-vehicle information terminal) such as a navigation system causes the distribution application 153 that the license key 100 is not valid to be executed using the temporary license key 101, and the distribution application The convenience of 153 can be maintained.

(Second Embodiment)
A second embodiment of the mobile terminal license authentication system according to the present invention will be described with reference to FIGS.

  Note that the license authentication system according to the present embodiment is different from the first embodiment in that the function provided by the distribution application is determined based on the account information after the license authentication is performed using the license key, as in the first embodiment. It is a different point. Therefore, in the following, differences from the first embodiment will be mainly described, the same reference numerals are given to the same configurations as those in the first embodiment, and the description thereof will be omitted.

As shown in FIG. 3, a plurality of accounts can be provided for the distribution application 153 of the present embodiment. That is, one or more accounts can be set for one license key 100. Since each account gives a functional restriction to the distribution application 153, the function provided by the distribution application 153 is defined by this. For example, in the account, a rule according to a mode in which the distribution application 153 is used, for example, a function restriction is set. For example, when a plurality of users use the same in-vehicle terminal 10 as in car sharing, accounts such as “owner user account”, “general user account”, and “guest user account” are provided. The “owner user account” is an account that can use all the functions of the distribution application 153. For example, all functions provided in the distribution application 153, “user management function”, “application setting function”, and “application The “use function” is available. The “general user account” is an account in which the use of some of the functions available in the “owner user account” is restricted. For example, while the “application setting function” and the “application use function” provided in the distribution application 153 can be used, the “user management function” that can be used with the “owner user account” cannot be used. ing. “Guest user account” is an account in which the use of some of the functions available in “general user account” is restricted. For example, while the “application use function” provided in the distribution application 153 can be used, the “user management function” and the “application setting function” that can be used in the “general user account” cannot be used. It has become. In this embodiment, the “guest user account” is the account with the highest level of function restriction because the function restriction is the highest. In this way, the user can use the functions of the distribution application 153 permitted by the account.

  The authentication center 20 is provided with an account information management unit 23 that sets a function provided to the user by the distribution application 153. The account information management unit 23 sets an account for performing an appropriate function restriction on the distribution application 153 in the in-vehicle terminal 10 as an account given to the user when purchasing the distribution application 153 and the like. An account certificate 111 corresponding to the account is generated. The account certificate 111 includes an identification number of the corresponding distribution application 153, a user ID as an identification code for identifying the user, an account for the distribution application 153 selected to be given to the user, and the like. The code to be included is created based on a predetermined algorithm. The account information management unit 23 generates a valid period 112 indicating a period in which the account certificate 111 is valid and a valid number 113 indicating the number of times of validity, along with the generation of the account certificate 111. In other words, the account certificate 111 is valid at the date and time included in the validity period 112, and is invalidated at the date and time when the validity period 112 is not reached or exceeds the validity period 112. Further, the account certificate 111 is validated when the number of activations of the distribution application 153 is the effective number 113 or less, and invalidated when the number of activations exceeds the effective number 113.

  As described above, the account certificate 111, the validity period 112, or the validity count 113 created by the account information management unit 23 is sent to the in-vehicle terminal 10 in response to a request from the in-vehicle terminal 10 in which the distribution application 153 is executed. Sent. For example, the account information management unit 23 transmits the account certificate 111 and the validity period 112 together with the license key 100 to the in-vehicle terminal 10 in response to a request from the in-vehicle terminal 10 that executes the distribution application 153 for the first time. For example, the account information management unit 23 updates the account certificate 111 in response to a request for updating the account certificate 111 from the in-vehicle terminal 10 due to the expiration of the validity period 112 of the account certificate 111 or the like. The effective period 112 is transmitted to the in-vehicle terminal 10. In addition, when the update of the account certificate 111 is requested | required, the account information management part 23 discriminate | determines a user and its account based on the user ID and password which are transmitted from the vehicle-mounted terminal 10 with the request | requirement. The user ID is an identification code that can identify a user given to each user, and the password is a code that is registered by the user when the user purchases the distribution application 153. As a result, the authentication center 20 manages the user account, the validity period 112, and the validity count 113 for the distribution application 153 so as to be associated with the user ID and the password.

  The in-vehicle terminal 10 is provided with a user registration information management module 11 </ b> A for performing license authentication based on the license key 100 and performing account discrimination based on the account information 110. The user registration information management module 11A is provided in place of the license management module 11 of the first embodiment. The user registration information management module 11A is connected to the application execution module 15, the storage module 12 as a holding unit and a storage unit, and the wireless communication module 13 so as to be able to communicate with each other, and an authentication code as an input device An input module 14 is connected.

The storage module 12 stores user registration information 1 by the user registration information management module 11A.
20 and the like can be read and written. Thereby, the storage module 12 holds the license key 100 and account information 110 received from the user registration information management module 11A, and the held license key 100 and account information 110 are read to the user registration information management module 11A. Or The user registration information 120 is provided with a license key 100 and account information 110 so as to correspond to each distribution application 153. In each account information 110, an account certificate 111 acquired from the authentication center 20, and a validity period 112 and a validity count 113 associated with the account certificate 111 are set. Each account information 110 holds previous activation information 114 as an execution history, which is information that can identify an account when the distribution application 153 was activated last time. In the account information 110, a plurality of account certificates 111 may be set together with a validity period 112 and a validity count 113 associated therewith. Further, the previous activation information 114 may be provided in the account information 110 so as to correspond to each account certificate 111.

  The previous activation information 114 is set by the user registration information management module 11A, and stores the user ID and password input by the user for execution as the usage status of the corresponding account each time the distribution application 153 is activated. Is done. Such user IDs and passwords are not only input by the user each time, but once the relationship with the electronic key possessed by the user is registered in the in-vehicle terminal 10, an electronic key used for starting the vehicle 10A, etc. It may be automatically input in response to.

  The authentication code input module 14 acquires the authentication code 102 and inputs it to the license management module 11 as in the first embodiment described above, and acquires the user ID and the password corresponding to the user ID to acquire the license management module 11. 11 to input. The authentication code input module 14 acquires the user ID and password by inputting the user ID and password through the user's operation of the character input device included therein. The authentication code input module 14 is provided with a short-range wireless device, and the authentication code input module 14 automatically uses the short-range wireless device to automatically acquire at least one of a user ID and a password held in a device having the short-range wireless device. The user ID or password searched may be automatically acquired by searching.

The configuration for license authentication in the user registration information management module 11A has the same configuration as the license management module 11 of the first embodiment described above.
Further, the user registration information management module 11A performs an account determination process for the distribution application 153 executed by the application execution module 15 in response to a request from the application execution module 15 for account determination. That is, the user registration information management module 11A is requested by the application execution module 15 to determine the account of the distribution application 153 as the distribution application 153 is executed. Then, the user registration information management module 11A determines the account of the distribution application 153 based on the account information 110 corresponding to the distribution application 153 and the user ID of the user. In account determination, when the user registration information management module 11A determines that the account certificate 111 included in the account information 110 is valid, an account set in the account certificate 111, for example, an owner user account or a general user account is selected. The account is used to limit the function of the distribution application 153. Then, the user registration information management module 11A transmits the certified account to the application execution module 15. On the other hand, if the user registration information management module 11A determines that the account certificate 111 included in the account information 110 is not valid, an account that provides a minimum function, for example, a guest user account, is used as a function restriction of the distribution application 153. The account to be used is recognized and transmitted to the application execution module 15. Whether or not the account certificate 111 is valid is determined by the user registration information management module 11A comparing (referring) the account certificate 111 to the validity period 112 associated with the account certificate 111, and the current date and time is Judgment is made based on whether or not it is within the valid period 112. That is, when the current date and time is within the range of the valid period 112, it is determined that the account certificate 111 is valid, and the account included in the account certificate 111 is recognized as an account used for the function restriction of the distribution application 153. The On the other hand, when the current date and time is not within the range of the valid period 112 (for example, has exceeded), it is determined that the account certificate 111 is not valid, and the account with the minimum function becomes the function restriction of the distribution application 153. Certified as an account to be used. Further, the user registration information management module 11 </ b> A refers to the validity count 113 associated with the account certificate 111 and determines whether or not the current activation is within the range of the validity count 113. That is, when the current execution is within the range of the valid count 113, it is determined that the account certificate 111 is valid, and the account included in the account certificate 111 is recognized as an account used for function restriction of the distribution application 153. . On the other hand, when the current execution is not within the range of the valid count 113, it is determined that the account certificate 111 is not valid, and an account with a minimum function is authorized as an account used for function restriction of the distribution application 153.

  Also, the user registration information management module 11A creates account information 110 corresponding to the distribution application 153 when there is no account information 110 corresponding to the distribution application 153, for example, when the distribution application 153 is executed for the first time. With the creation of the account information 110, the user registration information management module 11A requests the authentication center 20 to issue the account certificate 111, the account certificate 111 issued from the authentication center 20, its validity period 112, and the like. The received account certificate 111 and the validity period 112 are stored in the account information 110.

  Further, when the user registration information management module 11A determines that the account certificate 111 included in the account information 110 is not valid, the user registration information management module 11A requests the authentication center 20 to update the account certificate 111. The user registration information management module 11A receives the updated account certificate 111 and its validity period 112 from the authentication center 20, and stores the received account certificate 111 and validity period 112 in the account information 110. .

  Note that the user registration information management module 11A requests the authentication center 20 for an account certificate 111 when the vehicle 10A is in a mountainous area or an underground parking lot where wireless communication with the authentication center 20 cannot be performed through the wireless communication module 13. However, the account certificate 111 and the validity period 112 cannot be received from the authentication center 20. That is, the user registration information management module 11A cannot have the authentication center 20 issue or update the account certificate 111, the validity period 112, or the like.

  Next, a license authentication process and an account determination process performed by the user registration information management module 11A will be described with reference to FIGS. Since the license authentication process is the same as that in the first embodiment, the same reference numerals are used and the description thereof is omitted.

First, the user registration information management module 11A performs a license authentication process (steps S10 to S20 in FIG. 4) for the distribution application 153 designated by the application execution module 15. If the license is not authenticated, the distribution application 153 cannot be activated (step S20 in FIG. 4). Thereby, the process of authenticating the license by the user registration information management module 11A ends without performing the account determination process.

  On the other hand, when the distribution application 153 is permitted to execute the normal mode (step S11 in FIG. 4) or the emergency mode is permitted to execute (step S19 in FIG. 4), the user registration information management module 11A The discrimination process is performed. That is, as shown in FIG. 5, the user registration information management module 11A starts the distribution application 153 (step S30 in FIG. 5). Thereby, the application execution module 15 that has received the execution permission of the distribution application 153 from the user registration information management module 11A activates the distribution application 153 based on the execution mode that has received the permission. As the distribution application 153 is activated, the application execution module 15 requests the user registration information management module 11A to determine an account for the distribution application 153. The user registration information management module 11A determines whether the account of the distribution application 153 is valid. Is determined (step S31 in FIG. 5). Whether or not the account is valid is determined by whether or not the account certificate 111 included in the account information 110 corresponding to the distribution application 153 is valid. For example, if the account certificate 111 corresponding to the user ID exists, the current date and time is within the valid period 112, and the activation count does not exceed the valid count 113, the account certificate 111 is valid. To be judged. On the other hand, when the account certificate 111 does not exist, when the current date and time is outside the valid period 112, or when the number of activations exceeds the valid number 113, the account certificate 111 is determined to be invalid. .

  If it is determined that the account certificate 111 is valid (YES in step S31 in FIG. 5), the user registration information management module 11A is configured to execute the distribution application 153 with the account set in the account certificate 111. The execution module 15 is notified (step S32 in FIG. 5). As a result, the application execution module 15 executes the distribution application 153 based on the function restriction by the notified account.

  If it is determined that the account certificate 111 is not valid (NO in step S31 in FIG. 5), the user registration information management module 11A determines whether or not wireless communication with the authentication center 20 is available (FIG. 5). Step S33). If it is determined that wireless communication with the authentication center 20 can be used (YES in step S33 in FIG. 5), the user registration information management module 11A sends the account certificate 111 to the authentication center 20 via wireless communication. The updated account certificate 111 is acquired from the authentication center 20 (step S34 in FIG. 5). When the account certificate 111 is acquired, the user registration information management module 11A notifies the application execution module 15 of the account set in the account certificate 111, and the distribution application 153 determines whether or not the distribution application 153 has a function restriction based on the notified account. To be executed.

  On the other hand, if it is determined that wireless communication with the authentication center 20 cannot be used (NO in step S33 in FIG. 5), the user registration information management module 11A determines whether or not the previous activation information 114 is included in the account information 110. Is determined (step S35 in FIG. 5). If it is determined that the previous activation information 114 is not included (NO in step S35 in FIG. 5), the user registration information management module 11A cannot specify an available account, so the function of the distribution application 153 is minimized. The account to be notified is notified to the application execution module 15 (step S36 in FIG. 5). As a result, the application execution module 15 starts the distribution application 153 based on the notified account. The account that minimizes the functions of the distribution application 153 is, for example, a guest user account.

  If it is determined that the previous activation information 114 was included in the account information 110 (YES in step S35 of FIG. 5), the user registration information management module 11A inputs the user ID and password via the authentication code input module 14. Accept (step S37 in FIG. 5). Then, the entered user ID and password are compared with the contents of the previous activation information 114 held in the account information 110 to determine whether or not the account certificate 111 was valid at the previous activation (FIG. 5). Step S38). If it is determined that the account certificate 111 is valid at the time of the previous activation (YES in step S38 in FIG. 5), the user registration information management module 11A distributes based on the account function restrictions set in the account certificate 111. The application execution module 15 is notified to execute the application 153 (step S32 in FIG. 5). As a result, even when the account certificate 111 cannot be updated, the distribution application 153 can be temporarily activated based on the account certificate 111 before the update.

  Conversely, if it is determined that the account certificate 111 was not valid at the time of the previous activation (NO in step S38 in FIG. 5), the user registration information management module 11A cannot identify an available account. The distribution application 153 is activated based on an account that provides a minimum function (step S36 in FIG. 5).

  If it is determined that the account certificate 111 is valid at the time of the previous activation (YES in step S38 in FIG. 5), the user registration information management module 11A may delete the previous activation information 114 or the previous activation information. The content of 114 may be rewritten to the content that the account certificate 111 is invalid. As a result, when the determination in step S35 or step S38 is executed again without updating the account certificate 111, the account for starting the distribution application 153 is limited to an account that provides a minimum function. be able to.

  As described above, according to the license authentication system for a mobile terminal of the present embodiment, in addition to the effects (1) to (12) described in the first embodiment, the effects listed below are obtained. Be able to.

  (13) Execution of the distribution application 153, for example, provision of functions can be controlled (restricted) according to the account, so even if the distribution application 153 is used by a plurality of users, Provide appropriate functions. This further increases the utility value of such a license authentication system.

  (14) The functions provided by the execution of the distribution application 153 can be managed separately for each account by the restriction information (validity period 112 and validity count 113) that is a restriction on the account as well as the restriction of the provision function by the account. . For this reason, the function provided by the distribution application 153 can be suitably managed.

  (15) Even if the account is invalidated, the distribution application 153 is executed with the same function restriction as the function when the distribution application 153 was previously executed with the account. Will be enhanced. That is, an account of the distribution application 153 executed last time can be acquired based on the user ID associated with the account, and the acquired account can be used for function restriction of the distribution application 153.

(16) Even if the account is invalidated, the delivery application 153 provides a minimum function based on the guest user account and the like, so that the convenience of the user can be improved.

  (17) The distribution application 153 can be executed with an appropriate account even when it is difficult to update the account because the account is invalid and communication is interrupted. 153 execution management and user convenience can be improved.

  (18) Even when the account is invalid, the user of the invalid account is identified based on the user ID / password 35, and the distribution application 153 can be executed by an appropriate account for the user. Thus, the execution management of the distribution application 153 and the convenience of the user can be improved.

(Other embodiments)
In addition, each said embodiment can also be implemented with the following aspects.
In the second embodiment, the case where the license key 100 and the account information 110 are held in one storage module 12 has been illustrated. However, the present invention is not limited to this, and the license key and the account information may be held in different storage modules. This increases the degree of freedom in designing the license authentication system.

  In the second embodiment, the case where an owner user account, a general user account, and a guest user account are provided as accounts used for function restriction in the distribution application 153 has been illustrated. However, the present invention is not limited to this, and the number of accounts used for function restriction may be two, three or more, and the function assigned to the account used for function restriction may be freely assigned according to the application. For example, the function assignment may be made to correspond to the function to be assigned according to the price at the time of license purchase. As a result, the degree of freedom for setting a plurality of accounts is increased, and the utility value of the license authentication system is also increased.

  In the second embodiment, the case where the validity of the account certificate 111 is determined based on the validity period 112 and the validity count 113 is illustrated. However, the present invention is not limited to this, and the validity of the account certificate may be determined based on either the validity period or the validity count. This increases the degree of freedom in designing the license authentication system.

  In each of the above embodiments, the case where the distribution application 153 is provided by software is illustrated. However, the present invention is not limited to this, and the distribution application may be provided by hardware (electronic circuit) such as a custom LSI. As a result, applications to which this license authentication system can be applied are expanded.

  In each of the above embodiments, the distribution application 153 is illustrated as being distributed from a distribution center (not shown). However, the present invention is not limited to this, and the distribution application may be distributed from an authentication center. As a result, the degree of freedom in designing the license authentication system is improved.

  In each of the above embodiments, the case where the mobile phone 30 and the authentication code card 31 are provided in the license authentication system is illustrated. However, the present invention is not limited to this, and the license authentication system may be provided with at least one of a mobile phone and an authentication code card.

In each of the above embodiments, the case where the mobile phone 30 is used as the mobile terminal is illustrated. However, the present invention is not limited to this, and the mobile terminal may be a variety of devices such as a memory card as long as it can hold the authentication code It may be a storage device. In this case, the communication with the authentication center or the in-vehicle terminal may be wired communication via the connection slot. As a result, the design flexibility of the license authentication system can be improved.

  In each of the above-described embodiments, the case where it is determined that the temporary license key 101 is valid only once per temporary license key 101 is illustrated. However, the present invention is not limited to this, and the temporary license key may be used a plurality of times. As a result, the degree of freedom for license authentication based on the provisional license key is improved.

  In each of the above embodiments, the case where the license key 100 including the provisional license key 101 is given (distributed) from the authentication center 20 to the in-vehicle terminal 10 is illustrated. However, the provisional license key may be sent separately from the license key from the authentication center to the in-vehicle terminal. Further, the temporary license key sent separately may be input from the authentication center to the in-vehicle terminal via a mobile phone or an authentication code card, as in the case of the authentication code. Even in this case, if the distribution application corresponding to the provisional license key sent separately becomes clear, the provisional license key can be used when the distribution application is executed.

  In each of the above embodiments, the case where the temporary license key 101 is used when communication between the in-vehicle terminal 10 and the authentication center 20 is interrupted is illustrated. However, the present invention is not limited to this, and a temporary license key may be used when an appropriate response cannot be obtained from the authentication center even if communication between the in-vehicle terminal and the authentication center is possible. As a result, it is possible to prevent the distribution application from being unavailable due to inconveniences occurring in the authentication center, and the convenience of the distribution application is improved.

  In each of the above embodiments, the license authentication based on the temporary license key 101 is performed when the license cannot be successfully authenticated due to the communication state. However, the present invention is not limited to this, and if necessary, license authentication based on the temporary license key may be performed even when an appropriate response is obtained from the authentication center through communication. For example, when a mobile terminal such as a mobile phone having an authentication code is included, license authentication may be performed. As a result, the aspect in which the license can be authenticated based on the temporary license key is expanded, and the convenience of the system to which the license authentication system is applied can be improved.

  In each of the above embodiments, the case where the communication between the in-vehicle terminal 10 and the authentication center 20 is performed by wireless communication is illustrated. However, the present invention is not limited to this, and may be used when communication becomes unstable in wired communication or the like. This increases the availability of the license authentication system.

  In each of the above embodiments, the case where the license of the distribution application 153 is authenticated by the license key 100 is illustrated. However, the present invention is not limited to this, and authentication of licenses for applications other than the distribution application, such as basic applications and attached applications, may be managed by the license key. The distribution application may include one or more applications that do not require license authentication with a license key for execution. As a result, the flexibility of using the license authentication system can be improved.

In each of the above embodiments, the case where the license based on the temporary license key 101 is authenticated based on the fact that the temporary license key 101 and the authentication code 102 are the same is illustrated. However, the present invention is not limited to this, and the authentication code may include information different from the temporary license key as long as it can be identified that the authentication code corresponds to the temporary license key.

  For example, in the license key verification process in the in-vehicle terminal, processing such as encryption or decryption is performed, or by using various arithmetic for verification, an authentication code held in the mobile phone is temporarily stored in the in-vehicle terminal It can be different from the license key. By doing so, the degree of freedom in designing the license authentication system is improved, and proper handling of the temporary license key can be promoted.

  In each of the above embodiments, the case where the validity of the provisional license key 101 is determined by collating with the authentication code 102 is exemplified. However, not limited to this, when a temporary license key is required, such as when the license key cannot be renewed due to a lack of wireless communication, etc., it is subject to the restrictions set in the temporary license key without matching the authentication code. The distribution application may be executed. This enhances the convenience when the temporary license key is used.

  In each of the above embodiments, the case where the in-vehicle terminal 10 is a navigation system is illustrated. However, the present invention is not limited to this, and the in-vehicle terminal may be various vehicle control devices provided in the vehicle, an information processing device such as an acoustic product, or the like. Thereby, this license authentication system can be widely applied to in-vehicle devices.

  In each of the above embodiments, the case where the in-vehicle terminal 10 is a mobile terminal is illustrated. However, the present invention is not limited to this, and the mobile terminal may be a mobile phone or an information terminal carried by a person. Thereby, the types of mobile terminals that can provide this license authentication system are expanded, and the convenience of these mobile terminals can be improved.

  DESCRIPTION OF SYMBOLS 10 ... In-vehicle terminal, 10A ... Vehicle, 11 ... License management module, 11A ... User registration information management module, 12 ... Storage module, 13 ... Wireless communication module, 14 ... Authentication code input module, 15 ... Application execution module, 20 ... Authentication Center, 21 ... License key management unit, 22 ... Temporary license key management unit, 23 ... Account information management unit, 30 ... Mobile phone, 31 ... Authentication code card, 32 ... Authentication code character information, 35 ... User ID / password, 100 ... license key, 101 ... provisional license key, 102 ... authentication code, 110 ... account information, 111 ... account certificate, 112 ... validity period, 113 ... validity count, 114 ... activation information, 120 ... user registration information, 122 ... valid Period, 123 ... Effective count, 150 ... A Publication software, 151 ... Basic applications, 152 ... companion applications, 153 ... delivery applications, 161 ... operation button, 162 ... touch panel, 171 ... display screen, 172 ... speaker.

Claims (24)

In a mobile terminal license authentication system in which execution of an application installed in a mobile terminal is managed based on a license key given by communication with a center provided outside,
The mobile terminal has a holding unit that holds the license key, authenticates the license key held in the holding unit, and manages execution of an application installed in the mobile terminal based on the authentication result And having a holding unit for holding a temporary license key given in advance from the center , performing authentication based on the license key held in the holding unit, and as a result of the authentication, the license key is not valid wherein the time, a determination of the validity of the provisional license keys held by the holding unit, you allow execution of the application based on the determination of the provisional license key is valid it is determined that A mobile terminal license authentication system. The mobile terminal license authentication system according to claim 1, wherein communication between the mobile terminal and the center is performed by wireless communication. The mobile terminal license authentication system according to claim 1 or 2, wherein the validity of the provisional license key is determined when communication with the center is interrupted. The license authentication system for a mobile terminal according to any one of claims 1 to 3, wherein the temporary license key is given together with a license key given from the center when the communication is normal. The mobile terminal license authentication system according to any one of claims 1 to 4, wherein an application permitted to be executed based on the provisional license key is executed under a predetermined restriction. The mobile terminal license authentication system according to claim 5, wherein the restricted function is variably configured in the application according to a license content of the provisional license key. The license authentication system for a mobile terminal according to claim 5, wherein the restriction by the temporary license key is the number of times the application is executed. The mobile terminal license authentication system according to any one of claims 1 to 7, wherein the determination that the temporary license key is valid is performed only once for each temporary license key. The mobile terminal further includes an input unit for inputting a separately provided authentication code,
The mobile terminal license authentication system according to any one of claims 1 to 8, wherein the validity of the provisional license key is determined based on verification with the input authentication code. The authentication code given to the mobile terminal that can communicate with the center is input to the input unit, and the authentication code given to the mobile terminal is input to the input unit. Mobile terminal license authentication system. The authentication code is issued as character information from the center, and the input unit is provided with a character input device capable of character input,
The mobile terminal license authentication system according to claim 9, wherein the authentication code is input as character information via the character input device. The license authentication system for a mobile terminal according to any one of claims 1 to 11, wherein one or more accounts can be registered for one license key including the provisional license key in the application. The one or more accounts are provided with functional restrictions in addition to those accounts,
The mobile terminal has a storage unit that holds restriction information given separately for those accounts under communication with the center,
13. The transfer according to claim 12, wherein when the execution of the application for a certain account is permitted, a function provided by the application is determined based on collation between information on the account and restriction information held in the storage unit. Terminal license authentication system. The restriction information includes validity period information or validity count information for each account, and each time the application is executed, the mobile terminal stores the usage status of the account that executed the application in the storage unit. Is,
The execution of the application by the account is permitted on the condition that there is an execution history of the application by the account when it is determined that the effective period or the number of effective times of the account has been exceeded based on the restriction information. The mobile terminal license authentication system described. The mobile terminal license authentication system according to claim 14, wherein the mobile terminal raises the function limit of an application that is permitted to be executed to a maximum level for an account that is determined to have exceeded the valid period or the number of valid times. The license authentication system for a mobile terminal according to any one of claims 13 to 15, wherein acquisition of an account held in the storage unit is performed when communication with the center is interrupted. The mobile terminal further includes an input unit to which the identification code and password of the account are input, and the validity of the account is determined based on collation with the input identification code and password. The license authentication system for a mobile terminal according to any one of 16. The mobile terminal license authentication system according to any one of claims 1 to 17, wherein the mobile terminal is an in-vehicle information terminal mounted on a vehicle. In a mobile terminal license authentication method for managing execution of an application installed in a mobile terminal based on a license key given by communication with a center provided outside,
The license key is held in the mobile terminal;
Holding a provisional license key pre-assigned from the center to the mobile terminal;
Authenticating a license based on the license key in the mobile terminal;
As a result of the authentication, when the license key is not valid, determining the validity of the provisional license key held in the mobile terminal ; and
Activation method of a mobile terminal characterized by comprising the step of permitting the execution of the application based on the determination of the provisional license key is valid. The mobile terminal license authentication method according to claim 19, wherein communication between the mobile terminal and the center is performed by wireless communication. The mobile terminal license authentication method according to claim 19 or 20, wherein the step of determining the validity of the provisional license key is performed on condition that communication with the center is interrupted. The mobile terminal license authentication method according to any one of claims 19 to 21, wherein one or more accounts can be registered for one license key including the provisional license key in the application. The one or more accounts are given functional restrictions in addition to those accounts,
The mobile terminal stores in the storage unit restriction information given to each account under communication with the center, and when permitting execution of the application for an account, the account information and the storage unit The license authentication method for a mobile terminal according to claim 22, wherein a function provided by the application is determined based on collation with restriction information held in the mobile terminal. The restriction information includes validity period information or validity count information for each account, and each time the application is executed, the mobile terminal stores the usage status of the account that executed the application in the storage unit. And
The execution of the application by the account is permitted on the condition that there is an execution history of the application by the account when it is determined that the validity period or the number of effective times of the account has been exceeded based on the restriction information. License authentication method for mobile terminals.

Images