JP2015014817A - Software use control system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To support various license configurations, and to improve the availability of the use of a license on an off-line regarding software use control.SOLUTION: A software use control system includes: a contract information table in which the content of a license contract is registered; and a license management table in which the use state of a license is registered. In the contract information table, the number and period of an installation license determining how many client PC can install software and a simultaneous start license determining how many client PC can simultaneously use software are registered. When receiving an installation request, license management means newly applies the installation license when the number of installation licenses being used at present is less than an allowable number, and when receiving a start request of application software, the license management means newly applies the simultaneous start license when the number of the simultaneous start licenses being used at present is less than an allowable number.

Description

  The present invention relates to a software usage control system, and more particularly to software usage control related to accounting and taxation used in accounting firms and general companies.

  Conventionally, since software sales are sales of licensing rights (licenses), it is generally prohibited to install software with one license on multiple computers, exceeding the number of software licenses. In many cases, it cannot be used.

  In the node-locked license method that restricts the use of software by granting licenses on a computer basis, the license depends on the hardware, so there is inconvenience that the software cannot be used when the computer is used for other purposes. is there. For this reason, other users cannot try the software and experience the ease of use etc., and as a result of hesitating to purchase additional licenses, the work efficiency of the entire office is improved. You will lose opportunities.

  As a means for compensating for the inconvenience of the node-locked license method, there is a floating license method in which a license is temporarily granted for each computer only when software is used.

The accounting firm handles monthly settlements and tax returns for a number of corporate clients. In particular, in tax returns, when you need to update the software to the latest version due to tax reform, etc., or use software that is not frequently used (for example, inheritance tax), purchase only the license of the software to be used when necessary. The form to use is widespread.
In accounting offices composed of a plurality of staff members, there is a tendency that the use of the above-mentioned floating license method is preferred from the viewpoint of business efficiency.

  Also, when managing software licenses, a management system using a server connected via a WAN (Wide Area Network) such as the Internet may be constructed as a server for managing licenses.

  For example, there is Patent Literature 1 as a technique for solving the inconvenience caused by the failure to acquire a license due to a failure of a WAN line. According to such a technology, license management information is temporarily transmitted from an external license management server to a server in the office via a WAN line, and thereafter, license management is completely performed on the server in the office. Therefore, even if a failure occurs in the WAN line, no problem occurs.

  However, since license management is performed on the server in the office that is blocked from the license management server, it is unknown whether or not the license is properly managed on each terminal, and the application program provider also takes risks, In addition, there is a disadvantage that it is difficult to deal with dynamic license distribution management.

  The idea of using a license has also been used in CAD software and the like. In the case of CAD or the like, a license is obtained from a vendor that issues a license, the license is stored in a license management server installed in the office by a person using CAD, and the MAC address unique to the terminal that permits license use, etc. Local use that restricts the use of licenses is the mainstream, and it is not a form of accessing the vendor's license management server via the Internet every time the license is used, so dynamic license distribution management The inconvenience that it is difficult to deal with occurs.

JP 2001-5659 A

  In the floating license method, a method of managing licenses using a license management server is generally used. In such a system, a client-server type is adopted, and when the software is activated on the client machine, the number of activations is counted to limit the number of software that can be used simultaneously.

  In recent years, the use of a license management server using a wide area network such as the Internet has become widespread, but there is a problem that a license cannot be acquired if there is a communication failure. Also, depending on the license purchase time, validity period, contract status, etc., there are cases where it is inconvenient to simply limit the number of software that can be used simultaneously.

  Furthermore, there is a problem that management of software programs to be used, distribution method to client machines, license management, and the like are complicated.

  Therefore, the present invention relates to the use of accounting and tax software used in general corporate offices and accounting offices by providing an external license management server connected to the client machine via the Internet. License management at the time of occurrence, and if necessary, distribute the program to the client machine and distribute the license server to the server in the accounting office, etc. The purpose is to improve the installation efficiency.

The present invention relates to a software usage control system that manages license usage of application software in one or more client PCs.
Storage means for storing at least a contract information table in which the contents of the license contract are registered and a license management table in which the usage status of the license is registered;
License management means for referring to the contract information table and the license management table to perform license management of application software in an individual client PC,
In the contract information table, an installation license that defines how many client PCs the application software can be installed, and how many of the installed client PCs can use the application software simultaneously. The number and period of the specified simultaneous activation license are registered,
The license management means includes:
(1) When an installation request for the application software is received from the client PC, the number of installation licenses and their valid periods and the number of currently used installation licenses are confirmed, and the currently used installation is confirmed. If the number of licenses is less than the number of valid installation licenses, a new installation license is granted,
(2) Upon receiving a request for starting the application software, at least the number and the validity period of the concurrent activation license and the number of the concurrent activation licenses currently used are confirmed, and the concurrent activation licenses currently used When the number is less than the number of valid simultaneous activation licenses, a new simultaneous activation license is newly granted.

Further, the contract information table further includes an exclusive use column that defines a simultaneous activation license reserved for a predetermined client PC among the simultaneous activation licenses,
When receiving a request for starting the application software, the license management unit extracts the number of the simultaneous activation licenses excluding those reserved for the predetermined client PC as the number of effective simultaneous activation licenses. Thus, it is preferable to newly grant a simultaneous activation license when the number of simultaneous activation licenses currently used is less than the number of valid simultaneous activation licenses.

Furthermore, a system includes the client PC and / or the office server,
When the client PC and / or the in-office server detects a connection failure with the license management server when requesting the simultaneous activation license,
(A) When the access to the communication network is not possible, the application software can be activated only for a first period;
(B) When the access to the communication network is possible and maintenance information of the license management server cannot be acquired, the application software can be activated only for a second period;
(C) It is preferable that the application software can be activated without a time limit when the communication network is accessible and maintenance information of the license management server can be acquired.

  According to the present invention, the license of the application software is a “software license” as a superordinate concept in which each office concludes the right to use the software, and the software is installed on the number of client PCs for each office. “Installation license” as a middle concept that determines whether to use the software, and “Concurrent activation license” as a subordinate concept that determines how many of the installed client PCs can use the software at the same time Since various license checks are performed based on the respective contracts, software control appropriately corresponding to various license modes can be realized.

  In addition, according to the present invention, it is possible to efficiently purchase additional licenses, stop using them, and control the number of simultaneous activations.

  Furthermore, by setting the offline usage state in stages according to the failure status, the software can be used within the limits without accessing the license management server.

FIG. 1 is a block diagram showing the overall configuration of the software usage control system 100. FIG. 2 is a block diagram showing the configuration of the license management server 10. FIG. 3 is a block diagram showing the configuration of the in-office server 20. FIG. 4 is a block diagram showing the configuration of the client PC 30. As shown in FIG. FIG. 5 is a conceptual diagram for explaining the modes and types of licenses managed by the software usage control system according to the present invention. FIG. 6 is a diagram showing an embodiment of a contract information management table for registering license contents of each office stored in the license management server 10. FIG. 7 is a diagram showing a license management table for managing the number of installed software applications and the number of simultaneously activated software applications in each office. FIG. 8 is a diagram showing an embodiment of an authentication management table for managing authentication IDs and passwords when connecting from the in-office server 20 and / or the client PC 30 to the license management server 10. FIG. 9 is a diagram showing a client PC information management table for the in-office server 20 to manage the client PC 30 in the office. FIG. 10 is a diagram showing an application management table for managing application software registered in the license management server 10. FIG. 11 is a diagram for explaining a procedure for installing specific application software in the client PC 30. FIG. 12 is a flowchart for explaining the details of the installation process of the client PC 30. FIG. 13 is a diagram showing a floating license permission flow of the license management server 10. FIG. 14 is a diagram showing an alive monitoring log recorded in the license management server 10. FIG. 15 is a diagram for explaining another embodiment of the floating license permission flow shown in FIG. FIG. 16 is a diagram illustrating an operation mode management table that defines operation modes (0 to 3) when a failure occurs. FIG. 17 is a diagram illustrating a failure management table that records the occurrence of a failure and records the number of times of offline activation and time. FIG. 18 is a diagram showing a failure history table recorded by the license management server 10. FIG. 19 is a diagram for explaining a floating license permission flow when the in-office server 20 temporarily substitutes the license management of the license management server 10 during maintenance of the external network or the license management server 10 or when a failure occurs. is there. FIG. 20 is a sequence diagram showing the flow of processing for the entire system of the present application. FIG. 21 is a sequence diagram for permitting offline processing when a failure occurs in the license management server 10 or during maintenance. FIG. 22 is a sequence diagram for permitting offline processing when an Internet access failure occurs. FIG. 23 is a diagram illustrating the overall configuration of the software control system according to the second embodiment. FIG. 24 is a sequence diagram for explaining the flow from start to end of application software in the second embodiment. FIG. 25 is a diagram showing an offline operation sequence during failure or maintenance of the license management server 230 in the second embodiment. FIG. 26 is a diagram showing an offline operation sequence when an Internet access failure occurs in the second embodiment. FIG. 27 is a sequence diagram for explaining a process of releasing an activation license and allocating an activation license to another terminal when a terminal using application software fails. FIG. 28 shows a processing flow when a failure or maintenance of the license management server 210 or an Internet connection failure occurs in a state where the application software has already been activated on the client PC 230. FIG. 29 is a diagram illustrating an example of a contract information table according to the third embodiment. FIG. 30 is a diagram illustrating an example of a management screen displayed on the client terminal 30 according to the third embodiment.

  Exemplary embodiments of a software use control system according to the present invention will be described below in detail with reference to the accompanying drawings. Note that the present invention is not limited to the embodiments.

  In the first embodiment, an in-office server and one or more client PCs are installed in an accounting office, and an example in which software is used from an accounting office by connecting to a license management server via the Internet will be described. .

[Configuration of Software Use Control System According to Embodiment 1]
First, the configuration of the software use control system according to the first embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing the configuration of the software usage control system according to the first embodiment.

  As illustrated in FIG. 1, a software usage control system 100 according to the first embodiment includes a license management server 10, an in-office server 20, one or more client PCs (Personal Computers) 30a, 30b,. Is provided. In the software usage control system 100 of this embodiment, the license management server 10 and the office server 20 are connected via the Internet 40, and the in-office server 20 and the client PC 30 are LAN-connected in the office. The plurality of client PCs 30a, 30b,... Are described as client PCs when they are not particularly distinguished.

  The license management server 100 is a server that manages licenses based on information relating to software use and information relating to user contracts. The license management server 100 receives a software activation request from the in-office server 20, confirms the license usage status, and activates the license. Notify permission / denial to the office server, and monitor the usage of software (life monitoring).

  The in-office server 20 is a server device installed in an accounting office or a company office, and is connected to a client PC 30 installed in the office. Information management of the client PC 30 and connection to the license management server 10 are performed. Manage. This embodiment also has a function of distributing application software to the client PC 30. For example, the in-office server 20 receives a request for using a software license from the client PC 30 and requests permission to use the license management server 10 via the Internet 40. Alternatively, as necessary, the license management server 10 can be directly requested to permit use of the client PC 30 based on the management information in its own apparatus without requesting permission for sequential use.

  The client PC 30 is an information processing apparatus such as a desktop PC, a tablet PC, or a notebook PC, and is a computer terminal used in the office. The client PC 30 is assigned and holds a unique ID as advance preparation. Then, the desired application software can be downloaded and installed from the office server 20 connected via the LAN, and the application software can be used.

  Hereinafter, the configuration of the license management server 10, the configuration of the in-office server 20, and the configuration of the client PC 30 will be described in order with reference to FIG.

[License Management Server Configuration]
First, the configuration of the license management server 10 shown in FIG. 1 will be described with reference to FIG. FIG. 2 is a block diagram illustrating the configuration of the license management server 10 according to the first embodiment. As shown in FIG. 2, the license management server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The processing of these units will be described below.

  The control unit 11 is configured by loading a program defining various processing procedures onto a RAM (Random Access Memory) and executing each processing step by the CPU, and controls execution of various processing. And a work memory (RAM or the like) for temporarily storing necessary data, and various processes are executed by these. The control unit 11 is a program or function module, which includes an office information control unit that processes information on a contracted office that uses a software application, an external terminal authentication unit that performs connection authentication from the in-office server 20 and the client PC 30, An installation license control unit that processes installation license information of the client PC 30 and a simultaneous activation license information control unit are provided.

  The storage unit 12 stores data and programs necessary for various processes performed by the control unit 11, and stores various management tables in which license contract information for each office is registered and programs to be distributed to the in-office server 20. To do. Each application program is registered in the application program registration unit, and can be updated to the latest version as appropriate. However, the application program registration unit is not necessarily provided in the license management server, but may be provided in another server, and each application program may be distributed from here.

  The communication unit 13 controls communication related to various types of information exchanged with the in-office server 20 connected thereto. Specifically, the communication unit 13 receives an office ID, a software ID for which a license is requested, and the like from the office server 20 and notifies the in-office server 20 of license permission information.

[Office server configuration]
Next, the configuration of the in-office server 20 shown in FIG. 1 will be described with reference to FIG. FIG. 3 is a block diagram illustrating the configuration of the in-office server 20 according to the first embodiment. As shown in FIG. 3, the office server 20 includes a control unit 21, a storage unit 22, and a communication unit 23. The processing of these units will be described below.

  The control unit 21 has an internal memory for storing a program that defines various processing procedures and the necessary data, and executes various processes using these programs. As a program or function module of the control unit 21, an installation program installation control unit that distributes an installation program to each client PC 30, a license management server access control unit for connecting to the license management server 20, and connection from the client PC 30 are processed. A client PC access control unit and an application control unit are provided.

  The storage unit 22 stores data and programs necessary for various processes by the control unit, and stores various management tables and application programs distributed to the client PC. Each application program related to the contract is registered in the application program registration unit, and these can be updated from the license management server 10 to the latest version as appropriate, and the client PC 30 to which an installation license is assigned is appropriately configured. Can be downloaded or updated.

  The communication unit 23 controls communication related to various information exchanged between the license management server 10 and the client PC 30 to be connected. Specifically, the communication unit 23 receives, for example, the ID of software that is requested to use a license from the client PC 30 connected to the LAN in the office, and sends the license to the license management server 10 via the Internet 40. A request for use permission is received, the license use permission information received from the license management server 10 is received, and the client PC 30 is notified.

[Client PC configuration]
Next, the configuration of the client PC 30 shown in FIG. 1 will be described with reference to FIG. FIG. 4 is a block diagram illustrating the configuration of the client PC 30 according to the first embodiment. As shown in FIG. 4, the client PC 30 includes a control unit 31, a storage unit 32, a communication unit 33, an input unit 34, and an output unit 35. The processing of these units will be described below.

  The control unit 31 has an internal memory for storing a program that defines various processing procedures and the necessary data, and executes various processes using these. A module directly related to the present invention includes a software information acquisition unit and a software management unit. Of course, it also has a function of executing application software.

  The storage unit 32 stores data and programs necessary for various processes by the control unit 31, and stores various management tables and application programs.

  The communication unit 33 controls communication related to various information exchanged between the in-office server 20 and the client PC 30. Specifically, the communication unit 33 requests the use of a license from the in-office server 20 (via the license management server 10) connected to the LAN in the office, and receives the license notified from the office server 20. Receive usage permission information.

  The input unit 34 is used to input an instruction to select application software to be used, and includes a keyboard, a mouse, a microphone, and the like. The output unit 35 includes a monitor (display, touch panel) and a speaker.

[Explanation of license type and concept]
FIG. 5 is a conceptual diagram for explaining the modes and types of licenses managed by the software usage control system according to the present invention. In this application, the application software license is a “software license” as a superordinate concept that each office concludes on the right to use the software, and the number of client PCs 30 installed in each office "Installation license" as a middle concept that determines whether it is okay and "simultaneous activation license" as a subordinate concept that determines how many of the installed client PCs can use the software at the same time are specified ing.

  In the example shown in FIG. 5A, for the “corporate tax return” creation software, the office that uses it creates a software license in one year, and then extends the contract for another year. Then, two installation licenses are contracted simultaneously with the software license, and then one installation license is added in the middle of the contract period. The contract contents can be arbitrarily set if the software provider and the user agree, but in the example shown in this figure, the usage period of the installation license is attached to the software license, and the added installation license is 1 with the end of the software license. It ends in less than a year. In this example, as the software license is extended by one year, all three installation licenses are extended by one year. Although not explicitly shown in the figure, a simultaneous activation license can be set separately from the installation license, and the simultaneous activation license is equal to or less than the number of installation licenses. These are managed by the license management server 10, and the software cannot be installed on the client PC 30 exceeding the number of contracts, and the software cannot be used simultaneously on the client PC 30 exceeding the contract number of the simultaneous activation licenses.

  FIG. 5B shows a contract example of the simultaneous activation license. As a premise, a software license is concluded between the office and the software provider, and at least three installation licenses are purchased. As shown in Figure 5, two simultaneous activation licenses that expire for one year are first purchased, one continues one year later, and one expires by not renewing the contract after one year To do. In addition, another additional activation license for another year is purchased before the first year, which is valid for one year from the date of purchase and disappears without being renewed after one year. Therefore, as shown in FIG. 5, there are two simultaneous activation licenses at the beginning, after which one is added to become three, after which one continues the contract, one expires and the simultaneous activation license Becomes two, and after that, one additional contract expires and finally one remains. As described above, various types of licenses can be set between the software provider and the user (office) using the three concepts of software license, installation license, and simultaneous activation license. Software control appropriately corresponding to the above is realized by the system of the present invention.

[Description of various tables]
(1) Contract information management table (license management server / office server)
FIG. 6 is a diagram showing an embodiment of a contract information management table for registering license contents of each office stored in the license management server 10. As shown in the figure, the contract information management table includes registration fields for an office ID, an application ID, a software license (start-end), an installation license (start-end), and a simultaneous activation license (start-end). Is provided. In the contract information management table, the number of installed licenses and the start and end times of each of the application software contracted by each office according to the contract concluded between the provider of the application software and each office, The number of simultaneous activation licenses and the start and end of each are registered. The end period is determined on the basis of the concept of FIG. 5 based on the information of the start period and the period of use (in the example shown in the figure, it may be managed in units of one month or one week), and is recorded in the table. Here, the number of simultaneous activation licenses is always set to be equal to or less than the number of installation licenses. When a license is newly purchased or the period is updated, the end period is set based on the concept of FIG. 5, and the contract information management table is updated for the new end period. In addition, the license management server 10 checks the contract information management table at least once a day, and deletes the license whose expiration date has passed or sets an invalid flag. In this way, various license forms as shown in FIG. 5 can be flexibly recorded and managed. The registration contents for each office in the contract information management table are notified to the in-office server 20 of the office as needed, and the in-office server 20 holds the same contract contents for the office.

(2) License management table (license management server / office server)
FIGS. 7a and 7b show two types of license management tables for actively managing the number of installed software applications and the number of simultaneously started software applications in each office held by the license management server 10 and, if necessary, the in-office server 20. An example is shown. In the example shown in FIG. 7a, the license management table includes, for each application software contracted by each office, the ID of the client PC 30 installed in the office and the ID of the client PC 30 currently running the application software (these Is referred to as “PCID”.). Here, as for the office ID, the license management server 10 records information for each office, and the in-office server 20 records only the information of the office. The installed PCID column and the startup PCID column are updated as needed by a notification from the server 20 in the office. That is, upon receiving an installation request from the office, the license management server 10 checks the number of installed licenses in the contract information table (FIG. 6) and the number of installed PCs in the license management table (FIG. 7). A new installation license is assigned, and the PCID included in the installed notification is registered in the license management table. Similarly, when the activation request is received, referring to the contract information table (FIG. 6) and the license management table (FIG. 7), if the number of simultaneously activated PCs is less than the number of simultaneously activated licenses, a simultaneous activation license is granted and activated. The PCID included in the notification is registered in the license management table. Upon receiving the application software end report of any client PC 30 from the in-office server 20, the license management server 10 deletes the corresponding simultaneously activated PCID in the license management table. Further, the license management server 10 receives the activation notification from the client PC 30 that periodically activates the application software or the in-office server 20 that monitors the application software, and monitors whether the application in each client PC is active or not. If the regular activation notification cannot be obtained from the registered client PC even once, or if the predetermined activation period has elapsed without obtaining the regular activation notification, the client PC is determined from the activation PCID in the license management table. Delete minutes. In addition, the license management server 10 makes an inquiry to the client PC 30 that is running the application software or the in-office server 20 that monitors the client PC 30 on a regular basis as to whether or not it is running as described above. It is also possible to monitor the life and death of an application on each client PC and delete the corresponding client PC from the activation PCID in the license management table. As a result, deadlock of the simultaneous activation license can be prevented.

  In another embodiment shown in FIG. 7b, the license management table manages the number of installable units, the number of installed PCs, the number of simultaneously startable PCs, and the number of simultaneously started PCs for each application in each office. Among these, the installable number and the simultaneously startable number are appropriately updated by referring to the contract information table (FIG. 6). The installed number and the simultaneously activated number are updated as needed by notification from the in-office server 20. When the license management server 10 receives an installation request or activation request from the in-office server 20, the license management server 10 refers to the license management table and grants a license and updates the table if it is within the license. In addition to registering each PCID as shown in FIG. 7A, floating license management can be performed only by managing the number of installed / activated devices as a whole as shown in FIG. 7B. The number of simultaneous activations is decremented by 1 when an application termination notification is received. In this example as well, application software in each client PC is monitored for life and death, and periodic activation notifications cannot be obtained even once. If a predetermined period has not passed since the periodic activation notification cannot be obtained, it may be determined that the application software is no longer used in the client PC, and the number of simultaneous activations may be reduced by one.

  In the above, the process of managing the activation request of each client PC 30 via the in-office server 20 mainly by the license management server 10 has been described. Without notifying the activation request of the client PC 30, the in-office server 20 can mainly manage the activation request of each client PC 30 using the license management table (FIGS. 7a to 7b). . In this case, each license management table may be used by the in-office server 20 by sharing only the portion of the license management table stored in the storage unit of the license management server 10 for the office. Accordingly, a table stored in the storage unit of the in-office server 20 and synchronized with the license management server 10 at any time may be used.

(3) Authentication management table (license management server)
FIG. 8 shows an example of a table that is stored in the license management server 10 and manages the authentication ID and password when connecting from the in-office server 20 and / or the client PC 30 to the license management server 10. In the example shown in the figure, the office ID, the authentication password, and the connection destination address of the office server are registered in the authentication license management table. When the license management server 10 receives a connection request from the in-office server 20 or the client PC 30, the license management server 10 permits the connection when the ID and password included in the request are matched and matched.

(4) Client PC information management table (in-office server / license management server)
FIG. 9 shows a table for the office server 20 to manage the client PC 30 in the office. In this client PC information management table, a client PC ID and a name of each client PC (arbitrary, for example, “Tanaka exclusive use PC”) are registered. The same information may be notified and held by the license management server 10.

(5) Application management table (license management server / office server)
FIG. 10 shows a table for managing application software registered in the license management server 10. In this application management table, an application ID, an application name, and version information are registered. When a new version of the application software is registered in the license management server 10, this table is updated (that is, the latest version is recorded). When the license management server 10 receives the activation request, the license management server 10 checks the application management table based on the application ID and version information included in the request, and the application installed in the requested client PC 30 is older than the registered version. If it is a thing (usually when the version value is small), a version upgrade can be notified. Further, when a new version is registered in the application management table, the client PC of which office is extracted with reference to the license management table of FIG. 7a, and the client PC is extracted. Alternatively, a version upgrade guide may be automatically transmitted. The license management server 10 and the in-office server 20 may periodically communicate so that the in-office server 20 holds the same application management table.

[Application installation from office server to client PC]
FIG. 11 is a diagram for explaining a procedure for installing specific application software in the client PC 30. As a premise, the latest version of the installer, which is a program for executing the installation process, the connection tool for connecting to the license management server 10, and the software application package is registered in the storage means of the license management server 10. These programs and tools are copied to the shared folder of the in-office server 20 by periodically communicating from the in-office server 20 to the license management server 10. The connection tool includes a connection address for connecting to the license management server 10. The client PC 30 accesses the shared folder of the in-office server 20, acquires an installer and a connection tool, and installs a desired application program. In this embodiment, an example in which an application program is stored in an office server and installed on a client PC from the office server will be described. However, an application is not stored in the office server, and an application is received from an external license management server. You may comprise so that a program may be downloaded directly. Details of the installation process of the client PC 30 will be described with reference to FIG.

  As shown in FIG. 12, first, the installer is downloaded from the client PC 30 with reference to the shared folder of the in-office server 20 (a1-a2). When this installer is activated, the connection tool is downloaded from the shared folder of the in-office server 20 (a4). The acquired connection tool includes the connection destination address of the license management server 10, the ID of the application program, and the like. When the connection tool is activated (a5), an installation license request is automatically transmitted to the license management server 10 via the in-office server 20 (a6). This installation license request includes an office ID, a client PC ID, a server connection authentication password, an application ID, and the like. The license management server 10 refers to the license management table (FIG. 7) and the contract information table (FIG. 6) as needed. If the number of installed licenses in the office is less than the number of installed licenses, the license management server 10 Is returned (a7). In response to this, the client PC 30 downloads the software package and installs the application software (a8), and sends an installation license use notification to the license management server 10 via the in-office server 20 (a9). The license management server 10 records that the application software is installed in the new client PC 30 in the license management table (FIG. 7). In the case of FIG. 7a, the PCID of the client PC is recorded in the installed PCID column, and in the case of FIG. 7b, the installed number is added by one.

[Floating license permission flow of license management server]
FIG. 13 shows a floating license permission flow of the license management server 10. The floating license check is roughly composed of a stepwise and hierarchical check procedure such as an installation license check and a simultaneous activation license check (if necessary). When the application software is to be activated on the client PC 30, an activation license request is transmitted to the license management server 10 via the in-office server 20 (b1-b2). The activation license request includes at least an office ID and an application ID, and optionally includes a terminal PCID. Here, “optional (if necessary)” means that if the server in the office acquires the required number of concurrent activation licenses and then allocates them to the terminals, the license management server side This is because it is not necessary to notify the PCID of the terminal. When the license management server 10 receives the application software activation license request, the license management server 10 refers to the contract information table (FIG. 6) recorded in the storage unit (b3), and first determines whether there is a contract for the software. Is checked (b4). That is, the presence / absence and validity period of the software license is confirmed from the office ID and application ID, and if there is no license or it is outside the validity period, the license request is rejected. In this case, a message “Application cannot be started” is displayed on the client PC 30, and the start of the application itself is restricted, or the partially started application is forcibly terminated if necessary (b12). In another embodiment, more specifically, a message such as “Software license is not purchased” may be displayed.

  If the software license is confirmed, the installation license is checked (b6). Here, with reference to the license management table of FIG. 7, it is confirmed whether the number of installations is within the license (b7). In the embodiment shown in FIG. 7a, it is confirmed whether the PCID included in the activation request is registered in the installed PCID column. In the embodiment shown in FIG. 7b, it is checked whether the installed number of the application software exceeds the installable number. If there is a problem, the license is rejected (to b12). If there is no problem, the simultaneous activation license is checked (b8). In the embodiment of FIG. 7a, the number of simultaneous activation licenses in the contract information table in FIG. 6 is confirmed. If the number of activation PCIDs in the license management table in FIG. 7a is less than the number of licenses, a new activation license is permitted. . In the case of the embodiment of FIG. 7b, a new activation license is permitted (b9-b10) if the number of simultaneous activations is less than the number of simultaneous activations. This is notified to the client PC 30 and the application is activated (b11). When the activation license is granted, it is recorded in the license management table (FIG. 7).

  In the above, the process of managing the activation request of each client PC 30 via the in-office server 20 mainly using the license management server 10 has been described. The activation request of each client PC 30 may be managed using the license management table (FIGS. 7a to 7b). The processing flow using each license management table in this case is the same.

  For example, if the contract information for the number of concurrent startups of the corporate tax application program in the office is 3 and if 2 are already running, the startup request for the 3rd is within the scope of the concurrent startup license. Therefore, activation is permitted, and the activation of the third unit is recorded in the license management table held by the license management server 10. In this state, if there is a corporate tax application program activation request from another terminal, the activation request is not permitted. If the activation request is not permitted, the activation of the application itself is restricted, and a message “Application cannot be activated” is displayed on the client PC 30. In this case, the user may display a floating activation status screen as shown in FIG. 30 to be described later, confirm the usage (activation) status of the application to be activated, and confirm whether or not there is a free space. Alternatively, when the license management server 10 or the in-office server 20 terminates the use of the application for which the activation request is not permitted in any terminal and the activation license becomes empty, the client PC 30 that is not permitted. It may be configured to notify that a vacancy has occurred.

  Even when the application program is terminated in any one of the client PCs 30, the license management server 10 is notified and activation completion is reflected in the license management table. Further, an application usage report is periodically transmitted from each client PC 30 executing the application program to the license management server 10, and this is recorded in the license management server 10 as an alive monitoring log as shown in FIG. The license management server 10 periodically acquires the periodic activation notification from the client PC registered as being activated by referring to the license management table in FIG. 7 and the alive monitoring log in FIG. 14 even once. Alternatively, when a predetermined period has elapsed since the periodic activation notification cannot be acquired, the client PC is deleted from the activation PCID in the license management table. As a result, deadlock of the simultaneous activation license can be prevented.

  FIG. 15 is a diagram for explaining another embodiment of the floating license permission flow shown in FIG. The flowchart shown in FIG. 15 is the same as that shown in FIG. 13 except that steps b6-b7 for checking the installation license are not provided. The same processing is indicated by the same reference numeral. As described above, when the floating license is permitted, the installation license may not be checked, but the activation may be permitted only by checking the software license and the simultaneous activation license. In yet another embodiment, the software license in steps b4-b5 may be omitted (not shown). It should be noted that the step of confirming the install license (b6-b7) is omitted because the fact that the app can be activated is based on the premise that the install license is valid in the first place.

  In this way, various licenses can be defined by flexibly combining different concepts of an installation license and a simultaneous activation license. An image of such a flexible license structure is shown on the right side of FIGS. For example, in the type A license structure, information on the use start date and the use end date indicating the use end date is used as the software license composition of application software (for example, corporate tax return, depreciation, etc.). Configured as the first tier, the second tier has software activation (validation, meaning installation here) based on the installation license, and the third tier starts based on the simultaneous activation license Shows a state in which floating (number of activations) that is permitted is assigned.

  In the case of the type B license structure, the installation license and the simultaneous activation license are assigned in the same row as the first layer of the software license, and the usage start date and the expiration date information are simultaneously activated as the second layer. Assigned to a level below the license. On the premise of such a hierarchical structure, the installation license and the simultaneous activation license are used in a composite and hierarchical manner, thereby enabling multifaceted management of the floating license.

  Especially in the case of the type B configuration, an installation license and a simultaneous activation license can be set in parallel below the software license. For example, independent floating license management is possible even at the head office and branch of the same company. This enables more flexible floating license management.

  Here, the NET license shown in FIG. 13 and the like is an installation request / startup request from the office side client PC based on the install license or the simultaneous start license registered in the license management server by the contract with the office. In this case, the concept corresponds to a license (installed license or simultaneous activation license) that is actually granted after performing a license check. In other words, as viewed from the license management server side, for individual applications in individual offices, it is a paraphrase for convenience in order to distinguish the contracted license from the actually granted license. The actually granted license for the number of allowable licenses) is called a NET license.

[Processing when an external license management server connection failure occurs]
Further, the software control system of the present invention can start the application software on the client PC even when the failure of the license management server 10 occurs, during maintenance of the license management server 10, or when communication with the license management server 10 is not possible due to an Internet connection failure. It has a function to make. This will be described in detail below.

[Description of tables used when a failure occurs]
(6) Operation mode management table (office server / client PC)
FIG. 16 is a table defining operation modes (0 to 3) when a failure occurs. The operation mode 0 is a normal operation in which no failure has occurred, and the application software of the client PC is also an operation mode in which the above-described normal operation is performed. The operation mode 1 is an operation mode in which the offline operation is permitted without imposing a time limit when the license management server 10 is under maintenance. In this case, if the maintenance period is notified and recorded in advance in the in-office server 20, or if maintenance information is recorded in an authentication server (not shown) in front of the license management server 10 and there is a connection request, that fact To be returned. The operation mode 2 is an operation mode in which an offline operation is permitted for X hours (for example, 12 hours) when a failure occurs in the license management server 10. The operation mode 3 is an operation mode in which an off-line operation is permitted only for Y hours (for example, 6 hours) when a failure occurs in the Internet connection. Internet failures include hub and router failures, connection cable failures, Internet provider maintenance and failures. This operation mode management table is registered in the in-office server 20 and / or each client PC. The above X time and Y time can be arbitrarily set on the application software provider side, but cannot be changed on the user side. For example, an operation mode management table that is a source that can be set in the license management server 10 is registered, and the operation mode management table cannot be changed when the in-office server 20 and / or each client PC 30 downloads application software. It is conceivable to capture in various forms.

(7) Fault management table (office server / client PC)
FIG. 17 is a table for recording the occurrence of failure and the number of times of offline activation and time. In the failure management table, the number of offline activations and the activation time are recorded in addition to the failure event and the failure occurrence date and time. This information is notified to the license management server 10 at the time of failure recovery, and is also recorded by the license management server 10.

(8) Failure History Table of License Management Server 10 FIG. 18 is a failure history table recorded by the license management server 10. In this table, the office ID, the office name, the total number of offline activations, the total offline activation time, and the like are recorded. The license management server 10 acquires the failure information recorded as shown in FIG. 17 from the client PC 30 or the in-office server 20 at the time of failure recovery, and adds the failure occurrence count and the offline activation time to the failure history table. Based on this record, it is conceivable to perform management such as additional charging for offline activation.

[Floating license permission flow when a failure occurs]
FIG. 19 shows that the office server 20 temporarily replaces the license management of the license management server 10 when an external network failure occurs (including provider maintenance), when the license management server 10 is maintained, or when a failure occurs. The floating license permission flow is shown.

  First, in the client PC 30, when a desired application is to be activated (c1), activation license request processing is executed by the license management server 10 via the in-office server 20 (c2). If no failure has occurred, the license check shown in FIG. 13 or FIG. 15 is performed (c4), the activation license is granted (c5), and the client PC 30 is in the operation mode 0 (see FIG. 16). The application software is activated and normal operation is performed (c6).

  In step c3, if there is no response to the activation license request for a predetermined period, the above-mentioned failure or maintenance status is confirmed. First, the Internet connection is checked (c7), and when there is a response to the Internet access (c8) and information during maintenance of the license management server 10 is acquired, the operation mode 1 is shifted to the offline operation permission mode. Basically, as long as maintenance is underway, offline operation is permitted without time limit. The off-line operation is permitted without time limit because the office or the client PC is not responsible, and is due to the convenience of the license management server 10.

  Next, when there is a response to the Internet access in Step C8, if the maintenance information cannot be acquired (c9: N), the in-office server 20 or the client PC 30 determines that a failure has occurred in the license management server 10. Then, the operation mode management table of FIG. 16 is referred to, and the operation mode 1 is shifted to the X time (for example, 12 hours). By setting X time (for example, 12 hours) at the time of failure of the license management server 10, it is possible to flexibly cope with a case where the license management server 10 is recovered immediately or a relatively long down time. In the first embodiment, since the in-office server 20 exists, the management server stored in the storage unit of the in-office server 20 is used without intentionally shifting to the offline operation mode as described above. The service permitted for the use request (start-up request) of the client PC 30 can be continued. For terminals that have already acquired an activation license and activated and used the application, the detected failure status or maintenance status without shifting to the offline operation mode, in particular, as described in FIG. 28 described later. You can use the app only while you want to use it as it is.

  Further, in step c7, the Internet connection is checked, and if there is no response to the Internet access (c8: N, external network failure, service provider maintenance, etc.), offline operation in operation mode 3 for Y hours (for example, 6 hours) Similarly, it is possible to flexibly cope with a case where a recovery is made immediately or a relatively long down.

  As described above, by making the time during which the in-office server 20 can substitute the license management in the offline state variable according to the failure, maintenance status, and level, a flexible response is possible.

  In advance, the license management server notifies the in-office server of information on the scheduled date and time during which maintenance is not possible and the service cannot be answered. Based on the scheduled date and time information, the process proceeds to the offline operation mode 1 in step c10 in FIG. You may make it do.

  The offline activation time in the client PC 30 is recorded in the in-office server 20 and / or the failure management table (FIG. 17) of the client PC 30. If communication with the license management server 10 has not been recovered after the time when offline activation is permitted, the application The software is forcibly terminated. When the failure is recovered later, information on the failure management table is notified to the license management server 10 and recorded in the failure history table (FIG. 18) on the license management server 10 side.

[Flow of overall processing from application startup to termination]
FIG. 20 is a sequence diagram showing a processing flow for the entire system including the client PC, the in-office server, and the license management server from the start to the end of the application. This sequence diagram corresponds to the processing of the flowcharts of FIGS.

  When an operator operates a keyboard or mouse on the client PC 30 or operates an application activation icon (not shown) on the screen by remote operation via a portable terminal, the client PC 30 performs office work. A connection request and an application activation request are notified to the license management server 10 via the in-house server 20. Alternatively, without going through a scheme in which the license management server is sequentially notified of the use request of the client PC 30 and granted permission, the server in the office is the main body and the various management tables stored in the own machine or the license management server side The use request of the client PC 30 may be permitted based on the various management tables stored in. In this case, in FIG. 20, communication between the in-office server 20 and the license management server 10 is performed in the license management server as necessary (such as when the license management table is not recorded in the storage unit of the in-office server 20). Starting with only communication between the client PC 30 and the in-office server 20 except when performing a reference process such as a license management table or a reference process of a license management table or contract information table at a predetermined timing. License management such as request to activation permission is performed.

  Upon receiving the connection request and activation request notification, the license management server 10 compares the ID and password with reference to the authentication management table (FIG. 8), and proceeds to the license check process (FIG. 13) if the authentication is successful. To do. Here, the contract information table in FIG. 6 and the license management table in FIG. 7 are referred to, and an application program that is already within the software license expiration period or that has been requested to start is assigned an installation license and is about to start. Determine if it is an installed terminal.

  Here, referring to the application management table of FIG. 10, the version of the application software related to the activation request is determined, and if the version is not the latest, the latest version is updated prior to activation. In addition, it may be controlled via the in-office server 20.

  When the appropriateness of the installation license is confirmed, the process proceeds to the confirmation process of the number of simultaneous activations. In the confirmation process of the number of simultaneous activations, in the office where the activation is requested, it is confirmed whether the application program is within the range of the number of simultaneous activations related to the contract information in light of the activated status of the other client PCs 30. Done. As described with reference to FIG. 15, the installation license check can be omitted.

  More specifically, while referring to the contract information table in FIG. 6 and confirming how many units can be activated simultaneously in the office, referring to the license management table in FIG. Confirm in real time that the terminal is using the application that requested the activation. When it is determined that the value is within the range of the maximum number of simultaneous activations, activation permission is notified (activation license issuance). At this time, the PCID of the client terminal 30 according to the request is recorded in the activation PCID column of the license status management table (FIG. 7), or is updated and registered by incrementing the value of the number of simultaneous activations. For example, in the office with ID “1004” in FIG. 7B, the number of simultaneous activations for the application software with the application ID “A001” is 2, but if a new activation request is permitted, this number is set to 2. Will be updated from 3 to 3.

  When the activation license is issued in this way, the in-office server 20 permits the client PC 30 to activate the application software requested to be activated. In the client PC 30, the application software requested to be activated is activated for the first time.

  In addition, when application software termination processing is performed in the client PC 30, an application termination notification is notified to the license management server 10 via the in-office server 20 in parallel with the data saving (registration) processing. The license management server 10 reduces the number of simultaneous activations in the license management table by one or deletes the PCID from the activation PCID column for the application in the office that has received the end notification.

  In this way, one or more installation licenses are distributed in advance to an office or business operator, and a terminal that may use an application program among a plurality of computer terminals owned by the office or business operator. By pre-installing the application program and preinstalling the application program, the application software can be used immediately on the necessary client PC 30 within the range of the simultaneous activation license number.

  For example, in the case of accounting processing at an accounting office, installation and various initial settings are saved in applications where it is required to perform operations while switching many application programs related to tax accounting. This is useful in that the application program can be used immediately on a necessary terminal.

  In particular, in accounting tax services for accounting firm advisors, accounting for head office branches at companies, and accounting for subsidiaries of the parent company, multiple advisors or branches, etc. This is particularly effective because it is required to perform processing while switching from time to time using a plurality of application programs according to the business.

  In addition to preinstalling application programs in advance on terminals to which installation licenses have been assigned, the license management server 10 and the in-office server 20 cooperate to update the latest application programs as needed. It is particularly effective for applications in the tax accounting field where frequent application program updates are required due to tax system revisions or changes in accounting standards.

  In this way, the usability of floating licenses for application programs, especially in the field of tax accounting, is dramatically improved by utilizing software licenses, installation licenses, and simultaneous activation licenses in a multifaceted, complex, and organic manner. Can be made.

[License management server offline processing]
The overall system processing of the offline operation described in the flowchart of FIG. 19 will be described with reference to FIGS. FIG. 21 is a sequence diagram for permitting offline processing when a failure occurs in the license management server 10 or during maintenance. When the application of the client PC 30 is activated, an activation license request is transmitted to the license management server 10 via the office server 20. However, if a failure occurs in the license management server 10 and the license permission / rejection response times out without being returned for a predetermined period, the client PC 30 first checks the Internet access, and if the Internet access is normal, the license management server 10 maintenance information is confirmed. If the maintenance information can be acquired, the client PC 30 is allowed to operate offline in the offline operation mode 1 with no time limit. If the maintenance information cannot be confirmed, the license management server 10 is permitted to perform the offline operation in the operation mode 2 for Y hours. The When the use of the application program is terminated, the server 20 is notified and the number of activations and the offline activation time are recorded.

  FIG. 22 is a sequence diagram for permitting offline processing when an Internet access failure occurs instead of a server failure. In this sequence, the application program activation request does not reach the license management server 10 due to a communication failure and times out. When the Internet access check is performed from the client PC 30, the communication failure is confirmed. In this case, the in-office server 20 operates in the operation mode. 3 permits offline operation for Y hours. In the first embodiment, since the in-office server 20 exists, the management server stored in the storage unit of the in-office server 20 is used without intentionally shifting to the offline operation mode as described above. The service permitted for the use request (start-up request) of the client PC 30 can be continued.

  Although the first embodiment of the present invention has been described in detail above, the present invention is not limited to the above configuration and operation. As long as the flexible floating license management that is the object of the present invention can be realized, each component of the system, details of the table, details of processing, and the like can be changed as appropriate. For example, although the above shows a minimum table configuration and processing configuration for achieving a desired operation, various other improvements and changes can be added. For example, in one or more of the license management server 10, the office server 20, and the client PC 30, the installation date and time of application software based on the installation license, the activation time based on the activation license, and the like may be recorded in the table. Furthermore, the system of the present invention can be realized without providing the in-office server 20. This will be described below.

[System configuration]
FIG. 23 is a diagram illustrating the overall configuration of the software control system according to the second embodiment. As shown in FIG. 23, in the software control system 200 of this embodiment, an external license management server 210 and a plurality of client PCs 230 in the office are connected via the Internet 40. The license management server 210 of the present embodiment is almost the same as the configuration of the license management server 10 of the first embodiment, and the contract information table of FIG. 6, the license management table of FIG. 7, the authentication management table of FIG. Client PC information management table, an application management table of FIG. 10, a failure history table of FIG. The communication unit 33 controls communication related to various types of information exchanged with each connected client PC 230. Specifically, the communication unit 33 receives an office ID, an application ID for which a license is requested, and the like from each client PC 230, and notifies each client PC 230 of license permission information. On the other hand, each client PC 230 on the office side has various tables (contract information table having only information of the office or the client PC 230, a license management table, an authentication management) held by the server 20 in the first embodiment. Table, the operation mode management table of FIG. 16, the failure management table of FIG. 17, and the like.

[Operation flow]
(1) Software Installation In this embodiment, the process of installing the application software on each client PC 30 is basically the same as the process of the first embodiment, and since there is no in-office server 20, the client PC 230 and the license management server 210 are Application installation is performed through direct communication.

  Here, details of the application installation process from the license management server 210 to the client PC 230 will be described with reference to FIG. 12, which is a process flow diagram of installation from the in-office server. First, when the license management server 210 is accessed for installation from the client PC 230, the license management server 210 refers to the contract information table (FIG. 6) and the authentication management table (FIG. 8) stored in the storage unit, and then contracts. Using the information, the office ID and the authentication password, the client PC 230 recognizes that the software license to be installed is a terminal belonging to the office related to the predetermined contract, and is allowed to connect to the license management server. The installer is downloaded (steps a1 to a2). Thereafter, except that the client PC 230 directly accesses the license management server 210, the process of executing the steps a3 to a9 to install the application is the same. In this embodiment, the details of each process are as described above. Although it adjusts suitably according to a change, since these are obvious changes for those skilled in the art, the detailed description is abbreviate | omitted.

  When the application is installed on the client PC 230 (step a8), the contract information table (FIG. 6) and the license management table (FIG. 7) stored in the storage unit of the license management server 210, or the license management server 210 A client PC information management table (FIG. 9) and an application management table (FIG. 10) that are shared with the client PC 230, or an application management table (FIG. 10) and installation installed in the storage unit of the client PC 230 In the application management table (FIG. 9) and the like, information on the installed application software (for example, the application ID and version information of the application software, the application software installed in which terminal of which office) It has been one of the association information, install date information, a license valid date and information of the license expiration date, etc.) registration is done.

(2) Floating License Management FIG. 24 is a sequence diagram for explaining the flow from start to end of application software. Floating license management is almost the same as in the first embodiment, and the license management is performed by the client PC 230 and the license management server 210 directly communicating without going through the in-office server. Details of the license check are the same as those in the first embodiment shown in FIGS. Further, the flow when a failure occurs when trying to start the application software after the occurrence of the failure is the same as the operation of the first embodiment shown in FIG. 19 and is offline in any of the operation modes 1 to 3 according to the failure event. Operation is possible. FIG. 25 shows an offline operation sequence at the time of failure or maintenance of the license management server 230, and FIG. 26 shows an offline operation sequence at the time of Internet access failure.

  FIG. 27 shows a process of releasing an activation license when a specific terminal (for example, client PC 230a) receives application license and using application software, and assigning the activation license to another terminal when the client PC 230a breaks down. FIG. When an activation license is granted in response to a request from the first client PC 230a and the application software is used on the client PC 230a, a usage report is periodically sent to the license management server 210, and the alive monitoring management table in FIG. To be recorded. The license management server 210 periodically refers to the life and death monitoring management table, inquires whether or not it is periodically activated, and when there is no response, or periodically issues a notification of activation from the client PC. If the client PC 230a cannot be acquired even once, or if a predetermined period of time has not elapsed since the periodic activation notification cannot be acquired, it is determined that the client PC 230a no longer uses the application software due to a failure or other reason. In this case, the license management server 210 deletes the client PC 230a from the activation PCID column in the license management table of FIG. 7 (in the case of FIG. 7a) or updates the table by subtracting one from the simultaneous activation number (in the case of FIG. 7b). Then, the application software can be used by another client PC. Thereafter, when there is an activation license request from another client PC (for example, client PC 230b), an activation license is separately given to the client PC 230b with reference to the license management table. Thus, by appropriately releasing the activation license of the client terminal that has not been reported for a predetermined period, it is possible to eliminate the situation where the simultaneous activation license reaches a constant and deadlocks.

(3) Processing flow when a failure occurs when an application is already activated FIG. 28 shows that an activation license is granted by the license permission flow shown in FIG. 13, for example, and the application software has already been activated on the client PC 230. In the state, a processing flow when a failure or maintenance of the license management server 210 or an Internet connection failure occurs is shown. As a premise, the activation license is granted by a normal procedure, and the application software is being used in the client PC 230 (d1). The application software or client PC 230 periodically reports the use of the application to the license management server 210 (d2). The license management server 210 accumulates this in the alive monitoring management table of FIG. 14 and performs alive monitoring of the application software in each client PC 230. If the response of the license management server 210 to the periodic report is not obtained for a predetermined period at any time (d3), the client PC 230 checks whether the maintenance information of the license management server 210 can be acquired (d4). As described above, if the maintenance management notice is received in advance from the license management server 210 side, the registration location in the own PC is referred to, or an authentication server (not shown) in front of the maintenance management server 210 is referred to. This is done by inquiring maintenance information.

  If the information that the license management server 210 is currently under maintenance can be acquired (d5: Y), the date and time and the information that the server maintenance is in progress are recorded in the failure management table (FIG. 17) of the client PC 230 (d10). ). If maintenance information cannot be acquired (d5: N), an Internet access check is performed (d6). If the Internet access is normal (d7), a failure occurrence of the license management server 210 is recorded in the failure management table. (D9). When Internet access is impossible, the occurrence of communication failure is recorded in the failure management table (d8). In either case, the failure event and date / time are only recorded in the failure management table, and the application software that has already been started wants to continue using the software on its own without going to a special offline operation mode. As long as the use is completed (d11). Attempts to report to the license management server 210 are continued periodically, and when communication with the server 210 returns to normal, the contents of the failure management table (FIG. 17) are reported to the server 210. In this way, even when a failure occurs when the application software is used based on the activation license granted during normal operation, the application software can be continuously used in the client PC 230, so that the user's It will be convenient.

  A further embodiment of the present invention will be described with reference to FIGS. In this embodiment, the floating license in Embodiments 1 and 2 described above is an operation mode that secures the right to occupy and preferentially use the application software such as a PC dedicated to the director of the accounting office. is there. FIG. 29 is a diagram illustrating an example of a contract information table registered in the license management server 10 and / or the in-office server 20 and the client PC 30 according to the first embodiment. The same processing can be performed in the license management server 210 or the client PC 230 in FIG. 23 in the second embodiment. However, in the following description, for simplification of description, the reference numerals of the respective devices in the first embodiment are used. explain. This contract information table is provided with an exclusive use column in addition to the contents of the contract information table shown in FIG. 6. This exclusive use column is a setting flag and the PCID of the terminal for which the exclusive use right is set (see FIG. 9). Is registered. The setting flag is a flag indicating whether the exclusive use right is valid / invalid. If the flag is valid, another client terminal corresponding to the set number of terminals for the exclusive use right set in the contracted simultaneous activation license. Allocation to 30 is limited. The reason why the setting flag is provided here is to release the exclusive use right so that other terminals can use the application software when, for example, the user of the set terminal is on vacation. . The concept of the exclusive use right of the present embodiment can be applied to both the first and second embodiments. Since license management for each client terminal is required in this embodiment, the license management table shown in FIG. 7A is used.

  The exclusive use right is set by applying to the license management server 10 from the client terminal 30 or the in-office server 20 in advance. This application can be made, for example, by calling a setting screen, and the application includes at least the PCID of the terminal for which exclusive use is set. Upon receiving this application, the license management server 10 registers the PCID in the exclusive use column of the contract information table in FIG. 29, and turns on the exclusive use flag by default.

  The management of the floating license is almost the same as in FIG. 13 or FIG. 15, but in the simultaneous activation license check process in step b8, the license management server 10 has registered the PCID of the terminal requesting the license in the exclusive use column. In this case, the activation license is always issued, and the license management table in FIG. 7 is updated. If the PCID of the terminal related to the request for the activation license is not registered in the exclusive use column, the set number and flag of the exclusive use right, the number of simultaneous activation licenses are acquired from the contract information table, and then the number of simultaneous activation licenses is acquired. Referring to the license management table, after excluding the number of simultaneous activation licenses with exclusive use rights, if there are more concurrent activation licenses, the activation license is granted and the license management table is updated. In this way, a license is always secured for a terminal for which exclusive use is set among simultaneous activation licenses, and for example, the manager of an accounting office or the like is ready to use application software at any time.

  Further, the client terminal 30 may be configured to set the grasp of the current application use terminal in the office, the release request for the activation license, the release of the exclusive use right, and the like. FIG. 30 is a diagram illustrating an example of a management screen displayed on the monitor screen of the client terminal 30 or a web page served by the in-office server or the license management server. The management screen shown in FIG. 30 includes a floating startup status overview window 41 that reflects the number of installed licenses / simultaneous startup licenses for each application software and a summary of the number of installed / started licenses, and startup status in the office. Floating license activation status detail window 42 showing details of the license, exclusive use release button 43 when the exclusive use right is set for the terminal that displays the management screen, and activation that stops the active state of any active terminal A right release button 44. This screen can be configured to be called arbitrarily by pressing a dedicated icon or a button on the application. For example, when the application software is started up, all simultaneous activation licenses are used and the activation license is rejected. It may be displayed automatically.

  The floating license activation status overview window 41 acquires the contents of the contract information table (FIG. 29) and the license management table (FIG. 7A) at that time from the license management server 10, for example, by the client terminal 30. The contracted application software name, license ID (corresponding to the application ID in FIG. 10), the number of installed licenses, the number of installed PCIDs, the number of simultaneously activated licenses, and the number of simultaneously activated PCIDs are displayed side by side. The floating license orbit status detail window 42 further acquires the contents of the client PC information management table (FIG. 23), and determines the expiration date, whether there is an exclusive use right, whether the application software and the client terminal are running, A column indicating whether the activation license has been released is displayed side by side.

  When the client terminal 30 displaying this management screen has the exclusive use right, that is, when the PCID is registered in the exclusive use column of the contract information table in FIG. 29, the exclusive use release button 43 is displayed actively. Is done. As described above, this terminal can be used exclusively by application software, that is, a simultaneous activation license is always secured. For example, if this terminal malfunctions, or if you take the terminal out to travel to a consultant or customer, take it home, and use it for purposes other than using the app, or if the user takes a vacation, etc. When the exclusive use release button 43 is pressed when not used, an exclusive release application is transmitted to the license management server 10 after a confirmation screen although it is not essential. Here, if the terminal for exclusive use breaks down, access the web page served by the in-office server or the license management server from another terminal, display the management screen of FIG. You may make it transmit. The license management server 10 switches the exclusive use flag in the contract information table in FIG. 29 to OFF. As a result, the exclusive use right of the client terminal is temporarily released, and an activation license is granted to another terminal as necessary. When the exclusive use is released, the button 43 is displayed as “Start exclusive use”. For example, when the terminal 43 is repaired or when the user returns from vacation, the user presses the button 43 again to occupy the license management server 10. The usage application is sent, and the exclusive use flag in the contract information table is turned ON again.

  In addition, for example, when a terminal that already uses application software is defective, or when the terminal is taken out and traveled to a consultant or customer, or the terminal is taken home to use it for purposes other than using the application Alternatively, when the user of one of the terminals is away for a lunch break or the like, the activation license can be released by designating a specific client terminal. For example, when one of the licenses in the floating license activation information detail window 42 on the screen of FIG. 30 is highlighted and the activation right release button 44 is pressed, this is notified to the license management server 10, and the server 10 is included in the notification. A license is identified and released from the PC ID and application ID. This is returned to the client terminal 30 and displayed in the activation right release column of the floating license activation status detail window 42. As a result, other client terminals can acquire the activation license. In this case, it is possible to control the release of the activation right by using either one of the monitor screen of the client PC 30 or the management screen displayed on the web page serviced by the in-office server or the license management server, or using a plurality of screens. You may do it. In one embodiment, it may be possible to prevent the inconvenience that the activation right of a terminal that has been registered for exclusive use in advance cannot be released so that it cannot be activated on an important terminal. For example, a confirmation screen may be displayed on the client terminal that has lost the activation license even though it is being used, and the application software may be forcibly terminated after giving an opportunity to save data.

  Furthermore, according to the floating license activation information detail window 42 as shown in FIG. 30, the terminal user who has rejected the activation request of the application because the other terminal user has used up all the activation licenses of the application. , Managers such as office managers, how many concurrent activation licenses are secured for which applications in the office, how many concurrent activation licenses are used, whether there is a free activation license, or It can be used to check whether the simultaneous activation license of the desired application has been released or to wait, or to inquire the user of the terminal using the application software about the future use schedule.

  Alternatively, if there is no available activation license for the application to be used, it can be preferentially used when the number of simultaneous activations is available by providing a separate reservation button on the display screen of FIG. You may do it.

  According to the present invention described above, by introducing various complex and hierarchical license concepts such as an installation license or a simultaneous activation license provided below the software license, various offices ( Floating license management corresponding to the characteristics of companies, accounting firms, etc. and various software systems can be easily performed without assigning a specialist in charge to the office side.

  In addition, various license concepts that make up software licenses, for example, installation licenses are configured separately from simultaneous activation licenses, such as multiple or hierarchical license concepts. When you want to use the app after automatically storing the latest application program on a given terminal, perform management so that the latest app can be used immediately within the scope of the simultaneous activation license. be able to. Thereby, like a business application in the tax accounting field, it is particularly suitable for an application that needs to be frequently updated due to a tax system revision or a revision of accounting standards.

  Also, in the management of floating licenses, if a WAN line (external network) such as the Internet is used without any ingenuity between the license management server and the client PC to which the license is granted, the license management server In the case of maintenance or failure of the system, or maintenance or failure of the external network, there may be a problem that the floating license cannot be properly assigned or managed. By migrating, you can continue to manage and issue floating licenses.

  In this way, we have provided a mechanism for managing floating licenses safely and appropriately, so by introducing only a minimum number of licenses and making them available on multiple terminals in the office, while reducing costs for users, Providing an opportunity to introduce additional licenses by allowing multiple persons in charge to experience ease of use, etc. using application software, and practice usage in a so-called trial form. Can do.

  In addition, as a result of attracting the purchase of additional licenses, it is possible to provide an opportunity to improve the work efficiency of the entire office.

  The present invention can be used in a floating license service system that distributes a license of an application program and uses the required number of application programs for a predetermined period.

10, 210 License management server 20, 220 Office server 30, 230 Client PC
11, 21, 31 Control unit 12, 22, 32 Storage unit 13, 23, 33 Communication unit 41 Floating activation status overview window 42 Floating license activation status details window 43 Exclusive use release button 44 Activation right release button 100, 200 Software management system

Claims (6)

A software usage control system for managing license usage of application software in one or more client PCs on a user side, comprising: a license management server connected to the client PC directly or via a communication server in the office on the user side. , The license management server
Storage means for storing at least a contract information table in which the contents of the license contract for each user are registered, and a license management table in which the usage status of the license for each user is registered;
License management means for referring to the contract information table and the license management table to perform license management of application software in an individual client PC,
In the contract information table, a software license that each user concludes with a right to use specific application software, an installation license that defines how many client PCs the user can install the application software for each user, The number and period of simultaneous activation licenses that determine how many of the installed client PCs can use the application software at the same time are registered,
The license management means includes:
(1) When receiving an application software installation request directly from the client PC or via the user's office server, the presence / absence of the software license and the validity period, the number of installed licenses, and the validity of each Check the period and the number of installation licenses currently in use, and if the number of installation licenses currently in use is less than the number of valid installation licenses, grant a new installation license,
(2) At the time of receiving the application software activation request directly from the client PC or via the user's office server, at least the number and validity period of the concurrent activation license and the concurrent activation currently used A software usage control system characterized by confirming the number of licenses and granting a new simultaneous activation license when the number of currently activated simultaneous activation licenses is less than the number of valid simultaneous activation licenses. The software usage control system according to claim 1, wherein the contract information table further includes an exclusive use column that defines a simultaneous activation license reserved for a predetermined client PC among the simultaneous activation licenses,
When receiving a request for starting the application software, the license management unit extracts the number of the simultaneous activation licenses excluding those reserved for the predetermined client PC as the number of effective simultaneous activation licenses. A software usage control system, wherein a new simultaneous activation license is newly granted when the number of currently activated simultaneous activation licenses is less than the number of valid simultaneous activation licenses. The software use control system according to claim 1 or 2, wherein the system includes the client PC and / or the office server.
When the client PC and / or the in-office server detects a connection failure with the license management server when requesting the simultaneous activation license,
(A) When the access to the communication network is not possible, the application software can be activated only for a first period;
(B) When the access to the communication network is possible and maintenance information of the license management server cannot be acquired, the application software can be activated only for a second period;
(C) A software usage control system capable of starting the application software without any time limit when the communication network is accessible and maintenance information of the license management server can be acquired.   4. The software usage control system according to claim 1, wherein the client PC acquires and displays contract information and license usage status for the user among registration contents of the storage means of the license management server. A software usage control system comprising means.   5. The software use control system according to claim 4, wherein the client PC further designates a predetermined client PC to release the simultaneous activation license, or is reserved for the predetermined client PC among the simultaneous activation licenses. A software usage control system comprising license release request means for requesting the license management server to release a simultaneous activation license. 2. The software use control system according to claim 1, further comprising an in-office server disposed on the user side and connected to the one or more client PCs on the user side and the license management server.
Storage means for storing at least an in-office server contract information table in which the contents of a license contract related to the user are registered, and an in-office server license management table in which the license usage status in each client PC is registered;
In-office server license management means for managing licenses of application software in individual client PCs,
In the in-office server contract information table, among the license management server contract information table, the installation license for the user and the number and period of the simultaneous activation license for the user are registered,
The office server license management means includes:
(1) When an installation request for the application software is received from the client PC, the number of installation licenses and their valid periods and the number of currently used installation licenses are confirmed, and the currently used installation is confirmed. If the number of licenses is less than the number of valid installation licenses, a new installation license is granted,
(2) Upon receiving a request for starting the application software from the client PC, check at least the number and validity period of the concurrent activation license and the number of concurrent activation licenses currently used, A software usage control system, wherein a new simultaneous activation license is newly granted when the number of simultaneous activation licenses is less than the number of valid simultaneous activation licenses.