JP2009163480A - License management device, license management method, license management program, and license management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a license management device which facilitates management of a license for a user by presenting a candidate of a device which allows a user to continue use of a license beforehand. <P>SOLUTION: The license management device comprises steps of: judging whether there is a license having expiration date of license less than a predetermined period (step S4); checking the remaining number of licenses when the expiration date of the license has expired when it is judged there is the license having expiration date less than the predetermined period (step S5); comparing the number of license use with the remaining number of licenses when expiration date of the license has expired (step S7); judging next whether there is a setting of use candidate of the license when the number of license use is over the remaining numbers of licenses when expiration date of license of has expired (step S8); and executing a setting process of the license use candidate when there is no setting of use candidate of the license (step S9). <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a license management apparatus, a license management method, a license management program, and a license management system, and more particularly to software license management.

  For example, when using a specific application software (hereinafter also simply referred to as an application) in a terminal device connected via a network, the user uses the application provided by an application service provider (ASP), for example. It is necessary to purchase a license.

  A license is a right (license) to use purchased software. Usually, the use of one piece of software is permitted only to one terminal device.

Therefore, when a user wants to use a specific application in a plurality of terminal devices connected via a LAN in the company or the like, it is necessary to purchase a plurality of licenses as many as necessary. The user is allowed to use the application within the range of the number of licenses defined in the license agreement, and various license management methods have been proposed (Patent Document 1).
JP 2002-258967 A

  On the other hand, if some of the registered licenses become unusable in a license management environment that requires as many licenses as the number of terminal devices, some of the terminal devices that are permitted to use licenses. It is necessary to select which terminal device is prohibited from using the application, that is, out of license management, and it is necessary to select a terminal device to be out of management on the system managing the license, A terminal device not intended by the user may be out of license management, which is undesirable.

  In such a situation, the user may be at a loss as to which terminal device is out of license management or which terminal device should continue to use the license.

  The present invention has been made in order to solve the above-described problems, and makes it easy for a user to manage licenses by presenting candidate devices that allow the user to continue using the license in advance. An object of the present invention is to provide a license management apparatus, a license management method, a license management program, and a license management system.

  A license management device according to the present invention is a license management device that is connected to a plurality of terminal devices via a network and manages licenses when the plurality of terminal devices use a predetermined application. A managing unit that manages the expiration dates of a plurality of licenses of a predetermined application that can be used, a monitoring unit that monitors a terminal device that is permitted to use a license among the plurality of terminal devices, and a managing unit. Detection means for detecting a license whose expiration date is less than a predetermined period among a plurality of managed licenses, confirmation means for checking the number of remaining licenses excluding licenses detected by the detection means, and remaining The number of licenses and the number of terminal devices being monitored by the monitoring means If it is determined that the number of used licenses exceeds the number of remaining licenses based on the comparison results of the update license comparison unit and the update license comparison unit, among the plurality of terminal devices based on the device information of the plurality of terminal devices Candidate setting means for setting candidate terminal devices that are permitted to be used corresponding to the number of remaining licenses.

  Preferably, a registration unit for registering a terminal device that permits use of a license based on a plurality of licenses managed by the management unit among a plurality of terminal devices, and the number of effective licenses managed by the management unit and monitoring Valid license comparison means that compares the number of used terminal devices monitored by the means and the comparison result by the valid license comparison means. Update registration means for updating and registering terminal device candidates set by the candidate setting means based on the number of licenses as terminal devices that are permitted to be used.

  Preferably, the candidate setting means includes priority order execution means for performing prioritization out of license management of a plurality of terminal devices based on device information of the plurality of terminal devices.

  In particular, the candidate setting means is a candidate display instruction means for displaying a list of candidates for which use of licenses is permitted in accordance with the number of remaining licenses for a plurality of terminal devices that have been prioritized by the priority order execution means. Further included.

  In particular, the device information of the terminal device has a plurality of attribute information of the terminal device, and the priority order execution unit is selected by receiving selection input of at least one attribute information from the plurality of attribute information. Prioritize out of license management for a plurality of terminal devices based on the attribute information.

  A license management method according to another aspect of the present invention is a license management method that is connected to a plurality of terminal devices via a network and manages a license when the plurality of terminal devices use a predetermined application. A management step for managing each expiration date of a plurality of licenses of a predetermined application that can be used by the terminal device; a monitoring step for monitoring a terminal device that is permitted to use the license among the plurality of terminal devices; A detection step for detecting a license whose expiration date is less than a predetermined period among a plurality of licenses managed by the management means, and a confirmation step for confirming the number of remaining licenses excluding the license detected by the detection means among the plurality of licenses And the remaining number of licenses and the number of licenses monitored by the monitoring means. If it is determined that the number of used devices exceeds the number of remaining licenses based on the comparison result of the updated license comparing step and the updated license comparing step, the device information of a plurality of terminal devices A candidate setting step of setting terminal device candidates that are permitted to be used corresponding to the number of remaining licenses among the plurality of terminal devices.

  A license management program according to another aspect of the present invention is executed by a computer that controls a license management apparatus that is connected to a plurality of terminal apparatuses via a network and manages a license when the plurality of terminal apparatuses use a predetermined application. Management program for managing the expiration date of each of a plurality of licenses of a predetermined application that can be used by a plurality of terminal devices, and use of the license among the plurality of terminal devices is permitted. A monitoring step for monitoring a terminal device, a detection step for detecting a license whose expiration date is less than a predetermined period among a plurality of licenses managed by the management means, and a license detected by the detection means among the plurality of licenses Confirm the number of remaining licenses except for Update license comparison step that compares the number of licenses, the number of remaining licenses, and the number of used terminal devices monitored by the monitoring means, and the number of remaining licenses based on the comparison result of the update license comparison step When it is determined that the number exceeds the number, a candidate setting step of setting a candidate terminal device that is permitted to be used corresponding to the number of remaining licenses among the plurality of terminal devices based on the device information of the plurality of terminal devices is provided.

  A license management system according to still another aspect of the present invention is connected to a plurality of terminal devices that execute a predetermined application and a plurality of terminal devices via a network, and the plurality of terminal devices use a predetermined application. A license management apparatus for managing licenses. The license management device includes a management unit that manages the expiration dates of a plurality of licenses of a predetermined application that can be used by a plurality of terminal devices, and a terminal device that is permitted to use a license among the plurality of terminal devices. Monitoring means for monitoring the license, detection means for detecting a license whose expiration date is less than a predetermined period among a plurality of licenses managed by the management means, and remaining licenses excluding the license detected by the detection means among the plurality of licenses Based on the result of comparison by the update license comparison unit, the update license comparison unit that compares the number of licenses that are confirmed, the number of remaining licenses, and the number of terminal devices that are monitored by the monitoring unit, If it is determined that the number of licenses used exceeds the number of remaining licenses, the device information of multiple terminal devices Based on and a candidate setting means for setting a candidate of the terminal apparatus permitted to use corresponding to the remaining number of licenses among the plurality of terminal devices.

  The license management device according to the present invention, when it is determined that the number of used devices exceeds the remaining number of licenses based on the comparison result by the updated license comparison unit, the license management device of the plurality of terminal devices based on the device information of the plurality of terminal devices. Of these, candidate setting means for setting candidate terminal devices permitted to be used corresponding to the remaining number of licenses is included. In other words, by setting the license use candidate when the license expires before the license expires, the user can check the license registration status when the license expires in advance, which is convenient for the user. High and easy license management.

  Embodiments of the present invention will be described below with reference to the drawings. In the following description, the same parts and components are denoted by the same reference numerals. Their names and functions are also the same.

(Overall system configuration)
FIG. 1 is a schematic configuration diagram of a license management system according to an embodiment of the present invention.

  Referring to FIG. 1, a plurality of terminal devices 1A to 1E according to the embodiment of the present invention are connected to a LAN (Local Area Network) which is a network laid in the same office. Further, a server SRV connected to the Internet 5 that is an external network is connected to the LAN.

  Also, provision of a license registration server 10 for outputting license management information (to be described later) for permitting use of the application via the Internet 5 and an application service provider (ASP) that is a provider of the application software and license Servers 11 are connected to each other.

  In addition, a PC (Personal Computer) is connected to the LAN, and the user can connect to a plurality of terminal devices and server SRVs owned by the user who are connected via the network using the PC. Necessary access or the like can be executed.

  In the following, as an example, when a user requests use of a specific application for a plurality of terminal devices 1A to 1E owned by the user, the management of an application license provided by an application service provider (ASP) is performed. Will be described.

  The user accesses the providing server 11 using a PC connected to the LAN when requesting the use of an application for the plurality of terminal devices 1A to 1E owned by the user. Then, the user downloads from the providing server 11 and executes the charging process corresponding to the number of licenses corresponding to the number of applications of the terminal device with the providing server 11 using the PC. It is assumed that the server SRV functions as an application server (hereinafter also referred to as an application server SRV). At this time, a license management program for managing the license of the application is also provided from the providing server 11 to the server SRV and stored therein, and the server SRV executes the license management program via the CPU, thereby the license management apparatus. As well.

  In addition, the provision server 11 provides the user with license registration information for setting the license of the application along with the provision of the application.

  The user inputs the license registration information via the PC and transmits it to the application server SRV, so that the application server SRV executes the license management based on the license management program provided from the providing server 11. Issue a license key for. The user can receive the application service within the scope of the license contract based on the license key. In this example, it is assumed that the application can be used for the terminal devices 1A to 1E.

  The application server SRV outputs the license key issued based on the license registration information input by the user via the PC to the license registration server 10.

  Then, the license registration server 10 outputs, to the application server SRV, the manageable number of licenses of the terminal device corresponding to the number of purchased licenses and the expiration date of the license key in accordance with the license key issued in accordance with the charging process or the like. To do.

  The application server SRV permits the use of the application to the terminal device registered by the user based on the license management information including the number of licenses that can be managed and the expiration date of the license key output from the license registration server 10 according to the license management program. Manage licenses.

  Specifically, the application server SRV receives registration information of a terminal device that requests the use of an application from a user input via a PC in accordance with the license management program, and the license key is valid for the registered terminal device. Based on the expiration date, license management for using the application is executed.

  In the present embodiment, an MFP (Multi Function Peripheral), a printer device, and the like will be described as representative examples of the terminal devices 1A to 1E connected to the network. The terminal device according to the present invention may be a facsimile device, a scanner device, or the like, and is not particularly limited to its type. In this example, the terminal device 1A is assumed to be a high-function color MFP capable of high-speed printing and the like and capable of printing a color image. The terminal device 1B is a high-function monochrome MFP capable of high-speed printing or the like but capable of printing a monochrome image. The terminal device 1C is assumed to be a low-function color MFP capable of printing at a normal speed and printing a color image. The terminal device 1D is assumed to be a color printer device. The terminal device 1E is assumed to be a monochrome printer device. It is assumed that the number of functions of the MFP is greater than the number of functions that the printer device has because a FAX function, a scan function, and the like are installed.

  In addition, as a specific application, for example, a log management function for managing a history of using a print / copy / fax / scan function in an MFP or a printer, a user who can limit the function limit or the upper limit number of use for each user or each apparatus / Application management software that can execute each of a function for acquiring registered device error information and consumable information, a function for acquiring application setting change information for each device, and the like. In this example, a case where a plurality of functions can be executed for one application software will be described. However, the present invention is not particularly limited to this, and one function may be executed for one application software. Application software that performs other functions can be applied in the same manner.

  As an example, for example, when the log management function is executed as a specific application, history information using the print / copy / fax / scan function is managed and recorded by the application server SRV for the registered terminal device, and the user For example, by accessing the application server SRV via a PC, it is possible to easily obtain history information of a registered terminal device.

  In the above description, the application is downloaded from the providing server 11 via the network and stored in the server SRV. However, the present invention is not limited to this, and is stored in a CD-ROM or the like as package software. The application may be read and stored via a CD-ROM drive (to be described later) of the server SRV, and the means is not limited. In this case, the same operation as described above can be realized when the user inputs license registration information such as an encryption key presented as an accompanying package software on the CD-ROM.

  In this example, the case where the license registration server 10 and the providing server 11 are provided separately will be described. However, the providing server 11 may have the function of the license registration server 10. .

  In this example, as an example, the case where the application server SRV issues a license key for the application according to the license management program when the user inputs the license registration information via the PC and transmits it to the application server SRV will be described. However, the present invention is not limited to this. When the user exchanges necessary data with the providing server 11, the license is issued from the providing server 11 according to the license management program together with the application, and the above-described license management is performed. It is also possible to provide the information to the server SRV together with the information. In that case, it is also possible to realize license management without providing the license registration server 10. Alternatively, the license registration server 10 may issue a license for the application and provide it to the server SRV.

(Schematic configuration of MFP)
FIG. 2 is a block diagram illustrating a schematic configuration in MFP as terminal apparatuses 1A to 1C according to the embodiment of the present invention.

  2, MFP according to the embodiment of the present invention includes control unit 100, memory unit 102, image reading unit 104, fax transmission / reception unit 105, printing unit 106, communication interface unit 108, and data. Storage unit 110.

  The control unit 100 is typically composed of an arithmetic device such as a CPU (Central Processing Unit).

  The memory unit 102 is typically a volatile storage device such as a DRAM (Dynamic Random Access Memory), and holds a program executed by the control unit 100, data necessary for executing the program, and the like.

  The communication interface unit 108 is typically a part for transmitting / receiving data to / from a PC, application server SRV, etc. via a network (for example, LAN and Internet 5). For example, a LAN adapter and driver software for controlling the LAN adapter Including.

  The image reading unit 104 is a part for performing the scanner process, and includes a control device for controlling the operation of each unit in addition to the hardware configuration related to the scanner process.

  The fax transmission / reception unit 105 is a part for performing FAX transmission / reception processing, and includes a control device for controlling the operation of each unit in addition to the hardware configuration related to the FAX transmission / reception processing.

  The print unit 106 is a part for performing print processing, and includes a control device for controlling the operation of each unit in addition to the hardware configuration related to print processing.

  The data storage unit 110 is typically a non-volatile storage device such as a hard disk device or a flash memory.

  Note that the configuration of the printer device that is the terminal device 1D, 1E is a configuration in which the image reading unit 104 and the fax transmission / reception unit 105 in the configuration of FIG. 2 are not provided, and the other points are basically the same. The detailed description will not be repeated.

FIG. 3 is a block diagram illustrating a schematic configuration of the PC according to the embodiment of the present invention.
Referring to FIG. 3, a PC according to the embodiment of the present invention includes a CPU (Central Processing Unit) 201 that executes various programs including an operating system (OS), and data necessary for executing the programs of CPU 201. Are temporarily stored, and a hard disk unit (HDD: Hard Disk Drive) 211 that stores a program executed by the CPU 201 in a nonvolatile manner. Further, such a program is read from a flexible disk 217a or a CD-ROM (Compact Disc-Read Only Memory) 215a by the FTD drive 217 or the CD-ROM drive 215, respectively.

  The CPU 201 receives an instruction from the user via the input unit 209 including a keyboard and a mouse, and outputs a screen output generated by executing the program to the display unit 205. Further, the CPU 201 acquires necessary information from the terminal devices 1A to 1E connected to the LAN and the application server SRV connected via the network via the communication interface unit 207 including a LAN card or the like. The above-described units exchange data with each other via the internal bus 203. Further, the CPU 201 acquires information such as time and date from the clock 202.

  FIG. 4 is a block diagram illustrating a schematic configuration of application server SRV according to the embodiment of the present invention.

  Referring to FIG. 4, application server SRV according to the embodiment of the present invention includes a CPU 301, a memory unit 313, a hard disk unit 311, an input unit 309, a display unit 305, a communication interface unit 307, and an internal bus. 303, an FTD drive 317 for reading a flexible disk 317a, a CD-ROM drive 315 for reading a CD-ROM 315a, and a clock 302, which are basically the same as the configuration of the PC described in FIG. Description is omitted.

  The hard disk unit 311 stores a license management program for managing licenses of the application together with specific application software provided from the providing server 11, and the CPU 301 reads and executes these various programs, Various functions of the application server that provides the application service are realized. In this example, it is assumed that the license management function is executed by the CPU 301 reading and executing the license management program. In this example, a method for realizing the license management function by reading and executing software by the CPU 301 will be described. However, the present invention is not limited to software and can be configured by hardware.

  In this example, the CPU 301 reads and executes various programs, specifically, user authentication processing, license key issuance processing based on license registration information input by the user via the PC, and application provision processing. Various functions of the application server such as the license management process are executed. In this example, the license management process according to the license management program is mainly described, and a publicly known method is used for the other application server processes. Detailed description thereof will be omitted.

  In addition, it is assumed that the hard disk unit 311 records the addresses of the terminal devices 1A to 1E, which are clients registered in advance according to user input, the device ID indicating the device type of the terminal device, the license management history, and the like. . In addition, in the license management processing according to the license management program, it is assumed that data necessary for screen display on the display unit 305 of the user's PC is also stored as necessary.

  The basic configuration of the license registration server 10 and the providing server 11 is the same as that of the application server SRV.

  Although not shown, the hard disk unit of the license registration server 10 has a manageable number of terminal devices corresponding to the number of licenses purchased and the validity of the license key according to the license key issued from the application server SRV based on the license registration information. A program for outputting license management information including a time limit to the application server SRV is recorded, and various functions of the license registration server are realized by the CPU reading and executing the program.

FIG. 5 is a flowchart for explaining a license management process in the application server SRV.
Referring to FIG. 5, in step S1, CPU 301 determines whether there is a valid license purchased by the user (step S1). Specifically, the date information acquired via the clock 302 is confirmed, and the license management table stored in the HDD 311 is referred to and it is confirmed whether or not the managed license expiration date is within the expiration date. .

FIG. 6 is a diagram illustrating a license management table according to the embodiment of the present invention.
Referring to FIG. 6, in this example, as an example for using a specific application, a total of five licenses of three licenses LA, LB, LC and two licenses LD, LE are purchased by the user, and license management is performed. The case where the license management table is registered in the memory unit 313 according to the program is shown. Specifically, different license names are registered in the HDD 311 corresponding to the number of licenses purchased by the user based on the license management information output from the license registration server 10 in accordance with the license key, and corresponding to it. Thus, the license expiration date corresponding to the expiration date of the license key is registered.

  In this example, as an example, based on the license management information, three licenses of license name, license LA, LB, and LC, and the license expiration date are registered and managed as “2008/9/30”. Further, two licenses of license name, license LD, and LE based on different license management information and the license expiration date are registered and managed as “2008/1/31”. Note that a license whose expiration date has expired is deleted from the license management table of the HDD 311.

Here, it is assumed that the current date information is “2008/1/1”.
Therefore, in this case, the licenses LA, LB, LC, LD, and LE are all valid, and are all valid licenses. In this example, the case where the license management table is stored in the HDD 311 has been described, but it may be stored in the memory unit 313.

  Referring to FIG. 5 again, if it is determined in step S1 that there is no valid license, the process ends (END). This is because when the number of licenses is 0, use of the license cannot be permitted.

  Next, the CPU 301 confirms the number of licenses used (step S2). Specifically, referring to the license permission management table stored in the HDD 311 according to the license management program, the number of devices (license used number) that are the management targets of the license that is currently using the license is confirmed. .

FIG. 7 is a diagram illustrating a license permission management table according to the embodiment of the present invention.
Referring to FIG. 7, in this example, as an example, as a list of devices, devices 1A to 1E are registered in accordance with a user's input via, for example, a PC, and licenses are not permitted / managed according to devices 1A to 1E, respectively. It is recorded whether or not it is in the state. In this example, as an example, a case where the licenses of all the devices 1A to 1E are permitted is shown. Note that it is assumed that the licenses and the devices are not associated one-to-one, and the number of devices that use the license is associated with the number of valid licenses. In this example, the case where the license permission management table is stored in the HDD 311 has been described, but it may be stored in the memory unit 313.

  Referring to FIG. 5 again, next, the number of licenses used is compared with the number of valid licenses to determine whether the number of licenses used exceeds the number of valid licenses (step S3).

  In step S3, if the number of licenses used exceeds the number of valid licenses, the number of valid licenses is insufficient, so a license update setting process is executed (step S10). The license update setting process will be described later.

  On the other hand, if the number of licenses used does not exceed the number of valid licenses in step S3, the process proceeds to step S4.

  Next, in step S4, it is determined whether there is a license whose license expiration date is less than a predetermined period (step S4). For example, as an example, it is determined whether there is a license whose expiration date is less than one month. In this example, the determination is made on the basis of less than one month. However, the present invention is not limited to this, and can be freely adjusted as long as it is within the license expiration date.

  In step S4, when there is no license whose license expiration date is less than the predetermined period, the processing is ended (END). This is because it is not particularly necessary to change the license usage permission in the license management process.

  On the other hand, when it is determined in step S4 that there is a license whose license expiration date is less than the predetermined period, the number of remaining licenses when the license expiration date expires is confirmed (step S5).

  Next, it is determined whether the number of remaining licenses when the license expiration date has expired is greater than 0 (step S6). If the remaining number of licenses is 0, the process is terminated (END). This is because when the remaining number of licenses is 0, use of the license cannot be permitted.

  If the number of remaining licenses is not 0 in step S6, the number of licenses used is compared with the number of remaining licenses when the license expiration date has expired (step S7).

  In step S7, it is determined whether the number of licenses used exceeds the number of remaining licenses when the license expiration date has expired (step S7).

  If it is determined in step S7 that the number of licenses used does not exceed the number of remaining licenses when the expiration date of the license has expired, the process ends (END). This is because it is not particularly necessary to change the license usage permission in the license management process.

  On the other hand, if the number of licenses used exceeds the number of remaining licenses when the expiration date of the license has expired in step S7, it is then determined whether or not there is a license usage candidate setting (step S8). .

  In step S8, if there is a license use candidate setting, the process ends (END).

  On the other hand, if no license use candidate is set in step S8, a license use candidate setting process is executed (step S9).

  Considering the example described with reference to FIG. 6 above, since the license expiration dates of both the licenses LD and LE are “2008/1/31”, the current date information is “2008/1/1” in step S4. When compared with “1”, it corresponds to a license whose license expiration date is less than a predetermined period. Next, in step S5, when the number of remaining licenses when the license expiration date has expired is confirmed, the number of remaining licenses is “3”.

  Therefore, when the number of licenses used is compared with the number of remaining licenses in step S7, the number of licenses used exceeds the number of remaining licenses when the expiration date of the license has expired. Accordingly, the process proceeds to step S8, and if the license use candidate has not been set yet, the process proceeds to step S9.

  FIG. 8 is a flowchart illustrating execution of a license use candidate setting process according to the embodiment of the present invention.

  Referring to FIG. 8, first, the CPU 301 displays screen data for setting determination criteria for a device that is not managed by a license when a license use candidate setting process according to a license management program is executed. (Step S11).

  FIG. 9 is a diagram illustrating a determination criterion setting screen 400 displayed on the display unit 205 of the PC.

  Referring to FIG. 9, here, a case is shown in which determination criterion setting screen 400 is displayed on display unit 205 of the PC based on screen data in accordance with the license management program output from application server SRV.

  The user selects and inputs a candidate for a device that is not managed by the license when the license is expired by using a pointing device (not shown) included in the input unit 209 to select and input the determination criterion setting screen 400. It is possible to specify a determination criterion. Specifically, it is possible to select a candidate for a device that is not managed by a license based on a single criterion, and selectively add a criterion for a candidate for a device that is not managed by a license. It is also possible to select a plurality of determination criteria in combination. Alternatively, it is also possible to delete a determination criterion designated by a predetermined operation.

  In this example, as an example, in the display area 401 on the left side of the determination criterion setting screen 400, a list of candidate items for determination criteria for selecting candidate devices to be excluded from license management is displayed. In the display area 402 on the right side, items of designated determination criteria used for selecting a candidate for a device that is not managed by a license are displayed.

  Specifically, in the display area 401 on the left side, a candidate list of items of “usage frequency”, “manufacturing / support information”, “error information”, “consumables information”, and “application setting information” is displayed. Yes.

  In the display area 402, for example, the item “function” is displayed as a default as a criterion item specified by the user. The item “function” is merely an example, and other items may be displayed as defaults, or may be displayed as defaults with all items specified.

  In addition, in the determination criterion setting screen 400, an “add” button 303 and a “delete” button 304 are provided, and the item of the determination criterion selected by the cursor is selected by the “add” button 303, so that the right side It can be added to the display area 402. Alternatively, by selecting with the “delete” button 304, it is possible to delete from the right display area 402 and return to the left display area 401.

  Then, by pressing an “Ok” button 407 provided on the determination criterion setting screen 400, the selection result of the determination criterion item set by the user is transmitted from the PC to the application server SRV. On the other hand, pressing the “Cancel” button 406 cancels the setting of license use candidates.

  Further, a “detail” button 405 is provided on the determination criterion setting screen 400, and the user can set more detailed determination criteria for each item of the determination criterion by pressing the “detail” button 405. .

  FIG. 10 is a diagram for explaining a function information setting detail screen 420 displayed on the display unit 205 of the PC.

  Referring to FIG. 10, here, a case where a function information setting detail screen 420 is displayed on the display unit 205 of the PC based on screen data in accordance with the license management program output from the application server SRV is shown.

  When the “function” item is selected on the determination criterion setting screen 400 of FIG. 9 described above, by pressing the “detail” button 405, for example, the determination criterion for the “function” item is set in more detail. Can do.

  Referring to FIG. 10, here, in the function information setting detail screen 420, items such as “the number of installed options such as finisher”, “color mode”, “resolution”, and “printing speed” are respectively determined in the display area 422 on the right side. It is displayed as a standard item list. In the left display area 422, the item “number of functions” is displayed as a determination criterion selected as a default. Note that, even when the “Ok” button 407 is pressed without pressing the “Detail” button 405 on the determination criterion setting screen 400, what is transmitted to the application server SRV as an example when the item is selected. And In this example, the case where the item “number of functions” is selected as a default will be described. However, this is only an example, and other items may be selected as defaults, or all items may be specified. It is also possible to select the selected state.

  Also, in the function information setting detail screen 420, an “add” button 423 and a “delete” button 424 are provided similarly to the determination criterion setting screen 400, and the item of the determination criterion selected by the cursor is added to the “add” button. By selecting at 423, it is possible to add to the display area 422 on the right side. Alternatively, by selecting with the “delete” button 424, it is possible to delete from the right display area 422 and return to the left display area 421.

  Then, an “Ok” button 427 and a “Cancel” button 426 provided on the determination criterion setting screen 420 are provided. By pressing the “Ok” 427 button, the selection result of the determination criterion item set by the user is displayed. It is transmitted to the application server SRV. That is, in this example, the “number of functions” is selected as the determination criterion item and is transmitted to the application server SRV. On the other hand, when the “Cancel” button 426 is pressed, the screen returns to the determination criterion setting screen 400 which is the previous screen.

  In this example, the “function” item has been described, but the same applies to other items such as “usage frequency”.

FIG. 11 is a table for explaining the details of the determination criteria.
Referring to FIG. 11, devices that are not managed by the license for the items “function”, “usage frequency”, “manufacturing / support information”, “error information”, “consumables information”, and “application setting information” The contents of determination criteria for prioritizing for selecting candidates are shown. The user can freely select a criterion according to the user's preference from these item lists and select a candidate that is not managed by the license.

  Specifically, the item “function” can be classified into “number of functions”, “number of options such as finishers attached”, “color correspondence”, “resolution”, and “printing speed”.

  The “number of functions” is a criterion for executing “prioritization so that a device with a small number of functions (copy, print, scan, fax) is out of management”.

  “The number of options such as finishers attached” is a determination criterion for executing “prioritization so that those not equipped with finishers are not managed”.

  “Color correspondence” is a criterion for executing “prioritization so that monochrome machines are preferentially excluded from management”.

  “Resolution” is a determination criterion for executing “prioritization so that low resolution is not managed”.

  The “printing speed” is a determination criterion for executing “prioritization so that the one with a low printing speed is not managed”.

  As a determination criterion for the item “function”, prioritization is executed based on the device ID indicating the model type of each terminal device registered in the application server SRV. Specifically, the application server SRV corresponds to the device ID, the information table regarding “number of functions”, “number of options such as finishers installed”, “color correspondence”, “resolution”, “printing speed” of each terminal device. And prioritizing is performed by comparing each piece of information acquired from the information table with each terminal device. For example, in the case of “number of functions”, the device having the smallest “number of functions” is not managed by the license, the device having the highest priority is ranked “1”, and the order of “number of functions” is small. Prioritize rank “2” and rank “3” in ascending order.

  Then, it is possible to make the apparatus candidates out of license management in order from the smallest rank value.

  In addition, when the criterion is related to a combination of a plurality of items, the total value of those ranked by the above method is calculated, and the device candidates that are excluded from license management in order from the smallest rank value Is possible. The same applies to the following cases.

  The item of “usage frequency” can be classified into “thing with a small print count”, “number of users in use”, “number of registered users”, and “print processing (upper limit management) not yet reached”.

  “The one with a small print count” is a determination criterion for executing “prioritization so that one with a small print count is not managed”.

  The “number of users in use” is a determination criterion for executing “prioritization so that those with a small number of users who have used the device in the past month are excluded from management”.

  “Number of registered users” is a determination criterion for executing “prioritization so that a user with a small number of users registered in the apparatus is excluded from management”.

  “Print prohibition (upper limit management) not yet reached” is a determination criterion for executing “prioritization so that a print prohibition setting for upper limit management that has not been set in the past is excluded from management”.

  As a determination criterion for the item “usage frequency”, determination is performed based on history information recorded by the log management function stored in the application server SRV. Specifically, when executing the log management function as a specific application, the application server SRV, based on the history of using each device, “usage frequency” of each terminal device, “thing with a small print count”, Information relating to the “number of users in use” and “number of registered users” is acquired, and prioritization is performed by comparing the acquired information with each terminal device. For example, in the case of “usage frequency”, the device with the smallest “usage frequency” is ranked as “1” as the device with the highest priority of the device not to be managed by the license, and the order of the smallest “usage frequency”. In accordance with the above, rank “2” and rank “3” are given priority in ascending order.

  Then, it is possible to make the apparatus candidates out of license management in order from the smallest rank value.

  With respect to the determination criterion “printing prohibition (upper limit management) not reached”, determination is performed based on the upper limit management history information. Specifically, the application server SRV has an upper limit management function when executing a user / device management function as a specific application, specifically, when executing an upper limit management function for managing the upper limit of printing of each terminal device. The determination is executed based on the history information recorded by. As an example, prioritization is executed by setting a device that does not have history information that has executed the upper limit management function as a high-priority device that is out of license management.

  The item “manufacturing / support information” can be classified into “manufacturing time” and “guarantee period”.

  “Manufacturing time” is a determination criterion for executing “prioritization so as to make it out of control from the oldest manufacturing time”. The “guaranteed period” is a determination criterion for executing “prioritization so that a user / serviceman who has passed a guaranteed period is preferentially excluded from management”.

  As a criterion for determining the item “manufacturing time” of the “manufacturing / support information”, the determination is executed based on the serial number of the device registered in advance in the application server SRV by the user. Specifically, the manufacturing time is determined based on the server model information from the serial number and the like, and prioritization is performed as a high priority device that is out of license management for devices with an older manufacturing time.

  In addition, as a determination criterion for the item “guarantee period” of “manufacturing / support information”, the determination is executed based on the warranty period of the device registered by the user / serviceman in the application server SRV. Specifically, prioritization is executed for a device that has passed the warranty period as a device with a high priority that is not managed by the license.

  “Error information” can be classified into “number of errors”, “number of serious errors”, and “error frequency trend”.

  The “number of errors” is a determination criterion for executing “prioritization so that those having a large number of errors in the past month are not managed”.

  The “number of serious errors” is a determination criterion for executing “prioritization so that those with a large number of occurrences of serious errors in the past month are excluded from management”.

  “Error frequency trend” is a determination criterion for executing “prioritization so that the number of errors in the past three months is higher than the previous error frequency is out of management”.

  As a determination criterion for the item “error information”, determination is performed based on the history information of the apparatus. Specifically, when executing the error information acquisition function as a specific application, the application server SRV executes determination based on the history information acquired and recorded by executing the error information acquisition function. Specifically, the application server SRV acquires error history information stored as history information in each terminal device, and performs determination based on the error history information. Specifically, the application server SRV acquires information on the “number of errors” and the “number of serious errors” included in the error history information for the past month, compares the acquired information with each terminal device, Prioritization is executed as a high-priority device that makes a device with a large number of times out of license management. The “error frequency trend” is an error frequency calculated for each device based on error history information for the past three months, and is higher than the error frequency calculated before that. A device is prioritized as a high-priority device that is out of license management.

  The “consumable information” can be classified into “remaining toner amount” and “imaging unit use count”.

  The “toner remaining amount” is a determination criterion for executing “prioritization so that toner with a small amount of toner remaining is out of management”.

  “Imaging unit usage count” is a determination criterion for executing “prioritization so that those with a large number of imaging unit usage counts are not managed”.

  As a determination criterion for the item “consumable information”, the determination is performed based on the consumable information of each device. Specifically, when executing the consumable information acquisition function as a specific application, the application server SRV makes a determination based on the consumable information in each device acquired and recorded by executing the consumable information acquisition function. Execute. Acquire and record toner remaining amount information or imaging unit usage count information for each terminal device, and the application server SRV compares the toner remaining amount information for each terminal device, and manages licenses for those with less toner remaining Prioritization is performed as a device with high priority that is outside. Alternatively, prioritization is executed as a high-priority device that does not manage licenses that are frequently used imaging units.

  The “application setting information” is a determination criterion for executing “prioritization so as to preferentially exclude those devices whose settings related to the device are changed from the default in the application”.

  As a determination criterion for the item “application setting information”, determination is performed based on application setting update information of each device. Specifically, when executing the function of acquiring the application setting change information for each device as a specific application, the application server SRV performs the determination based on the application change information from the default for each device. Specifically, the number of application changes is compared for each terminal device, and prioritization is executed as a high-priority device that does not manage licenses that have a small number changed from the default.

  Referring again to FIG. 8, in step S12, a determination criterion setting input for selecting a candidate device to be excluded from license management is received (step S12).

Then, it is determined whether there is an input for setting a determination criterion (step S13).
If it is determined in step S13 that a determination criterion has been input, the process proceeds to the next step S14. On the other hand, when there is no determination criterion setting input, for example, when the user presses the “Cancel” button 406, the setting of license use candidates is stopped.

  In step S14, prioritization of devices is executed according to the above-described determination criteria (step S14).

  Next, the CPU 301 outputs selection screen data of a device that permits use of the license and a device that is not managed by the license according to the priority order to the PC on the user side (step S15).

  For example, to explain using the above example, consider a case where the item “number of functions” is set and input as a criterion. As described above, the terminal devices 1A to 1C are MFPs having a large number of functions, and the terminal devices 1D and 1E are color printer devices having a relatively small number of functions.

  In this case, by setting and inputting the above item “number of functions” as a judgment criterion, prioritize each device so that those with a small number of functions (copy, print, scan, fax) are not managed. The terminal devices 1D and 1E, which are printer devices having a small number of functions, are ranked higher as terminal devices that are not managed.

  FIG. 12 is a diagram for explaining a candidate screen 500 showing a list of candidates for devices that are permitted to use licenses and devices that are not managed by licenses.

  Referring to FIG. 12, here, a case where a candidate screen 500 is displayed on the display unit 205 of the PC based on the screen data output from the application server SRV is shown.

  Specifically, on the candidate screen 500, a list of device candidates that are permitted to use licenses is shown on the left side, and a list of device candidates that are not managed by licenses are shown on the right side.

  In this example, when the above example is used, as an example, devices 1A to 1C, which are MFPs having a large number of functions, are shown as a list of device candidates that are permitted to use licenses. The terminal devices 1D and 1E, which are printer devices having a relatively small number of functions, are shown as a list of device candidates. In this example, a case has been described in which both a device candidate list that permits use of a license and a device candidate list that is not managed by a license are displayed. However, at least one of them may be displayed. Is possible.

  Referring to FIG. 8 again, it is determined whether or not “Ok” has been input for the selection display of the device candidate permitted to use the license and the device candidate to be excluded from the license management (step S16). In step S16, when there is an input indicating that “Ok” is selected in the selection of a device candidate that is permitted to use a license and a device candidate that is not managed by the license, that is, the “Ok” button 501 is pressed on the screen of FIG. If so, the devices listed in the list of device candidates that are permitted to use the license are set as license use candidates (step S17). Then, the process ends (END).

  On the other hand, in step S16, when “Ok” is not input for the selection display of the device candidates that are permitted to use the license and the device candidates that are not managed by the license, that is, the “Cancel” button 502 is pressed in FIG. In such a case, it is assumed that the process returns to step S11 and the determination criterion setting screen data of the apparatus not to be managed by the license is output again.

  That is, when the user determines that the device candidate list display is not appropriate by viewing the list display of the device candidates, the user can select and display the desired device by using another determination criterion on the determination criterion setting screen again. It can be adjusted to be a candidate. In this example, a description will be given of a method of executing selection display of device candidates using another determination criterion again when the “Cancel” button 502 is pressed. If it is determined that the device candidate list is not appropriate by viewing the displayed list of device candidates, the pointing device or the like is directly operated so that the device candidate list becomes a user-desired list so that the device candidates are appropriately set. Anyway.

Next, a license update setting process according to the license management program will be described.
In step S3 of FIG. 5, the number of licenses used is compared with the number of valid licenses to determine whether the number of licenses used exceeds the number of valid licenses (step S3). If it exceeds, the number of valid licenses is insufficient, so the license update setting process is executed (step S10).

FIG. 13 is a flowchart for executing a license update setting process.
Referring to FIG. 13, first, it is determined whether there is a setting of license use candidates corresponding to the number of valid licenses (step S21).

  In step S21, if there is a license use candidate setting corresponding to the number of valid licenses, the license permission management table is updated based on the set license use candidate (step S23). And it ends.

  On the other hand, in step S21, if there is no license use candidate setting corresponding to the number of valid licenses, the apparatus prioritization is performed according to the determination criteria defined by default as described in step S14 of FIG. Execute (Step S22). Thereby, for example, when there is no license use candidate setting, for example, the item “number of functions” is used as a default determination criterion, and the above-described device prioritization is executed using the determination criterion. License usage candidates are set according to the prioritization of the devices.

  In step S22, the license permission management table is updated based on the set license use candidates. And it ends.

  For example, to explain using the example of FIG. 6, consider the case where the current date information is “2008/2/1”.

  In this case, referring again to FIG. 5, in step S1, valid licenses are licenses LA, LB, and LC. In step S2, the number of licenses used is confirmed, and in step S3, the number of licenses used and the valid licenses are checked. The number of licenses used is compared with the number of valid licenses. In step S3, since the number of licenses used exceeds the number of valid licenses, the process proceeds to step S10.

  If the license use candidate described with reference to FIG. 11 is set, the process proceeds to step S21 and step S23 in the license update setting process of FIG.

FIG. 14 is a diagram for explaining another example of the license permission management table.
Referring to FIG. 14, here, the license permission management table in the case where the license use candidate is set in FIG. 11 is updated. Specifically, in FIG. 11, candidates are listed as a list of devices that the devices 1 </ b> A to 1 </ b> C permit to use licenses, and when the user sets the candidates, the license permission management table is updated. That is, the devices 1D and 1E are set and registered outside the license management.

  For example, when the log management function is used as a specific application, since the device 1D and device 1E are terminal devices that are not permitted to use licenses, the history information about the devices 1D and 1E is stored in the application server SRV. The history information using the print / copy / fax / scan function is recorded in the application server SRV for the devices 1A to 1C without being recorded. When the devices 1D and 1E are set and registered out of license management, for example, when the user accesses the application server SRV, it is also possible to notify that fact. Alternatively, it is possible to notify the user's PC to that effect by e-mail or the like. Alternatively, it is possible to notify the corresponding terminal device of the same content.

  If license use candidates are not set, license use candidates are set according to device prioritization according to default determination criteria, and the license permission management table is updated. If the license is registered outside the license management, the registration can be changed.

  Therefore, by using the license management method according to the present embodiment, in the license management environment where licenses are required for the number of terminal devices, some of the registered licenses cannot be used, and the number of licenses used In a situation where the number of licenses exceeds the number of valid licenses, it is possible to allow the user to select device candidates that are permitted to use the license in advance. At that time, by presenting candidates that are permitted to use the license and candidates that are not managed by the license using the determination criteria according to the user's preference among the plurality of determination criteria, by setting the candidates in advance Even if some licenses become unusable, it is possible to maintain licenses for terminal devices set as candidates for permitting use of licenses that the user desires in advance. It is easy and the convenience of the user can be improved.

  In the above description, the application server SRV functions as the application server SRV by storing the application or the like in the server SRV, and the license is managed. However, the providing server 11 functions as the application server described above and is provided. It is also possible for the server 11 to manage the license of the application.

  In addition, although the case where a computer is made to function and the program which performs control as demonstrated in the above-mentioned flow was provided was demonstrated, such a program is a flexible disk attached to a computer, CD-ROM (Compact Disk- The program can be provided by being recorded on a computer-readable recording medium such as a read only memory (ROM), a read only memory (ROM), a random access memory (RAM), and a memory card. Alternatively, the program can be provided by being recorded on a recording medium such as a hard disk built in the computer.

  The program according to the present invention is a program module that is provided as a part of a computer operating system (OS) and calls necessary modules in a predetermined arrangement at a predetermined timing to execute processing. Also good. In that case, the program itself does not include the module, and the process is executed in cooperation with the OS. A program that does not include such a module can also be included in the program according to the present invention.

  The program according to the present invention may be provided by being incorporated in a part of another program. Even in this case, the program itself does not include the module included in the other program, and the process is executed in cooperation with the other program. Such a program incorporated in another program can also be included in the program according to the present invention.

The provided program product is installed in a program storage unit such as a hard disk and executed. The program product includes the program itself and a recording medium on which the program is recorded.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

1 is a schematic configuration diagram of a license management system according to an embodiment of the present invention. FIG. 3 is a block diagram illustrating a schematic configuration in an MFP that is terminal apparatuses 1A to 1C according to an embodiment of the present invention. It is a block diagram illustrating a schematic configuration of a PC according to an embodiment of the present invention. It is a block diagram explaining schematic structure of application server SRV according to the embodiment of the present invention. It is a flowchart explaining the license management process in application server SRV. It is a figure explaining the license management table according to embodiment of this invention. It is a figure explaining the license permission management table according to an embodiment of the present invention. It is a flowchart explaining execution of the setting process of the use candidate of the license according to the embodiment of the present invention. It is a figure explaining the criteria setting screen 400 displayed on the display part 205 of PC. It is a figure explaining the function information setting detail screen 420 displayed on the display part 205 of PC. It is a table | surface explaining the detail of a criterion. It is a figure explaining the candidate screen 500 which shows the list | wrist of the candidate of the apparatus which permits use of a license, and the apparatus made out of license management. It is a flowchart which performs the setting process of a license update. It is a figure explaining another example of a license permission management table.

Explanation of symbols

  1A to 1E Terminal device, 5 Internet, 10 License management device, 100 Control unit, 102 Memory unit, 104 Image reading unit, 105 Fax transmission / reception unit, 106 Print unit, 108 Communication interface unit, 110 Data storage unit, 201, 301 CPU 202, 302 clock, 203, 303 Internal bus, 205, 305 Display unit, 207, 307 Communication interface unit, 209, 309 Input unit, 211, 311 Hard disk unit, 213, 313 Memory unit, 215, 315 CD-ROM drive 217, 317 FTD drive, 400 judgment criterion setting screen, 420 function information setting detail screen, 500 candidate screen.

Claims (8)

In a license management apparatus that is connected to a plurality of terminal devices via a network and manages a license when the plurality of terminal devices use a predetermined application,
Management means for managing the expiration dates of a plurality of licenses of the predetermined application that can be used by the plurality of terminal devices;
Monitoring means for monitoring a terminal device permitted to use the license among the plurality of terminal devices;
Detecting means for detecting a license whose expiration date is less than a predetermined period among the plurality of licenses managed by the managing means;
Confirmation means for confirming the number of remaining licenses excluding the license detected by the detection means among the plurality of licenses;
Update license comparing means for comparing the number of remaining licenses with the number of terminals used by the plurality of terminal devices monitored by the monitoring means;
When it is determined that the number of used devices exceeds the remaining number of licenses based on the comparison result by the updated license comparison unit, the remaining number of the plurality of terminal devices based on the device information of the plurality of terminal devices. A license management apparatus, comprising: candidate setting means for setting a candidate terminal apparatus that is permitted to be used corresponding to the number of licenses. Registration means for registering a terminal device that permits use of a license based on the plurality of licenses managed by the management means among the plurality of terminal devices;
Effective license comparison means for comparing the number of valid licenses managed by the management means with the number of used terminal devices monitored by the monitoring means;
When it is determined that the number of used devices exceeds the number of valid licenses based on the comparison result by the valid license comparison unit, the terminal device candidates set by the candidate setting unit based on the number of valid licenses The license management apparatus according to claim 1, further comprising update registration means for performing update registration as a terminal apparatus that permits use of the license management apparatus.   2. The license management apparatus according to claim 1, wherein the candidate setting means includes priority order execution means for performing prioritization out of license management of the plurality of terminal devices based on device information of the plurality of terminal devices. .   The candidate setting means is a candidate display for displaying a list of candidates permitted to use licenses in accordance with the number of remaining licenses for the plurality of terminal devices that have been prioritized by the priority order executing means. 4. The license management apparatus according to claim 3, further comprising an instruction unit. The device information of the terminal device has a plurality of attribute information of the terminal device,
The priority order execution means receives a selection input of at least one attribute information from the plurality of attribute information, and prioritizes out of license management of the plurality of terminal devices based on the selected attribute information The license management device according to claim 3, wherein: In a license management method for managing a license when connected to a plurality of terminal devices via a network and using the predetermined application by the plurality of terminal devices,
A management step of managing each expiration date of a plurality of licenses of the predetermined application that can be used by the plurality of terminal devices;
A monitoring step of monitoring a terminal device permitted to use the license among the plurality of terminal devices;
A detection step of detecting a license whose expiration date is less than a predetermined period among the plurality of licenses managed by the management means;
A confirmation step of confirming the number of remaining licenses excluding the license detected by the detection means among the plurality of licenses;
An updated license comparison step for comparing the number of remaining licenses with the number of used terminal devices monitored by the monitoring means;
When it is determined that the number of used devices exceeds the remaining number of licenses based on the comparison result of the updated license comparison step, the remaining number of the plurality of terminal devices based on the device information of the plurality of terminal devices. A candidate setting step of setting candidate terminal devices permitted to be used corresponding to the number of licenses. A license management program that is executable by a computer that is connected to a plurality of terminal devices via a network and controls a license management device that manages a license when the plurality of terminal devices use a predetermined application,
A management step of managing each expiration date of a plurality of licenses of the predetermined application that can be used by the plurality of terminal devices;
A monitoring step of monitoring a terminal device permitted to use the license among the plurality of terminal devices;
A detection step of detecting a license whose expiration date is less than a predetermined period among the plurality of licenses managed by the management means;
A confirmation step of confirming the number of remaining licenses excluding the license detected by the detection means among the plurality of licenses;
An updated license comparison step for comparing the number of remaining licenses with the number of used terminal devices monitored by the monitoring means;
When it is determined that the number of used devices exceeds the remaining number of licenses based on the comparison result of the updated license comparison step, the remaining number of the plurality of terminal devices based on the device information of the plurality of terminal devices. A license management program, comprising: a candidate setting step of setting terminal device candidates that are permitted to be used in accordance with the number of licenses. A plurality of terminal devices that execute a predetermined application;
A license management device that is connected to the plurality of terminal devices via a network and manages licenses when the plurality of terminal devices use a predetermined application;
The license management device includes:
Management means for managing the expiration dates of a plurality of licenses of the predetermined application that can be used by the plurality of terminal devices;
Monitoring means for monitoring a terminal device permitted to use the license among the plurality of terminal devices;
Detecting means for detecting a license whose expiration date is less than a predetermined period among the plurality of licenses managed by the managing means;
Confirmation means for confirming the number of remaining licenses excluding the license detected by the detection means among the plurality of licenses;
Update license comparing means for comparing the number of remaining licenses with the number of terminals used by the plurality of terminal devices monitored by the monitoring means;
When it is determined that the number of used devices exceeds the remaining number of licenses based on the comparison result by the updated license comparison unit, the remaining number of the plurality of terminal devices based on the device information of the plurality of terminal devices. A license setting system including candidate setting means for setting a candidate terminal device permitted to be used corresponding to the number of licenses.

Images