JP2018112990A - License server, license management method, program and system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a license management server capable of automatically updating a license by adjusting the update timings of the licenses of expanded functions used by a plurality of image formation apparatuses in a contract period agreed with a customer.SOLUTION: A license server includes: first management means which manages group information indicating the available period and update timing of a license; second management means which manages the groups to which applications belong in association with each other; and issuing means which issues the license to the application set with the available period on the basis of the group information to which the application belongs. In a case where the new application belongs to the existing group managed by the first management means, the license server issues the license so as to be updated at the most recent update timing indicated by the group information of the existing group in issuance of the first license to the new application.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a license server, a license management method, a program, and a system.

  The image forming apparatus is equipped with basic functions such as a copy function, a print function, and a scan function as standard, and may have an extended function as an option. In general, a user who wants to use such an extended function can use it by purchasing a product of the extended function. When purchasing products with extended functions, there are subscription models that allow users to use the functions only for the contract period by continuing to pay usage fees. For example, in Patent Document 1, data such as a period during which an extended function can be used and whether the extended function can be used continuously is held in a license necessary for using the extended function. As a result, when the extended function can be used continuously, a license in which a new usage period is set is acquired, and a method for continuously using the extended function is presented.

JP 2013-250997 A

  However, there are many users who use a plurality of image forming apparatuses, and there is a demand for matching the license update timings of the extended functions used in the respective image forming apparatuses. Patent Document 1 discloses an invention for easily realizing license update of an extended function, but it is considered that the license update timings of extended functions used in a plurality of image forming apparatuses in the same contract are matched. Not.

  The present invention solves this problem, and a license management mechanism capable of automatically renewing a license by matching the renewal times of licenses of extended functions used in a plurality of image forming apparatuses within a contract period concluded with a customer I will provide a. In addition, even when there are image forming apparatuses with different usage periods in the same contract, a mechanism for adjusting the license renewal time without stopping the use of the extended function is provided.

  In order to achieve the above object, the present invention comprises the following arrangement. That is, a license server that issues a license used when an application is operated, and for each group, manages the group information indicating the license validity period and the update timing for updating the license at a predetermined cycle. Based on the management means, the second management means for managing the application and the group to which the application belongs, the group to which the application belongs, and the group information of the group, a license for the application for which the valid period is set is obtained. An issuing means for issuing and a registration means for accepting registration of a new application, wherein the issuing means adds the new application registered by the registration means to an existing group managed by the first management means. Belong In this case, when the initial license is issued for the new application, regardless of the license validity period indicated by the group information of the existing group, at the latest update timing indicated by the group information of the existing group. Issue a license to be updated.

  According to the present invention, it is possible to automatically update the license at the same time as the update of the license of the extended function used in the image forming apparatus within the contract period concluded with the customer.

The figure which shows the example of the network structure which concerns on this invention. The figure which shows the example of the hardware constitutions which concern on this invention. The figure which shows the example of the software structure which concerns on this invention. The figure which shows the example of the screen which the license server which concerns on this invention provides. FIG. 4 is a diagram showing an example of a screen provided by the image forming apparatus according to the present invention. The figure which shows the example of the data structure of the file which concerns on this invention. The flowchart of the process performed in the utilization information registration request | requirement receiving part which concerns on this invention. The figure which shows the structural example of the table which concerns on this embodiment. The figure which shows the structural example of the table which concerns on this embodiment. The figure which shows the structural example of the table which concerns on this embodiment.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. First, define terms.

  The “application file” is a file that stores a program that is an extended function of the image forming apparatus. The application file is not stored in the image forming apparatus as a standard, and is stored in the hard disk of the image forming apparatus when the image forming apparatus receives an installation request together with a license, which will be described later, at the time of initial installation. In order to install and use application files, a license described later is required.

  The “license” is a file necessary for permitting the image forming apparatus to install the application file and use the application file. In the present invention, a license that updates and permits use of an application file in a period contracted with installation of the application file is defined as an update license.

  “Usage information” is information on a contract between a customer and a sales company. Information on the image forming apparatus purchased by the customer and information on how long the product is used in the purchased image forming apparatus are held. Note that the license server cannot issue an update license unless information for identifying the image forming apparatus is registered in the usage information. When information for identifying the image forming apparatus is registered in the usage information, the license server periodically issues an update license. The periodic license issuance will be described later.

<First Embodiment>
[System configuration]
FIG. 1 shows an example of a network configuration of a license management system to which the present invention is applied. The license server 101 is a server that can issue a license, and can communicate with various devices via the Internet 102. In the example of FIG. 1, the image forming apparatus 112 and the information processing apparatuses 111 and 121 are connected to the network one by one. However, the number is not limited to this number, and more apparatuses may be included.

  The customer network environment 110 is a network environment of a customer who has purchased the image forming apparatus 112. In a customer network environment 110, an image forming apparatus 112 and an information processing apparatus 111 are connected via a LAN (Local Area Network) 113. The LAN 113 can be connected to the Internet 102. The sales company network environment 120 is a network environment of a sales company that sells extended functions. In the sales company network environment 120, an information processing apparatus 121 and a contract server 122 are connected via a LAN 123. The LAN 123 can be connected to the Internet 102. In FIG. 1, one customer network environment 110 and one sales company network environment 120 are shown, but the present invention is not limited to this. For example, the customer network environment 110 may be provided according to the number of contracts. Further, although one license server 101 is shown, a configuration in which processing is performed in a distributed manner by a plurality of apparatuses may be employed.

[Hardware configuration]
FIG. 2 shows an example of the hardware configuration of a license management system to which the present invention is applied. FIG. 2A shows an example of the hardware configuration of the image forming apparatus 112. FIG. 2B shows an example of the hardware configuration of the information processing apparatuses 111 and 121, the contract server 122, and the license server 101.

  As shown in FIG. 2A, the image forming apparatus 112 according to the present invention includes a document feeding unit 201, an image reader 202, an image forming unit 203, a paper feeding unit 204, a network I / F (Interface) 205, and A sensor 206 is provided. The image forming apparatus 112 further includes a CPU 207, a hard disk 208, a nonvolatile memory 209, a volatile memory 210, a display unit 211, and an operation unit 212. Each part of the image forming apparatus 112 is connected to be communicable via a system bus 213.

  The document feeder 201 automatically feeds a document to be read to the image reader 202. An image reader 202 (for example, a scanner) reads a supplied document. The image forming unit 203 converts the read original and received data into a print image and prints it. The paper feeding unit 204 feeds printing paper. A network I / F 205 connects to the LAN 113 and the Internet 102 via a network and exchanges information with the outside. The sensor 206 detects the state of each part of the image forming apparatus 112. The CPU 207 manages each process on the image forming apparatus 112. The hard disk 208 stores programs and data related to each process of the image forming apparatus 112. The nonvolatile memory 209 is a rewritable memory that can hold a memory without supplying power, and is, for example, a FRAM (Ferroelectric Random Access Memory). The volatile memory 210 is a memory that can electrically store and rewrite temporary data related to each process of the image forming apparatus 112. The display unit 211 displays information related to the operation status of the image forming apparatus 112 and operations on the operation unit 212. The operation unit 212 receives an instruction input to the image forming apparatus 112.

  As shown in FIG. 2B, the information processing apparatuses 111 and 121, the contract server 122, and the license server 101 according to this embodiment include a display unit 221, an operation unit 222, a CPU 223, a hard disk 224, a volatile memory 225, and A network I / F 226 is provided. Each part is communicably connected via a system bus 227. The display unit 221 displays windows, icons, messages, menus, and other user interface information. The operation unit 222 receives input from an end user using a keyboard and a mouse. The CPU 223 manages each process on this apparatus. The hard disk 224 stores programs and data related to each process of the apparatus. The volatile memory 225 is a memory that can electrically store and rewrite temporary data related to each process of the apparatus. The network I / F 226 is connected to the LANs 113 and 123 and the Internet 102 via the network, and exchanges information with the outside.

  The configuration shown in FIG. 2 is an example, and other parts may be provided. In addition, the information processing apparatus according to the present embodiment is not limited to the configuration illustrated in FIG. 2B, and may be configured different for each apparatus.

Software configuration
FIG. 3 shows an example of the software configuration of the license management system to which the present invention is applied. FIG. 3A shows an example of the software configuration of the license server 101. FIG. 3B shows an example of the software configuration of the image forming apparatus 112. In addition, FIG. 8 to FIG. 10 show configuration examples of various tables according to the present embodiment.

(License server)
Each part of the software of the license server 101 shown in FIG. 3A is executed when the CPU 223 loads the program stored in the hard disk 224 onto the volatile memory 225 in the license server 101. Also, the tables shown in FIGS. 8 and 9 included in the license server 101 are held in each memory and hard disk, and are read and updated.

  The application information holding unit 311 is means for holding the application information table on the hard disk 224 of the license server 101. FIG. 8A shows an example of the application information table 800 stored in the application information holding unit 311.

  In the application information table 800, an application ID column 801 is a column that stores an application ID that is an identifier for uniquely identifying the type of application file. The application version column 802 is a column for storing the version of the application file. An application file can be uniquely identified by an application ID and an application version. An application name column 803 is a column for storing an application name. A file path column 804 is a column for storing a path for storing an application file. Each record of the application information table 800 is referred to as an “application information record”, and is registered in the application information table 800 in units of applications. The application information record is added when the application information registration request receiving unit 321 receives the application information registration request.

  The product information holding unit 312 is a means for holding a product information table for holding product information in the hard disk 224 of the license server 101. A product is a unit for selling an application file, and a customer purchases a product in units of product information. FIG. 8B shows an example of a product information table 810 stored in the product information holding unit 312.

  In the product information table 810, a product ID column 811 is a column that stores a product ID that is an identifier for uniquely identifying a product. The product name column 812 is a column for storing product names. The application ID column 813 is a column for storing the application ID of an application file that can be used by purchasing this product. Each record of the product information table 810 is referred to as a “product information record” and is registered in the product information table 810 in units of products. The product information record is added when the product information registration request receiving unit 322 receives the product information registration request. In this embodiment, an example in which one piece of application information is associated with one piece of product information will be described, but a plurality of pieces of application information may be associated with one piece of product information. In that case, when one product is purchased, the customer can use application files of a plurality of associated application information. One piece of application information may be associated with different types of products.

  The license access number information holding unit 313 is means for holding a license access number information table that holds license access number information in the hard disk 224 of the license server 101. The license access number is a key necessary for using a product managed on the license server 101, and is a product key issued by the license server 101 for each designated product. When the license access number is notified to the license server 101, the application file and the license can be acquired via the Internet 102. FIG. 8C shows an example of the license access number information table 820 stored in the license access number information holding unit 313.

  In the license access number information table 820, a license access number column 821 is a column for storing a license access number. The product ID column 822 is a column for storing the product ID of a product that can be used by the license access number. Each record of the license access number information table 820 is referred to as a “license access number information record”, and a license access number information record is added in units in which the license access number is issued by the license access number issuance request receiving unit 323. One license access number is issued for one product.

  The usage information holding unit 314 is a unit that holds a usage information related table that holds usage information in the hard disk 224 of the license server 101. The usage information is information on a contract made between the customer and the sales company, and holds information as to which period the product is used in the image forming apparatus purchased by the customer. FIG. 9 shows an example of a usage information related table stored in the usage information holding unit 314. In the present embodiment, a configuration example using four tables as the usage information related table is shown. Here, for the image forming apparatus having the device serial number “AAA00130” purchased by the customer A from the sales company, the use of the product with the product ID “P0002” is changed from “April 1, 2016” to “December 2016. An example in which a contract is made until "31st" is shown. Similarly, it indicates that the use of the product having the product ID “P0004” is contracted from “April 1, 2016” to “May 15, 2016”. Similarly, the customer B makes a contract with the image forming apparatus whose device serial number is “BBB00240” for the product ID “P0002” from “January 1, 2016” indefinitely (blank on the table). tie. After that, a contract to use the image forming apparatus with the device serial number “CCC00350” from “April 15, 2016” to “April 30, 2017” is added to the product with the product ID “P0006”. Here is an example.

  Information managed in the usage information table 900 of FIG. 9A is stored in the usage information holding unit 314 when the usage information is registered by the usage information registration request receiving unit 324. The license access number column 901 is a column for storing the license access number of a product for which a contract with a customer is concluded. The device serial number column 902 is a column for storing the device serial number of the contracted image forming apparatus that has contracted with the customer. The contract start date column 903 is a column for storing the start date of the contract period concluded with the customer. The contract end date column 904 is a column for storing the end date of the contract period concluded with the customer. The group column 905 is a column for storing whether a new usage group is specified or an existing usage group is specified when usage information is registered by the usage information registration request receiving unit 324. The usage group ID column 906 is a column for storing usage group IDs. The usage group ID is an ID for collectively managing usage information in units of groups, for example, an ID used for collectively managing usage information in units of customers.

  The information managed in the usage group information table 910 in FIG. 9B is stored when a new usage group is designated when usage information is registered by the usage information registration request receiving unit 324. The usage group ID column 911 is a column that stores an ID for uniquely identifying a usage group. The usage group ID stored here is a value that the license server 101 automatically issues, but a specific ID that does not overlap may be used. The update license validity period column 912 is a column for storing the value of the validity period of the update license designated when the usage information is registered. Similarly, the closing date column 913 is a column for storing the closing date value specified when the usage information is registered. In this embodiment, contracts (applications) belonging to one usage group are managed so that the validity period and the closing date of the update license are the same.

  The validity period of the renewal license is a value that defines the validity period of the renewal license, and a monthly value can be specified. Note that the unit is not limited to this unit, and designation in other units such as a week unit or a year unit may be performed. The license server 101 issues an update license for each month set in the validity period of the update license. The closing date is a reference value for determining the date for issuing the renewal license, and a value in units of days can be designated. In other words, the closing date indicates an update timing for updating the license (timing for issuing the update license). For example, an update license is newly issued the day after the closing date. For example, when “20 days” is specified, an update license is issued once a month on the 20th, with one month as a predetermined cycle. The update license issuance timing here is not limited to this, and for example, time may be designated. In addition, when the day designated by the month does not exist, you may make it change to the day before and behind that. The license server 101 uses the license issuance unit 328 to change the valid period of the renewed license × n (n ≧ 1) months from the start date of the contract until the end date of the contract of the image forming apparatus, for the (n + 1) th time. Issue renewal licenses repeatedly.

  Information managed in the usage group information detailed table 920 in FIG. 9C is stored when a record is added to the usage group information table 910 shown in FIG. 9B and an update license is issued. The usage group ID column 921 is a column for storing the usage group ID of the record added to the usage group information table 910. The sequence number column 922 is a column for storing a number issued by the license server 101 for each usage group ID in order to sequentially manage information managed for each usage group ID in the usage group information detail table 920. The update license deadline column 923 is based on the contract start date of the usage information that is a trigger for adding the record of the usage group information table 910 (value managed in the contract start date column 903 of the usage information table 900). N of the validity period of the update license (value managed in the validity period column 912 of the update group information table 910) and the closing date of the month (value managed in the closing date column 913 of the use group information table 910) The column to store. That is, the closing date of the renewal license is based on the setting of the corresponding usage group, and is the closing date immediately before the end date of the renewal license (the last day of the validity period).

  The description will be supplemented by taking the first line in FIG. 9A and the first line in FIG. 9B as examples. In this example, the device serial number “AAA00130” can use the product with the product ID “P0001” specified by the license access number “LA01” from “April 1, 2016” to “December 31, 2016”. It is shown that. Further, the license server 101 belongs to the usage group of the usage group ID “G0001” newly issued. In the usage group ID “G0001”, as illustrated in FIG. 9A, the validity period of the update license is “1 month” and the closing date is “20 days”. Therefore, “April 20, 2016” which is “20th day” from “April 1, 2016” to “1st month” is stored in the closing date column of the update license.

  The update license end date column 924 is a contract start date of use information that is a trigger for adding a record of the use group information table 910 in FIG. 9B (a contract start date column 903 of the use information table 900). This is a column for storing the value of the date after the elapse of the validity period of the renewal license (the value managed in the renewal period of validity period 912 of the usage group information table 910).

  The supplementary explanation will be made by taking the first line in FIG. 9A and the first line in FIG. In this example, the date “April 30, 2016” after the passage of “one month” from “April 1, 2016” is stored. In the example of FIG. 9C, an example of storing the update license closing date and the end date of the update license for the first to third update licenses calculated from the usage information illustrated in FIG. 9A is stored. Show.

  Information managed in the usage information detail table 930 in FIG. 9D is stored in the usage information holding unit 314 when the license server 101 issues an update license, and the license access number, device serial number, and available license are stored. It is a table for managing. The license access number column 931 is a column for storing a license access number. The device serial number column 932 is a column for storing the device serial number of the image forming apparatus to be contracted with the customer.

  The license ID column 933 is a column for storing the license ID of the update license. The update license is generated when the usage information is registered by the usage information registration request receiving unit 324, and is periodically generated by the license issuing unit 328 as long as the contract with the customer continues. The license ID stored in the license ID column 933 is an ID uniquely assigned by a combination of values of both the application ID and the device serial number. Even if the application is the same, if the installation destination image forming apparatuses are different, the license IDs of the two image forming apparatuses are different. The storage path 934 is a column for storing the path where the update license is stored.

  The use start date column 935 is a column for storing the date when the renewal license becomes valid. The use end date column 936 is a column for storing the date when the renewal license becomes invalid. The confirmation date column 937 is a column that stores the date when the image forming apparatus starts the processing of the license update request transmission unit 352. In the case of the first renewal license issued at the time of usage information registration, the “contract start date” set in the target usage information is set as the value stored in the usage start date column 935. In the case of the second and subsequent renewal licenses, the date stored in the use start date column 935 is set to the date of the last renewal license.

  The value stored in the use end date column 936 is set to the end date of the update license of the use group to which the use information belongs. The value stored in the confirmation date column 937 is set to the date of closing of the update license of the usage group to which the usage information of the target image forming apparatus belongs. If the end date of the renewal license of the usage group to which the “contract end date” set in the usage information belongs is earlier than the end date of the renewal license associated with the usage group, Instead, the contract end date is stored. When the confirmation date exceeds the use end date, the same value as the use end date column 936 is stored in the check date column 937.

  The usage information detail table 930 in FIG. 9D shows information on the first and second update licenses generated with the information exemplified in the usage information table 900 in FIG. 9A. The description will be supplemented by taking the record on the fourth line in FIG. 9D as an example. In this example, the record on the fourth line represents the information on the second update license issued from the usage information on the record on the second line of the usage information table 900 in FIG. 9A. Since the record in the fourth row stores information on the second update license, the use start date column 935 displays “April 20, 2016” which is the closing date of the first update license (FIG. 9 ( D) (the value of the confirmation date column 937 in the third row) is stored. The use end date column 936 stores the end date “May 31, 2016” of the update license that is normally managed with the use group ID “G0001”. However, here, the contract end date of the target usage information is “May 15, 2016”, which is the date before the end date of the renewal license, so “May 31, 2016”. “May 15, 2016” is stored in the use end date column 936. Similarly, in the confirmation date column 937, the contract end date “May 15, 2016”, not the closing date “May 20, 2016” of the renewal license managed by the use group ID “G0001” is displayed. "Day" will be stored.

  The records in the usage information table 900 in FIG. 9A are referred to as “usage information records”, and usage information records are added in units of usage information registration by the usage information registration request receiving unit 324. The record in the usage group information table 910 in FIG. 9B is referred to as a “use group information record”, and is added when the usage information registered by the usage information registration request receiving unit 324 belongs to a new usage group. The record in the use group information detail table 920 in FIG. 9C is referred to as a “use group information detail record”. Usage group information detail records are added in units in which a new usage group is registered by the usage information registration request receiving unit 324 or in units in which an update license is issued by the license issuing unit 328. The records in the usage information detail table 930 in FIG. 9D are referred to as “usage information detail records”. The usage information detail record is added in units in which the first update license is issued by the usage information registration request receiving unit 324 or in units in which the second and subsequent update licenses are issued in the license issuing unit 328.

  The application information registration request receiving unit 321 is a function executed by receiving an application information registration request from the network I / F 226 provided in the license server 101. The application information registration request is transmitted from the information processing apparatus 121 located in the sales company network environment 120. The application information registration request receiving unit 321 acquires the application file 601 from the received application information registration request and stores it in the hard disk 224. In addition, the application information registration request receiving unit 321 acquires the application ID 602, the application name 603, and the application version 604 of the stored application file 601. Then, the application information registration request receiving unit 321 adds the path of the stored application file 601 and the acquired application ID 602, application name 603, and application version 604 to the application information table 800 as a new application information record.

  The product information registration request receiving unit 322 is a function that is executed by receiving a product information registration request from the network I / F 226 provided in the license server 101. The merchandise information registration request is transmitted from the information processing apparatus 121 located in the sales company network environment 120. Although this embodiment assumes that the product information registration request includes at least a product ID, a product name, a product type, and an application ID, this is not restrictive. The product information registration request receiving unit 322 adds the data acquired from the received product information registration request to the product information table 810 as a new product information record.

  The license access number issuance request receiving unit 323 is a function executed by receiving a license access number issuance request from the network I / F 226 provided in the license server 101. The license access number issuance request is transmitted from the information processing apparatus 121 located in the sales company network environment 120. The license access number issuance request includes at least the product ID. The license access number issuance request receiving unit 323 issues a license access number for the product with the product ID included in the acquired license access number issuance request, and returns it as a response to the request source.

  The usage information registration request receiving unit 324 is a function executed by receiving a usage information registration request from the network I / F 226 provided in the license server 101. The usage information registration request is transmitted from the information processing apparatus 121 or the contract server 122 located in the sales company network environment 120. The usage information registration request includes at least a license access number, a device serial number, a contract start date, and information for specifying a usage group (hereinafter referred to as usage group information). The usage group information includes information on whether usage information is registered in a new usage group or additionally registered in an existing usage group. Furthermore, when registering in a new usage group, information on the validity period and deadline of the renewal license is included. In addition, when registering in an existing usage group, a usage group ID for specifying the usage group is included. Also, the contract end date can be set as additional information.

  When the acquired usage information registration request is a request for creating a new usage group, the usage information registration request receiving unit 324 creates a usage group information record after newly issuing a usage group ID, and stores the usage group information in the usage group information table 910. to add. Also, the usage information registration request receiving unit 324 creates a usage group information detail record from the received contract start date, validity period of the renewal license, and closing date, and adds the usage group information detail record to the usage group information detail table 920.

  When the acquired usage information registration request is a request for registration in an existing usage group, the usage information registration request receiving unit 324 acquires a usage group information detail record that matches the received usage group ID from the usage group information detail table 920. . Further, the usage information registration request receiving unit 324 specifies a record in which the value of the update license deadline column 923 of the acquired usage group information detail record has a recent value after the received contract start date.

  In the case of a usage information registration request for creating a new usage group, the usage information registration request receiving unit 324 issues an initial update license using the value of the newly added usage group information detail record. Further, in the case of a usage information registration request for registration in an existing usage group, the usage information registration request receiving unit 324 issues an initial update license using the value of the specified usage group information detail record.

  The usage information registration request receiving unit 324 sets a unique identifier in the license ID 612 of the update license 611 to be issued. Further, the usage information registration request receiving unit 324 sets the application ID of the product identified from the license access number included in the usage information registration request in the application ID 613. Further, the usage information registration request receiving unit 324 sets the device serial number and the contract start date included in the usage information registration request in the device serial number 614 and the usage start date 615. Further, the usage information registration request receiving unit 324 sets the update license end date and the update license closing date of the usage group information detail record in the usage end date 616 and the confirmation date 617.

  If the contract end date included in the use information registration request is a date prior to the end date of the renewal license, the use information registration request receiving unit 324 indicates the use end date 616. Set the contract end date. Further, the usage information registration request receiving unit 324 sets the contract end date in the confirmation date 617 when the contract end date is earlier than the contract date of the renewal license.

  Further, the usage information registration request receiving unit 324 creates a usage information record including the received license access number, device serial number, contract start date, and usage group information, and adds the usage information record to the usage information table 900. Further, the usage information registration request receiving unit 324 creates a usage information detail record including information on the issued update license and adds it to the usage information detail table 930. Details of the processing of the usage information registration request receiving unit 324 will be described later with reference to the flowchart of FIG.

  The application file acquisition request receiving unit 325 is a function executed by receiving an application file acquisition request from the network I / F 226 provided in the license server 101. The application file acquisition request includes a license access number. The application file acquisition request receiving unit 325 returns an application file 601 related to the license access number included in the acquired application file acquisition request as a response.

  Specifically, the application file acquisition request receiving unit 325 acquires a license access number from the acquired application file acquisition request. Next, the application file acquisition request receiving unit 325 acquires a license access number information record that matches the acquired license access number from the license access number information table 820. Next, the application file acquisition request receiving unit 325 acquires from the product information table 810 a product information record that matches the product ID of the acquired license access number information record. Next, the application file acquisition request receiving unit 325 acquires an application ID from the acquired product information record. Next, the application file acquisition request receiving unit 325 acquires an application information record that matches the acquired application ID from the application information table 800. Then, the application file acquisition request receiving unit 325 returns the application file 601 of the file path included in the acquired application information record as a response.

  The license acquisition request receiving unit 326 is a function executed by receiving a license acquisition request from the network I / F 226 provided in the license server 101. The license acquisition request includes a license access number and a device serial number. The license acquisition request receiving unit 326 returns an updated license 611 corresponding to the acquired license access number and device serial number as a response.

  The license acquisition request reception unit 326 checks whether there is a usage information detail record that matches the license access number and the device serial number included in the received license acquisition request. Specifically, the license acquisition request receiving unit 326 specifies a record including the received license access number and device serial number from the usage information detail table 930. In the specified usage information detail record, if there is a record whose usage start date and usage end date satisfy "use start date ≤ current date ≤ use end date," The license acquisition request receiving unit 326 returns an update license 611 that satisfies the condition as a response. When there are a plurality of records that satisfy the condition, the license acquisition request receiving unit 326 returns an updated license 611 of the future record with the latest use end date as a response.

  The license update request receiving unit 327 is a function executed by receiving a license update request from the network I / F 226 provided in the license server 101. The license update request includes the device serial number and the application ID of the application file 601 for which an update license is to be obtained. The license update request receiving unit 327 returns an update license 611 as a response when there is usage information that is available for the acquired device serial number and application ID.

  Specifically, the license update request receiving unit 327 specifies a record including the application ID received from the product information table 810, and specifies a product ID included in the specified product information record. Next, the license update request receiving unit 327 specifies a record including the product ID specified from the license access number information table 820, and specifies a license access number included in the specified license access number information record. Further, the license update request receiving unit 327 specifies a record including the license access number specified from the usage information detail table 930 and the received device serial number. Then, the license update request receiving unit 327 sets the usage start date and usage end date in the specified usage information detail record to “use start date ≦ current date ≦ use end date. If there is a record that satisfies “date”, an update license 611 that satisfies the condition is returned as a response. When there are a plurality of records that satisfy the condition, the license update request receiving unit 327 returns, as a response, the update license 611 of the record whose use end date is the future.

  The license issuing unit 328 is a function provided in the license server 101 and executed periodically. The license issuing unit 328 determines whether or not the usage information update license 611 managed by the usage information table 900 needs to be issued, and issues the update license 611 when the issue is necessary.

  The license issuance unit 328 identifies a record in which the value of the confirmation date column 937 is the current date from the usage information detail table 930, and license access number / device serial number / license ID / use end date from the identified record. To get. Next, the license issuing unit 328 specifies a record including the license access number / device serial number acquired from the usage information detail table 930 from the usage information table 900. Further, the license issuing unit 328 acquires the contract end date / use group ID from the specified record. The license issuing unit 328 confirms whether the contract end date acquired from the usage information table 900 is equal to the usage end date acquired from the usage information detail table 930. If they are not equal, the license issuing unit 328 issues an update license 611. The license issuance unit 328 confirms whether or not it is necessary to issue an update license for all the records whose values in the confirmation date column 937 are the current date from the usage information detail table 930. Then, the license issuing unit 328 issues an update license 611 for the usage information that needs to be issued.

  The license issuing unit 328 sets the license ID acquired from the usage information detail table 930 in FIG. 9D as the license ID 612 of the update license 611 to be issued. The license issuing unit 328 sets the application ID of the product identified from the license access number acquired from the usage information detail table 930 as the application ID 613. Further, the license issuing unit 328 sets the device serial number acquired from the usage information detail table 930 as the device serial number 614 and sets the current date as the usage start date 615. The license issuing unit 328 sets the end date / end date value of the update license identified from the use group ID acquired from the use information table 900 in the use end date 616 and the confirmation date 617.

  Specifically, the license issuing unit 328 specifies, from the usage group information detail table 920, a record in which the usage group IDs acquired from the usage information table 900 match and the value of the update license deadline column 923 is the current date. . Then, the value of the sequence number column 922 (N) is acquired from the identified record. Furthermore, the license issuing unit 328 matches the usage group IDs acquired from the usage information table 900 of FIG. 9A from the usage group information details table 920, and the value of the sequence number column 922 is “N + 1”. Identify the record. Here, “N + 1” corresponds to the next issue of an update license. Then, the update license deadline / update license end date is acquired from the specified record. When the contract end date acquired from the usage information table 900 is a date prior to the end date of the renewal license acquired from the usage group information detail table 920, the license issuing unit 328 sets the usage end date 616. Sets the contract end date. Otherwise, the license issuing unit 328 sets the end date of the update license. Similarly, if the contract end date acquired from the usage information table 900 is a date prior to the closing date of the renewed license acquired from the usage group information detail table 920, the license issuing unit 328 sets the confirmation date 617. Sets the contract end date. Otherwise, the license issuing unit 328 sets a deadline date for the updated license.

  In addition, the license issuing unit 328 creates a usage information detail record including information regarding the issued update license 611 and adds the usage information detail record to the usage information detail table 930 in FIG. The issued update license 611 is returned as a response when a request is received from the license update request transmission unit 352.

(Image forming device)
Each part of the software configuration of the image forming apparatus 112 illustrated in FIG. 3B is executed when the CPU 207 loads a program stored in the hard disk 208 onto the volatile memory 210 in the image forming apparatus 112. Each table shown in FIG. 10 included in the image forming apparatus 112 is held in each memory or hard disk, and is read out or updated.

  The device information holding unit 341 has a function of holding a device information table (not shown) on the hard disk 208 of the image forming apparatus 112. A device information table (not shown) holds at least a device serial number for uniquely identifying the image forming apparatus 112.

  The device license information holding unit 342 has a function of holding the device license information table on the hard disk 208 of the image forming apparatus 112. FIG. 10A shows an example of the device license information table 1000 stored in the device license information holding unit 342.

  In the device license information table 1000 of FIG. 10A, an application ID column 1001 is a column for storing the application ID of the installed application file 601. The application version column 1002 is a column that stores the application version of the application file 601. The application name column 1003 is a column for storing the application name of the application file 601. The use start date column 1004 is a column for storing the date when the use of the application file 601 can start. The use end date column 1005 is a column for storing the date when the use of the application file 601 is ended. The confirmation date column 1006 is a column for storing the date when the license update request transmission unit 352 starts a license update request to the license server 101. The storage path column 1007 is a column for storing the path of the hard disk 208 of the image forming apparatus 112 that stores the application file 601.

  The image forming apparatus 112 determines whether the application file 601 is available based on information stored in the device license information table 1000. When “use start date ≦ current date ≦ use end date” is satisfied, the application file 601 is determined to be usable. The records in the device license information table 1000 are referred to as “device license information records”, and device license information records are added in units of installing the application file 601 using a license.

  The device license history information holding unit 343 has a function of holding the device license history information table 1010 in the hard disk 208 of the image forming apparatus 112. FIG. 10B shows an example of the device license history information table 1010 stored in the device license history information holding unit 343.

  In the device license history information table 1010, a license ID column 1011 is a column for storing a license ID of a license installed in the image forming apparatus 112. The application ID column 1012 is a column for storing the application ID of the license. The records of the device license history information table 1010 are referred to as device license history information records, and device license history information records are added in units of installing the update license 611 of the application file 601 using the license. The device license history information table 1010 is used to prevent the license period from being extended using a license with a license ID used in the past.

  The installation request receiving unit 351 is a function that is executed by receiving an installation request from the network I / F 205 of the image forming apparatus 112. The installation request is transmitted from the information processing apparatus 111. The installation request includes a license access number. The installation request receiving unit 351 transmits an application file acquisition request including a license access number included in the installation request and a device serial number held in the device information holding unit 341 and a license acquisition request to the license server 101.

  The installation request receiving unit 351 performs application file installation determination processing using the application file acquisition request and the application file 601 returned in response to the license acquisition request and the license. The installation request reception unit 351 determines that installation is possible when the following three conditions are satisfied. The first is that the application ID included in the acquired license matches the application ID of the application file. Secondly, the device serial number of the acquired license matches the device serial number held in the device information holding unit 341. Third, the license ID of the acquired license does not exist in the device license history information table 1010.

  When the three conditions are satisfied, the installation request receiving unit 351 determines that the application file 601 can be installed, and adds a device license information record to the device license information table 1000 based on the acquired application file 601 and license information. . Further, the installation request receiving unit 351 adds a device license history information record to the device license history information table 1010 based on the acquired application ID and license ID of the license.

  The license update request transmission unit 352 has a function of transmitting a license update request to the license server 101. The license update request transmission unit 352 presses the server license confirmation button 507 when the confirmation date of the record included in the device license information table 1000 exceeds the current date. If executed.

  When the license update request transmission unit 352 is executed, the application ID of the record in which the confirmation date exceeds the current date in the device license information table 1000 or the record in which the license confirmation button 507 is pressed is displayed. To get. Further, the license update request transmission unit 352 acquires the device serial number stored in the device information holding unit 341. Next, the license update request transmission unit 352 transmits a license update request including the acquired application ID and device serial number. The license update request transmission unit 352 acquires the license returned as a response, and updates the use start date, use end date, and confirmation date of the device license information record using the license.

  The application management screen display request receiving unit 353 is a function executed by receiving an application management screen display request from the network I / F 205 of the image forming apparatus 112. The application management screen display request is transmitted from the information processing apparatus 111. The application management screen display request receiving unit 353 transmits data for displaying the application management screen 501 to the information processing apparatus 111 that is the request source. The application management screen display request receiving unit 353 is executed when an application management screen display request is received from the image forming apparatus 112, and transmits data for displaying the application management screen 501 on the display unit 211 of the image forming apparatus 112. May be.

[screen structure]
FIG. 4 shows an example of a screen provided by the license server 101. The usage information registration screen 401 is a screen for transmitting a usage information registration request to the license server 101. The usage information registration screen 401 is returned as a response from the license server 101 when a usage information registration request is transmitted from the browser (not shown) of the information processing apparatus 121 to the usage information registration request receiving unit 324 of the license server 101. The usage information registration screen 401 is returned in a format that can be displayed on the display unit 221 of the information processing apparatus 121.

  The license access number field 402 is a text field for inputting a license access number for specifying a product purchased by a customer. The device serial number field 403 is a text field for inputting a device serial number for specifying an image forming apparatus (for example, the image forming apparatus 112) purchased by the customer. The contract start date field 404 is a text field for inputting the date on which the contract is started. The contract end date field 405 is a text field for inputting the date to end the contract. The usage group field 406 is a field for specifying target usage group information, and includes the following fields.

  When registering the usage information to be registered in a new usage group, the radio button of the new group field 407 is selected. When registering in the existing usage group, the radio button of the existing group field 408 is selected. Only one of the new group field 407 and the existing group field 408 can be selected. The renewal license validity period field 409 and the closing date field 410 are text fields that can be entered when the radio button of the new group field 407 is selected. The update license validity period field 409 is a text field for designating the validity period of the update license issued by the license server 101 on a monthly basis. The closing date field 410 is a text field for designating a date that serves as a reference date for the date on which the license server 101 issues an update license. The use group ID field 411 is a text field that can be input when the radio button of the existing group field 408 is selected, and is a text field that specifies a use group ID for specifying which use group the use information is registered in. It is.

  When the registration button 412 is pressed, a usage information registration request is transmitted to the license server 101 via the network I / F 226 of the information processing apparatus 121 by a browser (not shown). At that time, the usage information registration request includes the value specified in each field. It should be noted that the values of the new group field 407, the renewal license validity period field 409, and the closing date field 410, the existing group field 408, and the use group ID field 411 include only one set of values.

  FIG. 5 shows an example of a screen provided by the image forming apparatus 112. The application management screen 501 is a screen for displaying information on installed application files and licenses and updating licenses. The application management screen 501 is returned as a response from the image forming apparatus 112 when an application management screen display request is transmitted from the browser or the like of the information processing apparatus 111 to the application management screen display request receiving unit 353 of the image forming apparatus 112. The application management screen 501 is returned in a format that can be displayed on the display unit 221 of the information processing apparatus 111. In the case of a request from the display unit 211 of the image forming apparatus 112, it is returned in a format that can be displayed on the display unit 211 of the image forming apparatus 112.

  The labels 502 to 506 displayed on the application management screen 501 are set based on the records in the device license information table 1000 in FIG. The application ID label 502 displays the value of the application ID column 1001 of the device license information table 1000. The application name label 503 displays the value in the application name column 1003 of the device license information table 1000. The application version label 504 displays the value of the application version column 1002 of the device license information table 1000. The available period label 505 is ““ use start date ”−“ use end date ”” based on values in the use start date column 1004 and use end date column 1005 of the device license information table 1000. Displays period information in the form The confirmation date label 506 displays the value in the confirmation date column 1006 of the device license information table 1000.

  A license confirmation button 507 is a button for transmitting a license update request to the license server 101. Here, a button for transmitting a license update request to each application is provided. When the license confirmation button 507 is pressed, a license update request is transmitted to the license server 101 via the network I / F 205 of the image forming apparatus 112. At this time, the license update request includes the value of the application ID of the record in which the license confirmation button 507 is pressed and the device serial number held in the device information holding unit 341.

[data structure]
FIG. 6 shows an example of the data structure of the file. 6A shows an example of the data structure of the application file 601, and FIG. 6B shows an example of the data structure of the update license 611. Note that other information may be included in the data structure.

  An application file 601 shown in FIG. 6A is an extension program file for installation so that the extension function can be used later in addition to the basic function. The application file 601 holds information of at least 602 to 605. The application ID 602 is an identifier (identification information) for uniquely identifying the type of the application file 601. An application name 603 and an application version 604 are the name and version of the application file 601, respectively. The execution file 605 is a program (program code) that runs on the image forming apparatus 112.

  The update license 611 shown in FIG. 6B is issued at the time of usage information registration by the usage information registration request receiving unit 324 or when the conditions for issuing are satisfied by the license issuing unit 328. The update license 611 holds information of at least 612 to 617. The license ID 612 is an identifier that can uniquely identify a license. The application ID 613 is an identifier of the application file 601 that can be installed with this license. The device serial number 614 is a serial number of the image forming apparatus 112 that can be installed with this license. The use start date 615 and the use end date 616 are the date when the use of the application file 601 can be started by this license and the date when it ends. The confirmation date 617 is the date when the image forming apparatus in which the update license 611 is installed starts transmitting a license update request to the license server 101.

[Processing flow]
A flowchart of processing according to the present embodiment will be described with reference to FIG. FIG. 7 is a flowchart of processing executed when the usage information registration request receiving unit 324 receives a usage information registration request via the network I / F 205 in the license server 101. As described above, the usage information registration request receiving unit 324 is realized by the CPU 223 of the license server 101 executing a program stored in the hard disk 224 or the like, and executes this processing. The usage information registration request is transmitted from the information processing apparatus 121 or the contract server 122 of the sales company. The usage information registration request receiving unit 324 generates a new usage group and issues an update license for the target image forming apparatus based on the license access number, device serial number, and usage group information included in the received usage information registration request. .

  In S701, the usage information registration request receiving unit 324 receives the usage information registration request.

  In S702, the usage information registration request receiving unit 324 acquires the license access number / device serial number / contract start date / contract end date / use group information from the use information registration request received in S701.

  In S703, the usage information registration request receiving unit 324 registers the license access number / device serial number / contract start date / contract end date acquired in S702 in the usage information table 900.

  In S704, the usage information registration request receiving unit 324 determines whether a new group or an existing group is specified from the usage group information acquired in S702. Specifically, as described above, the value is set depending on whether the radio button of the new group field 407 is selected on the usage information registration screen 401 or the radio button of the existing group field 408 is selected. If a new group is specified (YES in S704), the process proceeds to S705. If an existing group is specified (NO in S704), the process proceeds to S711.

  In S705, the usage information registration request receiving unit 324 determines that the usage information registered in the usage information registration request received in S701 belongs to a new group, and issues a new usage group ID. The usage group ID is identification information for uniquely specifying the usage group in the license server 101. The used usage group ID is set in the usage group ID column 906 of the record newly added in S703 in the usage information table 900.

  In S706, the usage information registration request receiving unit 324 acquires the validity period / deadline date of the update license from the usage group information acquired in S702. Specifically, the values set in the update license validity period field 409 and the closing date field 410 of the usage information registration screen 401 are acquired.

  In S707, the usage information registration request receiving unit 324 registers in the usage group information table 910 the usage group ID issued in S705 and the validity period / deadline of the update license acquired in S706.

  In S708, the usage information registration request receiving unit 324 calculates the value of the closing date / end date of the first renewal license from the contract start date acquired in S702 and the validity period / closing date of the renewal license acquired in S706. To do. Specifically, the date when the renewal license is valid for the first month from the contract start date is the date of the first renewal license, and the year when the renewal license expires from the contract start date The date is the end date of the renewal license. As a specific example, supplementary explanation will be made using a case where the contract start date is April 1, 2016, the validity period of the renewal license is two months, and the closing date is 20 days. The deadline for the first-time renewal license is the 20th day set to the May 2016 deadline, which is the second month from April 1, 2016, and is May 20, 2016. Similarly, the end date of the renewal license issued for the first time is May 31, 2016 after two months have passed since April 1, 2016.

  In S709, the usage information registration request receiving unit 324 calculates the (n + 1) th update license validity period / closing date value from the closing date / end date value of the first updating license calculated in S708 (n ≧). 1). Specifically, a value obtained by adding the renewal license validity period × n to the renewal license expiration date / end date calculated in S708 is calculated as the (n + 1) th renewal license validity period / closing date value. The Supplementing with the specific example of S708, the closing date of the second renewal license is 2 months on May 20, 2016 plus July 20, 2016, and the end date of the renewal license is 2 months on May 31, 2016 Plus it will be July 31, 2016. Similarly, the closing date of the third renewal license is September 20, 2016, and the end date of the renewal license is September 30, 2016. Here, an example is shown in which the closing date / end date of the (n + 1) -th renewal license is collectively calculated, but only the closing date / end date of the renewal license up to the second time is calculated, and the m (m ≧ 3) th and subsequent times are calculated. The update date / end date of the update license may be calculated at the timing when the license issue unit 328 issues the update license at the (m−1) th time.

  In S710, the usage information registration request receiving unit 324 associates the value of the closing date / end date of the update license for n times calculated in S708 and S709 with the usage group ID issued in S705, and uses the usage group information detailed table 920. Register with.

  In S711, the usage information registration request receiving unit 324 determines that the usage information registered in the usage information registration request received in S701 belongs to an existing group, and acquires the usage group ID from the usage group information acquired in S702. Specifically, the value set in the usage group ID field 411 of the usage information registration screen 401 is acquired. The acquired usage group ID is set in the usage group ID column of the record newly added in S703. Thereafter, the process proceeds to S715.

  In S712, the usage information registration request receiving unit 324 acquires a record including the usage group ID acquired in S711 from the usage group information detailed table 920.

  In S713, the usage information registration request receiving unit 324 determines the date of the closing date of the update license closest (immediately after) the contract start date acquired in S702 from the usage group information detail record acquired in S712. Identify records that contain.

  In S714, the usage information registration request receiving unit 324 sets the deadline / end date values of the update license of the usage group information detail record specified in S713 for the first time of usage information registered in the usage information registration request received in S701. Set the deadline / end date of the renewal license. This will be supplemented with a specific example in which the validity period of the renewal license described in S709 is added to an existing group of 2 months and the closing date is 20 days. In this case, when the contract start date acquired in S <b> 702 is July 20, 2016, the closest update license due date after July 20, 2016 is July 20, 2016. Further, the closing date of the first renewal license of the usage information to be registered acquired in S702 is July 20, 2016. The end date of the first renewal license is July 31, 2016 because the end date of the renewal license in the use group information detail record same as July 20, 2016 is used.

  In S715, the usage information registration request receiving unit 324 confirms whether the end date of the first renewal license specified in S708 or S714 is a date after the contract end date acquired in S702. If the end date of the first renewal license is a date after the contract end date (YES in S715), the process proceeds to S716; otherwise (NO in S715), the process proceeds to S719.

  In S716, the usage information registration request receiving unit 324 changes the end date of the first update license of the usage information registered in the usage information registration request received in S701 to the contract end date acquired in S702.

  In S717, the usage information registration request receiving unit 324 confirms whether the closing date of the first renewal license specified in S708 or S714 is a date after the contract end date acquired in S702. If the date of the first renewal license is the date after the contract end date (YES in S717), the process proceeds to S718; otherwise (NO in S717), the process proceeds to S719.

  In S718, the usage information registration request receiving unit 324 changes the contract date of the initial update license of the usage information registered in the usage information registration request received in S701 to the contract end date acquired in S702.

  In S719, the usage information registration request receiving unit 324 registers the usage information registration request received in S701 using the deadline / end date values of the initial update license specified in S708, S714, S716, and S718. Issue an initial update license for information.

  In S720, the usage information registration request receiving unit 324 registers the update license information issued in S719 in the usage information detail table 930. Then, this processing flow ends.

  As described above, in response to a usage information registration request, information on a new usage group is created, and in the case of usage information to be registered in an existing usage group, the information associated with the registered usage group is used. An update license 611 can be issued.

  Simply update from the value of the validity period (2 months) / closing date (20 days) of the renewal license managed for each usage group and the value of the contract start date (July 20, 2016) of the usage information to be additionally registered A case where a license is issued will be described. In this case, the use start date is July 20, 2016, the use end date is September 20, 2016 after two months have passed, and the confirmation date is the 20th day of the second month 2016. September 20th. Thus, depending on the contract start date of the usage information to be additionally registered, the end date of the renewal license and the confirmation date may be the same date. As a result, if the image forming apparatus cannot acquire the next renewed license on the confirmation date, the license expires and the extended function cannot be used.

  On the other hand, according to the present invention, the expiration date / date of the update license based on the validity period / closing date value of the update license managed for each usage group and the contract start date / time date of the usage information that triggers creation of the usage group. Calculate a reference value for the end date. With this configuration, as shown in the example of S714, from the usage information additionally registered in the existing usage group, the usage start date is July 20, 2016 and the usage end date is July 31, 2016. An update license with a margin can be issued in the license update period whose date is July 20, 2016. As a result, it is possible to reduce the risk that the continuous use of the extended function stops in the middle.

  As described above, the license server 101 can easily manage and update the usage information by managing the usage information in units of groups, and can reduce the system load of the license server 101. In addition, for the usage information to be added later to an arbitrary usage group, an update license with a margin can be issued during the license update period, and the usage information can be continuously used without stopping the use of the extended function of the image forming apparatus 112. Can be made.

<Second Embodiment>
As a second embodiment according to the present invention, a case will be described in which the contract start date of usage information that triggers creation of a new usage group is later than the contract start date of usage information to be added later. . Note that the description of the same configuration and processing as those in the first embodiment is omitted.

  In the example described in S708 of FIG. 7, the value of the record to be stored in the usage group information detail table 920 of FIG. 9C is calculated starting from the contract start date of usage information serving as a trigger for creating a new usage group. doing. For example, let us consider a case where the contract start date starting from a new usage group with a renewal license validity period of 3 months / closing date of 20 days is the future (January 1, 2017). At this time, in the record added to the usage group information detailed table 920 in FIG. 9C, the update license deadline is “March 20, 2017” and the update license end date is “March 31, 2017”. It becomes. In this case, after creating a new usage group, usage information whose contract start date is “October 1, 2016” is additionally registered for the created usage group. As a result, the update license issued for the first time has a use start date of “October 1, 2016” and a use end date of “March 31, 2017” identified from the use group information detailed table 920 in FIG. 9C. The confirmation date is “March 20, 2017”. Therefore, an update license having a longer valid period than expected is issued.

  The present embodiment includes a configuration for solving the above problems. If the contract start date of the usage information that triggers the creation of a new usage group is later than the contract start date of the usage information to be added later, the record of the usage group information detail table 920 is re-read. create. Specifically, it is checked whether the contract start date of the usage information that is a trigger for creating a new usage group is later than the contract start date of the usage information that is additionally registered later. If it is in the future, the deadline / end date value of the renewal license is recalculated starting from the contract start date of the usage information to be additionally registered. Supplementing the explanation with the above example, since the contract start date of the usage information to be additionally registered is “October 1, 2016”, the closing date of the renewal license is the month in which three months have passed since “October 1, 2016” This is “December 20, 2016”, the 20th of The end date of the renewal license is “December 31, 2016” in a month three months after “October 1, 2016”. Further, the closing date / end date of the n + 1 (n ≧ 1) renewal license is a date obtained by adding 3 months × n to the date of each item. After recalculating the closing date / end date of the renewal license, the record of the use group information detail table 920 in FIG.

  As another means, when the contract start date of the usage information that triggers the creation of a new usage group is later than the contract start date of the usage information to be additionally registered, a record in the usage group information detail table 920 is displayed. There is a way to add rather than recreate it. Specifically, when the contract start date of the usage information that triggers the creation of a new usage group is a date that is later than the contract start date of the usage information that is additionally registered, the usage group information detail table 920 From among the records managed in association with the use group ID, the record having the smallest sequence number is specified. Then, “the specified update license deadline—the validity period of the update license × (n + 1) <the contract start date of the usage information to be additionally registered ≦ the specified update license deadline—the validity period of the update license × n (n ≧ 1) N) satisfying “)” is calculated. Records for the calculated value n are added to the usage group information detail table 920. When adding, the sequence number is updated so that each record is in ascending order of date. A large value may be set in advance so that the sequence number does not need to be updated even if a record is added later.

  The deadline of the renewal license specified from the usage group information detailed table 920 of FIG. 9C is “March 20, 2017”, and the contract start date of the usage information to be additionally registered is “October 1, 2016”. The explanation will be supplemented with an example in which the validity period of the renewal license is two months. In this case, the closing date of the renewal license one time before “March 20, 2017” is “January 20, 2017” two months ago, and the closing date of the renewal license two times before is “2 × 2 months ago” “November 20, 2016”, the closing date of the renewal license three times before is “September 20, 2016” 3 × 2 months ago. That is, n = 2, “September 20, 2016 <October 1, 2016 ≦ November 20, 2016” is the value of n that satisfies the condition. In the usage group information detail table 920, the update license deadline is “November 20, 2016” “January 20, 2017”, and the end date of the update license is “November 30, 2016” “January 2017”. Two records, “31st” are added. In addition, the first renewal license issued from the usage information to be additionally registered has a start date “October 1, 2016”, an end date “November 30, 2016”, and a confirmation date “ November 20, 2016 ".

  In the present embodiment, an example is shown in which the value of the usage group information detail table 920 is updated / added when the contract start date of usage information that is a trigger for creating a new usage group is in the future. In this case, the update license information that has already been issued is not affected by referring to the values in the use group information detail table 920. Information managed in the use group information detail table 920 is information used when an update license is issued.

  As described above, in addition to the effects of the first embodiment, it is possible to appropriately issue an update license even when there is a mismatch between the newly added usage information and the usage information already registered.

<Other embodiments>
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

DESCRIPTION OF SYMBOLS 101 ... License server, 102 ... Internet, 110 ... Customer network environment, 111 ... Information processing apparatus, 112 ... Image forming apparatus, 120 ... Sales company network environment, 311 ... Application information holding part, 312 ... Merchandise information holding part, 313 ... License Access number information holding unit, 314 ... usage information holding unit, 321 ... application information registration request receiving unit, 322 ... product information registration request receiving unit, 324 ... usage information registration request receiving unit

Claims (10)

A license server that issues licenses used to run applications,
First management means for managing group information indicating an update timing for updating a license in a valid period and a predetermined cycle for each group;
Second management means for managing an application and a group to which the application belongs in association with each other;
Issuing means for issuing a license for the application for which the validity period is set based on a group to which the application belongs and group information of the group;
A registration means for accepting registration of a new application,
When the new application registered by the registration unit belongs to an existing group managed by the first management unit, the issuing unit is configured to issue the existing application in the initial license issuance for the new application. A license server that issues a license so that the license is updated at the latest update timing indicated by the group information of the existing group regardless of the validity period of the license indicated by the group information of the group. The issuing means issues a license for the second and subsequent times for the application.
The validity period of the license is the validity period indicated by the group information of the group to which the application belongs,
The license server according to claim 1, wherein the next update timing of the license is an update timing indicated by group information of a group to which the application belongs immediately before the end of the validity period of the license. The second management means further manages a period in which a license for an application can be issued and a group to which the application belongs in association with each other,
The license validity period for the application issued by the issuing means is set to be within a period during which the license can be issued,
The license update timing for the application issued by the issuing means is set so as to be updated at the predetermined cycle within a period during which the license can be issued. The listed license server. When the new application registered by the registration means belongs to a new group, the issuing means, in issuing an initial license for the new application,
The validity period of the license is the period from the start date of the period during which the license can be issued for the new application to the validity period indicated by the group information of the new group,
4. The license server according to claim 3, wherein the next update timing of the license is an update timing indicated by the group information of the new group from the end of the validity period of the license. The registration means includes
When accepting registration of a new application, accept setting of whether the new application belongs to a new group or an existing group managed by the first management means,
5. The license server according to claim 1, wherein when the license server belongs to the new group, the license server further receives designation of a license validity period and an update timing in the new group.   6. The license server according to claim 1, wherein the predetermined cycle of the update timing is designated by any one of year, month, or week.   The license server according to any one of claims 1 to 6, wherein the validity period of the license is specified in any one of a year unit, a month unit, a week unit, and a day unit. First management means for managing group information indicating an update timing for updating a license in a valid period and a predetermined cycle for each group;
Second management means for managing an application and a group to which the application belongs in association with each other;
A license management method in a license server comprising:
Issuing step of issuing a license for the application for which the validity period is set based on the group to which the application belongs and the group information of the group;
A registration process for accepting registration of a new application,
In the issuing step, when the new application registered in the registration step belongs to an existing group managed by the first management unit, the existing application is issued in the first license issuance for the new application. A license management method for issuing a license so that the license is updated at the latest update timing indicated by the group information of the existing group regardless of the validity period of the license indicated by the group information of the group . Computer
A first management unit for managing group information indicating an update timing for updating a license at a license validity period and a predetermined cycle for each group;
Second management means for managing an application and a group to which the application belongs in association with each other;
An issuing means for issuing a license for the application for which the validity period is set based on a group to which the application belongs and group information of the group;
Function as a registration means to accept registration of new applications,
When the new application registered by the registration unit belongs to an existing group managed by the first management unit, the issuing unit is configured to issue the existing application in the initial license issuance for the new application. A program for issuing a license so that it is updated at the latest update timing indicated by the group information of the existing group regardless of the validity period of the license indicated by the group information of the group.   A system comprising: the license server according to claim 1; and one or more image forming apparatuses provided with the application.

Images